On Thursday 14 March 2002 09:00, Nicola Ken Barozzi wrote:
>. . .
> > 1. FopParser parses and validates the input XSL-FO document
> Not needed if using Cocoon as a pipeline.
>. . .

Right, but it's so easy that we might as well keep it for easier 

>. . .
> What I would like to see, is that FOP stops discussing about the
> logging, resolving, pipelineing and stuff and starts to focus on the
> core functionality.
>. . .

Yes, but IMHO resolving (in the sense of "resolving FO object 
properties" like I think is meant by FOP) is part of the core 
functionality. I'm talking about computing presentation attributes for 
child elements based on their parent's attributes. 

>. . .
> This can big opportunity also for other projects to collaborate in
> the rendering.
> JFor, for example (I don't remember who maintains it ;-P)
>. . 
That's me by the way ;-)
(but I haven't done much lately)

 Bertrand Delacrétaz (codeconsult.ch, jfor.org)

 buzzwords: XML, java, XSLT, cocoon, mentoring/teaching/coding.
 disclaimer: eternity is very long. mostly towards the end. get ready.

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to