9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] problem using a vera font in rio
Date: Thu, 25 Feb 2010 18:11:15 -0800	[thread overview]
Message-ID: <dd6fe68a1002251811le865ef4k4a42690b3f8d1653@mail.gmail.com> (raw)
In-Reply-To: <14ec7b181002251536jc123c89vf5d5814144ddd9ac@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

On Thu, Feb 25, 2010 at 3:36 PM, andrey mirtchovski
<mirtchovski@gmail.com> wrote:
>> an alternative is to use the p9p fontsrv to generate fonts.
>> here's acme with Calibri on OS X.
>
> that may be a good solution for p9p's acme. i admit i hadn't looked at it.

it could be a general solution - fontsrv just spits out
ordinary font files that you could use on plan 9.

>> the glyphs are a little more washed out than in your
>> screen shot, but maybe it's easier to fix that than to
>> keep working on ttf2subf.  maybe not, but either way
>> it's there.
>
> 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.

> what font works well for go programming in acme nowadays? what do you
> use? (doesn't matter if it's variable width)

i still use /lib/font/bit/lucsans/euro.8.font
and it works great.  i just can't get used to how fuzzy
and grey the supposedly "better" fonts are.
when you put them side by side there's just no
comparison for contrast and readability.
the attached picture is a 9term and an OS X terminal
using lucm/unicode.9.font and Lucida Sans Typewriter 15pt,
respectively.  it's easy to forget that the fuzzy fonts are
so fuzzy until you see a side by side comparison.

russ

[-- Attachment #2: Picture 2.png --]
[-- Type: image/png, Size: 126369 bytes --]

  reply	other threads:[~2010-02-26  2:11 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 [this message]
2010-02-26  2:43                         ` erik quanstrom
2010-02-26  2:53                           ` Ethan Grammatikidis
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=dd6fe68a1002251811le865ef4k4a42690b3f8d1653@mail.gmail.com \
    --to=rsc@swtch.com \
    --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).