ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: can I upgrade yet?
Date: Tue, 11 Jan 2005 18:02:36 +0100	[thread overview]
Message-ID: <41E406AC.6040908@wxs.nl> (raw)
In-Reply-To: <41E3F62D.8050407@iname.com>

Gary wrote:
> Hans Hagen wrote:
> 
>> Gary wrote:
> 
> 
> [...]
> 
>>> 3.) Is there some other way besides my traditional method of 
>>> unzipping cont-tmf.zip file into /localtexmf ?  Do I need to rebuild 
>>> the file system?
>>
>>
>>
>> no, you can unzip, run "textools --fixtexmf --force", regenerate the 
>> database, and cross your fingers
> 
> 
> ok, here's what I did:
> 
> 1. Upgraded MikTeX
> 2. Unzipped the latest cont-tmf.zip (from pragma-ade.com)  into 
> c:\tex\localtexmf
> 3. ran "textools --fixtexmf --force"  (what does that do?)

if needed it moves you rlocal enc/map files to their new locations, not needed 
if you have no commercial fonts

> 4. checked c:\tex\localtex\context\config.  texexec.ini is newer than 
> texexec.rme, so I left it alone.
> 5. ran "texexec --make en nl"  (do I need "nl"? I'm exclusively 
> English.  I guess it can't hurt.)
> 6.  noticed that cont-en.efmt was automatically relocated to 
> c:\tex\localtex\miktex\fmt but cont-nl was not.
> 7. moved cont-nl.efmt to c:\tex\localtex\miktex\fmt
> 8.  renamed them both to *.fmt  (per a note in the contextgarden wiki.   
> Is this necessary?)
> 9.  ran "texexec --make metafun"
> 10.  moved metefun.mem to c:\tex\localtex\miktex\mem
> 11. ran "mktexlsr"

texexec --make  (--all if you want all patterns)

is normally enough, apart from moving the fmt and mem files (aren't those put at 
the right spot by miktex?)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2005-01-11 17:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 16:44 next version Hans Hagen
2005-01-06 16:54 ` Nikolai Weibull
2005-01-06 17:32   ` Hans Hagen
2005-01-07 22:06     ` Adam Lindsay
2005-01-09 20:19       ` h h extern
2005-01-10 17:12         ` Adam Lindsay
2005-01-06 16:58 ` Adam Lindsay
2005-01-07 21:09 ` Hans van der Meer
2005-01-07 21:38   ` Tobias Burnus
2005-01-07 21:49   ` Peter Münster
2005-01-08 10:23     ` m-letter.tex (first page, input file) Rob Ermers
2005-01-09 20:22   ` next version h h extern
2005-01-11 14:20 ` can I upgrade yet? Gary
2005-01-11 14:33   ` Hans Hagen
2005-01-11 14:45     ` Gary
2005-01-11 17:00       ` Hans Hagen
2005-01-11 15:52     ` Gary
2005-01-11 17:02       ` Hans Hagen [this message]
2005-01-12 15:22         ` Gary
2005-01-13 18:48           ` m-letter backslash codes in xml database Rob Ermers
2005-01-14 16:44             ` h h extern
2005-01-15  1:31               ` Rob Ermers
2005-01-15 13:21                 ` Adam Lindsay
2005-01-16 10:12                   ` (resolved) " Rob Ermers
2005-01-16 10:45                     ` Adam Lindsay
2005-01-17 10:03                       ` Hans Hagen
2005-01-11 14:43   ` can I upgrade yet? Matthew Huggett

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=41E406AC.6040908@wxs.nl \
    --to=pragma@wxs.nl \
    --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).