* Some texexec/MP problems
@ 2002-09-18 9:57 Jens-Uwe Morawski
2002-09-18 11:52 ` Hans Hagen
0 siblings, 1 reply; 2+ messages in thread
From: Jens-Uwe Morawski @ 2002-09-18 9:57 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Some texexec/MP problems
2002-09-18 9:57 Some texexec/MP problems Jens-Uwe Morawski
@ 2002-09-18 11:52 ` Hans Hagen
0 siblings, 0 replies; 2+ messages in thread
From: Hans Hagen @ 2002-09-18 11:52 UTC (permalink / raw)
Cc: ConTeXt
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
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-09-18 11:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-18 9:57 Some texexec/MP problems Jens-Uwe Morawski
2002-09-18 11:52 ` Hans Hagen
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).