From: jadamson@partners.org (Joel J. Adamson)
To: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Printing fonts
Date: Thu, 18 Oct 2007 09:14:20 -0400 [thread overview]
Message-ID: <87ir541s5v.fsf@W0053328.mgh.harvard.edu> (raw)
In-Reply-To: <3A2B8026-D31A-4B6B-A3C8-5982593D7B71@Web.DE> (Peter Dyballa's message of "Wed\, 17 Oct 2007 23\:32\:27 +0200")
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> Am 15.10.2007 um 20:43 schrieb Joel J. Adamson:
>
>> Is there a way to specify an arbitrary font (not just the set allowed
>> by ps-font-family) for ps-print-buffer or print-buffer?
>
> Have you tried to customise a bit? The Ps Print group contains the
> Font group, in which you can add more entries to the Ps Font Info
> Database. Then you can select from this new set.
I'll check that out; I presumed that the given choices were _it_ since
those would be all the printer would automatically have.
> This will have one problem: no non-built-in font will be downloaded
>to the PostScript printer. This might make it necessary to use an
>external utility to actually create the PS output.
That's the solution I've found; I created postscript fonts from my
..ttf fonts via ttf2afm and ttf2pt1 in a personal font directory, then
used them with GNU enscript (shell-command-on-region or
shell-command-on-buffer). I used mkafmmap to create an afm map file,
then added that directory to my font path in .enscriptrc. I figured
this out from the enscript FAQ. This works just fine: I can still get
the Emacs "ps-print-buffer" style header, highlighting a la a2ps, and
the fonts I like. This is simpler than redesigning prologues like the
a2ps info recommends.
I only discovered enscript after writing my initial message.
Thanks for responding,
Joel
--
Joel J. Adamson
Biostatistician
Pediatric Psychopharmacology Research Unit
Massachusetts General Hospital
Boston, MA 02114
(617) 643-1432
(303) 880-3109
The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.
next prev parent reply other threads:[~2007-10-18 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:43 Printing fonts Joel J. Adamson
2007-10-17 21:32 ` Peter Dyballa
2007-10-18 13:14 ` Joel J. Adamson [this message]
[not found] ` <mailman.2240.1192713450.18990.help-gnu-emacs@gnu.org>
2007-10-18 18:00 ` Joel J. Adamson
2007-10-19 14:43 ` Giorgos Keramidas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ir541s5v.fsf@W0053328.mgh.harvard.edu \
--to=jadamson@partners.org \
--cc=Peter_Dyballa@Web.DE \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).