properties nightmare

Build 3353 always loads properties files as ascii encoding.
Destroys all my non-ascii characters on save.

Just had some fun reverting changes from CVS - yeah, I know it's my fault using an EAP version, ...

http://www.jetbrains.net/jira/browse/IDEA-2324

(I think many users only convert properties file to ascii with ant when building installers, or even load properties files with a custom loader.)

1 comment
Comment actions Permalink

That was a consequence of fixing this bug:
http://www.jetbrains.net/jira/browse/IDEADEV-1237

However, as I've found that too many people :) store properties files in
non-ISO8859 encoding (as standard suggests), other possibilities are
discussed there.
In particular, I'm leaning to introduce separate setting "Use this encoding
for properties files by default:".
Please post your suggestions there.

--
regards,
--
Alexey Kudravtsev
Software Developer
JetBrains, Inc, http://www.jetbrains.com
"Develop with pleasure!"

"Stephen Kelvin" <mail@gremlin.info> wrote in message
news:10463689.1117547842026.JavaMail.javamailuser@localhost...

Build 3353 always loads properties files as ascii encoding.
Destroys all my non-ascii characters on save.

>

Just had some fun reverting changes from CVS - yeah, I know it's my fault
using an EAP version, ...

>

http://www.jetbrains.net/jira/browse/IDEA-2324

>

(I think many users only convert properties file to ascii with ant when
building installers, or even load properties files with a custom loader.)



0

Please sign in to leave a comment.