Message118367
| Author |
loewis |
| Recipients |
ixokai, lemburg, loewis, pitrou, pjenvey, ronaldoussoren, vstinner |
| Date |
2010年10月11日.14:38:38 |
| SpamBayes Score |
0.000539122 |
| Marked as misclassified |
No |
| Message-id |
<4CB3216D.4020804@v.loewis.de> |
| In-reply-to |
<70b6a53c-7aee-c2c0-b567-b3fd31ca1052@me.com> |
| Content |
> There is one reason for not wanting to assume that the encoding is
> always UTF-8: the user might access the system from a non-UTF8
> terminal (such as when logging in with an SSH session from a system
> not using UTF-8, or using an alternate terminal application). IMHO
> these are minor enough use-cases that we could just enforce that the
> encoding is UTF-8 on OSX.
Ok, that's enough of an expert statement for me to settle the OSX
case: we will always assume that environment data is UTF-8 on OSX
(leaving the rest to the surrogate escape handler). |
|