➜

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 benjamin.peterson
Recipients Drekin, benjamin.peterson, ezio.melotti, vstinner
Date 2014-10-22.14:03:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413986630.4029653.182006545.5AAEB617@webmail.messagingengine.com>
In-reply-to <1413978178.37.0.161674055556.issue22667@psf.upfronthosting.co.za>
Content 
The unicode standard explains some of the tradeoffs.
http://www.unicode.org/reports/tr31/tr31-21.html#normalization_and_case

On Wed, Oct 22, 2014, at 07:42, Drekin wrote:
> 
> Drekin added the comment:
> 
> I understand. I have found
> https://mail.python.org/pipermail/python-3000/2007-May/007995.html as a
> reason for using NFKC rather than NFC. On the other hand I think one may
> want these double-struct mathematical letters to be different from the
> ordinary ones if used as variable names. So I wonder if there are some
> other reasons for choosing NFKC over NFC.
> 
> ----------
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue22667>
> _______________________________________
History
Date User Action Args
2014-10-22 14:03:53benjamin.petersonsetrecipients: + benjamin.peterson, vstinner, ezio.melotti, Drekin
2014-10-22 14:03:53benjamin.petersonlinkissue22667 messages
2014-10-22 14:03:52benjamin.petersoncreate