LOGFONT lf;
memset( &lf, 0, sizeof(LOGFONT) );
lf.lfHeight = 240; // tenths of a point
_tcscpy( lf.lfFaceName, _T("Arial") );
lf.lfCharSet = ANSI_CHARSET;
VERIFY( m_Font.CreatePointFontIndirect(&lf) );
...what is the meaning of ANSI_CHARSET? I know the (mis)use of "ANSI" to
mean "not Unicode" in its usual Win32 API context. In its "not Unicode"
sense, "ANSI" means shift-JIS as well as CP1252. The FooA() APIs take
shift-JIS, while FooW takes Unicode, for example.
The above usage is just a way of specifying a subset of fonts installed on
the current system. Since there is a separate SHIFTJIS_CHARSET, as well as
Korean and Chinese equivalents, does the above (mis)use really just mean
"only CP 1252", therefore not Japanese or Chinese on a US system, or does it
mean whatever the standard script system is on the current OS?
Thanks.
--
MichKa
random junk of dubious value at the multilingual
http://www.trigeminal.com/ and a new book on
i18N in VB at http://www.trigeminal.com/michka.asp
"Art Decco" <ple...@dontemail.com> wrote in message
news:u3gxpRh7$GA....@cppssbbsa02.microsoft.com...
CP1252 is closer to it than the "A" functions with actually will accept any
code page depending on the system default. So it is less of a misuse of the
term (jaywalking rather than assault? <g>).
In any case, DEFAULT_CHARSET is what you want to use here.
--
MichKa
random junk of dubious value at the multilingual
http://www.trigeminal.com/ and a new book on
i18N in VB at http://www.trigeminal.com/michka.asp
"Brendan Murray" <bpmu...@no-spam-At-mediaone.net> wrote in message
news:Ww%b5.26914$DJ2.1...@typhoon.ne.mediaone.net...
Agreed. But of since they use it in a way that is obviously not true, I do
not have as hard of a time with it as some people do. In summary (MS term
and its actual meaning):
*ANSI (for charsets)= all western european code pages (fonts map all of
that)
*ANSI (for everything else) = ~Unicode ("Not" Unicode)
*Unicode (<Win2000) = UCS-2, Little endian
*Unicode (>=Win2000) = UTF-16, Little endian
Seems simple enough, even if it is not standard terminology. :-)
> And because of their continued insistance on tagging CP1252
> data with "charset=iso-8859-1", this is an assault on all other
> purveyors of better-quality messaging systems who have to
> accomodate this abuse.
What programs do this? I do not think any of the ones I run do, but I only
use Exchange 5.0 and Outlook Express for e-mail (and the latter has separate
tags for Western European (ISO) and Western European (Windows).
michka
--
MichKa
random junk of dubious value at the multilingual
http://www.trigeminal.com/ and a new book on
i18N in VB at http://www.trigeminal.com/michka.asp
"Brendan Murray" <bpmu...@no-spam-At-mediaone.net> wrote in message
news:TxCc5.31999$DJ2.1...@typhoon.ne.mediaone.net...
Agreed
> *ANSI (for everything else) = ~Unicode ("Not" Unicode)
> *Unicode (<Win2000) = UCS-2, Little endian
> *Unicode (>=Win2000) = UTF-16, Little endian
Widely seen is "Wide" being a synonym for what you call "Unicode".
> Seems simple enough, even if it is not standard terminology. :-)
> > And because of their continued insistance on tagging CP1252
> > data with "charset=iso-8859-1", this is an assault on all other
> > purveyors of better-quality messaging systems who have to
> > accomodate this abuse.
>
> What programs do this?
About every old ones. BTW, competitors were no better (and since
MS entered this market later, this is hardly MS's fault).
This have been corrected in the products that presently ship (thanks!)
Antoine
Well, yes.... but not in any MS documentation or product UIs.... they call
it Unicode there. Even UTF-8 is JAM (just another multibyte? <g>).