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? Regards, Arje Cahn > -----Original Message----- > From: Torsten Knodt [mailto:[EMAIL PROTECTED] > Posted At: 02 June 2003 15:21 > Posted To: Cocoon Dev List > Conversation: TidySerializer > Subject: Re: TidySerializer > > > On Monday 02 June 2003 12:57, Arjé Cahn wrote: > AC> Torsten, am I missing something? Have I forgotton why we > needed it? What > AC> are your reasons to implement a TidySerializer? > AC> I'm sure I had my reasons to need the TidySerializer; but > I simply forgot > AC> them. > My problem where unreadable XML/ HTML output (for humans) > because of not > working indent, dtd's which weren't checked at output (tidy > can print out > errors) and the "namespace problem". > For you it was only textarea when I'm not wrong. But a hint. > I saw, that jtidy > has many open patches, bugs and feature requests (see > http://sourceforge.net/projects/jtidy). Perhaps incorporating > them could > help. The last jtidy update was in august 2000. In march 2002 > someone claimed > he wanted to make a new release. Someone asked later about > it, but it seems > there was no answer. > > Regards > Torsten > > -- > Domain in provider transition, hope for smoothness. Planed > date is 1.7.2003. > >
