From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ttf2subf (again)
Date: Wed, 13 Aug 2003 19:17:10 +0100 [thread overview]
Message-ID: <1722437096d2b5c0615f6967a5b9e241@vitanuova.com> (raw)
In-Reply-To: <01731cefa649f6fe524c9886640c4aea@orthanc.cc.titech.ac.jp>
> 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...
next prev parent reply other threads:[~2003-08-13 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 1:12 YAMANASHI Takeshi
2003-08-13 18:17 ` rog [this message]
2003-08-13 21:13 ` matt
-- strict thread matches above, loose matches on Subject: below --
2003-08-27 3:16 Joel Salomon
2003-08-15 3:03 YAMANASHI Takeshi
2003-08-12 16:13 andrey mirtchovski
2003-08-12 17:41 ` Charles Forsyth
2003-08-12 18:38 ` Latchesar Ionkov
2003-08-12 18:54 ` Chris Hollis-Locke
2003-08-12 19:14 ` Latchesar Ionkov
2003-08-13 9:29 ` Martin C.Atkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1722437096d2b5c0615f6967a5b9e241@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).