From: Latchesar Ionkov <lucho@ionkov.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bitstream vera
Date: Sun, 26 Oct 2003 12:48:39 -0500 [thread overview]
Message-ID: <20031026174839.GA21901@ionkov.net> (raw)
In-Reply-To: <f20c84b2632e4e1f64c3208cbb606f83@vitanuova.com>
On Sun, Oct 26, 2003 at 03:57:02PM +0000, C H Forsyth said:
> is that canonical? any references? i'd like to know that's really
> what is supposed to be implemented, without having to
> go off to investigate, since i've got a lot on at the moment.
I don't know if it is canonical and I don't have any references. Finding out
that is one of the reasons I asked on the mailing list before I start
implementing it.
I just looks as the easiest way of implementing subpixel fonts -- the font
image is used as a mask for memdraw, if the red, green, and blue channels
from the mask are used as masks for red, green, and blue channels we can get
the subpixel font drawn properly.
Thanks,
Lucho
> From: Latchesar Ionkov <lucho@ionkov.net>
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] bitstream vera
> Date: Sun, 26 Oct 2003 09:05:47 -0500
>
> Speaking about multibit fonts ...
>
> I was trying to add suport for subpixel fonts. I think the easier way to
> implement that is to make memimagedraw to apply the channels of the "mask"
> image (if it is not monocrhome) to the appropriate channels of the "src"
> image. Currently it generates a greyscale image and applies it to every
> channel.
>
> Is that change going to break anything? Is it a good idea at all?
>
> Thanks,
> Lucho
>
> On Sat, Oct 25, 2003 at 07:35:21PM -0400, Russ Cox said:
> > > I've converted Bitstream Vera to Plan 9 format:
> > > http://www.cse.psu.edu/~schwartz/vera.tar.bz2
> > >
> > > I'm not sure what dpi ttf2subf is using, but I selected a handful of
> > > point sizes, hopefully good ones.
> >
> > That's a nice font. Does it look good in 1-bit depth?
> > (I find the multibit fonts too fuzzy for every-day use.
> > I think my eyes keep trying to focus better.)
> >
> > Russ
next prev parent reply other threads:[~2003-10-26 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 3:57 Scott Schwartz
2003-10-25 14:06 ` Latchesar Ionkov
2003-10-25 23:35 ` Russ Cox
2003-10-26 0:02 ` Scott Schwartz
2003-10-26 14:05 ` Latchesar Ionkov
2003-10-26 15:11 ` Russ Cox
2003-10-26 15:57 ` C H Forsyth
2003-10-26 17:48 ` Latchesar Ionkov [this message]
2003-10-26 21:06 ` [9fans] sub-pixel Charles Forsyth
2004-02-24 17:19 [9fans] bitstream vera 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=20031026174839.GA21901@ionkov.net \
--to=lucho@ionkov.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).