From: andrey mirtchovski <mirtchovski@gmail.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 16:36:38 -0700 [thread overview]
Message-ID: <14ec7b181002251536jc123c89vf5d5814144ddd9ac@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a1002251508u1b9fe8dt5475d18511680a93@mail.gmail.com>
> 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.
> 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?
what font works well for go programming in acme nowadays? what do you
use? (doesn't matter if it's variable width)
next prev parent reply other threads:[~2010-02-25 23:36 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 [this message]
2010-02-26 2:11 ` Russ Cox
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=14ec7b181002251536jc123c89vf5d5814144ddd9ac@mail.gmail.com \
--to=mirtchovski@gmail.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).