On 2004.4.19, at 10:02 PM, Veniamin Fichin wrote:
seiji takegata wrote:
Try this:
<%@ page contentType="application/pdf; charset=ISO-8859-1" pageEncoding="Shift_JIS" %>
I tried. This time jasper generates: response.setContentType("application/pdf; charset=ISO-8859-1");
OK, and with that you still can't get PDF right?
Yes, I can get right PDF by specifying just pageEncoding. But IE displays download
dialog (with some warning message) that I don't want to see.
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. All I found is:
org.apache.jasper.compiler.Validator public static void validate(Compiler, Node.Nodes) throws JasperException;
In that method there is some logic that determines "...; charset=..." value in case this substring is absent in "contentType" page directive.
I see. Your suggestion helps me a lot, thanks. Seiji
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
