From: Michael \(michka\) Kaplan (michka@trigeminal.com)
Date: Wed May 07 2003 - 15:37:17 EDT
This is not actually true, and it can cause problems for a lot of functions
due to the nature of "best fit" code page mappings within Windows corrupting
data.
The problem is insidious (after all, the mappings are called "best fit" due
to the fact that they share something in common with the original code
point) but corruption is inevitable if you don't pay attention to what the
app will do to the text....
What happens with DBCS is just a symptom.
MichKa [MS]
This posting is provided "AS IS" with
no warranties, and confers no rights.
----- Original Message -----
From: "Stefan Persson" <alsjebegrijptwatikbedoel@yahoo.se>
To: "Michael (michka) Kaplan" <michka@trigeminal.com>
Cc: <unicode@unicode.org>
Sent: Wednesday, May 07, 2003 12:30 PM
Subject: Re: variants and code-page --> unicode conversion
> Michael (michka) Kaplan wrote:
>
> >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).
> >
> >
> VB 4.0 allows you to set the default code page for each control. Any
> one-byte code page works on any Windows-1252-based system, but
> double-byte code pages do not work.
>
> Stefan
>
>
This archive was generated by hypermail 2.1.5 : Wed May 07 2003 - 16:28:43 EDT