Message389118
| Author |
eryksun |
| Recipients |
eryksun, lemburg, methane, vstinner |
| Date |
2021年03月19日.22:13:13 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1616191993.74.0.348928927305.issue43552@roundup.psfhosted.org> |
| In-reply-to |
| Content |
> But it is not what I want for now. I want to ignore UTF-8 mode
> when `encoding="locale"` is specified.
> This is almost "only in Windows" issue, and users can use
> `encoding="mbcs"` in Windows-only script.
Why is it being specified that the current LC_CTYPE encoding should be ignored in Windows when a "locale" encoding is requested? Cross-platform C code would use mbstowcs() and wcstombs(), with the current LC_CTYPE encoding. That's Latin-1 in the initial "C" locale and defaults to GetACP() if setlocale(LC_CTYPE, "") is called, but otherwise it's whatever locale is requested by the program and supported by the system (all Windows installations support pretty much every locale). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2021年03月19日 22:13:13 | eryksun | set | recipients:
+ eryksun, lemburg, vstinner, methane |
| 2021年03月19日 22:13:13 | eryksun | set | messageid: <1616191993.74.0.348928927305.issue43552@roundup.psfhosted.org> |
| 2021年03月19日 22:13:13 | eryksun | link | issue43552 messages |
| 2021年03月19日 22:13:13 | eryksun | create |
|