Just as a reference:
In Tapestry 4 the property files no longer need to be ASCII -- Tapestry
implements its own parsing that is backward compatible with the Java
one, but allows it to be based on other encodings if needed.
Please read this for details:
http://jakarta.apache.org/tapestry/UsersGuide/localization.html
(just to mention: nice description Howard :)
I am actually guessing that the problem may not be in the property
files, but in your template encodings.
Please place something like this in your .application file:
<meta key="org.apache.tapestry.template-encoding" value="ISO-8859-1"/>
Replace the encoding above with the one you use for the templates. That
would also resolve any property problems as well, actually, since the
encoding of the propery files defaults to the template encoding, unless
specified separately.
I hope this helps,
-mb
P.S. Please note that in Tapestry 3 the above line is
<property name="org.apache.tapestry.template-encoding" value="ISO-8859-1"/>
and the property files still require native2ascii
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
