View source for Thread:Support/Moroccan arabic ISO639-ary/reply

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

Request username change

Rename my account from "A2093064" to "Xiplus". Thanks.

A2093064 (talk)04:32, 28 September 2019

It suggests that you can edit (or delete) layers, but really the corresponding button in VisualEditor's map dialog currently allows editing all geometric features present and there are no layers to edit. A layer in sense of managing geometric features is usually a group of features.

Pikne11:16, 19 December 2016

Tools for counting users' contributions for bbc-latn

Hi Nike, is there any edit count tools in for us to know any/all users' contributions for bbc-latn? Our group in Jakarta has been translating in that language, and we plan to give small prize for some of the most active users. Thanks.

Naval Scene (talk)13:11, 13 May 2013
Edited by another user.
Last edit: 21:59, 28 September 2019

Hello, I think Special:SupportedLanguages is the only way to do that, currently. By creating Portal:Bbc-latn/translators I managed to make the language appear on the page; you should try fetching the usernames from recent changes and/or Category:User bbc, add them to the subpage and see if counts are generated.

Nemo (talk)17:29, 13 May 2013

Naval Scene, I saw you added some names, did you find what you needed?

Nemo (talk)18:01, 26 May 2013

Two of the names are struck through. I have opened a separate thread to get the whole list reviewed.

Lloffiwr (talk)18:20, 1 June 2013

Nemo & Lloffiwr, so sorry I forgot to reply. The May 2013 bbc-latn people/community interest turned out to be just a short one. So we didn't give any prize and will not be doing bbc, until we could find another bbc group that's willing to do this. Thanks.

Naval Scene (talk)09:35, 1 April 2016

Moroccan arabic ISO639-ary

Hello, I speak Moroccan Arabic (Darija), & I noticed big mistakes (not talking about translations) about Darija "Moroccan Arabic" ISO639-ary, I'll propose here some modifications:

  • The Language name in its own language: {الدارجة} instead of {Maġribi}
ref1 see section "Autonym", {الدارجة} read as [ddæɾiʒæ] means common language
  • Writing system & direction (rtl/ltr):
It is writed with Arabic script as it's a member of the macrolanguage Arabic ref1 (section Writing) & ref2, then the writing direction is rtl (right to left), see for example a news website written with darija:
SADIQUI (talk)20:35, 27 September 2019

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/Moroccan arabic ISO639-ary/reply.


A language label

How to modify a language label? for ex: "English", "Kotava", " Patois"

SADIQUI (talk)12:58, 27 September 2019

You mean on Special:Preferences? As far as I know these are determinated by the software and not changeable.


Tobi 406 (talk)20:31, 27 September 2019

For this site only, there are more languages than those currently supported in Mediawiki; as the purpose of thios site is to help develop the translations, including in languages still not in Mediawiki, there's the Template:Languagename that provides local translations (notably when they are still not supported by the "#language:" parser function of Mediawiki which uses a very partial database with many missing data, or approximative data that have not evolved since years and were refined in relevant standards (notably in ISO 639, with most data vetted from The Linguist List and researches indexed in Glottolog, frequently many years before they are vetted in ISO 639, then incoporated to the IANA database for BCP47 and then vetted once a year in CLDR (which is also very incomplete except a for few major languages), and finally integrated in MediaWiki (where there are also various non standard uses kept and not corrected since many years, sometimes decennials).

The Template:Languagename however allows an immediate central change locally for use in portals, languages navboxes, without having to rewrite many pages. It can be discussed here. But note that Wikipedia is not the best source (even its English version) because various distinguised languages are merged. Other possible sources include Wikidata. Both these wikis still want to provide sources. This just attempts to cover the most recommended practices, backed by serious linguistic sources (academic) like Glottolog and The Linguist List, then BCP 47 (for variants and current best practices that preserves the upward compatiblity) then by ISO 639 (for the encoding and English-only names, but ISO 639 still does not have enough coverage, even for modern languages and provides no hints for their classification like the one made in Glottolog, and ISO 639 has not always been not very stable), then CLDR (for translations of language names to other non-English languages or for autonyms), then Wikipedia (English Wikipedia is not always the best source even if it has the widest coverage and it's a very instable source).

Sometimes some existing Wikipedia editions use the wrong codes, still kept for legacy reasons, but do not distinguish them as much as they could (or currently don't have the tools to allow useful distinctions). Here we won't focus on the existing decisions made locally in a single wiki, because is for all wikis, and projects (including those outside Wikimedia itself).

Verdy p (talk)21:16, 27 September 2019

Hi allǃ

This is incorrectly translated. I don't speak the language so I can't reliably translate it but it's definitely not the English "rɛd". The same applies to Wikimedia:Wikipedia-ios-talk-page-discussion-unread-ipa-accessibility-attribute/zh-hant.

Nharateh (talk)14:41, 2 August 2019

Thanks for reporting this. I've marked these two translations as outdated.

Abijeet Patro (talk)08:00, 5 August 2019

Thank you!

Nharateh (talk)14:13, 27 September 2019

iNaturalist Leaving Translatewiki

Hi folks,

We at iNaturalist are extremely grateful for all the translations we've received from Translatewiki over the years, but we would like to stop using Translatewiki for translations as of October 1, 2019. We want to make sure all Translatewiki translators continue to receive attribution, so any advice / requirements on how best to do that would be appreciated. We could make a wiki page in our github repo, or maybe attribute them by name in our README or on our website. In doing so we will also make sure to thank Translatewiki itself for many years worth of translations.

If possible, we would like iNaturalist's presence on Translatewiki to be removed by the above date so translators don't waste their time providing translations that will never be integrated into our code.

If there are any requests or requirements you have regarding the end of our collaboration, please let me know.

Kueda (talk)18:11, 16 September 2019

Thank you for caring about not wasting translators' work. Naturally, we'll do as the project pleases.

However, could you please elaborate on what are the reasons for this decision? I suspect they might be easier to fix than you think.

I see a lot of strange things going on at , probably a result of some misunderstanding. If the things are not going well for iNaturalist, maybe a solution is to try a simpler and more efficient workflow compared to what we had so far. For instance, normally we strongly advise against: 1) pushing outside master, which makes errors more likely and slower to fix; 2) keeping up parallel/competing workflows and translation systems, such as Crowdin and translation changes directly pushed to the repository.

Nemo (talk)12:33, 17 September 2019

Hi Nemo. The two main reasons are the Mediawiki UI and Translatewiki's, well, wiki-esque policies.

Regarding the UI, we on iNat's staff find Translatewiki so frustrating and awkward to use that we hardly ever interact with translators directly and are extremely demotivated to fix things like problems with markup code in translations. We want to have a closer relationship with translators so we can explain things like context, jargon, why markup needs to be copied exactly, etc. I realize this is possible on Mediawiki, but those of on staff find it difficult. Furthermore, a great deal of our growth beyond English-speaking countries gets mitigated by partners in those countries, and those partners tend not to be technically-minded and often have even more frustrations with the Mediawiki UI than we do. I realize Translatewiki could probably fix things like those markup issues (and you have fixed many of them, both through filters and manually, so thanks for that), but it seems unlikely that a) you will abandon Mediawiki for a more usable web application, or b) that Mediawiki will become more generally usable in the near future.

Regarding policy, we really need to allow some people to have privileged approval permissions within specific locales. This is such a deal-breaker for some of our international partners that they simply refuse to use Translatewiki and asked us to stop integrating Translatewiki's contributions for their locale. Given my past inquiry on this topic, I got the impression that this kind of hierarchy is something that Translatewiki is philosophically opposed to. Personally, I understand and to a large extent agree with that stance, but it's proving to be a real hindrance to some of our collaborations.

Since we don't think either of those issues are likely to be resolved any time soon, we're going to move our translation process to Crowdin, which we've been using for our mobile apps for years and, while it has its own set of problems, does not have the problems I described above.

I hope that all makes sense and that my explanation didn't seem overly harsh. Again, we've been very happy with the translations we've received from Translatewiki and I've personally always been impressed with how responsive the Translatewiki developers have been considering it's an all-volunteer open source project.

Kueda (talk)17:42, 17 September 2019

Well, I'm surprised because at I don't see anyone complain about this perceived problem. If people had experienced such big conflicts within their locales, I would expect to see signs of it somewhere. Could it be that some translators just refused to engage because they rejected the wiki way for ideological reasons?

Nemo (talk)19:30, 17 September 2019

It's possible some folks have ideological problems with wikis, but the complaints we've heard offline about assigning proofreaders are more practical, e.g. the ones I tried to describe at,_excluding_locales.

Kueda (talk)19:37, 17 September 2019

I understand, but as I said "our suggestion is to give it a try and avoid overthinking things beforehand". If people were making changes like vs. Usted outside, i.e. without communicating with other translators, that's not a problem with the platform but a social problem. I don't see anything on translating:iNaturalist warning translators to use "Usted", for instance.

Another example: at times your commits resulted in User:FuzzyBot seemingly edit warring with users [1] [2] who appear to have registered just to translate iNaturalist (so iNaturalist translators?). No wonder it was hard for the es-mx locale to coordinate, when translation edits were flying in all directions unexplained.

This social problem of lack of communication can be nudged towards a fix by eliminating the alternative platforms and forcing everyone to translate on Translators would then discover that we offer tools to quickly solve such issues of consistency, like Special:SearchTranslations, as well as effective communication methods like edit summaries, talk pages and so on.

It seems to me that you've not yet really tried to use, so it's no surprise that the results have been unsatisfactory. I would suggest to give it a try for real, for instance with a trial of 3-6 months. If the communication/coordination problems continue to be so pressing, then they can be acted on (as opposed to letting them stew for 18 months or so without any sign to the community of translators).

Nemo (talk)20:05, 17 September 2019

Hi Kueda,

We've run exports from for iNaturalist today, and then removed the project from the list of supported projects. Translators will no longer be able to translate messages on the project, and no exports will be made from to the iNaturalist Github repo.

You can remove the access given to @translatewiki Github account

Best of luck for the future.


Abijeet Patro (talk)14:52, 19 September 2019

[I understand, but as I said "our suggestion is to give it a try and avoid overthinking things beforehand". If people were making changes like Tú vs. Usted outside, i.e. without communicating with other translators, that's not a problem with the platform but a social problem. I don't see anything on translating:iNaturalist warning translators to use "Usted", for instance.]

An issue which is also the case with German and Dutch. I ignored it cause changing it is too much work, although Google translate defaults to using Usted...

Optilete (talk)10:25, 26 September 2019

Delete empty qqq pages

Edited by author.
Last edit: 22:49, 26 September 2019
Tobi 406 (talk)20:50, 18 September 2019

The /qqq pages are intended to provide help to translators, such as listing other resources with similar terms, giving hint about usage (when the English resource alone is ambiguous, such as lack of distinction between nouns and verbs, or the too frequent overuse of Capitalization in English where other languages have more restrictions, based on meaning or usage in sentences). They may convey pointers to check the usage in the application, or with related separately separated resources, or give hints about what will be in replaced placeholders. There may also be warnings, such as terms probably left untranslated (except if needed for transliteration of the Latin script, notably brand names that are still derivable grammatically in some languages; some brands may also have dedicated adaptations for some languages, e.g. "Wikipedia", with the adapted name chosen in a separate process that may need to be documented in qqq pages). So the /qqq pages are not specific to any language, they are usually written in English (sometimes they include some autotranslated templates for generic hints). For some projects, there may exist a terminologic list that should be checked (to help increase the coherency). But they have nothing to do with specific languages like "de"... The "/qqq" pages are helpful and can be recreated at any time even if some hints are removed (because they were temporary). If you are multilingual or can read/understand other languages, check how resources are translated, because you can detect cases that were tested and corrected in other languages and this gives hints about what to do (English alone is ferquently not enough). If there are talks somewhere about terminologic choices, these "/qqq" pages should not be cleared. If a problem was found in a language, and then fixed for that language, it's likely a problem also in other languages and keeping the issue doucmented is helpful. It also provides feedback to developers (even if they often request to post a bug report in a bug tracker like Phabricator or in the Support request pages: post the link to the bug report and its talks and resolution, keep it even if it's resolved). Deleting a page will just make the history invisible, and if it is recreated, the history is lost. An empty page anyway does not cost anything more in the server. otherwise is not a development platform for the supported software to translate. That's the role of "/qqq" pages to post any such reports and hints that will help translators to other languages still lacking proper translation: this avoids long searches and repeated corrections later after testing the result (which will not be used immediately but integrated progressively).

But NEVER use the "/qqq" page for making any actual translation, these are not junk "test' pages, but are like what documentation pages are for templates.

Verdy p (talk)19:11, 20 September 2019

Done Done Deleted all but two where other users have added content in the meantime.

Jon Harald Søby (talk)14:13, 23 September 2019

Protected edit request

Please enter the translation for the following message. I do not have permission to edit it.


मजकूर $1 हाच्या खाला उपलब्ध आसा खेरीज हेर नोंदी केल्या शिवाय.

The Discoverer (talk)16:06, 10 September 2019

Messages in the "Mediawiki:" namespace are not editable except by admins. You have to locate the messages in the translatable space, where they can be vetted and will later be imported into the "Mediawiki:" namespace by authorized bots. Also you use a final dot in the sentence, instead of the danda standard...

Verdy p (talk)16:52, 10 September 2019

In the past I have put requests in the support page for such translations, and admins have entered it for me. For example: here. Nevertheless, please let me know where I can save the message for vetting.

Regarding the final dot, you must be aware that unlike Hindi, in languages like Marathi and Konkani, it is usual to use a dot for the end of a sentence and not a danda. Take a look at some articles in these languages, and you will see that the danda is not used, e.g.:दुसरे_महायुद्धउदक

The Discoverer (talk)05:42, 11 September 2019

Nike or Nemo bis, please could you help save this message? I do not have permissions because it involves CSS/JS/JSON .

The Discoverer (talk)06:00, 18 September 2019

Done, thank you for your contribution.


Abijeet Patro (talk)18:17, 18 September 2019

Thank you :)

The Discoverer (talk)03:27, 19 September 2019

Offline translator rights

Hello. It's still possible to get "Offline translator" group described on Translating:Offline page?

Thank you,

Rail (my talk | contribs)06:42, 7 September 2019

Yes. Can you briefly state what you'd do and why you need to work offline? Thanks for your translations.

Nemo (talk)06:47, 7 September 2019

Sometimes I want to work on my localhost MediaWiki installation to make sure that context of my translations is correct and then submit all of the work in a batch, so offline translator rights would help me do that easier I guess.

Rail (my talk | contribs)06:53, 7 September 2019

There might be a misunderstanding: the offline translating work doesn't let you import messages from another wiki. You need to use a PO editor, so if you translate first on your local wiki you might as well just copy and paste your translations directly into Special:Translate here.

Just to make sure, are you aware of Special:SearchTranslations? That can help you find a string that needs to be translated. So you could do your local testing with the translations which are currently in MediaWiki code, identify the missing translations in their context and then find them here, input your translation into Special:Translate.

Nemo (talk)07:06, 7 September 2019

Hi Rail, did you manage to verify the context for your translations as you desired?

Nemo (talk)20:09, 17 September 2019

Sorry, I forgot to answer to this topic. It looks like I need to create my own tools rather than using offline translations feature. Never mind, thank you ^^

Rail (my talk | contribs)16:07, 18 September 2019

Where to indicate language-specific conventions or preferences?

A thread, Thread:Support/Where to indicate language-specific conventions or preferences?, was moved from here to Translating talk:INaturalist. This move was made by Nemo bis (talk | contribs) on 17 September 2019 at 20:28.

A grammatical doubt

Please refer this link. In that, I would like to know whether the word 'have' needs to be inserted in between the words 'you' and 'registered'. I think without that, there is some sort of grammatical error.

Adithyak1997 (talk)14:48, 12 September 2019

I don't think this blocks translations. But if it is corrected in English, the new version should not be marked to invalidate the existing ones. Overwise we'll just need to reconfirm again the existing translation. Using the preterit and not the compound past seems correct here; it's not gramamtically incorrect, and semantically the preterit is usable with the intent, as the registration in the message is still valid and not terminated (otherwise that message would not apply as one would have to register again a new account).

Verdy p (talk)14:54, 12 September 2019

Change username

I want to change my username to 'Iváns'

Navhy (talk)07:52, 2 September 2019

Done. :-)

Jon Harald Søby (talk)07:28, 4 September 2019

Many thanks

Iváns (talk)14:23, 11 September 2019

Delete account

How do I delete my account? I can't find it anywhere. I want to change the username!

Navhy (talk)07:52, 2 September 2019

You can request your current user name to be changed.

Nike (talk)08:00, 2 September 2019

I want to change my username to 'Iváns'.

Navhy (talk)09:40, 2 September 2019

Done. :-)

Jon Harald Søby (talk)07:27, 4 September 2019

Many thanks

Iváns (talk)14:22, 11 September 2019

Template:Delete and others

I see some people have copied some templates from English Wikipedia here. I am not following this process – all requests should be made here on this Support page.

If someone wants to change the process, I am not opposed, but that should be done properly by adding that to Succession_plan#Translator_liaison, for example, and picking up on that role :)

Nike (talk)08:28, 5 March 2018

Nike, sorry but what are you talking about?

Hamilton Abreu (talk)19:15, 5 March 2018

Which part is unclear? :)

I am just trying to set expectations.

Nike (talk)19:19, 5 March 2018


Hamilton Abreu (talk)14:43, 6 March 2018

Nike, do you mean @Verdy p:?

Liuxinyu970226 (talk)01:02, 8 March 2018

I was not notified, and discover this discussion, but I don't understand why I'm cited, given that I don't even understand what this topic is about, what is the problem, or if there's even any reply expected. The initial topic speaks about "someone" (who?) copying some templates (which? and does it cause some problem?) and about a "process" (without more details to link it with the "Support page"). And finally why Liuxinyu cites me at end ?

Verdy p (talk)01:51, 5 September 2019

Problem about MediaWiki:Mwe-upwiz-tooltip-title and Wikimedia:Commons-android-strings-title info

MediaWiki:Mwe-upwiz-tooltip-title/en and Wikimedia:Commons-android-strings-title info/en say that filenames should contain spaces. That means a filename should contains more than one words on Wikimedia Commons. But written forms of some languages, such as Chinese and Japanese, don't use spaces at all.(Files can be named in any language on Commons. See .) However, the translations in these languages still mention "spaces" ("空格" in Chinese and "空白" in Japanese).

神樂坂秀吉 (talk)14:43, 23 August 2019

The message doesn't say that filenames should contain spaces. It says: "You may use plain language with spaces". This means that you are allowed to use spaces if you want, but you don't have to do it.

Does this help? Or do you think that the English message should be changed?

Amir E. Aharoni (talk)10:07, 4 September 2019

What it means is that you should use plain readable spaces (not URL-encoded as "+" or " " or replaced by underscores) as appropriate for the normal rendering in the target orthography (for some languages, some non-ASCII spaces may be needed, including in Chinese sometimes where it could be an ideographic space, i.e. double-width, or thin spaces, and sometimes non-breaking, or zero-width spaces needed in some South-Asian scripts to separate words and avoid rendering ligatures or clusters, even if that space seems invisible but is still visible by the absence of ligation and a clear separation between the trailing or isolated form of the final letter form of the first word and the leading or isolated form of the 1st letter of the next word). As well, it may be needed to add joiner controls in some Southeastern Asian languages. In summary: use the best accurate orthography without any technical encoding. That message is still useful in Chinese because it may be displayed in the UI language of the translation tool itself, while the translation to provide is in another target language (and China has many languages from many very different families, and written using various scripts, not just Han sinograms and Han typographic rules based on fixed-width cells: even some Sinitic languages may be normally written in Latin, Cyrillic, Arabic, Tibetan scripts, or other Lolo-Burmese and Indo-Aryan scripts in their standard orthography; there are also Semitic languages, Italic languages, Germanic languages, Turkic languages, Korean; each language has its own orthographic behavior, almost all countries are multilingual even if there's a dominant language or a "normative" standard form which is still not universal; and various languages that were considered extinct, are also resurrecting with increased communication between communities spread now worldwide that want to restore their culture, and it's possible to do that now with the Internet, even in absence of support on national or regional medias).

Verdy p (talk)14:10, 4 September 2019

The content of MediaWiki:Permalink/en is the same as the content of MediaWiki:Minerva-page-actions-permalink/en (Permanent link). The Japanese translation of MediaWiki:Minerva-page-actions-permalink/en (MediaWiki:Minerva-page-actions-permalink/ja) is "固定リンク". Why the Japanese translation of MediaWiki:Permalink/en (MediaWiki:Permalink/ja) is "この版への固定リンク" (Permanent link to this revision)?

神樂坂秀吉 (talk)13:24, 23 August 2019

I don't know Japanese and I cannot fully answer this myself.

I can say this, however: It's quite common that messages have the same content in English as other messages, and this is OK. This is useful because quite often they have to be translated differently to other languages, although sometimes they are the same is other languages.

It's up to you and other people who know Japanese and use Wikipedia and other MediaWiki site in Japanese to decide whether they should be the same or different in Japanese. If you are not sure yourself, you should consult with other people who know Japanese. If you decide that they should be the same, just change them.

Amir E. Aharoni (talk)10:04, 4 September 2019

Account deletion

Hello again. It's been about 4 years, and my account has only ever been used shortly after its creation and never afterwards. If possible, I would like the account to be deleted. Thanks.

TheIsraeliSudrian (talk) (talk)13:49, 26 August 2019


I will wait for a day and then delete your account tomorrow.


Abijeet Patro (talk)16:11, 27 August 2019


MediaWiki core does not support account deletion. Even if we do block you, or remove you from the translator group, your contributions will remain.

It would be good to know what your motivations are for wanting this account to be deleted.

If there is no specific reason other than to get rid of an unused account, I'd say we remove you from the translator group and leave the account as is.


Abijeet Patro (talk)09:05, 4 September 2019

LibreMesh typo? 'software' or 'softwrae'

A Chinese Wikipedian (talk)02:32, 7 December 2018

Thanks for reporting this. I've created an issue on their issue tracker -


Abijeet Patro (talk)08:17, 4 September 2019
First page
First page
Last page
Last page