[debbugs-tracker] bug#17133: closed (json-encode-string incorrectly encodes extra-BMP characters)

[GNU bug Tracking System]

Your message dated Sun, 04 Oct 2015 17:55:22 +0200
with message-id <address@hidden>
and subject line Re: bug#17133: json-encode-string incorrectly encodes 
extra-BMP characters
has caused the debbugs.gnu.org bug report #17133,
regarding json-encode-string incorrectly encodes extra-BMP characters
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
17133: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17133
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> json-encode-string incorrectly encodes extra-BMP characters
>
>
>
>
> Date: 
>
> Fri, 28 Mar 2014 18:22:25 -0400
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux)
>
>
>
>
> 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".
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: 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 <address@hidden> 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
>
>
> --- End Message ---