Message 183104 - Python tracker

➜

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	marten
Recipients	marten
Date	2013-02-27.01:32:45
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1361928766.42.0.728949411958.issue17305@psf.upfronthosting.co.za>
In-reply-to

Content
Since Python 2.3 the idna encoding is available for Internationalized Domain Names. But the current encoding doesn't work according to the latest version of the spec. There is a new IDNA2008 specification (RFCs 5890-5894). Although I'm not very deep into all the changes, I know that at least the nameprep has changed. For example, the German sharp S ('ß') isn't replaced by 'ss' any longer. The attached file shows the difference between the expected translation and the actual translation.

Since Python 2.3 the idna encoding is available for Internationalized Domain Names. But the current encoding doesn't work according to the latest version of the spec.

There is a new IDNA2008 specification (RFCs 5890-5894). Although I'm not very deep into all the changes, I know that at least the nameprep has changed. For example, the German sharp S ('ß') isn't replaced by 'ss' any longer.

The attached file shows the difference between the expected translation and the actual translation.

History
Date	User	Action	Args
2013-02-27 01:32:46	marten	set	recipients: + marten
2013-02-27 01:32:46	marten	set	messageid: <1361928766.42.0.728949411958.issue17305@psf.upfronthosting.co.za>
2013-02-27 01:32:46	marten	link	issue17305 messages
2013-02-27 01:32:45	marten	create