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.
Details of how the content type (and character encoding) of the output
response are determined are in the spec section that I quoted yesterday.
Craig
> Kevin Jones
> Developmentor
> www.develop.com
>
> > -----Original Message-----
> > From: Bill Barker [mailto:[EMAIL PROTECTED]]
> > Sent: 30 January 2002 21:07
> > To: Tomcat Developers List
> > Subject: Re: pageEncoding and Jasper
> >
> >
> >
> > ----- Original Message -----
> > From: "Kevin Jones" <[EMAIL PROTECTED]>
> > To: "'Tomcat Developers List'" <[EMAIL PROTECTED]>
> > Sent: Wednesday, January 30, 2002 11:55 AM
> > Subject: RE: pageEncoding and Jasper
> >
> >
> > > > pageEncoding should be the encoding of the file
> > containing the page,
> > > > should not it?
> > >
> > > I assumed that the encoding would be set as part of the
> > content-type
> > > header in the generated servlet, but I can't see the value
> > anywhere in
> > > the servlet code.
> > Your assumtion is wrong. The pageEncoding is only used to
> > set the encoding on the Reader when the jsp page is compiled.
> > See section 3.1 of the JSP spec.
> > >
> > > > >do anything. I can't use
> > > > >
> > > > > <%@ page contentType="text/html; charset=windows-1256" %>
> > > > >
> > > >
> > > > Why?
> > >
> > > Because IE hates it (although being fair that seems to be a
> > limitation
> > > of IE)
> > >
> > > Kevin Jones
> > > Developmentor
> > > www.develop.com
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]
> > > > On Behalf Of jean-frederic clere
> > > > Sent: 30 January 2002 18:00
> > > > To: Tomcat Developers List
> > > > Subject: Re: pageEncoding and Jasper
> > > >
> > > >
> > > > Kevin Jones wrote:
> > > > >
> > > > > If I add a
> > > > >
> > > > > <%@ page pageEncoding="windows-1256" %>
> > > > >
> > > > > (or any pageEncoding)
> > > > >
> > > > > What does Jasper do with this? I would expect this to be set on
> > > > > the content-type header but it's not.
> > > >
> > > >
> > > > >Jasper certainly parses the parameter
> > > > > and fails if I put an invalid value in there, I just can't
> > > > get it to
> > > >
> > > > > I have to use
> > > > >
> > > > > <META HTTP-EQUIV="content-type" CONTENT="text/html;
> > > > > charset=windows-1256">
> > > > >
> > > > > Some of this might seem like a user question, but I'm more
> > > > concerned
> > > > > about how Jasper works and what it should be doing.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Kevin Jones
> > > > > Developmentor
> > > > > www.develop.com
> > > > >
> > > > > --
> > > > > To unsubscribe, e-mail:
> > > > <mailto:tomcat-dev-> [EMAIL PROTECTED]>
> > > > > For
> > > > additional commands,
> > > > e-mail:
> > > > > <mailto:[EMAIL PROTECTED]>
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
> > > > <mailto:tomcat-dev-> [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]>
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:tomcat-dev-> [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]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
