ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: Taco Hoekwater <taco.hoekwater@wkap.nl>
Subject: Re: switching fonts
Date: Sun, 21 Jun 1998 20:19:10 +0200	[thread overview]
Message-ID: <358D4E9E.BC0911F4@wxs.nl> (raw)

PS: Taco, one for you. 

Berend de Boer wrote:

> Hai All,
> 
> How do I switch from cmr to postscript within context without getting .tfm
> errors?
> 
> It seems context refers to a nonstandard (at least compared with latex's
> \usepackage{times} command) kind of encoding. Is there a fix or workaround
> available?

Context refers to standard names, while tex users often use karl berry
ones, therefore try:

\stelkorpsin[kb,pos]   % == \setupbodyfont 

(I don't have the CD here, so let me know if you need an update.)

> I have things like ptmr.tfm and ptmbi.tfm and ptmrre.tfm. ConTeXt looks for
> things like 7ptrmtf.

No! ... bf=tib at 10pt ... is internally assigned to 10ptrmbf so 7ptrmtf
is not the font name. Context searches for tib.tfm. 

The latest release does things more clever: 

  bf=TimesBold at 7pt 

where 

  TimesBold is mapped on tib or something ptmbi   

Taco will work out some decent ps math support, and also will provide
asuitable set of decent tfm's (we strongly suggest texnansi encoding:
simple and good). 

Hans 

-----------------------------------------------------------------
                                              Hans Hagen | PRAGMA
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@wxs.nl
-----------------------------------------------------------------


             reply	other threads:[~1998-06-21 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-21 18:19 Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-06-20 12:01 Berend de Boer

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=358D4E9E.BC0911F4@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=taco.hoekwater@wkap.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).