Re: encoding name mappings in codecs.py with email/charset.py

2014-12-15 Thread Stefanos Karasavvidis
I played around with changing the names in the aliases.py and locale.py files (from iso8859 to iso-88559), but this broke mailman. I ended up changing the charset.py file input_charset = codecs.lookup(input_charset).name except LookupError: pass if (inpu

Re: encoding name mappings in codecs.py with email/charset.py

2014-12-14 Thread gst
Le dimanche 14 décembre 2014 14:10:22 UTC-5, Stefanos Karasavvidis a écrit : > thanks for replying gst. > > I've thought already of patching the Charset class, but hoped for a cleaner > solution. > > > This ALIASES dict has already all the iso names *with* a dash. So it must get > striped som

Re: encoding name mappings in codecs.py with email/charset.py

2014-12-14 Thread Stefanos Karasavvidis
thanks for replying gst. I've thought already of patching the Charset class, but hoped for a cleaner solution. This ALIASES dict has already all the iso names *with* a dash. So it must get striped somewhere else. sk On Sun, Dec 14, 2014 at 7:21 PM, gst wrote: > Le vendredi 12 décembre 2014 04

Re: encoding name mappings in codecs.py with email/charset.py

2014-12-14 Thread gst
Le vendredi 12 décembre 2014 04:21:14 UTC-5, Stefanos Karasavvidis a écrit : > I've hit a wall with mailman which seems to be caused by pyhon's character > encoding names. > > I've narrowed the problem down to the email/charset.py file. Basically the > following happens: > Hi, it's all in th

encoding name mappings in codecs.py with email/charset.py

2014-12-12 Thread Stefanos Karasavvidis
I've hit a wall with mailman which seems to be caused by pyhon's character encoding names. I've narrowed the problem down to the email/charset.py file. Basically the following happens: given an encoding name as 'iso-8859-X' it is transformed to 'iso8859-X' (without the first dash). This happens w