On Mon, 11 Dec 2000, Christoph Egger wrote:

> What I want to say is:
> 
> Use routines with 32bit-wide chars (signed long) for extensibility and
> flexibility.
> 
> Use US-ASCII-chars as _default_, unless the user sets the charset s/he wanna
> use.
> 
> 
> For example, you have in the <ggi/gft.h> something like this:
> -----------------------------------------------------
> ...
> 
> enum {
>       GFT_US_ASCII,   /* 7-bit font */
>       GFT_IBM_ASCII,  /* 8-bit font */
>       GFT_UNICODE,
>       GFT_LATIN1,
>       GFT_LATIN2,
>       ...
> 
>       GFT_LAST_FONT
> } charset_t;
> 
> 
> /* Sets the charset. You can also change the current
>  * charset during runtime.
>  * It fails, if it isn't supported by the used target/font-type
>  * and falls back to the one used before.
>  */
> int gftSetCharset(enum charset_t charset);
> 
> 
> /* Returns the current charset. It returns GFT_US_ASCII as default,
>  * when no charset is set before.
>  */
> int gftGetCharset(enum charset_t *charset); 
> 

OK this is already an option to the the user through the freetype call

FT_Select_Charmap(font, map);

Calls to gftPrintCode(vis, font, code)  would then map using the desired code.

I still feel obligated to keep the PrintChar functions because of their
simplicity and are what somebody would intuitively look for. Blindly using
these routines should get you the "right" result.

I think we're all on the same page here.  I like your comments and I take them
all seriously.  It's more fun that way.


-- 
Lee Brown Jr.
[EMAIL PROTECTED]

Reply via email to