Some time ago I created qqq pages (switched namespace to qqq and started translating without going back to de), that are now empty (I cleared them).
As I think having empty pages is not good in general, I'm asking for the deletion of these pages.
The pages are:
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. Translatewiki.net 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.
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.
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 https://github.com/inaturalist/inaturalist/commits/master/config/locales , 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.
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.
Well, I'm surprised because at https://forum.inaturalist.org/t/translators-what-do-you-like-dislike-about-crowdin-and-translatewiki/3108 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?
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 https://translatewiki.net/wiki/Thread:Support/designated_proofreaders,_excluding_locales.
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 translatewiki.net, 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   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 translatewiki.net. 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 translatewiki.net, 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).
We've run exports from Translatewiki.net 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 Translatewiki.net to the iNaturalist Github repo.
You can remove the access given to @translatewiki Github account
Best of luck for the future.
Please enter the translation for the following message. I do not have permission to edit it.
मजकूर $1 हाच्या खाला उपलब्ध आसा खेरीज हेर नोंदी केल्या शिवाय.
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...
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.:
Hello. It's still possible to get "Offline translator" group described on Translating:Offline page?
Yes. Can you briefly state what you'd do and why you need to work offline? Thanks for your translations.
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.
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.
Hi Rail, did you manage to verify the context for your translations as you desired?
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.
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).
How do I delete my account? I can't find it anywhere. I want to change the username!
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 :)
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 ?
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 https://commons.wikimedia.org/wiki/Commons:Language_policy .) However, the translations in these languages still mention "spaces" ("空格" in Chinese and "空白" in Japanese).
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?
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).
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)?
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.
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.
I will wait for a day and then delete your account tomorrow.
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.
LibreMesh:limedocs-01-1804cc-10b)=0AA NODE is composed of an/en, is softwrae should be software?
EOL:Devise-devise.failure.locked/en Is it spell error and it should be "again"?
during the last few dates I noticed that on the page Special:ContributionScores for my User for Last 7 days (Top 50) the number of contributions is marked as following:
Rank Score Pages Changes Username
49 9 9 9 Robby
while on  you may see that I made at least 50 edits on 31 August till 2nd September.
So there seems to be something broken on this.
49 or 50 edits, this is not a huge difference, and the statistics are not counted immediately; your last few edits were probably made after the statistic batch was run (so it counted only 49). Look at the statistics after 24 hours, you should see evolve it (but the count may still be off by the edits you made in the last few hours after the batch ran). Verdy p (talk) 23:35, 1 September 2019 (UTC)
I've the same problem since the last days of August. I'm on 27th overall ranking but my changes are stopped on 38201 (and the scores is stopped too). May be there's a bug?
You are mistakken 49 is the rank not the number of changes or pages these were 9 and there is quite some difference between 9 and over 50.
OK, but your actual statistics is not 50 but over 70,000. Still my comment remains valid: the statistics are not computed all the time continuously but with batches running periodically, so it's normal that it can ignore your most recent edits over the last shortest period. As well, the results depend on the activity of the job queue (which is very active on this wiki even if there's few edits, as the longest jobs are those created for SemanticWiki, some of them running for hours may lock temporarily not just some pages but also the updates of related statistics (which will be deferred). These statistics are not intended to be actualized in real time, they are just estimates. Computing them has a huge cost on the server, so they cannot be refreshed instantly, even if this is based on a live SQL request (which is already costly and quite long to reply for this page, because it has to lookup all existing users to sort them and then extract about 50 of them in each "top list"; the statistics however are quite accurate for least frequent users, but must frequent users are only roughly sorted, especially for the shortest period of 7 days). Note also that the computed statistics do not show the actual period of dates on which they were computed: the period may be off by more time than what you expect, and the "last 7 days" may be 7 days before the last run of statistics offline jobs which may have occured up to 7 days ago (possibly more of the database had long job lists, with some jobs taking several days to complete and deferring other pending Statistics jobs to run that, most probably, have lower priority than Semantic jobs and regular jobs built in MediaWiki).
This statistics page is not certainly the one to consult if you want to get your own personal edit statistics, that you can get using the live Mediawiki API:
For example: https://translatewiki.net/w/api.php?action=query&list=users&usprop=editcount&ususers=Robby
The same for Joe Taras: https://translatewiki.net/w/api.php?action=query&list=users&usprop=editcount&ususers=Joetaras (note: you must use the actual username, like in your user page, not the displayed username in your signature, and URL-encode it if needed in the URL) This gives a total on all periods. Computing this over a period is much more complex as it requires scanning your history, so this cannot be done directly with the live API. Doing that on all existing users (just to get the Top 50 lists) is even more complicate and costly.
I am trying to translate Fandom (aka Wikia). when I have translated them, are the systems going to add it automatically?
We do not have any Wikia specific translations here anymore. For generic MediaWiki and extension translations, my understanding is that it can take a while (multiple years) for them to appear there. They seem to still be using MediaWiki 1.19.24 from 2015.
Hello, Could someone please come and help add this to translatewiki. The bot should have access. Thanks,
These translations don't use IPA:
- Wikimedia:Wikipedia-ios-talk-page-discussion-unread-ipa-accessibility-attribute/ja (Latin transcription)
- Wikimedia:Wikipedia-ios-talk-page-discussion-read-ipa-accessibility-attribute/ja (Latin transcription)
These translations are IPA pronunciations of English words: