Paul,
While the bug tracker is the appropriate place to file bugs,
there hasn't been a lot of activity on the PLIB site lately and in fact
the mailing lists are probably a better choice.
I doubt that there is a guide for porting TexFont to PLIB. I'm
probably more familiar with the "fnt" library than most people, though,
and while I'm a bit busy right now I am certainly willing to answer
questions and help when I can.
John F. Fay
Technical Fellow
Jacobs Technology TEAS Group
850-883-1294
-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of Paul Wise
Sent: Tuesday, April 15, 2008 12:18 AM
To: pli...@li...
Subject: [Plib-users] plib fnt bug
Hi all,
I'm porting Chromium BSU from Mark J. Kilgard's non-free[1] TexFont code
to plib's fnt library. The first issue I came across was that the plib
fnt code does not store and use the max descent value for the font and
it stores the max ascent value in a field called max_height. In TexFont,
max_ascent - max_descent is returned by the txfStringHeight function.
I've filed a bug about this at [2].
I'm wondering if the tracker is the right place to file bugs?
I'm wondering if there is a guide to porting TexFont code to plib? The
rest of the TexFont functions used by Chromium BSU are txfStringLength,
txfRenderString and txfBindFontTexture.
1. http://bugs.debian.org/467123
2. http://sf.net/support/tracker.php?aid=1942632
--
bye,
pabs
http://pabs.zip.to
|
