Jump to: navigation, 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.


Thread titleRepliesLast modified
Improvements for Serbian language309:51, 21 May 2017
Questionable translations021:50, 20 May 2017
Language coordinator617:11, 20 May 2017
Talysh Wikipedia Project's Name017:04, 20 May 2017
Talysh language017:02, 20 May 2017
RFC: Personal goals916:51, 20 May 2017
Yandex for bengali216:33, 20 May 2017
Wrong Links 115:57, 20 May 2017
Filter by message key substring in Special:Translate115:48, 20 May 2017
Translating WMDE's attribution generator615:42, 20 May 2017
CirrusSearch insource: not working115:41, 20 May 2017
PSA: Space as the first thing in PLURAL output does not work015:40, 20 May 2017
PLURAL/GENDER215:39, 20 May 2017
About "Meta message group"...215:37, 20 May 2017
Rename115:32, 20 May 2017
Translations:Group descriptions/visualeditor/en115:28, 20 May 2017
Please open Blockly item for Chinese translation 015:20, 20 May 2017
MediaWiki:Apihelp-query+templates-param-namespace/en014:16, 20 May 2017
MediaWiki:Apihelp-query+search-param-enablerewrites/en014:16, 20 May 2017
Notification014:08, 20 May 2017
First page
First page
Last page
Last page

Improvements for Serbian language

I have a few questions.

  1. Bot for "sr-el": Is it possible that someone creates bot that will copy all pages suffixed "/sr-ec" to "/sr-el" (only if "/sr-el" does not already exist or exists but is different from Cyrillic counterpart when transliterated to Latin) so that newly created pages are same as "/sr-ec" ones but transliterated to Latin script? This tool,, is good and might be useful for taking script or some sort of mediate usage. This would improve largely percent statistics as main translation tool creates pages suffixed "/sr-ec" i.e. only for Cyrillic script.
  2. Change "sr" to "sr-ec" in interface so link lead to proper places: Where to change "sr" into "sr-ec" that makes on the left menu link titled "Translation" ("Превођење"), right below logo, because now it gives no result because localization is being done in "sr-ec" and not "sr" ("Language code" field)?
  3. Main Page of Translate Wiki: This is also problem on Main Page, where statistics are 0 for some reason — maybe because "sr" is used instead of "sr-ec". Also, how convert "9.6k" into "9,6k" (comma is for Serbian) and make "поруке за превођење" displays in two lines (I tried with br but it does not expand into newline but displays as such; right now [2017/5/10 18:33] it is with newline in message, but it might not work either). Bottom "Powered by" should be made translatable.
  4. Mobile sr.wikipedia logo: Someone should implement translated image commons:File:Wikipedia wordmark sr.svg to

Also, is it possible to remove two "српски" messages in menus and elsewhere and leave only one i.e. make them different (for example, "српски / srpski" for "sr", "српски" for "sr-ec" and "srpski" for "sr-el"). It is very confusing to have two same "српски" messages... This problem is also present when choosing language on Wikimedia Commons etc. --Obsuser (talk) 16:46, 10 May 2017 (UTC)

11:32, 6 May 2017
Edited by another user.
Last edit: 13:54, 20 May 2017

1) Yes it is possible, but I don't have time for it.

4) This should be reported to We do not handle logo changes here.

For 2 and 3 I need to investigate more.

12:05, 20 May 2017

OK, can you also change dot to comma as default separator for Serbian (especially on TW Main Page; here it is comma for Croatian and Bosnian, should be for Serbian too; maybe MediaWiki:Twnmp-stats-number-k/sr-ec and sr-el should be deleted, as those two languages have not created these pages).

Also, why there are two toolbars shown when editing this thread (at least for me)?

17:03, 20 May 2017

I reported for the first issue.

The two toolbars has started happening recently.

09:51, 21 May 2017

Questionable translations

A thread, Thread:Support/Questionable translations, was moved from here to Portal talk:Ro. This move was made by Liuxinyu970226 (talk | contribs) on 20 May 2017 at 21:50.

Language coordinator

I talked with a friend who is a member of KDE Serbian translation team about what should be done if two or more users do not agree about translation, terminology or other language issues. He told me the following, and I quote:

"As people are aware that in practice the translation is a very subjective thing, then it is determined who is in charge of that language (the person is often called "coordinator"), and what the coordinator says, that's final. It is very important that the coordinator has technical means in order to be his last. If there is someone new and do not agree about some issues, and do not convince the coordinator what they want, they can leave; if they just start to work beside the warnings, then the chief will prevent that using his/her technical means.

As to who is in charge of a translation unit, in voluntary undertakings it's the one who first came on the project *AND* work on a regular basis. The coordinator can be changed only if he leaves the project or stops to work regularly. There is no other way — for example, referring to any writings, even if they are from God itself, do not pass."

This method is used in many open source projects, including Gnome, KDE, Debian, Fedora, Mandriva etc. Something similar could be applied here. What do you think?

12:16, 17 August 2012

I'm fine if some language communities want to have a benevolent dictator who is be able to have the final say, if that reduces conflicts. I would limit it to that, however. What I don't want is any kind of gate keeper role like the coordinators usually are in above mentioned projects.

10:45, 19 August 2012

I think it would be much better to strive for a consensus model, if possible. Precisely because translation is subjective, I don't think it is a good idea to give one person the absolute power to impose his/her personal preferences -- especially if this power is not based on translation quality but simply given to whomever got there first and/or produces the most. That way, one person could easily ruin an entire project language.

11:45, 19 August 2012

I have the exact opposite problem. A user came into the project, ignoring the translation practice in Serbian language, and started fuzzing around with the translations. This message is a response to his use of noun forms for button messages, which is totally wrong. Of course, he didn't consider my suggestions, and he kept reverting my edits, stating that "It is inappropriate to revert my edit or initial translation without a discussion". For such a basic thing a discussion or consensus is not necessary at all.

23:04, 5 September 2012

Well, this is a discussion. Niklas gave his suggestion, is it impossible to follow it? If that's a basic thing perhaps it won't be too hard to get it added to your language's guidelines with a brief discussion on portal talk.

07:24, 6 September 2012

I already posted the guidelines on the portal page of Serbian language, but it seems nobody care for it. Though, I am the only active Serbian translator on this site. Other users periodically come here to translate a few messages (often on translation rallies, like the already mentioned user I had problems with, which proves an obvious thing).

15:45, 8 September 2012

We try to cover some of these desires (from our own point of view) at mw:Internationalisation_wishlist_2017#Motivation_and_understanding. Some reasonable pieces are still missing.

17:11, 20 May 2017

Talysh Wikipedia Project's Name

A thread, Thread:Support/Talysh Wikipedia Project's Name, was moved from here to Portal talk:Tly. This move was made by Nemo bis (talk | contribs) on 20 May 2017 at 17:04.

Talysh language

A thread, Thread:Support/Talysh language, was moved from here to Portal talk:Tly. This move was made by Nemo bis (talk | contribs) on 20 May 2017 at 17:02.

RFC: Personal goals

Just an idea: let users to set personal goal for how many edits they want to do per month (with some granularity like 5, 10, 15, 20, 25, 50, 100). If that goal has been met in every consecutive month for, say, six months, they would get some praise, like for example a mention in our newsletter.

The purpose of course is to get them contribute regularly, even in the expense of huge one time contributions. What do you think?

09:12, 16 August 2011

I don't think that setting a personal goal would be useful for myself. Is it possible to ask translators to say whether they would find this useful or not?

The idea itself seems quite interesting, but as we have just been reminded by Irshgrl500 our help pages still needs work. Maybe we should be concentrating on improving these first?

07:56, 21 August 2011
Edited by another user.
Last edit: 09:22, 4 September 2011

The problem is that the goat is guarding the cabbage patch. There doesn't seem to be any good user centric documentation writers among us.

We need lots of new ideas, and then we can implement the best ones we can actually do.

08:48, 21 August 2011

Fair points.

09:25, 21 August 2011

I don't see how improving documentation is in contrast with this proposal.

The problem is certainly worth an effort (do I need to explain why?) and the idea is nice, especially if users were sent reminders of their goals and what they need to achieve them. Many users are not accustomed to goal-setting and they wouldn't even start to use the feature, so I'd suggest to set goals automatically (based on past activity and what we think is most sensible), with the possibility to change them; users would be notified of the feature and asked to confirm the goal or change it, but if they don't they won't receive email reminders; the automatically-chosen goal should stay as a recommendation (Nike, you might remember this). The suggestion on TWN end makes it slightly more similar to a barnstar-giving and how praise works in general, so it helps to introduce the user to the system. Finally, I suggest to create more understandable and interesting goals, like translating a small extension (small goal) or all MediaWiki "core" messages of some language (100 a month for 5 months, quite big goal), providing a list of such extensions or languages or whatever (in random order or with some order of importance if we have one).

09:54, 4 September 2011

Is it worth reviving this thread?

21:07, 4 December 2012

It's something worth considering some day, I think. I guess the Translation UX would be the only concrete occasion in the foreseeable future, but even after that it's nice to track such proposals; move back to unconfirmed maybe?

21:27, 4 December 2012

I guess we could look into AchievementsII by Wikia. Not sure if these are the docs: It's not impossible that this extensions requires a whole heap of other social and profile related extensions, in which case we probably won't be able to use it.

21:37, 4 December 2012

While I do not mind that this may be useful for some contributors, and it may be helpful for estimative planning of server ressources, and similar, it is not for me. I most often cannot forsee the amount of time available to me. It may be next to nothing for weeks and months, and may jump to several consecutive hours unexpectedly, when for example I am "suffering" from a travel delay while having internet access and nothing more important to do. This may not be typical, however. :-)

12:55, 27 December 2012

Yandex for bengali

Is it possible to enable Yandex Translate suggestion for bengali (bn) in this wiki?

13:15, 14 September 2016

In theory all supported pairs should automatically be used and I see bn in and .

However I can't see whether $wgTranslateTranslationServices['Yandex']['pairs'] is customised on this wiki.

18:45, 19 September 2016

Yandex is also currently disabled due to some prolonged temporary errors.

16:33, 20 May 2017

Wrong Links

15:30, 7 December 2016

From what I can tell, they are correct at the moment.

15:56, 20 May 2017

Filter by message key substring in Special:Translate

I'm interested in all messages with keys like 'Templatedata-doc-param-type-*'.

While the filter in Special:Translate apparently can only filter by text.

Filtering by message group is not sufficient because it only brings me as far as 'TemplateData-*'.

I tried Special:PrefixIndex, too, but it gives messages for all languages while I'm only interested in one. And it limits the number of results that it gives, too.

17:05, 30 May 2016

This is a nice feature request. We should report this in Phabricator and then Niklas could probably get it done!

15:48, 20 May 2017

Translating WMDE's attribution generator

Hi everyone,

at Wikimedia Deutschland, we have recently launched the "Lizenzhinweisgenerator" (German for "Attribution Generator"). It helps to create correct attributions for Wikipedia and Wikimedia Commons pictures. At the moment, it's only available in German. We will provide an English version soon, but there are further request(s) from the Wikimedia Communities to translate it to other languages. I thought Translatewiki would be the environment to do so. The text files to be translate are on Github, most of them html, one is a json file.

Now my questions are: Generally, is Translatewiki suited to translate the files? Is it easy to export the files back from here to Github/our webspace? What needs to be done from my (our) side? Could someone support me with that?

Best and cheers,

10:00, 25 May 2016

At the moment we do not support HTML files.

To be enabled on you have to fill the usual requirements such as ensuring that provided translations will be used and reach users in timely manner and providing message documentation for contextual information.

10:48, 25 May 2016

That's a pity, as 4 of the 5 file are html files. Any workaround for that?

We fulfil the usual requirements, as it is in our highest interest to have the tool translate. Message documentation for contextual information will be provided, of course.

11:13, 25 May 2016

Can't you convert them to a set of .json files (or if you don't like json)?

11:27, 25 May 2016

Well, the idea of all this was to make the re-import as easy as possible.

11:40, 25 May 2016

There are tools that can be integrated in the build process to extract Gettet pot files (maybe json as well, I haven't researched) and rebuild the translated html files.

One idea is to forgo having the html files as primary format and use some templating system or static file generator system to generate the html files from the json files. Something like this would be easy to write for a programmer as well.

Alternatively you could write a FileFormatSupport class for your HTML format, but I am afraid it wouldn't be very re-usable and would have maintenance costs.

14:19, 27 May 2016

Cornelius, did you find some library suitable for your needs to load the (translated) text from files?

15:42, 20 May 2017

CirrusSearch insource: not working

I tried to search for insource:Project:Copyright, and got the following error:

[10055add3fc7981b9afb68ee] /w/i.php?search=insource%3A%22Project%3ACopyrights%22&title=Special%3ASearch&fulltext=1 RuntimeException from line 398 of /srv/mediawiki/tags/2016-08-23_08:15:51/extensions/CirrusSearch/includes/Search/ResultsType.php: regex is only supported with $wgCirrusSearchUseExperimentalHighlighter = true
#0 /srv/mediawiki/tags/2016-08-23_08:15:51/extensions/CirrusSearch/includes/Search/SearchContext.php(430): CirrusSearch\Search\FullTextResultsType->getHighlightingConfiguration(array)
#1 /srv/mediawiki/tags/2016-08-23_08:15:51/extensions/CirrusSearch/includes/Searcher.php(576): CirrusSearch\Search\SearchContext->getHighlight(CirrusSearch\Search\FullTextResultsType)
#2 /srv/mediawiki/tags/2016-08-23_08:15:51/extensions/CirrusSearch/includes/Searcher.php(352): CirrusSearch\Searcher->search(string)
#3 /srv/mediawiki/tags/2016-08-23_08:15:51/extensions/CirrusSearch/includes/CirrusSearch.php(406): CirrusSearch\Searcher->searchText(string, boolean)
#4 /srv/mediawiki/tags/2016-08-23_08:15:51/extensions/CirrusSearch/includes/CirrusSearch.php(150): CirrusSearch->searchTextReal(string, NULL)
#5 /srv/mediawiki/tags/2016-08-23_08:15:51/includes/specials/SpecialSearch.php(298): CirrusSearch->searchText(string)
#6 /srv/mediawiki/tags/2016-08-23_08:15:51/includes/specials/SpecialSearch.php(150): SpecialSearch->showResults(string)
#7 /srv/mediawiki/tags/2016-08-23_08:15:51/includes/specialpage/SpecialPage.php(522): SpecialSearch->execute(NULL)
#8 /srv/mediawiki/tags/2016-08-23_08:15:51/includes/specialpage/SpecialPageFactory.php(583): SpecialPage->run(NULL)
#9 /srv/mediawiki/tags/2016-08-23_08:15:51/includes/MediaWiki.php(283): SpecialPageFactory::executePath(Title, RequestContext)
#10 /srv/mediawiki/tags/2016-08-23_08:15:51/includes/MediaWiki.php(749): MediaWiki->performRequest()
#11 /srv/mediawiki/tags/2016-08-23_08:15:51/includes/MediaWiki.php(521): MediaWiki->main()
#12 /srv/mediawiki/tags/2016-08-23_08:15:51/index.php(43): MediaWiki->run()
#13 {main}

The problems are:

  1. The error message isn’t right (it tells regex isn’t supported, altough I searched for a simple text in the source code (I don’t know wheter the error message is right that you should enable $wgCirrusSearchUseExperimentalHighlighter for normal insource search).
  2. Why have I got this whole error message? (I.e. in Wikimedia wikis I get a nice error page, and the details, including file paths, are hidden from the Internet.)
  3. And last, but not least: why doesn’t this work?
17:07, 24 August 2016

This no longer happens.

15:41, 20 May 2017

PSA: Space as the first thing in PLURAL output does not work

A thread, Thread:Support/PSA: Space as the first thing in PLURAL output does not work, was moved from here to Translating talk:MediaWiki. This move was made by Nemo bis (talk | contribs) on 20 May 2017 at 15:40.


If your language does not need the PLURAL function at all, then explain this on the Support page. You may be able to get the check software to ignore missing PLURALs in your language.

(same for GENDER, from FAQ)

Korean does not need PLURAL/GENDER in the language (Singular and plural all have same following words, no per-gender words). So is it possible to ignore nonexisting PLURAL & GENDER instead of a workaround? (Or if it is not possible then please remove this line?)


11:02, 24 September 2015

We already ignore the plural checks for Korean in groups/check-blacklist.php, while we don't seem to have a specific checker for GENDER.

15:34, 20 May 2017

Can we ignore the GENDER checks too? We're currently working around by just wrapping it, but it's really annoying to just see fuzzy when GENDER is the only addition or such.


15:39, 20 May 2017

About "Meta message group"...

Hi everyone,

About "meta message group" in messages such as:

Can someone please clarify whether "meta group" in these messages means a group of groups, or instead is a reference to MetaWiki? In other words, should it be translated as "meta group of messages" or as "group of messages for MetaWiki"?

12:00, 24 October 2016

"meta group of messages"

21:16, 25 October 2016

Meta message group and aggregate message group are the same in this context. It's a group that consists of multiple message groups.

15:36, 20 May 2017

Hello, can someone rename me to SimmeD instead?

12:24, 11 April 2017

Done Done

15:32, 20 May 2017

Hello.Please replace "[ visualeditor]" with "[[mw:Special:MyLanguage/Extension:visualeditor|visualeditor]]".Thank you

14:06, 12 December 2016

Done Done

15:28, 20 May 2017

Please open Blockly item for Chinese translation

A thread, Thread:Support/Please open Blockly item for Chinese translation, was moved from here to Translating talk:Blockly. This move was made by Nemo bis (talk | contribs) on 20 May 2017 at 15:20.


A thread, Thread:Support/Notification, was moved from here to Translating talk:MediaWiki. This move was made by Nemo bis (talk | contribs) on 20 May 2017 at 14:08.
First page
First page
Last page
Last page