version that you are working on. See TRANSLATION for details.
@end ignore
-@c \version "2.11.61"
+@c \version "2.11.51"
@node Tweaking output
@chapter Tweaking output
So now we need to learn how to find the properties of interfaces,
and to discover what objects use these interface properties.
-Look again at the IR page which describes LyricText. At the bottom of
-the page is a list of clickable interfaces which LyricText supports.
-The list has several items, including @code{font-interface}. Clicking
-on this brings up the properties associated with this interface, which
-are also properties of all the objects which support it, including
-LyricText.
+Look again at the IR page which describes LyricText. At the
+bottom of the page is a list of clickable (in the html versions
+of the IR) interfaces which LyricText supports. The list has
+seven items, including @code{font-interface}.
+Clicking on this brings up the properties associated
+with this interface, which are also properties of all the objects
+which support it, including LyricText.
Now we see all the user-settable properties which control fonts,
including @code{font-shape(symbol)}, where @code{symbol} can be
the property is @code{font-shape} and the value is
@code{italic}. As before, we'll omit the context.
-As an aside, although it is an important one, note that because the
-values of @code{font-shape} are symbols they must be introduced with a
-single apostrophe, @code{'}. That is why apostrophes are needed
-before @code{thickness} in the earlier example and @code{font-shape}.
-These are both symbols too. Symbols are then read internally by
-LilyPond. Some of them are the names of properties, like
-@code{thickness} or @code{font-shape}, others are used as values that
-can be given to properties, like @code{italic}. Note the distinction
-from arbitrary text strings, which would appear as @code{"a text
-string"}; for more details about symbols and strings, see @ref{Scheme
-tutorial}.
+As an aside, although it is an important one, note that because
+the values of
+@code{font-shape} are symbols they must be introduced with a
+single apostrophe, @code{'}. That is why apostrophes
+are needed before @code{thickness} in the earlier example
+and @code{font-shape}. These are both symbols too.
+Symbols are special names which are known internally to
+LilyPond. Some of them are the names of properties,
+like @code{thickness} or @code{font-shape}, others are in
+effect special values that can be given to properties, like
+@code{italic}. Note the distinction from arbitrary
+text strings, which would appear as @code{"a text string"}.
Ok, so the @code{\override} command we need to print the lyrics
in italics should be
@warning{In overrides in lyrics always place spaces around
the dot between the context name and the object name.}
-@seealso
-
-Learning Manual: @ref{Scheme tutorial}.
-
-
@node Types of properties
@subsection Types of properties
@tab A positive decimal number (in units of staff space)
@tab @code{2.5}, @code{0.34}
@item Direction
- @tab A valid direction constant or its numerical equivalent (decimal
-values between -1 and 1 are allowed)
+ @tab A valid direction constant or its numerical equivalent
@tab @code{LEFT}, @code{CENTER}, @code{UP},
@code{1}, @code{-1}
@item Integer
@tab A positive whole number
@tab @code{3}, @code{1}
@item List
- @tab A set of values separated by spaces, enclosed in parentheses
-and preceded by an apostrophe
+ @tab A bracketed set of items separated by spaces,
+preceded by an apostrophe
@tab @code{'(left-edge staff-bar)}, @code{'(1)},
@code{'(1.0 0.25 0.5)}
@item Markup
preceded by an apostrophe
@tab @code{'italic}, @code{'inside}
@item Unknown
- @tab A procedure, or @code{#f} to cause no action
+ @tab A procedure or @code{#f} (to cause no action)
@tab @code{bend::print}, @code{ly:text-interface::print},
@code{#f}
@item Vector
- @tab A list of three items enclosed in parentheses and preceded
+ @tab A list of three items enclosed in brackets and preceded
by apostrophe-hash, @code{'#}.
@tab @code{'#(#t #t #f)}
@end multitable
-@seealso
-
-Learning Manual: @ref{Scheme tutorial}.
-
-
@node Appearance of objects
@section Appearance of objects
in a piece of music. But the bar lines are normally inserted
automatically. How do we prevent them printing?
-Before we tackle this, let us remember that object properties are
-grouped in what are called @emph{interfaces} -- see @ref{Properties
-found in interfaces}. This is simply to group together those
-properties that may be used together to tweak a graphical object -- if
-one of them is allowed for an object, so are the others. Some objects
-then use the properties in some interfaces, others use them from other
-interfaces. The interfaces which contain the properties used by a
-particular grob are listed in the IR at the bottom of the page
-describing that grob, and those properties may be viewed by looking at
-those interfaces.
+Before we tackle this, let us remember that object properties
+are grouped in what are called @emph{interfaces} -- see
+@ref{Properties found in interfaces}. This is simply to
+group together those properties that are commonly required
+together -- if one of them is required for an object, so are
+the others. Some objects then need the properties in some
+interfaces, others need them from other interfaces. The
+interfaces which contain the properties required by a
+particular grob are listed in the IR at the bottom of the
+page 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,
projects / lilypond.git / blobdiff