On Sep 26, 2007, at 04:17, Steve Ebersole wrote:
Hi
Can you please provide a small FO sample showing the problem? Not the
source DocBook file (or, at least, not only), but the result of
the XSLT
transformation.
I do not write an intermediate FO file.
Good! As a general rule, nobody really should, unless for debugging
purposes.
But I can get you a slimmed source and XSLT. Will that suffice?
Although it isn't that much effort for us, I consider everyone on the
team to be a good programmer (and hence, as the saying goes, also a /
lazy/ programmer ;-))
Seriously, minimal source XML+XSL is fine with me in this case, but
if you want to spare us the effort and run FOP with the '-foout'
parameter yourself, that is always much appreciated. The reasoning is
that the XSL transform actually has nothing to do with FOP. In your
particular case, the issue is definitely not in the XSLT, so we do
not run the risk of running the same document with a different XSLT
processor.
2) Quite a few of the tables are of the term/definition variety.
Some of
them reference java class names (FQN), and as such represent long,
unbroken text. In a lot of cases, that causes horizontal
"bleeding" of
the left/right cells.
If you want to keep your class names unbroken, then I’m afraid you’re
stuck. Otherwise you may add zero-width spaces (u+200B) after the
dots
or soft hyphens (u+00AD) inside class/package names to have your
class
name broken over several lines.
I'll just introduce a convention to shorten the 'domain portion' of
the
package name (i.e. org.hibernate.dialect.HSQLDialect ->
o.h.dialect.HSQLDialect)
If that works for you, all the better, but I would take care: this
does not really solve the issue if the packages are nested deeper
than three levels, does it?
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
