Hi!
jsp pages served by tomcat contain a bad charset string in
their http header. This is not understood by some non iso8859-1
systems/browsers. Macintosh w/ netscape 4.76, for example
will fail to understand that 8859_1 is actually ISO-8859-1.
According to
jakarta-tomcat/src/webpages/docs/api/javax/servlet/ServletResponse.html,
the reply should be "ISO-8859-1". According to IANA,
the 8859_1 is *not* a way to say ISO-8859-1 in MIME headers
<http://www.isi.edu/in-notes/iana/assignments/character-sets>:
Name: ISO_8859-1:1987 [RFC1345,KXS2]
MIBenum: 4
Source: ECMA registry
Alias: iso-ir-100
Alias: ISO_8859-1
Alias: ISO-8859-1 (preferred MIME name)
Alias: latin1
Alias: l1
Alias: IBM819
Alias: CP819
Alias: csISOLatin1
are all allowed ways to describe a character set. 8859_1 is
apparently not one of them, although Java uses this string
internally, which is fine...
Hence, I vote for my enclosed patch, so Mac users can benefit
from tomcat jsp pages. ;-)
>To repeat:
create a simple jsp page with some latin1 characters, like едц.
serve this page with tomcat to a Macintosh w/ netscape 4.76.
You won't get едц, but other strange characters instead.
Cheers,
Palle
--
Partitur Informationsteknik AB
Wenner-Gren Center +46 8 566 280 02
113 46 Stockholm +46 70 785 86 02
Sweden [EMAIL PROTECTED]
Index: src/share/org/apache/jasper/compiler/Compiler.java
===================================================================
RCS file:
/home/cvspublic/jakarta-tomcat/src/share/org/apache/jasper/compiler/Compiler.java,v
retrieving revision 1.19.2.2
diff -u -u -r1.19.2.2 Compiler.java
--- src/share/org/apache/jasper/compiler/Compiler.java 2000/08/28 17:48:24
1.19.2.2
+++ src/share/org/apache/jasper/compiler/Compiler.java 2000/12/06 00:39:09
@@ -142,7 +142,7 @@
// - compiling the generated servlets (pass -encoding to javac).
// XXX - There are really three encodings of interest.
- String jspEncoding = "8859_1"; // default per JSP spec
+ String jspEncoding = "ISO-8859-1"; // default per JSP spec
String javaEncoding = "UTF8"; // perhaps debatable?
// This seems to be a reasonable point to scan the JSP file
