ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: mp file not compiling
Date: Wed, 3 May 2006 16:46:58 +0200	[thread overview]
Message-ID: <6faad9f00605030746q1a0d7502wf71361b78adb74c8@mail.gmail.com> (raw)
In-Reply-To: <Pine.WNT.4.63.0605022111580.2232@nqvgln>

On 5/3/06, Aditya Mahajan wrote:
> Hi,
>   Is the mp support for btex...etex broken in the latest context
> (ConTeXt  ver: 2006.04.27 15:59) The following does not compile,
>
> \starttext
> \startMPpage
>    label(btex This is a test etex, origin) ;
> \stopMPpage
> \stoptext
>
> I get an error
>
> ! Unable to make mpx file.
> l.123 label(btex
>                    This is a test etex
>
> Even an mp file
>
> beginfig(1)
>    label(btex hello world etex, origin) ;
> endfig
>                                         end;
>
> with texexec --mptex gives the same error message.
>
> Can somebody confirm this? Or is something broken at my end?

First of all:
1. in case you are using windows, update "texmfstart.exe" from
cont-win.zip (you have to do that every now and then)
2. check that "texexec" is a synonym (for example texexec.bat under
windows or an executable) for running "texmfstart [new]texexec"
3. Hans would say that you have to use "textext" instead of btex ... etex


I doubt that this came with the latest distribution. The btex/etex and
textext functionality is  a bit broken anyway: sometimes it works and
sometimes it doesn't. It depends a lot on the system that you use
(MikTeX/tetex/standalone), on texexec that you run (texexec or
newtexexec), how you run it (a batch/shell script with "texmfstart
[new]texexec" or from linux/windows binaries that come with other
distributions than the standalone one).

It might also be that "write18" is set to off, it might be that some
\runMP[TEX]graphic[s]true, \forceMP[TEX]graphic[s]true are set to
false (chech your cont-usr.tex file). (I don't know which variable
does what, but if you try to use an undefined one, TeX will complain
anyway. Check the sources or try to switch on all the possible
combinations of the commands mentioned above.)


Since the topic is already open: Hans, if you find out what is going
on with those input-ed strings, can you please also check what has to
be done to enable "textext" under XeTeX? The more combinations I try,
the more I break the system as the whole, so that I even had to
reinstall everything. How does "runtexmpjob" know which TeX engine to
use? Here the labels are processed with pdfTeX instead of being
processed with XeTeX. I also have some problems with defining the
proper font for those labels, but that's another story anyway.

Thanks a lot,
    Mojca

  parent reply	other threads:[~2006-05-03 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03  1:18 Aditya Mahajan
2006-05-03 13:13 ` Peter Rolf
2006-05-03 14:46 ` Mojca Miklavec [this message]
2006-05-03 16:14   ` Aditya Mahajan
2006-05-05  7:33     ` Taco Hoekwater

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=6faad9f00605030746q1a0d7502wf71361b78adb74c8@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).