Edward Z. Yang wrote: > Edward Z. Yang wrote: >> The Python and Ruby implementations of HTML5 both extend the spec a >> little by distinguishing between different types of parse errors. This >> is quite useful functionality, but also proprietary. It would be great >> if we could see these error codes and messages standardized in some >> fashion, so that translation efforts can be centralized, etc. Have there >> been any plans to do so? > > I sent this message a while back, and didn't see any response. So I'm > prodding the issue again, and I've also CC'ed the imps list.
There have been no plans that I know of but you are welcome to reuse the type definitions if you like. I also have no objections to documenting them in some implementation-independent format if other people are likely to find them useful. --~--~---------~--~----~------------~-------~--~----~ 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