> Le 16 déc. 2016 à 13:47, Peter Toye <lilyp...@ptoye.com> a écrit :
> 
> Jean,
> 
> Thanks to all who answered. It seems to be the space in the file name. I 
> replaced it with an underline and it seems OK now.
> 
> Should be a warning to all application developers: if you're going to put 
> Windows file names in a script, always enclose them in quotes!

The same holds for Linux and Mac OS, it’s a shell feature actually.

JM

> 
> Best regards,
> 
> Peter
> mailto:lilyp...@ptoye.com <mailto:lilyp...@ptoye.com>
> www.ptoye.com <http://www.ptoye.com/>
> 
> -------------------------
> Thursday, December 15, 2016, 7:32:47 PM, you wrote:
> 
> > Le jeudi 15 décembre 2016 à 19:16 +0000, Peter Toye a écrit :
> >> As far as I can tell, all I did was move a few files into different
> >> directories. And I am now getting this message when it tries to
> >> convert the PS file to PDF. The PS file is is still on the disk and
> >> looks OK. Any idea what it means and how I can get my output back?
> 
> >> Layout output to `All night.ps'...
> >> Converting to `./All night.pdf'...
> >> warning: `(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28
> >> -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE
> >> -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./All night.pdf
> >> -c.setpdfwrite -fAll night.ps)' failed (1)
> >> fatal error: failed files: "D:/Peter/Music/Lilypond/Gurney/All
> >> night/Gsharpm/All night.ly"
> 
> 
> >> Regards,
> 
> >> Peter
> >> mailto:lilyp...@ptoye.com <mailto:lilyp...@ptoye.com>
> >> www.ptoye.com <http://www.ptoye.com/>
> 
> > The white space inside the file name might be the issue. On *nix the
> > command would fail because of that, white spaces need to be escape.
> 
> > Hope this helps
> > Jean
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to