David Kastrup <d...@gnu.org> writes: > Jean Abou Samra <j...@abou-samra.fr> writes: > >> Le 10/06/2022 à 23:37, Carl Sorensen a écrit : >>> >>> >>> On Fri, Jun 10, 2022 at 2:23 PM Jean Abou Samra <j...@abou-samra.fr> >>> wrote: >>> >>> >>> >>> >>> This is a known issue. This was added as a feature, but most >>> people are >>> finding it more of a quirk than a feature, especially since >>> there's no >>> built-in way to switch back to English. See >>> >>> https://gitlab.com/lilypond/lilypond/-/issues/6305 >>> >>> >>> >>> I propose we revert that commit. It is broken. We could fix it >>> correctly, but in the meantime, I think we should just revert it. >> >> >> >> On the other hand, if we revert it, there will >> be no way to have the chord names in another language, >> which some people are presumably using. It's >> never simple ... > > Presumably the solution would be to provide a reliable interface for > selecting chord name language not intermingled with the input language > setting.
In essence, what we should be doing is separating chord name language and chord name style. The "legacy" \germanChords and similar can then set _both_ for compatibility reasons. -- David Kastrup
