Kalle,
I just made the test on my app, since I had a char encoding problem for
about a week with 5.0.14-SNAPSHOT, and had to fallbacl to 5.0.13. So
yes, accented chars in ISO-8859 properties files are not rendered
properly in the final HTML page. If you switch the coding of that
property file to UTF-8, things are ok.
Now I need to find out how to tell Eclipse to create UTF-8 property
files by default...
José
Kalle Korhonen a écrit :
Does it mean that the old-school (name-value, not xml) property files for
Tapestry now *have to be* encoded in UTF-8 rather than the standard Latin-1?
Kalle
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]