Recommended Addon

[Alf]

Dutch locale updated, tested and set as released.
Please note: locale 'nl-NL' has changed to 'nl'. Please change chrome.manifest and/or install.rdf file(s)!

[saster]

Dutch locale updated, tested and set as released.
Please note: locale 'nl-NL' has changed to 'nl'. Please change chrome.manifest and/or install.rdf file(s)!

OK, I'll change to nl.

[Fux]

German (de) locale updated, tested and set as released. I converted de-DE to de.

[saster]

German (de) locale updated, tested and set as released. I converted de-DE to de.

I've just uploaded it to AMO as 0.9.8.16 .
See you all later...
Attila

[saster]

Hi there!

still alive and kicking

Attila

[Olding200]

Hi, i did the Danish translation with the new additions, but when i test the extension it gives me an error. When i click on the Mozilla Internet Dictionary in my tools menu it gives me this error:

XML tolkningsfejl: udefineret entitet adresse: chrome://mid/content/mid.xul linje 340, kolonne 7: <label value="&history.toolbar.label;"/>
------^

I can translate it to english, but i don't think it's necessary. I can see it's one of the new strings, so i guess theres some small error there.

Just wanted to let you know.

[saster]

XML tolkningsfejl: udefineret entitet adresse: chrome://mid/content/mid.xul linje 340, kolonne 7: <label value="&history.toolbar.label;"/>
------^

I can translate it to english, but i don't think it's necessary. I can see it's one of the new strings, so i guess theres some small error there.

Just wanted to let you know.

Yes, i understand the error message :-(
Thank you for reporting it.

Regards
Attila

[saster]

Yes, i understand the error message :-(
Thank you for reporting it.
Regards
Attila

I've downloaded the da-DK locale, tested, and it seems good at me. I attach it.
Attila

Attached File(s)

 mid.xpi ( 191.31K ) Number of downloads: 1

 

[Lakrits]

Swedish locale (sv-SE) added and released.

[ZuGro]

Hi

@Attila:

Please check "choose_dict.xul" (line 58):

CODE

accesskey="&label.select.dictionary.types;" />

Must be:

CODE

accesskey="&key.select.dictionary.types;" />

And, where are shown the followin entities?:
"dialog.apply.temporarily" (Apply temporarily)
"dialog.save.dictionaryset" (Save)
"dialog.save.as.dictionaryset" (Save as...)

There are extra buttons like for "dialog.save.as.default" entity?

Also, what's suppose to doing the "Widescreen mode" option?, I'm checking and un-checking that option, but nothing happens...
Please forgive this, opening the navigation panel i can see what's happening (in Widescreen mode the navigation panel is displayed sibe by side with the dictionaries, instead of above or below), that's nice!

Finally, i guess when select "New dictionary group", a confirmation window must be shown, in order to display the "db.newsession.cleardictionaries" (Do you want to remove the current dictionary tabs and define a new dictionary group?) from "mid.properties file, but it is not showed, it is clearing all my tabs and showing the dictionary settings window directly, without asking.

(OMG, I hope you can understand my very bad spanglish) :(

Best regards.

[ZuGro]

Hi again...

Spanish [es-ES] is ready, updated and released...

Greetings.

[saster]

Hi,

Hi
@Attila:
Please check "choose_dict.xul" (line 58):

CODE

accesskey="&label.select.dictionary.types;" />

Must be:

CODE

accesskey="&key.select.dictionary.types;" />

thank you, I'll check it

And, where are shown the followin entities?:
"dialog.apply.temporarily" (Apply temporarily)
"dialog.save.dictionaryset" (Save)
"dialog.save.as.dictionaryset" (Save as...)

There are extra buttons like for "dialog.save.as.default" entity?

These strings became obsolete, I'm going to remove them, thanks again.

Finally, i guess when select "New dictionary group", a confirmation window must be shown, in order to display the "db.newsession.cleardictionaries" (Do you want to remove the current dictionary tabs and define a new dictionary group?) from "mid.properties file, but it is not showed, it is clearing all my tabs and showing the dictionary settings window directly, without asking.

You may be right here, too. Thank you very much for your tests and help!

This version is feature complete but I'm still testing it, there might be other smaller issues.

Attila

[Lakrits]

Hi, saster

You don't have to pre-fill any English (en-US) text in the locale files for this add-on
before you upload language files with new strings. The reason is that any non-en-US
locale file updated with English text, and then uploaded to BabelZilla, will look like it is
100 % translated if you fill in the new strings beforehand (Image 1), and we (the translators)
must search through all the text to find the new strings. That is not so difficult when
the locale files are short and few, but e.g. new/changed hot-keys, access keys and
abbreviated strings are harder to find.

The only files you have to update before you upload a new version of your add-on are
the en-US locale files. If you do that, BabelZilla will automatically insert the new strings
into the other locales' language files, with the English string text as the translation
source text. That will also make the new strings red and easy to find in the translation
editor interface (Image 2). If you want all locale files to include all strings, even if some
are untranslated, you can download the locale files with the missing/untranslated strings
pre-filled or empty (Image 3).

Well, that's all for me

Lakrits

---

Screen-shots

Image 1: With en-US text pre-filled in a non-en-US locale file.




Image 2: With en-US text not pre-filled in any non-en-US locale file.




Image 3: Downloading locale files with different options for e.g. untranslated strings.

[saster]

Hi, saster

You don't have to pre-fill any English (en-US) text in the locale files for this add-on
before you upload language files with new strings...
....

Hi,

Well, thank you for the thorough explanation, yes, I really made a mess. Dear Localizers, please excuse me for making your hard work even harder. I used to know these rules, but this time I inadvertently made a mistake. I apologize for it.

Attila