Re: 2-bytes character display ready ?

[Fred Kiefer]

This sounds great!

Yen-Ju Chen wrote:

> I try some modification and start getting some good results. :) This
>  is what I did:
>
> 1. In NSStringDrawing, use encode_unitochar_strict instead 
encode_unitochar.
>

> 2. Change char to unsigned char in DPSshow.


You surely refer to "unsigned" as meaning "unsigned in" not "unsigned
char" here. Otherwise this would not make much difference.

> 3. In XGFont.m, use XFontSet to set the Font.
This last step should not be needed. There is an X interface to draw 16 
bit strings. As far as I remember I put a comment on this in the code. 
Still font sets are fun to have, the only problem being that you don't 
get that range of informations on them, as you get for normal strings. 
What I would suggest is that you make just another subclass of 
GSFontInfo and register that in initializeBackend, as I did for 
XftFontInfo to gat simple anti-aliasing.


> Then I can show 2-bytes character in NSTextField and NSButton !! That
>  is a ugly modification because I'm not familiar with Xlib and unicode.
>

>
> Is the PostScript interface means char vs unsigned char ? I found
> DPSxxx() always accept const char.
>
> Since ASCII character is a subset of 2bytes character, I hope
> GNUstep can include the ability to handle 2bytes character. I have
> no idea how hard it will be, or how it will break the PostScript
> interface. But here is my idea after my first successful try, which
>  may totally wrong. 1. Add XFontSet into GSFontInfo interface. XFontSet
>  can handle the font for 2bytes character. 2. Initiate XFontSet as
> XFontStruct in XGFont.m. That's the most difficult part for me. Too
>  many parameters. 3. If it won't break any interface, use unsigned
> char instead char.
>
This is exactly the change I was refering to in my mail. But now that 
you can proof that this extension would be needed, some people might 
change their mind and we might get this additional interface.

Cheers
Fred