Recommended Addon

[Goofy]

hello all

As everyone, I still have encoding problems from time to time. Even if I can avoid most of them by experience, I am very ignorant about ANSI, UTF8 (to which I have a superstitious fervor) and whatsoever weird things
Sometimes I am proud to find the bug and to have spent hours for a "&" in a locale file..
Sometimes I am ashamed of having destroyed the ja-JP locale of a babelZillian friend, just with opening/closing a file with Pspad set for UTF8

So... Some of you seem to know much about that, some others are real hackers, some are dedicated to sorcery code ...

so please post your tricks and tips and knowledge here !

[Luana]

- dear MatrixIsAllOver, I have read frequently your messages about using ANSI, and I never really tried, not that I don't trust you  , but I thought it was compulsory to use utf-8. Can you confirm nothing strange happens for the extension when your locale is in ANSI ? (I suppose it is for the .properties file, what with the contents.rdf and the .dtd ? )
[right][snapback]1737[/snapback][/right]

Dear Goofy,
I can confirm that the following quoted method works really fine

I try to explain better using an Italian example:
In case I have to translate "it will open" I start my translation using UTF8 encoding, therefore I'll write "aprirà", but before saving the file I'll change the encoding to ANSI-> "aprirà "; and this method works fine! 

NOTE: ANSI is 8-BIT, and not UNICODE !!!
E.g.>>In the above example "it will open" using UTF-8 encoding becomes "aprirà", using ANSI-> "aprirà " and using * UNICODE "aprir\u00E0"
* I use UNICODE (& PsPad) when I have to localize properties file!

Naturally, only if you try you may confirm yourself too

Regards