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