From: Thomas Esser <te@dbs.uni-hannover.de>
Cc: ConTeXt users <ntg-context@ntg.nl>,
tetex-pretest <tetex-pretest@dbs.uni-hannover.de>
Subject: Re: Update ConTeXt 2004-12-06 for teTeX 2.99.4-beta: map files
Date: Tue, 7 Dec 2004 21:29:04 +0100 [thread overview]
Message-ID: <20041207202904.GA30279@dbs.uni-hannover.de> (raw)
In-Reply-To: <e5d3f265041207121076761492@mail.gmail.com>
> 1. In ConTeXt all map files are in fonts/map/pdftex/context/*.map
That's the wrong location. There is nothing pdftex specific in these
files, so the "syntax" is dvips, not pdftex. I have told Hans about it.
The level below fonts/map is "syntax" according to TDS 1.1.
> So my question is how I could update ConTeXt safely ? Which directory
> structure I have to follow ? teTeX will continue to work if map files
> installed in ConTeXt's structure ?
The TDS tells us where to put those files and even though Hans does not
care much about dvips, I suggest that he moves his files. Some files
don't have a proper newline in the end, so they are not even proper
text files. Thers is no non-whitespace difference between teTeX's files
in fonts/map/dvips/context and cont-tmf's fonts/map/pdftex/context,
so you can just ignore the files from cont-tmf.
So, I suggest that you
unpack cont-tmf.zip in a temp directory
rm -rf fonts/map/pdftex/context
rm -rf tex/latex
cp -a * /to/your/texmf-dist
(teTeX has aliases for the files that context distributes in tex/latex,
so we don't need these files).
Thomas
next prev parent reply other threads:[~2004-12-07 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 20:10 VnPenguin
2004-12-07 20:29 ` Thomas Esser [this message]
2004-12-07 20:48 ` VnPenguin
2004-12-07 20:53 ` Thomas Esser
2004-12-08 20:48 ` Hans Hagen
2004-12-09 18:57 ` [NTG-context] " Thomas Esser
2004-12-09 22:33 ` h h extern
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=20041207202904.GA30279@dbs.uni-hannover.de \
--to=te@dbs.uni-hannover.de \
--cc=ntg-context@ntg.nl \
--cc=tetex-pretest@dbs.uni-hannover.de \
/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).