On 12/8/2017 2:58 PM, Urs Liska wrote:
(from documentation)
"...
To determine whether to print an *accidental*, LilyPond examines the
pitches and the key signature. The key signature only affects the
*/printed/***accidentals, not the note’s pitch!
--> This is a feature that often causes confusion to newcomers, so let
us explain it in more detail.
LilyPond makes a clear distinction between musical content and layout.
The alteration (flat, natural sign or sharp) of a note is part of the
pitch, and is therefore musical content. Whether an accidental (a
*/printed/***flat, natural or sharp sign) is printed in front of the
corresponding note*is a question of layout*.
But to be fair one should note that there are serious encoding systems out there that work like the OP expects, for example the MEI encoding format or the Amadeus notation software.
I didn't think Amadeus was still being developed...?
When I discussed the topic with an Amadeus power user he said that he would go nuts with all the typing (of the extra is and es) with the thousands of pages of music he has to create every year.
I went nuts typing with SCORE for years but looking back, it built
character I say :)
MEI on the other hand wants to encode "what is on the paper", that is: an "a" for any pitch on that step. However, I don't accept that because that a flat in e flat major is *not* printed as an "a" that becomes an a flat through the key signature. Actually it's a note head in the second space that becomes an a through the treble clef and only then an a flat.
Urs
|