On Sat, 12 May 2012 12:11:45 -0700, <d...@gnu.org> wrote:
\breathe c2 \footnote #'(0.5 . 0.5) #'BreathingSign \markup { Breathe }
Not exactly the most intuitive order I have to say.
True. Good to document it, I guess. http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1049 Documentation/notation/input.itely:1049: The @code{\footnote} command comes immediately after the item being "... comes after the note or rest associated with the item being annotated" to be more accurate for the odd things like the breath mark. And as you show later, if you have dynamics and a slur on a sharped note, you can type the \footnote for the sharp after \f( -- which might be convenient. http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1069 Documentation/notation/input.itely:1069: >1 maybe bring the example for #'Accidental up here, too, where there is more space in the typeset output ? >1 \breathe cis2 \footnote #'(0.5 . 0.5) #'BreathingSign \markup { Gasp} \footnote #'(0.5 , 0.5) #'Accidental \markup { Chromatic } http://codereview.appspot.com/6137050/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
