On 25 Jun 2009, at 19:19, Frank Worsley wrote:
Hi Frank
Andreas Delmelle <andreas.delmelle <at> telenet.be> writes:
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.
Thank you for your reply. I've added a bug report:
https://issues.apache.org/bugzilla/show_bug.cgi?id=47430
Splendid! Thanks.
Do you think this will be easy to fix? If yes, can you point me in a
general
direction in the code base? I might try and fix it myself.
As always: that depends on what you call easy... :-)
It would require a general understanding of the Knuth/TeX algorithm
for line-breaking[*], and specifically, the way inline-blocks are
implemented in FOP.
It may be a side-effect of a more general issue with inline-block
content, since I know for a fact that FOP trunk also has trouble with
tables if they appear as descendants of fo:inlines.
You will probably need to dive into the code in
org.apache.fop.layoutmgr.inline.InlineLayoutManager, and debug this to
get an understanding of what precisely happens there (or more to the
point: what precisely does NOT happen). If you need assistance with
setting up FOP in an IDE, we have step-by-step Wiki pages for
Netbeans, Eclipse and IntelliJ [**]
If I were to have a go at this myself, I'd have to start by debugging
both cases, with and without inlines, to see what the exact difference
is between the two.
Finally, and perhaps most importantly: if you're serious about taking
this on, I invite you to subscribe to fop-dev@, if you have not done
so, and follow up there (as this off-topic for the user list).
Once you're there, and have specific questions, we'll be here to (try
to) answer them.
[*] http://wiki.apache.org/xmlgraphics-fop/KnuthsModel
[**] http://wiki.apache.org/xmlgraphics-fop/FOPIDESetupGuide
Thanks for your interest in FOP!
HTH!
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
