draft-klensin-unicode-escapes-03.txt (was: Re: draft-klensin-unicode-escapes-02.txt)

[John C Klensin <[e-mail]>]

--On Monday, 19 February, 2007 22:34 +0100 Frank Ellermann
<[e-mail]> wrote:

> John C Klensin wrote:
> 
>> Anyone who prefers the latter should please send the ABNF
>> they would like to see.
> 
> Here's what I'd do with the existing ABNF:
> 
>    EmbeddedUnicodeChar =  BMP-form / Full-form
>    BMP-form  =  %x5C.75 4HEXDIG   ; starting with lower case
> "\u"    Full-form =  %x5C.55 8HEXDIG   ; starting with upper
> case "\U"
> 
> IOW no more <Hex-quad> because you didn't use it elsewhere, and
> replacing <HexDigit> by <HEXDIG>, because the latter is already
> defined in RFC 4234.
>...

Done, including removal of <HexDigit>

> Please add the [CharMod] reference (informative) with a note
> about its C042..C048 conformance criteria in ch. 4.6
> (character escaping).

A reference to [CharMod] has been included, but as part of a
comment (per discussion with Charles on 9 February) about what
this document does not try to address.

I think most (and hope all) of the other comments since -02 was
posted have been picked up, with one major exception.  I believe
that complexity is the enemy of this type of work.  So, while it
is clearly possible to figure out how to write, e.g.,
   \u(NNNN, NNNNN, NNNN)
rather than
   \u(NNNN)\u(NNNNN)\u(NNNN)
or to incorporate named characters into escaped strings, I don't
think doing that is wise.   YMMD, of course, and, if you, I'm
sure I will hear about it.

-03 is now in the posting queue.  I just realized that I didn't
update Section 8 (the change log) for either this version or
-02.  The major changes are the elimination of a specific
recommendation in -02 and cleaning up of a lot of text and
fixing the ABNF in -03.

      john