View source for Support

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
Support Saraiki language310:04, 16 October 2017
Wikimedia:Xtools-edits/sr001:53, 16 October 2017
CSRF token issue301:52, 16 October 2017
Wikimedia:Xtools-edits/sr001:54, 16 October 2017
LibreRouter: new project with software and HowTo booklets714:29, 15 October 2017
how to translate an article into wikipedia?104:18, 14 October 2017
The last untranslated message is missing505:36, 13 October 2017
Translating *from* Italian *to* English220:14, 6 October 2017
Language selector does not worked305:37, 13 October 2017
Making Template:Doc-apihelp-param translatable003:50, 4 October 2017
Support for Kumyk521:30, 3 October 2017
How can the language name be changed?110:37, 3 October 2017
Why are translations in the Gothic wiki not correctly imported?1007:59, 30 September 2017
All local MediaWiki messages of Gothic need to be removed012:38, 30 September 2017
Please enable Tunica for translation917:08, 28 September 2017
Filter out API messages?207:54, 28 September 2017
Mistakes in edit protected pages: choosen instead of chosen008:43, 28 September 2017
Support for Guianese Creole French1320:51, 19 September 2017
Lost edit summaries621:04, 17 September 2017
Talk page preview on message pages creates "Changes you made may not be saved" window in browsers010:12, 16 September 2017
First page
First page
Previous page
Previous page
Last page
Last page

Support Saraiki language

Edited by author.
Last edit: 10:04, 16 October 2017

Language Saraiki is mainly written in Arabic script. So Skr and Skr-arab be merged. In wikimedia and other sites Skr-arab be deleted. Because Saraiki is just one language. In interface language and internationalization only one langauge be shown. Interface of Urdu words be adjusted as they are adjusted in SKR_Arab. All translations be converted to Skr i.e., Skr-arab be renamed as skr. so that one language Skr-arab be deleted from Special:SupportedLanguages. In language selector of Wikimedia Saraiki is Written two times. Kindly Skr-arab be deleted.

15:33, 27 July 2017

Merging messages between two variants can be easy for sysops by using Special:mergehistory, but I'd love to know what's your actual wanted code (aka merge which to which)? Merge skr to skr-arab? Or vice versa?

00:57, 1 August 2017
Edited by author.
Last edit: 12:34, 28 September 2017

In interface language merge Skr-Arab in Skr، In interface language the all work as stood as in Skr-Arab be adjusted as Skr, and the word Skr-Arab be deleted in the the internationalization of the the language. Wiki is only in Skr. Please this conflict be removed. Saraiki. (talk) 10:45, 1 August 2017 (UTC).

10:45, 1 August 2017


Could someone delete/empty this page? It is probably primary for Xtools; Wikimedia:Xtools-edits/sr-ec should be used (capitalized), and here it is non-capitalized and editing /sr is not possible becuase we got transferred to sr-ec (and sr-el).

There is some problem with saving posts here, so it is saved twice. And it constantly keeps asking Do you want to leave this site, Changes you made may not be saved...

23:25, 15 October 2017

CSRF token issue

I keep having to resubmit my edits, because they don't get saved and an "invalid CSRF token" warning is shown to me. I only have this problem with Translatewiki. Same browser works just fine with other MW wikis.

13:59, 15 October 2017

Can you try logging out and in again?

So far I have restart both hhvm and memcached and after I did that I haven't seen the problem again.

14:08, 15 October 2017

I just did. On logging back in, it gave me a hard time (kicked me out a few times, gave me a "our backend cannot process this request" error, etc). But now it seems to work fine.

14:30, 15 October 2017

I have same problem...

23:23, 15 October 2017


Could someone delete/empty this page, or capitalize the word it contains? Translations in /sr are probably primary relative to sr-ec; for Xtools, Wikimedia:Xtools-edits/sr-ec should be used (capitalized); here it is non-capitalized, and editing /sr is not possible becuase we got transferred to sr-ec (and sr-el).

23:22, 15 October 2017

LibreRouter: new project with software and HowTo booklets

Hi, we're curious about whether TranslateWiki might be a good home for the translation of a project we're working on, the LibreRouter. We want to translate software interfaces, documentation, and also an illustrated booklet about how to use the LibreRouter. There's more info about the project at

The code is in the repositories at, and is in English. All the software is in active development or pre-development. One of the apps in active development that's already giving attention to translation is

The source language for the HowTo booklets is Spanish. The text for those booklets isn't ready to translate yet, though we hope to have first drafts ready no later than mid-October.

Some people from our community would join the translation effort, especially for English, Spanish, Portuguese, and maybe German and Afrikaans.

We've tried the interface for translating software strings on TranslateWiki, and we like it. We're not sure if the format of the HowTo booklets is compatible with TranslateWiki, since those are long paragraphs of text. We tested on Zanata, and it worked with .ODT files.

If we need to use a different file format for the code i18n/l10n or for the booklets, we're open to that.

We're interested in TranslateWiki because of the community of translators already active here, and the long-term continuity of the TranslateWiki platform and community.

Does this look like a good match, LibreRouter with TranslateWiki? What would be necessary or desirable actions from the LibreRouter community in order to move forward? We're available to chat on IRC or via e-mail or here on this thread.

15:05, 21 September 2017

Hi TranslateWiki team,

I wonder how to get in touch with you so that we can figure out whether LibreRouter can join TranslateWiki. I don't see any email address to write to, and the IRC webchat isn't working at the moment (and I don't usually spend any time on IRC). I will respond here to the items listed on the New Project criteria page, and hopefully this will make it clearer whether LibreRouter can join TranslateWiki.

- Openness: yes, LibreMesh software and documentation use free and open source licenses, such as GPLv3.

- Development: yes, LibreMesh is in active development, using a Git repository for version control. The project has periodic releases of LibreMesh, and will have periodic releases of other software and documentation (which has't yet reached first release). Time to get translations into use is currently unknown, and depends on how often network maintainers update the firmware on their router (perhaps we could automate part of this process to make TIU faster, or have a translation-only auto-update so as not to deal with potential software bugs and version incomatibilities between routers on a network), and how often users update Lime-App on their phones. More discussion could be helpful.

- Integration: It seems very reasonable that TranslateWiki staff could have direct push commit access.

- i18n Support: two key parts of the LibreRouter system support i18n already (LibreMesh GUI and Lime-App), though I do not know if they support the details of i18n mentioned on the TranslateWiki New Project page. I have passed the Localization for Developers link to developers and they're looking at it.

- Communication: I am the current liason, and I am not active in development. I have communication with the developers, and it's feasible that one of the developers may takeover the liason role and/or at least one developer might be active in I am a user and tester of the software and documentation.

- File formats: yes, we use translation files, I don't know if they're in one of TranslateWiki's preferred formats. Here's a translation file for Lime-App , and I'll find one for LibreMesh.

We need to start translating this month, October 2017.

What else do you need to know in order to decide whether LibreRouter can join TranslateWiki?

cheers, Pato

20:35, 6 October 2017

The JSON format looks okay except we don't include the language code as a key in the file (it's already there in the filename). Would you consider changing that format?

Is the repository in GitHub your main repository?

I would request to add some message documentation to guide the translators (see

20:45, 6 October 2017

Does taking the language code as a key out of the file just mean removing the line   "es": { As well as the closing bracket } ?

Yes, the repository in GitHub is our main repository.

We will add some message documentation to guide the translators based on the advice at It might take us a week or so to start adding that documentation.

21:03, 14 October 2017

Yeah if the file looks like following, then we support the format.

  "key": "value",
14:10, 15 October 2017

Also, what are the howto booklets you mention in the subject? Our primary focus is on software user interfaces. [edit] We don't currently support ODT files. Some kind string extraction to another format would be needed. Are the booklets created so that they can be automatically generated from the translated texts (i.e. no hardcoded positionings with length restrictions)?

20:46, 6 October 2017

The HowTo booklets are a series of guides about the social, technical, and economic aspects of how to create and maintain a community network, with the LibreRouter as the example hardware and software. The idea is that each booklet will be laid out by hand after translating. This means that an automated workflow (as is used in software) is not our plan for the first three languages, and we would join only for the software interfaces.

However, if anyone can suggest a workflow to create the booklets that aligns with the way functions, we're interested to try it out since that could facilitate the translation of the booklets into many more languages. Perhaps the ODT parser from the Zanata translation management platform could be included in, or perhaps we could use a different format. Or perhaps a bit of the BookType software used to create the books at could be reused.

21:22, 14 October 2017

I haven't done that before. I am sure there are string extraction plugins for ODT. The problem is that usually booklets have quite tight positioning and size constraints. Doing the layout manually for many dozens of languages (and dealing with possibly frequent updates) doesn't scale. But a flexible or simple ODT file we could probably support if there is a suitable parser-generator we can integrate.

14:29, 15 October 2017

how to translate an article into wikipedia?

how to translate an article into wikipedia?

20:12, 13 October 2017

try ContentTranslation?

04:18, 14 October 2017

The last untranslated message is missing

I'm trying to finish the Swedish translation of Intuition, but there seems to be one message left to translate even though no messages appear when I open the translation GUI. Any help?

12:29, 10 October 2017

This sometimes happens because there is an optional message needing update, but I've checked the box under the three dots next to the "Translated" tab and nothing comes up. I'm not sure then...

12:55, 10 October 2017
13:02, 10 October 2017

I purged the DB manually and it is gone now.

13:03, 10 October 2017

Neat! Thank you so much!

13:43, 11 October 2017

When I encounter this bug on Commons, I can usually fix it by opening the last message I translated, add and remove a space (which enables the Save button even though no changes have been made) and then saving.

13:48, 11 October 2017

Translating *from* Italian *to* English


I'm very worried that this is too basic a question, but I'm just getting started and I'm feeling stumped, so apologies if this is a stupid question...

I am an Italian-to-English translator as my job, and what I'm really looking for is to translate Wikipedia pages in Italian into English (I have seen such pages while doing research, so I know they exist). So far, I've only found English stuff to be translated into Italian, which isn't really my thing, as I am a native English speaker.

I've only looked around a little bit, so I may well be missing something, but if you could give me a shove in the right direction of finding Italian stuff to translate into English, I would very much appreciate it.


18:29, 6 October 2017

Ciao, temo che in effetti qui non abbiamo nessun progetto che sia traducibile verso l'inglese, anche se potresti per esempio tradurre dall'italiano allo spagnolo. Per tradurre verso l'inglese in Wikipedia ti conviene andare in w:Special:ContentTranslation e poi selezionare l'italiano come fonte. Puoi anche contribuire a qualche progetto di traduzione tematico, per esempio w:it:Progetto:GLAM/BEIC/Voci elenca qualche centinaio di voci in italiano che non hanno ancora una traduzione in inglese (sono semplicemente quasi tutte quelle che non hanno a fianco "tradotto in en:"...).

18:53, 6 October 2017

Nemo, grazie mille!

20:14, 6 October 2017

Language selector does not worked

ULS does not worked now. Changing interface language trough user preferences also does not worked (new value is saved in preferences, but interface language is still in old language).

Worked only "&setlang=" option in the URL.

This is TWN local problem, in Wikimedia wikis all worked correctly.

PS: In the dev. console i saw two critical errors:

  • Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
  • analytics.js Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

Maybe these is related with this issue.

09:53, 5 October 2017
11:32, 5 October 2017

I have rolled back last deployment while investigation continues.

12:47, 5 October 2017

Currently all works correctly. Thanks!

17:19, 6 October 2017

Hi there, I'm trying to replace the content in Template:Doc-apihelp-param with Template:Localized in order to make it possible to translate it to other languages, since other templates (Template:Doc-singularthey to name one) used in documentation pages allows this. I wasn't successful in my (two) attempts, since the bullet list that follows "For other messages relating to this module[...]" won't display, so now I'm asking for assistance. The problem seem to lie in the fact that the some parameter values, like params, won't pass to the sub page I created for the English translation (Template:Doc-apihelp-param/en).

22:45, 3 October 2017

Support for Kumyk

Hi everyone!

Would like to request support for Kumyk language.

Portal link:

Looking forward to your reply


00:11, 15 September 2017
Edited by another user.
Last edit: 19:31, 18 September 2017

I am supporting this request. This user is one from active participants of test Kumyk Wikipedia in the incubator:.

11:41, 15 September 2017
Edited by another user.
Last edit: 19:30, 18 September 2017

I am supporting this request.

18:13, 16 September 2017

Fallback to Russian? English? Or others?

04:31, 17 September 2017

Could you please specify what fallback means within Wikipedia? Or link me to the info? Thanks a lot

Got it.

Fallback to Russian, next to English. Thanks

19:30, 18 September 2017

hey guys! any updates on this request? thanks

21:30, 3 October 2017

How can the language name be changed?

For Gothic it says "gutisk", but it should be "gutiska razda". Where can this be changed?

01:04, 3 October 2017

In general, those language names are handled by CLDR. However as I checked Locale Data Summary, there's unfortunatelly no Gothic locale available.

If by filling this thread you mean that those should be shown in Gothic, please first file a new ticket (ask @Amire80: if you don't know how to submit it).

If you visited a site in other languages, and saw that name is shown wrong, can you provide which language were you using in that time?

10:37, 3 October 2017

Why are translations in the Gothic wiki not correctly imported?

I translated recent changes as 'aftumistos inmaideinos', but it shows 'aftumistos maideinos' for months now, it's the samewith other words and phrases.

02:39, 1 October 2016

What I don't understand isthat I translated all instances like this. So why does it show an old translation?

02:41, 1 October 2016

Local messages such as w:got:MediaWiki:Recentchanges need to be deleted, for the MediaWiki translations to take effect.

12:06, 1 October 2016

@Krenair: Isn't this tracked at phab:T45917? Or why don't you use script on gotwiki?

23:12, 1 October 2016

Irrelevant, the script is used for identical messages. Local sysops need to delete the non-identical messages where appropriate (after copying the translation here if it's better for all MediaWiki wikis).

08:27, 2 October 2016

My adminship recently expired so I 'll unfortunately have to wait some time to do this... And we have 0 admins currently.

15:16, 2 October 2016

Where can I find a page with all our local MediaWiki messags to delete?

15:19, 2 October 2016

Pressing the delete button is the smallest part of the job. If you make a list of messages to delete, people at m:SRM will gladly delete pages for you.

15:20, 2 October 2016

All local MediaWiki messages of Gothic need to be removed

An administrator needs to do this, I didn't want to become one again, so I van't remove them.

These all need to be removed. It is interfering with all the translations I did in Translatewiki and the results don't show up because it is wrong here.

02:35, 30 September 2017

Please enable Tunica for translation

I'm trying to start translating text for a Tunica-language wikipedia. Here is the required info about the language:

  • ISO 639-3 language code: tun
  • Language name: Tunica – Yoroni (tun)
  • Left-to-right language


23:23, 2 October 2016

Is more information needed? What can I do to make this happen?

16:19, 8 October 2016

I checked Wikipedia and ethnologue and they both say it's a basically dead language with no fluent speakers. This makes me doubt how are you able to translate MediaWiki which contains many technical terms to this language. Is there a standard orthography? We are having troubles with other languages here where there is no standard orthography and then translators are fighting with each other about correct spelling.

14:46, 12 October 2016

I completely understand your skepticism. The language is being revitalized, much like Manx or Cornish have been. There is a standard orthography, a textbook, children's books, and other materials. Information can be found at the University of Hawaii's Catalogue of Endangered Languages (elcat). The revitalization project, of which the Tunica-Biloxi tribe itself is the main driver, continues to gain momentum, and we have several editors up to the task, with over 50 years of combined experience with the language. We're eager to get started on translating.

Thanks so much for your help.

16:39, 14 October 2016

What is the status on this request?

15:39, 8 November 2016

Bumping again. We're busy writing articles in the language on the Tunica incubator wiki. It would be nice to translate the Wikipedia messages that will need to go with it at the same time.

21:20, 21 November 2016

Rejected. Heritage language of the Tunica-Biloxi Tribe of Marksville, Avoyelles Parish, Louisiana. There is no benefit in creating this as a UI language. Please focus your efforts on digitizing the language corpus, etc.

12:37, 20 May 2017

There is a great benefit to creating this as a UI language for the students who are learning it. I appreciate the suggestion to focus on "digitizing the corpus, etc." but that has already been done. The comment seems to imply that the language has no current speakers. The page from which the heritage language quote is pulled clearly shows that this is not the case.

Why has Cornish, which also has a small number of L2 speakers and no L1 speakers, been granted not only translatewiki permission but also its own wikipedia page, while Tunica can't even get past this step? If there is a lower limit to the number of L2 speakers that must exist in order for a wikipedia UI to be beneficial, or something else that differentiates Tunica from Cornish, please advise.

I realize that the service offered here isn't vital to the continued revitalization of the Tunica language (nor was it vital to Cornish), but it would be helpful, and it's disappointing that a single sentence in contradiction of everything that's been updated more recently can scuttle approval. If you require more proof that people speak and use this language, I'd be more than happy to provide it. There are people who want to learn in this language, as there are people who want to learn in Cornish. There is no one who speaks Cornish who doesn't also speak English, but this does not mean it wasn't beneficial to create a Cornish Wikipedia. In the same vein, it is indeed beneficial to allow for the creation of a Tunica Wikipedia.

I hope you reconsider your rejection. Additionally, I hope that, as the wheels of bureaucracy gradually turn and more updates are made on the sites of various gatekeepers of language status, it will hopefully become harder for people to find outdated information on the Tunica language that they can use to inappropriately justify rejection of a spoken language for translation.

17:08, 28 September 2017

Filter out API messages?

There are soooo many API-specific messages, and they will only be read by a tiiiiiny fraction of the people who use MediaWiki. I'd like to focus on translating anything else, but as far as I know there's no way to do that. Would it be possible to implement something to filter them out from Special:Translate (and the stats at Special:LanguageStats)?

12:14, 15 September 2017

I second that.

23:01, 17 September 2017

The same with the localized Wikimedia project names, iHRIS, iNaturalist, Mifos and future big projects.

07:54, 28 September 2017

Mistakes in edit protected pages: choosen instead of chosen

09:38, 27 September 2017

Support for Guianese Creole French

Hi, there would be someone who could help me, I have as a project a new Wikipedia that is in the incubator of Wikimedia and I want to know what to do on this site with regard to my language, because I have already created the portal of the language but I don't know what to do after...?!

23:38, 20 August 2017

See We can use French as secondary (fallback) language, right?

04:26, 21 August 2017

Yes but if I use French as a secondary language what will be in French on the Guianan Wikipedia ?

14:42, 21 August 2017

Hi everyone, there would be someone who would activate the translation for my language please ?!

12:10, 6 September 2017

why no one answers me, it's been nearly a month that I ask the same question and no one answers me ?

18:01, 6 September 2017

If French is the fallback language, the interface of the Wikipedia will be in French where it's not translated.

06:20, 8 September 2017

why my language is not part of the active languages, without that I can not translate anything in Kréyòl Gwiyanè (Guianan Creole) !!!

17:42, 11 September 2017

In the meantime, you can write a MessagesGcr.php file (french example).

If nobody else answers here, you may open a Phabricator task with "MediaWiki-Internationalization" tag.

18:33, 7 September 2017

I don't know how to write a MessageGcr file I have to look but I have not found !

23:05, 7 September 2017

Why doesn't support my language so I can start translating what to translate ???

04:51, 10 September 2017

To write MessageGcr file, you only have to replace French translations after arrows (=>) by Creole translations. For example, the first variable corresponds to namespaces.

The second variable is aliases and can be empty, like this: $namespaceAliases = [ ];.


16:11, 19 September 2017

Yes I see what you want me to translate, but I don't know this site, when I type this (link), there is nothing that tells me to create this page or this message, this site is not like Wikipedia, I don't know how to use it!

19:45, 19 September 2017

Sorry, I have not been clear. You do not have to create this file on the repository.

I only wanted to advise you to prepare this file. You can for example create it as a local file on your computer or as a wiki subpage of Gcr portal. A developer will post your file when it will be time, don’t worry. ;)

20:39, 19 September 2017

I have opened the task for you, hoping it can help you to receive an answer more quickly.

17:07, 18 September 2017

Lost edit summaries

The popup thing that is supposed to warn you about the importance of edit summaries actually eats them if you submit the edit form via keyboard.

18:38, 30 June 2015

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page.

Return to Thread:Support/Lost edit summaries/reply.

Thanks for reporting. What do you suggest/plan to do? Did you report this on phabricator with more details in the meanwhile?

21:08, 31 August 2015

T111670. I suggest removing $wgDefaultUserOptions['wikieditor-publish'] = 1; from the TranslateWiki configuration; it seems to be a thoroughly useless feature.

07:05, 7 September 2015

Thanks, now I understand. I never use WikiEditor so I had no idea those buttons existed.

07:33, 7 September 2015

I don't find such a setting in the current or past configuration for twn. Hmm.

13:06, 21 May 2017

Tested with a new account and it indeed defaults to off. Maybe I just enabled it manually a long time ago and forgot it (it's the "Enable step-by-step publishing" option in Editing > Labs features btw). Sorry for the noise.

21:03, 17 September 2017

Talk page preview on message pages creates "Changes you made may not be saved" window in browsers

When creating new topic on e.g., after typing something and clicking "Show preview", I get Leave–Stay window (in Chrome: "Changes you made may not be saved."). Same happens when saving or leaving talk page after saving.

Also, after I saved this thread / new topic here on Support and tried to leave page, I got Leave–Stay window (after choosing to Leave, message was saved indeed – so conclusion is that something is 'false-positive' creating this). Editing this comment is fine, no Leave–Stay window.

23:39, 15 September 2017
First page
First page
Previous page
Previous page
Last page
Last page