Comment #8 on issue 2343 by [email protected]: Faulty file-naming when
outputting multiple \books
http://code.google.com/p/lilypond/issues/detail?id=2343
Just a thought, Before I implemented \bookOutputSuffix, the only way of
controlling the version suffix was to set a Scheme variable output-suffix,
e.g.
"output-suffix" = "Allegro"
\book {
\paper {
}
...
}
"output-suffix" = "Andante"
\book{
\paper {
}
'''
}
"output-suffix"= "Alleluia"
\book {
\paper {
}
...
}
So we retained the global variable for this and the new \bookOutputName
function to retain backwards compatibility.
The above sort of fail gives this output pre this patch:
ian@nanny-ogg ~/Dropbox/Development/Lilypondwork/OutputFilenameTests$
$LILYBUILD/out/bin/lilypond Exsultate-Osuffix.ly
GNU LilyPond 2.15.30
Processing `Exsultate-Osuffix.ly'
Parsing...
Interpreting music...
Interpreting music...
Exsultate-Osuffix.ly:67:51: warning: Two simultaneous tempo-change events,
junking this one
\transposition f \time 4/4
\tempo "Allegro"
\hornsmovoneMusic
Exsultate-Osuffix.ly:21:1: warning: Previous tempo-change event here
\tempo "Allegro" 4=128
Preprocessing graphical objects...
MIDI output to `Exsultate-Osuffix-Allegro.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `Exsultate-Osuffix-Allegro.ps'...
Converting to `./Exsultate-Osuffix-Allegro.pdf'...
Interpreting music...
Interpreting music...
Exsultate-Osuffix.ly:163:61: warning: Two simultaneous tempo-change events,
junking this one
\transposition f \time 4/4 \key e \major
\tempo "Allegro" \hornsmovtwoMusic
Exsultate-Osuffix.ly:111:1: warning: Previous tempo-change event here
\tempo "Andante" 4=72
Preprocessing graphical objects...
MIDI output to `Exsultate-Osuffix-Andante.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `Exsultate-Osuffix-Andante.ps'...
Converting to `./Exsultate-Osuffix-Andante.pdf'...
Interpreting music...
Interpreting music...
Exsultate-Osuffix.ly:224:5: warning: already have slur
d8
( c) bf-. a-. |
Preprocessing graphical objects...
MIDI output to `Exsultate-Osuffix-Alleluia.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `Exsultate-Osuffix-Alleluia.ps'...
Converting to `./Exsultate-Osuffix-Alleluia.pdf'...
Success: compilation successfully completed
ian@nanny-ogg ~/Dropbox/Development/Lilypondwork/OutputFilenameTests$
I reckon this patch is probably going to deprecate this sort of usage, so
we may need something in CHANGES or whatever, or have a convert-ly rule to
change
"output-suffix" = <blah>
or #(define output-suffix <blah>) to
\bookOutputSuffix <blah>
I found the directory with all the test files I had for playing with this
stuff. Unfortunately I never figured out a way of getting the regression
test suite to process this stuff as they tend to rely on fixed input and
output file names.
However, if you'd find it helpful, I'll comb through all the junk I have
and get together a list of Test conditions so you can put this patch
through the wringer.
Cheers,
Ian
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
