Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!nntp-feed.chiark.greenend.org.uk!ewrotcd!news.nosignal.org!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.066 X-Spam-Evidence: '*H*': 0.87; '*S*': 0.01; 'x-mailer:evolution 2.28.3': 0.07; 'codec': 0.16; 'subject:non': 0.16; 'cc:addr :python-list': 0.16; 'wrote:': 0.18; 'cc:no real name:2**0': 0.20; '(or': 0.22; 'header:In-Reply-To:1': 0.22; 'cc:2**0': 0.24; 'module.': 0.29; 'cc:addr:python.org': 0.29; 'subject:support': 0.30; 'subject:?': 0.31; 'there': 0.33; 'fri,': 0.34; 'subject:How': 0.35; 'problem.': 0.36; 'header:Reply-To:1': 0.71; 'reply-to:no real name:2**0': 0.72; 'received:bethere.co.uk': 0.84; 'similar)': 0.84 Subject: Re: How to support a non-standard encoding? From: Tim Wintle To: jmfauth In-Reply-To: <1480875f-d133-40a1-8fd1-dd31a2dd430b@d10g2000vbh.googlegroups.com> References: <1480875f-d133-40a1-8fd1-dd31a2dd430b@d10g2000vbh.googlegroups.com> Content-Type: text/plain; charset="UTF-8" Organization: Team Rubber Date: Fri, 06 Jan 2012 20:42:33 +0000 Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 87.194.110.230 X-SA-Exim-Mail-From: tim.wintle@teamrubber.com X-SA-Exim-Scanned: No (on mail.netsight.co.uk); SAEximRunCond expanded to false Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: tim.wintle@teamrubber.com 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: 8 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1325882556 news.xs4all.nl 6983 [2001:888:2000:d::a6]:41507 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:18619 On Fri, 2012-01-06 at 12:00 -0800, jmfauth wrote: > The distibution of such a codec may be a problem. There is a register_codec method (or similar) in the codecs module. Tim