mal wrote: > Same here: UTF-16 -> UCS-2. Note that I very much favour > removing the surrogate generation in unichr() for UCS2-builds. > > If I don't here strong opposition, I'll disable this feature > which was added as part of the UCS-4 patches. unichr() > will then raise an exception as it did in version 2.1. the rationale behind this change was that unichr() should behave like the \U escape. (they both take a 32-bit character code, and turn it into a unicode string; see GvR's mails in the ucs4 thread for more on this topic). don't change one of them without considering if the other one really does the right thing. </F>
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