➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: chr() returns ? when input > 127 in OS X
Type: Stage:
Components: None Versions:
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: craighoward, loewis, mwh
Priority: normal Keywords:

Created on 2005-07-02 13:52 by craighoward, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg25705 - (view) Author: Craig Howard (craighoward) Date: 2005-07-02 13:52 
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.
msg25706 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2005-07-03 15:01 
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.
msg25707 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2005-07-06 05:17 
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.
History
Date User Action Args
2022-04-11 14:56:12adminsetgithub: 42155
2005-07-02 13:52:28craighowardcreate