[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wrong note name conversion in musicxml2ly

From: David Kastrup
Subject: Re: wrong note name conversion in musicxml2ly
Date: Tue, 11 Feb 2020 17:22:14 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Torsten Hämmerle <address@hidden> 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"
> Here's the coding for German pitch names:
> Replacing generic "hes" by "b" is OK, but, that way, generic "heses" will
> become "bes", wich is clearly wrong and will lead to the error observed.
> So obviously, it's a problem with *python substring replacement*.
> I don't know much about python, but replace() doesn't seem to work out here.
> Probably only a direct string comparison will help here, perhaps someone
> knowledgeable has a more elegant solution.


Tracker issue: 5746 (https://sourceforge.net/p/testlilyissues/issues/5746/)
Rietveld issue: 547610043 (https://codereview.appspot.com/547610043)
Issue description:
  Fix and align musicxml and input language "deutsch"  Has commits:
  In \language "deutsch" use b only to replace hes  The quartertone
  names should all be derived from h instead of b since beh was being
  used inconsistently.   Fix deutsch language of musicxml2py  Use b
  only for hes and nothing else.  Also use asas and asah instead of
  ases and aseh.

should fix either.  It doesn't use patterns for hes.  Somewhat artless.
So what.

David Kastrup
My replies have a tendency to cause friction.  To help mitigating
damage, feel free to forward problematic posts to me adding a subject
like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".

reply via email to

[Prev in Thread] Current Thread [Next in Thread]