ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Undefined control sequence \starttypescriptcollection
Date: Wed, 07 Sep 2005 12:31:04 +0200	[thread overview]
Message-ID: <431EC168.6050001@elvenkind.com> (raw)
In-Reply-To: <4A78B8B834217341AA3152A47BB3C447014D58B8@CAPITACAREXCH01.central.ad.capita.co.uk>

Pearson, Mark (Capita Symonds) wrote:
>                 cont-en : ver: 2005.01.31  fmt: 2005.9.6  mes: english
>                 cont-nl : ver: 2005.01.31  fmt: 2005.9.6  mes: dutch
> 
>          total run time : 4 seconds
> 
> -------------------------- END OUTPUT --------------------------
> 
> Any ideas what could be wrong?

The old format file is used instead of the new one.
Delete the old one; run mktexlsr; try again.

Cheers, Taco

      parent reply	other threads:[~2005-09-07 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 10:14 Pearson, Mark (Capita Symonds)
2005-09-07 10:21 ` luigi.scarso
2005-09-07 10:31 ` Taco Hoekwater [this message]

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=431EC168.6050001@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).