Re: TCHAR string?
- From: "Jonathan Wood" <jwood@xxxxxxxxxxxxxxxx>
- Date: Sat, 7 Jan 2006 18:26:58 -0700
Daniel,
>> The term ASCII was used loosely in my post, but I should've said ANSI.
>
> You wrote:
> | When you use TCHAR, LPCTSTR, etc. and define your string constants
> | using _T("Here's a string"), your strings will be ASCII when you
> | do a multibyte build, and they'll be Unicode when you do a Unicode
> | build.
>
> ANSI is just as wrong as ASCII in that context.
Then what does the "A" stands for at the end of Windows API functions that
accept non-Unicode strings?
> The important thing to grasp is that both MBCS and Unicode builds suffer
> from the fact that a single character may need to be encoded into more
> than one TCHAR (depending on the character set being used), but in MBCS
> a TCHAR is 8 bits while in Unicode it is 16 bits.
I thought the whole point of Unicode was that only one TCHAR was required
for each character?
--
Jonathan Wood
SoftCircuits
http://www.softcircuits.com
.
- Follow-Ups:
- Re: TCHAR string?
- From: Daniel James
- Re: TCHAR string?
- References:
- TCHAR string?
- From: kathy
- Re: TCHAR string?
- From: Ajay Kalra
- Re: TCHAR string?
- From: kathy
- Re: TCHAR string?
- From: Jonathan Wood
- Re: TCHAR string?
- From: Norman Diamond
- Re: TCHAR string?
- From: Jonathan Wood
- Re: TCHAR string?
- From: Daniel James
- TCHAR string?
- Prev by Date: Re: TCHAR string?
- Next by Date: Odd Z-order behavior
- Previous by thread: Re: TCHAR string?
- Next by thread: Re: TCHAR string?
- Index(es):
Relevant Pages
|
Loading