Thanks for looking into this. I can live with this being turned into the sum of: 1. A bug report for German chord names. The German names for h, his and b chords would be H, H# and B, but I showed that in the last case Hb was printed instead, which I believe that no German will recognize as the expected chord name. 2. A documentation issue. As you said, it is not currently in the notation reference that Lilypond tries to print chord names in the input language. 3. A feature request. The feature request may be to add a \defaultChords or \englishChords command that would give me what I had expected.
I am not sure that we want the implicit coupling between input note name language and output chord name language, though. Also we seem to have 12 input languages and 5 chord name languages, so what should be the expected output in the remaining 7 cases? I am afraid that even with proper documentation this could turn confusing. I will let others decide about that. Best regards, Ole Sendt med ProtonMail sikker e-mail. ------- Original Message ------- D. lørdag den 12. marts 2022 kl. 17:17, Thomas Morley skrev <thomasmorle...@gmail.com>: > Am Sa., 12. März 2022 um 17:10 Uhr schrieb Thomas Morley > > thomasmorle...@gmail.com: > > > Am Sa., 12. März 2022 um 09:58 Uhr schrieb Ole V. Villumsen via > > > > bug-lilypond bug-lilypond@gnu.org: > > > > > % When input language is "deutsch" (German), > > > > > > % Lilypond does not seem to print the default chord names > > > > > > % given in the notation reference > > > > > > % > > > https://lilypond.org/doc/v2.22/Documentation/notation/displaying-chords#customizing-chord-names > > > > > > % The only workaround I have found was to use a different input language. > > > > > > \version "2.22.2" > > > > > > \language "deutsch" > > > > > > << > > > > > > \new ChordNames { > > > > > > % Expecting default chord names: B B# Bb > > > > > > % Instead getting: H H# Hb > > > > > > \chordmode { > > > > > > h1 his b > > > > > > } > > > > > > } > > > > > > [billede.png] > > > > > > -- > > > > > > Ole V. Villumsen > > > > > > Jelshøjvænget 13 > > > > > > 8270 Højbjerg > > > > > > 86 27 29 26 > > > > > > SMS 30 22 29 26 > > > > > > Sendt med ProtonMail sikker e-mail. > > > > > > _______________________________________________ > > > > > > bug-lilypond mailing list > > > > > > bug-lilypond@gnu.org > > > > > > https://lists.gnu.org/mailman/listinfo/bug-lilypond > > > > Hi Ole, > > > > thanks for the report. Here my current understanding. > > > > The behaviour is expected. > > > > Granted, we have the possibility to transform input in the > > > > default-language into german/italian/french chordnames. Via > > > > \germanChords etc. > > > > But not from a different input-language into english chordnames. > > > > So this may turn this bugreport into a feature request? > > > > If \language is specified LilyPond tries to print chordnames in that > > language. > > > > This is not documented, afaict. > > > > So this may be an doc-issue? > > I withdraw below, it doesn't work as I thought... > > > > % The only workaround I have found was to use a different input language. > > > > Do you mean something like below? > > > > \language "deutsch" > > > > << > > > > \new ChordNames { > > > > \languageSaveAndChange #default-language > > > > \chordmode { > > > > b bis bes > > > > } > > > > \languageRestore > > > > } > > > > \new Staff { > > > > h his b > > > > } > > > > Then I'd vote for better documentation of languageSaveAndChange and > > > > languageRestore, currently there's none. > > > > Cheers, > > > > Harm _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
