[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Unprintable characters

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] Unprintable characters
From: Greg Ewing <greg.ewing@xxxxxxxxxxxxxxxx>
Date: Wed, 03 Mar 2010 11:54:48 +1300
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Tue, 02 Mar 2010 17:44:40 -0500
In-reply-to: <5f89b79c1003020746l3791acd1i4f71cd71f576554f@xxxxxxxxxxxxxx>
References: <20100228105625.GA24691@xxxxxxxxxxxx> <ccaebeed1002280941x21b92894p78b6397f94559e2e@xxxxxxxxxxxxxx> <20100302070941.GB3890@xxxxxxxxxxxx> <64ddb72c1003012325p3f31182br1822fc382de4434a@xxxxxxxxxxxxxx> <4B8CDDB0.70708@xxxxxxxxxxxxxxxx> <5f89b79c1003020746l3791acd1i4f71cd71f576554f@xxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx
User-agent: Mozilla Thunderbird 1.0.5 (Macintosh/20050711)

B W wrote:

Assuming these are UTF8 characters, the encoding is backwards compatiblewith ASCII. Therefore, you should be able to use the ASCII chart toclassify non-printable character codes (0-31 and 127).


There's no standard ASCII code for arrow keys, however, and
I've seen at least some systems translate them into non-ASCII
unicode characters.

--
Greg

Follow-Ups:
- Re: [pygame] Unprintable characters
  - From: B W

References:
- Re: [pygame] Unprintable characters
  - From: Chris McCormick
- Re: [pygame] Unprintable characters
  - From: René Dudfield
- Re: [pygame] Unprintable characters
  - From: Greg Ewing
- Re: [pygame] Unprintable characters
  - From: B W

Prev by Author: Re: [pygame] Unprintable characters
Next by Author: Re: [pygame] super surface... a surface made up of many smallersurfaces
Previous by thread: Re: [pygame] Unprintable characters
Next by thread: Re: [pygame] Unprintable characters
Index(es):
- Author
- Thread