[xep-support] Keep-together precedence

Alexander Peshkov peshkov at renderx.com
Mon Sep 15 08:03:23 PDT 2003


Hello Anders,

The situation with keeps precedence in XEP haven't changed yet.

Best regards,
Alexander Peshkov                             mailto:peshkov at renderx.com
RenderX

 
 
AS> Hello,
 
AS> Before the summer I asked the question below regarding keep-together
AS> restraints, and got the answer below that xep doesn't support
AS> precedences. So does that mean there is no way to solve conflicts
AS> between elements? (see my needs below)
 
AS> As it is I'm getting bad page breaks where either a table cell will be
AS> broken right in the middle (if the keep-together is set on "sections",
AS> and this looks truly awful), or a "section" of text (which we want to
AS> keep together in general) will haphazardly be broken up all over the
AS> document (if the keep-together is set on table-cells instead). This
AS> doesn't look as immediately awful as the first one, but is on the whole
AS> just as bad because it is all over the place.
 
AS> Regards,
 
AS> Anders
 
AS> ************************************************************************
AS> ******************
AS> Previous messages:
 
AS> According to the specification, you can use whatever integer values you 
AS> want. Any integer value has a lower precedence than 'always'. However,
AS> XEP 
AS> doesn't support these precedences yet. It interprets all integer values
AS> as 
AS> 'always'. 


AS> Jeff 


>> -----Original Message----- 
>> From: Anders Svensson [mailto:anders.svensson at explicon.se] 
>> Sent: Tuesday, May 13, 2003 9:41 AM 
>> To:    > Subject: [xep-support] Keep-together weighting 
>> 
>> 
>> Hi, 
>> 
>> does anyone here know how to weight keep-together restraints 
>> against one another? I.e. if I have a 
>> keep-together.within-page on a table-row, a table and a 
>> "section" I want to be able to give them different priority 
>> so that the table-row is absolute (value="always"), must not 
>> be broken, the table is second and the section third, but 
>> should still be kept together whenever possible. I read that 
>> you could do this by giving integer values, but what values? 
>> I.e. what is the allowed span? Is i 0-10 or 0-100 or what? 
>> Does the maximum integer value equal "always"? 
>> 
>> Thanks in advance, 
>> 
>> Anders 
>> ------------------- 

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


-------------------
(*) 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



More information about the Xep-support mailing list