Re: Adding text to chord names or note names

[Jean Abou Samra]

Hello,

Le 29/11/2022 à 23:22, Flaming Hakama by Elaine a écrit :
> Lilypond provides ways both to choose among a few of the common 
> approaches, and a way to define your own.
>
> It does not provide a way to use different symbols for the same chord 
> in the same sequence.  There are workarounds for that, if it is really 
> desired.  But it is not clear that any one engraving should employ 
> more than one way to notate the same chord.


It apparently occurs frequently enough for a GSoC project to have been 
invested in it.

Not an expert here, but Cm7 omit root and E♭ are indeed quite different 
things, a bit like enharmonically equivalent notes.


> In any case, the suggestion of using text does not address this.


Please clarify. The whole point is that the full name is given for each 
chord without automatic calculation.


> It would probably be possible to write a function that does the 
> root/bass note respellings.


Yes, cf. my previous post linking to exactly such a function.


> In my opinion, part of the reason there has been no movement on the 
> chord work done as part of GSOC is that it is a solution looking for a 
> problem.


The problem addressed by the GSoC code is very clear. It is that \chords 
{ c:m7^1 ees } yields "E♭ E♭".

That problem goes away if you use specify chord symbols with text 
markup. Doing that has advantages and disadvantages compared to the GSoC 
code. The whole debate is about the balance of these advantages (some 
find it more convenient) and disadvantages (loss of semantic input, 
although its benefit is not very clear in this case).

Best,
Jean

OpenPGP_signature
Description: OpenPGP digital signature