![](https://secure.gravatar.com/avatar/5b37e6b4ac97453e4ba9dba37954cf79.jpg?s=120&d=mm&r=g)
Feb. 18, 2013
5:11 p.m.
Hi, On Mon, Feb 18, 2013 at 12:37 PM, Eleytherios Stamatogiannakis <estama@gmail.com> wrote:
An API like the one you propose would be very nice, and IMHO would give a substantial speedup.
https://bitbucket.org/cffi/cffi/issue/57/shortcuts-to-encode-decode-between-...
May i suggest, that for generality purposes, the same API functions should also be added for UTF-16, UTF-32 ?
Well, I'll rather wait for someone to clearly shows the purpose of that. As I said in the above issue, modern programs tend to use UTF-8 systematically, unless they are on an OS with a precise notion of wider unicodes (like Windows), in which case Python's own unicode representation matches already and can be used directly in "wchar_t*". A bientôt, Armin.