×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Thu, May 17, 2018 at 11:33 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:
Maybe the data should be encoded and html entities used instead?
The official JSON spec says Unicode characters may be specified using
a hexadecimal escape sequence. For BMP code points, this is (in its
most general form) a six-character sequence consisting of a backslash,
the lowercase letter 'u', and then the four hex digits representing
the numeric code point. For code points outside the BMP, use a
12-character sequence corresponding to the UTF-16 surrogate pair.
John Y.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
