Comments on draft-klensin-net-utf8-06
Marcos Sanz/Denic <sanz@denic.de> Tue, 16 October 2007 14:46 UTC
Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhngN-0000dF-Bk; Tue, 16 Oct 2007 10:46:07 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IhngL-0000aU-2Q for discuss-confirm+ok@megatron.ietf.org; Tue, 16 Oct 2007 10:46:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhngK-0000aD-4W for discuss@apps.ietf.org; Tue, 16 Oct 2007 10:46:04 -0400
Received: from smtp.denic.de ([81.91.161.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IhngC-000700-QO for discuss@apps.ietf.org; Tue, 16 Oct 2007 10:46:04 -0400
Received: from notes.rz.denic.de ([192.168.0.77]) by smtp.denic.de with esmtp id 1Ihng2-0006lH-EC; Tue, 16 Oct 2007 16:45:46 +0200
To: discuss@apps.ietf.org
Subject: Comments on draft-klensin-net-utf8-06
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
From: Marcos Sanz/Denic <sanz@denic.de>
Message-ID: <OF037DA1CA.695DAFC1-ONC1257376.004E5008-C1257376.00511560@notes.denic.de>
Date: Tue, 16 Oct 2007 16:45:38 +0200
X-MIMETrack: Serialize by Router on notes/Denic at 16.10.2007 16:45:46, Serialize complete at 16.10.2007 16:45:46
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org
To my eyes the document is in good shape, but it still leaves one of the issues at stake partially open: Section 2, bullet 2 says "CR SHOULD NOT appear except when followed by LF". The last paragraph of the section 2 says "CR MUST NOT appear unless it is immediately followed by LF (...) or NUL". To me the first of these statements is much less restrictive than the second. Nitpicking: * Section 1.1: s/variable length/variable-length/ for coherence with other text appearances * Section 3: s/to convert all canonically equivalent sequences a single unique form/to convert all canonically equivalent sequences into a single unique form/ * Section 4: The definition of the normalization stability is misleading, actually even wrong. Old text: That is, if a string does not contain any unassigned characters, and it is normalized according to NFC, it will always be normalized according to all future versions of the Unicode Standard. Suggested text: That is, if a string does not contain any unassigned characters for a given version of Unicode, and it is normalized according to the definition of NFC in that version, it will always result in the same normalized string according to all future versions of the Unicode Standard. * Section 4: "the string order of RFC 3629". It's not very clear to me what is meant with this. Byte order? Sorting order? * Section 4: I would drop the last paragraph, since it is a repetition of what is exhaustively explained in section 5.2. I got a parsing error at the last sentence of that paragraph anyway. * Section 5.2: s/[RFC3454])/[RFC3454]),/ * Section 5.2, bullet 4: "This process has been discussed in the Unicode Consortium under the name 'Stable NFC'". That might very well be but the only hits I get when googling for that string are this very draft and some contributions of the draft author to some mailing lists. So I cast doubt on the utility of introducing this new term here which is a pointer to nowhere. Is this again referring to the normalization stability policy of unicode? http://unicode.org/standard/stability_policy.html Best regards, Marcos Sanz
- Comments on draft-klensin-net-utf8-06 Marcos Sanz/Denic
- Re: Comments on draft-klensin-net-utf8-06 John C Klensin
- Re: Comments on draft-klensin-net-utf8-06 Frank Ellermann
- Re: Comments on draft-klensin-net-utf8-06 Marcos Sanz/Denic
- Re: Comments on draft-klensin-net-utf8-06 Clive D.W. Feather
- Re: Comments on draft-klensin-net-utf8-06 John C Klensin