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

part of word missing when broken across pages

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Blocker                     |Normal
          Component|pdf renderer                |page-master/layout
           Priority|Other                       |Low



------- Additional Comments From [EMAIL PROTECTED]  2002-10-18 13:02 -------
The maintenance code works for the attached sample due to some changes in the
code. Unfortunately, the real bug is not fixed, its only much more unlikely
to run into it.
The following FO fails with the current code:
<?xml version="1.0"?>
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format";>
  <fo:layout-master-set>
    <fo:simple-page-master master-name="a"
      page-width="100pt" page-height="18pt">
      <fo:region-body/>
    </fo:simple-page-master>
  </fo:layout-master-set>
  <fo:page-sequence master-reference="a">
    <fo:flow flow-name="xsl-region-body">
      <fo:block>blah blablabla<fo:inline>wurb</fo:inline></fo:block>
    </fo:flow>
  </fo:page-sequence>
</fo:root>
The text "blah blablabla" is laid out into a line, the second word "blablabla"
is not added as a child but stored into the pending area list, because it could
for a word with following text and wrapped. The fo:inline causes the following
text "wurb" to be delivered separately to the line layout routine, and it
overflows the line. In normal operation, the pending text would have been added
to the next line. In the example, this happens at the end of a page, and this
means a new block is started from scratch which gets the "wurb" but does not
know about the pending "blablabla" text.
I have no idea how to fix this so that it would work with tables, and it's
probably not worth it. I will add a diagnostic.

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

Reply via email to