Malte Meyn <[email protected]> writes: > Am 21.02.2016 um 11:54 schrieb David Kastrup: >> >> So in summary: you state to LilyPond that you never want to see an >> accidental before a natural G and you complain that you see no >> accidental before a natural G. > > I think the problem is: If you set accidentals.natural for G in > pitchGlyphs, every G gets this accidental, not only those which are > preceded by G flats.
Why would LilyPond do that? Have you tried it? The respective properties are usually initialized using standard-alteration-glyph-name-alist defined in scm/output-lib.scm which most definitely contains a natural (how else would LilyPond know how to typeset it?). > Is there a possibility to say something other than “always print a > natural” or “never print a natural”? That's not the business of the glyph lists but of the accidental style. The glyph lists have to be complete. It's the accidental style which decides when to use a glyph or not. >> You also state that any cautionary >> accidental should look like a natural. Good thing that your example >> does not contain a cautionary Gb. > > There Erich made a mistake but this doesn’t have to do with the > problem above. The "problem above" does not exist in LilyPond. Can you point out documentation which would make you believe otherwise? If so, that may need fixing. If not, there is nothing to be seen here. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
