On 02.08.2009, at 11:02, Peter Chubb wrote:
Hi,
I'm typesetting a little setting of Jn 3:16 I composed, in a
file called Jn3:16.ly. Lilypond can't see the file! It seems to be
trying to open 16.ly instead.
From strace;
...
stat64("/usr/share/lilypond/2.12.2/scm/16.ly", 0xbfc06ce4) = -1
ENOENT (No such file or directory)
stat64("/usr/share/lilypond/2.12.2/ps/16.ly", 0xbfc06ce4) = -1
ENOENT (No such file or directory)
stat64("/usr/share/lilypond/2.12.2/ly/16.ly", 0xbfc06ce4) = -1
ENOENT (No such file or directory)
stat64("16.ly", 0xbfc06ce4) = -1 ENOENT (No such file or
directory)
...
$ lilypond Jn3\:16.ly
GNU LilyPond 2.12.2
warning: cannot find file: `Jn3:16.ly'
error: failed files: "Jn3:16.ly"
To reproduce:
echo '\version "2.12.2"' > 'Jn3:16.ly'
lilypond 'Jn3:16.ly'
On Posix compliant systems the *only* two characters illegal in a file
name are the slash ('/' which is used as a directory separator) and
the
NUL that terminates a C string.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT
gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT
Australia
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Ghostscript has issues with accented characters as well, so I would
avoid those as well, if I were you.
James E. Bailey
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
