On 24 Jun 2009, at 08:07, Frank Worsley wrote:
Hi
First of all: apologies for the rather late reply. Just noticed that
this post had not been answered...
> <snip />
> Notice that removing either the fo:block or the second fo:inline
> element will fix the problem.
>
> I know that this is rather weird formatting to begin with, but
> unfortunately I have no easy way to prevent it from being generated
> this way. I'm wondering if this may be fixed on the trunk or if
> someone can suggest a work around.
Bad news: current trunk still has the same issue, which is definitely
a bug.
If you want, please attach the files to a Bugzilla report, so we don't
lose track of it, and you will be kept informed about the status.
Thanks!
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail:
fop-users-unsubscribe@...
For additional commands, e-mail:
fop-users-help@...