Re: FOP manual
Victor Mote schrieb: Clay Leeds wrote: A single PDF manual for FOP would really be nice... It might even be [..] that, but it might make more sense to try to use Forrest/Cocoon instead, so http://marc.theaimsgroup.com/?l=forrest-dev&m=105516618908652&w=2 ? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP manual
Clay Leeds wrote: > 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... It is long gone. Yes, you'll want to get a rudimentary understanding of Cocoon. There are some good books available, and it seems like the web site is pretty helpful. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP manual
On 7/2/2003 10:08 AM, Victor Mote wrote: 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]
FOP manual (WAS: Running FOP 'headless' FAQ)
Clay Leeds wrote: > A single PDF manual for FOP would really be nice... It might even be > cool to just make a PDF with links to the other PDFs (I assume that the > current "manual" is what comes in the build/site directory). What would > it take to generate a single PDF of the FOP manual? Of course, it would > be great it it had bookmarks, too. Would it be possible to make this > happen by creating some sort of 'meta' xml file which somehow contains > links to all of the sub-files? It could either be a single PDF file or > it could be a multi-PDf file. Is there a better way to make it happen? > Anyone? Anyone? ;-p 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. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]