[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: |
Mon, 25 Aug 2014 09:18:53 +0000 |
Comment #3 on issue 4076 by address@hidden: allow bn for B-natural in English
https://code.google.com/p/lilypond/issues/detail?id=4076
Regarding the issue report: while the issue summary contains a paraphrase,
the report itself fails to mention that this change is considered for
\language "english" only.
I've been mulling this over a bit. I'm not overly qualified to comment on
the primary motivation behind it, not using English note names habitually.
The actual issue I have with this is that it promotes a divergence of user
styles that makes it harder for people to read other people's scores and
cooperate on common scores.
Now to be fair, that is to some degree already a problem inherent in the
existence of notename languages.
What I am afraid of is that people will become more rather than less
confused when trying to read something like "as as an as as a a a" or just
something written as "as a a" in the first place.
With regard to documentation: since this is intended to help beginners, it
would be in the Learning Manual, but presumably with a notice like "you can
do that if you want to, but we will not be doing it ourselves anywhere else
in the documentation".
Since especially beginners learn by example, that is not likely to promote
this feature a whole lot. Again: if this rationale would hold completely,
people would not be using any note language apart from Dutch anyway.
So there is definitely quite a bit of handwaving involved in my reasoning.
Still summarily my gut feeling is that it is not a good idea.
We should likely try to survey active users of the English notename
language what they think of this feature overall and its effect on scores
they may produce and come across in future. Because those will clearly be
the ones who are affected.
--
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
- [Lilypond-auto] Issue 4076 in lilypond: allow bn for B-natural in English, lilypond, 2014/08/24
- 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 <=
- 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