122 replies to this topic

[ericjung]

Creator: LeahScape, Inc.
Ext. Version: 1.7b8

Extension is compatible to:
Firefox: 1.0 - 2.0.0.*
Mozilla Suite: 1.6 - 1.8+
Seamonkey: 1.0 - 1.1.*
Netscape: 8.0 - 8.1
Flock: 1.0+ - 1.0+
Included locales: de-DE en-US es-ES fr-FR nl-NL pl-PL pt-BR zh-CN
Description: Creates and manages passwords and other account information.

 View on WTS -- Download the extension

Edited by grimholtz, 21 September 2007 - 12:56 AM.

[Goofy]

Welcome back here with this other celebrated extension of yours.

I am a bit puzzled by the locale files as they are submitted here. There are a huge number of things like

passwdmakerOverlay.006.label
&navigatorOverlay.006.label;

passwdmakerOverlay.006.accesskey
&navigatorOverlay.006.accesskey;

passwdmakerOverlay.007.label
&navigatorOverlay.007.label;

passwdmakerOverlay.007.accesskey
&navigatorOverlay.007.accesskey;

passwdmakerOverlay.008.label
&navigatorOverlay.008.label;

...where each second line is supposed to be a string of the user interface to be translated. But obviously these are not strings but ENTITIES without their corresponding strings.

Would you mind explaining ? What are we supposed to translate in such a case? Just copy-paste the entity name?

Thanks in advance for any guidance

[edit] Mmh after having browsed the en-US file, yes, I think we have to do that

Just copy-paste the entity name

Please confirm.

[Goofy]

@ all translator friends.

You can find in the attachment a passwordmaker.dtd fil including ONLY items that need NO translation, as mentioned above. Just grab it and upload it, and your work will be automatically 33% made (255 lines )

 passwdmaker.dtd   17.48KB   5 downloads
mmh a zipped version may be easier to grab
 passwdmaker_reduced_DTD.zip   1.7KB   4 downloads


@grimholz

I have no objection to unusual things (I even love totally unexpected ones ) but I have noticed that

CODE

<!ENTITY advanced-options.100.accesskey "&advanced-options.017.accesskey;">
<!ENTITY advanced-options.100.accesskey "&advanced-options.017.accesskey;">
<!ENTITY advanced-options.102.tooltiptext "&advanced-options.101.tooltiptext;">
<!ENTITY advanced-options.103.tooltiptext "&advanced-options.101.tooltiptext;">
<!ENTITY advanced-options.104.tooltiptext "&advanced-options.101.tooltiptext;">

Is is intentional you dropped twice or three times the same thing with same or different names ?

[ericjung]

Welcome back here with this other celebrated extension of yours.

Thank you!

Just copy-paste the entity name?

Yes, correct. The person who localized the extension (Mauro, pt-BR) did this when strings were duplicated in the extension. What is normal? To make two or three or four ENTITIES, all with the same quoted string?

I have no objection to unusual things (I even love totally unexpected ones ) but I have noticed that

CODE

<!ENTITY advanced-options.100.accesskey "&advanced-options.017.accesskey;">
<!ENTITY advanced-options.100.accesskey "&advanced-options.017.accesskey;">
<!ENTITY advanced-options.102.tooltiptext "&advanced-options.101.tooltiptext;">
<!ENTITY advanced-options.103.tooltiptext "&advanced-options.101.tooltiptext;">
<!ENTITY advanced-options.104.tooltiptext "&advanced-options.101.tooltiptext;">

Is is intentional you dropped twice or three times the same thing with same or different names ?

These ENTITIES I added when Mauro was finished. What is wrong with the names? I don't understand, but I must have done something differently than Mauro?

Thank you,
Eric
p.s. teo--welcome. i see you have registered for the Polish translation. I hope we can work well together this time

[Goofy]

I would not be comfortable to leave two identical entities with different values

<!ENTITY advanced-options.100.accesskey "&advanced-options.017.accesskey;">
<!ENTITY advanced-options.100.accesskey "&advanced-options.017.accesskey;">

I fear there may be some kind of conflict (well if the extension is working fine, don't worry )

[EDIT] now that I see it with less goofy eyes, I suggest the second one is just to be erased, totally useless


Here there is nothing weird

CODE

<!ENTITY advanced-options.102.tooltiptext "&advanced-options.101.tooltiptext;">
<!ENTITY advanced-options.103.tooltiptext "&advanced-options.101.tooltiptext;">
<!ENTITY advanced-options.104.tooltiptext "&advanced-options.101.tooltiptext;">

... I was only wondering if the sequence should not have been

<!ENTITY advanced-options.102.tooltiptext "&advanced-options.102.tooltiptext;">
<!ENTITY advanced-options.103.tooltiptext "&advanced-options.103.tooltiptext;">
<!ENTITY advanced-options.104.tooltiptext "&advanced-options.104.tooltiptext;">

I suspected some kind of copy/paste error, but you are the boss after all

[ericjung]

... I was only wondering if the sequence should not have been

<!ENTITY advanced-options.102.tooltiptext "&advanced-options.102.tooltiptext;">
<!ENTITY advanced-options.103.tooltiptext "&advanced-options.103.tooltiptext;">
<!ENTITY advanced-options.104.tooltiptext "&advanced-options.104.tooltiptext;">

Yes, it looks suspicious, but it is OK--I checked again to make sure. Thank you for being so diligent!

[EDIT] now that I see it with less goofy eyes, I suggest the second one is just to be erased, totally useless smile.gif

Yes, you are right! This is a copy-paste error. Should I upload new version?

[Goofy]

Yes, you are right! This is a copy-paste error. Should I upload new version?

mmmh not necessary for the moment (if your xpi is working as it is), wait to have more changes for an update I should say

[ericjung]

mmmh not necessary for the moment (if your xpi is working as it is), wait to have more changes for an update I should say

ok.

[teo]

p.s. teo--welcome. i see you have registered for the Polish translation. I hope we can work well together this time

I hope also.
Now you don't wrote files in one line.
And now mine first remark.
I saw that will be problem with BabelZilla. WTS when file is downloaded changed all '<' and '>' characters to HTML code
These characters are using in the HTML entities.

[ericjung]

I saw that will be problem with BabelZilla. WTS when file is downloaded changed all '<' and '>' characters to HTML code
These characters are using in the HTML entities.

Can you give an example? You mean in DTD file or properties file?

Thanks,
Eric

[ericjung]

Can you give an example? You mean in DTD file or properties file?

Thanks,
Eric

Nevermind. This is being discussed here, too, and Mauro has provided an example. I wish WTS was smarter

[Goofy]

Sure DTD files don't like HTML tags!

From what I have seen, I know only a safe solution which is also a bit tedious. You should leave every html tag in the xul file and slalom around them with entities.
A simple example here :

Initial line 48 in tips.xul

CODE

<li>The order of the characters affects what is generated! Using <b>0123456789abcdef</b> creates different passwords<br/>than using <b>abcdef0123456789</b>"></li><br/>

Final line 48 in tips.xul

CODE

<li>&tip7.1;&nbsp;<b>0123456789abcdef</b>&nbsp;&tip7.2;<br/>&tip7.3;&nbsp;<b>abcdef0123456789</b>"></li><br/>

(Note the addition of non-breaking spaces)

Corresponding entities in the related *.dtd

CODE

<!ENTITY tip7.1 "The order of the characters affects what is generated! Using">
<!ENTITY tip7.2 "creates different passwords">
<!ENTITY tip7.3 "than using"

[Goofy]

No answer? OK I will make it myself

In this attached version  passwdmakerGoofy_OK_1.7b1.xpi   182.64KB   1 downloads you have only two parts changed:

in the tips.xul
now it looks like that

CODE

<p>&tip1.1;<br/>&tip1.2;
<br/><br/>
<ul>
<li>&tip2.1; <b>0123456789abcdef</b>.</li><br/>
<li>&tip2.2; <b>&tip2.3; </b><br/>&tip2.4; <b>&tip2.5;</b>.</li><br/>
<li>&tips.003.innerHTML;</li><br/>
<li>&tips.004.innerHTML;</li><br/>
<li>&tips.005.innerHTML;</li><br/>
<li>&tips.006.innerHTML;</li><br/>
<li>&tip7.1; <b>0123456789abcdef</b> &tip7.2; <br/>&tip7.3; <b>abcdef0123456789</b></li><br/>
<li>&tip8.1; <a onclick="passwordMaker.openAndReuseOneTabPerURL('http://en.wikipedia.org/wiki/Diacritic');" style="color: blue; cursor: pointer" href="">&tip8.2; </a>&tip8.5;  Ã¢, Ã¥, ç), <a onclick="passwordMaker.openAndReuseOneTabPerURL('http://en.wikipedia.org/wiki/Diaeresis');" style="color: blue; cursor: pointer" href="">&tip8.3; </a>&tip8.5;  Ã¼, ä, ë),<br/><a onclick="passwordMaker.openAndReuseOneTabPerURL('http://en.wikipedia.org/wiki/Ligature_%28typography%29');" style="color: blue; cursor: pointer" href="">&tip8.4; </a>&tip8.5; Æ, Å“, ß), &tip8.6;© ® â„— !@#$%^&amp;*(){};), &tip8.7;<br/>&tip8.8;<br/>&tip8.9; <br/>&tip8.10;<br/>&tip8.11;<b>&#xfe;</b>.</li>
</ul>

and in the passwdmaker.dtd (en-US only) you now have this

CODE

<!ENTITY tip1.1 "The characters field contains the list of characters used in generating this password.">
<!ENTITY tip1.2 "Here are some tips to follow when selecting characters:">
<!ENTITY tip2.1 "If you require passwords compatible with PasswordMaker 0.6 and before, you must use">
<!ENTITY tip2.2 "If your passwords are missing leading zeros which existed in 0.6, try using the hash algorithm">
<!ENTITY tip2.3 "MD5 Version 0.6">
<!ENTITY tip2.4 "or">
<!ENTITY tip2.5 "HMAC-MD5 Version 0.6">
<!ENTITY tips.003.innerHTML "A minimum of two characters is required">
<!ENTITY tips.004.innerHTML "Characters can be repeated">
<!ENTITY tips.005.innerHTML "Using the same character more than once causes that character to appear more often in the generated password">
<!ENTITY tips.006.innerHTML "The more unique characters that are specified, the greater the variety of characters in the generated password">
<!ENTITY tip7.1 "The order of the characters affects what is generated! Using">
<!ENTITY tip7.2 "creates different passwords">
<!ENTITY tip7.3 "than using">
<!ENTITY tip8.1 "You can specify non-English characters like those with">
<!ENTITY tip8.2 "diacritical marks">
<!ENTITY tip8.3 "diaeresis marks">
<!ENTITY tip8.4 "ligature marks">
<!ENTITY tip8.5 "(e.g.">
<!ENTITY tip8.6 "non-alphanumeric characters and symbols (e.g.,">
<!ENTITY tip8.7 "etc. If a">
<!ENTITY tip8.8 "character you desire does not appear on your keyboard, don't fret. Most every Western character can be created by">
<!ENTITY tip8.9 "typing ALT-, OPTION-, or CTRL-code key sequences. The key sequences vary by operating system. For example,">
<!ENTITY tip8.10 "typing ALT+0222 in Windows (numbers must be typed on the numeric keypad) yields the Icelandic upper-case Thorn">
<!ENTITY tip8.11 "character:">

One bugreport: in this version as well as in your original one, the 3 links to wikipedia (diacritic etc.) are non-functional

[teo]

I also played with this extension for resolve problem with html in entities. I totally rebuilt 'tips.xul' file and all entities for this file in the 'passwdmaker.dtd' file. I changed 'passwdmaker.css' file and built new 'tips.js' file. Now we haven't html in the entities, translators can adjust one's wikipedia links and text is matching to window size.
All files are in the attached file.
For tests please install extension on new blank profile or remove from 'localstore.rdf' file size window parameters for tips window.

I think we have to play with another window for better matching size to translations.

Attached Files

•  PasswordMaker.zip   9.24KB   6 downloads

[ericjung]

...and yet another implementation at http://forums.passwordmaker.org/index.php/...html#msg1280190
Goofy & Teo: how do you like it?

[Goofy]

Wow solutions everywhere !

Well, as I cannot judge about code I will state my opinion as a translator and from I have seen I must say that I prefer Teo's proposition.
(*though it seems not fully functional: I have tried to test but encountered that probable css issue on the extended settings dialog )  pwmakerTeo.png   26.54KB   10 downloads)

Reasons why I think a html in a locale is not such a good idea :

1. Even though you removed a certain number of tags, translators would have to slalom around "strange" things such as <li>, <ul> and <a href. . Of course it is nothing for old translators like me, but one big idea of BabelZilla is to make translation an easy non-technical game. Translators are not supposed to be coders, and they are allowed to ignore javascript, xul and even html. They should concentrate on what they are required for: translation.
So I would prefer to spare them the handling of an html file: use the proper html editor that will not break the encoding, beware not to translate what should not be, beware not to delete one closing tag here and there etc.

2. The size of an html file in every locale (and you know that this extension will probably get more than 20 language subfolders) is more important than the .dtd with corresponding strings. 20 times a small difference becomes significant difference.

If you stick to your idea the solution could be (my little howto here):
- have one .Xhtml file in the content
- entitize its strings
- drop the entities and strings in the locale .dtd file

About your reluctance to modify your plans to match wts limitations: you are right of course You should not lose your time trying to adjust good work to annoyances, I understand perfectly. Note that the next version of the WTS will allow to edit html online (as html code, so it is not as good as wysiwyg for non-geek translators)

So I think in this case Teo's solution (*IF it matches code standards and is functional) can be better. My 2 GoofyCents.

[teo]

So I think in this case Teo's solution (*IF it matches code standards and is functional) can be better. My 2 GoofyCents.

Thanks Goofy. You know, I'm translator but I like some play with code. Your bug isn't caused by mine changes.
1. As Goofy wrote - extension (if developer want internationalize them) should easy for translation. IMHO mine proposal is easy for translation and translator without any problem can adjust one's links to explain some terms.
2. IMHO size all dialog and information windows should matching to all translation without translator or user intervention.
These two ideas conducted my work.

Eric,
If in this case you decide leave html, your proposal is good, but I don't like iframe .

[ericjung]

OK, we will use Teo's approach. Teo, where are the #passwordmaker-button and #passwordmaker-key-button styles specified in passwordmaker.css used? in tips.xul? I don't see them. Another XUL file? You only included tips.xul.

[teo]

OK, we will use Teo's approach. Teo, where are the #passwordmaker-button and #passwordmaker-key-button styles specified in passwordmaker.css used? in tips.xul? I don't see them. Another XUL file? You only included tips.xul.

Eric,
I added style for link only . These styles was in the file. Now I'm playing with 'advanced-options.xul' and 'basic-options.xul' files.

[Goofy]

I added style for link only . These styles was in the file. Now I'm playing with 'advanced-options.xul' and 'basic-options.xul' files.

OMG who'll ever stop teo?

Please cool down teo, otherwise you will rewrite the entire extension. Seriously, you should wait a bit things are carefully tested with your last patch, (see some minor issues here )and moreover be more precise with the changes you made, because it may be a bit confusing. At last, don't take for granted the developer has to change things according to your suggestions (which are often pretty smart I reckon)