I actually had this working at one time in the pre-Forrest days, and in the days before I was a committer, so I don't think it ever got committed. The solution then was a target in the build.xml file, and it could still be that, but it might make more sense to try to use Forrest/Cocoon instead, so that the PDF can actually be placed on the web site for downloading. Forrest uses the book.xml files for its structure, and you could use that, but it seems pretty inflexible to me. IIRC, my previous solution was a stylesheet that essentially imported the other documents. Cocoon seems to have been made for this sort of thing. I think the solution I would probably try first is to our Cocoon infrastructure, as it can do the XSLT (some are non-standard, FAQ and Compliance for example), aggregate it, then FOP it. I'm no expert on any of this, but I can probably help you. Also, eventually two manuals would be nice, one for FOP users, another for FOP dev, design, and alt-design.
Sounds good. Would you send me what you had (if you can find it! ;-p) so I can do a bit of learning? Does this mean (gulp!) I'll have to learn how to mess around with Cocoon? I guess it could be a good thing...
--
Clay Leeds - [EMAIL PROTECTED]
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]