Jump to navigation Jump to search
NoteProblems? Questions? Suggestions? Write your message below. — See also the FAQ or try to catch us in IRC or in Telegram.

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

First page
First page
Last page
Last page

External Guidance in MediaWiki

Hi! External Guidance extension needs doc pages to provide context. I don't know what I'm translating.

Do the translation variables on the pages above represent languages?

Piramidion (talk)10:20, 9 January 2019

Block user

Hi, I request that an administrator consider the temporary blocking of User:Navhy. He has been modifying messages in Galician language unnecessarily, causing an increase in revision work (you can review my last undo contributions). The user was already warned several times on his talk page but he has not attended to the reasons given. Bye.

Elisardojm (talk)09:02, 14 January 2019

The last edit was yesterday and the last message on their talk page months ago, so I sent a reminder/warning.

Nemo (talk)11:32, 14 January 2019

Ok, thanksǃ

Elisardojm (talk)13:49, 14 January 2019

Deletion request

Shirayuki (talk)06:42, 14 January 2019

Add Baluchi(بلۏچی) Language for translate

Please add Baluchi language to translate. We want be together for growing Baluchi Wikipedia.

Basic information language code: bal language name: Baluchi self-name: بلۏچی Script: Arabic Direction: LTR

Sultanselim baloch (talk) 13:22, 11 January 2019 (UTC)

Sultanselim baloch (talk)13:22, 11 January 2019


This message is missing 'to' (and 'the'?):

Press <b>F11</b> to toggle the <i>web browser</i> fullscreen
— Mar(c).10:56, 6 January 2019

Northern Thai variants

I'm trying to add translations for Northern Thai and I'm having problems putting them in the right place. The root of the problem is that there are three groups of writing systems:

  1. nod-Lana: The Tai Tham script writing system. The language name may be written ᨣᩤᩴᨾᩬᩥᨦ in this group.
  2. One variant of nod-Thai, which is a transliteration of nod-Lana, though it does not faithfully represent mere spelling variations within nod-Lana. In this scheme, the language name may be written คำเมือง.
  3. The other variant of nod-Thai, where stop consonants have their Siamese values rather than the Northern Thai values as in the previous scheme. In these schemes, the language name may be written กำเมือง, as seen in the longer form กำเมืองล้านนา used by the 2017 New Testament.

The Northern Thai wikipedia, currently only in the incubator, is primarily in Scheme 1, with Scheme 2 desired as an alternative orthography. Most users of the language can't read scheme 1. Most users of the language should be able to read standard Thai, and therefore be able to read scheme 2, where words are often the same as in Standard Thai. Scheme 3 is the natural one for sounding words out, and is the Thai script scheme chosen for the New Testament. It also seems to be the one with the greatest informal use. Most of the Northern Thai Wikipedia 'community' seem to turn their noses up at it. I argue that 'nod' ought to imply 'nod-Thai'; I further believe that it should imply Scheme 3 rather than Scheme 2.

As far as I can make out from the nod portal, translatewiki is set up to support schemes 1 and 2, and they appear to be nod and nod-Thai. When I choose the language to translate to, the names available for selecting a language are nod and คำเมือง. As the name is in the Thai script, I assumed I would have selected a Thai script orthography, and from the first letter, scheme 2 above. However, the entries I have added (all in the Thai script) by selecting the language คำเมือง are all stored in the "nod" language variant, which appears to be intended for the Tai Tham script version (Scheme 1).

Note that translations to Scheme 2 can naturally fall back to standard Thai.

My immediate request is to be able to select Scheme 2 for entering translations; that is the more useful scheme with fairly obvious spellings. (Scheme 3 seems to have several subschemes, some based on dialect areas - Chiang Rai v. Chiang Mai.) So, how do I select Scheme 2 for data entry? Scheme 2 translations can be converted to Scheme 1 translations fairly easily, though full automation is not possible.

RichardW57 (talk)03:07, 9 January 2019

"Revision rules"?? Isn't it "revision rulers"?

Tektasc (talk)17:28, 2 January 2019

I would like to know what "revert plan" means here. Does it mean cancel changes or go back to a hole previous plan? Thanks in advance.

Tektasc (talk)13:27, 2 January 2019

Not sure about the meaning of this one


I am trying to translate this passage: "This comment was made on a file which this file was moved to, but in an older diff."

Could a translation of that be: "Ce commentaire a été fait sur un fichier sur lequel ce fichier a été déplacé, [...]"

Thanks in advance, hope I understood it right.

Tektasc (talk)18:22, 31 December 2018

'Tab' est traduit d'ordinaire par 'onglet'. Ici 'panel' que l'on voudrait traduire par 'panneau' à de nombreuses reprises a été traduit par 'onglet', mais on aurait eu dans ce cas 'tab' dans le texte EN. Quelqu'un peut-il préciser svp ?

ChristianW (talk)12:09, 31 December 2018

Statistics per project per languague


I would like to see some statistics about all users active on one project. Something like this but with an extra selection on project. So it is in total a selection about project and language.

And and also interesting but less important an selection on project but then all languages, something like this or this but then not a selection on languague but on project.

Optilete (talk)18:07, 23 December 2018 Like this, but not for 7 days but for 365 days or a calendar year (like 2017,2018) and a selection for a project.

Marcelhospers (talk)10:26, 31 December 2018

I want to be editinterface user here, so that I can translate those messages for Urdu which require editinterface permission. How it be? Muhammad Shuaib (talk) 16:20, 25 December 2018 (UTC)

Muhammad Shuaib (talk)16:20, 25 December 2018

There is only a couple of those, and those are expected to be temporary. You can provide translations here and an admin can put them in place in the meantime.

Nike (talk)13:03, 30 December 2018

Is it possible to merge two users?

Hi, For some reason I've got two user accounts on, probably due to a misunderstanding concerning username and a display-name, or even the fact that my display-name contains a special UTF-8 letter.

I'm currently using Sveinn í Felli but my old login was Sveinki. It would be nice (and useful for avoiding misunderstandings) to have this latter account point to the former, or to merge them so that Sveinn í Felli becomes prevailing.

Is this possible?

Sveinn í Felli (talk)09:29, 2 February 2018

Yes, this is on TWN, where we are not in the WMF instance, so we can try merging your two accounts.

Liuxinyu970226 (talk)09:43, 2 February 2018

Can you please do it?

Sveinn í Felli (talk)15:12, 2 February 2018

Should I send a specific request to someone? Where/Who?

Sveinn í Felli (talk)10:53, 15 August 2018

We don't have any user merge extension here and there's no plan to install it, so I'd just decline this request. User:Sveinki has less than 500 edits; User:Sveinn í Felli is older, has an email address and was used recently. If you just stop using "Sveinki", you'll be fine. I can block and/or rename the account you don't want to use and you can place a redirect from one username from the other. We can also recover the password of either account if you lost it and the email address doesn't work.

Nemo (talk)11:02, 15 August 2018

"you can place a redirect from one username from the other" - yes, that was in my initial request. How can I redirect User:Sveinki to User:Sveinn í Felli ?

Sveinn í Felli (talk)11:00, 4 December 2018

I've redirected them for you.

McDutchie (talk)23:08, 20 December 2018

Adding DSpace

DSpace is a mature open source project originally created by HP and MIT back in 2002, now supported by a non-profit Duraspace. It is a web based platform for institutional repositories, used by academic, non profit and corporate institutions to provide (open) access to hosted content.

Some examples:

We became interested through the website and when chatting with your contributors, who advised us to answer the following six questions as part of the request to be added as a project. We would like to enter a dialogue to see if we could get adopted and what that would entail exactly.

1) is your code open source?

Yes, the license files can be found on:

2) is your development active currently and to the foreseeable future?

Yes, DSpace is being actively developed under a time based release schedule. The draft of the release notes for our next major release end of 2013 can be found at:

3) what file formats do you use?

DSpace has two user interfaces, one based on JSP and one based on Apache Cocoon. The JSP User Interface uses Java properties:

The Apache Cocoon based interface uses an XML format, the standard Cocoon Catalog/Dictionary format described midway down the page here:

Actual files can be found here:

More information describing the current state of the DSpace internationalization efforts can be found on:

4) do you have resources to address reports from (like, requests for adding message documentation, fixing i18n issues in messages)?

Yes, the DSpace committers and other community members actively address such reports in the DSpace JIRA environment:

5) can you appoint a contact person

6) Are you okay for using only as the way to contribute translations

We would have to investigate the details of what this entails exactly, but in principal we will agree to this as long as: - it should be easy for people to provide translations - it should be easy for people running a DSpace installation to do local changes or additional translations within their own instance of DSpace if they would want to.

Bluyten (talk)23:03, 19 June 2013

Thanks for your interest. I've checked out the product and the license. I think there is definitely a basis to explore further. Thanks for considering

I've looked at the two file formats for i18n that you linked to. I wasn't able to identify the file containing the source texts, for example in Where are those files located?

As for the XML format in; we do not support that file format yet. I'm not really a developer, but I took a stab at adding support for it in gerrit:70602 based on the Android XML format support that we already have. Would it be possible that one of you completes the patch set?

Siebrand09:25, 26 June 2013

The original source for can be found here:

For the Cocoon XML format: I will try to find someone to look at your code and finish this.

Bluyten (talk)10:04, 27 June 2013

That's cool! We have some documentation for that at

Nike (talk)08:09, 1 July 2013

Just a quick note that we haven't forgotten about this and will follow up in due course.

Bluyten (talk)12:41, 25 July 2013

Thanks Bluyten, please let us know here of any roadblock.

Nemo (talk)13:51, 29 July 2013

What's with the checks that are preventing the message Wikimedia:Wikipedia-library-ae475f-=7B=7BPLURAL:GETTEXT=7CContact=7CConta/en from being translated? I get the error message "The following parameter is unknown: {{PLURAL:GETTEXT|Contacto|Contactos}". Isn't the message supposed to be translated?

Hamilton Abreu (talk)16:40, 23 October 2018

Hi, I no have this problem. Can you check again?

Zoranzoki21 (talk)20:19, 27 October 2018

It continues.

To check it yourself, click Wikimedia:Wikipedia-library-ae475f-=7B=7BPLURAL:GETTEXT=7CContact=7CConta/pt and click "Edit". It will show:


This is the translated message, with "Contact/s" translated to Portuguese. The message is fuzzied because of the error reported. Now, remove the "!!FUZZY!!" and save it. Edit it again and the "!!FUZZY!!" is still there, meaning that the problem continues.

Now look at all existing translations. All those that have been translated are coloured pink, meaning they have a problem. For those that are not coloured pink, most were initially translated to the target language, got the same error and then people put them in English to get rid of the error. The only exception is /fi, which was inserted by the bot already translated.

So, the problem most obviously exists! When you state that you do not have this problem, EXACTLY WHAT LANGUAGE DID YOU TRANSLATE THE MESSAGE TO SUCCESSFULLY without the problem? There is no successful translation of this message made by you.

Hamilton Abreu (talk)00:59, 28 October 2018

Shouldn't the check that is preventing translation of the words "Contact" and "Contacts" be removed?

Hamilton Abreu (talk)11:50, 22 November 2018


Hamilton Abreu (talk)23:24, 11 December 2018
Nike (talk)13:52, 17 December 2018

Confirmed. Many thanks.

Hamilton Abreu (talk)20:13, 17 December 2018

Delete account or change username to sth anonymous

Hi. I dont have any contribs. Could you please Delete account or change username to sth anonymous? Thanks

Yasinaydin (talk)22:15, 16 December 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

About capital letters "KP"

Hello. I don't know why bot create two category named Category:User ko-kp and Category:User ko-KP.

In this situation, how can I fix this babel's problem?


Garam (talk)09:51, 7 December 2018

cannot PREVIEW my text when writing a message for Support

On I have checked last Experiemntal [X] Mettre en évidence les sélecteurs CSS i18n.

When I write this message for support and click on the Preview button, the popup says the equivalent of 'you'll leave this page and loose your modifications' instead of showing the new formatting for possible correction (<= nok)

When I use the visual editor and ask the preview in a similare way for standard messages translations, the new formatting is well presented and the correction is possible (<= ok, normal behaviour).


ChristianW (talk)11:55, 28 November 2018
First page
First page
Last page
Last page