[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: |
Fri, 28 Nov 2014 08:33:44 +0000 |
Comment #31 on issue 4076 by address@hidden: allow bn for B-natural in English
https://code.google.com/p/lilypond/issues/detail?id=4076
The idea is to let me type B-natural, which is what I'm already thinking,
in a melody in C-minor so that I, or maybe other mutopiaproject users,
can find my mistakes more easily.
I have no idea how this would make anybody find mistakes more easily. The
mistake you are trying to prevent is writing "b" instead of "bf". This
mistake will not in any manner be more apparent just because "b" could be
written as "bn".
What your change is supposed to accomplish instead is not finding
mistakes. It is a reassurance that a particular b has _not_ been a
mistake. This assurance, however, is a matter of knowing your personal
style as long as b itself is not an invalid notename. The resulting
inconsistency in personal styles on Mutopia is going to make the work for
proofreaders harder, not easier.
We had that discussion on the mailing list already. What's different this
time around? That you propose a different note name language that would be
identical to the previously proposed extended English note name language.
That means that using the new notename language tantamounts to a warning "I
might be using xn notation in some places if I feel like it". But that's
rather identical to the situation proposed before, including all of its
implications or rather non-implications. It's just more complicated.
That's not usefully different.
--
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
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/27
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/27
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/27
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/27
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/27
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English,
lilypond <=
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/29
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/29
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/29
- Message not available
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/11/29