Re: Documentation finished
On Wed, Jun 30, 2004 at 02:04:30PM -0700, Glen Mazza wrote: > On second thought, I would hold off on this; I just > noticed you copywrited the document under your name; > hence it would probably be improper to include the > current FOP system documentation from Keiron/Kelly or > other former/current committers. That is not a problem. I never publish anything without a copyright holder. If it goes to FOP CVS and other contributions are merged, then the copyright holder is just changed, like with source code. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Documentation finished
--- Simon Pepping <[EMAIL PROTECTED]> wrote: > On Mon, Jun 28, 2004 at 02:31:27PM -0700, Glen Mazza > wrote: > > Before doing so, it would probably be good if you > > could look at our System design pages > > (http://xml.apache.org/fop/design/index.html), if > you > > haven't already, and add to your document anything > > from them that is still relevant and useful but > > missing from your document. > > I have read them but I have not checked whether I > have included > everything that is relevant. As I replied to Clay, I > now want to take > a break from this work, and try to do some coding. I > will take your > suggestion up later. > On second thought, I would hold off on this; I just noticed you copywrited the document under your name; hence it would probably be improper to include the current FOP system documentation from Keiron/Kelly or other former/current committers. Glen
Re: Documentation finished
On Mon, Jun 28, 2004 at 02:31:27PM -0700, Glen Mazza wrote: > Before doing so, it would probably be good if you > could look at our System design pages > (http://xml.apache.org/fop/design/index.html), if you > haven't already, and add to your document anything > from them that is still relevant and useful but > missing from your document. I have read them but I have not checked whether I have included everything that is relevant. As I replied to Clay, I now want to take a break from this work, and try to do some coding. I will take your suggestion up later. > That way, when we add your document to our website, we > can rid of the system design pages. (Most of them are > obsolete with the changing architecture anyway.) That > way, we will just have one official Docbook-based > document to maintain. Much of it is still remarkably relevant, esp. regarding FO trees and Layout system. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Documentation finished
Hi Clay, On Mon, Jun 28, 2004 at 11:54:10AM -0700, Clay Leeds wrote: > Looks pretty good. As you indicated, there are a few areas to be > improved (e.g., 'TO BE IMPROVED" and 'no data' sections), and some I spent quite some time to this documentation. The chapter on properties took quite a bit more work than I expected. Now I want to take a break. I will look at those passages later. > issues with formatting (I think they're related to the > text-align='justify' setting--perhaps the document would read better > with default (i.e., 'left') justification?), but by and large this I suppose you refer to the section titles like 'LineLayoutManager.getNextBreakPoss'. I noticed that these can be mended using hyphenate="false", but it is hard to specify that through DocBook. I think I will change those titles, and set text-align="left" for the section titles. Otherwise I am quite pleased with the justification. > looks like it will be a valuable addition to the FOP arsenal! One other > addition I'd like to see is that the fo:region-before include the > Chapter '#' in addition to the Title. I will see if I can customize the DocBook style sheets to do that. There are a few other things that may benefit from customization. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Documentation finished
Great, this makes for an excellent system design document that we can refine over time. I'm also happy you have it done in Docbook. We're doing it right the first time that way. I'd like to see it incorporated, in Docbook format, on our site. Tapestry has already managed Forrest and Docbook together (http://jakarta.apache.org/tapestry/doc.html). Before doing so, it would probably be good if you could look at our System design pages (http://xml.apache.org/fop/design/index.html), if you haven't already, and add to your document anything from them that is still relevant and useful but missing from your document. That way, when we add your document to our website, we can rid of the system design pages. (Most of them are obsolete with the changing architecture anyway.) That way, we will just have one official Docbook-based document to maintain. Thanks, Glen --- Simon Pepping <[EMAIL PROTECTED]> wrote: > Hi, > > I finished my documentation of the FOP architecture > and code. Well, > more or less; this is version 0.9. Maybe I'll add a > short introduction > or some such. See > http://www.leverkruid.nl/FOP/index.html. > > How can this be contributed to the FOP website? The > documentation > consists of a number of Docbook 4.2 XML files. Could > this be part of > the wiki? Or could it be in CVS? > > Regards, Simon > > -- > Simon Pepping > home page: http://www.leverkruid.nl > >
Re: Documentation finished
On Jun 28, 2004, at 11:25 AM, Simon Pepping wrote: Hi, I finished my documentation of the FOP architecture and code. Well, more or less; this is version 0.9. Maybe I'll add a short introduction or some such. See http://www.leverkruid.nl/FOP/index.html. Looks pretty good. As you indicated, there are a few areas to be improved (e.g., 'TO BE IMPROVED" and 'no data' sections), and some issues with formatting (I think they're related to the text-align='justify' setting--perhaps the document would read better with default (i.e., 'left') justification?), but by and large this looks like it will be a valuable addition to the FOP arsenal! One other addition I'd like to see is that the fo:region-before include the Chapter '#' in addition to the Title. How can this be contributed to the FOP website? The documentation consists of a number of Docbook 4.2 XML files. Could this be part of the wiki? Or could it be in CVS? I would think this owuld be of interest to some of the more advanced fop-users (particularly those interested in customizing via Java and/or embedding). As such, perhaps there might be a place for its inclusion in a "Docs" tab or something? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl Web Maestro Clay
Documentation finished
Hi, I finished my documentation of the FOP architecture and code. Well, more or less; this is version 0.9. Maybe I'll add a short introduction or some such. See http://www.leverkruid.nl/FOP/index.html. How can this be contributed to the FOP website? The documentation consists of a number of Docbook 4.2 XML files. Could this be part of the wiki? Or could it be in CVS? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
