316 replies to this topic

[steffoz]

Creator: Federico Parodi, Stefano Verna, Nils Maier
Ext. Version: 1.1b1

Extension is compatible to:
Firefox: 3.0 - 3.1b3pre
Thunderbird: 3.0a1pre - 3.0b1pre
Seamonkey: 2.0a - 2.0a2
Flock: 2.0b - 2.0.*
Songbird: 0.7 - 1.0.*
Included locales: ar ar-SA bg-BG bn-IN ca-AD cs-CZ cy-GB da-DK de-DE el-GR en-GB en-US es-AR es-CL es-ES fa-IR fi-FI fr-FR fy-NL ga-IE gl-ES he-IL hr-HR hu-HU it-IT ja-JP ko-KR lt-LT mk-MK ms-MY nb-NO nl-NL pl-PL pt-BR pt-PT ro-RO ru-RU sk-SK sl-SI sq-AL sr-RS sr-YU sv-SE ta-IN th-TH tr-TR uk-UA vi-VN zh-CN zh-CN zh-TW
Description: The mass downloader for Firefox.

 View on WTS -- Download the extension

Edited by steffoz, 08 December 2008 - 12:20 AM.

[steffoz]

So finally here we are!
We've just finished the localization process and we're now ready to get all your help if anyone could spend some time on translating this piece of code.. well.. thanks a lot.
I'm always here to help you in any case.

[Luana]

B e n v e n u t i !!!!!!!
Hi, w e l c o m e on BabelZilla
Thanks to be here

In case you're looking for some specific translator, please see the list of the available translators on BabelZilla
Selected that desired one, you may send him a P.M. or an e-mail (if and when public)
You may also insert a new Topic in the Help Section, in order to ask for specific translations, to write a general request about missing translations, etc!

In case you have some curiosities about the WTS, you may find here short and simple Questions&Answers about it (Italian language)
* * *


@ Federico & Stefano:
may you add the localized description to you extension?
TIA


@ Translators:
Please, provide your localizations!

Many thanks in advance

[steffoz]

I updated the extension and I have accidentally lost french translation... (was only at 2% so i hope this won't be a disaster ) ...so sorry about that. Added localized description to extension.
BTW, I didn't expect to see all the pre-existing translators disappear from WTS after an upload. I'm sure I'm doing something wrong here.. Is there any way to re-upload an extension when there are localizations in progress without the nightmare of loosing all the translators settings? I tried to download the zipped locales and insert them into the new xpi I uploaded.. but it didn't work, as WTS fills not completed locales with english translations.. so a 2% in progress becomes a 100%..

[jojaba]

I updated the extension and I have accidentally lost french translation... (was only at 2% so i hope this won't be a disaster ) ...so sorry about that. Added localized description to extension.
BTW, I didn't expect to see all the pre-existing translators disappear from WTS after an upload. I'm sure I'm doing something wrong here.. Is there any way to re-upload an extension when there are localizations in progress without the nightmare of loosing all the translators settings? I tried to download the zipped locales and insert them into the new xpi I uploaded.. but it didn't work, as WTS fills not completed locales with english translations.. so a 2% in progress becomes a 100%..

Don't worry, I will make it again !
I agree with you for the translation, the main work is actually already made.
You have just to upload the files on wts I guess. I'm sure MIAO will give you the right answer to your question

I'll wait a little.

Regards, Jojaba

[Goofy]

Yes Steffoz, you were right to insert all the already-existing locales (even when not complete).
But as you can see on this bit from our Help Q&A guide :
http://www.babelzilla.org/index.php?option...cessfully+saved.
you also have to add one line per locale in the chrome manifest file of the extension.


---
GoofyNote to Miao : small addition made in the english version of the above mentionned Q&A

[Luana]

Added localized description to extension.

Thanks!

BTW, I didn't expect to see all the pre-existing translators disappear from WTS after an upload.
...
Is there any way to re-upload an extension when there are localizations in progress without the nightmare of loosing all the translators settings? I tried to download the zipped locales and insert them into the new xpi I uploaded.. but it didn't work, as WTS fills not completed locales with english translations.. so a 2% in progress becomes a 100%..

When you repackaged the xpi file by adding the various localizations, did you remember to 'update' also install.rdf and chrome.manifest files?
Please note that the WTS parses those files, and if they are not containing all the strings inherent to the present localizations, obviously the WTS won't be able to register the missing strings

Updated Italian Q & A "Come aggiornare un'estensione ?"




[OT](@Goofy: as usual funny cross posting
Thanks for the addition, I'll update the Italian Q & A soon)[/OT]

ADDED: done

Edited by MatrixIsAllOver, 02 May 2006 - 12:16 PM.

[ReinekeFux]

Uhm, all original strings in addurl.dtd are in Italian???
Makes it a bit difficult to understand (for me, at least)...

[steffoz]

Uhm, all original strings in addurl.dtd are in Italian???
Makes it a bit difficult to understand (for me, at least)...

addurl.dtd is not relevant and should be removed.. all his strings are present in dta.dtd. sorry about that.

[jojaba]

Could I begin to translate or should I wait for your tarnslation update ?

[ReinekeFux]

addurl.dtd is not relevant and should be removed.. all his strings are present in dta.dtd. sorry about that.

Ok. Thanks for the info.

[steffoz]

Could I begin to translate or should I wait for your tarnslation update ?

no, I don't think it'll be necessary an update.. you can start translating when you want.. and thanks a lot.

[steffoz]

Uhm... still troubles updating... All the started localizations goes to 100%. Am I missing anything?

Thanks and sorry,
Federico

[Alf]

Uhm... still troubles updating... All the started localizations goes to 100%. Am I missing anything?

Hi,
I just started with the Dutch (nl-NL) translation.
I don't think you missed something: the NON-translated parts of each translation is now filled with the original english strings. That's why WTS says 100%. The translator just needs to replace the english string with his own text.
Alf

[Goofy]

No problem, you did nothing wrong. It seems you have filled every other locale with english strings to translate, which is a kind concern for translators...
But we prefer you leave the other locales as they are (without new strings), because the WTS automatically recognizes new/modified strings in the en-US locale and creates "blank" textarea zones to be filled in every other locale. moreover, there is a handy yellow background that allows us to spot immediately where to translate, as can be seen on this example image from another extension :

Attached Files

•  example.png   7.14KB   40 downloads

[teo]

Hi Stefano, on BabelZilla. I end translation to Polish this new version and I have some remarks about extension. Still are some phrases in *.xul and *.js file which should be translated:

1. about.xul all phrases should be moved to about.dtd file - see attached file
2. addurl.xul phrases in line 88, 92 - line 88 is not obligatory translated but 'URL' in Polish language should be translated to 'Adres URL'
3. down.xul phrases in line 66-68 - these used keys in some languages not matching to the translated phrase
4. dta.xul phrases in line 97, 111, 165-166 - see point 2 and 3 (acceskey)
5. filters.js phrases in line 177, 181
6. info.xul phrase in line 84
7. renamingmask.xul phrases in line 39, 72 not changed to entity code
8. string.js phrase in line 285
9. barra.xul phrases in line 24, 26, 30, 33 - this names should (if translator want) translated - I want
10. menu.xul phrases in line 20, 21, 26, 27 - names, and 22, 23, 24, 28, 29 - acceskey- this names and adequate acceskey should (if translator want) translated - I want
11. saveas.xul phrases in line 22, 24- this names should (if translator want) translated - I want

Please correct these inconveniences.

@Edit: I started this post before you last updated extension.


(Old attachment has been removed)

Edited by MatrixIsAllOver, 24 June 2006 - 02:27 PM.

[steffoz]

But we prefer you leave the other locales as they are (without new strings), because the WTS automatically recognizes new/modified strings in the en-US locale and creates "blank" textarea zones to be filled in every other locale.

Thanks, I hope next time we won't mess up it all again

Federico

[teo]

Thanks, I hope next time we won't mess up it all again

Federico

With corrections about I wrote in the post above

@Edit: Don't upload new version! I'm prepering next important remarks

[steffoz]

1. about.xul all phrases should be moved to about.dtd file - see attached file
2. addurl.xul phrases in line 88, 92 - line 88 is not obligatory translated but 'URL' in Polish language should be translated to 'Adres URL'
3. down.xul phrases in line 66-68 - these used keys in some languages not matching to the translated phrase
4. dta.xul phrases in line 97, 111, 165-166 - see point 2 and 3 (acceskey)
5. filters.js phrases in line 177, 181
6. info.xul phrase in line 84
7. renamingmask.xul phrases in line 39, 72 not changed to entity code
8. string.js phrase in line 285
9. barra.xul phrases in line 24, 26, 30, 33 - this names should (if translator want) translated - I want smile.gif
10. menu.xul phrases in line 20, 21, 26, 27 - names, and 22, 23, 24, 28, 29 - acceskey- this names and adequate acceskey should (if translator want) translated - I want smile.gif
11. saveas.xul phrases in line 22, 24- this names should (if translator want) translated - I want

thanks teo, locales modified once again
i agree with numbers 2, 3, 4, 5, 6, 7 and 8. we want dta and oneclickdta to be universal. and we also want the license to remain in english.

[teo]

thanks teo, locales modified once again
i agree with numbers 2, 3, 4, 5, 6, 7 and 8. we want dta and oneclickdta to be universal. and we also want the license to remain in english.

Licence text OK, but Copyrirght, version, Privacy, information about icons, warranty, homepage ... should be translated.

And now next portions of my remarks - not all, will be next:

1. Not working delete filters
2. Not working Privacy link in the about window
3. mainPane.xul - in line 45 add align="center"
4. filtersPane.xul - in lines 47, 50, 53 add align="center"
5. filtersPane.js phrases in line188, 204, 209, 226, 229 should be translated
6. interfacePane.xul line 61 should be translated - I made also litle changes in layout
7. privaPane.xul - in line 42 add align="center"
8. advPane.xul - in lines 32, 52 add align="center" line 36 should be translated.

Changed files (only *.xul) are in the attached fil, without code for Tools Menu.
(Old attachment has been removed)

Edited by MatrixIsAllOver, 24 June 2006 - 02:29 PM.