Message114411
| Author |
loewis |
| Recipients |
amaury.forgeotdarc, brian.curtin, loewis, tim.golden, vstinner |
| Date |
2010年08月19日.21:02:19 |
| SpamBayes Score |
7.865994e-06 |
| Marked as misclassified |
No |
| Message-id |
<4C6D9BD9.9040503@v.loewis.de> |
| In-reply-to |
<1282219348.43.0.267719038373.issue9642@psf.upfronthosting.co.za> |
| Content |
> mbcs functions don't use the wchar_t type.
That's not true. MultiByteToWideChar use LPWSTR, which is a typedef for
wchar_t*.
These functions assume that Py_UNICODE is the same type as WCHAR.
> We should just check that we are compiling under Windows:
-1, see above. In the long run, it would be really good if Python
supported a four-byte Py_UNICODE on Windows - people keep asking for it.
I have been meaning to provide versions of the mbcs codecs for years
that work for UCS-4, but haven't found the time yet to implement them. |
|