On 24 Dec 2008, at 22:14, Edward Z. Yang wrote:
> > James Graham wrote: >>> 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" > > So, in PHP-land, if the built-in implementation doesn't work, you code > it up yourself. :-) I might take a look at triangulating this case a > little further; I'll report back if I find anything. Yeah, I started an entire Unicode implementation in userland PHP. Let's just say it became rather large while getting nowhere. :) This isn't really a case of the built-in implementation not working, it's just the built-in implementation is defined to use either UCS2 or UCS4 depending on a compile-time flag, which can end up being rather fun to deal with (look at ifragment in anolislib/utils.py in Anolis for example). -- Geoffrey Sneddon <http://gsnedders.com/> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "html5lib-discuss" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
