AW: AW: FOP In Latest Cocoon Releases
Hi Joerg Pietschmann, I checked out und built fop out of branch fop-0_20_2-maintain as you told me. Whe I test this version referring to my described problems with hyphenation I always get the following error message: [ERROR] Couldn't find hyphenation pattern de [ERROR] Error building hyphenation tree for language de java.io.InvalidClassException: org.apache.fop.layout.hyphenation.HyphenationTree ; local class incompatible: stream classdesc serialVersionUID = -778451683547287 1478, local class serialVersionUID = 6956085100635965297 There is obviously a problem within the serialization/deserialization process. Any further hints? With best regards Frank -Ursprungliche Nachricht- Von: J.Pietschmann [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 25. September 2002 21:50 An: [EMAIL PROTECTED] Betreff: Re: AW: FOP In Latest Cocoon Releases Przybilla, Frank wrote: My problem occurs especially in conjunction with the generation of fop tables and hyphenation of long text in table-cells. The output produced with fop in cocoon is sometimes messing around the characters of a word. Ah, the problem with parts of hyphenated word jumping around is actually a FOP bug. Yes, it depends on the parser, more specific, it depends on how the parser passes text up. The bug is fixed in CVS (maintenance branch). J.Pietschmann - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: FOP In Latest Cocoon Releases
Skladovs, Victor wrote: What would you suggest in this situation? How could I improve the Cocoon work as pdf concerns? Updating fop.jar doesn't help. First, get Xalan 2.4.0 and replace both the xalan.jar from FOP as well as the jar deployed with Cocoon. Check with the FOP command line application for problems. If this doesn't help, and you can get a small XML+XSL combo which reproduces the problem with the FOP command line app, post it to fop-user. J.Pietschmann - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: FOP In Latest Cocoon Releases
Dear J.Pietschmann! What would you suggest in this situation? How could I improve the Cocoon work as pdf concerns? Updating fop.jar doesn't help. Regards, Viktor -Ursprungliche Nachricht- Von: J.Pietschmann [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 26. September 2002 22:08 An: [EMAIL PROTECTED] Betreff: Re: AW: FOP In Latest Cocoon Releases Skladovs, Victor wrote: Frank, I don't believe it is a fop bug! I had been tested all the variants from the command line and I have assessed that it is xalan bug! The bug appears ONLY by transforming XML and XSL files. While working only with, say, FO documents, everything's works fine, but when I tried to transform my xml file with a xml2fo.xsl: fop -xml table.xml -xsl xml2fo.xsl -pdf table.pdf I've got a bad pdf! Xalan 2.3.1 still has bugs, in particular it accepts buggy style sheets. This is not exposed if the transformation result is serialized but causes trouble if the result is consumed via SAX events by something else, as it happens in Cocoon and the FOP command above. Try *upgrading* to Xalan 2.4, and you'll probably see an error message. J.Pietschmann - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
