ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: updating ConTeXt to latest on openbsd-current Q #2
Date: Mon, 06 Mar 2006 22:57:57 +0100	[thread overview]
Message-ID: <440CB065.8030907@elvenkind.com> (raw)
In-Reply-To: <20060306213300.GO21773@obiit.org>

Hi there!

frantisek holop wrote:
> my second question, is more like asking for pointers...
> 
> where can i read more about fmtutil, and how come that
> context does not use it when (i assume) pdftex does?

The following comes from a thread in december about this same
issue. The full thread is here:

http://archive.contextgarden.net/message/20051213.100910.f7bb2779.en.html

Posted by Taco Hoekwater (hey, that's me!):
-------
Here's what happened. In the "really old" days,
formats ended with .fmt, like plain.fmt.

When etex and omega came around, they identified themselves by having
e.g. plain.efmt (note the extra "e"), so that they could coexist
happily.

However, this cluttered the build system quite a bit, so recently it
was decided to drop the extra characters. At that time, it was
understood that there would be an extra subdirectory below texmf/web2c
to differentiate between the different engines (at least, that is what
Hans and I gathered from the discussion). So you would have, e.g.
"web2c/pdfetex/cont-en.fmt" as well as "web2c/omega/cont-en.fmt".

But it turned out that since LaTeX has separate names for the
different formats anyway (Lambda etc.), ConTeXt was the only client
of this new feature, and Thomas Esser decided that it was not worth
the effort to support these extra directories.

However, for ConText it would be very, very unwieldy to have
cont-pdfetex-en.fmt, cont-xetex-en.fmt, cont-aleph-en.fmt etc., each six
or seven times. And because context is always called through texexec,
the latest texexec's implement this engine subdirectory functionality
for you.

Finally, what goes wrong: unless you either delete the teTeX-supplied
context formats or change texmf.cnf, the old formats will be found first
by kpathsea.
------------

  reply	other threads:[~2006-03-06 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 21:33 frantisek holop
2006-03-06 21:57 ` Taco Hoekwater [this message]
2006-03-06 23:29   ` frantisek holop
2006-03-07  8:31     ` Taco Hoekwater
2006-03-06 22:21 ` Willi Egger

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=440CB065.8030907@elvenkind.com \
    --to=taco@elvenkind.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).