Subject: bug#17133: closed (Re: bug#17133: json-encode-string incorrectly encodes extra-BMP characters)

From: [email-masked] (GNU bug Tracking System)
Date: Sun, 04 Oct 2015 15:56:02 +0000

Your bug report

#17133: json-encode-string incorrectly encodes extra-BMP characters

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
17133: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17133
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#17133: json-encode-string incorrectly encodes extra-BMP characters
From: Simen Heggestøyl <[email-masked]>
To: Nathan Trapuzzano <[email-masked]>
Cc: [email-masked], [email-masked]
Date: Sun, 04 Oct 2015 17:55:22 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Nathan Trapuzzano <[email-masked]> 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

Subject: json-encode-string incorrectly encodes extra-BMP characters
From: Nathan Trapuzzano <[email-masked]>
To: [email-masked]
Date: Fri, 28 Mar 2014 18:22:25 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

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".