Ok,

thanks Jasha for your exclusively clear answer!

BTW, the page http://cocoon.apache.org/2.2/blocks/fop/1.0/1333_1_1.html (A complete list of all available Sitemap components, FOPNG) doesn't even exist.

- mika -

Jasha Joachimsthal kirjoitti:
Hi Mika,

cocoon-fop-ng-impl uses FOP 0.9x. cocoon-fop-impl uses FOP 0.20.x
The number of the Cocoon FOP block does not follow the FOP versioning.
Regards,

Jasha Joachimsthal
www.onehippo.com
Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA
94952-3329 +1 (707) 773-4646



-----Original Message-----
From: Lehtonen, Mika [mailto:[EMAIL PROTECTED] Sent: vrijdag 15 augustus 2008 10:39
To: users@cocoon.apache.org
Subject: Re: Cocoon 2.2 FOP

Am I asking something silly or too obvious? I'd just like to get a list as the following, which includes one column also for the Cocoon 2.2 FOP block.

http://xmlgraphics.apache.org/fop/compliance.html

thanks,
mika

Lehtonen, Mika kirjoitti:
Hi again,

taking second steps on Cocoon 2.2 and I started to wonder
whether the
version number of the FOP block follows the official FOP
versioning.
I have been using some 0.9x FOP in Cocoon 2.1.11, because the old
0.20.5 was too far from the standard. So I have now my XSL-FO files ported to work with that 0.9x. Do they work with Cocoon 2.2 and its FOP block?

- mika -


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



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


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

Reply via email to