From: "Mathieu Lonjaret" <mathieu.lonjaret@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] anonymous pro -- a programming font
Date: Fri, 10 Sep 2010 18:16:35 +0200 [thread overview]
Message-ID: <7d0488387068c12f886ef914c7997677@iram.fr> (raw)
In-Reply-To: <AANLkTiktHQA5KZbT9ibs-YoCG+G4VNft+yP0DCnm-MtK@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 134 bytes --]
Hello,
how about on p9p acme, do I have to convert them in any way before I
can use them there? if yes, how?
Cheers,
Mathieu
[-- Attachment #2: Type: message/rfc822, Size: 5360 bytes --]
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] anonymous pro -- a programming font
Date: Thu, 9 Sep 2010 10:22:15 -0400
Message-ID: <AANLkTiktHQA5KZbT9ibs-YoCG+G4VNft+yP0DCnm-MtK@mail.gmail.com>
On Wed, Sep 8, 2010 at 3:56 PM, andrey mirtchovski
<mirtchovski@gmail.com> wrote:
> seems to fit nicely with acme and rio. looks better antialiased than
> not. let me know if you want it in size 14, of use ttf2subf yourselves
> if you like it:
>
> http://www.ms-studio.com/FontSales/anonymouspro.html
>
> not a terribly good unicode coverage.
>
I tried rolling my own, but ran into problems:
cpu% ttf2subf -m antialias -r rgb 'Anonymous Pro.ttf' anon 12
FT_Glyph_Transform: status=18
Sizes 8 and 9 work, as does 14, but 10-13 give that same error. 14 is
almost small enough to use, but I'd prefer something around 12, I
think.
John
--
"With MPI, familiarity breeds contempt. Contempt and nausea. Contempt,
nausea, and fear. Contempt, nausea, fear, and .." -- Ron Minnich
next prev parent reply other threads:[~2010-09-10 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 19:56 andrey mirtchovski
2010-09-08 21:41 ` David Leimbach
2010-09-09 13:52 ` Gabriel Díaz López de la Llave
2010-09-09 14:22 ` John Floren
2010-09-10 16:16 ` Mathieu Lonjaret [this message]
2010-09-10 16:25 ` andrey mirtchovski
2010-09-10 16:42 ` Mathieu Lonjaret
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=7d0488387068c12f886ef914c7997677@iram.fr \
--to=mathieu.lonjaret@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).