ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: Context <ntg-context@ntg.nl>
Subject: Re: MetaPost inclusion - change?
Date: Thu, 02 Nov 2000 12:07:48 +0100	[thread overview]
Message-ID: <3.0.6.32.20001102120748.014ba100@pop.wxs.nl> (raw)
In-Reply-To: <3A011DF4.7960B35E@econ.muni.cz>

At 08:55 AM 11/2/00 +0100, Michal Kvasnicka wrote:
>Good morning.
>
>I found some (possible) change between the last version of ConTeXt
>I used and the current one (ver: 2000.9.21).
>
>When I have some jobname (let's say bum.tex) and the same MetaPost
>source (let's say bum.mp), ConTeXt is not willing to include MetaPost
>figures (e. g. bum.1). It complaines:
>    figures        : suffix bum by figure dvi is not handled

should be           : suffix dvi by figure bum is not handled

>    figures        : figure bum can not be found
>Is it bug or a feature? What does mean the error message?

Now, the message is somewhat confusing (i'll change it) and has to do with
the fact that a figure file with the same name as the jobname is very
dangerous, especially for some suffixes (tex, pdf), but even for mp, where
a temp file with jobname.<suffix> can be created, so to prevent any
potential problem, context will not support figure names with the jobname.
The second message is there because after disabling, the machinery still
runs so that we get the normal missing figure.  

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


      reply	other threads:[~2000-11-02 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02  7:55 Michal Kvasnicka
2000-11-02 11:07 ` Hans Hagen [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=3.0.6.32.20001102120748.014ba100@pop.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).