@code{#(ly:set-option 'point-and-click #f)}.
@item
-A @code{\header} block. This sets the global (i.e. the top of
+A @code{\header} block. This sets the global (i.e., the top of
file) header block. This is the block containing the default
settings of titling fields like composer, title, etc. for all
books within the file (see @ref{Titles explained}).
@item Around every opening and closing curly bracket.
-@item After every command or variable, i.e. every item that
+@item After every command or variable, i.e., every item that
begins with a @code{\} sign.
@item After every item that is to be interpreted as a Scheme
-expression, i.e. every item that begins with a @code{#}@tie{}sign.
+expression, i.e., every item that begins with a @code{#}@tie{}sign.
@item To separate all elements of a Scheme expression.
@code{\paper} block, using the following syntax:
@example
-@code{variable} = @code{\markup} @{
+variable = \markup @{
@dots{}
- @code{\on-the-fly} \@var{procedure} @var{markup}
+ \on-the-fly \@var{procedure} @var{markup}
@dots{}
@}
@end example
The @var{procedure} is called each time the @code{\markup} command
in which it appears is evaluated. The @var{procedure} should test
-for a particular condition and interpret (i.e. print) the
+for a particular condition and interpret (i.e., print) the
@var{markup} argument if and only if the condition is true.
A number of ready-made procedures for testing various conditions are
@q{and} operation, for example,
@example
- @code{\on-the-fly \first-page}
- @code{\on-the-fly \last-page}
+ \on-the-fly \first-page
+ \on-the-fly \last-page
@code{@{ \markup @dots{} \fromproperty #'header: @dots{} @}}
@end example
In addition to being shown in the printed output, @code{\header} variables
are also used to set PDF metadata (the information displayed by PDF readers
-as the @code{properties} of the PDF file). For example, setting the
-@code{title} property of the @code{header} block @q{Symphony I} will also give
-this title to the PDF document.
+as the @code{properties} of the PDF file). As metadata are applied per
+output file, only @code{\header} blocks located at top level or within an
+explicit @code{\book} block will be used to generate PDF metadata; while
+@code{\header} variables in a @code{\bookpart} or @code{\score} block
+will be reflected in the printed output of the respective blocks, the
+document-wide PDF metadata will not be affected by headers at that level.
+
+For example, setting the @code{title} property of the @code{header} block
+@q{Symphony I} will also give this title to the PDF document.
@example
- @code{\header@{}
- @code{title = "Symphony I"}
- @code{@}}
+\header@{
+ title = "Symphony I"
+@}
@end example
If you want to set the title of the printed output to one value, but have the
@code{pdftitle}, as below.
@example
- @code{\header@{}
- @code{title = "Symphony I"}
- @code{pdftitle = "Symphony I by Beethoven"}
- @code{@}}
+\header@{
+ title = "Symphony I"
+ pdftitle = "Symphony I by Beethoven"
+@}
@end example
The variables @code{title}, @code{subject}, @code{keywords},
@item Context
is the context in which the grob being footnoted is created. It
-may be omitted if the grob is in a bottom context, e.g. a
+may be omitted if the grob is in a bottom context, e.g., a
@code{Voice} context.
@item GrobName
are valid LilyPond identifiers (alphabetic characters only, no
numbers, underscores, or dashes) which cannot be confused with notes,
the @code{#'} may be omitted and, as a shorthand, a list of symbols
-can use the dot separator: i.e. @code{\tag #'(violinI violinII)} can
+can use the dot separator: i.e., @code{\tag #'(violinI violinII)} can
be written @code{\tag violinI.violinII}. The same applies to
@code{\keepWithTag} and @code{\removeWithTag}.
(assuming 4/4 time signature) of every @code{\score} in the input
file. For longer pieces, rendering only a small part is often an order
of magnitude quicker than rendering it completely. When working on the
-beginning of a score you have already typeset (e.g. to add a new part),
+beginning of a score you have already typeset (e.g., to add a new part),
the @code{showFirstLength} property may be useful as well.
Skipping parts of a score can be controlled in a more fine-grained
@noindent
The c will take the value of a crotchet.
-@item Ornaments (i.e. mordents, trills and turns et al.)
+@item Ornaments (i.e., mordents, trills and turns et al.)
@item Rallentando, accelerando, ritardando and a tempo
@item Slurs, including phrasing slurs
@item Tenuto
@item Glissandi
@item Falls and doits
@item Microtonal chords
-@item Rhythms entered as annotations, e.g. swing
-@item Tempo changes without @code{\tempo} (e.g. entered as annotations)
+@item Rhythms entered as annotations, e.g., swing
+@item Tempo changes without @code{\tempo} (e.g., entered as annotations)
@item Tremolos that @emph{are} entered with a @q{@code{:}[@var{number}]}
value
@end itemize
@}
@end example
-@warning{ A @code{@bs{}score} block that, as well as the music, contains
-only a @code{@bs{}midi} block (i.e. @emph{without} the @code{@bs{}layout}
+@warning{A @code{@bs{}score} block that, as well as the music, contains
+only a @code{@bs{}midi} block (i.e., @emph{without} the @code{@bs{}layout}
block), will only produce MIDI output files. No notation will be
printed.}
projects / lilypond.git / blobdiff