bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 2253 in lilypond: Markup in separate voices in \partcombine re


From: lilypond
Subject: Re: Issue 2253 in lilypond: Markup in separate voices in \partcombine results in "stacked" markup.
Date: Wed, 25 Jan 2012 17:39:32 +0000


Comment #1 on issue 2253 by address@hidden: Markup in separate voices in \partcombine results in "stacked" markup.
http://code.google.com/p/lilypond/issues/detail?id=2253

I have just now pushed the remaining parts of issue 2240 to staging, so this changes the game somewhat. In the new situation, the above input would mean attaching the respective markups to _note_ events. In this case it makes some sense to retain the output belonging to individual notes individually.

In the situation where the bug report was placed, however, this input was perfectly equivalent to
<c''4>_\markup { loud }
so the output was placed on the resulting _chord_. In this case, there is no point in retaining the non-noteevent-specific markup two times.

The question is whether we should, in the new situation, differentiate both cases (currently apparently not done). Which would mean that if you wanted a merged "articulation", you would have to write it as a chord rather than as a note articulation.

Anyway, it may be worth pointing out that a fix of any kind will likely have to take into account the just-now changed behavior of LilyPond.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]