Support

Problems? Questions? Suggestions? Write your message below. – See also the FAQ or try to catch us in IRC.

Your request has been forgotten? Feel free to post a reply to bump the thread to the top. The thread summarization feature is broken, see Phab:T245109. Very old threads have been archived.

I'm not sure nowiki works like this with a parameter. Usually, all parameters are shown with their raw text, for example <nowiki>{{{1}}}</nowiki> will remain {{{1}}} even when transcluded. It usually requires a {{#tag:nowiki|{{{1}}}}} to transclude a parameter within nowiki tags.

This is a change made in mwr:66749. Please comment in code review so the developer can look into it.

I think it will be good idea to add GENDER support for the word "user" to the following messages, unless technical restrictions make it difficult like in the case of Logouttext:

• Noemail ("There is no email address recorded for user "$1".")
• Blockedtitle ("User is blocked")
• Blocked-notice-logextract ("This user is currently blocked.

The latest block log entry is provided below for reference:")

• Customcssjsprotected ("You do not have permission to edit this page, because it contains another user's personal settings.")

Thanks.

• noemail: done in mwr:66933
• Blockedtitle: I think this message may be incorrect, and may have to be rephrased. It is used in OutputPage::blockedPage(), which has the following documentation: "Produce a "user is blocked" page.". I may be wrong, but not making changes here now.
• Blocked-notice-logextract: GENDER already supported. Documentation updated.
• Customcssjsprotected: Because of code structure, adding GENDER support here would be more complex than we would really like. Not changing.

Should be changed to "reason" for consistency with other similar messages and to not make it sound that optional. One should generally always write a reason for why to revert a file.

 Done mwr:66932.

Should use GENDER support, for example it's common in French to use different adjective endings depending on one's gender. Thanks.

I am a bit unsure if it would be wise to support GENDER because this message is shown after logout. At least the gender of the last user on (semi) public terminals could be revealed.

Right, I recognize the problem.

Hi,

I came here to tell you that the interface of Uyghur Wikipedia is still in Uyghur latin. Could you please switch it to Uyghur Arabic because the majority of Uyghurs prefer using it instead.

Thanks.

Both versions do not have their "most wanted" messages done but the Arabic version is the one best developed.

I would propose that we make the change if there is substantial effort in localising it (in either of the localisations). For now about 30% of MediaWiki has been localised in the Arabic script, and 5% in the Latin script. Neither localisation has had any contributions in the past 200 days. Please help us address that first, Jose.

There have been substantial effort in localising the Uyghur arabic interface messages, especially during the period from May 16 - 22, as could be seen here. This means that only 32 (1.3%) out of 2421 messages need to be localised.

Is there also a requirement that the Uyghur Latin version also needs to be localised before Uyghur Wikipedia interface is switched to the Uyghur Arabic script?

 Done mwr:66912. Might take a while for Wikimedia to update this, unless you request an update of MessagesUg.php in bugzilla:.

"Take Me Back" should be changed to "Take me back" because of the proper capitalization and for consistency with Prefswitch-main-on. Thanks.

 Done mwr:66879

Converted a few tables from MyISAM to InnoDB. Took a while for some tables, causing the wiki basically to be read-only, and lighttpd to serve some '500' errors.

ALTER TABLE `bw_text` ENGINE = InnoDB; 5 min 45.90 sec */
ALTER TABLE `bw_archive` ENGINE = InnoDB; 54.54 sec */
ALTER TABLE `bw_logging` ENGINE = InnoDB; 1 min 22.49 sec */
ALTER TABLE `bw_watchlist` ENGINE = InnoDB; 21 min 48.14 sec */
ALTER TABLE `bw_templatelinks` ENGINE = InnoDB; 4.37 sec */
ALTER TABLE `bw_pagelinks` ENGINE = InnoDB; 25.69 sec */
ALTER TABLE `bw_categorylinks` ENGINE = InnoDB; 0.91 sec */
ALTER TABLE `bw_externallinks` ENGINE = InnoDB; 12.14 sec */
ALTER TABLE `bw_imagelinks` ENGINE = InnoDB; 0.28 sec */
ALTER TABLE `bw_revision` ENGINE = InnoDB; 1 hour 44 min 57.29 sec */

Two tables to go, will try and find a faster solution for those...

ALTER TABLE `bw_page` ENGINE = InnoDB; /* 1 hour 10 min 33.22 sec on test db */
ALTER TABLE `bw_recentchanges` ENGINE = InnoDB; /* 54 min 50.80 sec on test db */

Stable-log-restriction ("Auto-review: requires "$1" permission"): Should it say "requires" instead of "require"?

 Done mwr:66853.

The following messages should have been fuzzied:

• Revreview-accuracy-0 ("Inadequate")
• Revreview-depth-0 ("Inadequate")
• Revreview-style-0 ("Inadequate")
• Review too low ("Revision cannot be reviewed with some fields left "inadequate".")

 Done

In Pt-parse-open is the word "template" referring to a MediaWiki template?

Translation template is the structure of translation page, where the place for translation of each section is marked with a placeholder.

I have added a draft FAQ on ensuring consistent localised terminology. Is what I have written good sense? Is there anything which could be usefully added on this topic? Is there a help page where this section could be usefully copied?

Looks fine.

Also propose putting links on each project page to glossaries on the project websites, if available, as resource to translators.

Just do it...

OK, 1 down, 14 to go.

What does the message Usermessage-summary ("Leaving system message.") mean?

And the message Usermessage-editor ("System messenger")?

• Usermessage-summary : the edit summary for a system message
• Usermessage-editor : the user that is the editor of system messages

What does "Leave system message" mean in that context?

Any message that is posted because of a system event - whichever you can think of. Currently only a failed asynchronous upload is notified as far as I know.

"Leave" should be translated as a verb, as in "To exit", "To go away"?

I'll update it to "Leaving".

Why not use System message editor instead of System messenger? I didn't know the word messenger used in the sense of message editor, a person who edits messages. For me the word messenger denotes a program, not a person. Of course I know that the general meaning of this word is bearer of messages.

Is this alternative definition of 'system messeger' correct? A system editor which leaves a message notifying that a system event has happened.

Wikia:Founderemails-email-3-days-passed-body-HTML/en: should have a comma after $FOUNDERNAME like this "$FOUNDERNAME,".

 Done - also for another message in the same extension.

Could someone use a bot to replace all "voltar" with "volver" for all Galician (gl) messages? Thanks you.

Sure. Running.

 Done -- btw, for the 31 changes made, this wasn't really worth the effort of extracting page names from the database, renaming namespace IDs to namespace names, and configuring the bot (~25 mins of work). Please make an estimate of how many changes will have to be made, and if it is in the tens, please do not make a bot request, but see if you can do it manually.

Sorry, but there are still many massages containing verb "voltar" which remains unchanged.

Apparently you didn't mention that 'Voltar' also had to be replaced with 'Volver'.

113 replacements in total now.

Should refer to version 1.16.

 Done

Wikia:Multilookupnbrresult/en (Number of results:): it apperas that this should say "results" instead of "result". Anyone able to confirm?

Already fixed per Thread:Support/MediaWiki:Multilookupnotspecify/en.

Wikia:Multilookupnotspecify/en (You have not specified an IP address yet.): "a IP" should be "an IP".

 Done All messages for the extension cleaned up.

After a long discussion at [1] we decided to migrate ro.wp from s/t-cedilla (ţ, ş) to s/t-comma (ț, ș). I have changed the namespace names at [2], but we need the old names to be kept as aliases.

Below is a list of standard namespaces with the _OLD_ spelling. They need to be used for _ALIASES_:

1: Discuţie
3: Discuţie Utilizator
5: Discuţie Wikipedia
6: Fişier
7: Discuţie Fişier
9: Discuţie MediaWiki
11: Discuţie Format
13: Discuţie Ajutor
15: Discuţie Categorie

In addition to that, there are 2 more namespaces specific to the Romanian Wikipedia which need to be converted (from the form on the left to the form on the right):

101: Discuţie Portal -> Discuție Portal
103: Discuţie Proiect -> Discuție Proiect

A bugzilla bug with the same request exists [3] and should be closed after making the changes.

Thank you for your help.

[1] http://ro.wikipedia.org/wiki/Discu%C5%A3ie_Wikipedia:Sfatul_B%C4%83tr%C3%A2nilor#Concluzii_finale

[2] http://translatewiki.net/w/i.php?language=ro&module=namespace&title=Special%3AAdvancedTranslate

[3] https://bugzilla.wikimedia.org/show_bug.cgi?id=22616

Linked to the request above, I want to ask you if there is anyone able and willing to run a bot to replace ţ,ş with ț,ș in all the Romanian translations. This needs to happen at a later time, after all the preparations are finished on ro.wp.

Will make the replacements now, and ask Raymond to hold off on committing 'ro' until the namespaces are active. Committed the namespaces in mwr:66591, so Wikimedia can merge per bugzilla:22616.

Bot is running now. Will probably take a while.

SieBot made between 3,000 and 3,500 updates in ~10,000 /ro pages.

'ro' excluded in script 'bpmw' for the moment.

Please give me a ping when preparations are finished. Then I will export the changes from translatewiki into SVN. The day after my export it will be live on all Wikimedia projects.

I have just reactivated 'ro' in the MediaWiki export, so Raymond will most probably automatically export the Romanian updates later today, if he remembers to use the correct export window :).

I'm afraid it is still too early. Please hold on until we can have all the preparations finished - I estimate another week or so.

It was committed last evening and is probably live already in the entire Wikimedia cluster since early this morning (CEST).

Explicitly refer to Wikimedia Commons, what is Wikimedia projects centric. Will be issue for independent shared repository installations.

This is an exception that will prove the rule.