James Graham wrote:
> Edward Z. Yang wrote:
>> Philip Taylor wrote:
>>> Oops, I had added some test cases with non-ASCII characters in their
>>> descriptions, which unittest.py doesn't like. Fixed that now.
>> Great, thanks!
>>
>>> I get 109 failures when running on Windows, seemingly caused by
>>> Unicode issues, along the lines of:
>>>
>>> Expected: [u'ParseError', [u'StartTag', u'a\U00100000', {}]]
>>> Received: [u'ParseError', u'ParseError', u'ParseError',
>>> [u'StartTag', u'a\U00100000', {}]]
>>>
>>> but I don't really know what the problem is or how to fix it. (All the
>>> tests pass correctly for me on Linux.)
>> It looks like there's a problem with the character encoding algorithm
>> implementation on Windows... did the Python implementation roll its own
>> or are we using a built-in library?
>
> There are some known issues with UCS2/UCS32 builds of python; on the OSX
> python two tokenizer tests fail because of this.
Er that should probably read "with differences between UCS2 and UCS4 builds of Python" --~--~---------~--~----~------------~-------~--~----~ 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