Re: Code Page problem in SetWindowText
- From: "Tom Serface" <tom.nospam@xxxxxxxxxxxxx>
- Date: Wed, 5 Sep 2007 08:28:02 -0700
Hi Mihai,
For the most part I agree with what you say here, the only exception being... if you are using a lot of strings and doing a lot of string handling and don't need anything except English then using MBCS may be a bit faster to execute, better in memory storage, and quicker to read and write files since Unicode doubles all character sizes whether needed or not. I wish Windows/MFC/all those good things had better handling for other methods like UTF-8 that would give similar results as MBCS.
That say, the differences in most cases are not all that significant and I've gone to using Unicode all the time.
Tom
"Mihai N." <nmihai_year_2000@xxxxxxxxx> wrote in message news:Xns99A27125F83BMihaiN@xxxxxxxxxxxxxxxx
I've created a MFC project in MBCS. I need to show some set special
characters ( ASCII code > 128) in a CStatic controls.
If you start now with a new project, there is no reason no to go Unicode.
The only reason for MBCS is to support Win 9x (with a new project?),
to learn about things that will be obsolete in 2-3 years,
or for being a masochist :-)
--
Mihai Nita [Microsoft MVP, Windows - SDK]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email
.
- Follow-Ups:
- Re: Code Page problem in SetWindowText
- From: David Ching
- Re: Code Page problem in SetWindowText
- References:
- Code Page problem in SetWindowText
- From: Marco Hung
- Re: Code Page problem in SetWindowText
- From: Mihai N.
- Code Page problem in SetWindowText
- Prev by Date: Re: Adding Qoutation mark " to CString
- Next by Date: Re: Write to an Edit Control with the << operator
- Previous by thread: Re: Code Page problem in SetWindowText
- Next by thread: Re: Code Page problem in SetWindowText
- Index(es):
Relevant Pages
|
Loading