View source for Thread:Support/Support for lad-hebr on Ladino Wikipedia/reply (2)

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. The thread summarization feature is broken, see Phab:T245109. Very old threads have been archived.

First page
First page
Last page
Last page

Question related to problem with message

Hello, I have GrowthExperiments installed on my test wiki. Why is tag shown in message on wiki? This message: MediaWiki:Growthexperiments-homepage-suggestededits-difficulty-filters-article-count/sr-ec is related.

On english version of site everything is fine, so I think that problem is with translation. Is something wrong?

Zoranzoki21 (talk)17:51, 2 April 2020

I don't see anything wrong with the translation. Can you give a screenshot of what you are seeing?

Edit: By tag I assume you mean the strong tags?


Abijeet Patro (talk)16:08, 1 May 2020

It is fixed by another user already. Thanks in each case!

Zoranzoki21 (talk)13:39, 2 May 2020

Update "Translating:MediaWiki/Credits" page

A thread, Thread:Support/Update "Translating:MediaWiki/Credits" page, was moved from here to Translating talk:MediaWiki/Credits. This move was made by Nemo bis (talk | contribs) on 2 May 2020 at 10:50.

Delete my account


Could you please delete my account ?

Thank you

Amaziɣ maziɣ (talk)14:11, 27 April 2020

The platform does not support user deletion. We can change your password, delete your talk page and block your account. Would it be possible to know the reason why you want to do this?

Abijeet Patro (talk)09:11, 1 May 2020

Request Offiline Translator Right

As Translating:Offline suggested, I need offline translator rights to upload translation. However, it does not say whether or not I should request the right before I send my first submission to the email address provided. To not get refused when I send the submission, I think I should request the right beforehand.

VulpesVulpes825 (talk)09:51, 28 April 2020

I've handled the imports and given you offline rights. Do remember to avoid large message groups and do not work offline for extended periods of time. Thanks.

Nike (talk)08:31, 30 April 2020

Understood, and thank you for the import.

VulpesVulpes825 (talk)09:44, 30 April 2020

help when 'Plural' syntax is not accepted

Hi all, concerning following message =>

I think a parameter $1 is missing as for the plurality but it is rejected saying it must be {PLURAL| ...

{{PLURAL:$1|zero=Vous n’avez encore fait aucune rephoto|one=<b>1</b> rephoto|<b>%1$d</b> rephotos}}

I cannot find the correct syntax. I checked it is ok with template => but cannot succeed; help please. Seems as if the original message was wrong (?). Thanks.

ChristianW (talk)12:12, 23 March 2020

As per CLDR data, French has only two plural forms. So the below should be enough,

{{PLURAL|one=<b>1</b> rephoto|<b>%1$d</b> rephotos}}
Abijeet Patro (talk)12:57, 26 March 2020

The source string was just fixed yesterday by Ajapaik developers. The zero version is now a separate message.

Nike (talk)13:03, 26 March 2020

Sounds good now; in french 0 or 1 follow the same way, 2 and over start plural, so according to the number of books on the shelf you say

Il n'y avait aucun livre   sur l'étagère. 
Il   y avait zéro  livre   sur l'étagère.
Il   y avait un    livre   sur l'étagère.
Il   y avait deux  livres  sur l'étagère. 

Thanks; done.

ChristianW (talk)21:04, 26 March 2020

You're lucky in that someone is even willing to listen to you. I've been trying to correct the Portuguese plural for years to no avail, despite the fact that even CLDR agrees with me. The first thing that they usually throw back at you is that you need to convince CLDR. Once you point out that CLDR is already correct and convinced, and agrees with you, and MediaWiki is wrong, they'll push onto you the job of correcting it yourself.

Hamilton Abreu (talk)02:22, 28 March 2020

The "zero" case can be treated specially in French: if you use a number in the translation, treat it as singular only.

But like in English, the message can also use the negation if the number is spelled in a sentence like "Il n'y avait aucun livre" or "il n'y a pas de livre" where sometimes such negative form implies a plural for the noun, depending on the meaning of the noun: "Il n'y a pas de livres" is also correct with the plural, applicable only to enumeratable things, and means "not one and not even more than one").

So the "zero" case may be added optionally to any translation, in addition to the 1st (singular) and 2nd (plural) forms.
This "zero" case should not be used at all if the number is displayed with digits as "0", which must be treated with the singular.

For some sentences where the number is a small integer quantity, you can specialize the translation to spell that number instead of formatting it with digits. This would apply only if the maximum number is small and spelled as a single word (0 treated specially with the "zero" case, or other integers from 1 to 16, or one of 20, 30, 40, 50, 60, 100 and 1000, each using a special case for these values and nàot depending on the default plural rules even if grammatical French rules still apply to these numbers: 1 may be special-cased but the translation should use a singular form for nouns, adjectives and verbs, all other special cases should use the plural form); all other values should be formatted using digits and the standard French plural rules:

  • if abs(n) <= 1 (including n=0.5 or n=0 or n=-1), then use the singular (1st form, used by default)
  • if abs(n) > 1 (including n=1.5 or when n is infinite), then use the plural (2nd form if it's specified, otherwise display the 1st mandatory form)
  • if n is unknown/unspecified, then use the plural (2nd form if it's specified, optional otherwise display the 1st mandatory form) without writing any number

Note that the 2nd form is also optional in French translations, as it may be the same when the form is grammatically invariant in some cases. For example,

  • "1 face" vs. "2 faces" (because the noun "face" has no mute mark of the plural in its singular form, you need a second form to mark the plural)
  • "1 dos" vs. "2 dos" (because the noun "dos" is already terminated by a mute "s" which then remains invariant in the plural)
  • Such cases with invariant grammatical plurals also occur in English (but much more rarely than in French, as English will most often repeat the 's' by inserting an extra non-muted 'e' pronounced as a schwa before this added 's' for its semi-regular forms of plural marks: "1 boss" vs. "2 bosses", but in French the borrowed term boss would remain invariant: "2 boss" because the French term "bosse(s)" is completely unrelated).
  • Invariant grammatical plurals also occurs in almost all languages with abbreviated units of measurement ("1 m" vs. "2 m"), and some translations may prefer using common abbreviations with a single translated form, rather than translating several plural forms: "1 meter" vs. "2 meters" in English, "1 mètre" vs. "2 mètres" in French.
  • Marking the plural in French for terms borrowed from other language is variable and depends on usage: you may use the normal French rules for derivation ("1 pizzaïolo" vs. "2 pizzaïolos", this is generally preferred) or the derivation from the original language ("2 pizzaïoli" from the Italian term, except this is generally not acceptable here as the orthographic term was already modified in French with the diaeresis in the singular, and this singular form should be the base for forming a regular plural), but the choice of marking the singular or plural must still use the French rules ("0 pizzaïolo" : must be singular). Another example (more acceptable): "2 misses" (irregular plural form taken from the English noun "miss(es)" for a woman borrowed as is, but not that we'll still write "0 miss" in French with the singular form chosen, vs. "0 misses" in English with the plural form chosen).

But if you add some other terms in the translation, you may see the difference of plural form in dependant adjectives or verbs that require marking the singluar or plural distinctly:

  • "1 dos courbé" vs. "2 dos courbés" : now you need the two forms in translations
  • "1 dos se courbe" vs. "2 dos se courbent" : now you need the two forms in translations
  • "1 dos à courber" vs. "2 dos à courber" : one form remains sufficient in translations; the verb "courber" is invariant as an infinitive as it has no subject with which to match a number); if you translate the second form, it should be identical to the 1st form intended for singular, also used by default.

If n is a rational fraction, and the full fraction is specified as the explicit numeric values of the numerator and of the denominator (like "⅘") the plural is marked in French only the term for the denominator but then the unit that follows is using the singular form when it is preceded by the preposition "de" according on this fraction: "½ litre" but "10/20 de litre", "¾ de litre". The French rule is:

  • if the absolute denominator is 2, don't use the preposition, but match the plural with the absolute numerator; the French term for the denominator "2" is the adjective "demi-" which is invariant before the noun it qualifies and attached to it by an hyphen: ("demi-" is prefered to the alternate ordinal "2e(s)=deuxième(s)" which is also possible and whose plural varies according to the numerator, but which is almost never used)
    "½ litre" = "1 demi-litre" (= "10/20 de litre" = "10 vingtièmes de litre"): the denominator is 2, so no preposition and then the numerator 1 is singular, so after "demi-", the "litre" will be singular.
    "3/2 litres" = "trois demi-litres": the numerator is 2, so no preposition and then the numerator 3 is plural, so after "demi-", the "litres" will be plural.
  • if the absolute denominator is not 2, use the preposition "de" before the singular noun;
    • the fraction may be spelled using ordinal numbers as nouns for the denominator: "3/12e(s) de litre" or "3 douxièmes de litres" ; when the denominator is spelled, it takes its plural form according to the numerator); The form "3/12e(s)" with an explicit ordinal mark including its own plural mark is needed (either use a suffix preferably in superscript, or use a more compact typographic fraction like "¾" without any suffix and without even any preposition "de" before the noun); the terms for fractional ordinals however are a bit different from rank ordinals, for these two denominators 3 and 4:
      "3s" or "tiers" (numerically invariant) for fractional ordinals, instead of the normal ordinal "3e" or "troisième" only used for (invariant) ranks.
      "4t(s)" or "quart(s)" (numerically variable according to the numerator) for fractional ordinals, instead of the normal ordinal "4e" or "quatrième" only used for (invariant) ranks
    • the fraction may also be spelled using a cardinal number for the denominator and if so the noun after it will follow the denominator: "3/12 litres"="3 sur 12 litres" (plural according to the denominator 12), or better, if you can, the units may be placed before the numerator from which it will match its plural: "3 litres/12"="3 litres sur 12" (plural according to the numerator 3)
    • This means that "¾ de litre" = "3/4ts de litre" = "3 quarts de litre" is correct (litre is singular after "de"), but also "3/4 litres" ("litres" is then plural according to the numerator 3): you cannot use the typographic "¾" and the legacy "3/4" interchangeably. But you can use the typographic "¾ de" and the legacy "3/4 de" interchangeably (with a singular noun).

These rules are almost identical in English (using the preposition "of") which also has specific terms for a few common fractional ordinals (always "half"/"halves", rarely "tier(s)", frequent "quarter(s)") used instead of ordinals for ranks (never "second(s)", most frequent "third(s)", frequent "fourth(s)", ).

However, using rational fractions is still not supported as distinct cases in translations for now, because there's no key for them. They may be used only for specific fractions that are exact as decimal numbers (fractions whose denominator is decomposable in a product of powers of 2 and 5, for which the plural case key would its decimal value as a single non-integer with a limited precision (0.25, 0.5, 0.75, 0.125, etc.); this could work with some translation libraries offering the support for non-integer values of keys n, or offering support for rational keys with the form m/n.

Verdy p (talk)00:28, 28 April 2020

Tajik (Arabic script)

Edited by another user.
Last edit: 14:33, 15 July 2017

Pleas create language Tajik (Arabic script) (tg-Arab) for Arabic scripts in Tajik language.

ToJack (talk)10:15, 15 July 2017

Dear developers that are interested in doing it: Like Chinese, Kazakh, Kurmanci Kurdish, Serbian and others, Tajik is also having LanguageConverter support, although it's incomplete as it can only convert between Cyrillic and Latin. The Meta-Wiki suggests a shareware to convert Tajik Cyrillic to Perso-Arabic script, but since it's not updated for 9 years I doubt if there's users that are still interested in adding tg-arab support to converter.

PS: the ISO 639-3 abh tells me Tajiki Arabic, one of dialects of Central Asian Arabic, I don't know if there's relations between abh and tg-arab

Liuxinyu970226 (talk)11:44, 15 July 2017

No relations between abh and tg-arab. Translations for tg-arab you can add from fa.

ToJack (talk)14:16, 15 July 2017

I edited your original description to make that as not ambiguous

Liuxinyu970226 (talk)14:33, 15 July 2017

Sorry about replying after such a long time. I noticed it only now.

Why is this needed? As far as I know, the Tajik language is written in the Cyrillic alphabet.

Amir E. Aharoni (talk)10:46, 17 April 2020

I'll need a reply to this before I can act. I'm closing this for now. If anyone ever has an explanation of how will Tajik in Arabic script is useful, feel free to reopen.

Amir E. Aharoni (talk)12:07, 25 April 2020

Support for lad-hebr on Ladino Wikipedia

Hi. On behalf of the current Administrators at Ladino (Judeo-Spanish) Wikipedia, we would like to ask a few questions about how explicit support for lad-hebr might work on our project. We don't see being able to ramp up full support for it just yet, and we are certainly not going to be asking to create a separate project for it. However, we have 48 main-space pages (including one variant of our home page), plus a handful of templates and categories, in Hebrew script. We're wondering if some limited support might be available, and perhaps if we can even test fuller support on one or two pages. Here are some preliminary questions:

  • If we currently enter a very small group of translations into the system here, will they work if we call them explicitly? Example: date translations (day of week, conventional month, Hebrew month). Right now, MediaWiki:Monday/lad shows the value "Lunes". The proper value for MediaWiki:Monday/lad-hebr (or whatever that would be named) would be לוניס. Currently, if I call {{#time:l}}, I will get "Lunes". As things are currently configured, if I entered "לוניס" in the right place here on translatewiki, then called {{#time:l||lad-hebr}}, could I get it to return "לוניס"?
  • Similarly, we wondered if we could try to assign the language code "lad-hebr" to the Hebrew-script version of our home page, לה פרימירה אוזֿה, or at least to a copy of it. We would then start with the fallback cascade of lad-hebr>lad>es>en. Slowly, as we added translations to lad-hebr, we could get that page to work properly as lad-hebr, with rtl rendering not dependent on a div block, and so forth.

Are such things possible, or does a more complete commitment to a relatively full interface translation scheme have to come first? StevenJ81 (talk) 18:50, 7 September 2015 (UTC)

And by the way: Why doesn`t Special:SupportedLanguages show Ladino?
StevenJ81 (talk)18:50, 7 September 2015

I'm just curious that why we can't have a Latin-Hebrew converter for Ladino.

Liuxinyu970226 (talk)02:44, 20 July 2016

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/Support for lad-hebr on Ladino Wikipedia/reply (2).


Sorry, forgot about it for some reason. No idea why haven't I done it till now. It's now enabled.

Amir E. Aharoni (talk)12:26, 17 April 2020

Please support "Traditional Mongolian Script"

"Traditional Mongolian Script" ([w:] ) are used in mongolia and Inner Mongolia of China to this day to write Mongolian , which based on this classical vertical script. In Mongolia, the Cyrillic script writing system is used. Until 1990, only elders used to read and write the Mongolian script. But in the 1990s, secondary schools began to intensify the teaching of the Mongolian script.In China, the ethnic Mongol population was nearly 6 million according to a 2010 census. Many of them still receive nine-year compulsory education in Mongolian using the traditional Mongolian script.Mongolians living in Inner Mongolia are not familiar with the Cyrillic script and use the Mongolian script writing system only. They are unable to read Mongolian Wikipedia in Cyrillic. Data: A valid ISO 639-1 or 639-3 language code:mon [1] Unicode range: [2] The language name in English and in its own language: mongolian -ᠮᠤᠨᠭᠭᠤᠯ ᠬᠡᠯᠡ writing-mode: vertical-lr. Now, Internet Explorer, Safari, and Chrome support CSS writing-mode: vertical-lr. Default should still be "mon" in Latin alphabet. Please support "Traditional Mongolian Script".

Batu053235 (talk)00:50, 5 January 2014

I would exclusively oppose mn-Mong, as currently the Traditional Mongolian language is having a test-Wikipedia against at incubator:Wp/mvf.

Liuxinyu970226 (talk)13:15, 27 May 2017
  • One of the reason why the wiki is at mvf because creation of test wiki with codes like mn-Mong are not allowed?
  • Code on TWN do not need to correspond to wiki site code. For example, we have lzh and yue in TWN, while their wikis are now using zh-classical and zh-yue code.
C933103 (talk)22:20, 12 November 2017

I would leave first question for @Nikerabbit:, as the code selection should be judged by him. For the second question, URLs of both wikis are to be renamed, but not soon, technical blocks are listed on phab:T172035.

Liuxinyu970226 (talk)03:50, 13 November 2017

@C933103: The another reason that I oppose mn-Mong is the touchability, as a matching example, the Azerbaijani can be written (commonly) in Latin and Persian (aka Perso-Arabic) scripts, however, due to the tonal incompatible, we enabled both ISO 639-1 az for Latin (the national official language of the Republic of Azerbaijan, which should points ISO 639-3 azj "Northern Azerbaijani") and ISO 639-3 azb for Persian (the regional official language of South Azerbaijan province (?) of Iran, called "Southern Azerbaijani" in SIL website).

Liuxinyu970226 (talk)12:51, 13 November 2017

I believe there are no "incompatibility" between khk Mongolian and mvf Mongolian when writing with the Mongolian script. (Although Russian-originated words and Chinese-originated words will be different).

C933103 (talk)21:46, 15 November 2017

Sorry it took me such a long time. I somehow missed it.

I now added it as mvf.

Amir E. Aharoni (talk)09:11, 17 April 2020

Request for add latin script to persian language


Scripts (ISO 15924)

Arab: فارسی

Latn: Pârsi

Pârsi is Latin-based script that is clear, simple, and consistent. To make reading and writing of the Persian language readily accessible to most users.

Namo (talk)00:05, 25 February 2016

Where is this variant planned to be used? Is there some discussion showing a user demand for this feature?

Nemo (talk)16:46, 18 June 2016

for Mediawiki

I want to use it and install

Namo (talk)19:33, 27 June 2016

I'm cleaning up some old requests assigned to me.

This won't be done, as we only support existing standard orthographies and not new linguistic entities.

Amir E. Aharoni (talk)08:05, 17 April 2020

Special:Interwiki requesting a local link on Extension:Interwiki

Hi all, on special page => , I would like to access the TRANSLATED page of the manual => and not the base page in english ( see related topic => ).

Since I cannot modify the EN string here, my request is for the english text to be modified at =>

from :

This is an overview of the interwiki table, which defines the prefix shortcuts used to quickly link to different wikis and other external sites. For recommended use, please see [// the manual on].

into something as :

This is an overview of the interwiki table, which defines the prefix shortcuts used to quickly link to different wikis and other external sites. For recommended use, please see [[Special:MyLanguage/Extension:Interwiki|the manual on]].

(rather hard coding string "Special:MyLanguage/Extension:Interwiki" - Thanks.

ChristianW (talk) 13:14, 12 April 2020 (UTC)

ChristianW (talk)13:14, 12 April 2020

Thank you for the suggestion. Created a patch Gerrit:588168, pending review.

Raymond20:01, 12 April 2020


ChristianW (talk)22:33, 12 April 2020

A bit incorrect translation I cannot edit

Hi there, I’m working on improving translations in Russian. So I changed an incorrect pattern for all terms, for one from MediaWiki core I cannot do it, my action has been automatically identified as harmful, and therefore disallowed. So the translation of “Main Page” now is “Заглавная страница”, but “Заглавная” means “contains the title”. The translation should be “Главная страница“, it means “Main page”. Could you fix it or allow me to do it? Thanks!

Pacha Tchernof (talk)08:53, 8 April 2020

Hello Pacha Tchernof, sadly I see no chance to change this translation. As this message is not only a translation but also the defintion of the name of main page for all MediaWiki wikis with Russian as content language. Thousands and more wikis would break. Translations into Russian are ery old. The exisiting translation is 14 years old.

Raymond15:31, 8 April 2020

Thanks for your reply, Raymond. What do you think, if I’ll change it, and if it’ll break something, would changing to previous translation fix the problem? What do you think?

Pacha Tchernof (talk)15:36, 8 April 2020

Your suggested change would affect all wikis in Russian language all over the world, not only Wikipedia & sister projects. So I guess nobody could catch all broken wikis in Russian language and suggest/apply a fix.

Raymond18:06, 8 April 2020

Please do not change any more existing legacy translations from MediaWiki core without a discussion. That ends up hurting the wikis you are, supposedly, trying to help, when their messages suddenly become unsynchronised in their wording. (First and foremost, this is something that affects Wikimedia projects, since they get translations a lot earlier than other MediaWiki sites.)

stjn[ru]23:56, 10 April 2020

Request for username change


Could you please change my username for 밝은소년? In addition, please delete my user page first. Thanks.

Tursetic (talk)00:33, 21 March 2020

Done. How about your credited username in l10n files?

Nike (talk)07:03, 30 March 2020

Is that something I can change? (...what means localization files?) If not, I'll very appreciate if u change that :D

밝은소년 (talk)13:32, 8 April 2020

It's done.

Nike (talk)16:41, 9 April 2020

COVID-19's Discontinuation Translations

Hello. I am here to ask a bad news that COVID-19 messages no longer translatable. You can see the reason here.

Baran (talk)09:45, 4 April 2020

Translation updates to GitHub based extensions still working?

I wonder if it is still working since the last updates happend 11 days ago, e.g. my changes to German translation the SimpleBatchUpload extension did not make it to the repo yet. Also the last update for Semantic MediaWiki happened 11 day ago, whereas we usually got two update rounds a week.

If there is something wrong or something to be fixed in repo management to make it work again, please inform accordingly.

[[kgh]] (talk)15:07, 30 March 2020

Maybe... I did a manual run just now and it worked.

Nike (talk)15:12, 2 April 2020

Thanks for looking at it. Affirmative, it is working, at least when triggered manually. Suppose we are cool. :)

[[kgh]] (talk)10:27, 3 April 2020

Context needed

For this message: Wikimedia:Wikiedudashboard-campaign.slug/en

And this one: MediaWiki:Sofa-desc/en. I didn't find any info on that extension elsewhere. Not a single mention on (unless it uses some other name there). "Reporting extension" - reporting what? Like vandalism, or some issues? Or some kind of a status report? Results report? And who is to report: a human user, a bot, or an application? In my language we have different words for those. Please be more precise while creating those English messages (or create /qqq subpages with meaningful explanations), whoever does that. They're giving me a headache.

One more: can someone please tell me why this one (Wikimedia:Wikimedia-grant-review-theme-research/en, "research") is being translated to some languages as "repeat search"?

Another one: MediaWiki:Apihelp-wbcreateclaim-param-tags/en (Change tags to apply to the revision) is being translated as if "change" is a verb, which is incorrect, afaict.

Piramidion (talk)01:22, 1 March 2020
  1. "Slug" is probably something like a "permalink", but we'll ask for a clarification from the developer.
  2. I reported a bug: . Thanks. Don't let this give you a headache! (But it's really great that you are trying to translate all the extensions into your language and to do it well.)
  3. I see a problem with Wikimedia:Wikimedia-grant-review-theme-research only in Russian. This is obviously a mistake (or even vandalism).
  4. I updated the documentation for MediaWiki:Apihelp-wbcreateclaim-param-tags.

Thanks a lot for all the comments!

Amir E. Aharoni (talk)13:03, 30 March 2020

Hi, Sofa was (still is) an extension that was meant as a proof of concept for some crazy ideas I had. I never finished it, i might some day, but its not even working yet, so I'm not sure if there is much point in translating it.

The extension is meant to be used to generate automatically updated user-defined reports (e.g. like Special:AncientPages). Its envisioned as a replacement for DPL extension.

Bawolff (talk)13:20, 30 March 2020

There is this message MediaWiki:Paramvalidator-param-sensitive/en in a recently added "paramvalidator library" message group. The message is empty for some reason, and it displays as if it's been created, but it doesn't have revision history. Is this a bug of some kind?

Piramidion (talk)13:24, 28 March 2020

This has been added to the ignored message list and you should no longer see it in the Translate window.


Abijeet Patro (talk)06:39, 30 March 2020


Please fix the message: Click on$1bellow then read the word aloud. Looks like 2 whitespaces are missing.

Piramidion (talk)22:26, 28 March 2020

Submitted a PR to fix this and a few spelling mistakes -


Abijeet Patro (talk)06:26, 30 March 2020

Dear Interface administrator

Please could the line I just parked in MediaWiki_talk:Feedback-terms/fy be copied as the new message text.

Thank you so much!

PiefPafPier (talk)17:22, 27 March 2020

Already Done Done

PiefPafPier (talk)17:27, 27 March 2020

After some change (to the Rails format, I assume) this message started to display an error, saying that "Plural forms should be defined as {{PLURAL|one=…|few=…|many=…|…}}. This translation contains {{PLURAL|zero=…|one=…|few=…|many=…|…}}." (see here). How am I supposed to translate that message now, if the original message contains a |zero= parameter, while the error insists that the translation shouldn't contain it?

Piramidion (talk)13:10, 22 March 2020

I have messages the upstream that zero should be a separate message. You can leave it out for now.

Nike (talk)13:04, 26 March 2020

OK, thanks!

Piramidion (talk)12:29, 27 March 2020

The message lacks indication of the quantity of files allowed (aside from the one being used for PLURAL), and should look like this: You cannot upload more than $1 {{PLURAL:$1|file|files}} at a time. Correct it, please.

Piramidion (talk)13:03, 19 March 2020

Submitted a PR for this change here -


Abijeet Patro (talk)13:11, 26 March 2020

This is fixed.


Abijeet Patro (talk)14:56, 26 March 2020
First page
First page
Last page
Last page