You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Romit Saha <ro...@ge.com> on 2013/01/04 09:59:41 UTC
JFOR 0.7.1 behaving weird
Hi All,
My environment has been upgraded from jdk1.4 to jdk1.6 and from Solaris
Unix box to Linux2.6.18-238.5.1.el5 x86_64 Box with Oracle 11g for
connectivity from 10g earlier
But the RTF generated by JFOR 0.7.1 is looking very different from the
earlier version
The header and footer is getting enlarged and thus looking very odd..though
the content is fine
While looking at the log I got this message
----------------------------------------------------------------------------
------------------------------
Rendering complete : RTF_Quote 0.092 secs.
jfor.INFO:jfor V0.7.1 - setting up conversion...
jfor.INFO:Parsing xsl:fo document...
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.WARNING:fo:table-column width not defined,using 200.0
jfor.INFO:Writing out RTF...
jfor.INFO:Writing image 'http://tst1-xxxx.com/images/xxxx.jpg'.
jfor.INFO:Writing image 'http://tst1-xxxx.com/images/xxxx.jpg'.
jfor.INFO:Writing image 'http://tst1-xxxx.com/images/xxxx.jpg'.
jfor.INFO:Writing image 'http://tst1-xxxxx.com/images/xxxx.jpg'.
jfor.INFO:Writing image 'http://tst1-xxxxx.com/images/xxxxx.jpg'.
jfor.INFO:Writing image 'http://tst1-xxxxx.com/images/xxx.jpg'.
jfor.INFO:Writing image 'http://tst1-xxxxxx.com/images/xxxx.jpg'.
jfor.INFO:Writing image 'http://tst1-xxxxx.com/images/xxxx.jpg'.
jfor.INFO:Write bookmark 'terminator'.
jfor.INFO:Done converting xsl:fo to RTF.
jfor.DEBUG:conversion took 585 milliseconds.
----------------------------------------------------------------------------
-------------------------------
Can you suggest any clue where I should be looking????
I have migrated all the xsl files that were used earlier
Thanks
Romit Saha
RE: JFOR 0.7.1 behaving weird
Posted by Robert Meyer <rm...@hotmail.co.uk>.
Hi Romit,
I have come across something similar before when I was working on the following patch for FOP:
https://issues.apache.org/jira/browse/FOP-2104
It was caused by there being a mismatch with one of the FO table elements being converted to RTF i.e. a start table header element with no closing element. This issue though was self-induced as I was trying to manually create and force a table header into the mix without closing it off. I think if the tree structure isn't correct it gets confused down the line and starts throwing out those messages.
I am not sure what sort of FO validation JFOR used, but it might be worth just checking over the structure even if it did work before.
As a side note, from my understanding JFOR was donated to FOP a while ago so I imagine both projects were merged as FOP also has the ability to generate RTF from FO. Have you tried converting your FO using the latest version of FOP and see if you get the same thing? Maybe it was an issue which has subsequently been resolved. FOP has good FO validation so if there is something wrong I imagine it would highlight it. If it is however reproducible in FOP, we can create a bug to add to the list.
Regards,
Robert Meyer
From: romit.saha@ge.com
To: fop-users@xmlgraphics.apache.org
Subject: JFOR 0.7.1 behaving weird
Date: Fri, 4 Jan 2013 14:29:41 +0530
Hi All, My environment has been upgraded from jdk1.4 to jdk1.6 and from Solaris Unix box to Linux2.6.18-238.5.1.el5 x86_64 Box with Oracle 11g for connectivity from 10g earlierBut the RTF generated by JFOR 0.7.1 is looking very different from the earlier versionThe header and footer is getting enlarged and thus looking very odd..though the content is fineWhile looking at the log I got this message----------------------------------------------------------------------------------------------------------Rendering complete : RTF_Quote 0.092 secs.jfor.INFO:jfor V0.7.1 - setting up conversion...jfor.INFO:Parsing xsl:fo document...jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.WARNING:fo:table-column width not defined,using 200.0jfor.INFO:Writing out RTF...jfor.INFO:Writing image 'http://tst1-xxxx.com/images/xxxx.jpg'.jfor.INFO:Writing image 'http://tst1-xxxx.com/images/xxxx.jpg'.jfor.INFO:Writing image 'http://tst1-xxxx.com/images/xxxx.jpg'.jfor.INFO:Writing image 'http://tst1-xxxxx.com/images/xxxx.jpg'.jfor.INFO:Writing image 'http://tst1-xxxxx.com/images/xxxxx.jpg'.jfor.INFO:Writing image 'http://tst1-xxxxx.com/images/xxx.jpg'.jfor.INFO:Writing image 'http://tst1-xxxxxx.com/images/xxxx.jpg'.jfor.INFO:Writing image 'http://tst1-xxxxx.com/images/xxxx.jpg'.jfor.INFO:Write bookmark 'terminator'.jfor.INFO:Done converting xsl:fo to RTF.jfor.DEBUG:conversion took 585 milliseconds.----------------------------------------------------------------------------------------------------------- Can you suggest any clue where I should be looking????I have migrated all the xsl files that were used earlier ThanksRomit Saha