Hy, I usually use FOP client side, using a batch to launch it. I'm to do the same on a Tomcat server so with JSP I beleave.
But the same FO is transformed with the batch process and is not with the jsp (in tomcat) process. I noticed this message is displayed when I launch the batch : [DEBUG] Input mode: [DEBUG] FO [DEBUG] fo input file: my.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: FT410 GFH T533-23.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on >>>>[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] base directory: file:/C:/tropic/jakarta-tomcat-3.3.1/webapps/tropic/fop-0.20.5rc3a/ [INFO] FOP 0.20.5rc3a >>>>[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts And I noticed the jsp display this : [DEBUG] FO [DEBUG] fo input file: my.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: FT410_GFH_T533-23.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on >>>>[INFO] Using org.apache.crimson.parser.XMLReaderImpl as SAX2 Parser [INFO] base directory: file:/C:/tropic/jakarta-tomcat-3.3.1/bin/ [INFO] FOP 0.20.5rc3a >>>>[INFO] Using org.apache.crimson.parser.XMLReaderImpl as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts The first transform is done correctly, the second is not : (org.apache.fop.apps.FOPException: Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa"). The problem can be from the parser used ? (seems to be sax for the batch, and crimson for the jsp) The bases directories differ too. Can it be a problem ? Any Idea ? Help would be great. Thanks. Rodolphe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
