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
so should i add the content of sroaming.jar and and reporter.jar to my
ab-CD.jar, and translate them?
Cédric
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?