python 2.7 and unicode (one more time)

Chris Angelico rosuav at
Sun Nov 23 17:39:07 CET 2014

On Mon, Nov 24, 2014 at 3:33 AM, Dennis Lee Bieber
<wlfraed at> wrote:
> On Sat, 22 Nov 2014 20:52:37 -0500, random832 at declaimed the
> following:
>>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
>         Why would that be possible? Many truetype fonts only supply glyphs for
> single-byte encodings (ISO-Latin-1, for example -- pop up the Windows
> character map utility and see what some of the font files contain.

A program should be able to print those characters even if they all
look identical. Chances are you can copy and paste them into something
else. But yes, finding a suitable font that covers the whole Unicode
range is *hard*. I've struggled with this one with a few programs (and
I still haven't managed to get VLC to satisfactorily display subtitles
that include Chinese characters).


More information about the Python-list mailing list