From: "Chris Hollis-Locke" <chris@hollis-locke.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] catenating subfont files, catsf
Date: Mon, 15 Dec 2003 17:14:51 +1300 [thread overview]
Message-ID: <003201c3c2c1$fe6340a0$c48058db@laptop> (raw)
In-Reply-To: <1ced80d01a18ec54a5b7a944fddd9ca4@orthanc.cc.titech.ac.jp>
----- Original Message -----
>From: "YAMANASHI Takeshi" <uncover@beat.cc.titech.ac.jp>
>
> 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.
>
Wouldn't it be better to fix ttf2subf rather than add more utils to fix
problems with existing ones?
I showed how to do it in a limbo prog I posted here a few months ago.
You map subfonts to standard unicode ranges as defined by unicode.org.
A simple scan determines which pages are present, you then produce subfonts
with 0 width glyphs for
those in a range that do not exist in the source font - causing draw to
render a peterface.
(there are other obvious optimisations to minimise the amount of glyph data
per subfont).
I haven't looked at ttf2subf but the Limbo prog was very simple, it cannot
possibly be that difficult.
Alternatively you could always use my Limbo app.
Chris.
next prev parent reply other threads:[~2003-12-15 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 2:59 YAMANASHI Takeshi
2003-12-15 4:14 ` Chris Hollis-Locke [this message]
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='003201c3c2c1$fe6340a0$c48058db@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).