Resource property files ignores systems file
encoding and uses always ISO-8859-1.
This is a problem because developers want to have
properties source files in the languages enconding
(e.g ISO-8859-7 for greek properties files) and
using native2assii transform this files to unicode
for the build distribution.
This is rather an enhancement than a defect. According to the
specification of routines for reading and writing of properties,
.properties files are always saved using ISO-8859-1.
We will try to implement this enhancement.
*** Issue 69075 has been marked as a duplicate of this issue. ***
If the properties file is opened using "Open", then any non-latin1 characters
are converted to unicode sequences as in \u017C. However if it is opened using
"Edit", any such characters are lost (converted to ?). The "Edit mode" editor
should perform the same conversion.
The spec forces ISO-8859-1 + escapes for the physical storage. (Alas. Would have
been far better to specify UTF-8. Too late.) But the editor could show the real
*** This issue has been marked as a duplicate of 32392 ***