9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Thinking of getting Helvetica Black, how to add to troff?
Date: Tue, 27 Nov 2007 10:56:07 -0500	[thread overview]
Message-ID: <20071127155608.6C2541E8C22@holo.morphisms.net> (raw)
In-Reply-To: <4485A76F-F022-4FCA-9727-9F8A9C29AE8F@mac.com>

> Hello. I'm thinking of getting the Helvetica Black font (http:// 
> www.linotype.com/12565/helveticablack-font.html? 
> PHPSESSID=fe724d529f3cedd385a9625bf2e87340#format) for troff. What  
> format should I get it in and how do I install it as HK in both troff  
> and lp? Thanks.

Lp is easy: copy each Type 1 font file to /sys/lib/postscript/font/Name
where Name is the exact PostScript name of the font (e.g., Helvetica-Black,
but you'll have to double-check).

Troff is a bit harder.  You'll need to convert the AFM font metrics into
a form that troff can understand.  http://swtch.com/usr/local/plan9/dist/troff
contains the programs I used to convert DejaVu for the plan9port distribution.
I think I wrote those programs.  I don't know if there are more official ones.
The shell script there uses OpenForge (a Unix font program) to convert TTF
and SFD files into Type 1, if you don't have Type 1 already.  Read the script
before blindly running it.

You want to use that to generate font files in /sys/lib/troff/font/devutf.
If you want the font to be named HK, then use HK.
Notice that you don't have to use a two-letter name here, and HK 
is already taken for Helvetica-LightOblique, so you might be
better off using Helvetica-Black as the file name.
Then you can say

	.fp 1 HK Helvetica-Black

in your troff document to install Helvetica-Black as \f1 and \f(HK.

Russ


      reply	other threads:[~2007-11-27 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24 21:28 Pietro Gagliardi
2007-11-27 15:56 ` Russ Cox [this message]

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=20071127155608.6C2541E8C22@holo.morphisms.net \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /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).