Support

Problems? 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)

User:ArticleEditor404 made a ton of low quality translations in yue and also a couple in ja. The majority of the yue translations by them are worth nuking.

Their translations in other languages should be checked as well, as they appears to have used a (rather low-quality) machine translation service.

Why I cannot translate pages for sr-ec or bs? It is 'View source' ('Извор', 'Izvorni kôd')...

Hello. The current option is no longer used. Wikibooks, Wikisource, Wikipedia, Wiktionary, Wikiquote.

Ana Səhifə —→ Ana səhifə

Hello,

Today I noticed that in MantisBT we have an unhandled language file 'strings_skr-arab.txt'. According to ISO 639, this is Saraiki language.

Looking for it here, I found 2 entries for it

• https://translatewiki.net/wiki/Special:ActiveLanguages/skr-arab
• https://translatewiki.net/wiki/Special:ActiveLanguages/skr

Following the 2nd link gives an error message: Sorry, the servers are overloaded at the moment. Too many users are trying to view this resource. Please wait a while before you try to access this resource again.

A user recently submitted translations for new Hindi language on MantisBT project.

Changes were committed to MantisBT repo https://github.com/mantisbt/mantisbt/commit/fd621be14f5a78af382f23d5be91ac3b777cb70d but the file strings_hi.txt is not following the naming convention, so the translations are not picked up by the Lang API.

File should be called strings_hindi.txt

Can you please fix that ?

Please update https://mantisbt.org/bugs/view.php?id=28648 when done, thank you.

Done and done.

Thanks !

There is a problem with MediaWiki:Wsu-js-batchtable-status/en. If $2 is zero, extra "." appears in the resulting text like this: "99% complete. .". I suggest joining "." into the inner text like {{PLURAL:$2|0=|$2 failed.}}.

Thanks. Fixed upstream. Will be reflect here soon.

If I update translation file using gtranslate and create an update PO file, will it be accepted for translatewiki? Is there any criteria for offline translation approval?

Please read the guide at https://www.mediawiki.org/wiki/Help:Extension:Translate/Off-line_translation. Then submit a link to your translated po file here. After one successful submission, you will be given the rights to use Special:ImportTranslations yourself.

I'm trying to understand review workflow. I started translation of a project (http://translatewiki.net/wiki/Special:Translate/out-mantis-core) which has multiple subprojects. In one case, the translations is parked for review (where I cannot act). In another case, I was able to review and act. Does this workflow depend on individual project settings? If yes, who is the the person to approach for reviewer role?

What do you mean by "parked for review"? Was the translation not committed upstream at MantisBT?

When I see the status it shows "100% translated, 0% reviewed". At another translation platform (transifex) there may be two different roles for translator and reviewer. I read the documentation and could not find if translatewiki also has two different roles for translator and reviewer.

As regards commit, overall translation level is still below min expected percentage (MantisBT page says 40%) in main project, so I'll continue to translate and verify the results once I achieve that level.

There is only one role here, which allows both to review and translate. You cannot review your own translations though, only translations from others.

There is currently no review threshold for exports, the threshold only checks translation completion percentage.

That's what appeared to me when I started. Since some of work have progressed and reflected in commits to respective projects, I've full visibility of the process.

Thanks for help and clarification.

Our IRC channel has moved from Freenode to Libera Chat and is now called #translatewiki instead of #mediawiki-i18n. There is also #translatewiki-rc that relays recent changes feed. If you are using IRC, please join our new channel.

If you come across old references, please update them to the new channel, or let me know so I can do it. You can help by updating outdated translations for pages Project:About and Translating:New project.

I would also like to ask whether you are interested in translatewiki branded cloaks on Libera Chat? If so, I am wondering whether we should have flat cloaks like translatewiki/username or role-based like translatewiki/translator/username, translatewiki/staff/username.

Wuu has two writing systems. At this time, most of the messages are written in simplified Chinese characters, I wish to enable two new variants: wuu-hans "吴语（简体）" and wuu-hant "吳語（繁體）", and fallback to wuu when they are unavailable.

Moment.js doesn't have a Chechen (ce) time format support and falls back to Russian, so Notifications are in an incorrect time format.

I am not sure if this can be fixed here. Better to report it upstream: https://github.com/moment/moment/issues

Posted by reference

There was a problem with Growthexperiments-help-panel-question-subject-template-with-title ("Help panel question on $1"). If $1 is "Category:something" it will be sometihing like [1] ("หมวดหมู่" is alia for Category) and add page to category. I would suggest to add ":" to escape category magic like [[$1]] → [[:$1]]

Thank you for the report. I have submitted patch Gerrit:693604, waiting for review now.

Above patch was approved and will go live this or next week.

Thank a lots :-)

In group list about Tarandine localization, I see (since last March) some groups with not update percentage, but when I try to fix the messages I've NO MESSAGE TO UPDATE

Please fix this error

It's very difficult work with you! A simple request to clean the summary abour group messages becomes an impossible things. This language has one of more translated but os not right by you don't care about it.

Hi Joe,

All those skins have optional messages that are translated but have become outdated and need to be translated again.

Eg: https://translatewiki.net/w/i.php?title=Special:Translate&group=mediawiki-skin-cologneblue&language=roa-tara&filter=%21translated&action=translate&optional=1

Also see: https://phabricator.wikimedia.org/T159122 and https://phabricator.wikimedia.org/T41068 to understand why optional but translated messages count towards the group statistics.

Here's how you can access optional messages:

Regards,

Thank you dear. I've no checked the opzional messages. Have a nice day ;)

I am the developer and project contact of Cita. The translation project began a couple weeks ago and it's been translated to multiple languages already. That's so cool! Before having the project on translatewiki, I took care of Spanish translations, which is my native language. Development of Cita continues and there usually are new messages or message changes. I would like to be able to change the Spanish translations directly at the source code when corresponding changes are made to the English strings. Otherwise, I have to wait until changes are pulled by translatewiki, then translate to Spanish online, and then wait again until translatewiki sends a pull request. Would this be possible? Something similar happens with message documentation (qqq). When a new message key is added, it would be easier to immediately add the corresponding message documentation, rather than waiting until changes are available at translatewiki (chances to forget are so high). Thank you very much for your support!

Hi Diegodlh, adding new/updated translations together with new/updated messages is OK.

But for changes of translations unrelated to patches I kindly ask you to do this in translatewiki. Otherwise the import process could get out of sync.

Thanks, Raymond! I'm planning to do this only occasionally and mostly for new messages, sure. Thanks!

Hi there,

We're working to address a longstanding issue that precluded some of our content from being translatable via translatewiki. We've now moved the last of that content into json files, with the pattern: `locale/<locale_code>/tag_names.json` example: https://github.com/WikipediaLibrary/TWLight/blob/master/locale/en/tag_names.json

We'd love to have these picked up as translatable strings.

Thanks!

Tracked under: https://phabricator.wikimedia.org/T282768

Regards,

This concerns an issue saving a Dutch translation for the following message:

Osm:Issues.show.reports/en
Display:
{{PLURAL|zero=No reports|one=1 report|%{count} reports}}

Osm:Issues.show.reports/nl
Display:
{{PLURAL|zero=Geen rapporten|%{count} rapporten}}

Editor -this should be the most recent text according to the History page-:
{{PLURAL | zero = Geen rapporten | één = 1 rapport |%{count} rapporten}}

My attempt which did not get saved and would not return an error message when published -only an empty page-:
{{PLURAL|zero=Geen rapporten|one=1 rapport|%{count} rapporten}}

There is also an issue previewing a topic on this Support page; it sends you to a different page and as such returns "this topic does not exist". This does not happen with previewing translation edits in the wiki editor.

Just below the orange notice there is a word 'papamientu'. I'm not sure what a papamientu is, but could it be that the word 'papiamentu' is misspelled here?

Hello! I usually contribute in another project, such as Wikipedia. I don't really understand about technical stuffs in translatewiki. So, I found an abuser's (AJBot2) contributing here, he's already global locked there. I want to make block request for him but i dunno how and where. His translations are mostly nonsense. Anyone can help me for this case? Thanks for the help!

Hi ANukuma,

Thanks for bringing this to our notice.

I've left a comment on their talk page: https://translatewiki.net/wiki/Thread:User_talk:AJBot2/Poor,_unnecessary_and_unwanted_contributions

I will check back their contributions again after 7-10 days to see if anything has improved.

Regards,

Thank you so much for your help! Cheers.