W3C home > Mailing lists > Public > html-tidy@w3.org > January to March 2003

Re: observing HTML rules when converting to XML

From: Piotr Banski <bansp@venus.ci.uw.edu.pl>
Date: Wed, 5 Feb 2003 11:08:46 +0100 (CET)
To: Bjoern Hoehrmann <derhoermi@gmx.net>
cc: html-tidy@w3.org
Message-ID: <Pine.LNX.4.21.0302051058130.1449-100000@venus.ci.uw.edu.pl>

Hi Bjoern,

On Wed, 5 Feb 2003, Bjoern Hoehrmann wrote:
> * Piotr Banski wrote:
> >Converting an HTML file to XML, I noticed that Tidy relocates bits of
> >markup trying to be HTML compliant. In the case at hand, it removes <meta>
> >elements from within <td> elements and puts the former at the top of the
> >output file. The comment is: "Warning: <meta> isn't allowed in <td>
> >elements".
> >
> >But it's XML I'm converting to, so why should it care about what HTML
> >allows or not? Is this a bug, or a feature ( ;-) ), please?
> It's a feature. Tidy tries to fix your invalid markup, that's what Tidy
> is written for.

My point was that the markup in question is not invalid XML. or rather,
that Tidy has no way of knowing that. Given that Tidy offers the option of
translating HTML into XML, which I'm sure is the reason many people use
this tool nowadays, "fixing invalid markup" does not mean, or should not
mean IMO, the same as "making markup compliant with *some* version of
HTML". Naturally, if what you're saying is the Dev Team's point of view
then I have no other way but to accept it. However, not relocating markup
in HTML->XML translation still seems a plausible config option to me.

Thanks for your time,

Received on Wednesday, 5 February 2003 05:09:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:38:53 UTC