Re: English note names generate errors

[David Kastrup]

John Holcroft <address@hidden> writes:

> Your bug summission page is very rude and annoying.

We don't have a "bug submission page": users are advised to mail problem
reports to this bug list.  I have no idea what page you used.

> My lilypond files include \language "english" at the top.  In version
> 19.20 any note names written in english, like eflat, cause a syntax
> error.
>
> error: unrecognized string, not in text script or \lyricmode

That's because the long note names have been changed.  If you had used
convert-ly for converting the syntax, you'd hopefully not have seen a
problem ("hopefully" since the conversion rule currently is less than
perfect and will likely be improved in 2.19.21, probably including the
results of issue 4372
<URL:http://code.google.com/p/lilypond/issues/detail?id=4372>.

LilyPond's Changes section
<URL:http://lilypond.org/doc/v2.19/Documentation/changes/index#top>
states:

Actually, it does not state anything at all.  Uh, that would likely be
worth a few words.  The issue introducing this change had been
issue 4209
<URL:https://code.google.com/p/lilypond/issues/detail?id=4209> and the
changes had been present since version 2.19.16.

The respective discussion (namely none at all) is evenly distributed
between the issue report itself and the code review at
<URL:https://codereview.appspot.com/180440043>.

There might have been some ongoing discussion on the developer list
before that, so you might want to look in the Nov/Dec 2014 time frame in
the archives.

-- 
David Kastrup