@c -*- coding: utf-8; mode: texinfo; -*-
+@c This file is part of lilypond-learning.tely
+@ignore
+ Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
@node Tweaking output
@chapter Tweaking output
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
instead) and the note. In LilyPond, this is called the
@code{padding} property; it is measured in staff spaces. For most
objects, this value is around 1.0 or less (it varies with each
-object). We want to increase it, so let's try 1.5
+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
the next bit of text). To change the behavior of everything after
the command, omit the @code{\once}. To stop this tweak, use a
@code{\revert}. This is explained in depth in
-@ref{The \override command}.
+@ruser{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
@seealso
-This manual: @ref{The \override command}, @ref{Common tweaks}.
+This manual: @ruser{The \override command}, @ruser{Common tweaks}.
@node Fixing overlapping notation
@section Fixing overlapping notation
-In @ref{Moving objects}, we saw how to move a @code{TextScript}
+In @ruser{Moving objects}, we saw how to move a @code{TextScript}
object. The same mechanism can be used to move other types of
objects; simply replace @code{TextScript} with the name of
another object.
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
+the bottom of @ruser{Dynamics}, we see
@quotation
@seealso
context handles a certain object. Since the @code{MetronomeMark} object
is handled in the @code{Score} context, property changes in the
@code{Voice} context will not be noticed. For more details, see
-@ref{Constructing a tweak}.
+@ruser{Constructing a tweak}.
@cindex extra-offset
} >>
@end lilypond
-To make sure that the just blanked stem doesn't sqeeuze the too much
-tie, we also lengthen the stem, by setting the @code{length} to
+To make sure that the just-blanked stem doesn't squeeze the tie too much,
+we also lengthen the stem, by setting the @code{length} to
@code{8},
@lilypond[quote,fragment,relative=2,verbatim]
@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 @ruser{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
@item
Alter the horizontal spacing via @code{SpacingSpanner}. See
-@ref{Changing horizontal spacing} for more details.
+@ruser{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
-@ref{Interfaces for programmers}.
+of this, see the @ruser{Scheme tutorial}, and
+@ruser{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
\override Score.PaperColumn #'keep-inside-line = ##t
@end example
+@c see issue 246
+In some cases, this must be done before @code{\override} commands
+can be processed.
+
+@verbatim
+\new Score \with {
+ \override PaperColumn #'keep-inside-line = ##t
+ } {
+ ..
+}
+@end verbatim
+
+
projects / lilypond.git / blobdiff