DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23317>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23317

FOP url Rendering issue.

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From [EMAIL PROTECTED]  2003-09-23 22:18 -------
The PDF document is doing the same thing on my side as yours.

But, I ran your xml & xsl through Xalan--one thing I noticed in the FO output 
are lots of nonsensical  (A-caret?) letters--I don't see why you need them.  
There appears to be something wrong with your stylesheet.

Also, running the FO output through FOP gave a warning that you have specified 
your column widths about 25% too wide.  (Sum about 500K, specified IPD 417K or 
so.)  This may be the source of your problem--your columns are too narrow, and 
your results would therefore be undefined.  Also, there were complaints about 
missing images, etc., so that may be an issue.

Finally, in a separate, simple document I created two PDF links--one outside a 
table and one within in a simple file in 0.20.5--works fine!--So I believe the 
problem is with your XSL FO document.  I'm attaching a sample XSL FO document 
and resultant PDF--you can see that the links work fine.  

Somehow, perhaps by correcting your XSL FO you should be able to get the links 
to work like they do in my sample document.  But right now, there are too many 
things messy/wrong with your stylesheet for it to indicate that the problem is 
with FOP.  At any rate, we are making very few changes to our 0.20.x branch, 
and given that the fo:basic-link mostly work, changes do not appear called for 
at this time.

Reply via email to