Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 64979 invoked by uid 500); 3 Jun 2003 07:38:30 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 64964 invoked from network); 3 Jun 2003 07:38:29 -0000 Received: from dobit2.ugent.be (HELO dobit2.rug.ac.be) (157.193.42.8) by daedalus.apache.org with SMTP; 3 Jun 2003 07:38:29 -0000 Received: from allserv.UGent.be (allserv.ugent.be [157.193.40.42]) by dobit2.rug.ac.be (8.12.8/8.12.8) with ESMTP id h537cftN008924 for ; Tue, 3 Jun 2003 09:38:41 +0200 (MEST) Received: from otsrv1.iic.rug.ac.be (otsrv1.iic.ugent.be [157.193.121.51]) by allserv.UGent.be (8.12.8/8.12.8) with ESMTP id h537ce7w000993 for ; Tue, 3 Jun 2003 09:38:41 +0200 (MEST) Received: from [192.168.123.102] (host102 [192.168.123.102]) by otsrv1.iic.rug.ac.be (8.11.6/8.11.6) with ESMTP id h537cex27618 for ; Tue, 3 Jun 2003 09:38:40 +0200 Subject: Re: TidySerializer From: Bruno Dumon To: cocoon-dev@xml.apache.org In-Reply-To: <200306021757.53626.torstenknodt@datas-world.de> References: <84F0A43A4248CE45B5C0E20F4C40779C34C3E1@naomi.webworks.nl> <1054568300.21067.1368.camel@yum.ot> <200306021757.53626.torstenknodt@datas-world.de> Content-Type: text/plain Organization: Outerthought Message-Id: <1054625891.32336.1441.camel@yum.ot> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 03 Jun 2003 09:38:12 +0200 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 2003-06-02 at 17:57, Torsten Knodt wrote: > > When TidySerializer would be in cocoon, more people would try it. And perhaps > there will be someone who cleans it up and adds SAX and DOM support. That's right. > Also > perhaps someone integrates it into xalan. > And for the namespace problem. Tidy hides it only for (X)HTML. It doesn't hide > it for WML, where you have the same. Everywhere where you have a DTD for the > output and using different namespaces during creation, you can have the > problem. > We have a current problem, that cocoon is not useable in many cases, because > it's nearly impossible to create valid (x)html. And again I'm wondering why? Of the tree reasons given earlier: AC> 1) As a fix for the "the namespace problem" AC> 2) When human-readable HTML output is needed AC> 3) To validate the output to a dtd only number 1 really causes problems, the others are merely conveniences. Those are important too, but don't make it "impossible to create valid (x)html". > With TidySerializer we would > have a temporary inofficial solution. There is also HTMLGenerator using jtidy > and noone says, we wait for the web pages to have valid (X)HTML. While I do find this a false comparison (we don't control webpages, but we do control what we generate in our pipelines), please understand that I'm not opposed to a tidyserializer. I'm just figuring out why I would use it. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center bruno@outerthought.org bruno@apache.org