2007/6/11, Sam Ruby: > > I'm a "release early and often" kinda guy.
+1 > So to all the people who are creating new function (like error messages > on out of place li's and whitespace filters) without creating test > cases, shame on you. :-P I know I know... I've just added tests for the whitespace stripping filter (using the strip_whitespace option of the HTMLSerializer). > Oh, and by the way, if other language ports start showing up here (C#, > PHP, Java, whatever), I would help keep these implementations in sync > too. I know that Thomas Broyer would prefer that the implementations be > kept separate, but my feeling is that anything we can do to increase the > size of the development community, the higher the quality of all of the > implementations will be. I'll try to work more on (well, actually, to work on, not work "more" ;-) Twintsam than on html5lib in the next few weeks. The reason I think keeping Twintsam separate from html5lib is better is that I'd like Twintsam to first act as an XmlReader (i.e. without reordering elements, such as moving things into <head>) then add a "tree builder" on top of this. This is I think enough different from html5lib's design to deserve its own development tree, roadmap et al. And of course, .NET's XML processing is far different from Python's or Ruby's ones. The next step would be to add a DOMImplementation to create XmlNode's implementing the specialized interfaces defined in the spec. -- Thomas Broyer --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "html5lib-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/html5lib-discuss?hl=en-GB -~----------~----~----~----~------~----~------~--~---
