Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of michael.wechner@wyona.com
 designates 195.226.6.68 as permitted sender)
Message-ID: <438D62D4.2050906@wyona.com>
Date: Wed, 30 Nov 2005 09:29:08 +0100
From: Michael Wechner <michael.wechner@wyona.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Antennahouse XSL Formatter Serializer
References: <438C58BD.7070207@abs.de> <438D608E.3010408@daidalos.nl>
In-Reply-To: <438D608E.3010408@daidalos.nl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Geert Josten wrote:

> Yes, I am interested.


me too. I think it's always good to be able to use/compare different 
implementations.

> Maybe you can put it on the scratchpad of Cocoon? (don't ask me how!)


you might want to create a block similar to the FOP block src/blocks/fop 
and make it optional

Michi

>
> Have you compared the performance with FOP and/or XEP engine? What is 
> the (estimated) gain?
>
> Regards,
> Geert
>
> Michael Wirz wrote:
>
>> Dear cocoon Users,
>>
>> since I am working on a project using cocoon 2.1.5 and we have been
>> using the Antennahouse XML, XSL/FO to PDF Formatter for
>> performance reasons, I developed a small serializer for this formatter.
>> It calls XSLFormatter via an external Shellskript, the command to
>> be executed can be configured in the serializer declaration of the 
>> sitemap.
>> It expects the XML/FO input from stdin and pipes the pdf to stdout --
>> just as a serializer should work.
>>
>> If there is any interest in my solution I'd like to hear from you.
>>
>> Best regards,
>> Michael Wirz
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org