> TrueType font with, say, fonts for A000 to A4CF, then you can load it into > memory using whatever software you have for > doing that, which will load it into memory in steps of 96 or 192 bytes at a > time, into the format which Amiga's graphic.library can use. You can then > either make a simple call to ucode.library or make a simple AREXX command to > put those characters into A000 to A4CF within Ucode's memory. If you often > used the same characters, you could ask ucode.library to save that > range of
[snip] > be loaded on the fly form disk in about 3 seconds. Or, you can pre-load the > most commonly used glyphs into memory, > when a window-full can be displayed in less than a second (running at > 50MHz). Long winded, ne? Saving glyph caches to disk is a waste of disk space. > > There is an easy way of avoiding a multi-megabyte download. > > > > Grab a copy of Microsoft Office, extract the fonts from the CDs. Or go > > buy a font CD from any DTP vendor. > > Isn't that slightly illegal? If you buy a font CD then you are legally allowed to use the fonts, no? As for using fonts from Microsoft Office, you licensed the copy of MS Office, didn't you? Microsoft offer most of them for free download, and you can even take them and encode them for the web. > > Can you do either with ShillitoFonts? :) > > No because there *aren't* any Shillito fonts. But if you want my glyph > packs, I daresay by now they are out on Aminet glyph pack == font, in my experience. What else is a font but a bunch of graphics and a reference table? <snip> Blah blah. I already coded a unicode font solution, discussed it with ttf.lib and ft2.lib authors, begged for enhancements and hints on source code and it works. Open a font, render text, close a font. It's no more complex. I am a little dismayed by the wealth of Unicode and Truetype rendering solutions out on Aminet these days which require either a lot of hassle of a LOT of custom rendering options to get output. I have simply cloned graphics.library and diskfont.library functions (such as TextExtent) to deal with unicode strings and glyphs from a bullet.library-API font. It uses no exorbitant amount of memory. It caches glyphs. Under MorphOS it can render antialiased text the same way Voyager renders alpha transparent PNG files. And it's fast - certainly no slower than standard API calls (hell.. I use the same functions the CGX Text() patch uses..) It's even got provisions for rendering for print previews etc. I basically wrote it to see if the Amiga font system was up to the job, and while it has a few missing features (which I can either emulate or implement in ttf.library or pull from OS4.0 or MorphOS solutions.. not a deficiency in my library, but the host system) It's been at the ttflib Yahoogroups site for about a year or so now, I don't think I touched it since February either. At the least it's a fancy interface to the bullet API that I *will* leverage to get fancy fonts in Voyager (quite essential for CSS) -- Matt Sealey <[EMAIL PROTECTED]>
