Hi,
2012/2/29 Thomas Morley <thomasmorle...@googlemail.com>:
> TODO
>
> Convert:
> Converting some files gave:
> "Not smart enough to convert minimum-Y-extent.
> Vertical spacing no longer depends on the Y-extent of a VerticalAxisGroup.
> Please refer to the manual for details, and update manually."
> (or sth similiar).
> Could be fixed.
I changed my mind about these files and fixed them too.
I used a little script after the script from CG 7.7 Updating LSR to a
new version to ease the process:
#!/bin/bash
for LILYFILE in *.ly
do
STEM=$(basename "$LILYFILE" .ly);
echo "running $LILYFILE...";
convert-ly -e -t2.14.2 "$LILYFILE" >& "$STEM".txt;
done
One file gives me problems: forcing-fixed-distance-between-staves.ly
converting-log:
convert-ly (GNU LilyPond) 2.15.30
convert-ly: Processing `forcing-fixed-distance-between-staves.ly'...
Applying conversion: 2.12.3, 2.13.0, 2.13.1, 2.13.4,
Not smart enough to convert alignment-offsets.
alignment-offsets has been changed to alignment-distances:
you must now specify the distances between staves rather than the
offset of staves.
Please refer to the manual for details, and update manually.
2.13.10, 2.13.16, 2.13.18, 2.13.20, 2.13.27, 2.13.29, 2.13.31,
2.13.36, 2.13.39,
2.13.40, 2.13.42, 2.13.44, 2.13.46, 2.13.48, 2.13.51, 2.14.0
Well, it compiles without warning but it does nothing (as opposed to 2.12.3).
Currently I don't know how to receive the promised results with the
2.14.2-commands.
Suggestions?
Thanks,
Harm
\version "2.12.2"
\header {
texidoc = "
Since the staves in a PianoStaff context no longer have a fixed
distance set as default, this can result in wide variations in system
spacing.If you need to prevent the spacing engine from varying the
distance between staves (not just piano staves), you can override the
property @code{line-break-system-details} in the
@code{NonMusicalPaperColumn} object. In the first example, we override
the @code{NonMusicalPaperColumn} object in the score's context block;
the result is completely fixed vertical distance throughout the score.
In the second example, the override is applied on the fly at different
points (but always at line breaks) throughout the score; the result is
precisely controlled -- but varying -- amounts of vertical space for
each system, plus the option (see final system) of swapping the staves
around. Note that in this case, overriding @code{NonMusicalPaperColumn}
inline with note entry requires the special @code{\\overrideProperty}
command.
"
doctitle = "Forcing fixed distance between staves"
}
\book {
\score {
\new PianoStaff <<
\new Staff {
c'1^"Fixed distance: fourteen staff spaces for every system"
\break
\repeat unfold 5 { c'1 \break }
}
\new Staff {
\clef bass
\repeat unfold 6 { c'1 }
}
>>
\layout {
\context {
\Score
\override NonMusicalPaperColumn
#'line-break-system-details = #'((alignment-offsets . (0 -14)))
}
}
}
\score {
\new StaffGroup <<
\new Staff {
\overrideProperty #"Score.NonMusicalPaperColumn"
#'line-break-system-details #'((alignment-offsets . (0 -10)))
c'1^"Ten staff spaces"
\break
\overrideProperty #"Score.NonMusicalPaperColumn"
#'line-break-system-details #'((alignment-offsets . (0 -20)))
c'1^"Twenty staff spaces"
\break
\overrideProperty #"Score.NonMusicalPaperColumn"
#'line-break-system-details #'((alignment-offsets . (0 -30)))
c'1^"Thirty staff spaces"
\break
\overrideProperty #"Score.NonMusicalPaperColumn"
#'line-break-system-details #'((alignment-offsets . (0 10)))
c'1^"Ten staff spaces again, with staves swapped around"
}
\new Staff {
\clef bass
c'1
c'1
c'1
c'1
}
>>
}
}
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
