Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 73916 invoked from network); 11 Aug 2000 08:57:39 -0000 Received: from p3e9b81e0.dip.t-dialin.net (HELO siteos.de) (62.155.129.224) by locus.apache.org with SMTP; 11 Aug 2000 08:57:39 -0000 Received: from siteos.de (Aragorn.siteos-lokal.de [192.168.1.101]) by siteos.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id KAA23604; Fri, 11 Aug 2000 10:57:13 +0200 Message-ID: <3993C156.83F6069@siteos.de> Date: Fri, 11 Aug 2000 11:03:18 +0200 From: Hans-Guenter Stein Organization: SiteOS AG X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "cocoon-users@xml.apache.org" , "xsl-list@mulberrytech.com" Subject: XSLT and formatters Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Any suggestions towards the following? I produce html-output the following way: XML/XSP input -----(XSLT)----> XML-output ----(standard html-formater applied by Cocoon)---> HTML-output The problem is, that the XSLT that produces the XML-outputbe comes a performance issue simply because the XSLT-stylesheets contain A_LOT of HTML formating tags (i.e. tables in tables in tables ...) So the XSLT-processor spends most of the time in parsing tags that have nothing to do with the data (a page might well contain a few lines of data enclosed in 100-200 table-cells). Now: is there any solution for inserting all the surrounding table-formating stuff into the final HTML-output without having the XSLT-processor parsing all the table-formating and building a very large DOM-object?