From: "George N. White III" <WhiteG@mar.dfo-mpo.gc.ca>
Cc: Hans Hagen <pragma@wxs.nl>, ConTeXt mailinglist <ntg-context@ntg.nl>
Subject: Re: latest context problems
Date: Sat, 17 Nov 2001 09:49:53 -0400 (AST) [thread overview]
Message-ID: <Pine.GSO.4.40.0111170930180.24669-100000@emerald.bio.dfo.ca> (raw)
In-Reply-To: <877ksprdn4.fsf@dellius.nederware.nl>
On Sat, 17 Nov 2001, Berend de Boer wrote:
> Hans Hagen <pragma@wxs.nl> writes:
>
> > At 05:22 PM 11/16/2001 +0100, Berend de Boer wrote:
> > >Times-Roman'.
> >
> > so, it searches for times roman.
> >
> > maybe you shoudl say: \setupencoding[ec] so that the berrry ec names are loaded
> >
> > [or \setupencoding[texnansi]; you need such a default in cont-sys.tex]
>
> Things like that don't help at all.
>
> My test file:
>
> -----------------
> % interface=en
>
> \usetypescript [map] [all]
>
> \setupencoding[texnansi]
>
> \setupbodyfont
> [ber,pos]
>
> \starttext
>
> test.
>
> \stoptext
> ------------------
>
>
> In the log you see that it complains about original-ams-cmr.map. That
> file is located in pdftex/config. kpsewhich cannot found it, i.e:
>
> # kpsewhich original-ams-cmr.map
>
> returns nothing. Should it? It seems to look in the pdftex/config
> directory, but does not find a match.
It shouldn't find a match:
$ kpsewhich --show-path=map
will not have the pdftex/config directory, but on my system pdfetex
is able to find the .map files in pdftex/config. It would be useful
to know what path is used to find these files -- maybe TEXPSHEADERS?
> Lots of other map files do not exist on my system like
> texnansi-urw-courier.map. Should they?
You need to create them using texfont.pl
> texfont.pl doesn't run on my system, complains about unknown tex
> root. Is texfont.pl necessary for the plain old postscript fonts?
I edited texfont.pl to set the fontroot path.
Look at context/data/type-tmf.dat. I wasn't able to get the
batch mode working, so I ran texfont.pl manually (see my earlier
posting for the ksh script), which led me to find a couple bugs
in texfont.pl. This will configure your system to use the URW
fonts from ghostscrpt. One note: my teTeX (from Mandrake 7.1)
had older versions of the URW fonts, so I started my script
by copying (or was it linking) to the current ghostscript fonts.
Now that texfont.pl seems to be working via the command line,
I still can't run the batch file. I get:
processing aborted : unknown subpath ../fonts/afm/public/antp
and so on for each font collection. I tried running texfont
from different directories and got the same result.
--
George N. White III <gnw3@acm.org> Bedford Institute of Oceanography
next prev parent reply other threads:[~2001-11-17 13:49 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 [this message]
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
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=Pine.GSO.4.40.0111170930180.24669-100000@emerald.bio.dfo.ca \
--to=whiteg@mar.dfo-mpo.gc.ca \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).