From: "Skip Tavakkolian" <fst@centurytel.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How to writesubfont() for Memsubfont type?
Date: Thu, 19 Sep 2002 20:49:04 -0400 [thread overview]
Message-ID: <0e836bb70c61fbbc2da474334444503a@centurytel.net> (raw)
Thanks. I really should look at the code (the beauty of opensource).
This is the path I'm taking now.
How did I miss ttf2subf? Where do I get it?
> if you're just building subfonts to write to a file, you can fill in
> a Subfont instead of a Memsubfont and use writesubfont instead,
> since the latter doesn't need the draw subsystem (it just writes
> a representation to a file using write).
>
> that's what i did for my Freetype ttf2subf program.
next reply other threads:[~2002-09-20 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 0:49 Skip Tavakkolian [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 17:03 C H Forsyth
2002-09-19 15:46 rob pike, esq.
2002-09-19 11:46 Skip Tavakkolian
2002-09-19 11:46 Skip Tavakkolian
2002-09-19 9:59 rob pike, esq.
2002-09-19 3:46 Skip Tavakkolian
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=0e836bb70c61fbbc2da474334444503a@centurytel.net \
--to=fst@centurytel.net \
--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).