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 gwideman
Recipients akuchling, benjamin.peterson, docs@python, eric.araujo, ezio.melotti, gwideman, lemburg, pitrou, tshepang, vstinner
Date 2014-03-17.00:26:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395015996.83.0.917778771463.issue20906@psf.upfronthosting.co.za>
In-reply-to
Content
A further issue regarding "one-to-one mappings".

Article: "Encodings don’t have to be simple one-to-one mappings like Latin-1. Consider IBM’s EBCDIC, which was used on IBM mainframes."

I don't think this paragraph is about one-to-one mappings per se. (ie: one character to one code.) It seems to be about whether ranges of characters whose code values are contiguous in one coding system are also contiguous in another coding system. The EBCDIC encoding is still one-to-one, I believe.

The subject of one-chararacter-to-one-code mapping is important (normalization etc), though perhaps beyond the current article. But I think the article should avoid suggesting that many-to-one or one-to-many scenarios are common.
History
Date User Action Args
2014-03-17 00:26:36gwidemansetrecipients: + gwideman, lemburg, akuchling, pitrou, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, docs@python, tshepang
2014-03-17 00:26:36gwidemansetmessageid: <1395015996.83.0.917778771463.issue20906@psf.upfronthosting.co.za>
2014-03-17 00:26:36gwidemanlinkissue20906 messages
2014-03-17 00:26:36gwidemancreate