python 2.7 and unicode (one more time)
Chris Angelico
rosuav at gmail.com
Sat Nov 22 21:11:56 EST 2014
More information about the Python-list mailing list
Sat Nov 22 21:11:56 EST 2014
- Previous message (by thread): python 2.7 and unicode (one more time)
- Next message (by thread): python 2.7 and unicode (one more time)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Nov 23, 2014 at 12:52 PM, <random832 at fastmail.us> wrote: > On Sat, Nov 22, 2014, at 18:38, Mark Lawrence wrote: >> ... >> That is a standard Windows build. He is again conflating problems with >> using the Windows command line for a given code page with the FSR. > > The thing is, with a truetype font selected, a correctly written win32 > console problem should be able to print any character without caring > about codepages (via use of WriteConsoleW instead of WriteFile). You > cannot rely on having the codepage set to 65001, especially since 65001 > isn't actually a fully supported codepage. Is that true? Does WriteConsoleW support every Unicode character? It's not obvious from the docs whether it uses UCS-2 or UTF-16 (or maybe something else). ChrisA
- Previous message (by thread): python 2.7 and unicode (one more time)
- Next message (by thread): python 2.7 and unicode (one more time)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list