On Oct 22, 2005, at 15:01, Glen Mazza wrote:
I wonder if setting the margins on the fo:region-body (instead of
the fo:external-graphic) would also have solved this. The example
you gave had an empty <fo:region-body/> without dimensions, but
you may have been just abbreviating the sample by removing those
dimensions.
I doubt it, since many of our own layout-engine testcases have
similar, minimal page-masters. If this were a problem, it would have
surfaced much sooner...
In the meantime, I've pinpointed the culprits. Seems it's the two
calls one lines 952 and 955 in RTFHandler. These should first check
whether the respective property has an enum value of "auto" instead
of assuming that an explicit dimension will always be available, but
what exactly should happen in case either value is "auto", I'm not
sure about that. I'd say the values of content-height and content-
width should also be checked, and subsequently, the total bpd/ipd of
the area containing the graphic can be inferred from its original
size (?)
Tony Morris escribió:
Thanks, by explicitly setting a width and height, the problem
disappeared - it only occurred for the RTF renderer (though I only
tried the PDF one as well). The sizes themselves seem to be a tad
obscure though.
Tony, can you be a bit more precise as to what you mean by this last
sentence? All I know is that, in FOP Trunk, with 'height' and 'width'
you only specify the dimension of the area. Use them in combination
with 'content-height' and 'content-width' to get appropriate results.
HTH!
Greetz,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
