Re: Why use the unicode version of the api?
- From: "Tony Proctor" <tony_proctor@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 20 Nov 2005 11:33:25 -0000
Sorry, it sounds like we're talking at cross purposes Thorsten. My point was
that there is an ANSI code page for each MBCS (incl. SBCS/DBCS), and that's
set as part of your locale configuration. Hence, not all ANSI character sets
have 1 byte-per-character -- it depends where you are. In general, the ANSI
code pages just deal with the local characters, plus 7-bit ASCII, but as you
say, they don't cope with all multi-national characters, whereas Unicode
does. I think that is the point you were making yourself.
Tony Proctor
"Thorsten Albers" <albersRE@xxxxxxxxxxxxxxxxxxx> wrote in message
news:01c5ed0e$d5cc7ac0$7d8ee684@xxxxxxxxxxx
> Tony Proctor <tony_proctor@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> schrieb im
> Beitrag <#PlYoyP7FHA.3752@xxxxxxxxxxxxxxxxxxxx>...
> > That's not quite true Thorsten. "ANSI" code pages include all potential
> > locale-specific MBCS, and this includes DBCS such as Shift-JIS, Big-5,
> etc.,
> > but not confined to those alone. This is mirrored in the APIs
> > MultiByteToWideChar()/WideCharToMultiByte() which may be considered to
> > perform A-to-W/W-to-A.
>
> MultiByteToWideChar() and WideCharToMultiByte() are, no doubt, able to
> handle all possible DCBS if the respective code page is installed, because
> as character conversion routines they are working with the code page
> information.
> But I am interpreting Gustavo's question on a more general term: Are all
> "A" versions able to handle DCBS? The answer is: no they aren't (excepting
> functions which are working with code page information explicitely like
> MultiByteToWideChar()). On a japanese and a chinese system the "A"
versions
> are guaranteed to support japanese/chinese DCBS - and nothing more.
>
> --
> ----------------------------------------------------------------------
> THORSTEN ALBERS Universität Freiburg
> albers@
> uni-freiburg.de
> ----------------------------------------------------------------------
>
.
- Follow-Ups:
- Re: Why use the unicode version of the api?
- From: Thorsten Albers
- Re: Why use the unicode version of the api?
- References:
- Why use the unicode version of the api?
- From: Gustavo Echevarria
- Re: Why use the unicode version of the api?
- From: Thorsten Albers
- Re: Why use the unicode version of the api?
- From: Tony Proctor
- Re: Why use the unicode version of the api?
- From: Thorsten Albers
- Why use the unicode version of the api?
- Prev by Date: Re: Possible to add a button to an API dialog?
- Next by Date: Re: Time passed since last user action
- Previous by thread: Re: Why use the unicode version of the api?
- Next by thread: Re: Why use the unicode version of the api?
- Index(es):
Relevant Pages
|