[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 07:55:23 +0000 |
Comment #14 on issue 4076 by address@hidden: allow bn for B-natural in English
https://code.google.com/p/lilypond/issues/detail?id=4076
Since one cannot write f instead of fs when f-sharp is native to the key,
I don't see that a style of fanning out g into g and gn depending on the
key signature can be developed into a reasonably idiomatic/helpful personal
style.
It would be an interesting programming challenge to facilitate note entry
following the key signature (presumably with a "forget" accidental style
philosophy as far as it concerns note entry). But I suspect it would turn
into a copy&paste nightmare quite worse than that presented by \relative
mode (which only needs corrections for the first note of a pasted passage
and the first note afterwards).
In a way, "absolute accidentals" may be a dutchism. But I don't see that
we improve the situation for English-thinking users by offering an "escape"
for naturals only. That's freedom of the "you are allowed to move anywhere
as long as you do not leave the cage" kind. As long as g and gn remain
perfectly synonymous independent of key, I fail to see a tangible benefit
here.
Of course I may have problems putting myself into English-speaking users'
shoes anyway. I just don't see the planned shoe make for a better fit,
never mind that it's not my foot that needs to go in.
--
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, (continued)
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/25
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/25
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/25
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/25
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/25
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/25
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/25
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/25
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/26
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/26
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English,
lilypond <=
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/26
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/26
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/26
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/27
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/27
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/27
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/30
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/30
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/30
- Re: [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/30