3.2 does not convert source file encoding [message #166595] |
Tue, 22 August 2006 03:55  |
Eclipse User |
|
|
|
Eclipse 3.1 did some magic with the source file encoding so files were
encoded in ISO-8859-1, but local characters of Polish language were still
available and dispayed properly in program.
Eclipse 3.2 does not it only displays "File cant be saved in
ISO-8859-1/**/" message, and asks me to remove all unsupported characters
- but I like very much my unsupported characters! Is there a way to enable
3.1 like behaviour? Because if not I think it's a bug.
|
|
|
|
Re: 3.2 does not convert source file encoding [message #166609 is a reply to message #166603] |
Tue, 22 August 2006 05:40  |
Eclipse User |
|
|
|
>> Eclipse 3.1 did some magic with the source file encoding so files were
>> encoded in ISO-8859-1, but local characters of Polish language were
>> still available and dispayed properly in program. Eclipse 3.2 does not
>> it only displays "File cant be saved in ISO-8859-1/**/" message, and
>> asks me to remove all unsupported characters
> That's the only correct behavior because previously some of those
> unsupported characters might have gotten lost on save i.e. you lost work.
OK. I understand that smarter people than me said it is dangerous. But no
such thing happened to me.
>> - but I like very much my unsupported characters! Is there a way to
>> enable 3.1 like behaviour?
> You can of course change the encoding for the file, folder or all
> *.properties files to some other encoding but it means that your Strings
> might show up corrupted when running because the Java VM will use
> ISO-8859-1 to read them in. You should not do this - instead encode your
> local characters correctly in the properties file, read
> http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties .html#encoding
> for more info.
Well I didn't get the hint.. Are you sure that this is a proper link? Word
encoding in that file occurs only three times and only to suggest to use
ISO encoding or native2ascii. Is there any way to have polish chars in
Java program, that doesn't require either calling native2ascii on every,
or manually adding these hideous escape chars?
|
|
|
Powered by
FUDForum. Page generated in 0.06473 seconds