cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject RE: TidySerializer
Date Mon, 02 Jun 2003 15:38:21 GMT
On Mon, 2003-06-02 at 17:05, Arjé Cahn wrote:
> I'm using the TidyUI standalone from the Tidy sourceforge community (http://tidy.sourceforge.net/),
which is very good, but the JTidy port has been abandoned - how awfull!
> 
> But "the namespace problem" - that was one of my reasons, too.
> 
> When should one use the TidySerializer?
> ---------------------------------------
> 1) As a fix for the "the namespace problem"
> 2) When human-readable HTML output is needed
> 3) To validate the output to a dtd
> 
> --> otherwise, use the HTMLSerializer
> 
> I *am* a little worried about the fact that the JTidy community has
> died; we'll miss their backup. But I do think the TidySerializer is
> good think next to the traditional HTMLSerializer, because Tidy does
> things to you HTML that might leave it in a non-machine-readable
> state. 
> For example; we're running CHTML pages (i-mode) live from Cocoon, and
> those damn i-mode browsers won't take code that isn't aligned to the
> left (aargh?!). 
> 
> Bruno?

You expect me to give my blessing or so? I don't really care that much
about it all. Arguments 2 and 3 are reasonable, and certainly have their
uses.

What I wanted to avoid though is that problems with the normal HTML
serializer (like the namespace or textarea problem) would be hidden by
jtidy, and that users would be pointed to the tidyserializer as the
solution for these problems. One should not forget the performance
impact of the tidyserializer: it uses an additional thread and has to
reparse the serialized output.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


Mime
View raw message