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



Nathan

just to get the documentation right:

RFC 7159


8.1 <https://tools.ietf.org/html/rfc7159#section-8.1>. Character Encoding

JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32. The default
encoding is UTF-8, and JSON texts that are encoded in UTF-8 are
interoperable in the sense that they will be read successfully by the
maximum number of implementations; there are many implementations
that cannot successfully read texts in other encodings (such as
UTF-16 and UTF-32).

Implementations MUST NOT add a byte order mark to the beginning of a
JSON text. In the interests of interoperability, implementations
that parse JSON texts MAY ignore the presence of a byte order mark
rather than treating it as an error.



On Fri, Oct 9, 2015 at 9:24 PM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

Nathan

Node.js is based on a port of google V8 javascript engine, do you really
think they have changed the internal CCSID in that.

JSON is JacaScript Object Notation - used in any object or array in
javascript.

JSON has only one internal code page = Unicode/UTF-8 and there is
nothing to discus in that matter.

AJAX may convert result from a various ASCII code pages from none-JSON
conversations but not if it is JSON it receives.



On Fri, Oct 9, 2015 at 9:12 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:


come on, everybody knows that javascript requires \uxxxx characters
to work properly if the text string is outside 7 bit ascII x'00'-x'7F'
that
btw are shared with UTF-8.


Okay, I should admit that I didn't know that. Every reference I've read
suggests the use of "character representations" of various supported
character sets in "browsers".


Node.js runs javascript that runs UTF-8 Unicode internally in every
object you make.


Again, what make you so sure? Are you assuming that server-side JavaScript
runs in an environment comparable to browser-based JavaScript?
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.




--
Regards,
Henrik Rützou

http://powerEXT.com <http://powerext.com/>






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.