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

Publishing the translation failed

Hello I was not allowed to publish 63 translations into Lombard language due to this error messageː "Publishing the translation failed: You do not have permission to edit this page because it contains raw HTML which can be modified to affect all visitors." Therefore I need your help. I submit you the messages followed by their translations (please consider their wikitext)ː




Quell che te scrivet


Quell che te otegnet


















Test in corsiv


Test corsiv




Test in grasset


Test in grasset


Grasset & corsiv


Test in grasset & corsiv


Test in grasset & corsiv


Conligament interno


Conligament defoeura


Eticheta del conligament


<a href='#'>Titol de la pagina</a>
<a href='#'>Eticheta del conligament</a>


<a href='#' class='external'>Eticheta del conligament</a>
<a href='#' class='external autonumber'>[1]</a>
<a href='#' class='external'></a>


Intestazzion de segond nivell


Titol de la sezzion[edit]


Titol de la sezzion


Intestazzion de terz nivell


Titol de la sezzion[edit]


Titol de la sezzion


Intestazzion de quart nivell


Titol de la sezzion[edit]


Titol de la sezzion


Intestazzion de quint livell


Titol de la sezzion[edit]


Titol de la sezzion


Lista a pont


  • Element de la lista
    * Element de la lista


  • Element de la lista
  • Element de la lista


Lista numerada


  1. Element de la lista
    # Element de la lista


  1. Element de la lista
  2. Element de la lista


Fail incorporad




Test de l'insegna




Test de la pagina.<ref>Test del conligament, test adizzional.</ref>


Test de la pagina.<a href='#'>[1]</a>


Riferiment cont un nom


Test de la pagina.<ref name="test">Test del conligament</ref>


Test de la pagina.<a href='#'>[2]</a>


Un'altr'utilizazzion de l'istess riferiment


Test de la pagina.<a href='#'>[2]</a>


Mostra i riferiment


  1. <a title="" href="#">^</a> <a rel="nofollow" title="" class="external text" href="#">Test del conligament</a>, test adizzional.
  2. <a title="" href="#">^</a> <a rel="nofollow" title="" class="external text" href="#">Test del conligament</a>


Firma con marca temporal


--<a href='#' title='$1:Username'>Nom de l'utent</a> (<a href='#' title='$2:Username'>ciciarada</a>) 15:54, 10 sgiu 2009 (UTC)




<a href='#' title='$1:Username'>Nom de l'utent</a> (<a href='#' title='$2:Username'>ciciarada</a>)


Inseriment d'un spazzi voeud


Test normal
:Test cont un spazzi denanz
::Test cont un alter spazzi denanz


Test normal

Test cont un spazzi denanz
Testo cont un alter spazzi denanz


Page title
Eticheta del conligament


<a href='#'>Titol de la pagina</a>
<a href='#'>Eticheta del conligament</a>

Salvemm el lombard (talk)23:17, 22 January 2021

... working on it now...

Raymond16:44, 24 January 2021

Done Done

Raymond17:28, 24 January 2021

Thank you

Salvemm el lombard (talk)08:40, 26 January 2021

Username change

Kindly change my username to Yivan000 so that it will be consistent with other platforms.

Yivangamer (talk)03:04, 25 January 2021

Done Done

Raymond10:39, 25 January 2021

Change my username

Can someone help me change my name to LaMagiaaa? This is to unify with me on other platforms. Thanks.

Suchichi02 (talk)16:13, 23 January 2021

Done Done

Raymond17:29, 24 January 2021

Username change

Edited by 0 users.
Last edit: 23:16, 5 February 2020

Dear admins,

Is there one of you available and willing to change my current userName KlaasZ4usV to my real name I use on all WMF-projects except this one: Klaas van Buiten and leave a redirect behind. Thanks in advance for
? This issue is unconfirmed, still to be investigated
 Klaas `Z4␟` V23:16, 5 February 2020


Abijeet Patro (talk)06:43, 8 February 2020

Thank you, grazie, dank u

 Klaas `Z4␟` V10:09, 20 January 2021

[guw] Activate new language: Gun - 'Gungbe'

Hello. The Gun Wikipedia project has been initiated in Incubator. We would like to start translating the important messages into Gun language here. The language uses Latin script and write LTR. Please help activate it. Thanks.

Samatics (talk)10:34, 13 January 2021

This is enabled. I added a list of useful links to your user page. Good luck!

By the way, do you plan to write in the orthography from Benin or from Nigeria?

Amir E. Aharoni (talk)12:08, 15 January 2021

Thank you Amir. I plan to write from Nigeria.

Samatics (talk)12:55, 15 January 2021

What I mean to ask is whether you plan to write with the letters ⟨ẹ⟩ and ⟨ọ⟩, or with the letters ⟨ɛ⟩ and ⟨ɔ⟩.

Amir E. Aharoni (talk)14:00, 15 January 2021

Yes. I meant the Nigerian (Alada) variant which uses ⟨ẹ⟩ and ⟨ọ⟩. It is transborder. Thanks.

Samatics (talk)16:13, 15 January 2021

Hi, I'm Mahuton from Benin Republic. I can speak and write Gungbe too. Gungbe is spoken in Hogbonou, a border region with Nigeria. I think we can moveon with the nigerian variant.


Mahuton (talk)12:40, 16 January 2021

In the book Current Research in African Linguistics: Papers in Honor of Oladele Awobuluyi I found that the Nigerian variant was used only for a Bible translation in Nigeria, and that the Benin variant is used in schools, and that the proposals for unification are based on the Benin variant, not the Nigerian one.

Can you give some examples of where are the different variants used, and of how the Nigerian variant is used in Benin? Is it used in books, newspapers, websites, or schools?

Amir E. Aharoni (talk)04:59, 17 January 2021

Publishing the translation failed

There are two untraslalted messages of MediaWiki core messages due to this erro messageː "Publishing the translation failed: You do not have permission to edit this page because it contains raw HTML which can be modified to affect all visitors." They are listed below along with the translationsː

1 The english original message is (MediaWiki:Feedback-terms/lmo) "I understand that my user agent information includes information about my exact browser and operating system version and will be shared publicly alongside my feedback. The message traslated into lombard language is ː "Hoo capid che i me informazzion sora el me agent d'utent contegnen di informazzion sora el me programa de navigazzion che vegnarann condivise publicament insema ai me coment." 2 The english original message is (MediaWiki:Feedback-termsofuse/lmo) "I agree to provide feedback in accordance with the Terms of Use." The message traslated into lombard language is ː "Son d'acord de fornì di coment second conforma ai Condizzion de Utilizazzion"

Salvemm el lombard (talk)13:36, 11 January 2021

Reloading without cache in Opera

The message says:

"Note: After saving, you may have to bypass your browser's cache to see the changes.

  • Firefox / Safari: Hold Shift while clicking Reload, or press either Ctrl-F5 or Ctrl-R (⌘-R on a Mac)
  • Google Chrome: Press Ctrl-Shift-R (⌘-Shift-R on a Mac)
  • Internet Explorer / Edge: Hold Ctrl while clicking Refresh, or press Ctrl-F5
  • Opera: Go to Menu → Settings (Opera → Preferences on a Mac) and then to Privacy & security → Clear browsing data → Cached images and files."

But the last one is way too complicated, and it does something quite different from the first three: It clears the entire cache for all websites, which seems completely unnecessary. Why not just say "Press Ctrl+F5"? That's what Opera themselves say: "Ctrl+F5 - Reload page without cache, which is useful if something isn’t loading correctly on the page." (

I cannot change it myself, and the page told me to suggest the change here instead.

jhertel (talk)17:27, 8 January 2021

Patch submitted: Gerrit:655245. Waiting for review and merge now.

Raymond10:18, 10 January 2021

Standard date format in MediaWiki

In a MediaWiki installation you can select the preferred date format in Special:Preferences#mw-prefsection-rendering. Where is the standard value (called "No preference") set? – Is there a translatable string which determines the standard for a given language?

Dipsacus fullonum (talk)16:45, 9 January 2021

Hi Dipsacus fullonum, the standard for Danish is defined in

That means for any change a patch is needed. There are no translatable strings available.

Raymond10:09, 10 January 2021

Requirements to translate MediaWiki into a language.

Is there anywhere where I can read the requirements to be eligible to translate MediaWiki into a language?

Sabelöga (talk)01:42, 10 January 2021

The text on on: Wikimedia:Convenient-discussions-notification-reload/en 'Click to reload the page$1.' should be replaced by: 'Click to reload the page $1.' (= additional space between 'page' and '$1'

Robby (talk)00:01, 8 January 2021

iOS plural syntax off for N'Ko

The plural syntax for these translations broke our import script. I'm hoping my updates will fix them (see history):

Is there a way to kick off a new translations export? If not we can wait until this automatically kicks off. Thanks!

Tsevener (talk)23:49, 15 December 2020

Sorry, I did not saw this earlier. I noticed that a plural validator is not enabled for this project. Any issue if we add it?

Nike (talk)13:53, 4 January 2021

No problem - sure let's try adding it. I don't think there should be a problem but we'll keep an eye out for anything breaking on our end. Thanks!

Tsevener (talk)16:14, 7 January 2021

How to apply to add my open source project translations?

Happy new year.

My project is here:

The open source license is GPL-3.0

The translation files are here:

The format of the translation files are key-value JSON

机智的小鱼君 (talk)22:14, 2 January 2021

Hello 机智的小鱼君,

Happy new year.

Would it be possible for you to create a task on Phabricator by following this link? Phab task link

Secondly, I see that there is a single file that has the source and translations - Can we break these up into different files?

  • en.json
  • fr.json


I would also add a qqq.json file, that will have message documentation.


Abijeet Patro (talk)14:16, 4 January 2021

Thanks for reply!

I'll create the task on phabricator.

Btw, the languages.json file will be discarded. I realized that it is stupid to put strings of all languages in single file. So I'll using in the next versions.

机智的小鱼君 (talk)15:59, 4 January 2021

Alright, let me know if you need any help.


Abijeet Patro (talk)14:22, 6 January 2021

[bdr] Activate new language: West Coast Bajau - 'Bajau Sama'

Hello. The West Coast Bajau Wikipedia project has been initiated recently in Incubator. Hope we can start translating the important messages into West Coast Bajau here. The language uses Latin script and write LTR. Thank you.

Tofeiku (talk)06:42, 25 December 2020

This has been done. I noticed that there are already some translations, thanks for that!

Nike (talk)14:05, 4 January 2021

Problem with

Does anyone else have this problem? I've tried using two different browsers and the same thing happens: if I edit one of my posts, the edit does not show up even after a full reload. But once I add a reply, it does. It's bewildering.

Urhixidur (talk)14:44, 8 December 2020

Same problem here and not only on Support, when I edit a message, I need to do an ?action=purge to see the updated message.

Thibaut (talk)14:55, 8 December 2020

I am sorry to hear that. This extension we are using for discussions (LiquidThreads) does not have a maintainer and it has started to break in various ways.

We would do something about it, but it is not clear where to go. Don't have time to maintain LiquidThreads, Flow is in a similar situation without clear future and plain talk pages are not so nice.

Nike (talk)14:04, 4 January 2021

Quick question about grave accents


I didn’t get a reply on Thread:Translating talk:Phabricator/`$1` and it seems to affect other projects like Toolhub so I try my luck here.

Should we leave the grave accents `$1` as is or is it okay to replace them with quotes? Like here for example? Or here? It seems to me that grave accents mean that the text will be displayed in a monospace font and should be left as is but I might be wrong.

Pinging Verdy p and Urhixidur.


Thibaut (talk)17:08, 23 December 2020

I have serious doubts of te arguments made by Urhicidor that these backquotes are "executable". For me they are just markup (even if it's not the Mediawiki syntax) only for a presentation purpose (intended to render a monospace font, as if it was distinctive enough, whiole in fact such consideration should be in adequation for normal typography (here for a foreign word). I'm not even conveinced the monospace is good here, even if it is syntaxic: monospaced fonts do not line up correctly within sentences and here it is only a basic citation embedded in the rest of the code, and not a program or programming interface at all (monospaced fonts tend to create height line-heights, or would be decorated, making the paragraph conteining much more unpleasant to read, as it would be obscured by unnecessary decorations and extra padding and uneven font heights/line-heights. For me, it's jsut sufficiant to place quotation marks (if we don't want italics). But using quotation marks + monospace font with decaration and change of font-height is even worse: this is just abusing of emphasis.

We don't need it (note that in Mediawiki syntax using the "code" tag is also problematic with its decorations. The alternative was to use the "tt" tag, which undfortunately was deprecated without any good reason in Mediawiki (it was deprecated in HTML becauyse it was supposed to be equivalent to "code", but this is not true with Meiawiki renderers, so now we have to use "kbd" tags instead, which are LESS supported in browsers than "tt" which remains compatible with all of them, including HTML5: the "deprecation" meant only for its insufficient semantic purpose does not mean it is removed, just that "tt" has been *subclassed* by a few more precise element types: "kbd", "smp", however "kbd" iomplies user input and this is not true, while "tt" implied output with optional input on any terminal) HTML5 should have not deprecated "tt" at all (and in fact NO known browser have removed it, so HTML5 was wrong, and other other elements kept or added are not even really better for semantics.

Whinse use othe ways to represent verbatim text to type as is, with its own speciafic quotation marks (Chinese uses various quotation styles, whilst English is extremely poor at handling them correctly and consistantly; so inttead it uses stylistic conventions with uneven changes of font styles, which are not really easier to read and complicate to compose).

Verdy p (talk)02:45, 24 December 2020

Backticks (a.k.a. grave accents) are executable in most shells. There is no good reason to use them in English prose instead of straight or curly quotes, which is why the context of the messages in question leads me to believe they are meant to be executable. The qqq should clarify whether this is the case or not.

Urhixidur (talk)14:20, 2 January 2021

No. The most probabable reason is that it initially was using Markdown instead of the Mediawiki syntax for a monospaced font or text input (like in HTML with "code", "kbd", "tt" elements). It is not meant at all to be executable as is. this is just specifying text that can only be used verbatim (and normally not translated... except that we don't know what is in $1: if it was real code, the backticks would be part of the code and escaped inside $1, but here they are left outside of $1, meaing clearly that they are purely presentational and not semantic at all, so they are just used as a form of visual emphasis and backquotes should not be even present (or if they are, they should be correct quotation marks for the target language (and if quotation marks are really shown, there should not evben be any additional emphasing with italics or other font styles or decorations, the quotation marks being enough by themselves (and any other decoration being clearly redundant, according to almsot all typography handbooks for French at least, but even for English as well!).

Verdy p (talk)15:41, 2 January 2021

It will be difficult to get the Phab developers to comment on what's the intention with them. Most likely they are for monospace styling (which I don't think is for us to decide).

Nike (talk)13:44, 4 January 2021


Hi. Please mark Template:Optional for translation.

Shirayuki (talk)12:49, 22 December 2020

I approve; the recent changes did not work at all (the translation being actually in another subtemplate, listed in the documentation). Note: the template itself does not need to be translated, as the translation is actually in the subtemplate listed.

Now I see that with the most recent change, the template itself becomes translatable ; it i using now an "autotranslate" switch that detects when it should show the translated subtemplate directly, or use a "LangSwitch" function in a Lua module to select and render the appropriate translated subtemplate).

Note that I first invented this "trick" years ago, and it has been now more widely reused; it is a bit complex for some authors so it requires some explaination about why it is used and how it works: the trick does not require creating and maintaining another external template, all is done in the source template, and translated subtemplates are generated automatically with all new translations, and translators don't have to worry about the syntax, but only on actual translation items; and transcluding the template remains simple, as if it was not translatable, without changing the syntax; the tricks works with a "#switch: on an empty translation unit, which will be effectively empty on the generated translated templates, but not empty on the base template as it still contains the "translate" markup (opening and closing "translate" tags are eliminated only in a later phase just before the HTML generation, but not during the template expansion) and this allows the correct behavior to occur.

Note that this is still a "trick", which may eventually change and no longer later, provided that the translate extension provides a way to detect if we are on the base source page or in a generated translated subpage (this is not the same as detecting the current page language, which is not testing the template page itself but the target page of the transclusion).

Verdy p (talk)16:44, 22 December 2020

I don't understand why so much effort is put into this template. There are plans to convert this to be a feature of Translate to avoid divergence between configuration and message documentation:

Nike (talk)07:51, 30 December 2020

Non-"empty" translations of MediaWiki:Edittools

As per the documentation, MediaWiki:Edittools is supposed to be empty except for an HTML comment explaining how wikis can choose to use that feature. TWN has chosen to use this feature, as have many other wikis, but it appears that some translators have translated (sic; it's not like the message itself has much translatable content) TWN's local Edittools and these translations have been sent back to the MediaWiki core repository.

Such "translations"/impacted languages include:

Additionally, though not related to this particular issue, MediaWiki:Edittools/bcc seems to contain pointless <strong> tags inside the HTML comment.

Jack Phoenix (Contact)08:12, 29 December 2020

Fixed by reverting customizations or deleting.

Nike (talk)09:11, 29 December 2020

The description of variables made in MediaWiki:Notification-header-commentstreams-comment-on-watched-page/qqq indicates the parameter $5 for the user name to specify in {{GENDER:$5|...}}.

But the English source message in MediaWiki:Notification-header-commentstreams-comment-on-watched-page/en uses the unspecified parameter $6 for the user name to specify in {{GENDER:$6|...}}.

This is a contradiction. This can affect translations not working as expected.

Same problem in:

Verdy p (talk)23:39, 25 December 2020

This message most probably has a missing } for properly terminating a plural tag.

Verdy p (talk)23:36, 23 December 2020

Done Done Gerrit:651915. I will deploy later today.

Raymond13:34, 24 December 2020

unspecified "required" encoding/escaping in Wikimedia:Pageviews-url-structure-massviews-target/en and others

This message to be translated does indicates that the question mark must be encoded, but it does not explicit which form should be used.

In my opinion, we should not have to reencode the URL in the application and should be able to post the exact URL as it works, it should be up to the application to reencode it if it wants to encapsulate it into another URL or document format (other wise the result for any URL is unpredictable, notably for other characters like %, <, >, &, #

Note that a non-encoded URL may contain a fragment identifier, but if the URL has to be encapsulated into another URL for example in a query string parameter, that hash character will also need to be encoded, and all percent characters; whitespaces may also be present in non-encoded wiki page titles, and are normally reencoded in the URL form, but the default in browsers is to rencode them as +, whilst MediaWiki reencodes them as _ for page titles. Mediawiki also has special handling for + or ? and some other punctuations, allowed in page titles, that also need to be encoded for URLs, to avoid their interpretation as whitespaces remapped to '_' or as a question string delimiter. For URLs to some "Special:" pages there are other restrictions or different behavior for whitespaces.

So at least first explicit how to encode the question mark; but in fine please change the application's code to handle itself any needed reencoding, so that we won't ever need any such manual unpredictable tweak; in that later case, drop this statement from the message.

Note that there are various messages asking to the final users (reading these translated messages) to use an escaped form for some parameters or values to provide in the final app. This is generally not clear when there's no link to explin how to safely escape these parameters, and as well this exposes server-side or client-side security issues, or unexpected side-effects (which may be desastrous, either for theses users themselves, or site-wide or application-wide for all their users): those messages should be updated to reflect a change in the code of Mediawiki or its extensions: it's up to these applications to handle the proper escaping. Translators should not bothezr about this internal technical trick.

Verdy p (talk)15:21, 23 December 2020
First page
First page
Last page
Last page