Support

show archives

Problems? Questions? Suggestions? Write your message below. – See also the FAQ or try to catch us in IRC.

Your request has been forgotten? It's suggested to use {{Support}} in thread summaries, see also documentation.

Not sure if it's the translatewiki's fault (scanned the Translate extension commit history but found nothing), but since the new statistics tables are implemented, the Cantonese (yue) has disappeared from the message group statistics but not from the language statistics. Also, Cantonese is since then missing from the UniversalLanguageSelector. And in Special:Translations, the label "Cantonese" is now replaced by "yue". This has really caused some inconvenience.

It's not related to the statistics table. Can you confirm it is fixed now?

Yes, it appears to be fixed now.

Some untranslated messages of kjp are now showing in bo (Tibet). The fallback language of kjp should be Burmese (my). Please check.

I am unable to save the translation for MediaWiki:Copyright/gom-latn because of the following error:

Saving the translation failed: You do not have permission to edit this JavaScript page because it may affect all visitors. Permissions for editing of sitewide CSS/JS/JSON files were recently separated from the "editinterface" right. If you do not understand why you are getting this error, see mw:MediaWiki_1.32/interface-admin.

If you would like to save it yourself, the translation for this message is:

Mozkur $1 hachea khala uplobdh asa kheriz her nondi kelea xivai.

I saved it for you.

Thanks! :)

OPEN This issue is open, waiting for action

Hi, we're curious about whether TranslateWiki might be a good home for the translation of a project we're working on, the LibreRouter. We want to translate software interfaces, documentation, and also an illustrated booklet about how to use the LibreRouter. There's more info about the project at https://librerouter.org/.

The code is in the repositories at https://github.com/libremesh, and is in English. All the software is in active development or pre-development. One of the apps in active development that's already giving attention to translation is https://github.com/libremesh/lime-app.

The source language for the HowTo booklets is Spanish. The text for those booklets isn't ready to translate yet, though we hope to have first drafts ready no later than mid-October.

Some people from our community would join the translation effort, especially for English, Spanish, Portuguese, and maybe German and Afrikaans.

We've tried the interface for translating software strings on TranslateWiki, and we like it. We're not sure if the format of the HowTo booklets is compatible with TranslateWiki, since those are long paragraphs of text. We tested on Zanata, and it worked with .ODT files.

If we need to use a different file format for the code i18n/l10n or for the booklets, we're open to that.

We're interested in TranslateWiki because of the community of translators already active here, and the long-term continuity of the TranslateWiki platform and community.

Does this look like a good match, LibreRouter with TranslateWiki? What would be necessary or desirable actions from the LibreRouter community in order to move forward? We're available to chat on IRC or via e-mail or here on this thread.

Hi TranslateWiki team,

I wonder how to get in touch with you so that we can figure out whether LibreRouter can join TranslateWiki. I don't see any email address to write to, and the IRC webchat isn't working at the moment (and I don't usually spend any time on IRC). I will respond here to the items listed on the New Project criteria page, and hopefully this will make it clearer whether LibreRouter can join TranslateWiki.

- Openness: yes, LibreMesh software and documentation use free and open source licenses, such as GPLv3.

- Development: yes, LibreMesh is in active development, using a Git repository for version control. The project has periodic releases of LibreMesh, and will have periodic releases of other software and documentation (which has't yet reached first release). Time to get translations into use is currently unknown, and depends on how often network maintainers update the firmware on their router (perhaps we could automate part of this process to make TIU faster, or have a translation-only auto-update so as not to deal with potential software bugs and version incomatibilities between routers on a network), and how often users update Lime-App on their phones. More discussion could be helpful.

- Integration: It seems very reasonable that TranslateWiki staff could have direct push commit access.

- i18n Support: two key parts of the LibreRouter system support i18n already (LibreMesh GUI and Lime-App), though I do not know if they support the details of i18n mentioned on the TranslateWiki New Project page. I have passed the Localization for Developers link to developers and they're looking at it.

- Communication: I am the current liason, and I am not active in development. I have communication with the developers, and it's feasible that one of the developers may takeover the liason role and/or at least one developer might be active in translatewiki.net. I am a user and tester of the software and documentation.

- File formats: yes, we use translation files, I don't know if they're in one of TranslateWiki's preferred formats. Here's a translation file for Lime-App https://github.com/libremesh/lime-app/blob/master/i18n/translations/es.json , and I'll find one for LibreMesh.

We need to start translating this month, October 2017.

What else do you need to know in order to decide whether LibreRouter can join TranslateWiki?

cheers, Pato

The JSON format looks okay except we don't include the language code as a key in the file (it's already there in the filename). Would you consider changing that format?

Is the repository in GitHub your main repository?

I would request to add some message documentation to guide the translators (see https://www.mediawiki.org/wiki/Localisation#Message_documentation).

Does taking the language code as a key out of the file just mean removing the line   "es": { As well as the closing bracket } ?

Yes, the repository in GitHub is our main repository.

We will add some message documentation to guide the translators based on the advice at https://www.mediawiki.org/wiki/Localisation#Message_documentation. It might take us a week or so to start adding that documentation.

Yeah if the file looks like following, then we support the format.

{
  "key": "value",
  ...
}

I'm talking with coders... we're moving forward on changes to be more compatible with TranslateWiki, and we're coming up with questions about TranslateWiki:

1) We're looking at 4-7 different pieces of software to translate. Each piece has it's own practices of what branch development happens in, so we're getting all that info in one place. Arranging direct push commit access for TranslateWiki to the development branch of each software is part of our conversations.

2) If one or two pieces of software are ready to connect with TW.net before the others, can we go ahead and connect those? If yes, how?

3) Can the TW.net platform translate the Readme.md file for each software? Or maybe we'll have to setup a separate help folder with a file in each language, like at https://github.com/LonamiWebs/Stringlate/tree/master/help -- would that work? Is there a TW.net parser-generator for MarkDown .md files?

4) Is there a smartphone interface for TW.net, either via a web browser or a special app? (It seems that using a computer with a keyboard and at least a 10-inch screen is easier for translating, but sometimes a smartphone is the only device available to a translator.)

5) How do we include screenshots in the translator notes (the qqq messages)?

1) Are those pieces in different git repositories?

2) Yes we can. I need the basic info about the repository, push access, file format.

3) We do not have MarkDown parser at the moment. It could work as translatable page.

4) Amir is working on a Telegram app. There is also unmaintained android app. The web interface should accommodate tablets pretty well, but mobile phones are not well supported.

5) Uploading them here in translatewiki.net and using the wikitext syntax to include them. Can also put direct links to images, if they are too large, but then translators have to click.

1) Yes, each piece in a different repo.

2) The first two pieces that I think are ready:

• LibreMesh Web UI
  • https://github.com/libremesh/lime-packages/tree/develop/packages/lime-webui
  • format: Gettext
  • branch: not yet decided. Development usually happens in a new branch for each feature or fix, and then gets merged with "develop". Here's a conversation going on now about commit access for you/TW.net, wondering what branch to give you commit access to: https://github.com/libremesh/lime-packages/pull/254

• LiMeApp
  • https://github.com/libremesh/lime-app
  • format: JSON
  • branch: "uhttp" until December-ish, then "develop".

3) "It could work as translatable page." Do you mean it could work without a parser?

4) Cool! I hope Amir and crew get that Telegram app to a usable release.

5) Where in TranslateWiki would we upload the screenshots? When you say "too large", what are the maximum dimensions of the image (like 80px by 200px)? What is the maximum file size?

6) Where is the code for the parser-generators that are currently in use on TW.net? We'd like to look at them to get a sense of what it would take to write another.

7) Any suggestions on how to internationalize this relatively simple web page interface, https://github.com/libremesh/chef ?

6) https://github.com/wikimedia/mediawiki-extensions-Translate/tree/master/ffs and docs in https://www.mediawiki.org/wiki/Help:Extension:Translate/File_format_support (likely somewhat outdated).

7) Maybe https://github.com/wikimedia/jquery.i18n ?

6) Thanks, we'll look at those.

7) The maintainer of the software to internationalize (Chef) says: "I'm currently not using jQuery in Chef but plain JavaScript. I'd rather keep it that way - if possible. Some quick searches resulted in https://github.com/eligrey/l10n.js/ - maybe thats already enough?"

Also, what are the howto booklets you mention in the subject? Our primary focus is on software user interfaces. [edit] We don't currently support ODT files. Some kind string extraction to another format would be needed. Are the booklets created so that they can be automatically generated from the translated texts (i.e. no hardcoded positionings with length restrictions)?

The HowTo booklets are a series of guides about the social, technical, and economic aspects of how to create and maintain a community network, with the LibreRouter as the example hardware and software. The idea is that each booklet will be laid out by hand after translating. This means that an automated workflow (as is used in software) is not our plan for the first three languages, and we would join TranslateWiki.net only for the software interfaces.

However, if anyone can suggest a workflow to create the booklets that aligns with the way TranslateWiki.net functions, we're interested to try it out since that could facilitate the translation of the booklets into many more languages. Perhaps the ODT parser from the Zanata translation management platform could be included in TranslateWiki.net, or perhaps we could use a different format. Or perhaps a bit of the BookType software used to create the books at Flossmanuals.net could be reused.

I haven't done that before. I am sure there are string extraction plugins for ODT. The problem is that usually booklets have quite tight positioning and size constraints. Doing the layout manually for many dozens of languages (and dealing with possibly frequent updates) doesn't scale. But a flexible or simple ODT file we could probably support if there is a suitable parser-generator we can integrate.

Hi Nike, any chance you can setup the repo for LibreMesh document translation this week? Following the thread at https://github.com/libremesh/lime-packages/issues/257#issuecomment-423850005

This has been continued in chat discussions.

Hi, can you give me back offline translator right, so I no need each time to use bot for it?

Too, give me translation administrator right so I can manage translations. Thanks!

@Metalhead64:

 Done

For translation administrator, please contact a staff member.

Thanks!

I can't publish translation due the error.

See:

Is that normal? It's a translation, not a Javascript page or something…

A handful of messages (5) are not currently editable. This is one of them. If this doesn't resolve itself over time, I will lift the restriction.

Someone has translated some messages on #Babel to the Musi language. However, the translations do not seem to appear on the Babelbox in Incubator nor in Meta. Any idea? Thank you in advance.

Please see FAQ#How_is_the_work_done_on_translatewiki.net_connected_to_other_wikis?. The translations were made today.

In addition LocalisationUpdate is currently not running, so translation updates get deployed to the sites only once per week.

OPEN This issue is open, waiting for action by Nike

Please have a look.

We can no longer force it with "&action=purge" either, it just does nothing. I believe someone managed to force a purge yesterday (I got the "refreshing stats" message when viewing the stats) and since then it neither refreshes nor allows a purge.

Likely https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Translate/+/468319

I saw timeouts on our logs, so likely I should move that to the JobQueue.

Anyway, we should hunt down why it's not updating as it should.

Virtually, we can not see the messages that need to be translated. Does this mean that we must retire temporarily?

Your message sounds impolite. I hope that was not your intention.

I have cherry-picked by untested fix and purged all statistics. Give some time for them to repopulate. Let me know if you see further issues of stats not updating.

I do not mean any abuse. I mean it's because we need to update stats automatically.Thanks for responding

The problem returned quickly

Which problem? Can you give a specific example and/or steps to reproduce?

OPEN This issue is open, waiting for action by Jon Harald Søby

Please enable translation to the Malay (Arabic) language (the Arabic script variant of Malay language, which is also known as Jawi alphabet) because I want to start translating in the language with that particular script.

The Arabic script variant is still in use in Brunei (where it is co-official with Latin script), Malaysia (where all Islamic education textbooks for primary and secondary public schools are exclusively taught in Malay with Arabic script instead of the Latin script, and where certain states make it mandatory to put roadname signs in both scripts), Indonesia (in Malay-majority areas such as Riau and Jambi) and southern Thailand (in Malay-majority areas, such as Pattani).

Basic information:

• ISO code: ms-Arab (using BCP 47 format of langcode-Scriptcode)
• Language name: Malay
• Language self-name: بهاس ملايو
• Script: Arabic
• Direction: RTL
• Fallback to: Malay (ms)

Additional information:

1. Jawi alphabet on Wikipedia
2. ms_Arab is written in CLDR Supplemental Data XML
3. Malay (zlm) on Ethnologue, "Arabic script, Naskh variant [Arab]" is mentioned
4. Malay, Standard (zsm) on Ethnologue, "Arabic script, Naskh variant [Arab]" is mentioned
5. Malay (macrolanguage) written with Arabic script, Naskh variant is on ScriptSource under three codes, ms-Arab-MY, ms-Arab-CC, ms-Arab-ID
6. Malay (individual language) written with Arabic script, Naskh variant is on ScriptSource under code, zlm-Arab-MY
7. Universal Declaration of Human Rights in Malay (Arabic) on Unicode UDHR

I'm also requesting in advance, the right to translate in this script variant after it's added. Malay (Arabic) is the exact same language as Malay, just in different scripts. Hence, I'll be converting (manually) from existing Malay translations into Malay (Arabic) instead of doing another English -> Malay (Arabic) translations. If a translation is not in Malay yet, I'll translate them into Malay before converting them to Malay (Arabic).

Seems like a reasonable request, so I've created a pull request on GitHub to have this added to language-data, which is the first of four steps to have it added here. I'll keep you updated. :-)

Thank you. I'll keep waiting for it. :)

--MNH48 (talk) 15:42, 29 October 2018 (UTC)

If one searches "colocar" in Special:SearchTranslations, then selects only the "portuguese" and "MediaWiki" occurrences, the fifth entry in the list reads:

Colocar uma ligação "Upload file" ao lado desta entrada
MediaWiki:Sf forminputs uploadable/pt

However, the word "ligação" was changed to "hiperligação" back in December 2017. Is there some way to fully refresh regularly whatever data store this search engine is searching against?

There is but it will make the index unusable for quite a few hours, so I don't do it often.

There's a bug that really often sorts out the Italian word "partorisca" (subjunctive tense of the verb we use for "giving birth", technical), always without a real reason to do it. I can't retrieve what it is connected to, it seems to come out mostly for "per" (for), but not only. I don't know where in the process it was inserted, but it seems it was (perhaps for trolling purposes since the effect is quite ennoying).

Do you know which source language it is coming from?

I'm translating from English to Italian, I presume it should be an Italian dictionary; I've seen, indeed, that there is some interference with Spanish (upside down beginning question marks - not used in Italian); but it should be an Italian tool...

PS: decidedly it's an Italian tool derived from a Spanish one:

English	Apertium suggestion
You can have more than one reading list so that you categorize the pages in your list.	Partorisca categorizar le pagine, puoi creare più di un elenco.
	"categorizar" is Spanish - "Partorisca" has nothing to do with the text

I assume is no English to Italian support in Apertium, so it is likely that it is showing a translation from some other language like Spanish.

well, if it's so, it's nice to see that the result is fairly sufficient - apart from this invasion of childbirths... :-)

Do you think we should need to tell them something or it would be useless until they set up an Italian tool?

You can check what's inside the current Apertium pair to see where the word comes from: http://wiki.apertium.org/wiki/Contributing_to_an_existing_pair

OPEN This issue is open, waiting for action

What's with the checks that are preventing the message Wikimedia:Wikipedia-library-ae475f-=7B=7BPLURAL:GETTEXT=7CContact=7CConta/en from being translated? I get the error message "The following parameter is unknown: {{PLURAL:GETTEXT|Contacto|Contactos}". Isn't the message supposed to be translated?

Hi, I no have this problem. Can you check again?

It continues.

To check it yourself, click Wikimedia:Wikipedia-library-ae475f-=7B=7BPLURAL:GETTEXT=7CContact=7CConta/pt and click "Edit". It will show:

!!FUZZY!!{{PLURAL:GETTEXT|Contacto|Contactos}}

This is the translated message, with "Contact/s" translated to Portuguese. The message is fuzzied because of the error reported. Now, remove the "!!FUZZY!!" and save it. Edit it again and the "!!FUZZY!!" is still there, meaning that the problem continues.

Now look at all existing translations. All those that have been translated are coloured pink, meaning they have a problem. For those that are not coloured pink, most were initially translated to the target language, got the same error and then people put them in English to get rid of the error. The only exception is /fi, which was inserted by the bot already translated.

So, the problem most obviously exists! When you state that you do not have this problem, EXACTLY WHAT LANGUAGE DID YOU TRANSLATE THE MESSAGE TO SUCCESSFULLY without the problem? There is no successful translation of this message made by you.

Hello, I'm originally User:Vinhtantran. Every time I logged in, the website became blank and unusable regardless of different browsers. I believe it was because of the custom monobook.js in the User:Vinhtantran/monobook.js. As a solution, I had to create this username to gain access to translatewiki.net and hereby request a deletion of that js page from an admin. If you want to confirm the connection between these accounts, please don't hesitate to contact me via my Talk page. Thank you.

 Done

CLOSED This issue is closed by Jayprakash12345

double 'a' in "Seta a default directory for storage of compiled templates" (MediaWiki:Widgets-config-compiledir) has been signalled as -> https://phabricator.wikimedia.org/T206747 (... not found the possibility to add a comment to the ENglish text to inform translators that a request has been emitted with its reference number).
Json correction is : "widgets-config-compiledir": "Set a default directory for storage of compiled templates"

Seems to be fixed by Jayprakash12345.

CLOSED This issue is closed by siebrand

Could we get español nicaragüense enabled here? It's a very different dialect from español españa or español mexicano, which are probably the dialects being used here.

• lang code: es-ni
• Localized names:
  • English: Either "Nicaraguan Spanish" or "Spanish (Nicaragua)"
  • Native: Either "español nicaragüense" or "español (Nicaragua)"

We use "español (Nicaragua)" on my mainstay wiki, but it depends on what the standard is here.

• left to right, like the Spanish we have here right now
• It should fall back to es, or if available and possible, Uruguayan Spanish, or other Central American dialects that exist.

I'm willing to translate messages to this language.

Xbony told me to bump this, so I'm bumping this.

At the moment there is only one variant of Spanish. https://en.wikipedia.org/wiki/Spanish_dialects_and_varieties doesn't seem to explain the difference very well or whether there is a standard orthography for this dialect. Can you clarify?

The main difference is the use of voseo rather than tuteo (you can read about both on Wikipedia if you are unfamiliar with these verb forms). We also don't really use the word tú ever. You can read more about Nicaraguan Spanish at wikipedia https://en.wikipedia.org/wiki/Nicaraguan_Spanish

The code was added.

I have removed the code, as it has been unused for over a year. Please let us know if you are still interested in having it, in which case we can add it back (please clarify for which projects, MediaWiki?).

OPEN This issue is open, waiting for action

HI, I could know what is missing for you to change on "translatewiki.net" the name of the language "Kreyol Gwiyanè" in "Kriyòl Gwiyannen " ???

Because it will be months that I ask and yet I still have no concrete answer !

"Kreyol Gwiyanè" is the name of the language mix with French + Creole, NOT the original Creole. In the original creole it is written "Kriyòl Gwiyannen", click on the link you will see, but please, change the name of the language !

Hi, I am a contributor of the project, I could know when you will change the name of the language, because it is really needed for the activation of the project of Guianan Wikipedia, and besides we are missing that, so this would be nice if you do it as soon as possible, thanks !

Hi! İ tried to edit the Babel template for Serbian-1 in order to improve the translation, İ made the change in sr-ec and sr-el pages, but if the page MediaWiki:Babel-1/sr isn’t also changed, the text on the template when İ add Serbian to the template remains unchanged. For example, on my userpage, the old text is still there. İ can’t edit that page since iťs locked. İf İ only change the sr-ec version as indicated, the Babel template for Serbian remains unchanged. Could you do something about it, please? Thanks in advance!

It doesn't need updating. It doesn't even exist: https://translatewiki.net/wiki/MediaWiki:Babel-1/sr?action=history

Then, why on my userpage and in other inclusions of this template on Wikipedia still appears the old text (Овај корисник разуме српски / srpski језик на основном нивоу.)? Can you tell me where should İ also update the template in order to see the changes done?

The issue has been resolved, in Translatewiki has been updated (the text of this page is the updated version). For the other wikis that use this template, Nike told me that iťs is necessary to wait for it to be updated. Also, İ made a little change in sr-ec and sr-el, please use this new version when you update the template.

CLOSED This issue is closed by Metalhead64

Hi, can I request a username change to (شريف), please? Thank you.

 Done

Please move Translations:Group descriptions/pywikipedia/* to Translations:Group descriptions/pywikibot/* and update corresponding groups/Pywikibot/Pywikibot.yaml file in TWN Gerrit. Thank you!

We have an issue. For some reason, we now have translations at both skr and skr-arab.

Maybe this is an oversight in our language code validation changes, but this needs to be cleaned up now. Any suggestions?

 Good work. Thanks . for diabling one language.one of these is sufficient.
Saraiki (talk) 12:47, 4 October 2018 (UTC)

All skr translations have been moved to skr-arab if page didn't exist yet. Other translations have been deleted, but most of the time they were the same anyway, so I hope there isn't a great loss here. No new translations to skr can be done.

Exported translations have been deleted.

thanksSaraiki (talk) 12:58, 4 October 2018 (UTC)