Creator: David Dernoncourt
Ext. Version: 0.9.8

Extension is compatible to:
Firefox: 1.5 - 3.0b3
Included locales: af-ZA de-DE en-US es-ES fr-FR hr-HR it-IT ja-JP nl-NL pt-BR pt-PT ru-RU sk-SK uk-UA
Description: Temporarily disable popup blocking. Inspired by the Popups Must Die! extension. To toggle popups on/off, either click on the icon or press CTRL+SHIFT+Q.

 View on WTS -- Download the extension

W e l c o m e on BabelZilla!

In case you have some curiosities about the WTS, you may find here short and simple Questions&Answers about it!

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.


Just a 'request': may you please add the currently missing localized description to your extension?
TIA
--------


Finally, thanks for sharing with all us the fact inherent to your holidays. Don't worry, we will wait for your return!
Take a good rest.

Well, I'll work on it... it shouldn't make me miss my car... In fact I had wondered how I could localize the description, but didn't find and then forgot about it

Thank you for my activation btw, my account behaves better now

Localized description added... it's your turn to work now

Since it disappeared from my 1st post when I uploaded the new version, I remind you that I won't be here from Jul 24 to Aug 14

Hello
I have a little request too
There should not be .js fils in the locale folder because of security possible issue. I know you don't intend to drop malicious code in but our Tech Admin care about that. On the other hand, there is never .js files in locales for any extension. Though it is a bit longer, there is a workaround to localize strings from the .js file (that I used in the previous version I sent you*)

See here a tiny tutorial I made :
http://www.babelzilla.org/index.php?option...=18&Itemid=
or
http://www.babelzilla.org/index.php?option...=15&Itemid=

[*in fact, you probably just have to copy paste some lines, or I can arrange that for you if you are going on holidays ]

You don't want to let me go, do you ?
Well, anyway, I hadn't thought about the security issue so I fixed that... I chose this .js method because I had troubles to use French accents properly in .properties files, even with jEdit, but for some reason now it works (I guess I was using a wrong char encoding )

Ok. There is no problem if you take your time and have vacation time
As a sidenote, don't worry with french special characters, they should display without prob with utf-8 now (it was not the case one year ago)

Hmmm...
It seems there is something strange, because the extension doesn't work properly.
This is not inherent to the localization(s), but I can't confirm about the correctness of the localization because I can't see a few strings.
I've asked for a confirmation to a friend of mine before posting, and this is the result:


More, personally re-tested with a fresh profile of the candidate of the next version 1.5.0.5, I noticed that the word 'undefined' appears also in the Settings - General window:


Please, may someone confirm if this strange situation is not only happening to me (and to a few friends of mine)?
TIA

The locale es-ES is finished and in testing.

Locale es-ES is released.

Regards,

I made a translation too Dutch (nl-NL, nl-BE).

I'm testing it right now... tell me what to do when it's finished.
Should I mail you or what?

~Take care, Budsie

Hi

Once completed the testing phase, you should only set as Released your localization.
And voilà also the meaning of the various definitions about the phases of one localization!

Thanks... I actually did it.
It's finished, but there is this one thing that is not translated.
It's the copyright license in the "About" section.

@patheticcockroach:
So... it's finished and you can add it to your extension.
If you got any questions or something like that, just ask.

~Budsie

Thank you all for your help. I'll soon add de, es and nl to the xpi.
But maybe I'll wait for the it-IT problem to be solved though : Matrix, I think the problem is caused by the accentuated letters (there is this è in a .properties file...), that's the same problem as I had with my FR translation, I solved it first with a (bad) .js file, then by using the \uXXX character code (I used jEdit and a Chars_to_unicode_entities macro).
But, anyway when I downloaded your it-IT locale from babelzilla, it worked fine (see screenshot), did you try it too ?

Strange, both of us Italian translators have translated offline by applying the new possibility to use normal characters instead of unicode characters in *.properties file, and the results have been those in the added images.

BTW, I've just tried and I can confirm that it works fine!
Italian localization has been set as Released.

Well, it seems that this new possibility is so new that it's not even already implemented properly ^-^ Anyway, thank you, I'll add the it-IT local to the xpi... then should I upload the new xpi to babelzilla or just to addons.mozilla ? And is it better to change the version when adding locales ?

Eh eh eh, probable!
The important thing is that now it works fine. The next time I'll check (and I'll ask for a check) all possible versions.


IMHO, it would be nice if you could upload the last / updated version also here.
In this case, probably not necessary request, but please read this before uploading.
Well, it would be preferable if you could change the version number, so that final users know this is a new version (although it contains "only" new localizations!)

Ok, I've just uploaded the new version including all available locales.
Thanks

Hi,

I'm the second translator of your extension. Italian localization has been tested and re-released!

Luca

Hi,

I saw that Did you do any modifications though or was the test all ok ?

We didn't make any modification. We just tested once again the localization, then we set it as 'Released'.

Regards,
Luca

You didn't update your extension on https://addons.mozilla.org/!

Don't forget to do that.

~Cheers, Budsie

Hi

Thx for reminding me, but in fact if you have a quick look on the official page, you'll notice it's pending approval

Btw, I'll soon need another tiny update in the translations because I'll add credit for translators on the about page.

Bye

I'm on duty tomorrow... 24h of hard work... or maybe not ?

Slovak (sk-SK) locale added into WTS

Thank you, I uploaded the new version with sk-SK (and also fr-FR) to Mozilla and Filefront.

I made a new locale for your ext., but I think you should allow the translaters also to translate the key combinations in the options / keys dialogue, because, for one, German keyboards use the terms "St(eue)r(un)g" for "C(on)tr(o)l" and "Umschalt" for "Shift".

Hm... good idea, I didn't know about that... I'll fix this tomorrow.

Ok, so I uploaded the new version, there are 3 new strings.

Important note to other translators who hadn't yet updated their translations : due to the fact that I downloaded all locales, zipped them in the new XPI and resent them, some of the strings in your locale are in English. Check for english strings in settings.dtd. Sorry for this, I didn't know about it.

Hi,

Italian localization is ready in the WTS.

Locale es-ES release.

Regards,

Thanks. I'll update the extension on Sat 30... Maybe the Brazilian and Ukrainian locales will be released then ?

Ok, I released version 0.9.7.5 with nl-NL, de-DE, it-IT, es-ES (and fr-FR, en-US, sk-SK) (see official page for download link).

However, there is a problem with the af-ZA locale, which is why it's not included.
Screenshot :

(sorry for the file name btw , it was automatically modified from "a.png"...)
leuce, if you don't want to make the package yourself, here is one with your af-ZA locale included : http://files.filefront.com/yespopups_0975_...;/fileinfo.html

Regards

Well the error message is a bit cryptic -- I can't figure out what's wrong, but it seems that the error lies with the about.dtd file. I've checked the file and the only thing wrong with it is that the encoding of the international character (i-umlaut) seems to have gone awry. I've re-exported everything once again and uploaded it -- please let me know if this does the trick. If so, then I'll know what went wrong, and I apologise for it. If not, then we can work from there, if you want to. :-)

This version works, I'll add it in a new release when the current one is approved on Mozilla Update (otherwise it might never be approved - The reason why your Firefox extensions are old ).
Could I just know what you think went wrong ?

Forgot to save as UTF-8. :-(

Hi,

Just to let you know I'll release another version on Nov 18 including all locales 100% done (either testing/QA or released... but it would be great if you could do the testing yourself if your translation is still testing/QA).

Edit : done - added af-ZA, ru-RU and pt-BR (pt-BR is unfinished)

I finished testing of Russian version Yes popups.
ThanX you for it, it very usefull!

Yes, I find it very useful myself too ... It's funny because I got some comments who say "omg it's totally useless" and some other comments who say "wow it's definitely a must have", hm, lol.
Anyway, did you change anything compared to the translation I included in version 0.9.7.6 released on November 18 ?
If you did, I'll make sure to include your new version in the next release which should fix some, hm, minor or major (depending on whether or not you experience them ) compatibility issues.

Hi guys. I've tested and released the ja-JP locale!

Thanks. I'll merge it next week-end... I hope it will be approved though, the latest released pended *1 month* then got refused because the reviewer didn't understand what the extension does... They must be really lacking reviewers...
Oh, and I'll also upload the new version here (there is no new string) without including the locales 0% translated.

Oh please, upload the xpi file containing also the locales 0% translated, otherwise the WTS will delete the registration of the translators (of the locales 0% translated) who will appear like "Unknown".
Moreover, if their locales will be included also the registered translators of the locales 0% translated will receive the email notification and probably this could stimulate them to complete the previous 'job'!
TIA

Yeah but if I upload them they will appear as 100%... I'm not sure this will stimulate the registered translators... Are you sure it's a good idea ? Cause my point with not uploading the 0% was to free the slots for new translators.

Oh no!
If you upload them in this manner (please note the point number 3) their locales will appear at the percentage correspondent to the number of translated strings.

Hm... point 3 says leave all locales as they are and don't fill them with english strings... I'm sorry but if I leave the 0% as they are, they are filled with english strings and it's not my fault, the system does it... So they will appear 100% since there is no new string in the update.

Only if you download all locales in a single tar.gz the missing strings will be replaced by their English counterparts. If you download the individual locale files in separate tar.gz files the missing strings will remain empty, and they will show up as such when you upload the xpi again

Wow... thanks a lot, I didn't know that This should be written in big fat red somewhere in the download area.

That's a good suggestion!
Thanks for this, probably it will be added to the current Q & A (and probably also in the download area)

Well, I have a better one then : propose 2 buttons : one with download all locales with missing strings in en-US, one with download all locales with missing strings empty or non existent.

Hm so I just tried this and in fact it doesn't work : no matter what I choose to download (all locales, one locale at a time, or even just one file from a locale), it's filled up with English strings.

Hmmmh yes so it seems. I think one of our Tech Admins needs to take a look at this