nanogui: Fonts revisited
Subject:
Re: Fonts revisited
From:
"Greg Haerr" ####@####.####
Date:
20 Jan 2000 18:35:57 -0000
Message-Id: <023001bf6373$b16c0ae0$15320cd0@gregh>
: I suggest that GdText() is changed to use a low level function for drawing
: strings in whatever encoding the font uses, and that any i18n support is
: added in GdText() or above, so that the low level function doesn't have to
: bother about those issues at all.
My point here was that, if strings are to be passed as parameters, rather
than characters, then we have to decide now whether they're 8 bit or
16 bit strings... TrueType uses UNICODE, IIRC, but also has
provisions for an 8-bit codepage index to unicode to be carried
with the font so that 8-bit glyph indices can be used.
: I suggest that we require the low level renderer to use the psd->*()
: functions or the Gd*() functions. My T1lib support now uses GdArea()
: (since I use antialiasing, and T1lib can return something that works
: with GdArea(), that was the easiest ;)
:
Super. I like that. Someday GdArea can be sped up with two
planned improvements: breaking up the clipped area into multiple
GdArea() rectangles, and having GdArea use blit for max speed.
Actually, Morten should be working on the former. This method
also doesn't require getting involved with the clip code.
: >Cool. Take a shot at it.
:
: I have, and I can assure everyone that it looks *great* - the antialiasing
: makes the fonts look much better than it does with my X Windows setup :)
: I'll clean it up a bit, and make a patch available.
Are you going to include T1lib? Or should we pull it down and
compile it separately? I can't wait to see the antialiasing... Hopefully
you'll have a good demo ;-)
Regards,
Greg
