You are lucky, that there's already a predefined markup to typeset
fermatas, so you can do
c^\markup{ \fermataMarkup followed by some text }
If you want to do the same with a coda sign, for example, you can do
codaMarkup = \markup { \musicglyph #"scripts.coda" }
and then use it either standalone as c^\codaMarkup
or within a markup as
c^\markup{ D.S. al \codaMarkup }
Note that these will be typeset as TextScript objects, in contrast to if
you use
c^\coda
which is handled as the same way as all the articulation signs and thus
is typeset as a Script object,
/Mats
Werner wrote:
% looking for an easy possibility to just
% put a fermata followed by a text
% on/above one note
% \fermata followed by \markup would be nice, but doesn't work...
\version "2.10.33"
\relative c' {
\clef G
\time 3/2
% \key bes \major
\key g \minor
\partial 4
\repeat "volta" 2 {
d'4 | c cis d d8( c) bes4.
% works, but very very laborious
^\markup {
% try with or without next line - strange behaviour!
\hspace #0
\musicglyph #"scripts.ufermata" "2."
}
% in this case _\fermata could be a solution
% but this ist always dangerous for later transpositions
% btw - why \fermata without leading ^ an _ is always put
% above the note and not automaticaly there, where there
% isn't the stem?
% thus unfortunately ^ makes no sense
bes8 | % 3
a \noBeam g f \noBeam g es4. d8 d2
% doesn't work - markup to high
^\fermataMarkup ^\markup{ \hspace #2 3.}
| r8 g fis g a2 bes4
% doesn't work - fermata to high
^\fermata ^\markup{
% with or without next line - hspace seems to be "saved" space,
% where nothing else will be printed
% \hspace #2
"(1.)"}
}
}
_______________________________________________
lilypond-user mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=============================================
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
lilypond-user mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-user
