From: Latchesar Ionkov <lucho@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] ttf2subf
Date: Wed, 22 Mar 2006 21:33:23 -0500 [thread overview]
Message-ID: <20060323023323.GA18511@ionkov.net> (raw)
In-Reply-To: <109e196c9ccbae39c56a955dbc3e150d@swtch.com>
I think the magic most ttf fonts use to look good on screen is embedding
bitmap fonts for the small sizes.
Thanks,
Lucho
On Wed, Mar 22, 2006 at 09:25:39PM -0500, Russ Cox said:
> > i did for a while and you can find the latest source on sources or on
> > the web. i heard there's another ttf2subf which gets better results
> > generating less subfonts (which is what i worked last on, and i think
> > i made reasonable success). i have no idea whether the other one has
> > made it out.
>
> the program that generates fewer subfonts is one that
> rob wrote and starts with bdf, not ttf.
>
> generating screen fonts from ttf is basically not a good idea.
> they're going to be ugly at the low resolutions unless they
> were explicitly designed to double as screen fonts. the only
> examples i know of in that camp are verdana and georgia,
> but i'm not sure that the magic ttf goo that encodes how to
> make them look good at small resolutions is known to libfreetype.
> http://www.will-harris.com/verdana-georgia.htm
>
> you're much better off finding fonts that were designed as
> real bitmap fonts from the start. any of apple's early bitmap
> fonts would fit this category too, but i'm sure they're not
> available for general use.
>
> all that said, we've got a collection of very nice fonts - the pelm,
> lucm, and lucida bitmaps - i'd stick to those. if you must, there's
> always the x11 fixed-width fonts (/lib/font/bit/fixed).
>
> russ
next prev parent reply other threads:[~2006-03-23 2:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 0:12 erik quanstrom
2006-03-23 0:45 ` andrey mirtchovski
2006-03-23 2:25 ` Russ Cox
2006-03-23 2:33 ` Latchesar Ionkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 3:57 erik quanstrom
2006-03-23 4:36 ` Russ Cox
2006-03-23 7:58 ` Bruce Ellis
2006-03-23 11:38 ` erik quanstrom
2006-03-23 14:32 ` Russ Cox
2006-03-23 3:20 erik quanstrom
2006-03-23 3:33 ` Russ Cox
2006-03-23 2:51 erik quanstrom
2006-03-23 2:57 ` Russ Cox
2006-03-23 2:34 erik quanstrom
2006-03-23 4:31 ` Latchesar Ionkov
2006-03-23 2:29 erik quanstrom
2006-03-23 2:35 ` andrey mirtchovski
2006-03-23 2:38 ` Russ Cox
2006-03-23 2:52 ` geoff
2006-03-23 3:00 ` andrey mirtchovski
2006-03-23 3:06 ` andrey mirtchovski
2006-03-23 10:40 ` Arvindh Rajesh Tamilmani
2006-03-23 2:03 erik quanstrom
2006-03-23 2:27 ` Latchesar Ionkov
2006-03-23 10:18 ` Charles Forsyth
2006-03-23 21:38 ` Tim Wiess
2005-05-05 3:06 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=20060323023323.GA18511@ionkov.net \
--to=lucho@gmx.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).