[Top][All Lists]

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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 3356 di

From: Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 3356 discussion
Date: Sun, 11 Mar 2018 19:20:59 -0000


Triple flats/sharps may be exotic (to say the least), but there's no reason at all why LilyPond shouldn't be able to handle them.
In user discussion thread this issue has been brought up (again)...

The chords generated in \chordmode may look over-engineered and one might consider using enharmonic spellings, but currently (without triple accidentals), the output will be plain and simply wrong: withoutany accidental.

Work started.

[issues:#3356] add triple flats/sharps

Status: Started
Created: Wed May 08, 2013 12:47 PM UTC by Anonymous
Last Updated: Wed May 08, 2013 12:47 PM UTC
Owner: Torsten Hämmerle

Originally created by: *anonymous

Originally created by: address@hidden

Originaly reported by Marc Hohl on -devel:

Hello list,
yesterday I stubled upon a problem with chord transposition.

We had a jazz tune in c major with an a-flat:dim7 chord.

When transposing this tune to e-flat major, lilypond complains
about a missing triple flat and prints a c-flat minor 6/b5
instead (which is enharmonically correct, but ugly to read).

\score {
  \new ChordNames {
    \chordmode {
       \transpose c es as:dim7

Should we raise an issue for this on the tracker?
Regards, Marc

Sent from because address@hidden is subscribed to

To unsubscribe from further messages, a project admin can change settings at Or, if this is a mailing list, you can unsubscribe from the mailing list.

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
Testlilyissues-auto mailing list

reply via email to

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