Comment #18 on issue 1701 by freyraph...@gmail.com: default accidental
style prints too many 'extra' naturals
http://code.google.com/p/lilypond/issues/detail?id=1701
Please note that after changing the 'extraNatural' behaviour, the
documentation hasn't been adapted. All references of 'extraNatural' explain
the old behaviour. Some examples:
*
[http://lilypond.org/doc/v2.14/Documentation/internals/accidental_005fengraver]
"extraNatural (boolean)
Whether to typeset an extra natural sign before accidentals changing
from a non-natural to another non-natural."
I suggest this adjustment: "... before accidentals changing from a double
to a single one."
*
[http://lilypond.org/doc/v2.14/Documentation/notation/all-context-properties]
"extraNatural (boolean)
Whether to typeset an extra natural sign before accidentals changing
from a non-natural to another non-natural."
* [http://lilypond.org/doc/v2.14/Documentation/notation/writing-pitches]
"Preventing extra naturals from being automatically added
In accordance with standard typesetting rules, a natural sign is printed
before a sharp or flat if a previous accidental on the same note needs to
be canceled. To change this behavior, set the extraNatural property to f in
the Staff context."
*
[http://lilypond.org/doc/v2.14/Documentation/learning/modifying-context-properties]
All examples should be changed as they are completely useless and lead to
confusions now (this is actually why I discovered the change of
the 'extraNatural' behaviour).
There are many more places which need adjustment (see
[http://www.google.com/search?btnG=Google+Search&brute_query=extranatural&q=site%3Alilypond.org+%2Bv2.14+extranatural]).
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
