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

http://issues.apache.org/bugzilla/show_bug.cgi?id=44107


[EMAIL PROTECTED] changed:

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




------- Additional Comments From [EMAIL PROTECTED]  2007-12-19 23:58 -------
In my opinion, this is not a bug. XSL 1.1 (chapter 5.11) says that:
keep-together="always"
is equivalent to a specification of
keep-together.within-line="always"
keep-together.within-column="always"
keep-together.within-page="always"

And I/we interpret the value "always" very strictly as opposed to other FO
implementations. If that is correct is a different discussion. Anyway, with 0.94
you get support for keep-together.within-line. Before the setting never had an
effect. The net effect is that FOP cannot break anywhere in the content and so
the whole text is one line which overflows as a consequence.

If you ask me, you have to adjust your stylesheet and use
keep-together.within-column (or .within-page although that doesn't work
properly, yet) instead of keep-together. I'm closing this issue as "INVALID",
but if anyone thinks this is wrong, please reopen.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to