MAL: > Bill: > > Just as an FYI, the only problem I've found so far with my last patch was > > wrt handling Unicode characters with values in the UCS-4 code space. (Not > > that there are any yet, but the code must handle that case anyway, sine I > > don't want to have to go change it later.) > Why is there a problem there ? Python currently uses UTF16 > as native format. UTF-16 surrogates are not supported though... > and probably won't be for a while. The rest of Python may not care about UTF-16, but that's no particular reason to not have this code support generating surrogates if an input UnicodeData.txt happens to have character names for code points that require surrogates. Bill
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