On Oct 15, 6:32 pm, Sam Ruby <[EMAIL PROTECTED]> wrote: > Could it be a filter?
Hmmm. Probably could be implemented as a filter. That might be advantageous... Except that (as I understand the current state of affairs), it wouldn't be useful for much more than what my modified TreeWalker(s) do. Trouble is that (as things currently stand) the tokenizer escapes these entities, so a filter which runs *after* the tokenizer won't do any good. In my case, since I'm dealing with an already-constructed tree, I bypass the tokenizer, and a filter would work fine. > If not, I would prefer it to be in TreeWalkers base if all possible, and > not specific to any one particular DOM format. That's probably possible, too. but a filter would be better. Anyway, let me point you to the current implementation http://golem.ph.utexas.edu/~distler/code/rdoc/sanitize/ (API) http://golem.ph.utexas.edu/~distler/code/instiki/svn/lib/sanitize.rb (Source) Then we can discuss how best to fold this into HTML5lib. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] 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