From: Claus Färber (list-ietf-wg-apps-usefor@faerber.muc.de)
Date: Sun Aug 25 2002 - 15:45:00 CDT
Erland Sommarskog <sommar-usefor@algonet.se> schrieb/wrote:
> There are three distinct differences between UTF-8 and Punycode:
> 1. Punycode adds line noise in the beginning and the end of string.
> 2. With Punycode you cannot tell where the excluded letters should
> be inserted, and neither how many there are.
> 3. With UTF-8 each scrambled character is scrambled to a unique character
> sequence.
> One can note that even RFC2047 fulfils the latter two points.
> The Punycode encoding is completely unacceptable.
If you just set up certain requirements -- and disregard others --
without any reasoning you can come to any result you want to.
Please explain why the requirements above are more important than these:
. Leagacy news transport systems must be able to handle the newsgroups.
. Leagacy software accompanying news transport systems (e.g. scripts
that create newsgroups autmatically, etc.) must be able to handle
the newsgroups.
. Posting to moderated groups must work even if the NNTP server has not
been updated and uses a per-hierarchy configuration for moderation
addresses.
. Leagacy news user agents must be able to read the newsgroups.
. Leagacy news user agents must be able to post to the newsgroup.
. Leagacy news user agents must not create broken Newsgroup headers
(even if their programmers were just plain stupid).
. The same files must be editable with both UTF-8 and leagacy editors
and it must be guaranteed that the Unicode normalization form will not
be changed and that no 8bit character will be lost.
. Cut-and-pasting newsgroup names must work with the same guarantee.
Claus
-- ------------------------ http://www.faerber.muc.de/ ------------------------ OpenPGP: DSS 1024/639680F0 E7A8 AADB 6C8A 2450 67EA AF68 48A5 0E63 6396 80F0