ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Bill McClain <wmcclain@salamander.com>
Cc: NTG-ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: font question
Date: Tue, 19 Feb 2002 10:32:42 -0600	[thread overview]
Message-ID: <3C727E2A.883B224D@salamander.com> (raw)
In-Reply-To: <010a01c1b956$c5381ec0$0400a8c0@arnhem.chello.nl>

Frans Goddijn wrote:
> 
> Hello again,
> 
> since I can now easily compile a simple test file, I tried to add my
> existing own Times font setup with expert set, following the method I'd
> documented from the time that I worked with my home-cooked installation of
> fpTeX and ConTeXt. I copied the relevant files to the directories I would
> expect this setup to find them (for instance, from the former
> \mytex\fonts\type1\fg to \mytex\texmf\tex\fonts\type1\fg et cetera) but it
> is as hard as it is supposed to be ;=}

My only experience is with Type1 fonts and pdftex, but I have found this
to be true:

(1) If the pfb file is under the type1 tree, and...
(2) if the tfm file is under the tfm tree, and...
(3) if both of those files are listed on the same line in pdftex.map (or
other configurable resource), and...
(4) if the filename database has been refreshed with texhash or mktexlsr
since any new files were introduced, and...
(5) if all of the above files can be found with the kpsewhich utility...

...it should work.

If the fonts are found but some effects are missing (small caps,
old-style figures, etc) then some ConTeXt definitions need to be
adjusted.

-Bill


  reply	other threads:[~2002-02-19 16:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 15:04 Frans Goddijn
2002-02-19 16:32 ` Bill McClain [this message]
2002-02-19 17:22   ` Frans Goddijn
2002-02-19 18:31     ` Bill McClain
     [not found]     ` <003701c1b976$6ab1c800$0100a8c0@digitpaint.nl>
2002-02-19 21:27       ` Frans Goddijn
2002-02-20 12:39         ` Bill McClain
2002-02-20 18:47         ` W. Egger
  -- strict thread matches above, loose matches on Subject: below --
2008-02-29 19:42 Font question Marcin Borkowski
2008-02-29 20:54 ` Hans Hagen
2008-02-29 22:31   ` Marcin Borkowski
2008-02-29 22:57     ` Hans Hagen
2008-03-01  0:17       ` Marcin Borkowski
2008-03-01  0:22         ` Idris Samawi Hamid
2008-03-02  8:48           ` Marcin Borkowski
2008-03-02 13:08             ` Mojca Miklavec
2008-03-02 13:20               ` Wolfgang Schuster
2008-03-04 20:58               ` Marcin Borkowski
2008-03-04 21:09                 ` Wolfgang Schuster
2008-03-04 21:49                   ` Marcin Borkowski
2008-03-05  8:40                 ` Hans Hagen
2008-03-04 22:55     ` Marcin Borkowski
2008-03-05  6:55       ` Thomas A. Schmitz
2008-03-05 14:23         ` Marcin Borkowski
2008-03-05  9:17       ` Taco Hoekwater
2008-03-05 14:29         ` Marcin Borkowski
2008-03-11 14:07         ` Marcin Borkowski
2005-12-12 15:32 Font Question Henry Blodgiitt
2005-12-07 22:46 Aditya Mahajan
2005-12-07 23:45 ` Adam Lindsay
2005-12-08  0:05   ` Aditya Mahajan
2005-12-07 23:55 ` Hans Hagen
2001-08-02 17:01 Marco Kuhlmann
2001-08-03 14:01 ` Hans Hagen
2001-08-05 21:02   ` Marco Kuhlmann
2001-08-06  7:42     ` Hans Hagen

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=3C727E2A.883B224D@salamander.com \
    --to=wmcclain@salamander.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).