Re: New UTF-8 draft (RFC 2044 revision)

Chris Newman (Chris.Newman@innosoft.com)
Thu, 17 Apr 1997 10:27:58 -0700 (PDT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: David Goldsmith: "Registration of new character set"
Previous message: Francois Yergeau: "New UTF-8 draft (RFC 2044 revision)"
In reply to: Francois Yergeau: "New UTF-8 draft (RFC 2044 revision)"

Date: Thu, 17 Apr 1997 10:27:58 -0700 (PDT)
From: Chris Newman <Chris.Newman@innosoft.com>
Subject: Re: New UTF-8 draft (RFC 2044 revision)
In-reply-to: <3.0.1.32.19970415225309.00c4d768@genstar.alis.com>
To: Francois Yergeau <yergeau@alis.com>
Cc: IETF Charsets Mailing List <ietf-charsets@INNOSOFT.COM>
Message-id: <Pine.SOL.3.95.970417102143.6755J-100000@eleanor.innosoft.com>

On Tue, 15 Apr 1997, Francois Yergeau wrote:
>  http://www.alis.com:8085/~yergeau/draft-yergeau-utf8-rev-00.txt

>   version only, should be registered (a suggestion would be "UNI-
>   CODE-1-1-UTF-8"), in order to retain the advantages of a version-

You shouldn't allow an identifier to be split between lines like this --
it makes it very hard to read.  In general, I think hyphenation is a bad
idea in internet-drafts and RFCs.

The Bibliography reference to ISO 10646:1993 probably also needs to
mention the other amendments.

Thanks for doing this update!

--Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: David Goldsmith: "Registration of new character set"
Previous message: Francois Yergeau: "New UTF-8 draft (RFC 2044 revision)"
In reply to: Francois Yergeau: "New UTF-8 draft (RFC 2044 revision)"