I've tried the following for combinations of settings, where
jspx denotes the encoding declared and used in my jspx document,
jsp-javaEncoding is declared in conf/web.xml, and jasper-out is the
relevant line in the generated xxx_jspx.java.
(1)
jspx: ISO-8859-1
jsp-javaEncoding: not explicitly set
jasper-out:
out.write("\täöü�<84>�<96>�<9C>�<9F>\n");
(2)
jspx: UTF-8
jsp-javaEncoding: not explicitly set
jasper-out:
out.write("\täöü�<84>�<96>�<9C>�<9F>\n");
(3)
jspx: ISO-8859-1
jsp-javaEncoding: ISO-8859-1
jasper-out:
out.write("\t�������\n");
(4)
jspx: UTF-8
jsp-javaEncoding: ISO-8859-1
jasper-out:
out.write("\t�������\n");
Only (3) and (4) appear correctly in the browser as "�������" (german
umlauts). I don't think setting the javaEncoding should be necessary
here, but I may well be misunderstanding something.
Without any javaEncoding given, jasper produces UTF-8 encoded java
source code and the JDT compiler supposedly accepts UTF-8 as its
default input encoding. I haven't verified the latter.
There seem to be two possible causes for the incorrect output
the JDT compiler doesn't behave as advertised, i.e., it does not take
UTF-8 as default input encoding. *Or* the JDT compiler produces
character output in UTF-8 which is latter erroneously treated as
ISO-8859-1.
Michael
--
Michael Schuerig Contests between male toads over females are
mailto:[EMAIL PROTECTED] often settled by the depth of the croak.
http://www.schuerig.de/michael/ --John Maynard Smith
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
