[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 2236 in lilypond: accidentals in "complex chords"
From: |
lilypond |
Subject: |
Issue 2236 in lilypond: accidentals in "complex chords" |
Date: |
Fri, 20 Jan 2012 21:18:45 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Ugly
New issue 2236 by address@hidden: accidentals in "complex chords"
http://code.google.com/p/lilypond/issues/detail?id=2236
http://lists.gnu.org/archive/html/bug-lilypond/2012-01/msg00791.html
Reported by Xavier Scheuer:
I thought we had this accidentals in "complex chords" as an
issue on the tracker but I do not find it. It as been discussed several
times on various LilyPond mailing lists, there is a snippet "Displaying
complex chords" on the LSR: http://lsr.dsi.unimi.it/LSR/Item?id=505
(not always "usable").
AFAIK developers would like examples of how such situations are handled
by music publishers. Do they use separate note heads, where do they
place the accidentals, etc. But if "complex accidentals in chords" is
not tracked yet, then it should be added IMHO.
Relevant code showing the issue is simply
<bes b>
If someone could have a look at what Ross, Read or Gould say about this,
how to engrave it, that would be very kind.
Attachments:
bug.preview.png 1.0 KB
- Issue 2236 in lilypond: accidentals in "complex chords",
lilypond <=