Re: Unicode escape sequence | Re: draft-ietf-httpbis-header-structure-00, unicode range

On 15 December 2016 at 12:57, Matthew Kerwin <matthew@kerwin.net.au> wrote:
>
>
> On 15 December 2016 at 03:39, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
> wrote:
>>
>> Matthew Kerwin <matthew@kerwin.net.au>: (Wed Dec 14 13:53:45 2016)
>> > It says that "forms that use explicit string delimiters are generally
>> > preferred over other alternatives. In many contexts, symmetric paired
>> > delimiters are easier to recognize and understand than visually
>> > unrelated
>> > ones." So brackets are good.
>> >
>> > And while it advises against using Perl's \x{NNNN...} syntax (because of
>> > potential ambiguities with two-digit hex codes), it doesn't say anything
>> > at
>> > all about \u{N...}
>> >
>
>
> I have should noted here that Ruby uses this \u{N...} syntax, including the
> lower limit of one hexadecimal digit.  This is a valid string literal in
> Ruby:
>
> "\u{df}\u{9}\u{1f602}"

Lua also has this style of unicode codepoint escaping using curly braces.

>From lua reference manual:
> The UTF-8 encoding of a Unicode character can be inserted in a literal string with the escape sequence \u{XXX} (note the mandatory enclosing brackets), where XXX is a sequence of one or more hexadecimal digits representing the character code point.

Received on Wednesday, 21 December 2016 06:27:17 UTC