Re: Patch for "HTML5" support

Hi Bj=F6rn,

Great to hear about this new work.   I have long since been pushed back to =

the server side and, thus, have lost touch with current trends in browser =

based app development using Javascript, HTML5, SVG, MathML, etc.   So I =

look forward to learning from your efforts.

 From a process POV, however, perhaps a good approach would be to create a =

new branch in CVS and commit your changes there.   It would let folks start =

working with your code in the "real world" as you say.  But it would also =

keep the mainline stable until you feel the HTML5 support is ready for =

prime time.

At a minimum, put a label on the current code before checking in and we can =

still build and/or branch from that point if needed (e.g. to make bug fixes =

on the "old" Tidy).

In any case, +1 for checking it in.   If you find it necessary to make =

breaking changes to support new features, I trust your judgement on the =

matter.   I remember making changes to preserve character entities at one =

point and I also found breaking changes were needed.   So I have a bit of a =

feel for what you're talking about.

-Charlie

At 05:51 AM 11/5/2011 +0100, Bjoern Hoehrmann wrote:
>* Bjoern Hoehrmann wrote:
> >If there is enough interest in this that we get some test reports to the
> >[email protected] mailing list, and people can't find major
> >bugs, I might polish the patch and commit it.
>
>http://lists.w3.org/Archives/Public/www-archive/2011Nov/0007.html has a
>bit more polished version, I sorted some table entries, this should deal
>with data-* attributes, and I made the tidyAttrIsProp changes I noted. I
>also note that none of the "HTML5" named character references are added.
>I am unsure how the logic for those should work, four problems:
>
>   * It is unclear to me that this new feature has been properly tested
>     in the real world, supporting all the new ones may break things.
>
>   * There are now "foo" and "foo;" entities to accomodate the "missing
>     semicolon" problem to some degree. Tidy could do the same simply by
>     keeping the semicolon around with an appropriately changed table
>
>   * Some entities apparently resolve the multiple characters now. That
>     is a bit of a problem as it makes generating the entities from the
>     characters a good bit harder; also, this would require changes to
>     the data tables, would probably have to write { 0xABCD, 0x0000 } or
>     some such for lack of Unicode escape support in old compilers.
>
>   * Some of these entities are fairly new. When should Tidy generate
>     the new ones? Should there be an option to control this?
>
>Generally, I would probably put support for them on the "someday, maybe"
>pile along with inline SVG and MathML support, when there is evidence of
>these features being supported (by, say, all major search engines, where
>such support matters).
>--
>Bj=F6rn H=F6hrmann =B7 mailto:[email protected] =B7 http://bjoern.hoehrm=
ann.de
>Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld.=
de
>25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.=
de/



---------------------------------------------------------------------------=
---
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1