ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: ConTeXt 2006.04.27 released
Date: Thu, 27 Apr 2006 22:10:31 +0100	[thread overview]
Message-ID: <E1FZDkt-0000EZ-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Thu, 27 Apr 2006 13:34:54 PDT." <e2rabe$vh2$1@sea.gmane.org>

> context : ver: 2006.04.27 15:59
> cont-en : ver: 2006.04.06 23:00  fmt: 2006.4.7  mes: english
> cont-nl : ver: 2006.04.06 23:00  fmt: 2006.4.7  mes: dutch
> 
> Shouldn't cont-en and -nl be 2006.04.27 as well?

I think that, although the format files were probably remade, they are
not in the location where texexec finds them, so it is finding the
previous set.

If that's the case, a short-term hack is to figure out where texexec
put the new formats and then copy them over the old formats.  However,
that means doing so every time you upgrade, and it's better to let
computers deal with such matters automatically.

Not sure if you are using Unix or Linux, but if you are, these
directions may be useful (even if it's not Debian):
<http://wiki.contextgarden.net/Debian_installation#Steps_to_finish_a_first_context_upgrade>

Or if stupid mail transfer agents break the longish URL above:

<http://wiki.contextgarden.net/Debian_installation>

-Sanjoy

`Never underestimate the evil of which men of power are capable.'
         --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.

  parent reply	other threads:[~2006-04-27 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 19:58 Taco Hoekwater
2006-04-27 20:24 ` Tobias Burnus
2006-04-27 21:33   ` Hans Hagen
2006-04-28 10:56   ` Peter Münster
2006-04-27 20:34 ` Johannes Graumann
2006-04-27 20:57   ` Hans Hagen
2006-04-27 22:16     ` Johannes Graumann
2006-04-27 23:21       ` Sanjoy Mahajan
2006-04-27 21:10   ` Sanjoy Mahajan [this message]
2006-04-27 21:16   ` 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=E1FZDkt-0000EZ-00@skye.ra.phy.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).