From: "Marco Cimarosti" <marco.cimarosti@essetre.it>
> Yeah. Pity that the local code page is the default everywhere, and to use
> Unicode in the GUI one has to dig deep in options, registry, manuals, etc.
Well, I would not go *that* far.... in theory just defining _UNICODE is all
you need. How far an app is from that theory varies, but its a measureable
(and costable!) issue.
>
> And that's not enough, anyway. I still have to discover how to display
> Unicode in Visual Basic, for instance. Someone should write a book about
> this. ;-)
There's an idea. :-)
> If "high" and "low" have the usual meanings of "nearer to the user" and
> "nearer to the hardware", respectively, then I think that what I said is
> true for NT and many other environments.
Well, like I said, the apps that stay Unicode throughout are ones that I
would consider to be ideal. And then if you take wrapper implementations
like the one in Avery Bishop's white paper then you have a quite classic
reversal on Win9x: the low level non-Unicode and the high-level Unicode
interface.
> And truth is never wrong.
But it also never stays the same.
MichKa
Michael Kaplan
Trigeminal Software, Inc.
http://www.trigeminal.com/
This archive was generated by hypermail 2.1.2 : Fri Jul 06 2001 - 00:17:15 EDT