View source for Thread:Support/A language label/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. Very old threads have been archived.
(The thread summarization feature is broken, see: Phab:T245109)


Thread titleRepliesLast modified courses/fr022:33, 20 October 2019
[critical bug] MediaWiki:Withoutinterwiki-legend/fr : translation mixups: updates are going to the wrong page422:21, 15 October 2019
typo in Wikimedia:Whowrotethat-tour-welcome-description/en : "the the"217:12, 15 October 2019
[bug] Translate UI - wrong placement of circled accelerator keys220:33, 14 October 2019
An Error in, 10 October 2019
Deleting unused strings from translated language files515:13, 9 October 2019
Mobile version of main page112:59, 9 October 2019
Saving the translation failed121:22, 5 October 2019
Request username change111:38, 1 October 2019
MediaWiki:Leafletdraw-edit-toolbar-buttons-edit/en017:47, 30 September 2019
Tools for counting users' contributions for bbc-latn421:59, 28 September 2019
Moroccan arabic ISO639-ary121:16, 27 September 2019
A language label221:16, 27 September 2019
About Wikimedia:Wikipedia-ios-talk-page-discussion-read-ipa-accessibility-attribute/zh-hant and Wikimedia:Wikipedia-ios-talk-page-discussion-unread-ipa-accessibility-attribute/zh-hant214:13, 27 September 2019
iNaturalist Leaving Translatewiki910:29, 27 September 2019
Delete empty qqq pages222:49, 26 September 2019
User name change User:Ece Alpdeniz --> User:AliceJ016:37, 20 September 2019
Protected edit request503:27, 19 September 2019
Offline translator rights516:07, 18 September 2019
Where to indicate language-specific conventions or preferences?020:28, 17 September 2019
First page
First page
Last page
Last page

This message cannot be correct in French: the adjective must be "actives" after "campagnes" (feminine), but "actifs" after "cours" (masculine).

The English source incorrectly assumes that adjectives are invariant. And the grammatical gender of nouns (like the replaced curse type) is variable depending on each language, do not assume they are simple to predict as this also depends on the choice of translated termes (ex. if instead of "cours", which is masculine with invariant number, we chose the synonym "leçon" or "leçons" in plural, which would then be feminine.

Note that even the plural, marked by the final "s" in adjectives "actifs" or "actives", may become singular depending on the number of campaigns or curses displayed. But as well don't assume that plurals are always fomed using a final "s". If needed pass a number parameter to allow us to use. As there's no number parameter, the unknown number is assumed to be plural (for most frequent cases except initially for a very new program or campaign which is still incomplete if it's limited to only one short course of about half an hour to complete or a single wiki page to read or review).

Please split this message in two versions, one per type, don't use such patchwork. And its not simple to find another way to translate a <adjective+noun> phrase (note also that the order is swapped to <noun+adjective> in French and other languages).

Verdy p (talk)22:24, 20 October 2019

[critical bug] MediaWiki:Withoutinterwiki-legend/fr : translation mixups: updates are going to the wrong page

Translations are sent to the wrong page. Trying to set them correctly, the submission is accepted, but when we refresh the page, we still see an unrelated message, not for this resource, and no change is applied (and no error ever displayed).

And if we look deeper, we see that what was submitted has in fact changed another page, creating a mixup, which then affects multiple other pages.

Very probably problem of index corruption (page or version ID's) in the database (I think there are duplicate ID's in some tables that should be unique), or a previous bad use by some prvilege admin of native SQL update.

As well the histories are mixed up across pages.

A maintenance should be performed to check the database integrity (notably check all table indexes).

It is also likely a problem of the background job queue, which seems to be stalled (recent changes are not fed correctly, statistics are out of sync, page counts are wrong...)n or its backlog of pending jobs is too large, or there's a lack of storage on the server.

Verdy p (talk)14:08, 10 October 2019

I just opened the page MediaWiki:Withoutinterwiki-legend/fr and it really shows the unrelated text, but clicking on "Edit" shows the text correctly.

Vlad5250 (talk)14:51, 12 October 2019

This was a real bug ( and is what is referenced by the site notice at top. It was affecting stince the beginning of month. The bug was a caching bug on the server. Still it affects some resources displaying incorrect "fuzzy" state (yellow icon) which seem to reoccur again. The issue was real and very strange. Its resolution is partial, as some other glitches are still occuring; the resolution seems to be non definitive because the impact is still not well understood. That's why the site notice at top remains.

Verdy p (talk)10:02, 13 October 2019

Quite certain that these issues started appearing since our deployment last Wednesday (8th Oct, 2019). We should not be seeing this issue on twn any more, but if you do, please ping on the Phab ticket or here.


Abijeet Patro (talk)06:22, 14 October 2019

Actually this started around September 24-26: many edits made after that date (or even reviews) were affected. And this continues even if caches were tentatively purged.

See for example with a new incorrect edit saved based on the wrong unrelated message:

As long as the new patch for disabling the use of Memcached (by Fuzzybot and other background jobs, including bots exporting data or importing data from external sources) is not applied here (it is still being tested by Mediawiki developers, hoping to find the effective origin of this bug), we still see those bad data. It seems that there's a design bug in how multiple APIs are working together across multiple services, multiple hosts, and in very different security contexts.

The dates of 24-26 September does not match the 8 October deployment. Something occured earlier that had unexpected impact. For now there's no clear isolation of the bug, and there are propably multiple levels of unchecked assumptions between the various components, maintained separately but with a sequencing of events that may have changed and were not supposed to be out of sync or occuring in different orders, because they were not covered by any existing unit tests.

However the bug seems related to a probable bug in internal memory management in PHP for "function closures" (a very tricky piece of code in PHP). The PHP engine effectively used may also have an effect (for example Wikimedia is currently actively working on coming back to PHP7 instead of HHVM, and the past switch from PHP/Zend to HHVM had already caused similar problems some years ago, because PHP is still not defined with very strict semantics). As well there are strange bugs in Memcached itself (still using unsafe assumptions about memory allocation made by C compilers, plus the effects of some deployed mitigations in processor firmwares, used to solve 90% of problems while also adding their own few % of problems).

Thanks Wikimedia works in improving the unitary tests and give more powers to linters to detect false assumptions. But there are tons of compiler/linter warnings to check now: some early solutions to detect them can cause some parts of the software to be simplified, changing the behavior that was previously just "unspecified" but worked as expected. Ideally MediaWiki should be tested by running it on very different architectures and OSes. This is not really the case, but it would help detect more unspecified behaviors and isolate more bugs, while enforcing better software quality by improved portability. However Mediawiki is highly develkoped now in terms of pure performance on the existing and very costly Wikimedia architecture.

But the bug T235188 is now proven to affect also Wikimedia wikis (including Commons, Meta-Wiki and Wikidata, but also some Wikipedias that use the translate extension for some local project pages or for running some tools or because they need to support pages with several orthographies when automatic transliterators are not reliable enough).

Verdy p (talk)22:21, 15 October 2019

duplicate word in Wikimedia:Whowrotethat-tour-welcome-description/en : "Activate the the tool from the sidebar. ..."

Verdy p (talk)17:02, 14 October 2019

I have submitted a pull request to fix this.

Jon Harald Søby (talk)12:16, 15 October 2019

The pull request has been merged now, so it will appear here next time the source messages are imported.

Jon Harald Søby (talk)17:12, 15 October 2019

[bug] Translate UI - wrong placement of circled accelerator keys

Translate UI- wrong placement of circled accelerator keys.png

Accelerator keys in circles displayed in the Translation UI are incorrectly placed. They should not collide with the editable text area where they obscure the text being edited. Ideally they should be placed just below the bottom of their border box, with enough margins, and not above the top border.

And the surrounding circles (actually boxes with large paddings and rounded corners) are too large, given they are also completely opaque: there's no need to have so large paddings.

Finally they should probably be visible only if the input focus is inside the text area, and probably only when we hold the [Alt] or [Super] key (depending on the browser's UI for its platform) to use them by pressing the displayed key (one digit or letter). Without this focus (flashing caret or current text selection) in the editable text area, the accelerator keys should have no effect and should then not be displayed at all. In fact most users will prefer clicking (or tapping on a tactile screen) the suggestion boxes to insert their suggested text into the text area at its current input position.

Now if you zoom in/out with the browser their placement is even worse. They are in fact absolutely positioned in the window instead of being relatively positioned, and their computed absolute position is completely wrong.

Verdy p (talk)01:53, 9 October 2019

They are only visible when one presses ALT. Sometimes they get stuck if we don't key keup event (such as when ALT+Tabbing to another window), but pressing ALT again will make them go away.

Nike (talk)12:55, 9 October 2019

No, they are permanently on screen... Pressing ALT or releasing it does not change the display. This was probably displayed on just a few browsers, but does not work in Google Chrome (the most widely used browser in the world) in Windows (though I don't think this behavior is just tied to Windows).

I found that the bug occurs sometimes after pressing ALT+TAB to switch to another application in Windows, and then returning to Chrome, also with ALT+TAB or with a click. The release event for ALT key is no longer detected, even when pressing and releasing ALT again, or it has no effect for objects already in the interface. Note that there are still multiple warnings displayed in the Developer console, including deprecated interfaces in several component libraries, related to jQuery unsafe/deprecated APIs ,or APIs in Mediawiki itself when they hook some event handlers; may be the same handler has been registered twice or registered in a "lazy" way, possibly the ALT release event is registered too late and not bound correctly in all closures, or this does not work with international keyboards (if the Alt key is confused with AltGr; it may also be incorrect detection of Chrome for Mac keyboards when we use Windows).

I've not seen such issues in other websites using jQuery, where we can safely use common Windows accelerators like ALT+TAB to switch between multiple open windows. And I have a very minimalist number of browser extensions (I have even disabled several extensions preinstalled by Google in Chrome for Windows, and not allowed Microsoft to install its own extensions into Chrome).

There's no such issue if I use Edge Beta (Chromium-based), which is using dramatically less memory than Chrome and is more power-efficient, and loads faster, I'm about to switch to Edge Beta if Microsoft ever releases it instead of its current home-brewed Edge which is an horror breaking many sites.

And anyway the fact that their position is very wrong and is even worse with browser zooming (where circles are going to higher positions when the text and boxes are shifted down when the zoom lever is larger) is a sign that jQuery or similar APIs are wrong, or make unsafe assumption.

Verdy p (talk)13:22, 9 October 2019

An Error in

When I am trying to translate that in Turkish, the error gives...

Failed to save translation: This action has been automatically identified as harmful, and therefore disallowed. If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: Protect sensitive pages #2

Are you guys going to fix it?

BaRaN6161 TURK (talk)09:20, 10 October 2019

Thanks for reporting. This abusefilter rule is only a workaround. The actual solution is to mark this message as "ignored", because it does not need to be translated.

Nemo (talk)10:08, 10 October 2019


BaRaN6161 TURK (talk)10:55, 10 October 2019

Deleting unused strings from translated language files

Hi guys,

I'm posting this here since you don't seem to be responding to @translatewiki mentions in GitHub pull requests...

The question is, is it OK to directly modify foreign language files (translated and committed by translatewiki) ? Would that have an impact or cause problems, and if so, what ?

Specifically, this relates to the following commits in the above-mentioned PR:


-- Damien10:08, 27 September 2019

If you delete the English strings (the source strings), the next export will take care of deleting the translations as well. As for changing translations, it's better to do it here on, because then the translators can see what you're doing and why.

Nemo (talk)10:27, 27 September 2019

Thanks for your reply.

Please note that the actual translations have not been modified at all. Changes to foreign language files are :

  • removed unused strings ==> From your reply, I understand is that by deleting the string myself, I'm only anticipating on what would do anyway, so that should not cause any issue. Is that right ?
  • moving strings around in the file (without changing anything) ==> I assume this has no impact, can you confirm ? (note, this was done to have consistent ordering of strings across all language files)
  • renaming a language string (i.e. not the translation itself, but the string's identifier) ==> this is the one I'm really not sure about. I would think yes based on what the FAQ says, but since it also mentions informing the staff...
-- Damien07:28, 3 October 2019

Hi Damien,

  • removed unused strings --> This should be fine but would recommend doing it only for the source language and not the foreign language files.
  • moving strings around in the file --> Again no issues here and should be fine.
  • renaming a language string --> This is also fine. Thanks for the ping regarding this. We will review and do the necessary renaming on our end, which is quite easy.


Abijeet Patro (talk)07:42, 7 October 2019

Hello Abijeet,

FYI the pull request has been merged a few minutes ago, feel free to do your magic at your next convenience.

Cheers, Damien

-- Damien08:32, 9 October 2019

Hi Damien,

This is done. Translatwiki now has and tracks the renamed language keys.


Abijeet Patro (talk)15:13, 9 October 2019

Mobile version of main page

I would like to know to set-up a mobile version of the main page on Currently it shows the whole main page, but I would like it to only display certain paragraphs. Any help would be very much appreciated (main page).

Servien (talk)23:53, 5 October 2019

I am afraid this is not the right place to ask for such help. Hopefully someone will post a reply pointing you to the right direction, as I don't know whether his is related to Mobile Frontend or something that can be done in the wiki itself.

Nike (talk)12:59, 9 October 2019

Saving the translation failed

I was trying to modify two pages content but I was prevented:

  1. MediaWiki:Mainpage/ary from {صفحة لولا} to {الصفحة الرئيسية}; I was prevented for the fllowing reason: Established main page translations cannot be changed directly as it would disrupt wikis using the old translation.
  2. the outdated translation of MediaWiki:Copyright/ary because I don't have the Permissions for editing of sitewide CSS/JS/JSON files.

What can I do to fix the above translations?

SADIQUI (talk)21:38, 4 October 2019
  1. You can't modify MediaWiki:Mainpage/ary because AbuseFilter 3 prevents edits from you, simply request changes on here (like you already did, so just wait until someone with the needed rights does this)
  2. Similar to above, simply wait until someone with the needed rights does your request action.
Tobi 406 (talk)21:22, 5 October 2019

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

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

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

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/A language label/reply (2).


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.
First page
First page
Last page
Last page