Re: wrong note name conversion in musicxml2ly

2020-02-11 Thread Torsten Hämmerle
In any case, the current musicxml2ly problem is about heses. And the heses note name definition in LilyPond (scm/define-note-names.scm) is correct and should not be changed. musicxml2ly must not produce a German "bes", because this clearly should be "heses" Here's the coding for German pitch names

Re: wrong note name conversion in musicxml2ly

2020-02-11 Thread David Kastrup
Torsten Hämmerle writes: > In any case, the current musicxml2ly problem is about heses. And the heses > note name definition in LilyPond (scm/define-note-names.scm) is correct and > should not be changed. > musicxml2ly must not produce a German "bes", because this clearly should be > "heses" > >

Re: wrong note name conversion in musicxml2ly

2020-02-11 Thread Torsten Hämmerle
Oh, great, thanks, I missed issue 5746. it exactly solves the problem and even will produce the more common "asah" instead of "aseh" etc. So apologies for my late (and hence superfluent) reply/hint. Torsten -- Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html ___

Re: wrong note name conversion in musicxml2ly

2020-02-11 Thread David Kastrup
Torsten Hämmerle writes: > Oh, great, thanks, > > I missed issue 5746. it exactly solves the problem and even will produce the > more common "asah" instead of "aseh" etc. > So apologies for my late (and hence superfluent) reply/hint. Well, I should have posted a notice regarding the tracker issu