Thanks a lot for your answer, it helped me.
Here is my confusion:
- For T3 you cannot set messages encoding. Messages are java
properties that must be only in SO 8859-1 and therefor you must use a
tool like native2ascii to convert japanese text or the excellent
propedit
- For T4 you can set messages encoding and write your messages in
plain utf-8 no need for native2ascii
Thanks
Numa
Le 7 mai 06 à 03:17, Nick Westgate a écrit :
Hi Numa.
I have tried to set the property ' <property
name="org.apache.tapestry.messages-encoding" value="UTF-8"/>' in my
component or page specification but this still doesn't work i get the
same cabalistic characters.
I'm using T3 for Japanese, and don't set "messages-encoding".
I don't know if i have to do the same as for ResourcesBundle
properties file and convert them using native2ascii or do i have to
specify another encoding and encode my file in another character set?
I use tapestry 3 and here is snapshot of my .application:
Java properties files should be only ISO 8859-1 encoded, so yes,
you just need
to use native2ascii or similar. I use the following Eclipse plugin
to edit my
Japanese property files - it's much easier:
http://propedit.sourceforge.jp/index_en.html
Cheers,
Nick.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
