I know that hacking is not the better method to translate,
but it's now the only way.

I made it on 0.7sp1 with ResHacker.
I finish the same work on 0.8 always with ResHacker,
on km exe and kplugins dll.

I now have a problem with others files in chrome

What are the files to be translated?

*.properties ?
embed.jar ?
pip*.jar ?
install*.txt ?

If I take embed.jar:

content ?
locale ?
skin ?

If I now take locale\en-US
communicator ?
cookie ?
global ?
global-platform ?
navigator ?
navigator-platform ?
necko ?
pipnss ?
pippki ?

Which file types needed to be translated?
*.rdf ?
*.html ?
*.properties ?
*.dtd ?
*.xhtml ?

Is is a good method to tranlated en-US,
or is it a better way to add fr-FR for exemple
and to translate en-US files in it ?
Is it needed to update installed-chrome.txt ?
Updating installed-chrome.txt by replacing all
en-US by fr-FR or by adding references?

Which zipper is recommanded to build modified jar files?
no preference?
Packing methods seem to be classical (deflate, store) and seem
can be realized with a lot of zippers I know (Winzip, pkzip, 7-zip, ...)

I've begun to translate properties file, and it seems to have a problem with accenting.

If I put accented letter, the message is displayed until the letter before it.

I've tried to replace them with Html equivalents, it's not good.

Is there a way to put them in messages?