[ python-Bugs-1231488 ] chr() returns ? when input > 127 in OS X

[SourceForge.net]

Bugs item #1231488, was opened at 2005-07-02 15:52
Message generated for change (Settings changed) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1231488&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Craig Howard (craighoward)
Assigned to: Nobody/Anonymous (nobody)
Summary: chr() returns ? when input > 127 in OS X

Initial Comment:
When using macpython in OS X Tiger, chr(130) should
return an  "e" with an accent symbol above it. Instead
it returns a "?", as it does with any number above 127. 

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2005-07-06 07:17

Message:
Logged In: YES 
user_id=21627

I'm pretty sure it is like mwh suggest - this is not a bug
in Python, but just Terminal.app which displays single bytes
> 127 as question marks if it operates in UTF-8 mode.

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2005-07-03 17:01

Message:
Logged In: YES 
user_id=6656

I have a hard time believing this report at face value.  How are you 
determining that chr(130) is "?"?  Are you sure that it's not just being 
*printed* that way?

Also, I don't see why you think chr(130) should be LATIN SMALL LETTER 
E WITH ACUTE.  That character is 142 in the mac roman encoding and 
233 in the latin-1/iso8859-1 encoding.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1231488&group_id=5470