From: Michael \(michka\) Kaplan (michka@trigeminal.com)
Date: Wed May 07 2003 - 14:34:06 EDT
From: "Ostermueller, Erik" <Erik.Ostermueller@fnf.com>
> I could use some help understanding this behavior.
This is neither a font issue, nor strictly speakin a Unicode issue. Its a
limitation in VB <= 6.0.
VB intrinsic controls are not Unicode internally (though there property
interface is Unicode). Any string entered into them whether programatically,
via the clipboard, or vis user input, will be converted to the system
default code page (whatever that is).
Once this is done, whatever is left will be rendered by the control.
If you need to work with characters that a user might *ever* type that are
off the default system code page (CP_ACP) then it is best to move to Unicode
controls, since there is no realistic way to try to force users to type with
specific characters/ideographs in their own language (at least not without
upsetting them).
Arguably the most famous example of this on Windows is the so-called
"non-Big5" characters that exist in Unicode and in collation but are not a
part of code page 950.
MichKa [MS]
This archive was generated by hypermail 2.1.5 : Wed May 07 2003 - 15:24:12 EDT