A bit of explanation:
Normally, property files are expected to be ISO-8559-1 encoded [1]. When there are characters that
can't be represented using that character encoding, unicode escapes must be used. The native2ascii
tool can convert property files from UTF-8 to ISO-8859-1.
Tapestry does the same reencoding transparently, i.e. it treats all property files as UTF-8 encoded
and automaticalle converts them to ISO-8850-1 with unicode escapes.
Uli
[1] http://java.sun.com/javase/6/docs/api/java/util/Properties.html
Am 21.10.2009 10:02 schrieb Stephan Windmüller:
Gunnar Eketrapp wrote:
What is the recommended encoding for text files within a T5 project.
UTF-8
I just read ...
Properties files are ISO-8859-1 by definition - see the docs for the
Properties
<http://java.sun.com/javase/6/docs/api/java/util/Properties.html>class.
Where do you read that? This is from the tapestry home page:
"Tapestry uses the UTF-8 charset when reading the properties files in a
message catalog."
http://tapestry.apache.org/tapestry5/guide/localization.html
How do you folks do?
Using UTF-8 for the property files.
Note: The issues I have is that eclipse keeps insisting that my .properties
files are ISO-8859 and I have to manually switch encoding
for each new property file i create or copy. Besides that's everyting works
fine ....
Same here. It is a bit annoying, but it works.
HTH
Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
