On 12-9-2010 3:10, Peter Münster wrote:
On Sun, Sep 12 2010, Hans Hagen wrote:
On 12-9-2010 8:41, Peter Münster wrote:
- or don't ever use "*" in a filename?
in all our projects we normalize to a-z and a dash, otherwise you
always get into problems esp when graphics come from a third party
.
On Sun, Sep 12 2010, Hans Hagen wrote:
> On 12-9-2010 8:41, Peter Münster wrote:
>
> >- or don't ever use "*" in a filename?
>
> in all our projects we normalize to a-z and a dash, otherwise you
> always get into problems esp when graphics come from a third party
> ... multiple spaces in names, f
On 12-9-2010 8:41, Peter Münster wrote:
- or don't ever use "*" in a filename?
in all our projects we normalize to a-z and a dash, otherwise you always
get into problems esp when graphics come from a third party ... multiple
spaces in names, funny case mixing, underscores not seen on low res
On 09/12/2010 08:41 AM, Peter Münster wrote:
So the question is:
- bug?
Bad unstoppable cmd shell expansion
- or don't ever use "*" in a filename?
Not on windows, apparently.
Best wishes,
Taco
___
If your ques
On Fri, Sep 10 2010, Peter Münster wrote:
> Can anybody reproduce the following problem (Taco can't ...):
>
> \startbuffer[pdf-pages]
> \starttext
> page 1 \page page 2
> \stoptext
> \stopbuffer
> \savebuffer[pdf-pages][pdf-pages.tex]
> \executesystemcommand{context pdf-pages; mkdir testd
On Fri, Sep 10, 2010 at 21:27, Peter Münster wrote:
> On Fri, Sep 10 2010, Hans Hagen wrote:
>
>> i get empty pages in the case of a * but that can be simply because
>> a * might not be in a filename on windows
>
> Ok, I can rename the file.
>
> But I think, the behaviour is so strange, that there
On Fri, 10 Sep 2010, Peter Münster wrote:
On Fri, Sep 10 2010, Hans Hagen wrote:
i get empty pages in the case of a * but that can be simply because
a * might not be in a filename on windows
Ok, I can rename the file.
But I think, the behaviour is so strange, that there is somewhere a hidde
On Fri, Sep 10 2010, Hans Hagen wrote:
> i get empty pages in the case of a * but that can be simply because
> a * might not be in a filename on windows
Ok, I can rename the file.
But I think, the behaviour is so strange, that there is somewhere a hidden
bug.
Strange, because 2*8 is the only fi
On 10-9-2010 6:12, Peter Münster wrote:
On Fri, Sep 10 2010, Hans Hagen wrote:
\starttext
\setupexternalfigures[directory={./testdir}]
\externalfigure[28][page=3]
\stoptext
so, no * in the filename
Does this mean, that you can reproduce the problem, or not?
i get empty pages in t
On Fri, Sep 10 2010, Hans Hagen wrote:
> \starttext
> \setupexternalfigures[directory={./testdir}]
> \externalfigure[28][page=3]
> \stoptext
>
> so, no * in the filename
Does this mean, that you can reproduce the problem, or not?
I just want to know, how to compile the context manual, s
On 10-9-2010 2:25, Peter Münster wrote:
\startbuffer[pdf-pages]
\starttext
page 1 \page page 2
\stoptext
\stopbuffer
\savebuffer[pdf-pages][pdf-pages.tex]
\executesystemcommand{context pdf-pages; mkdir testdir;
mv pdf-pages.pdf testdir/2*8.pdf}
\starttext
\setupexternalfigures[direc
于 2010年09月10日 20:25, Peter Münster 写道:
Hello,
Can anybody reproduce the following problem (Taco can't ...):
No problem here.
\startbuffer[pdf-pages]
\starttext
page 1 \page page 2
\stoptext
\stopbuffer
\savebuffer[pdf-pages][pdf-pages.tex]
\executesystemcommand{context pdf-pages; m
Hello,
Can anybody reproduce the following problem (Taco can't ...):
\startbuffer[pdf-pages]
\starttext
page 1 \page page 2
\stoptext
\stopbuffer
\savebuffer[pdf-pages][pdf-pages.tex]
\executesystemcommand{context pdf-pages; mkdir testdir;
mv pdf-pages.pdf testdir/2*8.pdf}
\starttext
\s
13 matches
Mail list logo
