Happy New Year
Today I tried both the 32 bit and the 64-bit versions of version
2.12.1-1, but still producing the unwanted filename.
Could the answer lie in the language settings on this debian-box?
(excerpts of set and env):
MM_CHARSET=ISO-8859-1
SHELL=/bin/bash
LANG=da_DK
LESSCHARSET=latin1
LANGUAGE=da_DK:da:en_GB:en
BASH_VERSINFO=([0]="3" [1]="1" [2]="17" [3]="1" [4]="release"
[5]="x86_64-pc-linux-gnu")
BASH_VERSION='3.1.17(1)-release'
HOSTTYPE=x86_64
MACHTYPE=x86_64-pc-linux-gnu
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
Is the cause perhaps a variation of what happens to the text output if
you accidentally forget to save a .ly file as UTF-8?
Does /bin/bash and/or the parser/lexer read the UTF-8 formatted
output-suffix as ISO-8859-1, thus getting confused?
--
med venlig hilsen Villum Sejersen
Nørregade 1 A
DK-4500 Nykøbing Sj.
tlf. +45 59 91 31 57
mobil +45 30 34 03 44
http://home20.inet.tele.dk/vsevisit/
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
