I've been playing around with the fop instructions that Ben put on his blog a while ago, and I thought I would post here to see if anyone has some tips/pointers (that don't include reading some huge XML book...).
Despite many errors being generated, the xsltproc|fop toolchain does produce what seems to be clean PostScript or PDF. The errors do not seem to affect the output. I notice a few things, though: 1) Chapters with an odd number of pages end on the odd page. There is no "this page is blank" even-numbered last page. This meansthat we will have chapters beginning on the back of the last page of the previous chapter. Not necessarily bad--just a style thing we may want to think about. 2) The index has no page numbers. 3) I'm not seeing how to use the xinclude.mod file in the directory. The --xinclude option of xsltproc doesn't seem to understand it. 4) Using the --catalogs option while processing the main file (DRIVERTUT.xml) does pull the whole document together nicely, though, with the above caveats. Once I found that, I realized I don't need to play with merging PostScript/PDF files anymore. Just as well--psmerge silently gacks when trying to merge two files output by the fop process, whether going straight to PS, or to PDF and then using pdf2ps. That's pretty much it for now. Any pointers or comments to the above notes would be appreciated. Not sure how quickly I can get back to the testing; I have to do it at home, and the next two nights are tied up and I'm working Saturday. I may be able to sneak in a couple half-hours, though. I do plan on documenting what I've done in our community pages as soon as I can for the guidance of others. I'm actually surprised at how quickly I've managed to get a workable PDF, considering how I started my explorations, and kept missing the forest for the trees. :-) Rainer This message posted from opensolaris.org
