Support

From translatewiki.net
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

Proposal to change default skin to Timeless

I'm considering changing our default skin to Timeless. My reasons are:

  • Timeless has responsive design which works better on mobile devices (we get quite a few visitors from mobile devices, but not that many users), unlike the Vector skin. E.g. Google search has started penalizing sites which do not work well on mobile.
  • I like Timeless and I have been using it here for a while. Most glitches with Timeless have been fixed by now.

Notes:

  • Manually set skin preferences would not change, and Vector would still be available as a choice.
  • Other option would be to install MobileFrontend extension, but that has not been tested and could break quite a few things.
  • Vector is going through modernization, so it could get better mobile support in the future.
  • Also tracked in phab:T248064

Please let me know what you think.

Nike (talk)11:41, 20 April 2020

Personally I would stick to the Vector skin (thus I'd appreciate installing MobileFrontend and Minerva skin for better mobile support anyway) but I don't see anything against Timeless as the default skin. Do whatever you want.

Rail (my talk | contribs)11:58, 20 April 2020
 

I would like keep using the Vector skin.

Winston Sung (talk)12:25, 20 April 2020
 

The design of the Timeless skin is good, maybe we can add it as an option in user preferences.

Winston Sung (talk)12:26, 20 April 2020

It's already in the preferences, and you can enable it.

Amir E. Aharoni (talk)12:34, 20 April 2020
 

I never used Timeless in a prodction system. So I changed here to Tineless and will try is the next days...

Raymond16:44, 20 April 2020
 

I also use Timeless here for a while; I hardly noticed the site notice about this thread… The font size is the same on Vector as well, but on Timeless it quickly gets covered by the top toolbar as I start scrolling. I think you should use the default font size so that users have a chance to notice it.

On-topic: I’m quite conservative, so even though I personally like Timeless, I’m not sure if the majority of the users do so. Also, the visual similarity to Wikipedia is IMHO more important than search engine optimization—are there users at all who come here from Google? This project is a rather background one, so I expect 99% of the users to come here from the translated projects’ sites (or experienced users using this wiki’s OpenSearch engine, arriving right to the message to translate).

Glitches: I still found three of them on Special:Translate for first sight.

  • “Translate” link in the More toolbox (on the right on wide screens). This is the default tab on Vector, which appears in the place of the Article tab. It’s visually needed on Vector and Monobook, but makes no sense on other ones like Timeless, Modern or Cologne Blue. I’m not sure technically how, but it should not be there on Timeless.
  • Language statistics, Message group statistics and Export. These three links are in the top right corner, all with default icons. This way the icons don’t have much purpose, but it’s particularly annoying on narrow screens, where only the icons appear, so the only way to tell them apart is by analyzing the URL, which is far from being user-friendly. I think this is a release-critical bug in terms of making Timeless default for all (often inexperienced) users.
  • Message documentation on mobile. Because of the narrow screen, the message documentation pane and the translation pane overlaps on mobile. The documentation pane can be collapsed, but only one-by-one for each and every message, while often it doesn’t contain any information. Maybe it could be fixed by switching to a vertical layout on narrow screens. This should only display the message documentation by default, not the translation helpers (other languages, machine translation etc.), again to save space, which could be expanded if needed. Also maybe remembering the state between messages would be helpful.
Tacsipacsi (talk)21:35, 21 April 2020

Thanks for the feedback. Regarding your point about message documentation on mobile, isn't that same problem also present in Vector?

I'll look into the two other glitches.

For translators, you are right. But developers looking for alternatives come via search engines.

Nike (talk)07:48, 24 April 2020

No, the message documentation windows (just like the user boxes mentioned below) have no such issues on mobile with Vector—since Vector is not responsible, mobile browsers use a so-called “virtual viewport” as a self-defense, which is much wider than the actual screen width (see Using the viewport meta tag to control layout on mobile browsers on MDN). This means that the text is maybe unreadably small, but at least the layout is not broken. Of course, this situation is much improved by the introduction of Timeless if Tux is made work well with narrow viewports.

For SEO: I see. This is a tough decision, however, as I still think that keeping consistency with Wikipedia is important, but I agree that letting developers find this site is just as important.

P.S. What about the site notice? Is there a reason not to increase its font size?

Tacsipacsi (talk)13:31, 24 April 2020

Regarding issues 1 and 2 (the navigation tabs), I see no easy way to fix it. I am not skilled enough to make distinct icons for them. I considered moving them elsewhere, but I have no control over where (filed Phab:T251258).

Regarding the 3rd issue, it would fall under Phab:T146134. Unfortunately I don't think I can fix it without re-doing the UI with a more responsive grid system, which is a lot of work.

Nike (talk)14:54, 28 April 2020
 
 
 

I also noticed that my user page looks not-so-perfect on a narrow screen: the Babel boxes become 100% wide if the screen is less than 480px wide, while the other user boxes don’t. I think the best solution for this issue is installing mw:Extension:TemplateStyles and creating a responsive TemplateStyles subpage for {{Userbox}}.

Tacsipacsi (talk)16:47, 23 April 2020
 

+ 1 for Vector. EDIT: I abstain because of "Manually set skin preferences would not change, and Vector would still be available as a choice.", i.e. if you all agree on Timeless ... which should I stand in your way. :)

[[kgh]] (talk)17:45, 23 April 2020
 

I don't like new skin and I think it should not be used as default (neither for new users). One reason is that it is more intuitive for Wikipedia editors to see same appearance here as it is on Wikipedia (Message, Discussion – Read, Edit, View history / More; What links here is moved to the right and was always to the left etc.). Also, Timeless skin is not full width. One thing I like with the proposed skin is that it is more interactive than current standard one (buttons).

Obsuser (talk)16:42, 24 April 2020
 

Good reasons, no objections here.

PiefPafPier (talk)18:11, 24 April 2020
 

I changed my skin to Timeless after seeing the ad.

It's mostly fine, but there are some issues. The most significant is perhaps this: The ULS control for changing the UI language is hidden under the user menu. It's not a thing that people often do once they settle on a language they want, but initially choosing the language for new users may become challenging.

Amir E. Aharoni (talk)05:55, 28 April 2020

Probably language selection should be part of the registration process. This not only overcomes this issue in case Timeless wins, but also, more importantly, makes even more users aware of the possibility to set their interface language. (And don’t be shy to tell all issues you found, so that Timeless will work as seamlessly as possible.)

Tacsipacsi (talk)11:40, 28 April 2020

It already is a part of the registration process, and I notice that a lot of people don't actually do it and stay with English, not just as the language in which they use the site, but also as the only language they know :/

Amir E. Aharoni (talk)15:36, 3 May 2020
 
 

I just use Vector on laptop with extended display for my translations, comparing pages, viewing reference pages and so on , so that I dont really use my tablette for that. Nothing against, till my environment remains available.

ChristianW (talk)15:23, 28 April 2020
 

I like that Timeless is truly responsive, but I really do not like its design. If the skin by default was changed to Timeless, I would switch it back. It might be a good test as to see which pages are responsive or not (and need TemplateStyles / CSS changes), but I feel like that should be mostly a power-user thing.

I also feel like, with its Wikimedia colours being displayed quite prominently in the design, it doesn’t make much sense to use the skin as it is for a project that isn’t, formally, one of Wikimedia projects. But maybe I am reading too much into this and the only effect of the change would be ‘huh, skin is different from Wikipedia/Wiktionary/etc.’, since many people will probably not associate those colours with Wikimedia.

stjn[ru]11:14, 29 April 2020
 

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?

Regards,

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

Hello,

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
 
 

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

It's possible, but not easy. There are several orthographies for Ladino in Latin script, and any converter would have to be able to detect which orthography is being used. (Alternatively, I suppose, any page in lad-latn would have to identify its orthographic system.)

The opposite is much more difficult. The mapping from any given Latin orthography to Hebrew is essentially one-to-one, with the caveat that initial vowels need special handling, and so do certain final consonants. But the mapping from Hebrew orthography even to a single, preferred Latin orthography is not. For example, the same Hebrew-script vowel is used for both i and e, and a different Hebrew-script vowel is used for both o and u.

StevenJ81 (talk)15:57, 29 July 2016
 

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:https://en.wikipedia.org/wiki/Mongolian_script] ) 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

Portal:fa

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 => https://www.mediawiki.org/wiki/Special:Interwiki , I would like to access the TRANSLATED page of the manual => https://www.mediawiki.org/wiki/Extension:Interwiki and not the base page in english ( see related topic => https://www.mediawiki.org/wiki/Topic:Vkd4opajas0koud2 ).

Since I cannot modify the EN string here, my request is for the english text to be modified at => https://translatewiki.net/w/i.php?title=MediaWiki:Interwiki_intro/en&action=edit

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 [//www.mediawiki.org/wiki/Extension:Interwiki the manual on MediaWiki.org].

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 MediaWiki.org]].

(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

thanks.

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

Hi,

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 mediawiki.org (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: https://phabricator.wikimedia.org/T248849 . 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.

Regards,

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

MediaWiki:Mwe-recwiz-studio-info-audio/en

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 - https://github.com/lingua-libre/RecordWizard/pull/5

Regards,

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 - https://github.com/ProfessionalWiki/SimpleBatchUpload/pull/34/files

Regards,

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

This is fixed.

Regards,

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