[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Language Setup Document (Re: Text drawing bug - gaps after 16th char

From: Kazunobu Kuriyama
Subject: Re: Language Setup Document (Re: Text drawing bug - gaps after 16th character ...)
Date: Tue, 08 Jul 2003 15:49:33 +0900
User-agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.0.0) Gecko/20020614

Pete French wrote:

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 ?

Do you remenber where you saw the patch? (I join the two mailing
lists discuss-gnustep and bug-gnustep. Is there other useful list?)

It might be the one I privately sent to Adam Fedor several weeks ago.
The code I added to the source sums up a few hundred lines, making
the source code twice as much as it is.  So I have to deal with
some legal stuff together with the Free Software Foundation for the patch
to be applied to GNUstep officially.  I asked the FSF to send me a form for
that procedure.  But I haven't received it yet.  That's why I can't
make it public.

So if you refer to this particular patch,

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]