From: Neville Dean <nd1@artemis.anglia.ac.uk>
Cc: ntg-context@ntg.nl
Subject: Re: pdfetex font warnings
Date: Wed, 2 Feb 2000 12:16:02 +0000 (GMT) [thread overview]
Message-ID: <Pine.OSF.3.91.1000202120717.10774J-100000@artemis.anglia.ac.uk> (raw)
In-Reply-To: <199912242237.XAA05565@thucydides.nlr.nl>
Michael,
I too had recently installed Lucida Bright type 1 fonts and had similar
(though not identical problems) to yourself as regards pdfetex not being
able to find the Lucida fonts when producing pdf output. (Although
there's no problem with producing dvi output since that only requires the
tfm files.) Presumably there must be some way of telling pdfetex that the
Lucida fonts are type 1 rather than pk.
Unfortunately, I do not recall seeing any response to your question on the
mailing list. I would be very grateful to learn what, if anything, was
the advice given.
Cheers
Neville
---------------------------------
On Fri, 24 Dec 1999 guravage@nlr.nl wrote:
>
> I recently installed a set of type1 Lucida bright fonts; after which I needed
> to inch several context settings in texmf.cnf higher to get around a "TeX
> capacity exceeded" problem. There are no fatal errors now, but an examination
> of the log file shows that pdfetex is not satisfied:
>
> Warning: pdfetex (file lbr): Font lbr at 864 not found
> Warning: pdfetex (file lbr): Font lbr at 1244 not found
> Warning: pdfetex (file lbr): Font lbr at 720 not found
>
> One consequence is that acroread complains that it, "Could
> not find a font in the Resources dictionary." when it tries to opens the
> resulting pdf file.
>
> After tweaking texmf.cnf, I made new context formates by running "texexec
> --make." After installing the latest pdftex, I made new pdftex.fmt and
> pdflatex.fmt files by running "pdftex -ini pdftex.ini" and "pdftex -ini
> pdflatex" respectively. I would appreciate it very much if someone could tell
> me how to tell pdfetex how and where to find the new Lucida Bright fonts.
>
> Cheers,
>
> Michael Guravage
>
> --
> Michael A. Guravage Email: guravage@nlr.nl
> National Aerospace Laboratory Phone: +31 (0)20 511 3695
> P.O. Box 90502, 1006 BM, Fax: +31 (0)20 511 3210
> Amsterdam, The Netherlands URL: <http://www.nlr.nl>
>
>
>
>
prev parent reply other threads:[~2000-02-02 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-24 22:37 guravage
2000-02-02 12:16 ` Neville Dean [this message]
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=Pine.OSF.3.91.1000202120717.10774J-100000@artemis.anglia.ac.uk \
--to=nd1@artemis.anglia.ac.uk \
--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).