[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fop-user
Subject:    Re: block-progression-dimension: how it works?
From:       Giuseppe Briotti <g.briotti () gmail ! com>
Date:       2011-07-08 10:36:23
Message-ID: CALXsevfT-zt5ZmYTZvXYQPyuBwvN0FTha-1y7VraPCzwOG8z2A () mail ! gmail ! com
[Download RAW message or body]

2011/6/13 Vincent Hennebert <vhennebert@gmail.com>:
> Hi Giuseppe,
>
> This is a FOP limitation, as you found out the hard way. FOP does not
> make use of the flexibility in block-progression-dimension to adjust the
> height of the block according to the content. It uses only the optimum
> value. Likewise for tables: a table row will only grow as much as
> necessary to accommodate all its content, but the potential slack will
> not be used.
>
> Sorry,
> Vincent

I discover that this is a FO limitation too ;-)

I solved creating an extension to Saxon. I pass the nodes as
parameters and the exstimate the resulting heights programmatically
with Java2D and adopt a strategy to obtain a fit (including a font
resize if necessary). The extension return the final evaluated values
to xslt and here it is possible to use such values in
block-progression-dimension attribute.

It works fine.

G.

-- 

Giuseppe Briotti
g.briotti@gmail.com

"Alme Sol, curru nitido diem qui
promis et celas aliusque et idem
nasceris, possis nihil urbe Roma
visere maius."
(Orazio)

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]