Geoffrey Sneddon wrote: > I'd argue you shouldn't be porting the Python implementation to other > language, but rather writing from the spec (this should avoid copying > bugs in the Python implementation), even if you do look at the Python > implementation to see how it goes about implementing certain points. > Whatever you put in the Python implementation you aren't going to get > it to nicely map to all other languages. The Python implementation > should be written as it seems best to do in Python, the Ruby one in > Ruby, and the PHP one in PHP.
I would agree with this, especially with regards to scaffolding. My new entry point is PH5P, and I'm slowly going through the old code and updating it to the new HTML5. The hardest part was getting it to be testable with testdata, which is actually quite implementation dependent. Cheers, Edward --~--~---------~--~----~------------~-------~--~----~ 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