Message118268
| Author |
loewis |
| Recipients |
ixokai, lemburg, loewis, pitrou, pjenvey, ronaldoussoren, vstinner |
| Date |
2010年10月09日.11:49:50 |
| SpamBayes Score |
1.0228531e-06 |
| Marked as misclassified |
No |
| Message-id |
<4CB056DA.60006@v.loewis.de> |
| In-reply-to |
<1286621540.3177.10.camel@localhost.localdomain> |
| Content |
>> If the mere existence of the fsname encoding leads to that much
>> confusion, I think I also support its removal.
>
> Well, the fsname encoding has a hardwired value under OS X (regardless
> of the locale), which kind of justifies its existence, no?
Perhaps. We could also declare that command line arguments and
environment variables are always UTF-8-encoded on OSX (which I think
would be fairly accurate), and stop relying on the locale to determine
encodings on OSX (which Apple didn't like as a mechanism, anyway).
I think OSX converges faster to UTF-8 than the other Unices. |
|