W3C home > Mailing lists > Public > html-tidy@w3.org > October to December 2000

RE: clean XHTML : what's new?

From: philippe barthelemy <philippe.barthelemy@bdesign.fr>
Date: Fri, 15 Dec 2000 04:09:34 -0500 (EST)
Message-ID: <1355D3A54302D311BEE100902751554F85DAD8@milou.winwise.domain>
To: Bjoern Hoehrmann <derhoermi@gmx.net>, html-tidy@w3.org
ok, I may have been wrong.

My situation is :
I took a notoriously badly written page ( http://www.6sens.com/ , sorry it's
a French site ).
I wanted to XHTMLize it.

As real-world "validation", I tried to open the page  both with "XMLspy"
from Icon Information System and to "LoadXML" using microsoft parsers. The
output from HTMLtidy failed to load in both cases
(I just glanced at the XHTML specs, I admit.)

I did some corrections by hands, and I mananaged to load it.
Examples of corections: enclosed script content in CDATA, adding a white
space in empty comments 
	( ie : from <----> to <-- --> ) .

I do understand that a lots a w3c specs implementations are rather fuzzy. I
do not want to argue about it. ( especially, because I am likely to be wrong
quite often...)

Was I am looking for is a clear Status Report on HTMLtidy XHTML compliance (
both as compared to the specs and as compared to realworld "validation" ).
Ther are 2 items above to add on the to-do list .

Anyone wanting to centralize the datas ( or is it already done somewhere ? )


thanks Bjoern,
regards to you all,

Philippe



-----Original Message-----
From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net]
Sent: jeudi 14 décembre 2000 21:07
To: philippe barthelemy; html-tidy@w3.org
Subject: Re: clean XHTML : what's new?


* "philippe barthelemy" <philippe.barthelemy@bdesign.fr> wrote:
| XTML requires a CDATA section within a <script> block,

Thats not correct. XML does not know content model CDATA for Elements, so
the
content of a script element is interpreted as markup. To keep the script
readable, one could use a CDATA section, but there is no must to do so, you
can use

  if (a &lt; b)

too. Further, this is only necessary if the script includes characters, that
need to be escaped.

The problem is, that current browsers don't know CDATA sections and ignore
the
script completly. I've suggested the following to get around this:

  <script type="text/javascript">
  <!-- --> <![CDATA[ /> <!--

    for (var i=0; i < 10; i++) { ... }

  // --> <! ]]>
  </script>

Tidy should offer an option to extract the script and put it into a seperate
file.
--
Björn Höhrmann ^ mailto:bjoern@hoehrmann.de ^ http://www.bjoernsworld.de
am Badedeich 7 ° Telefon: +49(0)4667/981ASK ° http://bjoern.hoehrmann.de
25899 Dagebüll # PGP Pub. KeyID: 0xA4357E78 # http://learn.to/quote [!]e
  "Everything we see or seem is but a dream within a dream" - E.A. Poe
Received on Friday, 15 December 2000 04:11:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 April 2012 06:13:44 GMT