lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in En


From: lilypond
Subject: Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English
Date: Tue, 26 Aug 2014 05:05:08 +0000


Comment #12 on issue 4076 by address@hidden: allow bn for B-natural in English
https://code.google.com/p/lilypond/issues/detail?id=4076

"as" and "aes" are both accepted mostly to accommodate non-Dutch users of the Dutch notename language who are working by analogy or who are generating note names by program. The intent is to avoid people getting surprised/stuck by writing a note name that does not get accepted. There is not really much of a cause for confusion when seeing the "incorrect but regularly formed" note name, just for surprise or eye sores.

In contrast, this issue here was *created* in the first place because the issue submitter as well as some supporters considered the standard names an ongoing cause for confusion. But it's not like the standard names are going to go away or fall into disuse. And I doubt we'll see even the patch proponents write things like \key an\minor or \chordmode { an gn:dim }.

So even in a personal notewriting style, the question "when should I use g and when gn" will not likely have an altogether satisfactory answer once you consider gn a valid form at all.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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