delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/01/11/14:10:11

Xref: news-dnh.mv.net comp.os.msdos.djgpp:4264
Path: news-dnh.mv.net!mv!news.sprintlink.net!datalytics!news.ahc.ameritech.com!ddsw1!news.mcs.net!news.exodus.net!uunet!in2.uu.net!news.mathworks.com!news.kei.com!nntp.coast.net!swidir.switch.ch!cisun2000.unil.ch!iishp1!borel
From: borel AT iishp1 (Alain BOREL)
Newsgroups: comp.os.msdos.djgpp
Subject: GRX 2.0 and unicode problem
Date: 10 Jan 1996 12:01:06 GMT
Organization: University of Lausanne CH (Switzerland)
Lines: 20
Message-ID: <4d09q2$725@cisun2000.unil.ch>
NNTP-Posting-Host: iishp1.unil.ch
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

I have started drawing a Unicode font for use with the LIBGRX 2.0
beta (actually, I just added 64k-256 empty glyphs to an existing
font and s-l-o-w-l-y draw a few more in the empty slots). Now
I would like to display characters above 256, one at a time
(no strings yet); the problem is that LIBGRX only seems to
understand the lower byte of the word I ask.
I guess that the text attributes must be set to GR_WIDE_CHAR
(or somethong like that). Yes, I took a look at the source,
but unfortunately there are lots of #define'd constants
used in the function (I think it was GrDrawString) and
I got lost trying to replace them by their values.

So, did anyone try to do something like that? If yes, let
me hear of your success (hopefully) or failure.

Thank you in advance

Alain Borel
<borel AT iishp1 DOT unil DOT ch>

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019