Jump to navigation Jump to search

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

Your request has been forgotten? It's suggested to use {{Support}} in thread summaries, see also documentation.

First page
First page
Last page
Last page

Refresh special pages and request for SQL query

Hi, can you refresh SpecialPages like WantedPages and etc.. because content is not updated more than one year? Too, if you can, can you ask SQL for list of pages with translations which exists for Bosnian but no for Serbian Cyrillic? You can put result on /query-output subpage of my user page..


Zoranzoki21 (talk)22:04, 9 September 2018
Statistics                     [callback] completed in 0.50s
Ancientpages                   [QueryPage] got 1000 rows in 1m 28.90s
BrokenRedirects                [QueryPage] got 2 rows in 0.17s
Deadendpages                   [QueryPage] got 1000 rows in 10.30s
DoubleRedirects                [QueryPage] got 24 rows in 0.09s
FileDuplicateSearch            [QueryPage] cheap, skipped
ListDuplicatedFiles            [QueryPage] got 1 rows in 0.01s
LinkSearch                     [QueryPage] cheap, skipped
Listredirects                  [QueryPage] got 1000 rows in 0.24s
Lonelypages                    [QueryPage] got 1000 rows in 0.33s
Longpages                      [QueryPage] cheap, skipped
MediaStatistics                [QueryPage] got 9 rows in 0.13s
MIMEsearch                     [QueryPage] cheap, skipped
Mostcategories                 [QueryPage] got 621 rows in 1.18s
Mostimages                     [QueryPage] got 352 rows in 0.42s
Mostinterwikis                 [QueryPage] got 0 rows in 0.01s
Mostlinkedcategories           [QueryPage] cheap, skipped
Mostlinkedtemplates            [QueryPage] got 1000 rows in 9.41s
Mostlinked                     [QueryPage] got 1000 rows in 1m 2.65s
Mostrevisions                  [QueryPage] got 1000 rows in 4m 7.13s
Fewestrevisions                [QueryPage] got 1000 rows in 3m 48.61s
Shortpages                     [QueryPage] cheap, skipped
Uncategorizedcategories        [QueryPage] got 1000 rows in 1.80s
Uncategorizedpages             [QueryPage] got 1000 rows in 0.22s
Uncategorizedimages            [QueryPage] got 158 rows in 0.02s
Uncategorizedtemplates         [QueryPage] got 272 rows in 0.10s
Unusedcategories               [QueryPage] got 1000 rows in 0.21s
Unusedimages                   [QueryPage] got 99 rows in 0.10s
Wantedcategories               [QueryPage] got 262 rows in 0.08s
Wantedfiles                    [QueryPage] got 748 rows in 0.30s
Wantedpages                    [QueryPage] got 1000 rows in 20.44s
Wantedtemplates                [QueryPage] got 1000 rows in 0.50s
Unwatchedpages                 [QueryPage] got 1000 rows in 0.28s
Unusedtemplates                [QueryPage] got 258 rows in 0.11s
Withoutinterwiki               [QueryPage] got 1000 rows in 0.24s
GadgetUsage                    [QueryPage] got 22 rows in 1.28s

real    11m17.180s
user    0m0.448s
sys     0m0.400s
Nike (talk)09:47, 10 September 2018

Query done.

Nike (talk)14:05, 10 September 2018

Ok, thanks Nike. I now need only list of pages with translations which exists for Bosnian but no for sr-ec. Thanks!

Zoranzoki21 (talk)10:18, 11 September 2018

Translate bug: Misidentifies which version of /en message is the latest

The translation interface is misidentifying which version of an /en message is the latest.

The original message MediaWiki:Interfaceadmin-info/en was changed, as follows:

Translate bug 1.png

The change was presented by the translation interface, and the /pt translation was updated accordingly, as follows:

Translate bug 2.png

Now, after this update, the translation interface seems to be misidentifying which version of the /en message is the latest, compares the new /pt translation to the old /en message, identifies three errors in the new /pt translation and requests translation back to the original version of the /en message:

Translate bug 3.png

I have purged the translation statistics page, and the problem continues.

Do you want to verify first if this is due to something local, or should it be reported in Phabricator?

Hamilton Abreu (talk)09:01, 2 September 2018

Here's something even funnier about this.

This single message is listed as belonging to two groups: "MediaWiki core" and the extension "Wikimedia Overrides":

Translate bug 4.png

It's the same message being listed in both groups.

That in itself is probably incorrect, right? No message can belong to core and to an extension, I believe.

Now, the situation reported above was for the first time the message is listed, under the first group, "MediaWiki core". If we go to the second time it is listed, under the group "Wikimedia Overrides", this is shown:

Translate bug 5.png

So, here, the /en content shown that is to be translated is the correct one: the new version of the /en message. This is the correct text.

But, the three errors reported are the same as previously: those that result from a comparison with the old /en message instead of the new /en message that is being presented.

Hamilton Abreu (talk)12:17, 2 September 2018

The other one is now prefixed with 'wmf-' and this should be resolved.

Nike (talk)07:21, 3 September 2018

Can you please re-check? The situation as I see it is still exactly as reported.

There are indeed three messages starting with 'wmf-' in three languages but none of them is English.

Hamilton Abreu (talk)13:09, 4 September 2018

Sorry I was too hasty. It should really be fixed now.

Nike (talk)07:21, 7 September 2018

Sorry to report that the situation we have now is:

  1. For the original messages with name MediaWiki:Interfaceadmin-info/XX, the old, outdated, revision of MediaWiki:Interfaceadmin-info/en is being presented for translation instead of the latest revision. This remains as reported initially, and that is wrong.
  2. Five new messages have been imported with the name MediaWiki:Wmf-interfaceadmin-info/XX. These should probably be deleted.
  3. Several new messages have been imported with the name MediaWiki:Wikimedia-interfaceadmin-info/XX. As far as I can see, these have been appropriately fuzzied and should all be correct.
Hamilton Abreu (talk)18:49, 7 September 2018

A bug on discussion pages

There is a bug on discussion pages that doesn't allow more than 10 responses to be shown.

Rancher (talk)19:03, 26 August 2018

Can you provide more details, like steps to reproduce?

Nike (talk)07:58, 27 August 2018

Take a look at here. When I click on "Show 6 replies", it loads just fine. Then another button "Show 1 reply" pops up, which kinda refreshes the section and doesn't do what it needs to. The only way to see it is in page history of the entire user talk.

Rancher (talk)12:39, 27 August 2018

Were you able to reproduce it?

Rancher (talk)20:01, 5 September 2018

Yes I can reproduce it :(

Nike (talk)15:32, 10 September 2018

What is the result of GENDER in case of plurality ?

The following message:

{{PLURAL:$1|L’{{GENDER:$2|utilisateur|utilisatrice}} a|$1 utilisateurs ont}} été {{PLURAL:$1|supprimé|supprimés}}.

is NOK because 'supprimé' must be declined according to gender (at least) and number (at best).

Then what is the resulting GENDER in the 3 cases of plurality: several males, females, or mixed society ?

ChristianW (talk)06:45, 6 September 2018

The GENDER magic word is only available for individual users. Is it possible in French to write a gender neutral translation in plural? In Italian we would write "soppressi/e".

Nemo (talk)15:15, 6 September 2018

Hi Fredo , As I drafted, in french we expect 4 different combinations of the magic words :

L'utilisateur a été supprimé. (one male person)
L'utilisatrice a été supprimée. (one female person)
Les utilisateurs ont été supprimés. (two or more male only users)
Les utilisatrices ont été supprimées. (two or more female only users)

Les utilisateurs ont été supprimés. (mixed set of males(one or more) AND females(one or more) ) but this is the same as 3rd case.

So the current grammar sucks for:

L'utilisatrice a été supprimé. (one female person) -> missing 'e'
Les utilisatrices ont été supprimés. (two or more female only users)-> missing'e'
ChristianW (talk)09:10, 7 September 2018

Not a fix for the feminine plural, but the first issue in this post ("L'utilisatrice a été supprimé. (one female person) -> missing 'e'") is solved like this:

{{PLURAL:$1|L’{{GENDER:$2|utilisateur|utilisatrice}} a|$1 utilisateurs ont}} été {{PLURAL:$1|{{GENDER:$2|supprimé|supprimée}}|supprimés}}.
Jon Harald Søby (talk)21:41, 8 September 2018

Yes, but this post concerns plural.

ChristianW (talk)06:20, 9 September 2018

Yup, I know, I just wanted to point out that it's really just one of those cases that is problematic, and not two as you said in the post. :-)

Jon Harald Søby (talk)23:41, 9 September 2018

Add language to translate

Eastern Pwo Karen language to translate to English.

Rul1902 (talk)00:00, 28 August 2018

Needs more informations to verify:

  • language code: kjp
  • language name: Eastern Pwo (in English, is this right?) – (what's the autonym?)
  • writting in LTR or RTL?
  • which script(s) are using in this language?
  • fallback to which language(s), or just translate from English?
Liuxinyu970226 (talk)22:45, 28 August 2018

Basic information:

  • language code: kjp
  • language name: Eastern Pwo Karen or Pwo Eastern Karen
  • self-name: ဖၠုံလိက်
  • Script: Mon, Myanmar
  • Direction: LTR
  • Fallback to: Myanmar (my)
Rul1902 (talk)10:18, 29 August 2018

Is there perhaps any other source for the name "ဖၠုံလိက်"? I cannot find it anywhere else online.

Amir E. Aharoni (talk)11:19, 1 September 2018

"လိက်" = Language. In Microsoft windows 10, there is a language name for Eastern Pwo Karen, displaying as "ဖၠုံ".

NinjaStrikers «»14:20, 1 September 2018


Amir E. Aharoni (talk)07:29, 2 September 2018


Rul1902 (talk)13:07, 10 September 2018

about localized upper/lower cases in common words

Hi all, Last flow of messages to translate is mainly oriented to transform low case into uppercase caracters. Ex: "Add observations to this project" becomes "Add Observations to This Project". In some languages only the beginning letter is possibly in uppercase and apart of proper nouns, no uppercase can be found within the string. In that perspective, the translation brings nothing more than the previous existing translated version. So what is expected from translators ? Do we follow the case flow of the english text ? or remain coherent in our language ? Thanks.

ChristianW (talk)08:56, 7 September 2018

What project was that done for? Those changes to the English text should probably be reverted. It is Really Bad to Use Title Case for Things that Aren't Actual Titles, even in English. You should definitely follow the rules for your language.

Jon Harald Søby (talk)21:36, 8 September 2018

I agree with you. My example comes from iNaturalist:Add observations project/fr so project is "iNaturalist:" and there is a bulk of such messages where nouns have been prettified. I started to keep messages as before in FR as long as only uppercase was concerned, and stopped to translate when posting this subject. I dont know if there is a filter and how the adequation "message to be translated" is evaluated but I realised we were losing energy with such cases. More of that I have thought about German language in which the upper case for common nouns is a rule: ... they will see no difference.

ChristianW (talk)06:34, 9 September 2018

Yeah, that's basically just a stupid decision on their part, but I don't have any involvement in that project, so I don't want to try and change that, but just stick to the rules of your language. If your language doesn't normally do that (few languages do in my experience), don't use Those Annoying Capitals, it will just look silly (and possibly even unprofessional). If I see something written like that in Norwegian, I automatically think that it's autotranslated garbage, or that the person who wrote it barely even passed primary school, since they obviously don't know how to write Norwegian properly.

Jon Harald Søby (talk)23:36, 9 September 2018

I agree, but as it's not a rule of english language, it's either a mistake of iNaturalist developers, or a particular will independantly of grammatical rules. So if we think it has no sense, the english messages must first be modified, and then the translations will follow. Otherwise, why this change in english only?

Gomoko (talk)07:50, 10 September 2018

wrong doc message MediaWiki:Deletebatch-system-username

MediaWiki:Deletebatch-system-username "Delete page script"
Name of the system user account which can be used by privileged users (those who have the deletebatch-spoof user right) to delete pages. See also Right-deletebatch-spoof (« Pages supprimées par lots en tant que "suppression de page par script" »).
Message is speaking of script, documentation is speaking of system user account.

ChristianW (talk)06:57, 9 September 2018

I don't think this is a mistake. The extension uses a special account name (i.e. a system user account) to run a script. The account's name is "Delete page script".

Jon Harald Søby (talk)23:44, 9 September 2018

Montenegrin language

Please turn on Montenegrin language so it is available, since an official code has already been obtained (ISO 639-3). Thank you for your consideration. Best regards.

Freemanmne (talk)19:02, 24 January 2018
Edited by author.
Last edit: 02:36, 28 January 2018

Like such requests before:

  1. Language code: cnr (ISO 639-2/3);
  2. Language name: Montenegrin – Crnogorski;
  3. Writing direction: LTR;
  4. Script: Latin;
  5. Fallback: Bosnian (bs), see discussions below.
Liuxinyu970226 (talk)04:41, 25 January 2018

@Freemanmne and Ookuninusi: Can you two please answer the last two questions above?

Liuxinyu970226 (talk)08:46, 27 January 2018

We want in Latin!

Ookuninusi (talk)12:57, 27 January 2018

And how about fallback?

Liuxinyu970226 (talk)13:04, 27 January 2018

Can you explain to me a bit about the backup. I do not understand so much in the translate wiki technique :)

Ookuninusi (talk)13:31, 27 January 2018

This is done.

Amir E. Aharoni (talk)12:05, 6 September 2018

Reread impossible : no response from translatewiki when trying to review translations from other users

Hi all, on translatewiki, message "Chargement des messages… " is stuck in an infinite loop with the turning circle and without giving hand back with the list of possible messages to reread (... may be there are none). I must abort the page. Translations are possible from the home page of translatewiki in the normal way, leading to 'Reread' button when there are no more translations (this is ok). This wait was not observed before (... may be because there were always messages left to reread).

Similar situation on mediawiki.

Created task:

ChristianW (talk)07:08, 4 September 2018

The preservation of the :w:en:Wikipedia links in MediaWiki:Tag-AWB/en and MediaWiki:Tag-AWB-description/en should not be being checked in the translations, as this prevents localisation. Can the check be removed, please?

Hamilton Abreu (talk)10:34, 2 September 2018

The only way to do that, is to convert both links to external links, which is what I proposed at phab:T186454

Liuxinyu970226 (talk)11:05, 2 September 2018

It's not the only way, we also have overrides to disable checks.

Nike (talk)07:22, 3 September 2018

{{LanguageHeader|ISO 639-3}} request for Sylheti language & keyboard on translatewiki

please intruduce "Sylheti language & keyboard" on translatewiki so we can contribute in our mother tongue. many people face problem to translate in this language lack of sylheti keyboard. so install our keyboard & language layout in this project.

এম আবু সাঈদ (talk)07:08, 7 April 2016

New input methods can be requested for jquery.ime at GitHub: we do not develop input methods here:

Nike (talk)09:19, 25 August 2016

There is not enough information to add this language. Please provide all information requested at

Siebrand12:15, 20 May 2017
Nemo (talk)12:34, 20 May 2017

Hello, for your request can you confirm the information above is correct?

Nemo (talk)06:38, 29 August 2018

I want translate to Shesi kham language. I can't find the link. Please help me.राम प्रसाद जोशी (talk) 08:29, 14 July 2017 (UTC)

Edited by author.
Last edit: 11:48, 15 July 2017


  1. Code: kip
  2. Language names: Shesi kham – शेषी पाङ
  3. LTR
  4. Writing system: Devanagari
  5. fallback language: Nepali (ne)
Liuxinyu970226 (talk)12:26, 14 July 2017

Here is no items for translate. Please help me.

This language is recently enabled, sorry that Amire hasn't announced. You can now translate messages to this language now.

Liuxinyu970226 (talk)22:55, 28 August 2018

Request for bot for user Zoranzoki21

Edited by 3 users.
Last edit: 22:40, 28 August 2018

Please open Zoranzoki21-Bot account, for my bot and give him bot flag and offline translator right too. I need a bot so that I do not hit the limit every time when I work equalization of the translations of Serbian Cyrilic and Serbian Latin. Too give him translation admin so I can use Special:ImportTranslations and Special:ExportTranslations and remove me offline translator from main account. You can send me password for account with option send email to user of my user account. If you have more questions, you can ask me. Thanks!

Zoranzoki21 (talk)21:59, 26 August 2018

Support. Serbian Cyrillic and Serbian Latin translations are very unequal, so this is crucial for equalizing the translation in that language.

BadDog (talk)20:46, 27 August 2018

Things which will bot work:

  1. Bot will work on equalization of the translations of Serbian Cyrilic and Serbian Latin
  2. Massive translation changes for the Serbian language with agreement of other translators

... and other things for bots per request

Zoranzoki21 (talk)20:56, 27 August 2018

I finally opened account for bot. Give him bot flag and offline translator. Then you can remove me offline translator right. Thanks!

Zoranzoki21 (talk)19:38, 28 August 2018

Resolved by Metalhead64

Zoranzoki21 (talk)20:06, 28 August 2018

Deleting pages

Can someone delete pages MediaWiki:Gadget-blockuser/sr-ec and MediaWiki:Gadget-renameuser/sr-ec. These and simular pages should be created on local wiki, not on translatewiki.

BadDog (talk)15:06, 26 August 2018

By common practice we do not delete unused translations.

Nike (talk)07:59, 27 August 2018

Okay, anyway, thanks for speedy response.

BadDog (talk)16:06, 27 August 2018

Translate is losing translations

There's something odd going on with submission of translations, at least for our locale (gd). I have been working to catch up with the new filters strings and while some of them go through to live ok, some just keep disappearing. For example MediaWiki:Ores-rcfilters-goodfaith-good-desc/gd I have translated at least twice over the last 2-3 days (I'm working through the strings visible in the UI top to bottom so I know which ones I did) and yet this morning it's still showing in English in the UI and when I go to the string in the Translation tool, the target is empty. I am 100% I Saved the translations correctly and there were no error messages.

This one is equally weird, I had to translate it at least twice MediaWiki:Rcfilters-watchlist-showupdated/gd and while the translation is in the system, it did not hit live along with the others (and I did it around the same time). Something is weird.

Akerbeltz (talk)10:31, 20 July 2018

I see no evidence that the translation ever got through in the first place. More information when this happens is required to investigate this task.

Nike (talk)08:04, 1 August 2018

It has been over a month without further details, so I am closing this task. We can check again if further details are given.

Nike (talk)08:06, 27 August 2018

I've had what I think is a similar issue in the past, usually when my connection is bad. You click save, go to the next one, but it doesn't save. However, it is pretty visible that it doesn't go through, because the background color on the message is different from the ones that are saved. Are you sure that's not what's happening, Akerbeltz?

Jon Harald Søby (talk)21:31, 7 August 2018


When will be next deployment? For example, Wikimedia:Xtools-latest-action/sr-ec (from June 24, 2018 and still not applied).

Obsuser (talk)17:46, 14 July 2018

@MusikAnimal: that's your tool, so only you can answer us.

Liuxinyu970226 (talk)23:40, 17 July 2018

@Liuxinyu970226: Sorry but it seems you've posted the answer in the wrong section.

Obsuser (talk)19:16, 23 July 2018

He didn't actually, MusikAnimal is the maintainer of those tools, so he should be able to give a reply.

Jon Harald Søby (talk)21:34, 7 August 2018

Hey y'all, not sure why I didn't get your pings. I don't see anything in my notifications, and I have "mentions" turned on in my preferences.

Anyway, it looks like the translation in question was pushed to the repository two days ago. I hopefully will be doing a deploy either tonight or tomorrow. Sorry for the wait!

MusikAnimal talk22:27, 7 August 2018

Unfortunately, Liquid Threads do not support pings I believe.

Nike (talk)08:05, 27 August 2018

Sorry, the translation was indeed added June 25.

It is showing up on my end. See this example. "Последња забележена радња" is shown towards the top in the left column.

Are you not seeing it?

MusikAnimal talk22:34, 7 August 2018

push issues


We would like to have TranslateWiki not to push in our master branch but in different one. Is this possible?

In addition, are you using forced push in any of your push actions?


Haniavis (talk)10:53, 8 August 2018

Why not use master? What process will you use to ensure continuous localisation (for instance, how are you going to update source messages and bring translations to master)?

Nemo (talk)11:03, 8 August 2018

Because we use master for our automatic update of our deployments. And when you push to master, our users see that there is an update which they pull, but never understand what was that.

We need to handle this pushing of translations to master, we will manually merge your new branch with master when there is translations.

Haniavis (talk)16:37, 23 August 2018

Experience shows that doing merges manually adds work for developers and translators while lowering the quality of both code and translations. Deploying translations immediately is good. What is the concrete problem you see?

Nemo (talk)16:52, 23 August 2018

We never use forced push. We can export to a different branch from which we read from, but that means it is you must deal with merge conflicts. In our experience that often doesn't work (translation updates not getting applied in a timely manner), so that's why we recommend against it.

Nike (talk)08:01, 27 August 2018

How to change site name?

How do I change the site name from "Wikipedie" to "Wikipedia" on the nds-nl wiki? Can anyone tell where to go and what the steps are?

Servien (talk)12:15, 26 August 2018

It's a configuration change, so see m:Requesting_wiki_configuration_changes. Normally the name, subtitle and other things listed in m:User:Cbrown1023/Logos should be changed only with an extremely solid consensus, because they're supposed to be very stable. So, make sure to have a local discussion and involve all current and past users and translators.

Nemo (talk)12:20, 26 August 2018

Deleting page with invalid language code

Can someone delete page MediaWiki:Multimediaviewer-credit-fallback/dr-ec because its language code is mistaken. Correct page already exist at MediaWiki:Multimediaviewer-credit-fallback/sr-ec.

BadDog (talk)15:54, 15 August 2018

Done Done

\m/etalhead 18:55, 15 August 2018

@Metalhead64: thanks.

BadDog (talk)19:27, 15 August 2018
First page
First page
Last page
Last page