Path: csiph.com!usenet.pasdenom.info!news.albasani.net!newsfeed.freenet.ag!news2.euro.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!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; 'ascii': 0.07; 'bytes.': 0.07; 'character,': 0.07; 'subject:How': 0.09; '128': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:()': 0.09; 'subject:string': 0.09; 'subject:using': 0.09; 'aug': 0.13; 'sat,': 0.15; '10:59': 0.16; 'mathematics.': 0.16; 'reason.': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'subject: \n ': 0.16; 'subject:unicode': 0.16; 'subject:variable': 0.16; 'url:thread': 0.16; 'wrote:': 0.17; 'byte': 0.17; 'string,': 0.17; 'unicode': 0.17; '>>>': 0.18; 'non': 0.24; 'header:In-Reply-To:1': 0.25; 'header:User-Agent:1': 0.26; "doesn't": 0.28; 'header:X-Complaints-To:1': 0.28; 'represent': 0.28; '-0700,': 0.29; "d'aprano": 0.29; 'steven': 0.29; 'character': 0.29; 'basic': 0.30; 'from:addr:yahoo.co.uk': 0.32; 'to:addr:python-list': 0.33; "can't": 0.34; 'compared': 0.35; 'open': 0.35; 'pm,': 0.35; 'there': 0.35; 'received:org': 0.36; 'but': 0.36; 'characters': 0.36; 'expensive': 0.36; 'should': 0.36; 'supporting': 0.37; 'does': 0.37; 'url:in': 0.37; 'two': 0.37; 'why': 0.37; 'subject:: ': 0.38; 'mark': 0.38; 'fact': 0.38; 'some': 0.38; 'to:addr:python.org': 0.39; 'url:microsoft': 0.39; 'header:Received:5': 0.40; 'different': 0.63; 'more': 0.63; 'url:blogspot': 0.64; 'of:': 0.65; 'subject:value': 0.84; 'rusi': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Mark Lawrence Subject: Re: How do I display unicode value stored in a string variable using ord() Date: Sat, 18 Aug 2012 20:50:58 +0100 References: <308df2af-abe7-4043-b199-0a39f440e0ab@googlegroups.com> <502f8a2a$0$29978$c3e8da3$5496439d@news.astraweb.com> <502fd7f6$0$29978$c3e8da3$5496439d@news.astraweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: host-78-146-1-115.as13285.net User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20120713 Thunderbird/14.0 In-Reply-To: X-Antivirus: avast! (VPS 120818-0, 18/08/2012), Outbound message X-Antivirus-Status: Clean X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list 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: 31 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1345319708 news.xs4all.nl 6977 [2001:888:2000:d::a6]:54658 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:27328 On 18/08/2012 19:40, rusi wrote: > On Aug 18, 10:59 pm, Steven D'Aprano +comp.lang.pyt...@pearwood.info> wrote: >> On Sat, 18 Aug 2012 08:07:05 -0700, wxjmfauth wrote: >>> Is there any reason why non ascii users are somehow penalized compared >>> to ascii users? >> >> Of course there is a reason. >> >> If you want to represent 1114111 different characters in a string, as >> Unicode supports, you can't use a single byte per character, or even two >> bytes. That is a fact of basic mathematics. Supporting 1114111 characters >> must be more expensive than supporting 128 of them. >> >> But why should you carry the cost of 4-bytes per character just because >> someday you *might* need a non-BMP character? > > I am reminded of: http://answers.microsoft.com/thread/720108ee-0a9c-4090-b62d-bbd5cb1a7605 > > Original above does not open for me but here's a copy that does: > > http://onceuponatimeinindia.blogspot.in/2009/07/hard-drive-weight-increasing.html > ROFLMAO doesn't adequately some up how much I laughed. -- Cheers. Mark Lawrence.