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
