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 appropriate and safe to let go of that notion, perhaps on
a project-by-project basis.
Besides, let's face it, ISO 8859-1 was a pretty narrow-minded choice in
the first place.
It was not a narrow-minded choice. The original encoding was not
"ISO-8859-1" but "ISO-8859-1 *with* Unicode escapes". Java properties have
always been capable of storing all Unicode characters.
Unfortunately the JDK developers decided that it is okay for everyone to
choose their own encoding. Another file format that was interpreted
exactly the same in all runtime environments independent of user settings
down the drain.
Tapestry chose to use UTF-8 for properties files, so my previous comments
can be ignored.
--
Regards, Johan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
