Recommended Addon

[markh]

I suppose I never really learned how to use babelzilla properly, but:

I upload our XPIs, which contain the translations. In order for things not to break because XML entities are not defined, I include english strings in the XPI where they're not provided. What am I supposed to do different?

You only need to include those strings in the en-US locale. The WTS will spot the new strings and display them as such in every locale that is already existing, similar to all empty in newly registered locales. If a translator finishes his/her work, (s)he will download the locale files and repack the xpi for testing, so there should not be any non-existing entities in that particular locale anymore.

[Lakrits]

Hi,

To avoid confusion, we closed the old Greasemonkey thread. It's still there to read, but you can't post in it.

Admin

[Lakrits]

barryoni managed to post in the old thread just before I closed it. The message was:

Hebrew (he-IL) translation has been updated and released.

Thanks for the translation, barryoni!

Lakrits

[Lakrits]

There are some duplicate translations for Greasemonkey. Some of the language-region codes (e.g. ru-RU) are no longer needed, since those locales have been replaced by two-character codes for language only. If you like, I or any of the other admins can delete those extra and obsolete locales for you here at BabelZilla. They are

Czech cs-CZ
Finnish fi-FI
Italian it-IT
Russian ru-RU
Turkish tr-TR
Ukrainian uk-UA

Other locales (e.g. Romanian and Estonian) have changed codes, but still have the obsolete lang-reg codes in Greasemonkey. They should be renamed.

An up-to-date list of the locales Mozilla uses, incl. those that still uses the lang-reg format (e.g. Swedish sv-SE), can be found at the Mozilla Web localization Dashboard.

/Lakrits

[arantius]

There are some duplicate translations for Greasemonkey. Some of the language-region codes (e.g. ru-RU) are no longer needed, since those locales have been replaced by two-character codes for language only. If you like, I or any of the other admins can delete those extra and obsolete locales for you here at BabelZilla. They are

Czech cs-CZ
Finnish fi-FI
Italian it-IT
Russian ru-RU
Turkish tr-TR

Sure delete them, if they shouldn't be used. I'll be sure to remove them on our side too.

[pmi]

Romanian locale updated and released using the language code ro.

Locale ro-RO is now obsolete.

[arantius]

Other locales (e.g. Romanian and Estonian) have changed codes, but still have the obsolete lang-reg codes in Greasemonkey. They should be renamed.

What exactly should be removed? ro-RO, replaced by ro? That seems done babelzilla side. Estonian is et? et-EE still seems to exist babelzilla side.

[Lakrits]

What exactly should be removed? ro-RO, replaced by ro? That seems done babelzilla side. Estonian is et? et-EE still seems to exist babelzilla side.

What I mean is that Mozilla is undergoing an update of the locales they use for Firefox, Thunderbird etc. There is a list at Mozilla Web localization Dashboard (http://l10n.mozilla-community.org/webdashboard) with all the locales they currently use. We try to keep the locales at BabelZilla updated, but sometimes there are "old" translations left.

You may use as many locales/translations as you like, but it often unnecessary to have two locales for e.g. Swedish or Polish, while big languages, e.g. Spanish or English, may still need separate locales for different regions.

Ask your translators to review the "old" locales and decide if duplicates should be merged or if we at BabelZilla simply could delete the obsolete locale (upon your request of course). If there are two parallel translator teams, they could cooperate instead of producing duplicate translations. In the meantime the old locales will still work in Mozilla programs, but it's difficult to know if support for old locale names will continue. That's why I suggested that you can look at the list (see the link above) and rename the folders and references if necessary.

[markh]

@translators: please be aware that there is a new version up with some new strings. It was probably uploaded as a minor update, so you did not get a notification and the status has not been reset.
@arantius: I have removed a couple of obsolete locales (a.o. it-IT, ru-RU, tr-TR)

[gymka]

got email about update, everything is translated, so which strings are changed? i don't have time to compare old translation with new... if nothing big is changed so don't send notification email.

[markh]

got email about update, everything is translated, so which strings are changed? i don't have time to compare old translation with new... if nothing big is changed so don't send notification email.

I found several untranslated strings in a couple of files, mainly around the automatic updates.

[gymka]

compared version from AMO(1.0) and this version which is in babelzilla, both has same strings, there is no differences between them(en-US)... even md5sums are identical.

stone to babelzilla garden(i don't know equivalent for this proverb in english): why developer or translator should worry about which strings changed? i translate in a lot of different platforms, everythere platform marks strings which are changed compared to previous versions. even if project don't use translation paltform, it uses normal format and translator can simply run few commands and he will see differences.

[markh]

compared version from AMO(1.0) and this version which is in babelzilla, both has same strings, there is no differences between them(en-US)... even md5sums are identical.

stone to babelzilla garden(i don't know equivalent for this proverb in english): why developer or translator should worry about which strings changed? i translate in a lot of different platforms, everythere platform marks strings which are changed compared to previous versions. even if project don't use translation paltform, it uses normal format and translator can simply run few commands and he will see differences.

Yes, we are aware of that. The yet-to-be-finished new version of the WTS should have that possibility too.

[arantius]

got email about update, everything is translated, so which strings are changed? i don't have time to compare old translation with new...

Sorry, there are a handful of complete, but mostly still incomplete translations. I purposely didn't send mail last time (but some people noticed and competed it anyway); I was just uploading a development version here because the easiest way for me to make beta builds is download all possible strings, with English substitutions, from babelzilla. And I didn't yet want to bug translators for beta builds that might still change.


Separately: https://github.com/greasemonkey/greasemonkey/issues/1616

The es-CL translation is broken because of (I think) improper utf-8 encoding in the file I download from Babelzilla. Are the files I download always supposed to be utf-8? Is there a known bug in babelzilla?

[Lakrits]

The es-CL translation is broken because of (I think) improper utf-8 encoding in the file I download from Babelzilla. Are the files I download always supposed to be utf-8? Is there a known bug in babelzilla?

Hi,

All the files for es-CL are encoded in UTF-8, but I found a faulty character (probably from a failed conversion ANSI --> UTF-8). I fixed that. Try it and see if it still breaks the program.
I didn't find any missing quotations or other code errors. There are three instances of acute lower-case "i" characters ( í ) in one of the DTD's and one instance of a reversed question mark ( ¿ ) in a PROPERTIES file. If the locale keeps breaking the program, replace the í's with HTML/XML entities in the DTD and use the Unicode entity for ¿ in the PROPERTIES file.

Lakrits

I also fixed a small error in the sv-SE (Swedish) translation.

[Haebaru]

Hi,
I am a Japanese translator.
Unable to register now Greasemonkey translators.
Please add me! Greasemonkey to a Japanese translator.

[Lakrits]

Hi,
I am a Japanese translator.
Unable to register now Greasemonkey translators.
Please add me! Greasemonkey to a Japanese translator.

The translation was locked for some reason. I just unlocked it. Try again.

Lakrits

[Haebaru]

The translation was locked for some reason. I just unlocked it. Try again.

Lakrits

Thanks!

[Lakrits]

Thanks!

As the English say (or should say if they spoke Japanese with English grammar and wording):

どういたしまして、私の親愛なる

Lakrits-san