Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'python.': 0.02; 'output': 0.04; 'memory.': 0.05; 'python3': 0.05; 'utf-8': 0.07; 'missed': 0.09; 'subject:How': 0.09; 'python': 0.09; 'coding,': 0.09; 'encoding.': 0.09; 'pep': 0.09; 'subject:()': 0.09; 'subject:string': 0.09; 'subject:using': 0.09; 'cc:addr:python- list': 0.10; 'encodings': 0.16; 'jerry': 0.16; 'subject: \n ': 0.16; 'subject:unicode': 0.16; 'subject:variable': 0.16; '\xe9crit': 0.16; 'wrote:': 0.17; 'sorry,': 0.22; 'cc:2**0': 0.23; 'cc:no real name:2**0': 0.24; 'cc:addr:python.org': 0.25; 'header :In-Reply-To:1': 0.25; 'header:User-Agent:1': 0.26; 'wrote': 0.26; 'coding': 0.27; 'older': 0.27; 'all.': 0.28; 'source': 0.29; 'code': 0.31; 'problem': 0.33; 'point.': 0.33; 'text': 0.34; 'described': 0.35; 'pm,': 0.35; 'display': 0.36; 'keeps': 0.37; 'subject:: ': 0.38; 'comment': 0.38; 'nothing': 0.38; 'received:192': 0.39; 'received:192.168': 0.40; 'your': 0.60; 'easy': 0.60; 'email addr:gmail.com': 0.63; 'charset:windows-1252': 0.65; 'header:Reply-To:1': 0.68; 'received:74.208': 0.71; 'reply-to:no real name:2**0': 0.72; '21st': 0.75; 'century,': 0.84; 'received:74.208.4.194': 0.84; 'subject:value': 0.84; 'hill': 0.96 Date: Fri, 17 Aug 2012 16:55:14 -0400 From: Dave Angel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: wxjmfauth@gmail.com Subject: Re: How do I display unicode value stored in a string variable using ord() References: <253ddd61-4bb5-4f46-b58c-525e55b27558@googlegroups.com> In-Reply-To: <253ddd61-4bb5-4f46-b58c-525e55b27558@googlegroups.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:2g3OHLjeIfqMxXkYrj5DthvjGA10LXui7EUfAVNCgEb coUuNx/08xmjoJXL+yaYHBdF+3DkPoFlTbErl2Ab2mtVFkAt++ dDVoWUzOPm7bOYLIrdoowvESue8RKz65HQsq7bUyg8kZoLBfmU Ll0lsy+VHpgzti8Dzpn4G8Qy8wGgNI5BuPzHlGJeHwZGtPv63N KIMPNfasaq89TswIGMp5EsPudsbrpmlfCOURLnQSP8ivpt7J2K iDD9Nkz2WYNHbwIn2BsDDRyJVQe8hT0cTYcDNrhzrHF3QLqaIm dPvuEWTIT5ZqSEBOnnBW/Pq8RsKpJKY3KIyRS/xwIiMKpUxXw= = Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: d@davea.name List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 34 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1345236951 news.xs4all.nl 6902 [2001:888:2000:d::a6]:39620 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:27265 On 08/17/2012 02:45 PM, wxjmfauth@gmail.com wrote: > Le vendredi 17 août 2012 20:21:34 UTC+2, Jerry Hill a écrit : >> >> >> I don't understand what any of this has to do with Python. Just >> >> output your text in UTF-8 like any civilized person in the 21st >> >> century, and none of that is a problem at all. Python make that easy. >> >> It also makes it easy to interoperate with older encodings if you >> >> have to. >> > Sorry, you missed the point. > > My comment had nothing to do with the code source coding, > the coding of a Python "string" in the code source or with > the display of a Python3 . > I wrote about the *internal* Python "coding", the > way Python keeps "strings" in memory. See PEP 393. > > jmf The internal coding described in PEP 393 has nothing to do with latin-1 encoding. So what IS your point? Make it clearly, without all the snide side-comments. -- DaveA