From: Berend de Boer <berend@pobox.com>
Cc: ConTeXt mailinglist <ntg-context@ntg.nl>
Subject: Re: latest context problems
Date: 16 Nov 2001 15:46:14 +0100 [thread overview]
Message-ID: <87herurcy1.fsf@dellius.nederware.nl> (raw)
In-Reply-To: <5.1.0.14.1.20011116141503.02f27100@server-1>
Hans Hagen <pragma@wxs.nl> writes:
> Because multiple conflicting encoding need to be supported, and
> because one can create instances like slanted or capitalized locally,
> from now on we use the more verbose names
>
> texnansi-blabla
>
> and alike [see mtexfont.pdf and mfonts.pdf]
>
> This also means that ber does not make much sense now.
I get lots of msgs like:
pdftex : needs map file: original-ams-cmr.map
pdftex : needs map file: original-ams-euler.map
pdftex : needs map file: original-ams-logo.map
pdftex : needs map file: 8r-adobe-utopia.map
pdftex : needs map file: 8r-bit-charter.map
On my system they're in $TEXMF/pdftex/config.
Does this msg mean that pdftex cannot find the file or is this just
some msg that the thing is found and loaded??
--
Groetjes,
Berend. (-:
next prev parent reply other threads:[~2001-11-16 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 12:36 Berend de Boer
2001-11-16 13:17 ` Hans Hagen
2001-11-16 14:15 ` Berend de Boer
2001-11-16 14:45 ` Hans Hagen
2001-11-16 16:22 ` Berend de Boer
2001-11-16 16:52 ` Hans Hagen
2001-11-17 8:43 ` Berend de Boer
2001-11-17 13:49 ` George N. White III
2001-11-17 18:38 ` Olaf Weber
2001-11-19 17:22 ` George N. White III
2001-11-19 18:48 ` Berend de Boer
2001-11-16 14:46 ` Berend de Boer [this message]
2001-11-16 16:44 ` latest context problems / map explanation Hans Hagen
2001-11-16 16:00 ` latest context problems George N. White III
[not found] ` <Pine.GSO.4.40.0111161012440.29583-100000@emerald.bio.dfo.c a>
2001-11-16 17:07 ` Hans Hagen
2001-11-16 18:28 ` Tobias Burnus
2001-11-16 21:05 ` Re[2]: " Giuseppe Bilotta
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=87herurcy1.fsf@dellius.nederware.nl \
--to=berend@pobox.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).