9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] problem using a vera font in rio
Date: Fri, 26 Feb 2010 02:53:13 +0000	[thread overview]
Message-ID: <7270F240-E0F0-406D-8FB6-52072E23F455@fastmail.fm> (raw)
In-Reply-To: <372505d10503442e41069b7ff901c512@ladd.quanstro.net>


On 26 Feb 2010, at 02:43, erik quanstrom wrote:

>> it could be a general solution - fontsrv just spits out
>> ordinary font files that you could use on plan 9.
>
> ttf2subf is only about 150 lines of code, once liberated from
> libfreetype.
>
>>> I am curious why the difference in rendering. in your screenshot
>>> 't',
>>> 'f' and 'g' look especially blurry. subpixel rendering?
>>
>> i don't know.  it's not libfreetype.  fontsrv asks the OS X
>> graphics code to render each glyph into a box and then
>> concatenates the boxes to make the subfont.
>> all the text was noticeably lighter (more grey)
>> than in your screen shot when i put them side by side.
>
> this is due to apple's algorithm for rendering glyphs.
> with freetype, if you get a purely vertical or horizontal
> stroke that is pixel-aligned, then you get no grey fuzz.
> with apple's algorithm, you will get grey fuzz.  overall,
> the color density is more even with the apple algorithm,
> but it results in many more grey pixels.  you can use the
> built-in screen magnifier to see this.

I find Apple's easier to read, curiously enough. Perhaps those who
don't could use fontsrv from an X11 build of p9p.

>
> i tend to like subpixel rendering, even the fuzz problem.
> (i don't have an opinion on apple's algorithm.  i don't have one.)
> this is because i use fonts small enough that the fuzz is
> hard to see and a non antialised font looks poor.  the
> font i use (/lib/font/bit/cyberbit/mod14.font) is about the
> same pitch as /lib/font/bit/lucidasans/unicode.7.font.
>
> maybe i just need better contacts :-).
>
> - erik
>




  reply	other threads:[~2010-02-26  2:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 11:21 Rudolf Sykora
2010-02-14 18:34 ` erik quanstrom
2010-02-14 19:09   ` Rudolf Sykora
2010-02-14 19:52     ` Federico G. Benavento
2010-02-15  4:15     ` erik quanstrom
2010-02-16  3:39       ` Russ Cox
2010-02-16  4:35         ` erik quanstrom
2010-02-16  4:57           ` andrey mirtchovski
2010-02-16  5:07             ` erik quanstrom
2010-02-16  6:58             ` Skip Tavakkolian
2010-02-17 16:31             ` Ethan Grammatikidis
2010-02-17 16:44               ` andrey mirtchovski
2010-02-25 21:45                 ` andrey mirtchovski
2010-02-25 22:01                   ` erik quanstrom
2010-02-25 23:08                   ` Russ Cox
2010-02-25 23:36                     ` andrey mirtchovski
2010-02-26  2:11                       ` Russ Cox
2010-02-26  2:43                         ` erik quanstrom
2010-02-26  2:53                           ` Ethan Grammatikidis [this message]
2010-03-02 16:49                             ` [9fans] int errno / errno.h patch EBo
2010-03-03  5:15                               ` Russ Cox
2010-03-03 14:02                                 ` EBo
2010-03-03 17:59                                   ` Charles Forsyth
2010-02-26 14:01                           ` [9fans] problem using a vera font in rio matt
2010-02-26 16:37                             ` david bulkow
2010-03-08 18:42                           ` Albert Skye

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=7270F240-E0F0-406D-8FB6-52072E23F455@fastmail.fm \
    --to=eekee57@fastmail.fm \
    --cc=9fans@9fans.net \
    /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).