Maintainer: FoxyProxyDevTeam
Creator: FoxyProxy, Inc.

Ext. Version: 4.2.1b1
Release date: 0000-00-00
Description: Premier proxy management for Firefox
Extension is compatible to: ( 3.0a1pre - 23.0a1) ( 2.0a - 2.20a1) ( Songbird 0.4 - 2.3.0a) ( 3.1b3 - 23.0a1)

Included locales: ar bg-BG cs da de de-AT el en-US es-AR es-ES et-EE fa fa-IR fi fr gl-ES hr-HR hu-HU it ja-JP ko-KR lt lv-LV nl pl pt-BR pt-PT ro ru-RU sk sr sv-SE th tr uk-UA vi zh-CN zh-TW

View on WTS -- Download the extension

Hi, w e l c o m e on BabelZilla.

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.
* * *

There isn't a previous Italian translator, therefore an invitation for this translation will be inserted soon!

Hi MatrixIsAllOver,

I'm a little confused. If I want all possible translations, according to this FAQ I have to send at least 45 PMs (one for every language except en-US). Is that correct? and if some of the translators I contact aren't interested, then I have to send more PMs.

Is there a more efficient way?

Thanks,
eric

Oh no, !
This FAQ is inherent to whichever extension which already contains localizations for which BabelZilla translators registered themselves as official translators



In this case, in order to add as more localizations as possible the invitation in the Help forum is a good and efficient way!

@Translators : among the files to translate, you will find a .XHTML help file that cannot be translated online. You have to download it, edit and translate with your favorite text editor (I use Pspad), then upload it (upload link is at the top of your locale files page).
You cannot reach 100% status without this translation, though the percentage of translation may be partly wrong in various cases, sometimes displaying 130% . Please check.

I do for FoxyProxy translation of the UI into Russian.

Hi

I'm working in Spanish translation, and I could see that one string remains in English:



Alert shows on clicking 'Use SOCKS proxy for DNS lookups' option (line #113 in options.xul file).

Could you change it? Thanks

Oops! Thanks for finding that, chuzo.

I also found a few accesskeys (shortcuts) which are missing from foxyproxy.properties.

How can I update this? Do I resubmit the entire XPI or just the changed files... or?

Thanks,
grimholtz

See this

How to update an extension ?

ru-RU locale is ready.

One question - and unless cannot be pulled out names of months and days of week from operation system?

@chuzo: thanks, but could this be a problem? Suppose the German translation is 60% complete. I download all the translations (including 60% German) and include them in the new XPI. Now just before I upload the new XPI, the German translator finishes another 20% and uploads that. Now I upload the new XPI (which only has 60% German translation, not 80%). Is the 20% lost??

Not to my knowledge. Not with Javascript, at least. Javascript uses numbers to represent days and months and time. Perhaps there's an XPCOM component to get this info; I'll have a look.

Thank you,
Eric

Yes, it is lost in this case. But you could download all translations again just before upload new .xpi

Yes, but there is always a period of time (even if it's just a few seconds) when a translator can upload a translation just as the extension author is about to upload (or is in the process of uploading) a new extension version.

This is why version control systems exist!

Hi,

I uploaded a new version. Please note there are now only 3 files for translation:

• foxyproxy.dtd
• foxyproxy.properties
• torwizhelp.xhtml

The old files have been merged into just two, but there are also lots of new words for translation (as well as some that have been removed). This is the last beta before release 1.1, so whatever you translate now will be included in version 1.1. Please don't forget the .xhtml file!

Thanks!

-Eric

Spanish (es-ES) updated and released in the WTS

Spanish (Spain) / es-ES

Hi Chuzo,

It looks like there's a problem with torwizhelp.xhtml es-ES version.. I think you accidentally removed "<p>" from around line 50. (after "Comodines")

Try opening it in FF and you'll see the error displayed. Is this something I should fix? If I fix it, how do I submit it to WTS?

Thank you,
Eric

Sorry, but file seems to be broken each time I upload it to WTS

I attached here correct file, please use it

(Old attachment has been removed)

@translators : please from now on attach your XHTML files here with your post, just as for HTML files. thanks.
Chuzo, may you report in the bugreport section ? Thanks.

Hi everyone,

I just uploaded FoxyProxy 1.1 beta5... the FINAL 1.1 beta. I know I said that before but I was motivated to make some last-minute changes

Fortunately there is very little work for you to do.

Please note, the only files needed for locales now are:

• foxyproxy.dtd
• foxyproxy.properties
• torwizhelp.xhtml (has not changed)

All the other files can be deleted!

Also, can everyone PLEASE post torwizhelp.html here on the forums because the WTS strips out some of the HTML and makes the file unusable. Thanks!! (You do not need to edit torwizhelp.xhtml -- it has not changed!! just post it here, please, if you haven't already)

-eric

@chuzo: thanks for the quick turnaround!

Anyone else? I'm going to publish version 1.1 to http://addons.mozilla.org on Sunday, 14 May about 17:00 GMT-5. It would be nice to have more translations before then so they can be in release 1.1

Thank you,
Eric Jung

Oops, well, can't win'em all.

Danish tested and released.

2 details:
1) For initial config of FoxyProxy, the "Help contents" button 'does not work'; that is, it works but no Firefox window is being opened until guide is finished, so it isn't visible...
2) Description of module seems to be in english, still.

Important: Please check my xhtml-file for errors in the first bytes and remove the BOM there...

Nice one!

Hi AlleyCat,

Thanks for the translation!

Thanks, I will look into this. I assume it isn't a Danish-specific problem, right?


You mean "FoxyProxy - Take Back Your Privacy"? I don't know how to i18n that, do you?


What does BOM mean?

Thanks and regards,
Eric

See this:

Howto : localize the initial description for Moz family extensions

You can see also here : BOM is a kind of signature that extensions don't like, must be removed when text editor add it (I think, I am never sure with all these encoding misteries )

Verison 1.1 -- the first internationalized and localized release -- is now available!.
Thanks to all who helped! Your names are emblazoned on the about box:



If you'd like:

• A different name or pseudonym than what's shown above, please let me know and I'll change it for version 1.2 (you can also remain anonymous, if you like... just tell me)
• Your name to be hyperlinked with a website or email address, please let me know and I'll change it for version 1.2.

Notice the BabelZilla.org promotion -- If the user clicks on "Your Language" or "Your Name Here!", he is taken to http://www.babelzilla.org



Thanks. Looks like I followed most of those steps, but used a different filename than prefs.js and the wrong key in the props file. Fixed now.



Ugh. I'll look into it.

Please re-release version 1.1 (/complete/ Slovak localisation is ready /without xhtml/) and please reupload the xhtml (because it is corrupted - so it cannot be localised).
Thanks in advance
-Rastislav Hubočan alias Hubo

Thanks you very much indeed for this promotion !

But, as far as the french locale is concerned, it was not on "release" status when you grabbed it on the wts, so you released a version with half-translated strings (which is not a good promotion for our lazy french team ).
Now we are just discussing some little probs of "better" translation, but we are very near to finish it. We shall post one word here on this topic to let you know. Sorry to be late !




----FYI


- You can use another filename without problem, the ID key is the very thing to care of

Hi Hubo, I'm sorry I can't re-release it because AMO would have to re-approve the entire release again (which takes a couple of days). Version 1.2 is just around the corner (2-3 days at most?) so I'd rather just wait for that. Is that OK? Will Slovak users not be able to use FoxyProxy 1.1 at all???


I am sorry about that. I couldn't understand which translations were complete and which were not because of the XHTML problem discussed earlier in the thread Sorry about that.

About BOM: Yeah sorry about that; 3 of my editors totally ignore BOMs (but neither strips them) and two of those can't handle utf-8 properly at all; my last handles it with some problems, but the bytes cannot be removed.

So far my only real solution to this has been uploading it to my linux webserver and editing it there via ssh, but that's not much of a solution, obviously...

And yes, I need to provide the link when I say that about localized description; but Goofy is usually quick to provide it. I've been too lazy to store it so far...

I don't see danish on the list yet, but a link to here is very fine.

About translations: Well, the french must live with partially translated; its better than none at all? And with a new release so close at hand, it doesn't really matter IMHO. Cest la vie... (OK that's pretty much all the french I know at all).

About XHTML: If the number of lines doesn't match exactly (like, a translation might be shorter in chinese than in english and thus take up fewer lines) the WTS sees this as missing lines - it has to base it assumption on something, and for all translations it assumes line-for-line.
Failing any lines, the version the author (and anyone else getting it from the wts) receives contains the last lines of the english files, and can cause an error in the browser. A small error when you know where to look, but care needs to be taken.

Version 1.1 is usable. OK I will wait for 1.2 :-)

FYI : I have just used NVU to edit/translate the xhtml file and it displays fine in the interface.

Can you post your XHTML file here as an attachment, please? WTS mangles it.

But... but... it's... wysiwyg...

OK, I actually have NVU installed, I will try it out as editor.

EDIT: Mine? Really? Will attach...

(Old attachment has been removed)

OK above attachment is my 'original' with BOM at the start of the file. Goofy, after having tested NVU, a number of things were changed in the file:

1) It removed starting <?xml version="1.0"?>
( is the BOM, <?xml version="1.0"?> is the document definition)

2) It corrected (correctly I guess) the
<html xmlns="http://www.w3.org/1999/xhtml">
to
<html xmlns="http://www.w3.org/1999/xhtml" lang="da">

3) After that, it has done some reformatting of the file - of no real consequence as it makes the file longer, but it still doesn't match the original

4) It has translated all danish characters into their HTML entities, which is good.

Conclusion so far: The entity translation is good, the correction is good, the other things seems dangerous to me. I'm not sure it's a good idea.

Here's a zip with both files. File '2' is the one which has been opened and saved in NVU.
(Old attachment has been removed)

@alleykat
I have nothing against wysiwyg html editors , not being a codehacker. You can anyway switch to html code with a source tab, and even visualize html tags as icons.
I don't know if it really dangerous to use Nvu , I use it each time I have to create or translate a html file and I rarely have problems. But maybe I am too ignorant to see the danger.

@ grimholz
--- At last the french locale is available here on the WTS

I also attach the xhtml file here.
(Old attachment has been removed)

English FoxyProxy Help has been updated and extended. Can you upload it to WTS (as zip), please?

Do you mean the 3 files (foxyproxy.dtd, foxyproxy.properties, torwizhelp.xhtml) or the entire XPI?

I mean torwizhelp.xhtml, but I repair it myself. So I am attaching it for slovak locale. Don't forget to change code of slovak localisation to "sk" instead of "sk-SK" it is official change (by Mozilla). -Thanks
Slovak localisation of other FoxyProxy files is updated, too.

(Old attachment has been removed)

Really? So the directory should be locale/sk not locale/sk-SK?

hello Igor,

i think 'pattern' mean 'шаблон' (not 'образец')

Working on the Dutch translation. It's not ready yet, but you can find the XHTML file attached.

-EDIT- D*mn, upload of the xhtml failed. I'll zip it.
(Old attachment has been removed)

Cool, thanks!

Yes!

Slovak localisation corrected/updated. Here is the XHTML...
(Old attachment has been removed)

Dutch locale is ready. I suppose, like the Slovak locale, the coding should be nl, not nl-NL. Although I am not sure.

Croatian translation released.

Here is attached torwizhelp.
[attachmentid=1385]

Hi Eric,
I made translation to Polish and some changes in the files:
addeditproxy.xul
options.xul
pattern.xul
proxyprompt.xul
foxyproxy.dtd
In the .xul files I don't changed id="xxxxx"
I prepared new extension version. See attached file.
What do you you think about my changes ?


(Old attachment has been removed)

Hi teo,

Thank you for the Polish translation! I've looked at the XUL files and I'm not sure what you changed? Can you please elaborate?

Thank you,
Eric

OK. Below are what I changed:

1. addeditproxy.xul
from line 37 I changed <hbox> to <grid> element for better looks
lines 156 and 203 'foxyproxy.notes.label' to 'foxyproxy.name.label'

2. options.xul
lines 72 and 141 'Click to select which columns to display' to '&foxyproxy.tree.pickertooltiptext.label;' this string is in the 'foxyproxy.dtd' file', but you forgot change phrase to string
lines 77-88 all phrases to strings. First - in Polish language should be i.e 'Port SSL' instead 'SSL Port' and second i.e 'HTTP', 'FTP'... should be ttranslated - the same as Firefox localization. i.e in the Polish Firefox locale we use something like 'HTTP Proxy host'

3. pattern.xul
lines 32,33 'foxyproxy.notes.label' to 'foxyproxy.name.label'

4. proxyprompt.xul
line 44 'foxyproxy.notes.label' to 'foxyproxy.name.label'

Why I changed 'foxyproxy.notes.label' to 'foxyproxy.name.label'? In this places are proxy name, pattern name not notes

5. foxyproxy.dtd' file'
Adequate changes to changes in the .xul files and 'Matching Pattern Notes' to 'Matching Pattern Name', 'Wildcard or Regular Expression' to 'Pattern Type' - is shortly, better looks

Hi everyone,

I've uploaded FoxyProxy 2.0 beta1. It has everyone's translations. I didn't know if I should use the XHTML files posted in this thread or the ones in WTS? Does anyone know? I thought they couldn't be put in WTS--has that been fixed? For now, I've included the ones in WTS; not the ones posted in this thread.

Please check the about box for your name! If you'd like a link to your web site when your name is clicked, please let me know.

Thank you,
Eric H. Jung