Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

hard coded strings in seamonkey?

0 views
Skip to first unread message

Tsahi Asher

unread,
May 7, 2006, 6:15:36 PM5/7/06
to
hi,
i noticed that the Roaming User category in the prefs, and the Report
Broken web site in the Help menu, are not translated in the language
pack i'm working on (and will be releasing shortly). are these strings
hard coded?
--
Tsahi Asher
Hebrew L10n Team
http://www.mozilla.org.il

Cédric Corazza

unread,
May 7, 2006, 5:34:22 PM5/7/06
to
Tsahi,

No, these strings are localizable.
Check your 'installed-chrome.txt' file. Here is the problem IMO.
This line should be like :
locale,install,url,jar:resource:/chrome/ab-CD.jar!/locale/ab-CD/sroaming/
and not like :
locale,install,url,jar:resource:/chrome/sroaming.jar!/locale/ab-CD/sroaming/
Same thing for reporter

Cédric

Tsahi Asher

unread,
May 7, 2006, 7:25:29 PM5/7/06
to
ציטוט Cédric Corazza:

so should i add the content of sroaming.jar and and reporter.jar to my
ab-CD.jar, and translate them?

Cédric Corazza

unread,
May 7, 2006, 6:42:43 PM5/7/06
to
Yes,
you could have a look at our .xpi, if it can help :
http://prdownloads.sourceforge.net/frenchmozilla/seamonkey-1.0.1.fr-FR.langpack.xpi?download

Cédric

Ricardo Palomares Martinez

unread,
May 7, 2006, 6:11:44 PM5/7/06
to
Cédric Corazza escribió:


Not just this, if you instruct sroaming and reporter to look into
ab-CD.jar for their locales, it would also be a good idea to actually
put their locales into ab-CD.jar. :-) IOW, you must extract
locale/en-US/sroaming/* and locale/en-US/reporter/* in the same
directory structure than en-US.jar. Alternatively, if you use Mozilla
Translator, you may merge the locales in a "expanded" en-US.jar.

For that, I copy all JARs into the MT directory for the product and
version I'm working on (in this case ~/MT/seamonkey/1.0, as no changes
should exist between 1.0 and 1.0.1) and run a small bash script like this:

--Start of File--
#!/bin/sh

EXTRAS="chatzilla
inspector
reporter
sroaming
venkman"

echo "This script must be run in the directory where en-US.jar and the
JAR: $EXTRAS are to be found"

mkdir tmp
cd tmp
unzip -q ../en-US.jar
mv -f ../en-US.jar ../en-US.old

for extra in $EXTRAS
do
echo "- Processing $extra"
unzip -q ../${extra}.jar locale/en-US/${extra}/*
done

echo "Recreating en-US.jar"
zip -q -D -r ../en-US.jar *
cd ..
rm -rf tmp

--End of File--

It's not more than a "commodity", but it saves quite a few keystrokes. :-)

HTH

--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?

Cédric Corazza

unread,
May 7, 2006, 7:33:52 PM5/7/06
to
Yes Ricardo,
that's another option. We chose to put those files in ab-CD.jar for
convenience, but what you proposed should work too.

Tsahi Asher

unread,
May 10, 2006, 6:12:39 PM5/10/06
to
ציטוט Cédric Corazza:
what are the files under fr-FR.jar!locale/fr/reporter? i see other files
under locale/fr-Fr/reporter.

Cédric Corazza

unread,
May 10, 2006, 5:23:00 PM5/10/06
to
Our locale in Firefox changed from fr-FR to fr only. That way, both
Chrome paths are handled. It's the same for inspector, I believe.
Frankly, I'm not sure this is useful, but I'm not the one who did that.
I will search for information about that and tell you.
0 new messages