Issue 546 in lilypond: Incorrect merging when a same note has different accidentals

[codesite-noreply]

Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546

Comment #8 by erlenda:
I've had another look at this and simplified the patch. I've yet to 
find a solution for how to automatically force
accidentals for altered unisons.

Attachments: new patch and a png showing some tests.

With the limitation mentioned in my previous comment, this isn't a 100% 
perfect solution, but it is better than
current behaviour. Shall I apply the patch if we document the 
workaround as a "known limitation"?

Attachments:
        alteredunison2.diff  3.1 KB
        accidental-altered-unisons.png  16.2 KB



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings