RE: Entering Plane 1 characters in XP

From: John McConnell (
Date: Fri Nov 15 2002 - 13:17:49 EST

  • Next message: John Cowan: "Re: mixed-script writing systems"

    There are multiple registry keys that can cause usp10.dll to load. So usp10.dll may be loading even though you've deleted the LanguagePack key (not recommended, btw). Also, an application can load usp10.dll, independently of what the OS does. I suspect that's what you are seeing on Win98.

    There is a performance penalty for loading usp10.dll. Some of the core text display functions become a tad slower because of the additional processing.


    -----Original Message-----
    From: Andrew C. West []
    Sent: Tuesday, November 12, 2002 6:12 AM
    Cc: John McConnell
    Subject: RE: Entering Plane 1 characters in XP

    On Tue, 12 Nov 2002 05:46:36 -0800 (PST), "John McConnell" wrote:

    > - in Windows 2000 and Windows XP, you can set a registry value to cause
    > Uniscribe to load (Uniscribe is required to display supplementary characters).
    > Alternatively, you could install any of the language packs that require
    > Uniscribe. The only difference between Windows 2000 and Windows XP in this
    > regard is that XP installs Uniscribe for East Asian languages, whereas 2000
    > installed it only for complex scripts.

    Thanks for the explanation.

    I've got all the language packs installed, which probably explains why I don't
    need to set the Registry on W2K as specified by Microsoft.

    But for my Windows 98 machine all I did was put USP10.dll in the system
    directory, and Unicode friendly apps are able to display surrogates (using

    Like everyone else I've copied the Registry mantra given by Microsoft in
    "" into my surrogates page
    (, but I can't
    say I understand what app uses the
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\LanguagePack]
    registry key and when. I deleted this key yesterday on my W2K machine, and
    rebooted it, and IE6 is still displaying surrogates OK.

    Leaving aside why one earth Microsoft would want to disable surrogates by
    default in the first place, can anyone explain what exactly they mean by
    "Windows disables surrogate support by default" ? How "disable" ? IE only ?


    This archive was generated by hypermail 2.1.5 : Fri Nov 15 2002 - 14:06:21 EST