Jump to navigation Jump to search
NoteProblems? 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. Very old threads have been archived.
(The thread summarization feature is broken, see: Phab:T245109)

First page
First page
Last page
Last page

Gothic language issues

I would like to ask what the gain is of having the translation interface locked of Gothic. I have studied Gothic thoroughly and corrected about all articles in Gothic, now the only problem is that we can't change the interface with grammatically completely incorrect translations. Since we can use the Skeirs font now globally, we don't need to add translations in latin script anymore and we can do everything in Gothic, but the export function is closed for years now with an interface which has a few thousand translations, the reason given is that it's a dead language, but why is Anglo-saxon and Latin not locked then? The administrator Siebrand advised to completely remove it, so should we also remove the translations of Anglo-saxon and Latin, which are dead languages too without native speakers? I would like to ask what makes it difficult to open up the interface again so that I can correct everything.

Gothicspeaker (talk)20:54, 31 March 2016

With articles I mean the ones in the Gothic wikipedia,

Gothicspeaker (talk)20:55, 31 March 2016

Add my extension for translation

Edited by another user.
Last edit: 07:24, 27 March 2016

I would like to request to add the extension mw:Extension:Avatar, hosted on GitHub, for translation. The officially supported languages are English and Simplified Chinese.

Nbdd0121 (talk)21:42, 26 March 2016

We don't (currently) do GitHub extensions. Any reason you can't mw:Git/New repositories/Requests move to gerrit? Once that's done, you can simply add Raimond to reviewers and he'll tell you what to do.

Nemo (talk)07:28, 27 March 2016

I can already tell you that you need to add a qqq.json file with message documentation.

Nemo (talk)07:34, 27 March 2016


[1]"MediaWiki:Notification-body-flow-post-reply" is not a translatable message, these pages are useless and should be deleted.

By LNDDYL. (Talk)08:08, 23 March 2016


[1]"MediaWiki:Notification-bundle-body-flow-post-reply" is not a translatable message, these pages are useless and should be deleted.

By LNDDYL. (Talk)08:11, 23 March 2016

Translating the 500 most used messages into Kabiyè

I am working on the Kabiyè (kbp) Wikipedia which is currently in the incubator. Apparently I need to translate the 500 most used messages before it will get moved to the real Wikipedia platform. But I'm not sure how to use this page. We need to use a French list. Where do I post the translations? When I try to choose "translate Kabiyè" in the top RH corner it doesn't let me. I also tried to export the list to work on it offline, but that didn't work either. We can work on this as soon as we know how. Any advice welcome. Gnangbade (talk) 18:49, 22 March 2016 (UTC)

Gnangbade (talk)18:49, 22 March 2016

Please change to "Date range".

FriedhelmW (talk)12:19, 19 March 2016

Visualeditor-toolbar-insert and related items

Would it be possible to split the items from the dropdown list and the titles of the new dialog windows that open up?

The problem I have is the verb "insert" ("unesi") needs to be followed by a word in the accusative case in the dropdown items, but the item following the verb needs to be displayed in the nominative case for the window titles in Bosnian. For example – <visualeditor-mwgalleryinspector-title> should be "Galeriju" in the dropdown, whereas it should be "Galerija" in the window title.

Srdjan m (talk)10:36, 16 December 2015

Empty? Perhaps should be

NoteTranslators: Don't translate this message.


Liuxinyu970226 (talk)08:58, 16 March 2016

Change username

Hi! Can you change my username to Josep Maria Roca Peña, as on Wikimedia and Wikia, please?

Josep Maria 15. (talk)00:06, 16 March 2016

Display of strings in fallback language

A thread, Thread:Support/Display of strings in fallback language, was moved from here to Translating talk:OpenStreetMap. This move was made by Nemo bis (talk | contribs) on 15 March 2016 at 18:32.

Quick intersection

Is there something like Magnus' tool that can be used here as well - basically, to find people proficient in more than one given language? Thanks.

Elitre (WMF) (talk)12:36, 13 March 2016

Yes, see mw:Help:CirrusSearch (incategory). If that doesn't work as expected, let us know.

Nemo (talk)18:31, 15 March 2016

This message lacks plural support.

Robby (talk)05:49, 14 March 2016

Change username

Because I'm a little dumb I made a mistake while registering, I have set my username to "Cl3m3n7" but it should be "C13m3n7" as it is on Wikipedia

How can I change my username ?

Thanks :D

Cl3m3n7 (talk)20:20, 13 March 2016

Question about masive edits

Let's say you want to unfuzzy theese translations. Could Replace Text be used for that?

If I could export all fuzzy translations of a given message to work offline, I could do it with any text editor. But it seems that you can only export messages from a given group and a given language.

Does anybody know any other way (online or offline)?

Macofe (talk)05:06, 2 March 2016

If you know how the regular expressions of Special:ReplaceText work, you probably could. I think Raimond doesn't know it, which is the primary reason it's not been done already.

Siebrand12:26, 9 March 2016

I've done a quick test. A simple regular expression doesn't replace all instances, but about 125 have been done.

This was a replacement of:

  • '''(.*:)'''
  • <strong>$1</strong>

The regular expressions will not always be this easy.

Siebrand12:39, 9 March 2016

I don't have access to Special:ReplaceText. Raymond does a good job, so let's leave it to him. I could ping him in the future with regex for him to run/test.

Macofe (talk)05:04, 10 March 2016

Meaningless cosmetic changes fuzzing translations

I have just created which says:


I would like to point your attention to this message's history.

The changes are: ''$2'' ---> "<i>$2</i>" ---> "''$2''" ---> "<em>$2</em>" ---> <em>$2</em>

Every change fuzzied every translation made until every one of thoose changes occured. In particular, the last one fuzzied over 200 tranlations. As a reminder, marking a message as fuzzy means that the translated message will be back to the English source until someone confirms or changes the translation. And we are taking about a message in "MediaWiki core".

Is this necessary/desired? Have developers been informed about the consequences of their changes to English source messages marked for translation, the number of current translations, the numbers of final users affected, and the time that they required from volunteer translators?


I would like to hear everyones opinion on this and possible solutions.

Macofe (talk)21:16, 28 February 2016

I'm sorry to see this frustrates you. Localisation is a very dynamic thing. These things have always changes, and will remain to change. We try to be as careful as we can by reviewing new messages as they come in, but new insights also cause large changes to existing messages. The changes you point out above, for example, have a large impact for accessibility of the features they are for. Screen readers do nothing with the HTML tags b and i, but they do operate on strong and em. Thanks for understanding.

Siebrand12:24, 9 March 2016

Thanks for your answer. I didn't know about screen readers and HTML tags compatibility. So thoose changes are not "meaningless cosmetic" as I said. I didn't know either that fuzzing messages does not mean that the translations are lost as I thought (that is why the ticket was closed as invalid). I don't feel frustrated now :)

Macofe (talk)04:43, 10 March 2016

I would like to change my name to "Caçador de Palavras," is it possible?

Raphaelras (talk)02:48, 1 March 2016

What does "but it's not" in context of this message mean? But it's not a description or what?

Piramidion (talk)18:39, 23 February 2016

Information needed.

Macofe (talk)04:25, 23 February 2016

Documentation needed.

Macofe (talk)03:37, 23 February 2016
First page
First page
Last page
Last page