From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: Some texexec/MP problems
Date: Wed, 18 Sep 2002 13:52:52 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020918132419.0278df98@server-1> (raw)
In-Reply-To: <20020918115740.531f962d.morawski@gmx.net>
At 11:57 AM 9/18/2002 +0200, Jens-Uwe Morawski wrote:
>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.
ok, i'll add an newline
>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?
not that i know, btw, no .pdf is needed after myfile.pdf; are you sure that
texexec.pdf is not kept open by some app?
>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?
hm, the familiar sort by name of number problem;
i'll send you some files to test
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
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
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
prev parent reply other threads:[~2002-09-18 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 9:57 Jens-Uwe Morawski
2002-09-18 11:52 ` 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=5.1.0.14.1.20020918132419.0278df98@server-1 \
--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).