ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: skhilji@tampabay.rr.com
Subject: Re: How to use PostScript font
Date: Wed, 18 Aug 2004 15:16:43 -0400	[thread overview]
Message-ID: <672d10671a77.671a77672d10@tampabay.rr.com> (raw)

----- Original Message -----
From: Hans Hagen <pragma@wxs.nl>
Date: Wednesday, August 18, 2004 11:02 am
Subject: Re: [NTG-context] How to use PostScript font

> >  
> >
> [ppl,12pt]
> 
> may work, but nowadays we say: 
> 
> \usentypescript[palatino][\defaultencoding]
> \setupbodyfont[palatino,12pt]

With this:

\setupbodyfont[ppl,12pt]  
\starttext
The quick brown fox jumps over the lazy dog.
\stoptext

I get errors.  I am using Fedora Core 2 with teTex 2.02.  The error messages follow this message.

I also tried:

\usetypescript[palatino][\defaultencoding]
\setupbodyfont[palatino,12pt]

without any luck.

Someone suggsted that I use the actual font names.  So I tried:

\setupbodyfont[uplr8a,12pt]

and it generated an error message something like: 
"bodyfont       : unknown variant uplr8a"



Here are the error messages using [ppl,12pt]:



kpathsea: Running mktexmf ec-uplr8a
! I can't find file `ec-uplr8a'.
<*> ...jfour; mag:=1; nonstopmode; input ec-uplr8a
                                                   
Please type another input file name
! Emergency stop.
<*> ...jfour; mag:=1; nonstopmode; input ec-uplr8a
                                                   
Transcript written on mfput.log.
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input ec-uplr8a' failed.
kpathsea: Appending font creation commands to missfont.log.
 
! Font \*12ptrmtf*=ec-uplr8a at 12.0pt not loadable: Metric (TFM) file not foun
d.
...
...
...
l.2   [ppl,12pt]
                 
?

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

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 19:16 skhilji [this message]
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-24 14:38                     ` Siep Kroonenberg
2004-08-18 19:28 ` Bill McClain
2004-08-18 21:16 ` Matt Gushee
2004-08-19 22:01 ` Patrick Gundlach
  -- strict thread matches above, loose matches on Subject: below --
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
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-18  2:56 skhilji
2004-08-18 15:02 ` Hans Hagen
2004-08-18 16:13   ` Matt Gushee

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=672d10671a77.671a77672d10@tampabay.rr.com \
    --to=skhilji@tampabay.rr.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).