elements can overlap. This is unfortunate, but (in most cases) is easily
solved.
+@c FIXME: find a better example for 5.1 Moving Objects. -gp
+@c yes, I want this TODO to be visible to end-users. It's better
+@c than having nothing at all.
+TODO: with the new spacing features in 2.12, these specific examples are no
+longer relevant. However, they still demonstrate powerful features
+of lilypond, so they remain until somebody creates some better examples.
+
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+ % temporary code to break this example:
+ \override TextScript #'outside-staff-priority = ##f
e4^\markup{ \italic ritenuto } g b e
@end lilypond
object). We want to increase it, so let's try 1.5
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+ % temporary code to break this example:
+ \override TextScript #'outside-staff-priority = ##f
\once \override TextScript #'padding = #1.5
e4^\markup{ \italic ritenuto } g b e
@end lilypond
the behavior here.
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+ % temporary code to break this example:
+ \override TextScript #'outside-staff-priority = ##f
c4^"piu mosso" b a b
-\once \override TextScript #'padding = #2.6
+\once \override TextScript #'padding = #4.6
c4^"piu mosso" d e f
-\once \override TextScript #'staff-padding = #2.6
+\once \override TextScript #'staff-padding = #4.6
c4^"piu mosso" fis a g
\break
c'4^"piu mosso" b a b
-\once \override TextScript #'padding = #2.6
+\once \override TextScript #'padding = #4.6
c4^"piu mosso" d e f
-\once \override TextScript #'staff-padding = #2.6
+\once \override TextScript #'staff-padding = #4.6
c4^"piu mosso" fis a g
@end lilypond
that the result can overlap with other objects.
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+ % temporary code to break this example:
+ \override TextScript #'outside-staff-priority = ##f
\once \override TextScript #'extra-offset = #'( 1.0 . -1.0 )
e4^\markup{ \italic ritenuto } g b e
@end lilypond
that these values look good
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+ % temporary code to break this example:
+ \override TextScript #'outside-staff-priority = ##f
\once \override TextScript #'extra-offset = #'( -1.6 . 1.0 )
e4^\markup{ \italic ritenuto } g b e
@end lilypond
@ref{The \override command}.
@lilypond[quote,fragment,ragged-right,verbatim,relative=3]
+ % temporary code to break this example:
+ \override TextScript #'outside-staff-priority = ##f
c4^"piu mosso" b
-\once \override TextScript #'padding = #2.6
+\once \override TextScript #'padding = #4.6
a4 b
c4^"piu mosso" d e f
-\once \override TextScript #'padding = #2.6
+\once \override TextScript #'padding = #4.6
c4^"piu mosso" d e f
c4^"piu mosso" d e f
\break
-\override TextScript #'padding = #2.6
+\override TextScript #'padding = #4.6
c4^"piu mosso" d e f
c4^"piu mosso" d e f
\revert TextScript #'padding
objects; simply replace @code{TextScript} with the name of
another object.
-To find the object name, look at the ``@strong{see also}'' at
+To find the object name, look at the @q{@strong{see also}} at
bottom of the relevant documentation page. For example, at
the bottom of @ref{Dynamics}, we see
f-5
@end lilypond
- @item
+@item
Setting the @code{transparent} property will cause an object to be printed
-in `invisible ink': the object is not printed, but all its other
+in @q{invisible ink}: the object is not printed, but all its other
behavior is retained. The object still takes up space, it takes part in
collisions, and slurs, ties, and beams can be attached to it.
} >>
@end lilypond
-To make sure that the just blanked stem doesn't sqeeuze the too much
+To make sure that the just blanked stem doesn't squeeze the too much
tie, we also lengthen the stem, by setting the @code{length} to
@code{8},
@file{@var{installdir}/LilyPond.app/Contents/Resources/share/lilypond/current/}.
To access this, either @code{cd} into this directory from the
Terminal, or control-click on the LilyPond application and select
-"Show Package Contents".
+@q{Show Package Contents}.
@item Windows: @file{@var{installdir}/LilyPond/usr/share/lilypond/current/}
When investigating layout issues, @code{annotate-spacing} is
an invaluable tool. This command prints the values of various
-layout spacing commands; see @ref{Displaying spacing} for more
+layout spacing commands; see @ref{Displaying spacing}, for more
details. From the output of @code{annotate-spacing}, we can
see which margins we may wish to alter.
@example
\paper @{
-between-system-padding = #0.1
-between-system-space = #0.1
-ragged-last-bottom = ##f
-ragged-bottom = ##f
+ between-system-padding = #0.1
+ between-system-space = #0.1
+ ragged-last-bottom = ##f
+ ragged-bottom = ##f
@}
@end example
@example
\paper @{
-system-count = #10
+ system-count = #10
@}
@end example
systems, they will take up more space than one system with
the volta repeats and another system without.
-Another example is moving dynamics which ``stick out'' of
+Another example is moving dynamics which @q{stick out} of
a system.
@lilypond[verbatim,quote,fragment]
@item
Alter the horizontal spacing via @code{SpacingSpanner}. See
-@ref{Changing horizontal spacing} for more details.
+@ref{Changing horizontal spacing}, for more details.
@lilypond[verbatim,quote]
\score {
commands like
@code{\override TextScript #'extra-offset = ( 1 . -1)}. But
we have even more power if we use Scheme. For a full explantion
-of this, see the @ref{Scheme tutorial} and
+of this, see the @ref{Scheme tutorial}, and
@ref{Interfaces for programmers}.
We can use Scheme to simply @code{\override} commands,
#})
\relative c'' {
-c2 e
-\tempoMark #3.0 #"Allegro"
-g c
+ c2 e
+ \tempoMark #3.0 #"Allegro"
+ g c
}
@end lilypond
projects / lilypond.git / blobdiff