On Mon, 19 May 2008, Piller Sébastien wrote: > I have a problem with the encoding of some text, on my deployment server > (Unix/Linux). I use wicket to generate the body of emails, with this code: ... > But on the production server, it seems that the email is converted to > ISO8859-1 (and special chars are not rendered properly in UTF8). But > others web pages are properly rendered (I only have a problem when > dealing with responses)
What are the locales of the machines (or the users running the server software on the machines)? I think that by default, Java assumes the character encoding it gets from the operating system, but you can override it by explicitly setting the relevant system property, -Dfile.encoding=utf-8 or something like that. The root problem is that property files are plain text files that do not contain any metadata such as what encoding they are written in, so anybody reading them just needs to assume something. The same goes for Java source files. The problem of property files is partially solved by using property XML files, though it is a pity to lose the nice, simple property file syntax with the change. > Have you guys any idea on how to fix it? Do I have to do someting on the > server config? locale -a And debugging the file encoding system property of Java in each cases are good places to start. I don't believe that this is Wicket related. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]