From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/9306
Path: main.gmane.org!not-for-mail
From: Jens-Uwe Morawski <morawski@gmx.net>
Newsgroups: gmane.comp.tex.context
Subject: Some texexec/MP problems
Date: Wed, 18 Sep 2002 11:57:40 +0200
Sender: owner-ntg-context@let.uu.nl
Message-ID: <20020918115740.531f962d.morawski@gmx.net>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Trace: main.gmane.org 1035399646 2179 80.91.224.250 (23 Oct 2002 19:00:46 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 19:00:46 +0000 (UTC)
Original-To: ConTeXt <ntg-context@ntg.nl>
Xref: main.gmane.org gmane.comp.tex.context:9306
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:9306

Hi,

i have some problems with the MP support of texexec:

1. a MP input that has no line-break or whitespace after the "end"
   results in mptrace.mp in "endend"

   Thus a job 'texexec --mptex myfile.mp' does not
   finish correctly. Maybe texexec should add an additional line-break.

2. many of my MP files include more than 100 figures.
   I use currently

  texexec --pdf --fig=c myfile.[0-9] myfile.[1-9][0-9] myfile.[1-9][0-9][0-9]

   to have all figures in _one_ PDF file. But the result ist always the file
   texexec.pdf. The texexec option --result=myfile.pdf leads to a missing
   myfile.mps. Is this a bug?

3. The strange looking 'myfile.[0-9] myfile.[1-9][0-9] myfile.[1-9][0-9][0-9]'
   is necessary to keep the order of the figures, since normally 'myfile.*'
   expands in a shell to 'myfile.1 myfile.10 myfile.11 ... myfile.2'

   Is it possible to let
    'texexec --pdf --fig=c myfile' expand the file-names correctly itself?

Thanks,
  Jens