Updates:
Status: Fixed
Labels: -Patch-countdown Fixed_2_17_13
Comment #20 on issue 754 by [email protected]: \transpose should not affect
\transposition
http://code.google.com/p/lilypond/issues/detail?id=754
Pushed to staging as
commit 7680952372689f3ce5674d47af42edfc475cface
Author: David Kastrup <[email protected]>
Date: Tue Feb 5 17:31:48 2013 +0100
Adapt input/regression/quote-transposition.ly to new realities
commit 4424fd71b56d27d8e1215e28fabec43e7ab8b253
Author: David Kastrup <[email protected]>
Date: Thu Feb 7 10:18:39 2013 +0100
Issue 754: don't transpose generic property-setting music commands
The actual issue was that
\transpose c e { \transposition bes ... }
created a Midi corresponding to an instrument using a transposition of
ges, leaving the Midi unchanged. Making the generic property-setting
commands (\set and \override) impervious to transposition will also
keep \transpose from tampering with user-set values.
This is particularly important since the pitch data type in LilyPond
is also being used for signifying intervals or pitch differences
rather than absolute pitches.
In the Rietveld review, there were discussions about a
backward-compatibility option. This should be made into a different
issue. Also an entry in changes.itely is called for. There is already a
documentation issue for the notation manual to document the post-754
behavior (rather than not mentioning the relation between \transpose and
\transposition).
