PasswordMaker - Ver. 1.7b8, Updated: 21/09/07 01:56 Options

[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

This post has been edited by grimholtz: Sep 21 2007, 00:56

[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.54K ) Number of downloads: 10
)

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)

[teo]

Goofy,
These problems are Mauro's problems. I tested mine changes on new blank profile on Fx 2.0.0.4 EN and PL version with extension downloaded from BabelZilla and all working properly. Links are opens in new tabs in the browser. Do you have any problems with French version?
See how tips window looks in the English and Polish window.

Edit: What you tell me now? Goofy!

Attached File(s)

 pm1.png ( 16.81K ) Number of downloads: 6
 pm2.png ( 18.37K ) Number of downloads: 6