From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ttf2subf
Date: Wed, 22 Mar 2006 20:34:57 -0600 [thread overview]
Message-ID: <903f4a3dcca9eb812b79ac7ba02d52b2@quanstro.net> (raw)
not true (at least on p9p):
; for(i in 10 12 16) ttf2subf -f *.ttf -s $i -n dolous -m subpixel -r rgb
; font=`{pwd}^/dolous/dolous.16.font 9term
- erik
On Wed Mar 22 20:27:43 CST 2006, lucho@gmx.net wrote:
> You can ignore the subpixel mode -- libdraw doesn't support it.
>
> Thanks,
> Lucho
>
> On Wed, Mar 22, 2006 at 08:03:29PM -0600, erik quanstrom said:
> > i've been using a version that makes an attempt to generate as few subfonts as possible.
> > the last time i goggled ttf2subf the website located was down.
> >
> > i've been working with code2000, which looks hideous in mono mode, but is pretty readable
> > subpixel or antialias mode, but ttf2subf is too agressive in its antialiasing and does not snap
> > near-grid vertical or horizontal lines to the grid.
> >
> > i cleaned up the code a bit and think that in subpixel mode, it generates non-grey
> > pixels. that is pixels like
> >
> > char a,b,c;
> >
> > (a<<24) | (b<<16) | (c<<8) | 0xff where a, b, c are not all equal.
> >
> > but i have not yet come up with a good solution to either issue.
> >
> > - erik
> >
> > On Wed Mar 22 18:51:46 CST 2006, mirtchovski@gmail.com wrote:
> > > 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.
> > >
> > > On 3/22/06, erik quanstrom <quanstro@quanstro.net> wrote:
> > > > has anybody been working on this program? (it converts truetype fonts
> > > > to plan9 subfonts by using freefont.)
> > > >
> > > > - erik
> > > >
>
next reply other threads:[~2006-03-23 2:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 2:34 erik quanstrom [this message]
2006-03-23 4:31 ` Latchesar Ionkov
-- 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: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
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
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=903f4a3dcca9eb812b79ac7ba02d52b2@quanstro.net \
--to=quanstro@quanstro.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).