Victor Mote schrieb: > FOP Developers: > > I submitted a patch (through Bugzilla, for trunk) that fixes some problems > in the pdfdoc build. I realize that Joerg is doing some work in that area as > well, and I don't mean to step on any of that, but I am not sure exactly > what that work involves, so I pressed forward. (BTW, my apologies to > Joerg -- I think I have mis-Romanized his name in some previous postings). > My purpose here is to be able to generate a downloadable PDF that is the
Forrest offers one PDF per page at the moment (see http://outerthought.net/forrest/ for example) > Item 1: The 0.20.4 release does not seem to have the fo.pdf file included, > probably because the xmldoc files aren't in the maintenance branch (to build Because pdf generation was broken.. > the pdfdocs, use the FOP classes from the maintenance branch on the xml-docs > files in the trunk). Since we don't plan to do many more releases from the > maintenance branch, I don't know whether it is easier to a) copy the files > from trunk to maintenance, b) just generate the pdf from the trunk & include > it with the maintenance release, or c) not include the document in the > release. I'm too not sure what's the best .. Some time ago we decided to maintain the docs in the trunk only. For the 0.20.3 release I copied the xml-sources to the maintenance branch and build the docs there. For FOP 0.20.4 I did build the html-docs within the trunk and copied the html to the distribution because stylebook was (and still is) broken in the maintenance branch (I think xerces1 is needed) > for example). Equally important, I want to beef up some of the content > areas, especially the FAQ. (It has been well-documented on this list that > nobody reads the FAQ, but I need a place to write such things just for my > own benefit :-) ). IIRC Joerg has done some work on the (new) FAQ. (And I'm sure at least some people will read the FAQ) > Item 3: This is really a question about content organization. I would like > to split the documentation into two groups, user and developer, and in We already have some kind of developer documentation (called design docs). See http://xml.apache.org/fop/design/index.html, sources are in docs/design. > please let me know if you have general objections. Also, this may have web > site and Forrest ramifications (I am unclear on how our web site is > currently generated), so there may be implementation objections as well. It's quite complicated at the moment and Forrest should improve this but I don't see how this will happen at the moment. Ok. IMHO the next step should be the migration of the current docs to forrest (Joerg?) Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
