Re: draft-klensin-unicode-escapes-03.txt

[Frank Ellermann <[e-mail]>]

John C Klensin wrote:

>> 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"
[...]
> Done, including removal of <HexDigit>

You kept the multiline comment after <BMP-form>, and Bill's parser
doesn't like this:

BMP-form =  %x5C.75 4HEXDIG ; starting with lower case "\u"
   ; In both this case and the one above, note that the encodings are
   considered to be abstractions for the relevant characters, not
   designations of specific octets.

With more semicolons it's okay:

BMP-form =  %x5C.75 4HEXDIG ; starting with lower case "\u"
   ; In both this case and the one above, note that the encodings are
   ; considered to be abstractions for the relevant characters, not
   ; designations of specific octets.

But actually I think this ABNF comment is unnecessary - or if not it
could be moved into the prose.  Then the contrast \u vs. \U would be
also more directly visible:

BMP-form  =  %x5C.75 4HEXDIG   ; starting with lower case "\u"
Full-form =  %x5C.55 8HEXDIG   ; starting with upper case "\U"

Lillyguilding => ready, maybe add "intended status: BCP" and set the
"PubReq" flag while authors are still allowed to manage this flag. ;-)

Frank