RetroSearch Browse

Sat Nov 14 18:39:32 EST 2015 · https://mail.python.org/pipermail/python-dev/2015-November/142163.html

On 11/14/2015 3:21 PM, Serhiy Storchaka wrote:
> On 15.11.15 00:56, Victor Stinner wrote:
>> These encodings are rarely used. I don't think that any text editor use
>> them. Editors use ascii, latin1, utf8 and... all locale encoding. But I
>> don't know any OS using UTF-16 as a locale encoding. UTF-32 wastes disk
>> space.
>
> AFAIK the standard Windows editor Notepad uses UTF-16. And I often 
> encountered Windows resource files in UTF-16. UTF-16 was more popular 
> than UTF-8 on Windows some time. If this horse is dead I'll throw it away.

Just use UTF-8, ignoring an optional leading BOM. If someone wants to 
use something else, they can write a "preprocessor" to convert it to 
UTF-8 for use by Python.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20151114/7f745ea8/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-November/142163.html below:

[Python-Dev] Support of UTF-16 and UTF-32 source encodings