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?
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.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to