From: David Kastrup <dak@gnu.org>
Date: Thu, 7 Feb 2013 09:18:39 +0000 (+0100)
Subject: Issue 754: don't transpose generic property-setting music commands
X-Git-Tag: release/2.17.13-1~10^2~22
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=4424fd71b56d27d8e1215e28fabec43e7ab8b253;p=lilypond.git

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.
---

diff --git a/scm/define-music-types.scm b/scm/define-music-types.scm
index dc93024041..e7d121b411 100644
--- a/scm/define-music-types.scm
+++ b/scm/define-music-types.scm
@@ -376,6 +376,7 @@ Syntax: @code{\\override} [ @var{context} @code{.} ]
 	(types . (general-music layout-instruction-event
 		  override-property-event))
 	(iterator-ctor . ,ly:push-property-iterator::constructor)
+	(untransposable . #t)
 	))
 
     (PageBreakEvent
@@ -442,6 +443,7 @@ Syntax: @var{note}@code{\\(} and @var{note}@code{\\)}")
 Syntax: @code{\\set @var{context}.@var{prop} = @var{scheme-val}}")
 	(types . (layout-instruction-event general-music))
 	(iterator-ctor . ,ly:property-iterator::constructor)
+	(untransposable . #t)
 	))
 
     (PropertyUnset