Hi
> >Maybe you should query tomcat-dev list about how (and if you really
> > need) to override Jasper's behaviour on inserting "pageEncoding" value
> > into Content-Type header.
> >
In tomcat-dev list, they say "IT'S SPEC." that's it.
I've learned that "If you don't like it, shut up and
sary, to reflect the character
> encoding used, through the /charset=.../ property. This means that the
> content type must be set before calling this method.
>
> So don't use it for binary things...
>
>
> Antonio Fiol
>
>
> seiji takegata wrote:
>
> >
Hi,
> seiji takegata wrote:
>
> > Hi Veniamin,
> > Thank you for your reply.
> >
> >>What it means "character is not encoded correctly"? If PDF content
> >>is unreadable, then that's PDF file problem, not Tomcat. Is this PDF
>
, then the content should not be attributed
like "charset=Shift_JIS". but still I need to specify
pageEncoding attribute for correct character encoding.
I just want tomcat to stop adding charset option when
pageEncoding attribute is specified.
Am I wrong?
> seiji takegata wrote:
&
obeReader opens as I expect. But character is not encoded
correctory.
I wonder why "charset=Shift_JIS" is added to contentType string.
I want remove it from the contentType string, or remove whole
the line. I think I can specify contentType by
response.setCotentType("applicatio
