Edward Z. Yang wrote: > Hello all, > > Presently, all documentation for the parser tests format is at [1]. I > think this is a less than ideal situation. Mostly because I wasted an > hour writing what I thought were missing docs. But also because if a > person is interested in what the parser tests have to say, they'll have > the testdata directory in front of them, and it would make good sense > for there to be a README.txt file that explains things right then and there.
Well at the very least we should have a link to the wiki page. However I don't have any strong objections to checking the documentation in as long as it stays in sync with the wiki. > Also, the Tree Construction Tests is presented as a very specific > format. However, parts of the format are reused in encoding tests. So I > think that it might make more sense for there to be a general container > format, which simply encodes a list of tests, and then define the > semantics of each of the sections on a suite by suite basis. That is certainly reasonable. I think you have commit privileges for html5lib so if you check in whatever you have written then it will be easier to improve it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "html5lib-discuss" group. To post to this group, send email to html5lib-discuss@googlegroups.com To unsubscribe from this group, send email to html5lib-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/html5lib-discuss?hl=en-GB -~----------~----~----~----~------~----~------~--~---
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