You are right. It was My fault. I did use the wrong path.
Thank you for fixing.
On 2/16/20 6:30 PM, David Kastrup wrote:
> mari+lilyp...@mailbox.org writes:
>
>> As far as I understand the closed issue 5746 should fix the problem
>> musicxml2ly generating the note name "bes" instead of "heses"
mari+lilyp...@mailbox.org writes:
> As far as I understand the closed issue 5746 should fix the problem
> musicxml2ly generating the note name "bes" instead of "heses" with
> --language=deutsch.
>
> In fact the problem is not fixed in the actual git repository. See my
> attached mxl-file and the
As far as I understand the closed issue 5746 should fix the problem
musicxml2ly generating the note name "bes" instead of "heses" with
--language=deutsch.
In fact the problem is not fixed in the actual git repository. See my
attached mxl-file and the ly output of
musicxml2ly --language=deutsch
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
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
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"
>
>
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
mari+lilyp...@mailbox.org writes:
> According to
> http://www.ekmelic-music.org/de/extra/name24.htm
> the "beh" in Netherlands or "bqf" in English does correspond indeed to
> "heh" in German. But I never worked with quarter notes.
Frankly, I suspect that their names are essentially
According to
http://www.ekmelic-music.org/de/extra/name24.htm
the "beh" in Netherlands or "bqf" in English does correspond indeed to
"heh" in German. But I never worked with quarter notes.
On 2/9/20 5:52 PM, David Kastrup wrote:
> mari+lilyp...@mailbox.org writes:
>
>>> On 2/9/20 1:49 PM, David
mari+lilyp...@mailbox.org writes:
>> On 2/9/20 1:49 PM, David Kastrup wrote:
>>> mari+lilyp...@mailbox.org writes:
>>>
when converting a mxl file with "musicxml2ly --language=deutsch" the
note "beses" is converted to "bes". Lilypond gives an error at this
notename with \language
At least the output of musicxml2ly should be consistent with lilypond
and should not not give an error message when compiling.
Here the german Wikipedia for "double flat b":
https://de.wikipedia.org/wiki/Doppel-b
On 2/9/20 1:49 PM, David Kastrup wrote:
> mari+lilyp...@mailbox.org writes:
>
>>
mari+lilyp...@mailbox.org writes:
> when converting a mxl file with "musicxml2ly --language=deutsch" the
> note "beses" is converted to "bes". Lilypond gives an error at this
> notename with \language "deutsch", because the correct german notename
> for "double flat b" is "heses". This happens
when converting a mxl file with "musicxml2ly --language=deutsch" the
note "beses" is converted to "bes". Lilypond gives an error at this
notename with \language "deutsch", because the correct german notename
for "double flat b" is "heses". This happens with all musicxml2ly
versions at least from
13 matches
Mail list logo
