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=18275>.
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=18275

Fop enter in an infinite loop if image size is biger than page size

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|0.20.4                      |0.20.5



------- Additional Comments From [EMAIL PROTECTED]  2003-03-28 10:14 -------
A bug is a violation of the formal spec for the software, or at least widely held
beliefs how the software should work. Neither can be claimed for this problem.
As I already said, there are basically two choices when a FO too large for the
available space is encountered:
1. Use the curent area anyway, perhaps overflowing it, and apply some
 interpretation of how clipping properties, alignment etc. should be handled
 (the spec is very vague about most of the details in this case)
2. Spill the FO to the next page. After all, there could be a following page
 with a page master ultimately allowing to fit the FO properly into an area.
FOP chooses the second interpretation, and the "infinite loop" is the technical
expression of the fact that it is not necessarily always successful.
The spec does not explicitely mandate either, nor is one of the choices always
preferable to the other. Therefore, unless the spec is fixed to be more
precise about this issue, the current implementation is technically not at
fault.
In fact, the conceptual difficulties encountered while trying to formalize
handling of oversized FOs hints that is is simply bad style to use them.

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

Reply via email to