On Sep 1, 2008, at 01:06, Ryan Lortie wrote:
<snip />
When you don't use <character> then FOP makes its decision about the height of the line based solely on the first listed font family (ignoring all of the others, irrespective of if they are used for font substitution in that line).
Having taken a quick, closer look at the related code, it goes in this direction indeed.
Technically, the story is that, without fo:character or fo:inline a combined text-area is generated for each separate 'word' (in the sense of: uninterrupted sequence of non-white-space characters, regardless of whether they can be rendered in the same font).
Those areas are currently all based on a single alignment-context (which seems to correspond to the first font-family in the list; this explains why we get a different result when putting the Symbol font first). AFAICT, it does not seem like a real tough problem to solve... I do seem to remember Max pointing out this issue at some time while implementing font-selection (?) If we place the characters in an fo:inline or an fo:character, the only big difference is that a new alignment-context is created automatically, which later on triggers correct baseline alignment of the two pieces.
If you want, you can open a Bugzilla(*) entry for this, so that the issue is tracked.
Thanks Andreas (*) https://issues.apache.org/bugzilla --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
