Vincent,

Thanks for taking the time to look at my fo.

The "distribute" attribute definitely improves the output, but indeed
there are situations in which it fails to align the columns.

I'm not a stranger to space-before but I didn't know about the
sub-attributes.  I'll give those a try, but it will likely be some time
next week before I can report my findings. The distribute attribute
apparently adjusts leading between lines within paragraphs.  Would it be
correct to assume using space-before.* would shift whole blocks?. As you
may have noticed in my example document I have one rather small
region-body (simply because a single flow will not skip a page: another
topic I'm sure).  It's entirely possible that the contents of that
region would be a single block and maybe I could use distribute on just
that region...  We'll see.

If any are interested in comparing the pdf output, it could be arranged.

Thanks again to all involved,

rjs


On 01/28/2011 03:32 AM, Vincent Hennebert wrote:
> Hi Rob,
>
> On 27/01/11 20:21, Rob Sargent wrote:
>   
>> It certainly has my vote!  The difference is dramatic and very
>> pleasing.  Without this attribute, I'm not sure we could publish the book.
>>     
> From what I saw in the file you sent, I think you would be much better
> off using elastic spaces between sections instead of relying on
> a non-standard property. “distribute” may be of use when you are dealing
> with very long paragraphs. This is not the case of your document; in
> your case the way to go definitely is to allow space to shrink or
> stretch between sections. Do something like this:
>     <fo:block
>       space-before.minimum="5pt"
>       space-before.optimum="7pt"
>       space-before.maximum="14pt"
>       ...>Section Title</fo:block>
>
> Non-standard properties are not guaranteed to be maintained so you
> better not rely too much on them.
>
> HTH,
> Vincent
>
>
>   
>> On 01/27/2011 12:33 PM, Andreas Delmelle wrote:
>>     
>>> On 27 Jan 2011, at 20:25, Rob Sargent wrote:
>>>
>>>   
>>>       
>>>> I will most certainly give that a try, even if
>>>> http://www.w3.org/TR/xsl/#display-align does not suggest that is a valid
>>>> doesn't suggest that as an option.  
>>>>     
>>>>         
>>> Indeed. That is because, as Jeremias explained, it is a non-standard (= 
>>> FOP-proprietary) extension.
>>>
>>>   
>>>       
>>>> I guess I need a better reference for the current state of fop.
>>>>     
>>>>         
>>> Well, this particular extension is documented nowhere, AFAIK. 
>>> Reason is that, so far, no one has put any effort in verifying the 
>>> behavior, so we are not confident enough to advertise it as part of FOP's 
>>> core functionality...
>>>
>>>
>>>
>>> Regards
>>>
>>> Andreas
>>> ---
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>   
>>>       
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>     
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>   

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

Reply via email to