[xep-support] A question of page breaks and keeps

[Lori Wong]

David:

At 05:09 PM 3/17/2003, David Tolpin wrote:
>At 2003-03-17 16:27 -0800, Lori Wong wrote:
>>I have an instance where I have a list-item (with 
>>keep-together-within-page="always") that exceeds the length of a page.
>
>The W3C Recommendation states this is an overflow error condition and the 
>content exceeding the page length is discarded, not to be formatted.  A 
>numeric value of keep is allowed to be broken by exceeding the length of 
>the page, any higher numeric values of keep will still try to be 
>respected.  When the keep is broken it is flowed as if the keep were never 
>specified.

Do you have any recommendations as to what values I might use?  I'm 
unfamiliar with using a numeric value in the keeps, so I'm not sure what 
might be appropriate to use - is there an implied value for keep="always"?

One other option comes to mind is to have an attribute associated with the 
list-item that would specify whether this item is allowed to be 
broken.  Then the XSLT could set the keep-together-within-page value 
appropriately, rather than forcing the keep="always" in all cases.

>Can you get rid of the empty block?  The keep-with-sibling properties have 
>effect on the immediately adjacent area.

>The empty block is the kicker in this situation ... I think you'll have to 
>get rid of it.  Is there a reason why it is there?

I'd like to, but I'm currently using the empty block to hold an ID to 
keyword a passage - in this case the list-block.  Ideally, we should have 
the ID associated with the list-block, rather than an empty block, but I'm 
working with some legacy data... it might be possible to rework the XSLT to 
eliminate the empty block and move the ID into the list-block.

Thanks,
Lori

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo at renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html