From: "Chris Hollis-Locke" <chris@hollis-locke.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] ttf2subf changes
Date: Sat, 14 Feb 2004 20:03:36 +1300 [thread overview]
Message-ID: <000901c3f2c8$ad94b190$2a8158db@laptop> (raw)
In-Reply-To: <4ac03d521d7f802fa70c6a33cb729dc8@plan9.ucalgary.ca>
Don't subsitute the 0x0 glyph, just set width to 0 in the metrics data for
the glyph, devdraw does the 0x0 glyph substitution. This results in the
image part of the file being much smaller.
From: "andrey mirtchovski" <mirtchov@cpsc.ucalgary.ca>
> now ttf2subf substitutes the 0x0 glyph whenever it doesn't have a
> particular glyph. for normal fonts containing basic latin/cyrillic
> support this results in 12 to 15 subfont files only, which is
next prev parent reply other threads:[~2004-02-14 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 21:16 andrey mirtchovski
2004-02-14 7:03 ` Chris Hollis-Locke [this message]
2004-02-14 23:07 ` andrey mirtchovski
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='000901c3f2c8$ad94b190$2a8158db@laptop' \
--to=chris@hollis-locke.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).