From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1722437096d2b5c0615f6967a5b9e241@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ttf2subf (again)
From: rog@vitanuova.com
In-Reply-To: <01731cefa649f6fe524c9886640c4aea@orthanc.cc.titech.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed, 13 Aug 2003 19:17:10 +0100
Topicbox-Message-UUID: 1a01a376-eacc-11e9-9e20-41e7f4b1d025

> I kind of feel implement it as a file server
> sits on somewhere like /lib/font/bit/ttf.  When a
> certain font like /lib/font/bit/ttf/R.7.1 is requested
> to be open(2)ed and doesn't exist, the server creates
> it using ttf2subf and returns the resulted bit map font.

the question is how much information to embed in the path name...  and
what does one do about partial matching.  short names are desirable
(we don't want to end up with something that looks like X11 font
specs), but then again it might be nice to be able to specify "12pt
bold" without worrying about the exact typeface...