Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed3.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.016 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'received:134': 0.05; 'problem?': 0.07; 'subject:file': 0.07; 'string': 0.09; '"a"': 0.16; 'chunks': 0.16; 'splits': 0.16; 'subject:String': 0.16; 'coding': 0.22; 'header:User-Agent:1': 0.23; 'handling': 0.26; 'header:In-Reply-To:1': 0.27; 'coded': 0.31; 'subject:the': 0.34; 'problem.': 0.35; 'two': 0.37; 'problems': 0.38; 'to:addr:python- list': 0.38; 'to:addr:python.org': 0.39; 'solve': 0.60; 'email addr:gmail.com': 0.63; 'face': 0.64; 'pardon': 0.84 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAOW2KVKGuA9G/2dsb2JhbABbxV6BOIMYAQEEAXgRCyEWDwkDAgECAQ82EwYCAodsAwkGtTcNV4hGjQSCdRaEBwOWDIFphhiGH4UvgyI Date: Fri, 06 Sep 2013 13:10:37 +0200 From: Antoon Pardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Chardet, file, ... and the Flexible String Representation References: <4ce85ea8-4a4c-46cf-a546-ad999576a5f7@googlegroups.com> In-Reply-To: <4ce85ea8-4a4c-46cf-a546-ad999576a5f7@googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 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: 13 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1378465845 news.xs4all.nl 16002 [2001:888:2000:d::a6]:45399 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:53779 Op 06-09-13 11:11, wxjmfauth@gmail.com schreef: > > The Flexible String Representation has conceptually to > face the same problem. It splits "unicode" in chunks and > it has to solve two problems at the same time, the coding > and the handling of multiple "char sets". The problem? Not true. The FSR always uses the same coding. An "A" is always coded as 65. -- Antoon Pardon