On approximately 4/28/2009 10:00 AM, came the following characters from the keyboard of Martin v. Löwis: > An alternative that doesn't suffer from the risk of not being able to > store decoded strings would have been the use of PUA characters, but > people rejected it because of the potential ambiguities. So they clearly > dislike one risk more than the other. UTF-8b is primarily meant as > an in-memory representation. The UTF-8b representation suffers from the same potential ambiguities as the PUA characters... perhaps slightly less likely in practice, due to the use of Unicode-illegal characters, but exactly the same theoretical likelihood in the space of Python-acceptable character codes. -- Glenn -- http://nevcal.com/ =========================== A protocol is complete when there is nothing left to remove. -- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
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