One reason for failure of external scripts on Win32

2004-06-02 Thread Angus Leeming
On Tuesday 01 June 2004 6:45 pm, Angus Leeming wrote: On Tuesday 01 June 2004 6:27 pm, Timm Danker wrote: Angus, I just realised that I get the same error message regardless whats in the lyxpreview2bitmap.sh. its sufficient that it is just there in the ./lyx/scripts directory. its not

Re: One reason for failure of external scripts on Win32

2004-06-02 Thread Jean-Marc Lasgouttes
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Timm confirms that this works on Win32 also, so it seems that Angus we have a way out: when invoking an external script, we should Angus wrap the argument in quotes (using QuoteName) if we have Angus replaced one of the placeholders $$a,

Re: One reason for failure of external scripts on Win32

2004-06-02 Thread Angus Leeming
Jean-Marc Lasgouttes wrote: Angus Timm confirms that this works on Win32 also, so it seems that Angus we have a way out: when invoking an external script, we should Angus wrap the argument in quotes (using QuoteName) if we have Angus replaced one of the placeholders $$a, $$i, $$o, $$p, $$s,

Re: One reason for failure of external scripts on Win32

2004-06-02 Thread Jean-Marc Lasgouttes
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus The alternative is to escape 'special chars', so 'Dokumente und Angus Einstellungen' becomes 'Dokumente\ und\ Einstellungen'. This is probably more complicated and error prone. JMarc

Re: One reason for failure of external scripts on Win32

2004-06-02 Thread Angus Leeming
Jean-Marc Lasgouttes wrote: Angus The alternative is to escape 'special chars', so 'Dokumente und Angus Einstellungen' becomes 'Dokumente\ und\ Einstellungen'. This is probably more complicated and error prone. Agreed. So we need: string const subst_filename(string const input,

One reason for failure of external scripts on Win32

2004-06-02 Thread Angus Leeming
On Tuesday 01 June 2004 6:45 pm, Angus Leeming wrote: > On Tuesday 01 June 2004 6:27 pm, Timm Danker wrote: > > Angus, > > I just realised that I get the same error message regardless > > whats in the lyxpreview2bitmap.sh. its sufficient that it is just > > there in the ./lyx/scripts directory.

Re: One reason for failure of external scripts on Win32

2004-06-02 Thread Jean-Marc Lasgouttes
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Timm confirms that this works on Win32 also, so it seems that Angus> we have a way out: when invoking an external script, we should Angus> wrap the argument in quotes (using QuoteName) if we have Angus> replaced one of the

Re: One reason for failure of external scripts on Win32

2004-06-02 Thread Angus Leeming
Jean-Marc Lasgouttes wrote: > Angus> Timm confirms that this works on Win32 also, so it seems that > Angus> we have a way out: when invoking an external script, we > should Angus> wrap the argument in quotes (using QuoteName) if we > have Angus> replaced one of the placeholders $$a, $$i, $$o, $$p,

Re: One reason for failure of external scripts on Win32

2004-06-02 Thread Jean-Marc Lasgouttes
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> The alternative is to escape 'special chars', so 'Dokumente und Angus> Einstellungen' becomes 'Dokumente\ und\ Einstellungen'. This is probably more complicated and error prone. JMarc

Re: One reason for failure of external scripts on Win32

2004-06-02 Thread Angus Leeming
Jean-Marc Lasgouttes wrote: > Angus> The alternative is to escape 'special chars', so 'Dokumente > und Angus> Einstellungen' becomes 'Dokumente\ und\ Einstellungen'. > > This is probably more complicated and error prone. Agreed. So we need: string const subst_filename(string const & input,