> Actually I would call this a FGFS problem in that FGFS is > asking for a character that is not present in the PLib font > that is being used. The PLib Font system does not claim > to be a universal font renderer in fact just the oposite in that > it gives you only the characters that it can pack into a 256x256 > image. This is primarily for performance reasons.
I think it's a bug if PLIB crashes because I ask for an unavailable char. > > For now I'm going to replace "|" with a space. > This is the practical approach but note that the '|' character may > not be present in all of the 'stock' plib fonts so we may still have > this problem if a user 'replaces' the default font file. We could replace "|" with "!" and "_" with "-" as required, i.e. whenever PLIB asserts that those character codes are not available. > FWIW I have been experimenting with using the freetype library > with PLib and this would give us all the characters in any or the > truetype fonts. These do look MUCH better in that they are 'true > vector' fonts but they are noticeably slower to render How about starting with an empty PLIB-style texture, and adding characters to it incrementally using freetype, whenever they are first used to render to the screen. When it gets full, use LRU to overwrite existing entries. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
