Hi all, > I think most readers would interpret it as "C with A in the > bass" (and why that chord is not called A-minor-seventh, left unclear).
Agreed. > This would be a problem for a system like current LilyPond that insists on > translating it to notes and back, because the internal representation for > the choice is likely to collide with that for a chord which really is "C > with A in the bass” Again, for clarity/accuracy: It’s a problem with "current Lilypond”, but *not* with the abstract concept of translation to notes and back. (Not sure how many times I have to repeat myself on that point?) It would be fairly trivial to program a parser that knew the difference between C/A and C/a, and processed and output accordingly. > it'd be no problem with a system that just formats and prints what's typed, > in which "C/a" can mean anything and the system doesn't need to interpret it. This functionality has been available in Lilypond since at least 2003 (or whenever Lyrics were first introduced). Cheers, Kieren. ________________________________ Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
