ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Denis B. Roegel" <Denis.Roegel@loria.fr>
Cc: Denis.Roegel@loria.fr (Denis B. Roegel),
	ntg-context@ntg.nl, roegel@lorraine.loria.fr (Denis B. Roegel)
Subject: Re: problem with new beta
Date: Wed, 14 Mar 2001 20:25:43 +0100 (MET)	[thread overview]
Message-ID: <200103141925.UAA23871@bar.loria.fr> (raw)
In-Reply-To: <3.0.6.32.20010314171938.00b1e350@server-1> from "Hans Hagen" at Mar 14, 2001 05:19:38 PM

`Hans Hagen' wrote
>   
>   At 05:07 PM 3/14/01 +0100, Denis B. Roegel wrote:
>   >Hello,
>   >
>   >I have installed the new beta and ran it on an old file
>   
>   >ConTeXt  ver: 2000.10.22  fmt: 2000.10.26  int: english  mes: english
>    
>   seems like you run an old format with new files  

Right. That's what happens when you have six different english 
context formats around (two in the standard texmf tree, two in
the texmlocal tree (from previous context updates), 
two on my own account...). I was also confused
by the extensions of the formats. Can you confirm that

  texexec test.tex

uses cont-en.fmt and that

  texexec --pdf test.tex

uses cont-en.efmt and that therefore both are necessary?

I first created the formats the old way, with initex cont-en.ini,
but this would only create cont-en.fmt. I didn't call pdfetex -ini.
And fmtutil --byfmt cont-en would only create cont-en.efmt. 
Why doesn't fmtutil --byfmt cont-en create the two needed formats?

Thanks,

Denis


  reply	other threads:[~2001-03-14 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-14 16:07 Denis B. Roegel
2001-03-14 16:19 ` Hans Hagen
2001-03-14 19:25   ` Denis B. Roegel [this message]
2001-03-15  9:44     ` Hans Hagen
2001-03-14 21:32   ` H. Ramm

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=200103141925.UAA23871@bar.loria.fr \
    --to=denis.roegel@loria.fr \
    --cc=ntg-context@ntg.nl \
    --cc=roegel@lorraine.loria.fr \
    /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).