From: Nathan Trapuzzano <nbtrap@nbtrap.com>
To: 17133@debbugs.gnu.org
Subject: bug#17133: json-encode-string incorrectly encodes extra-BMP characters
Date: Fri, 28 Mar 2014 18:22:25 -0400 [thread overview]
Message-ID: <87wqfegdzy.fsf@nbtrap.com> (raw)
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".
next reply other threads:[~2014-03-28 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 22:22 Nathan Trapuzzano [this message]
2015-10-04 15:55 ` bug#17133: json-encode-string incorrectly encodes extra-BMP characters Simen Heggestøyl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqfegdzy.fsf@nbtrap.com \
--to=nbtrap@nbtrap.com \
--cc=17133@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).