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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 31. Dezember 2008 11:00:17 schrieb Villum Sejersen:
Am Dienstag, 30. Dezember 2008 11:41:13 schrieb Villum Sejersen:
lilypond 2.12.0-1 - 2.11.65-1 and most likely older versions too
The other day I tried to spare myself some
Minimal.ly
Description: application/extension-ly
Minimal-S_TB_d-major.pdf
Description: Adobe PDF document
v...@villums8:~/lilypond/testlily$ ly Minimal.ly
GNU LilyPond 2.12.0
Processing `Minimal.ly'
Tolker...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number
2008/12/31 Reinhold Kainhofer reinh...@kainhofer.com:
You say that you are using the x86_64 version, while I am on a 32-bit machine.
Might this be the difference? Can someone else with a 64-system check this
report?
Today's git on 64bits:
Sortie mise en page vers « Minimal-SAATB_d-major.ps
lilypond 2.12.0-1 - 2.11.65-1 and most likely older versions too
The other day I tried to spare myself some post-file-renaming, (in the
\global section in a rather simple 5-voice choral score) using:
#(define output-suffix SAATB_d-major)
To my surprise the resulting filenames
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 30. Dezember 2008 11:41:13 schrieb Villum Sejersen:
lilypond 2.12.0-1 - 2.11.65-1 and most likely older versions too
The other day I tried to spare myself some post-file-renaming, (in the
\global section in a rather simple 5-voice
