logo       

Re: Typographical error in draft-klensin-unicode-escapes-00: msg#00015

ietf.apps-discuss

Subject: Re: Typographical error in draft-klensin-unicode-escapes-00

John C Klensin said:
>> While these are not incorrect, they are confusing to many
>> readers. ABNF allows you to write these as:
>>
>> 4HexDigit and
>> 2Hex-Quad
>>
>> respectively, and I recommend you do so.
>
> Clive, I actually find it less confusing to be explicit about
> the lower and upper bounds.

We may have to agree to disagree. When I see "4*4XXX", it makes me wonder
if the author actually meant "4*" or "*4" and misunderstood the notation.

Incidentally, there's no significance to the groupings of 4 in the \u
notation, so I see little point in introducing "Hex-quad". The term "BMP"
is, as I understand it, deprecated these days. So I would just write:

EmbeddedUnicodeChar = %x5C.75 4HexDigit / %x5C.55 8HexDigit

or if you really want:

EmbeddedUnicodeChar = UnicodeShortForm / UnicodeLongForm
UnicodeShortForm = %x5C.75 4HexDigit
UnicodeLongForm = %x5C.55 8HexDigit

[Note that you omitted the / from your definition.]

--
Clive D.W. Feather | Work: <clive@xxxxxxxxx> | Tel: +44 20 8495 6138
Internet Expert | Home: <clive@xxxxxxxxxx> | Fax: +44 870 051 9937
Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646
THUS plc | |




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise