From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 25 Feb 2010 17:01:38 -0500 To: 9fans@9fans.net Message-ID: <292491efe596302123ad9aef0ac07dee@brasstown.quanstro.net> In-Reply-To: <14ec7b181002251345n5cea8b70nd05962d8b6386732@mail.gmail.com> References: <14ec7b181002152057p7128c56fre09bee50d96e28ae@mail.gmail.com> <14ec7b181002170844s17b0b37bve34e5e7fe36ec258@mail.gmail.com> <14ec7b181002251345n5cea8b70nd05962d8b6386732@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] problem using a vera font in rio Topicbox-Message-UUID: db7e5db0-ead5-11e9-9d60-3106f5b1d025 > i want pretty fonts in acme, but i'm not sure ttf2subf will get us > there without major work (and a new port of the freetype libraries). i've been running ttf2subf with the freetype appendage cut off. i'm using the system library directly from p9p. that seems to work better than porting the whole freetype blob to plan 9 or carting around an old copy of freetype. (generally, i'd rather port to plan 9.) unfortunately, i haven't made time to clean this version up enough to stick out for public consumption. yet. i think the cutoff problem has to do with not extending the antialiasing all the way down to the true bottom of the character. i notice that the ds were cut off, but not gs and ys at least in the last font. - erik