-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Petersson ha scritto: > Hi Giulio > > If I understand you right you have a working configuration when you are > starting and running the G server in a UTF-8 environment. > You can check the encoding settings used by Geronimo via the console > JVM section. > To make sure the browser knows what encoding to expect you can add the > following to the beginning of the JSP files > <?xml version="1.0" encoding="UTF-8"?> > and/or > <meta http-equiv="Content-Type" content="application/xhtml+xml; > charset=UTF-8" /> > Encoding problem can be really tricky especially if the text sources > also are fetched from a database where double encoding can be a issue. > I hope this helps. > /Peter >
The problem is not the browser. All pages have the right request / response setter to the correct character set (UTF-8). As I said dynamic content from db is displayed correctly. The problem is JSP compilation. I have to find a way to tell geronimo to compile the jsp with the correct character set. By default it uses the character set of the user who is running geronimo, but I want it to use the character set I want (the -encoding switch of the javac compiler). Bye. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGWp2SNTLkailsstIRAvEuAJ9/pUurEAmZUoYOJ4eCn9Sg0CBM1QCgtFXa nmibqxi4hMQzZOVNGi1T3FM= =m8Hh -----END PGP SIGNATURE-----
