<label value="This password was generated using the default account"/>
<hbox>
<label value="settings. Use the"/>
<label style="margin-left: -1px; margin-right: -1px; color: blue; cursor: pointer"
value="Advanced Options" onclick="onOptionsDialogButton('advanced');"/>
<label id="lastVisibleElement" value="to change them."/>
</hbox>
<vbox>
<label id="warningLbl" value="This password was generated using the default account settings."/>
<label id="lastVisibleElement" value="Use the Advanced Options to change them." style="color: blue; cursor: pointer" onclick="onOptionsDialogButton('advanced');"/>
</vbox>
var unicodeConverter = Components.classes["@mozilla.org/intl/scriptableunicodeconverter"].createInstance(Components.interfaces.nsIScriptableUnicodeConverter);
unicodeConverter.charset = "UTF-8";
this.data = unicodeConverter.ConvertToUnicode(this.data) + unicodeConverter.Finish();
extLocaleNames: ['en-US'], // e.g. ['en-US', 'en-GB']
extLocaleNames: null, // e.g. ['en-US', 'en-GB']
extLocaleNames: ['en-US','pt-BR'], // e.g. ['en-US', 'en-GB']
advanced-options.xul:
(passwdmaker.dtd)
<!ENTITY advanced-options.101.label "Store Master Password Fingerprint for all accounts">
<!ENTITY advanced-options.101.tooltiptext "This is used to validate that future master passwords typed here match this master password.">
<!ENTITY advanced-options.102.label "Store Master Password Fingerprint for selected account">
<!ENTITY advanced-options.102.tooltiptext "This is used to validate that future master passwords typed here match this master password.">
<!ENTITY advanced-options.103.label "Master Password Fingerprint for selected account">
<!ENTITY advanced-options.104.label "Default Master Password Fingerprint">
passwordprompt.js:
(passwdmaker.properties)
passwordprompt.onOK.03=The master password is not correct.
passwordMakerOverlay.js:
(passwdmaker.properties)
passwdmakerOverlay.generatepassword.03=Master Password matches stored fingerprint
passwdmakerOverlay.generatepassword.04=Master Password doesn't match stored fingerprint
passwdmakerOverlay.generatepassword.05=Master Password fingerprint is not stored on disk
textLocaleNames: null, // e.g. ['en-US', 'en-GB'].
I will translate the new strings, as well.
<br/>
,then BabelZilla converts it to:<br/>
That results in the HTML tag being shown on PasswordMaker window instead of a line break.<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/>
<li>&tip7.1; <b>0123456789abcdef</b> &tip7.2;<br/>&tip7.3; <b>abcdef0123456789</b>"></li><br/>
(Note the addition of non-breaking spaces)<!ENTITY tip7.1 "The order of the characters affects what is generated! Using">
<!ENTITY tip7.2 "creates different passwords">
<!ENTITY tip7.3 "than using"
I beg you pardon, but doing that can make difficult translating to some languages that don't use the same word order as English. Don't you think?
I would suggest removing the bold tags and anchor tags, which I think are not needed. As for the break-line tag, I think we can create one entity for each line.
What do you think?
Note, the way install.js is setup, the dtd and properties files should be in a passwdmaker subdirectory of the locale.I will fix install.rdf so it doesn't have the extra passwdmaker subdirectory (or you can do it if you like, it's a simple change and you have SVN commit privs).
Eric, if you allow me access to subversion, I will make the changes.I need your userid on SourceForge. That is where Subversion is hosted for PasswordMaker.
I need you to decide what to do about the HTML tagsI think we should go with Goofy's suggestion, but I don't really care one way or the other. I like Goofy's suggestion more only because it allows us to use HTML markup in strings. With the solution you propose, we are a little more restricted in the future. I will leave it to you to decide, Mauro.
I need your userid on SourceForge. That is where Subversion is hosted for PasswordMaker.My userid on SourceForge is 1840283 and my username is sjoruam.
I think we should go with Goofy's suggestion, but I don't really care one way or the other. I like Goofy's suggestion more only because it allows us to use HTML markup in strings. With the solution you propose, we are a little more restricted in the future. I will leave it to you to decide, Mauro.I have another solution. Instead of changing the DTD file, how about we change "tips.xul" file so that it converts the HTML tags properly?
<script type="application/x-javascript" src="chrome://passwdmaker/content/utils.js"/>
<xul:hbox style="margin: 1em;">
<p>
&tips.001.innerHTML;
<br/><br/>
<ul>
<li>&tips.002.innerHTML;</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>&tips.007.innerHTML;</li><br/>
<li>&tips.008.innerHTML;</li>
</ul>
</p>
</xul:hbox>
<script type="application/x-javascript" src="chrome://passwdmaker/content/tips.js"/>
<xul:hbox style="margin: 1em;">
<p>
<span id="001">&tips.001.innerHTML;</span>
<br/><br/>
<ul>
<li id="002">&tips.002.innerHTML;</li><br/>
<li id="003">&tips.003.innerHTML;</li><br/>
<li id="004">&tips.004.innerHTML;</li><br/>
<li id="005">&tips.005.innerHTML;</li><br/>
<li id="006">&tips.006.innerHTML;</li><br/>
<li id="007">&tips.007.innerHTML;</li><br/>
<li id="008">&tips.008.innerHTML;</li>
</ul>
</p>
<script language="javascript">
document.getElementById("001").innerHTML = decodeHTML(document.getElementById("001").innerHTML);
document.getElementById("002").innerHTML = decodeHTML(document.getElementById("002").innerHTML);
document.getElementById("003").innerHTML = decodeHTML(document.getElementById("003").innerHTML);
document.getElementById("004").innerHTML = decodeHTML(document.getElementById("004").innerHTML);
document.getElementById("005").innerHTML = decodeHTML(document.getElementById("005").innerHTML);
document.getElementById("006").innerHTML = decodeHTML(document.getElementById("006").innerHTML);
document.getElementById("007").innerHTML = decodeHTML(document.getElementById("007").innerHTML);
document.getElementById("008").innerHTML = decodeHTML(document.getElementById("008").innerHTML);
</script>
function decodeHTML(html) {
return html.replace(/</g, "<").replace(/>/g, ">");
}
<!-- tips.xul -->
<?xml-stylesheet href="chrome://global/skin/global.css" type="text/css"?>
<!DOCTYPE window SYSTEM "chrome://passwdmaker/locale/passwdmaker.dtd">
<dialog
id="passwordmakeraccountsettings"
windowtype="passwordmaker"
title="&tips.window.title;"
orient="vertical"
xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
persist="screenX screenY width height">
<iframe src="chrome://passwdmaker/locale/character-tips.html" flex="1" style="border: 1px black solid"/>
</dialog>
<!-- chrome://passwdmaker/locale/character-tips.html -->
<style>
* {
font-size: x-small;
font-family: verdana, sans-serif;
}
li {
margin-bottom: 1em;
}
a {
color: blue;
cursor: pointer
}
</style>
<p>
The characters field contains the list of characters used in generating this password.
Here are some tips to follow when selecting characters:
</p>
<ul>
<li>If you require passwords compatible with PasswordMaker 0.6 and before, you must use
0123456789abcdef. If your passwords are missing leading zeros which existed in 0.6,
try using the hash algorithm MD5 Version 0.6 or HMAC-MD5 Version 0.6.</li>
<li>A minimum of two characters is required</li>
<li>Characters can be repeated</li>
<li>Using the same character more than once causes that character to appear more often in the generated password</li>
<li>The more unique characters that are specified, the greater the variety of characters in the generated password</li>
<li>The order of the characters affects what is generated! Using 0123456789abcdef creates different passwords than using abcdef0123456789</li>
<li>You can specify non-English characters like those with
<a href="http://en.wikipedia.org/wiki/Diacritic">diacritical marks</a> (e.g., â, å, ç),
<a href="http://en.wikipedia.org/wiki/Diaeresis">diaeresis marks</a>,
(e.g., ü, ä, ë),
<a href="http://en.wikipedia.org/wiki/Ligature_%28typography%29">ligature marks</a>,(e.g., Æ, œ, ß),
non-alphanumeric characters and symbols (e.g., © ® ℗ !@#$%^&*(){};), etc. If a character you desire does not appear on your keyboard,
don't fret. Most every Western character can be created bytyping ALT-, OPTION-, or CTRL-code key sequences. The key sequences vary by operating system.
For example, typing ALT+0222 in Windows (numbers must be typed on the numeric keypad) yields the Icelandic upper-case Thorn character: þ.
</li>
</ul>
Here is what I committed to SVN. Please let me know if you think this is OK. This idea is different from both Goofy's and Mauro's. tips.xul is now a thin container for chrome://passwdmaker/locale/character-tips.html. Each locale creates their own locale/**-**/character-tips.html.
Ok. So I will commit Teo's idea to SVN after testing in on Firefox.
However, I'm afraid I will not be able to do it today. Maybe tomorrow.
Eric, those changes proposed by Teo doesn't have anything to do with "tips.xul", does it?No, this has nothing to do with localization and tips.xul. Teo just like to work on GUI stuff.
Should I keep on removing the bolds and links?Yes, please.
Eric, yesterday I made the following changes to "passwdmaker.dtd":Yes, I will do that tonight as well as make just one button on the dialog.
- split of tips.001.innerHTML into tips.001a.innerHTML and tips.001b.innerHTML;
- removal of bolds, links and line breaks from tips.002.innerHTML, tips.007.innerHTML and tips.008.innerHTML.
I think we should now send them to BabelZilla and warn the translators about them.
How can we do that?
Eric, could you please upload the current version of "passwdmaker.dtd" file to BabelZilla? Thank you in advance.
Eric, could you please upload the current version of "passwdmaker.dtd" file to BabelZilla? Thank you in advance.
Hi Mauro, I'm not ignoring you. I'm adding some more code with new strings that need translation. Rather than upload the version right now to Babelzilla, I'd like to wait until I'm complete (this week) and upload it then. That way, translators will only have to translate one XPI. Hope you understand? If you'd like me to email the XPI to you directly, let me know... I can do that.
Eric