➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients belopolsky, eric.araujo, ezio.melotti, jcea, lemburg, pitrou, rhettinger, sdaoden, vstinner
Date 2011-02-26.01:50:01
SpamBayes Score 8.2047217e-07
Marked as misclassified No
Message-id <AANLkTimJVvos=w=Qr4WHyOojnzjBYunxqVLGuKZ1UuyS@mail.gmail.com>
In-reply-to <1298684345.88.0.568485988805.issue11303@psf.upfronthosting.co.za>
Content 
On Fri, Feb 25, 2011 at 8:39 PM, Ezio Melotti <report@bugs.python.org> wrote:
..
> It would prefer to see the note added by Alexander in the doc mention *only* the preferred spellings
> (i.e. 'utf-8' and 'iso-8859-1') rather than all the variants that are actually optimized. One of the reasons
> that lead me to open #5902 is that I didn't like the inconsistencies in the encoding names (utf-8 vs utf8 vs
> UTF8 etc). Suggesting only one spelling per encoding will fix the problem.

I am fine with trimming the list.  In fact I deliberately did not
mention say UTF-8 variant even though it is also optimized.
Unfortunately, I don't think we have a choice between 'latin-1',
'latin1', and 'iso-8859-1'.  I don't think we should recommend
'latin-1' because this may cause people adding '-' to a very popular
and IANA registered 'latin1' variant and while 'iso-8859-1' is the
most pedantically correct spelling, it is very user unfriendly.
History
Date User Action Args
2011-02-26 01:50:02belopolskysetrecipients: + belopolsky, lemburg, rhettinger, jcea, pitrou, vstinner, ezio.melotti, eric.araujo, sdaoden
2011-02-26 01:50:01belopolskylinkissue11303 messages
2011-02-26 01:50:01belopolskycreate