Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 79864 invoked from network); 9 Feb 2000 02:03:15 -0000 Received: from dnai-216-15-97-206.cust.dnai.com (HELO kali.betaversion.org) (216.15.97.206) by locus.apache.org with SMTP; 9 Feb 2000 02:03:15 -0000 Received: from apache.org(firewall-95.exoffice.com[207.33.160.95]) (2488 bytes) by kali.betaversion.org via smail with P:esmtp/R:internet/T:smtp (sender: ) id for ; Tue, 8 Feb 2000 18:04:21 -0800 (PST) (Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Sep-21) Message-ID: <38A0CAD3.2A34856B@apache.org> Date: Tue, 08 Feb 2000 18:02:59 -0800 From: Pierpaolo Fumagalli Organization: Apache Software Foundation X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: disable-output-escaping References: <38A0BBBC.248D63DD@exoffice.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Assaf Arkin wrote: > > > BTW, while I'm looking at the Cocoon code, the way Cocoon is currently set > > up, I don't see how any of the xsl:output options are supported. But I > > could be misreading the code? > > Pier just explained to me why Cocoon does not support xsl:output. Simply > it can run more than one transformation on the same document, not > knowing which xsl:output to use, and the output actually depends on how > Cocoon wants to present it based on its site map, not what the > stylesheet has in mind. That's exactly the point... I hate because it tells xslt to be what it's not, a serializer instead of a filter... > What they do right now is figure out the xsl:output properties, do a > transaformation or two, process the output if necessary, and as a last > step send it to the serializers with the proper output. I'd say... Forget about and configure the instance of your serializer accordingly to the results you want to have... I don't want to patch all the code to see when is there or not, merging the different results, comparing them, making a whole mess of it, and then reporting that in the first and nth stylesheet there are some incompatibilities... IMVHO what the W3C should be doing right now is removing that thing from the XSLT spec and creating a new XML Serialization spec+API... Pier -- -------------------------------------------------------------------- - P I E R - stable structure erected over water to allow the docking of seacraft -------------------------------------------------------------------- - ApacheCON Y2K: Come to the official Apache developers conference - -------------------- --------------------