From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: [9fans] catenating subfont files, catsf
Date: Mon, 15 Dec 2003 11:59:18 +0900 [thread overview]
Message-ID: <1ced80d01a18ec54a5b7a944fddd9ca4@orthanc.cc.titech.ac.jp> (raw)
Ttf2subf is great, but the ouptut subfont files have
been sliced into very small pieces.
For example, I tried ttf2subf on the Cyberbit font and it
produced a font(6) file of almost 2000 lines. Furthermore,
in cerntain ttf, the result was almost 4000 lines and it
slows rio considerably using the font.
So I made a program catenating multiple subfont files
into a single file.
The following lines would do the installation for you:
hget http://p9c.cc.titech.ac.jp/plan9/catsf.tgz | gunzip | tar
cd catsf; mk install
See the manpage included in the tgz for more details.
--
YAMANASHI Takeshi
next reply other threads:[~2003-12-15 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 2:59 YAMANASHI Takeshi [this message]
2003-12-15 4:14 ` Chris Hollis-Locke
2003-12-15 5:32 YAMANASHI Takeshi
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=1ced80d01a18ec54a5b7a944fddd9ca4@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).