Recommended Addon

[lultimouomo]

Maintainer: lultimouomo
Creator: Luca Niccoli

Ext. Version: 0.4
Description: Defragment your firefox places.sqlite database to speed-up Firefox.
Extension is compatible to: ( 3.5 - 3.7a1pre)

Included locales: cs-CZ en-US it-IT pl-PL

View on WTS -- Download the extension

[markh]

Welcome!

Just a bit of information for you: in case you have some queries about the WTS, you can find short and simple Questions&Answers about it here!

In case you're looking for a specific translator, please see the list of available translators on BabelZilla.
When you select the desired one, you can send him/her 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.

[teo]

@lultimouomo
I posted you on support email from AMO. This version haven't localized extension description and phrases displayed in the notification after vacuum database. I attached mine version which resolved these issues and more….

Attached File(s)

 vacuum_places_improved_0.4_fx.xpi ( 8.62K ) Number of downloads: 0

 

[lultimouomo]

@lultimouomo
I posted you on support email from AMO. This version haven't localized extension description and phrases displayed in the notification after vacuum database. I attached mine version which resolved these issues and more….

Hi teo!
I just read your mail, thanks for the help, actually I had already implemented the internationalization of the javascript strings, but I was waiting to upload the new version because I was trying to understand if there was a way to use the new localization method for the install.rdf string with babelzilla
(see https://developer.mozilla.org/en/Localizing...on_descriptions ).
The add-on is not compatible with firefox < 3.5 anyway, so there's no need to keep backward compatibility.

Is there a way to do it? I'll go with the old way otherwise...
Another question: is there a way to automagically credit the translators in the install.rdf?

Cheers,

Luca

[teo]

Hi teo!
I just read your mail, thanks for the help, actually I had already implemented the internationalization of the javascript strings, but I was waiting to upload the new version because I was trying to understand if there was a way to use the new localization method for the install.rdf string with babelzilla
(see https://developer.mozilla.org/en/Localizing...on_descriptions ).
The add-on is not compatible with firefox < 3.5 anyway, so there's no need to keep backward compatibility.
Is there a way to do it? I'll go with the old way otherwise...

Old method is still supported by Fx3 and above. In the my version is used this method. New method is to complicate if you have many localization, old is easy to localize.

Another question: is there a way to automagically credit the translators in the install.rdf?

See my install.rdf file and pay attention to <translator> and open about window Tools->Addons-> addon->right click and choose About

My version is ready to use. You can just upload to WTS.

[lultimouomo]

Maintainer: lultimouomo
Creator: Luca Niccoli

Ext. Version: 0.4
Description: Defragment your firefox places.sqlite database to speed-up Firefox
Extension is compatible to: ( 3.5 - 3.7a1pre)

Included locales: cs-CZ en-US it-IT pl-PL

View on WTS -- Download the extension

[lultimouomo]

Old method is still supported by Fx3 and above. In the my version is used this method. New method is to complicate if you have many localization, old is easy to localize.

I know, the old one just looks an awful hack, but I see the new one is a PITA with the WTS.

See my install.rdf file and pay attention to <translator> and open about window Tools->Addons-> addon->right click and choose About

I was wondering if there's a way to retrieve the list of translators from the WTS...
Right now the only way I found is to click on each translation, then on the name of the translator, and then look on his/her page for the name, not the quickest thing.

My version is ready to use. You can just upload to WTS.

I had mine ready with some code changes, just added the description localization.

Cheers,
Luca

[teo]

I know, the old one just looks an awful hack, but I see the new one is a PITA with the WTS

No, this is recommended by Devmo old localize description method. You saw this method on MDC site.

I was wondering if there's a way to retrieve the list of translators from the WTS...
Right now the only way I found is to click on each translation, then on the name of the translator, and then look on his/her page for the name, not the quickest thing.

No, open your extension in WTS, find Developer and choose Contact translator. On the bottom of page is translators list.

[nam]

Hello,

I'm french, I've discovered this great FF add-on. I've used it with big FF start-up speed improvment and decided to help for the translation in french.
After sending translated files by mail to the creator without success . I've decided to enter in the babelzilla "Matrix" ... and here I am .

I've done my best to translate files, uploaded them in WTS, pass them to "needs review" status.

Can anyone have a look to them and tell me if they work or not ?

Best regards,

Nam (who needs some help for his first translation).

[markh]

Hello,

I'm french, I've discovery this great FF add-on. I've used it with big FF start-up speed improvment and decided to help for the translation in french.
After sending translated files by mail to the creator with no success I've decided to enter in the babelzilla "Matrix" ... here I am .

I've done my best to to translate files, uploaded them in WTS, pass them to "needs review" status.

Can anyone have a look to it and tell me if it works or not ?

Best regards

Nam (who needs some help for his first translation).

Hi, and a warm here! Although French is more Goofy’s turf, I will do the honors in his absence . You have done correctly so far, so if all goes according to plan someone from your fellow French translators will review it. Of course they will ask you to return the favor at some point, so you can find information on the testing procedure in this Wiki section.
Never hesitate to ask for help or guidance, either here if it concerns this specific extension or in our Help section or in the French forum for other stuff.

[nam]

Hi,

Many thank's for your quick response .

Can anybody help and provide me what you call "a test build" including my translation ? It's too complex for me because locale fr-FR is new for this extension and I need to add a line in the chrome.manifest file .

Many thank's for your help.

[markh]

Hi,

Many thank's for your quick response .

Can anybody help and provide me what you call "a test build" including my translation ? It's too complex for me because locale fr-FR is new for this extension and I need to add a line in the chrome.manifest file .

Many thank's for your help.

I’ve sent it to you through PM Note that the locale is fr, not fr-FR.

[nam]

I’ve sent it to you through PM Note that the locale is fr, not fr-FR.

Hi, I received the build : install OK but it does not work. I've tried to reply by PM ... but I didn't manage.

What's wrong with your re-packaged plug-in, is it my translation or something else ?

PS : the pb is "XML error" when try to enter/modify addon options.

[teo]

Hi, I received the build : install OK but it does not work. I've tried to reply by PM ... but I didn't manage.

What's wrong with your re-packaged plug-in, is it my translation or something else ?

PS : the pb is "XML error" when try to enter/modify addon options.

Use in the .dtd file

CODE

&apos; instead '

[nam]

all ' replaced by &apos; in .dtd file => no change.

the error returned is
"Erreur d'analyse XML : entité non définie
Emplacement : chrome://vacuumplacesimproved/content/prefs.xul
Numéro de ligne 41, Colonne 1 :<prefwindow id="VacuumPlacesImproved-prefs"

[Goofy]

all ' replaced by &apos; in .dtd file => no change.

the error returned is
"Erreur d'analyse XML : entité non définie
Emplacement : chrome://vacuumplacesimproved/content/prefs.xul
Numéro de ligne 41, Colonne 1 :<prefwindow id="VacuumPlacesImproved-prefs"

hey please stick to UTF-8 (have a look on the French forum )

[nam]

Ok file saved in "UTF-8 format" and now it's ok => I uploaded new files and switched translation's status to "Release".

What's next ?

[markh]

What's next ?

Nothing for now; the developer will include the locale in the next release and you will get a notification when an update arrives here. You can of course look for other translations to be done
Hint for the future: if you use the WTS for translating instead of doing it locally, the UTF-8 problem will not occur.

[nam]

the developer will include the locale in the next release and you will get a notification when an update arrives here.

Hello, I've realized that the extension stored in WTS /Babelzilla is an old version (0.4) . Hopefully the new one (1.0) seams not to have any new strings to translate. My job is safe !

Who can update Addons in BabelZilla to the correct version available here : https://addons.mozilla.org/en-US/firefox/addon/13878 ? (version 1.0 has been released a little more than one month ago).

[markh]

Hello, I've realized that the extension stored in WTS /Babelzilla is an old version (0.4) . Hopefully the new one (1.0) seams not to have any new strings to translate. My job is safe !

Who can update Addons in BabelZilla to the correct version available here : https://addons.mozilla.org/en-US/firefox/addon/13878 ? (version 1.0 has been released a little more than one month ago).

The extensions hosted here are not necessarily always the latest version; as you say, the newer version may not contain any new strings so there is no need to bother translators, unless there is a compatibility issue.