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 > Java Properties File >
*.properties
I never ever override the specifications of a file type for any project.
What if I have another project open that does stick to the specification?
If you go down this path then all languages work without further
thought, so I'd sincerely recommend it.
All languages will work without further thought if you stick to the
specification of Java properties files. Problems can be caused by one or
more of the following:
- Your IDE: it does not properly support Java properties files. It uses a
text editor that uses the default encoding of the user to store properties
files. Your IDE is essentially generating corrupt files. A better IDE or
an additional plug-in will fix that.
- Your API/framework: it does not properly read properties files.
You can see it working fine in all of JumpStart including the
localization examples.
It's not about whether it works in one particular situation or not. Not
adhering to a specification may break other applications/tools.
There is absolutely no need to muck around with the encoding of Java
properties files. It is very well defined. By using the correct tools and
APIs everything will work perfectly.
Note that Java 1.6 introduced additional methods that accept "Reader"s and
"Writer"s. A bad decision IMHO because the encoding of properties files
can now be anything instead of one fixed encoding.
--
Regards, Johan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
