It's not all that easy. I am building the docs via the Maven plugin for DocBook handing that I developed as part of migrating Hibernate over to Maven. In addition to my basic lack of understanding of DocBook, FOP, XSLT, etc I am also a noob at Maven, so of course I am the perfect person to write such functionality ;) But seriously, I just learned what I needed about each as I went along; so, unfortunately, at at this point I have no idea how to "run FOP with the '-foout' parameter". But if you tell me (or point me to resources) how to do that I have no issue with doing that. (note that because I am using maven as the infastructure I do not have fop properly 'installed').
On Wednesday 26 September 2007 01:19:56 pm Andreas L Delmelle wrote: > 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]
