Breakage of Translate Toolkit-driven localizations due to *2
Filip Miletic
A key reporterMenu.title was replaced by reporterMenu.title2 in
en-US/extensions/reporter/chrome/reporterOverlay.dtd
However, the keys reporterMenu.tooltip and reporterMenu.accesskey stayed.
This confuses Translate Toolkit, who no longer knows how to auto-match a
text with corresponding title.
NB: Translate Toolkit uses the .accessKey convention to offer
translators something like:
msgid "&Report broken web site..."
msgstr ""
From the fragment:
<!ENTITY reporterMenu.title "Report broken web site...">
<!ENTITY reporterMenu.tooltip "R">
Now, by adding the *2 to the end of the title, the Translate Toolkit is
screwed, and with it the people who maintain the l10n (and by the way do
that very efficiently thanks to TT!).
Is it really necessary to do this gymnastics? Stopping would be much
appreciated, thank you. NHF, just to let you know that although you
are in charge, it's more important to also be nice to your fellow
l10nizer...
f
