@node Objects and interfaces
@subsection Objects and interfaces
-@cindex objects
-@cindex grobs
-@cindex spanners
-@cindex interfaces
+@cindex object
+@cindex grob
+@cindex spanner
+@cindex interface
+@cindex properties, object
+@cindex object properties
+@cindex layout object
+@cindex object, layout
+@cindex interface
Tweaking involves modifying the internal operation and structures
of the LilyPond program, so we must first introduce some terms
note heads, ties, dynamics, etc. Every object has its own set of
property values.
-Some types of object are given special names. Objects which
-represent items of notation on the printed output such as
- note heads, stems, slurs, ties, fingering, clefs, etc are called
-@q{Layout objects}, often known as @q{Graphical Objects}, or
-@q{Grobs} for short. These are still objects in the generic sense
-above, and so they too all have properties associated with them,
-such as their position, size, color, etc.
+Some types of object are given special names. Objects which represent
+items of notation on the printed output such as note heads, stems,
+slurs, ties, fingering, clefs, etc are called @q{Layout objects},
+often known as @q{Graphical Objects}, or @q{Grobs} for short. These
+are still objects in the generic sense above, and so they too all have
+properties associated with them, such as their position, size, color,
+etc.
Some layout objects are still more specialized. Phrasing slurs,
crescendo hairpins, ottava marks, and many other grobs are not
shape. Objects with an extended shape like these are called
@q{Spanners}.
-It remains to explain what @q{Interfaces} are. Many objects,
-even though they are quite different, share common features
-which need to be processed in the same way.
-For example, all grobs have a color, a size, a position, etc,
-and all these properties are processed in the same way during
-LilyPond's
-interpretation of the input file. To simplify these internal
-operations these common actions and properties are grouped
-together in an object called a @code{grob-interface}. There
-are many other groupings of common properties like this, each
-one given a name ending in @code{interface}. In total there
-are over 100 such interfaces. We shall see later why this is
-of interest and use to the user.
+It remains to explain what @q{Interfaces} are. Many objects, even
+though they are quite different, share common features which need to
+be processed in the same way. For example, all grobs have a color, a
+size, a position, etc, and all these properties are processed in the
+same way during LilyPond's interpretation of the input file. To
+simplify these internal operations these common actions and properties
+are grouped together in an object called a @code{grob-interface}.
+There are many other groupings of common properties like this, each
+one given a name ending in @code{interface}. In total there are over
+100 such interfaces. We shall see later why this is of interest and
+use to the user.
These, then, are the main terms relating to objects which we
shall use in this chapter.
@node Naming conventions of objects and properties
@subsection Naming conventions of objects and properties
+@cindex naming conventions for objects
+@cindex naming conventions for properties
+@cindex objects, naming conventions
+@cindex properties, naming conventions
+
We met some object naming conventions previously, in
@ref{Contexts and engravers}. Here for reference is a list
of the most common object and property types together with
@node Tweaking methods
@subsection Tweaking methods
+@cindex tweaking methods
+
@strong{\override command}
@cindex override command
+@cindex override syntax
+
@funindex \override
+@funindex override
-We have already met the commands @code{\set} and @code{\with},
-used to change the properties of @strong{contexts} and to remove
-and add @strong{engravers}, in
-@ref{Modifying context properties}, and @ref{Adding
-and removing engravers}. We now must meet some more important
-commands.
+We have already met the commands @code{\set} and @code{\with}, used to
+change the properties of @strong{contexts} and to remove and add
+@strong{engravers}, in @ref{Modifying context properties}, and
+@ref{Adding and removing engravers}. We now must meet some more
+important commands.
The command to change the properties of @strong{layout objects} is
@code{\override}. Because this command has to modify
The general syntax of this command is:
@example
-\override @var{Context}.@var{LayoutObject} #'@var{layout-property} = #@var{value}
+\override @var{Context}.@var{LayoutObject} #'@var{layout-property} =
+#@var{value}
@end example
@noindent
-This will set the property with the name @var{layout-property}
-of the layout object with the name
-@var{LayoutObject}, which is a member of the @var{Context}
-context, to the value @var{value}.
+This will set the property with the name @var{layout-property} of the
+layout object with the name @var{LayoutObject}, which is a member of
+the @var{Context} context, to the value @var{value}.
The @var{Context} can be omitted (and usually is) when the
required context is unambiguously implied and is one of lowest
@strong{\revert command}
@cindex revert command
+
@funindex \revert
+@funindex revert
Once overridden, the property retains its new value until it is
overridden again or a @code{\revert} command is encountered.
@strong{\once prefix}
+@funindex \once
+@funindex once
+
Both the @code{\override} and the @code{\set} commands may be
prefixed by @code{\once}. This causes the following
@code{\override} or @code{\set} command to be effective only
@strong{\overrideProperty command}
@cindex overrideProperty command
+
@funindex \overrideProperty
+@funindex overrideProperty
There is another form of the override command,
@code{\overrideProperty}, which is occasionally required.
@strong{\tweak command}
@cindex tweak command
+
@funindex \tweak
+@funindex tweak
The final tweaking command which is available is @code{\tweak}.
This should be used to change the properties of objects which
@cindex bracket, tuplet
@cindex tuplet bracket
@cindex triplet bracket
+
@funindex TupletBracket
The @code{\tweak} command must also be used to change the
@cindex properties of grobs
@cindex grobs, properties of
@cindex layout objects, properties of
+@cindex Internals Reference manual
Suppose you have a slur in a score which, to your mind,
appears too thin and you'd like to draw it a little heavier.
which follow.
@subheading Finding the context
+
@cindex context, finding
+@cindex context, identifying correct
But first, what if we had needed to specify the Context?
What should it be? We could guess that slurs are in
@cindex overriding once only
@cindex once override
-@funindex \once
-As you can see, @emph{all} the slurs are thicker in the
-final example above. But what if we
-wanted just the first slur to be thicker? This is achieved
-with the @code{\once} command. Placed immediately before
-the @code{\override} command it causes it to change only the
-slur which begins on the @strong{immediately following} note.
-If the
-immediately following note does not begin a slur the command
-has no effect at all -- it is not remembered until a slur
-is encountered, it is simply discarded. So the command with
-@code{\once} must be
+@funindex \once
+@funindex once
+
+As you can see, @emph{all} the slurs are thicker in the final example
+above. But what if we wanted just the first slur to be thicker? This
+is achieved with the @code{\once} command. Placed immediately before
+the @code{\override} command it causes it to change only the slur
+which begins on the @strong{immediately following} note. If the
+immediately following note does not begin a slur the command has no
+effect at all -- it is not remembered until a slur is encountered, it
+is simply discarded. So the command with @code{\once} must be
repositioned as follows:
@lilypond[quote,verbatim,relative=2]
@subheading Reverting
@cindex revert
-@cindex default properties, reverting
+@cindex default properties, reverting to
+
@funindex \revert
+@funindex revert
Finally, what if we wanted just the first two slurs to be
heavier? Well, we could use two commands, each preceded by
@end lilypond
@noindent
-or we could omit the @code{\once} command and use the
-@code{\revert} command
-to return the @code{thickness} property to its default value
+or we could omit the @code{\once} command and use the @code{\revert}
+command to return the @code{thickness} property to its default value
after the second slur:
@lilypond[quote,verbatim,relative=2]
@node Properties found in interfaces
@subsection Properties found in interfaces
+@cindex interface
@cindex interface properties
@cindex properties in interfaces
-Suppose now that we wish to print the lyrics in italics. What
-form of @code{\override} command do we need to do this?
-We first look in the IR page listing @q{All layout objects}, as
-before, and look for an object that might control lyrics. We
-find @code{LyricText}, which looks right. Clicking on this shows
-the settable properties for lyric text. These include the
-@code{font-series} and @code{font-size}, but nothing that might
-give an italic shape.
-This is because the shape property is one that is common to all
-font objects, so, rather than including it in every layout
-object, it is grouped together with other similar common
-properties and placed in an @strong{Interface}, the
+Suppose now that we wish to print the lyrics in italics. What form of
+@code{\override} command do we need to do this? We first look in the
+IR page listing @q{All layout objects}, as before, and look for an
+object that might control lyrics. We find @code{LyricText}, which
+looks right. Clicking on this shows the settable properties for lyric
+text. These include the @code{font-series} and @code{font-size}, but
+nothing that might give an italic shape. This is because the shape
+property is one that is common to all font objects, so, rather than
+including it in every layout object, it is grouped together with other
+similar common properties and placed in an @strong{Interface}, the
@code{font-interface}.
So now we need to learn how to find the properties of interfaces,
including @code{font-shape(symbol)}, where @code{symbol} can be
set to @code{upright}, @code{italics} or @code{caps}.
-You will notice that @code{font-series} and @code{font-size}
-are also listed there.
-This immediately raises the question: Why are the common font
-properties @code{font-series} and @code{font-size} listed under
-@code{LyricText} as well as under the interface
-@code{font-interface} but @code{font-shape} is not? The answer
-is that @code{font-series} and @code{font-size} are changed
-from their global default values when a @code{LyricText} object
-is created, but @code{font-shape} is not. The entries in
-@code{LyricText} then tell you the values for those two
-properties which apply to @code{LyricText}. Other objects
-which support @code{font-interface} will set these
-properties differently when they are created.
+You will notice that @code{font-series} and @code{font-size} are also
+listed there. This immediately raises the question: Why are the
+common font properties @code{font-series} and @code{font-size} listed
+under @code{LyricText} as well as under the interface
+@code{font-interface} but @code{font-shape} is not? The answer is
+that @code{font-series} and @code{font-size} are changed from their
+global default values when a @code{LyricText} object is created, but
+@code{font-shape} is not. The entries in @code{LyricText} then tell
+you the values for those two properties which apply to
+@code{LyricText}. Other objects which support @code{font-interface}
+will set these properties differently when they are created.
Let's see if we can now construct the @code{\override} command
to change the lyrics to italics. The object is @code{LyricText},
and the lyrics are all printed in italics.
@subheading Specifying the context in lyric mode
+
@cindex context, specifying in lyric mode
+@cindex lyric mode, specifying context
In the case of lyrics, if you try specifying the context in the
format given earlier the command will fail. A syllable
@node Types of properties
@subsection Types of properties
-@cindex Property types
+@cindex property types
So far we have seen two types of property: @code{number} and
@code{symbol}. To be valid, the value given to a property
describing that grob, and those properties may be viewed by looking at
those interfaces.
-We explained how to find information about grobs in
-@ref{Properties of layout objects}. Using the same approach,
-we go to the IR to find the layout object which prints
-bar lines. Going via @emph{Backend} and @emph{All layout objects}
-we find there
-is a layout object called @code{BarLine}. Its properties include
-two that control its visibility: @code{break-visibility} and
-@code{stencil}. Barline also supports a number of interfaces,
-including the @code{grob-interface}, where we find the
-@code{transparent} and the @code{color} properties. All
-of these can affect the visibility of bar lines (and, of course,
-by extension, many other layout objects too.) Let's consider
-each of these in turn.
+We explained how to find information about grobs in @ref{Properties of
+layout objects}. Using the same approach, we go to the IR to find the
+layout object which prints bar lines. Going via @emph{Backend} and
+@emph{All layout objects} we find there is a layout object called
+@code{BarLine}. Its properties include two that control its
+visibility: @code{break-visibility} and @code{stencil}. Barline also
+supports a number of interfaces, including the @code{grob-interface},
+where we find the @code{transparent} and the @code{color} properties.
+All of these can affect the visibility of bar lines (and, of course,
+by extension, many other layout objects too.) Let's consider each of
+these in turn.
@subheading stencil
+
@cindex stencil property
This property controls the appearance of the bar lines by specifying
}
@end lilypond
-The bar lines are still printed. What is wrong? Go back to the
-IR and look again at the page giving the properties of BarLine.
-At the top of the page it says @qq{Barline objects are created
-by: Bar_engraver}. Go to the @code{Bar_engraver} page.
-At the bottom
-it gives a list of Contexts in which the bar engraver operates.
-All of them are of the type @code{Staff}, so the reason the
-@code{\override} command failed to work as expected is because
-@code{Barline} is not in the default @code{Voice} context.
-If the context
-is specified wrongly, the command simply does not work. No
-error message is produced, and nothing is logged in the log
-file. Let's try correcting it by adding the correct context:
+The bar lines are still printed. What is wrong? Go back to the IR
+and look again at the page giving the properties of BarLine. At the
+top of the page it says @qq{Barline objects are created by:
+Bar_engraver}. Go to the @code{Bar_engraver} page. At the bottom it
+gives a list of Contexts in which the bar engraver operates. All of
+them are of the type @code{Staff}, so the reason the @code{\override}
+command failed to work as expected is because @code{Barline} is not in
+the default @code{Voice} context. If the context is specified
+wrongly, the command simply does not work. No error message is
+produced, and nothing is logged in the log file. Let's try correcting
+it by adding the correct context:
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
{
@cindex break-visibility property
We see from the @code{BarLine} properties in the IR that the
-@code{break-visibility} property requires a vector of three
-booleans.
-These control respectively whether bar lines are printed at
-the end of a line, in the middle of lines, and at the beginning
-of lines. For our example we want all bar lines to be suppressed,
-so the value we need is @code{'#(#f #f #f)}.
-Let's try that, remembering
-to include the @code{Staff} context. Note also that in writing
-this value we have @code{#'#} before the opening bracket.
-The @code{'#} is required as part of the value to introduce a
-vector, and the first @code{#} is required, as always, to precede
-the value itself in the @code{\override} command.
+@code{break-visibility} property requires a vector of three booleans.
+These control respectively whether bar lines are printed at the end of
+a line, in the middle of lines, and at the beginning of lines. For
+our example we want all bar lines to be suppressed, so the value we
+need is @code{'#(#f #f #f)}. Let's try that, remembering to include
+the @code{Staff} context. Note also that in writing this value we
+have @code{#'#} before the opening bracket. The @code{'#} is required
+as part of the value to introduce a vector, and the first @code{#} is
+required, as always, to precede the value itself in the
+@code{\override} command.
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
{
And we see this too removes all the bar lines.
@subheading transparent
-@cindex transparent property
-We see from the properties specified in the @code{grob-interface}
-page in the IR that the @code{transparent} property is a boolean.
-This
-should be set to @code{#t} to make the grob transparent.
-In this next example let us make the time signature invisible
-rather than the bar lines.
-To do this we need to find the grob name for the time signature.
-Back to
-the @q{All layout objects} page in the IR to find the properties
-of the @code{TimeSignature} layout object. This is produced by
-the @code{Time_signature_engraver} which you can check also lives
-in the @code{Staff} context and also supports the
+@cindex transparent property
+@cindex transparency
+
+We see from the properties specified in the @code{grob-interface} page
+in the IR that the @code{transparent} property is a boolean. This
+should be set to @code{#t} to make the grob transparent. In this next
+example let us make the time signature invisible rather than the bar
+lines. To do this we need to find the grob name for the time
+signature. Back to the @q{All layout objects} page in the IR to find
+the properties of the @code{TimeSignature} layout object. This is
+produced by the @code{Time_signature_engraver} which you can check
+also lives in the @code{Staff} context and also supports the
@code{grob-interface}. So the command to make the time signature
transparent is:
leaves it where it is, but makes it invisible.
@subheading color
+
@cindex color property
Finally let us try making the bar lines invisible by coloring
@cindex color, X11
@cindex X11 colors
+@funindex x11-color
+
The second way of changing the color is to use the list of
X11 color names in the second list in @ruser{List of colors}.
However, these must be preceded by another function, which
@cindex rgb colors
@cindex color, rgb
+@funindex rgb-color
+
There is yet a third function, one which converts RGB values into
internal colors -- the @code{rgb-color} function. This takes
three arguments giving the intensities of the red, green and
@node Size of objects
@subsection Size of objects
+@cindex changing size of objects
+@cindex size of objects
+@cindex objects, size of
+@cindex objects, changing size of
+
Let us begin by looking again at the earlier example
see @ref{Nesting music expressions}) which showed
how to introduce a new temporary staff, as in an @rglos{ossia}.
@code{\with} clause, or if none have been set there, the normal
default values.
-Some context properties
-can be modified only in @code{\with} clauses. These are those
-properties which cannot sensibly be changed after the context
-has been created. @code{alignAboveContext} and its partner,
-@code{alignBelowContext}, are two such properties -- once the
-staff has been created its alignment is decided and it would
-make no sense to try to change it later.
+Some context properties can be modified only in @code{\with} clauses.
+These are those properties which cannot sensibly be changed after the
+context has been created. @code{alignAboveContext} and its partner,
+@code{alignBelowContext}, are two such properties -- once the staff
+has been created its alignment is decided and it would make no sense
+to try to change it later.
The default values of layout object properties can also be set
in @code{\with} clauses. Simply use the normal @code{\override}
Finally we come to changing the size of layout objects.
-Some layout objects are created as glyphs selected from
-a typeface font. These include note heads, accidentals, markup,
-clefs, time signatures, dynamics and lyrics.
-Their size is changed by modifying the
-@code{font-size} property, as we shall shortly see. Other
-layout objects such as slurs and ties -- in general, spanner
-objects -- are drawn individually, so there is no
-@code{font-size}
-associated with them. These objects generally derive their
-size from the objects to which they are attached, so usually
-there is no need to change their size manually. Still other
-properties such as the length of stems and bar lines, thickness
-of beams and other lines, and the separation of staff lines all
-need to be modified in special ways.
+Some layout objects are created as glyphs selected from a typeface
+font. These include note heads, accidentals, markup, clefs, time
+signatures, dynamics and lyrics. Their size is changed by modifying
+the @code{font-size} property, as we shall shortly see. Other layout
+objects such as slurs and ties -- in general, spanner objects -- are
+drawn individually, so there is no @code{font-size} associated with
+them. These objects generally derive their size from the objects to
+which they are attached, so usually there is no need to change their
+size manually. Still other properties such as the length of stems and
+bar lines, thickness of beams and other lines, and the separation of
+staff lines all need to be modified in special ways.
Returning to the ossia example, let us first change the font-size.
We can do this in two ways. We can either change the size of the
@node Length and thickness of objects
@subsection Length and thickness of objects
-@cindex Distances
-@cindex Thickness
-@cindex Length
+@cindex distances
+@cindex thickness
+@cindex length
@cindex magstep
@cindex size, changing
@cindex stem length, changing
@end lilypond
@noindent
-Since the length of stems and many other length-related properties
-are always calculated relative to the
-value of the @code{staff-space} property these are automatically
-scaled down in length too. Note that this affects only the
-vertical scale of the ossia -- the horizontal scale is determined
-by the layout of the main music in order to remain synchronized
-with it, so it is not affected by any of these changes in size.
-Of course, if the scale of all the main music were changed in this
-way then the horizontal spacing would be affected. This is
+Since the length of stems and many other length-related properties are
+always calculated relative to the value of the @code{staff-space}
+property these are automatically scaled down in length too. Note that
+this affects only the vertical scale of the ossia -- the horizontal
+scale is determined by the layout of the main music in order to remain
+synchronized with it, so it is not affected by any of these changes in
+size. Of course, if the scale of all the main music were changed in
+this way then the horizontal spacing would be affected. This is
discussed later in the layout section.
This, then, completes the creation of an ossia. The sizes and
@menu
* Automatic behavior::
* Within-staff objects::
-* Outside staff objects::
+* Outside-staff objects::
@end menu
@node Automatic behavior
@subsection Automatic behavior
+@cindex within-staff objects
+@cindex outside-staff objects
+@cindex objects, within-staff
+@cindex objects, outside-staff
+
There are some objects in musical notation that belong to
the staff and there are other objects that should be
placed outside the staff. These are called within-staff
right or left when they point up or down. This is controlled
automatically when @code{direction} is set.
-The following example shows in bar 1 the default behavior of
-stems,
-with those on high notes pointing down and those on low notes
-pointing up, followed by four notes with all stems forced down,
-four notes with all stems forced up, and finally four notes
-reverted back to the default behavior.
+@cindex down
+@cindex up
+@cindex center
+@cindex neutral
+
+The following example shows in bar 1 the default behavior of stems,
+with those on high notes pointing down and those on low notes pointing
+up, followed by four notes with all stems forced down, four notes with
+all stems forced up, and finally four notes reverted back to the
+default behavior.
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
a4 g c a
@code{UP} for stems, but for some objects it means @q{center}.
There is a constant, @code{CENTER} which has the value @code{0}.
-However, these explicit overrides are not usually used, as there
-are simpler equivalent predefined commands available.
-Here is a table of the commonest. The meaning of each is stated
-where it is not obvious.
+However, these explicit overrides are not usually used, as there are
+simpler equivalent predefined commands available. Here is a table of
+the commonest. The meaning of each is stated where it is not obvious.
@multitable @columnfractions .2 .2 .25 .35
@headitem Down/Left
@code{\xxxNeutral} command.
@subheading Fingering
+
@cindex fingering, placement
+@cindex fingering, chords
The placement of fingering is also affected by the value
of its @code{direction} property, but there are special
c-5 a-3 f-1 c'-5
@end lilypond
-This is how to control fingering on single notes, but the
-@code{direction}
-property is ignored for chords. Instead, by default, the
-fingering is automatically placed both above and below the
-notes of a chord, as shown:
+This is how to control fingering on single notes, but the
+@code{direction} property is ignored for chords. Instead, by default,
+the fingering is automatically placed both above and below the notes
+of a chord, as shown:
@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
<c-5 g-3>
< c-1 e-2 g-3 b-5 > 4
@end lilypond
-@node Outside staff objects
-@subsection Outside staff objects
+@node Outside-staff objects
+@subsection Outside-staff objects
Outside-staff objects are automatically placed to avoid collisions.
Objects with the lower value of the @code{outside-staff-priority}
these.
@cindex text spanner
+@cindex ottava bracket
+
@funindex \startTextSpan
+@funindex startTextSpan
@funindex \stopTextSpan
-@cindex ottava bracket
+@funindex stopTextSpan
+
@lilypond[quote,fragment,ragged-right,verbatim,relative=1]
% Set details for later Text Spanner
It also shows how ottava brackets are created.
-Note that bar numbers, metronome marks and rehearsal marks
-are not shown. By default these are created in the
-@code{Score} context and their @code{outside-staff-priority}
-is ignored relative to the layout objects which are created
-in the @code{Staff} context.
-If you wish to place bar numbers, metronome marks or rehearsal
-marks in accordance with the value of their
-@code{outside-staff-priority} the @code{Bar_number_engraver},
-@code{Metronome_mark_engraver} or @code{Mark_engraver} respectively
-should be removed from the @code{Score} context and placed in the
-top @code{Staff} context. If this is done, these marks will be
-given the following default @code{outside-staff-priority} values:
+@cindex tweaking bar number placement
+@cindex bar numbers, tweaking placement
+@cindex tweaking metronome mark placement
+@cindex metronome mark, tweaking placement
+@cindex tweaking rehearsal mark placement
+@cindex rehearsal marks, tweaking placement
+
+Note that bar numbers, metronome marks and rehearsal marks are not
+shown. By default these are created in the @code{Score} context and
+their @code{outside-staff-priority} is ignored relative to the layout
+objects which are created in the @code{Staff} context. If you wish to
+place bar numbers, metronome marks or rehearsal marks in accordance
+with the value of their @code{outside-staff-priority} the
+@code{Bar_number_engraver}, @code{Metronome_mark_engraver} or
+@code{Mark_engraver} respectively should be removed from the
+@code{Score} context and placed in the top @code{Staff} context. If
+this is done, these marks will be given the following default
+@code{outside-staff-priority} values:
@multitable @columnfractions .3 .3
@headitem Layout Object @tab Priority
@item @code{BarNumber} @tab @code{ 100}
@end multitable
-If the default values of @code{outside-staff-priority} do not
-give you the placing you want, the priority of any of the objects
-may be overridden. Suppose we would
-like the ottava bracket to be placed below the text spanner in the
-example above. All we need to do is to look up the priority of
-@code{OttavaBracket} in the IR or in the tables above, and reduce
-it to a value lower than that of a @code{TextSpanner}, remembering
-that @code{OttavaBracket} is created in the @code{Staff} context:
+If the default values of @code{outside-staff-priority} do not give you
+the placing you want, the priority of any of the objects may be
+overridden. Suppose we would like the ottava bracket to be placed
+below the text spanner in the example above. All we need to do is to
+look up the priority of @code{OttavaBracket} in the IR or in the
+tables above, and reduce it to a value lower than that of a
+@code{TextSpanner}, remembering that @code{OttavaBracket} is created
+in the @code{Staff} context:
@lilypond[quote,fragment,ragged-right,verbatim,relative=1]
% Set details for later Text Spanner
c^"Text4"
@end lilypond
-This certainly lifts @qq{Text3} above @qq{Text4} but it also
-lifts it above @qq{Text2}, and @qq{Text4} now drops down.
-Perhaps this is not so good. What we would really like to do
-is to position all the annotation at the same distance above
-the staff? To do this, we clearly
-will need to space the notes out horizontally to make more
+This certainly lifts @qq{Text3} above @qq{Text4} but it also lifts it
+above @qq{Text2}, and @qq{Text4} now drops down. Perhaps this is not
+so good. What we would really like to do is to position all the
+annotation at the same distance above the staff. To do this, we
+clearly will need to space the notes out horizontally to make more
room for the text. This is done using the @code{textLengthOn}
command.
@subheading \textLengthOn
-@funindex \textLengthOn
@cindex notes, spreading out with text
+@funindex \textLengthOn
+@funindex textLengthOn
+@funindex \textLengthOff
+@funindex textLengthOff
+
By default, text produced by markup takes up no horizontal space
as far as laying out the music is concerned. The @code{\textLengthOn}
command reverses this behavior, causing the notes to be spaced
@code{\override}, @code{\set}, @code{\revert} or @code{unset},
so cannot be used with @code{\textLengthOn}.
+@cindex markup text, allowing collisions
+
Markup text will also avoid notes which project above the staff.
If this is not desired, the automatic displacement upwards may
be turned off by setting the priority to @code{#f}. Here's an
@subheading Dynamics
+@cindex tweaking dynamics placement
+@cindex dynamics, tweaking placement
+
Dynamic markings will normally be positioned beneath the
staff, but may be positioned above with the @code{dynamicUp}
command. They will be positioned vertically relative to the
@end lilypond
@noindent
-Should a similar situation arise in @q{real} music, it may
-be preferable to space out the notes
-a little further, so the dynamic markings can all fit at the
-same vertical distance from the staff. We were able to do this
-for markup text by using the @code{\textLengthOn} command, but there
-is no equivalent command for dynamic marks. So we shall have to
-work out how to do this using @code{\override} commands.
-
+Should a similar situation arise in @q{real} music, it may be
+preferable to space out the notes a little further, so the dynamic
+markings can all fit at the same vertical distance from the staff. We
+were able to do this for markup text by using the @code{\textLengthOn}
+command, but there is no equivalent command for dynamic marks. So we
+shall have to work out how to do this using @code{\override} commands.
+@c START HERE
@subheading Grob sizing
@cindex grob sizing
projects / lilypond.git / blobdiff