Joao S. O. Bueno, 29.07.2011 13:22: > On Fri, Jul 29, 2011 at 1:37 AM, Stefan Behnel wrote: >> Brett Cannon, 28.07.2011 23:49: >>> >>> On Thu, Jul 28, 2011 at 11:25, Matt wrote: >>>> >>>> - What policies are in place for keeping parity with other HTML >>>> parsers (such as those in web browsers)? >>> >>> There aren't any beyond "it would be nice". >>> [...] >>> It's more of an issue of someone caring enough to do the coding work to >>> bring the parser up to spec for HTML5 (or introduce new code to live >>> beside >>> the HTML4 parsing code). >> >> Which, given that html5lib readily exists, would likely be a lot more work >> than anyone who is interested in HTML5 handling would want to invest. >> >> I don't think we need a new HTML5 parsing implementation only to have it in >> the stdlib. That's the old sunny Java way of doing it. > > I disaagree. > Having proper html parsing out of the box is part of the "batteries > included" thing. Well, you can easily prove me wrong by implementing this. Stefan
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4