By my reading of Java history, the notion that a Java properties file
must be encoded in ISO 8859-1 is a remnant from the days before the Java
SE 1.6 specification. Given that 1.6 has been with us for 6 years now -
in fact it is so old that it is being end-of-lifed this month - I'd
suggest
By my reading of Java history, the notion that a Java properties file must be
encoded in ISO 8859-1 is a remnant from the days before the Java SE 1.6
specification. Given that 1.6 has been with us for 6 years now - in fact it is
so old that it is being end-of-lifed this month - I'd suggest it is
For property files that are expected to have international characters,
the problem with using ISO-8859-1 is that a great many of those
characters require \x escape sequences, and that makes the text
unreadable to the human eye, so then you need some special editor
support (e.g. a plugin).
As i
Tapestry expects UTF-8.
Which is fine for file types defined by Tapestry.
Eclipse handles UTF-8 just fine. Eclipse can be set to default to UTF-8
for templates and properties:
Preferences > General > Content Types > Text > HTML > *.tml
Preferences > General > Content Types > Text >
Hi Johan,
I don't understand why you've interpreted the javadoc in that way. Here are
some things to consider:
Tapestry expects UTF-8. Eclipse handles UTF-8 just fine. Eclipse can be set to
default to UTF-8 for templates and properties:
Preferences > General > Content Types > Text > HT
Have you encoded you file into utf8?
Java properties files must never be encoded using UTF-8. The encoding for
Java properties files is always the same: ISO-8859-1 with Unicode escapes.
Your editor must convert any characters not in ISO-8859-1 to Unicode
escapes.
See the Javadoc of "Prop
