AW: [displaytag-user] displaytag.properties and character encoding

[Martin Kindler]

Title: Nachricht

Hi George,   I am not sure about Displaytag, but as Java has the same problem with its resource files, I would expect it to be the same reason. Java only allows ISO-8859 encoding in its resource files, so including unicode characters means tons of \uxxxx encodings :-).   Martin -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Georgovassilis George Gesendet: Dienstag, 24. Januar 2006 11:27 An: displaytag-user@lists.sourceforge.net Betreff: [displaytag-user] displaytag.properties and character encoding Dear All   I’ve run into trouble with displaytag 1.0 and character encoding for the displaytag.properties. When displaytag is to read the localised basic.msg.empty_list property from displaytag_el.properties it is reproduced with a wrong encoding. From the output result I guess it expects the file encoding to be ISO-8859-1, while in fact it is UTF-8 since every foreign character in the file is represented with two characters in the output. In contrast, resources from the spring message bundles (i.e. in the <displaytag:column titleKey=”…”/> are displayed correctly but I understand that currently it is not possible to populate the basic.msg.empty_list property from the spring resource bundles.   Thanks George   My setup: Tomcat 5.5 Java 1.5 Spring 1.2.6