Thanks Keiron,

I'll forward this to the Cocoon-dev list and see what they want to do :)

> -----Original Message-----
> From: Keiron Liddle [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 21 August 2001 6:46 am
> To: [EMAIL PROTECTED]
> Subject: Re: Cocoon 2 & FOP: Sharing SAX events
> 
> 
> John,
> 
> I have attached a diff that should help with the changed api.
> I have tried it with the latest cocoon cvs (5 minutes ago) at 
> it works for
> me. It will only work with the latest fop cvs.
> 
> Is this what you want.
> 
> Is there anything that should be done differently?
> 
> Keiron.
> 
> On Mon, 20 Aug 2001 23:07:27 COFFMAN Steven wrote:
> > Whups. John's recent Cocoon 2 patch did not update to FOP 
> 0.20 API, but
> > was
> > just adding PCL and PS as valid outputs and refactoring for 
> the old FOP
> > API.
> > 
> > Peter West is doing some good work on serializing the parse 
> events, and
> > generally opening up FOP to be less like a black box. His 
> code is still
> > experimental, and not part of CVS yet however. I'm not sure 
> what Cocoon's
> > release schedule is, but FOP 0.20 has a number of major 
> improvements that
> > we'd like to get into Cocoon 2.0 final (like less than 
> infinte memory
> > required for large documents).
> > 
> > BTW, John (as a Cocooner) is not subscribed to fop-dev, so 
> please Cc him
> > if
> > there's anything you want him to know. 
> > -Steve
> 


=======================================================================
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission.  There is no intention to
create any legally binding contract or other commitment through the use
of this email.

Experian Limited (registration number 653331).  
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF

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

Reply via email to