The list on Dolmetsch isn't too bad but it's a little confusing in my opinion. I think it'd be better to categorize the ways in which a single chord note is affected (or a set of notes) rather than naming all variations for each chord. For example it lists three variations for a minor triad (m, mi, min) but only two for minor-major7 chord (-maj7, -Δ). I'll make a list this week and then we can put together all the information we have from everyone and see what seems to be more useful.
> Given that I have only ever used \chordmode with ChordNames, I hadn't > noticed the problem, but having done a little test, I can see what you > mean. The chord <d f aes c> produces a chord name of Cb6/sus4/sus2!? > Bizarre! As I already said some time ago when I made my own chordnames functions, I still believe chordnames should be seperated from chords, or at least chords shouldn't produce chordnames since it'll never be clear. And the other way round there can also occur problems, i.e. with C7alt., how should Lilypond know which chord to display then. Another thing is the exceptions list. I think instead of defining some standards (\realbook, etc.) it would be easier to just type what you mean, maybe something like c:m7, c:mi7, c:-7 That way everyone could just type each chordname as they want it to be displayed instead of selecting an exception for each from a list. Regards, Tao -- Nur bis 31.05.: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate und Telefonanschluss nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user