×
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.
RFC 7159
JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32.
This is an interesting sideline discussion, Henrik. The RFC appears to
pertain to JSON documents, which would obviously contain text for thousands
of written and spoken languages. I admit a connection with using JSON to
define JavaScript "objects", which might be "run" in node.js.
With IBM documentation stating that connections between IBM i and PASE
require ASCII to EBCDIC conversions, have you concluded that node.js
requires an additional conversion from ASCII to UTF-x and visa versa?
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
