ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: Miktex, Metapost and \loadfontfilesoncetrue
Date: Tue, 4 Apr 2006 02:49:32 +0200	[thread overview]
Message-ID: <6faad9f00604031749o63bc9bd5ic02e48c0090cdf29@mail.gmail.com> (raw)
In-Reply-To: <442CD002.4020300@elvenkind.com>

On 3/28/06, WN wrote:
> Hi,
>
> I am using Miktex (latest updated version) and the latest
> Context on WindowsXP (write18 enabled).
>
> This is what happens :
>
> 1) First run of texexec gives me
> ! Undefined control sequence
> l 1 \global \loadfontfileoncetrue

On 3/31/06, Taco Hoekwater wrote:
> For the original problem, I guess Mojca is closest to the
> actual problem. She herself has a continuing fight with
> btex/etex and textext(). If you can, you should try to post
> a 'recipe': make a minimal example in a clean directory,
> post that here along with what commands to run, and all
> of the results (logs, temp files) you get.

The perl script (texexec.pl) has some difficulties (sometimes the
problem with wrong format loding appears and sometimes not), but since
the ruby script is supposed to replace it anyway it doesn't really
make sense to lose time fixing old stuff.

Hans has just fixed the behaviour of newtexexec.rb, so I would suggest
you to do the following:

1. create a file texexec.bat with the following content:
    texmfstart newtexexec.rb %*
and place that file to some arbitrary folder in PATH (but has to be in
front of MikTeX in PATH). So that after you type "texexec",
"texmfstart newtexexec.rb" will be executed.
You might have to download "texmfstart" if you don't have it yet
(cont-win.zip from pragma website, simply drop it into MikTeX bin
folder for example).

You may also try to politely ask the maintainer of MikTeX to include
the texmfstart.exe into MikTeX by default (the more users ask for it,
the more likely will be that he'll do that).

2. wait until Hans uploads the new beta & extract the content from
cont-tfm.zip into the MikTeX tree (to the proper place); I guess that
it should be enough if you only replace the content of /scripts/ruby/*
(Theoretically you can also wait for update in MikTeX, but that would
definitely take much longer.)


Then cross your fingers and try to compile your file again!

Mojca

  reply	other threads:[~2006-04-04  0:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 23:22 WN
2006-03-28  8:13 ` Hans Hagen
2006-03-28 12:51   ` Mojca Miklavec
2006-03-30 15:07   ` WN
2006-03-30 19:23     ` Hans Hagen
2006-03-31  6:45       ` Taco Hoekwater
2006-04-04  0:49         ` Mojca Miklavec [this message]
2006-04-04 16:30           ` WN

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=6faad9f00604031749o63bc9bd5ic02e48c0090cdf29@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.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).