The basic JVM and Java feature (independent of Tapestry or any other
framework) as we all know that every character is represented as two
bytes, it means as soon as byte-to-character conversion happened
characters can't be truncated anymore inside JVM.
The major points where data loss can happen
This is somewhat intersting to me.
This is the expected, usual, Java behavior (the .properties files must be in
ISO 8895-1 encoding); but I thought I read somewhere that T5 allowed one to
store the .properties files in UTF-8 encoding. Does this imply that is not
so, or perhaps this just has
I'm using message properties files in UTF-8 with russian symbols, for
T4 it's work, but T5 it's not work - russian symbols is damaged
Also problem with @ApplicationState, after save state and back to form,
russian as well is damaged
Hi,
you have 2 possibilities: either convert your property files into
native-encoded characters or start you server in UTF-8 mode.
http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/native2ascii.html
On 7/7/07, Foror [EMAIL PROTECTED] wrote:
I'm using message properties files in UTF-8 with
Have you tried this:
http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding
This will ensure that pages served by Tapestry are UTF8 encoded. For me
this was enough to make T5 serve German UTF8 characters correctly.
Uli
Foror schrieb:
I'm using message properties files in UTF-8 with russian
