[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: English note names generate errors
From: |
James Lowe |
Subject: |
Re: English note names generate errors |
Date: |
Mon, 11 May 2015 19:56:43 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
On 11/05/15 16:15, David Kastrup wrote:
>> 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>.
Just for the record (and bug squad) this now has a tracker
https://code.google.com/p/lilypond/issues/detail?id=4388
(just in case it was not clear).
James