f FOP will have all the properties implemented.
Let me know if you get some more information abut these rendering engines.
Thanks,
Dhiraj
- Original Message -
From: "Michiel Verhoef" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 28, 2002 12:4
$ The evaluation version does not include the API
$ documentation: it is meant
$ to let people assess formatting quality, memory footprint and
$ performance.
$ In our view, detailed knowledge of API is not necessary for making a
$ purchase
$ decision.
Well, that depends on the requirements o
Matt Savino wrote:
>Thanks Betty for filling in some of the blanks. (I was mixing up XEP and
>PassiveTex in a post I made earlier. I forgot XEP is RenderX.)
>
>I just had a couple of questions:
>
>Antenna House is Windows-only right?
>
>Do you think XEP's command line-driven approach would work
Thanks Betty for filling in some of the blanks. (I was mixing up XEP and
PassiveTex in a post I made earlier. I forgot XEP is RenderX.)
I just had a couple of questions:
Antenna House is Windows-only right?
Do you think XEP's command line-driven approach would work within a J2EE
internet applic
Aurelien:
I recently went through this exercise. I evaluated FOP, XEP and
AntennaHouse. I didn't evaluate PassiveTex. I started putting together
analysis sheet together of the different products but haven't completed it
yet. For commercial projects I think both XEP and Antenna House
I have to do a comparison between the different existing XSL-Fo processors.
I focused on these ones:
-FOP, Apache
-XEP, RenderX
-Antenna House XSL Processor
-PassiveTeX
Could you give me their "good and bad parts"?
Who support them?
What are the aims of each one about the XSL specification?
Fina
