[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17133: json-encode-string incorrectly encodes extra-BMP characters
From: |
Simen Heggestøyl |
Subject: |
bug#17133: json-encode-string incorrectly encodes extra-BMP characters |
Date: |
Sun, 04 Oct 2015 17:55:22 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Nathan Trapuzzano <nbtrap@nbtrap.com> writes:
> M-: (princ (json-encode "\U0001d11e"))
> ==> "\u1d11e" ;; should be "\ud834\udd1e" or "𝄞"
>
>>From ECMA-404:
>
> To escape a code point that is not in the Basic Multilingual Plane,
> the character is represented as a twelve-character sequence, encoding
> the UTF-16 surrogate pair. So for example, a string containing only
> the G clef character (U+1D11E) may be represented as "\uD834\uDD1E".
This seems to be working as expected in master now; (json-encode
"\U0001d11e") produces "𝄞" as described.
-- Simen
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#17133: json-encode-string incorrectly encodes extra-BMP characters,
Simen Heggestøyl <=