HTML5 Support?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

HTML5 Support?

wdhammond (Bugzilla)
I am attempting to use your product with html 5 documents and believe
tidy does not get it right.  Are there plans to update tidy to include
the html5 specifications?

Thank you,

Wayne Hammond
--
"Reasonable people adapt themselves to the world. Unreasonable
people attempt to adapt the world to themselves. All progress,
therefore, depends on unreasonable people."
—George Bernard Shaw


Reply | Threaded
Open this post in threaded view
|

Re: HTML5 Support?

Keryx Web
wayne skrev 2011-09-09 15:25:
> I am attempting to use your product with html 5 documents and believe
> tidy does not get it right.  Are there plans to update tidy to include
> the html5 specifications?
>
> Thank you,
>
> Wayne Hammond

Tidy has not been maintained in any useful way for a couple of years,
I'm afraid.

I wrote a piece about this a while ago
http://itpastorn.blogspot.com/2010/11/tidy5-aka-future-of-html-tidy.html


--
Keryx Web (Lars Gunther)
http://keryx.se/
http://twitter.com/itpastorn/
http://itpastorn.blogspot.com/

Reply | Threaded
Open this post in threaded view
|

Re: HTML5 Support?

Bjoern Hoehrmann
In reply to this post by wdhammond (Bugzilla)
* wayne wrote:
>I am attempting to use your product with html 5 documents and believe
>tidy does not get it right.  Are there plans to update tidy to include
>the html5 specifications?

Well, I am interested in adding some "HTML5" support. I would need a ma-
chine readable list of all allowed elements and which attributes they
may have ("a@href, a@title, ...") and for all new elements the table in
http://tidy.cvs.sourceforge.net/viewvc/tidy/tidy/src/tags.c?view=markup
would have to be filled out ("<time> is like <abbr>" style information
would be a good first order approximation, but for some elements this is
not quite that simple, so anyone compiling this data would have to point
out problems like "<track> is like <br> but not allowed everywhere that
<br> is allowed").

This data would then be used to update the table above and others like
it. Then I suppose some doctype-related things need to be updated so you
get your "HTML5 doctype" out. Some of element and attribute check sub-
routines might have to be updated so you don't get false errors due to
using new features. That would roughly give you "HTML5" support in the
"Conforming documents are accepted and you don't get many wrong errors
and they come out roughly as you put them in" sense, which is about all
you can expect. I could make the attribute list myself and am happy to
use machine-readable data to update the tables, but I am not going to
make the needed "<time> is like <abbr>" documentation.
--
Björn Höhrmann · mailto:[hidden email] · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/