ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matt Gushee <mgushee@havenrock.com>
Subject: Re: How to use PostScript font
Date: Wed, 18 Aug 2004 10:13:53 -0600	[thread overview]
Message-ID: <20040818161353.GA32013@swordfish> (raw)
In-Reply-To: <41236F68.6030905@wxs.nl>

On Wed, Aug 18, 2004 at 05:02:00PM +0200, Hans Hagen wrote:
> skhilji@tampabay.rr.com wrote:
> 
> >I'd like to use the paladino font from urw as my body font (Its the one 
> >used in the MetaFUN manual).  I tried setting:
> >
> >\setupbodyfont[pos,12pt]
> >
> >but it does not work.  What is the name that I should use?
> > 
> >
> [ppl,12pt]
> 
> may work, but nowadays we say: 
> 
> \usentypescript[palatino][\defaultencoding]
> \setupbodyfont[palatino,12pt]

It should be noted (with apologies if this is too obvious) that while
ConTeXt attempts to provide a simple, high-level font handling
interface--and does a very good job, all things considered--it can't do
magic. Either of the above techniques depends on font names that are
defined outside of ConTeXt--by the underlying TeX distribution, by you,
the user, or by a local administrator. So if neither of Hans' solutions
works, you will just have to dig into your TeX font directory (e.g.
/usr/local/share/texmf/fonts if you are on Linux--don't know for
Windows) and find out the exact file names.

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

  reply	other threads:[~2004-08-18 16:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18  2:56 skhilji
2004-08-18 15:02 ` Hans Hagen
2004-08-18 16:13   ` Matt Gushee [this message]
2004-08-18 19:16 skhilji
2004-08-18 19:24 ` Patrick Gundlach
2004-08-19  8:07   ` Hans Hagen
2004-08-19 21:58     ` Patrick Gundlach
2004-08-20  7:55       ` Hans Hagen
2004-08-20 14:09         ` Patrick Gundlach
2004-08-20 15:52           ` Hans Hagen
2004-08-21  8:48             ` Patrick Gundlach
2004-08-22 23:26               ` Hans Hagen Outside
2004-08-24  9:56                 ` Siep Kroonenberg
2004-08-24 10:09                   ` Patrick Gundlach
2004-08-18 19:28 ` Bill McClain
2004-08-18 21:16 ` Matt Gushee
2004-08-19 22:01 ` Patrick Gundlach
2004-08-19 13:02 skhilji
2004-08-19 13:40 ` Mari Voipio
2004-08-20  0:06   ` Nigel King
2004-08-20  0:42     ` Steve Peter
2004-08-20 13:41 skhilji
2004-08-20 13:54 ` Patrick Gundlach
2004-08-20 15:04   ` Hans Hagen
2004-08-20 16:11     ` Patrick Gundlach
2004-08-20 16:27       ` Hans Hagen
2004-08-20 16:40         ` Patrick Gundlach
2004-08-22  5:39           ` Salman Khilji
2004-08-22  6:28             ` Salman Khilji
2004-08-22  6:23               ` Larry Stamm
2004-08-22 18:11                 ` Patrick Gundlach

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=20040818161353.GA32013@swordfish \
    --to=mgushee@havenrock.com \
    --cc=ntg-context@ntg.nl \
    /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).