Hi

 

Attached here is an XSL-FO that causes the FOP 0.94 to go into an infinite 
loop. This is causing serious problems in our application. I narrowed down the 
problem to an "<fo:block>Â </fo:block> " element placed within the footnote. 
This block element contains the character Â. This character may be the cause 
for the FOP 0.94 to go into an infinite loop depending on certain data in the 
XSL-FO. When "<fo:block>Â </fo:block> is removed from the footnote the PDF will 
generate. However I am baffled as to why this FOP 0.94 goes into an infinite 
loop. Whatever the issue, FOP 0.94 shouldn't go into an infinite loop. It 
should throw an exception if it has problems with the XSL-FO. It appears to be 
a serious issue or Bug with FOP 0.94. Can some apache FOP developer confirm 
whether this is a problem or not? This is urgent.

 

Regards

Ankur 



DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. 
Any views or opinions presented in 
this email are solely those of the author and may not necessarily reflect the 
opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of 
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any mail and 
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------

Attachment: debug.fo
Description: debug.fo

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

Reply via email to