What Everyone Should Know About Character Encoding

goodness Joel wrote this article -- that means that I can cross it off of my list
of potential future blog entries!  "urn:schemas-microsoft-com:office:office" />Thanks




the script engines are entirely Unicode inside.  Making
sure that the script source code passed in to the engine is valid UTF-16 is the responsibility
of the host, and as Joel mentions, IE certainly jumps through some hoops to try and
deduce the encoding.  WSH also has heuristics
which try to determine whether the file is UTF-8 or UTF-16, but nothing nearly so
complex as IE.


should mention that in JScript you can use the u0000 syntax to put unicode codepoints
into literal strings.  In VBScript it is a little trickier -- you need to use
the CHRW method.


Comments (4)

  1. Olav Junker Kjær says:

    What about characters with code-points above 0xFFFF ?

  2. Eric Lippert says:

    Since JScript is UTF-16 internally, you can use the surrogate pair code units to represent a code point above u-FFFF.

  3. bryan says:

    for info’s sake: does this apply to jscript.net as well?

  4. Eric Lippert says:

    Yes, JScript .NET is also entirely UTF-16 internally, and is fully backwards compatible with JScript Classic (modulo a few edge cases.)

Skip to main content