----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 07, 2002 7:26 PM Subject: Re: pageEncoding and Jasper
> From: "Craig R. McClanahan" <[EMAIL PROTECTED]> > Subject: RE: pageEncoding and Jasper > Date: Thu, 31 Jan 2002 06:49:39 -0800 (PST) > Message-ID: <[EMAIL PROTECTED]> > > > On Thu, 31 Jan 2002, Kevin Jones wrote: > > > > > Date: Thu, 31 Jan 2002 10:37:10 -0000 > > > From: Kevin Jones <[EMAIL PROTECTED]> > > > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > > > To: 'Tomcat Developers List' <[EMAIL PROTECTED]> > > > Subject: RE: pageEncoding and Jasper > > > > > > So it's only used when compiling the JSP to a servlet? > > > > If "it" is the pageEncoding attribute of the <%@ page %> directive, then > > the answer is yes. > > Craig, the answer is "no". I'd like to think that Craig knows what Tomcat 4.x does ;-) > The pageEncoding attribute is used to "read" only. Servlet codes Which is what he said, if you followed the rest of the thread. > generated from JSP pages are written in UTF-8. You can confirm > the encoding of generated Servlet codes by a browser (Netscape: > View -> Character Coding) or a utf-8 enabled editor. This is controlled by the contentType attribute of the <%@page ...%>directive > So, the encoding for compile is UTF-8 only. > It is true that Jasper (in both 3.x and 4.x branches) generates (by default) the intermediate .java file as UTF-8 (which causes big problems when you configure the system to use Jikes :(. > --- > Yoko Kamei Harada, Web Studio Ne-Po-Le > http://www.netpotlet.com/ > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
