RE: 2-bytes character display ready ?

[Yen-Ju Chen]

  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.
  3. In XGFont.m, use XFontSet to set the Font.

  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.

  Any suggestion will help

  Thanx a lot.

  Yen-Ju

> -----Original Message-----
> From: discuss-gnustep-admin@gnu.org
> [mailto:discuss-gnustep-admin@gnu.org]On Behalf Of Fred Kiefer
> Sent: Monday, February 18, 2002 5:37 PM
> To: Yen-Ju Chen
> Cc: discuss-gnustep@gnu.org
> Subject: Re: 2-bytes character display ready ?
>
>
>  Sorry, we still don't provide the full Unicode text information from the
> front end to the back end. Actually the GNUstep developers at the FOSDEM
> have just been discussing this last weekend. And somehow I once again
> failed to make my point. So for the next time, we have to live with the
> PostScript interface between these two modules, which only allows for
> ASCII sized characters.
> Just to repeat this: The problem is more in the interface of the back
> end than in the backed itself.
>
> The good news here is that we agreed at FOSDEM to allow for a special
> method for NSBezierPath to be handed over to the back end more
> efficiently. So as the others made already one compromise in the pure PS
> interface, they will (after some more lobbying) surely allow for more.
>
> Cheers
> Fred
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://mail.gnu.org/mailman/listinfo/discuss-gnustep