LilyPond follows a number of builtin typesetting rules, saying if
a certain articulation should go below or above other indications.
What you noticed here is that LilyPond automatically will put the
fermata on the top. The easiest way to go around this cleverness is
to typeset both the fermata and the text as a single text markup,
such as:
r1^\markup {\column {\large "Test" \musicglyph #"scripts.ufermata" }}
/Mats
Wim van Dommelen wrote:
Hi,
In trying to get both a fermata AND a text description I ran into the
problem that when using a \fermata in combination with a \markup the
fermata is somehow lifted and the \markup and \fermata clash in the
printing. I tried different constructs, but couldn't get it right.
This sample illustrates this:
\version "2.7.9"
muziek = {
\time 4/4
r1 |
r1^\markup { \large "Test 1" }
r1\fermata |
r1\fermata^\markup { \large "Test 2" }
r1\fermata |
r1^\markup { \large "Test 3" }\fermata
r1\fermata |
<< r1\fermata
s1^\markup { \large "Test 4" }
>> |
r1 \fermata |
}
\score { \context Staff {
\clef "G"
\muziek
}}
A bug?
Regards,
Wim van Dommelen.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond