Re: Language Setup Document (Re: Text drawing bug - gaps after 16th character ...)

[Pete French]

> The current implementation of XGFont.m uses only XDrawString to draw 
> literal strings on the screen.

Was this not fixed ? I saw a patch go round a very long time ago that
seemed to be to fix it to draw muti-byte UTF8 encodings on the screen
didnt I ?

> NSGlyph*.  In other words,
> it works fine only for single byte charaters.  (This may be a subtle 
> point for those who exclusively
> use single byte characters.)

What do you mean by 'multi-byte' here ? That deoends on the encoding does it
not ? I used to use xlib all the time, and one pof the charatres I displayed
was a UK pound sign. This is encoded at C3 A8 as far as I am aware (thats
certainly how I store it) so I wold have thought i counted a "multi-byte"
and it certainly displayed properly under xlib. On the other hand it may be
that the multi-byte encoding can be mapped to a single byte representing the
character.

-bat.