V8 bug tracking thread following some of the same unicode/js issues I've been investigating.

Gist driven side-debate (also on Twitter) with Isaac of Node and Brendan of Javascript, about unicode escaping/encoding issues and the prospect of full VM-level support (fixing String.length, substring etc)

Brendan Eich's followup to last week's debate with the node.js community about full unicode support in Javascript.

The most commonly recommended (and decent) intro to unicode for programmers.

JSON text uses UTF-16 escapes.

JSON default encoding is UTF8.

Cal's big table of emoji code-points and equivalencies for various different implementations, where available.

More generally: how to escape UTF-16 characters (including surrogate pairs) in JSON.stringified javascript data.

Good explanation of surrogate pair encoding/escaping in UTF-16.

"Here's the list: cc, ms, ns, ps, in, ls, fi, fl, ffl, ffi, iv, ix, vi, oy, ii, xi, nj, ". " (period space), and ", " (comma space). ... All of these letter groups will be replaced with a single character, using unicode. This is possible because unicode has single character replacements for things like roman numerals (iv, ix), scientific abbreviations (ms, ns), and more."

Nice article from Cal Henderson that moves us on a bit further past "The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)". Which is good, because there are some folks out there who still think that ASCII will do.