Ian Kelly ian.g.kelly at gmail.com
Thu Nov 8 13:48:23 EST 2012

• Previous message (by thread): Right solution to unicode error?
• Next message (by thread): Right solution to unicode error?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Thu, Nov 8, 2012 at 11:32 AM, Oscar Benjamin
<oscar.j.benjamin at gmail.com> wrote:
> If I want the other characters to work I need to change the code page:
>
> O:\>chcp 65001
> Active code page: 65001
>
> O:\>Q:\tools\Python33\python -c "import sys;
> sys.stdout.buffer.write('\u03b1\n'.encode('utf-8'))"
> α
>
> O:\>Q:\tools\Python33\python -c "import sys;
> sys.stdout.buffer.write('\u03b1\n'.encode(sys.stdout.en
> coding))"
> α

I find that I also need to change the font.  With the default font,
printing '\u2013' gives me:

–

The only alternative font option I have in Windows XP is Lucida
Console, which at least works correctly, although it seems to be
lacking a lot of glyphs.

---

• Previous message (by thread): Right solution to unicode error?
• Next message (by thread): Right solution to unicode error?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list