Re: Using ToUnicode() under Win9X
- From: "Mihai N." <nmihai_year_2000@xxxxxxxxx>
- Date: Fri, 24 Feb 2006 02:07:54 -0800
95/98/me have limited UNICODE support and system API, especially 95.Correct. See my post in microsoft.public.platformsdk.mslayerforunicode
IfNot really possible. There are limitations in 95/98/Me that you cannot
you want to have the same support for 95/98/me as NT/W2K/XP have, you
should make your own complement to these platforms or find somewhere
third party API.
bypass, not matter what. You might be able to "trick" some things, just
to bump into others.
If you have a choice, just drop support for 95/98/Me. They are dead and
burried. And if not, then don't ask unreasonable things from them.
They are too old for that :-)
WORD ConvertWin1251ToUnicode(BYTE byCode)You don't have to. There is WideCharToMultiByte and MultiByteToWideChar.
--
Mihai Nita [Microsoft MVP, Windows - SDK]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email
.
- Follow-Ups:
- Re: Using ToUnicode() under Win9X
- From: John Carson
- Re: Using ToUnicode() under Win9X
- References:
- Re: Using ToUnicode() under Win9X
- From: John Carson
- Re: Using ToUnicode() under Win9X
- From: Joakim Andersson
- Re: Using ToUnicode() under Win9X
- From: John Carson
- Re: Using ToUnicode() under Win9X
- From: Mihai N.
- Re: Using ToUnicode() under Win9X
- From: Smike
- Re: Using ToUnicode() under Win9X
- Prev by Date: Re: Drawing on top of everything
- Next by Date: Re: Custom background in a Window Menu Area
- Previous by thread: Re: Using ToUnicode() under Win9X
- Next by thread: Re: Using ToUnicode() under Win9X
- Index(es):
Relevant Pages
|