This SAR contains pre-rendered versions of the BitstreamVera family, alongwith the FT2Font class and the BitBlt and other changes required to displaythese fonts (with or without the enhanced BitBlt plugin, but since I'm theonly one right now with a copy of that plugin that doesn't matter). It should work in a recent (3.7a) Squeak image; I have only tried it in a 5816image. Arjen van Elteren wrote the original plugin and font code; I have modified itto understand style changes (bold, italic, etc.) and to render properly inthe absence of the enhanced BitBlt modes that were provided by his plugins. There is also a plugin that speeds up drawing (which works under Linux rightnow), and a plugin that interfaces with the Freetype/2 libraries. I will beputting the code for all of these things on SqueakMap. I find them quite usable. They don't have the arrows re-mapped; I could dothis easily if there is enough demand (the glyphs are (I believe) in theoriginal fonts)). I believe that the demo has characters in the Latin1mapping, rather than MacRoman (I can fix this easily, but wanted to get asample out). Currently, the design of the FT2Font is very similar to the design of theStrikeFont: the character glyphs (corresponding to characters whose valuesare between 0 and 255) are stored in a single Form. So to use these for extended character sets would require a bit of tinkering.However, the FT2 library interface is quite capable of working together withsomething like TTCFont and producing better antialiased results. The font interface in Squeak should be unified; there is quite a bit ofoverlap. The BitBlt changes could also benefit TTCFonts which are rendered in a singlecolor. Right now we're caching 32-bit forms rendered in a single color. Usingthis 8-bit deep encoding would mean that we could save at least 75% of thememory, and more whenever we're rendering the same glyphs in differentcolors. I will be moving Arjen's BitBlt changes out of mode 34 and into a new mode(38?) soon.