On Monday 24 September 2007 02:05:02 am Vincent Hennebert wrote:
> Hi Steve,
>
> Steve Ebersole a écrit :
> > I have some DocBook sources I have been rendering via fop-0.20.5.  On
> > attempts to upgrade to either 0.93 or 0.94,
>
> Very good idea! ;-)
>
> > however, some of my tables render "goofy".  In particular, two
> >phenomena I have noted:
> >
> > 1) Tables that span a page break.  These get rendered "off page".
>
> 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.  But I can get you a slimmed source 
and XSLT.  Will that suffice?

> > 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)

> > Is there perhaps some settings introduced after 0.20.5 I am missing
> > that might cause this behavior?
>
> What’s sure is that FOP 0.94 better follows the Recommendation than
> 0.20.5. The result you got with the old version was perhaps not to be
> expected. But we will better be able to figure out once you provide
> a example.
>
> HTH,
> Vincent
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to