peter Maybe this is another reason to somehow separate chords from actual text in the editor, as I've been suggesting.
As always, I think you can make most people happy by offering different options. Of course, you'll still have some who will cry, but that's just life 🙂 It also depends on which approach requires the least coding and changes.
In any case, I think some way of setting clear rules for what the lyrics engine recognizes as a chord is important, because that would avoid having issue like this one (or the one I kept mentioning, with words like "cab", "ache" etc.).
A few suggestions (can be either, or can be all of these):
- Chords need to be in brackets
- Spreadsheet-like lyrics editor, with separate columns for timecode, chords, lyrics, midi data
OR (possibly the easiest option for the current code)
- Treat specific character sequences as chords, and everything else is treated as text.
For example:
- A, Ab, A#, Am, Asus, Ao, Adim, A6, A7 etc. < chord (any following character that comes before a "space" would be treated a chord). So Ab7b9#11 < chord, Ab7b9 #11 < only Ab7b9 is the chord, #11 is text
- Ac,Ad, As, Ao, Ae etc. < not a chord
- Z#, Zb etc. < not a chord
