ANSI_CHARSET

[Jeff Smith]

ANSI_CHARSET and SYMBOL_CHARSET need to be defined (in include/wingdi.h), 
but I
  have some doubts about the details.

SYMBOL_CHARSET should be defined as (BYTE)2, I believe.

If the current value of DEFAULT_CHARSET as (BYTE)1 is correct, then I 
suspect
  ANSI_CHARSET should be (BYTE)0.  I question the current value of
  DEFAULT_CHARSET, and suspect it should be the reverse (DEFAULT:0 ANSI:1).
  DEFAULT defines tend to be 0 except for a few special cases (and this one
  does not fit as one of in my book).

I'm sure someone out there is more familiar with this than I am, and I would
  appreciate their feedback.

Notes:
  There is a function in shell32.dll as distributed in Win95-OSR-2.1, that 
uses    the LOGFONT structure.  In this function, the structure is used for 
three
  fonts: "Times New Roman", "Arial", and "Wingdings".  The lfCharSet member 
for
  each case is 0, 0, and 2, respectively.

-- Jeff Smith

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

[Francois Gouget]

On Mon, 2 Sep 2002, Jeff Smith wrote:
> ANSI_CHARSET and SYMBOL_CHARSET need to be defined (in include/wingdi.h),
> but I have some doubts about the details.
>
> SYMBOL_CHARSET should be defined as (BYTE)2, I believe.
>
> If the current value of DEFAULT_CHARSET as (BYTE)1 is correct, then I
> suspect
>   ANSI_CHARSET should be (BYTE)0.  I question the current value of
>   DEFAULT_CHARSET, and suspect it should be the reverse (DEFAULT:0 ANSI:1).
>   DEFAULT defines tend to be 0 except for a few special cases (and this one
>   does not fit as one of in my book).

[...]

Don't know much about this but the Microsoft headers say that:
 * ANSI_CHARSET    is 0
 * DEFAULT_CHARSET is 1
 * SYMBOL_CHARSET  is 2

And that settles it.

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
              Linux: Because rebooting is for adding new hardware

[Marcus Meissner]

On Mon, Sep 02, 2002 at 11:56:49PM -0700, Francois Gouget wrote:
> On Mon, 2 Sep 2002, Jeff Smith wrote:
> > ANSI_CHARSET and SYMBOL_CHARSET need to be defined (in include/wingdi.h),
> > but I have some doubts about the details.

They are already defined there:

#define ANSI_CHARSET          (BYTE)0   /* CP1252, ansi-0, iso8859-{1,15} */
#define DEFAULT_CHARSET       (BYTE)1
#define SYMBOL_CHARSET        (BYTE)2

Why arent they in your wingdi.h file?

Ciao, Marcus

[Francois Gouget]

On Tue, 3 Sep 2002, Marcus Meissner wrote:
> On Mon, Sep 02, 2002 at 11:56:49PM -0700, Francois Gouget wrote:
> > On Mon, 2 Sep 2002, Jeff Smith wrote:
> > > ANSI_CHARSET and SYMBOL_CHARSET need to be defined (in include/wingdi.h),
> > > but I have some doubts about the details.
>
> They are already defined there:
>
> #define ANSI_CHARSET          (BYTE)0   /* CP1252, ansi-0, iso8859-{1,15} */
> #define DEFAULT_CHARSET       (BYTE)1
> #define SYMBOL_CHARSET        (BYTE)2
>
> Why arent they in your wingdi.h file?

They are in mine, but Jeff seems to think they are wrong. All I'm saying
is that since they match the Microsoft values they are by definition
correct.

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
  Any sufficiently advanced Operating System is indistinguishable from Linux

[Shachar Shemesh]

Francois Gouget wrote:
> All I'm saying
> is that since they match the Microsoft values they are by definition
> correct.

I think "correct" is too strong a word here. I would go for "conforming".

Shachar

[Andreas Mohr]

On Tue, Sep 03, 2002 at 10:34:28AM +0300, Shachar Shemesh wrote:
> Francois Gouget wrote:
> > All I'm saying
> > is that since they match the Microsoft values they are by definition
> > correct.
>
> I think "correct" is too strong a word here. I would go for "conforming".

Well said !
Given Microsoft's biblical documentation "correctness",
I can't help but wonder whether we should reject this value order completely
and use our own instead ;-))