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
-----Original Message-----
From: John Morrison [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 20, 2001 4:48 PM
To: COFFMAN Steven
Subject: RE: cocoon 2
Hi Steven,
Sorry, I don't believe that my patch fixes it, all it really does (and dims
did most of the refactoring) is add pcl and postscript to the available
serializers. What we would like to do however is hook our SAX events
straight into FOPs. How easy do you think it would be?
J.
PS, if you want a quicker response my work email is
[EMAIL PROTECTED] I'm online continiously all day (GMT) from
8.20am till 4(ish)
> -----Original Message-----
> From: COFFMAN Steven [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 20 August 2001 4:11 pm
> To: 'John Morrison'
> Subject: cocoon 2
>
>
> Hi John,
> The FOP team was going to submit a Cocoon 2 patch for our FOP 0.20
> release, but before we did so, your patch changed things. Does your patch
> work with the new version of FOP (which breaks the old API)? If so, cool,
> otherwise we'll try to get a patch out quick.
> -Steve
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
