From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ttf2subf (again)
Date: Wed, 13 Aug 2003 10:12:13 +0900 [thread overview]
Message-ID: <01731cefa649f6fe524c9886640c4aea@orthanc.cc.titech.ac.jp> (raw)
> My aim is to produce a scalable font server.
I'm interested in the implementation of the server.
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 beauty of Plan 9 file server.
--
YAMANASHI Takeshi
next reply other threads:[~2003-08-13 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 1:12 YAMANASHI Takeshi [this message]
2003-08-13 18:17 ` rog
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=01731cefa649f6fe524c9886640c4aea@orthanc.cc.titech.ac.jp \
--to=uncover@beat.cc.titech.ac.jp \
--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).