Guide, node Updating translation committishes..
@end ignore
-@c \version "2.15.17"
+@c \version "2.15.39"
@node General input and output
@chapter General input and output
@end itemize
-
@seealso
Learning Manual:
@rlearning{How LilyPond input files work}.
Installed Files:
@file{ly/titling-init.ly}.
+
@node Default layout of headers and footers
@unnumberedsubsubsec Default layout of headers and footers
@ref{Title blocks explained},
@ref{Default layout of book and score title blocks}.
+
@node Creating footnotes
@subsection Creating footnotes
@node Footnotes overview
@unnumberedsubsubsec Footnotes overview
-Automatic footnotes create incrementing, numerical indicators and
-manual footnotes allow a custom indicator to be created instead. All
-grobs, top-level @code{\markup} and chorded notes can be annotated.
+Automatic footnotes create incrementing numerical indicators and manual
+footnotes allow a custom indicator to be created instead. Footnotes are
+normally applied like @code{\tweak} and consequently can be placed
+directly on grobs (graphical objects) created by most music elements and
+post-events. In cases where this does not work (like with bar lines and
+meter changes, where the grobs are produced as a consequence of property
+changes), footnotes can also be specified as a standalone music event
+affecting all grobs of a given type at a particular time step.
-The order in which each grob is drawn determines the order in which each
-indicator and so footnotes are created during compilation.
+The full form of a footnote command is
+
+@example
+\footnote @var{mark} @var{offset} @var{grob-name} @var{footnote}
+@var{music}
+@end example
+The elements are as follows:
+
+@table @var
+@item mark
+is a markup or string specifying the footnote mark which is used for
+both marking the reference point as well as the footnote itself at the
+bottom of the page. It can be omitted (or equivalently replaced with
+@code{\default}) in which case a number in sequence will be generated.
+@item offset
+is a number pair such as @samp{#(2 . 1)} specifying the X and Y offset
+from the reference point where the mark will be placed.
+@item grob-name
+specifies a type of grob to mark (like @samp{#'Flag}). If it is given,
+the respective grob will be used as a reference point even in case that
+its @q{cause} is not the referenced @var{music} itself but a grob
+created from it. It can be omitted (or replaced with @code{\default}),
+and then only a directly created grob will be annotated.
+@item footnote
+This markup or string specifies the footnote text to use at the bottom
+of the page.
+@item music
+This is the item, a music event or chord constituent or post-event, that
+is being annotated. While it cannot be omitted, it @emph{can} be
+replaced by @code{\default} in which case the footnote is not attached
+to a music expression in particular, but rather to a moment of time. It
+is mandatory in this case to use the @var{grob-name} argument for
+selecting an affected grob type, like @samp{#'TimeSignature}.
+@end table
+
+Like with @code{\tweak}, if your @code{\footnote} is applied to a
+post-event or articulation, it will itself have to be preceded with
+@code{-} to make the parser attach the result to the preceding note or
+rest.
@node Automatic footnotes
@unnumberedsubsubsec Automatic footnotes
-Of the two commands used to create automatic footnotes, use
-@code{\autoFootnoteGrob} for individual grobs (i.e. note heads, stems,
-slurs, dynamics and @code{\markup} when using @code{TextScripts});
-and @code{\autoFootnote} for annotating chorded notes.
-
-Both commands take three arguments; the @var{Layout Object} to be
-annotated, the @var{(x . y)} position of the indicator and a
-@code{\markup} that will appear in the footnote at the bottom of the
-page.
-
-The command @code{\autoFootnoteGrob} must come @emph{before} the grob
-that the footnote is being attached to:
+Automatic footnotes take four arguments: the @samp{(x . y)} position of
+the indicator, the optional @var{grob-name} specifying the layout object
+to be annotated, the @var{footnote} markup itself that will appear at
+the bottom of the page, and of course the @var{music} to attach the
+footnote to.
@lilypond[verbatim,quote,ragged-right,papersize=a8]
\book {
\header { tagline = ##f }
\relative c' {
- \autoFootnoteGrob #'NoteHead #'(0.5 . -2)
+ \footnote #'(0.5 . -2)
\markup { The first note }
a'4 b8
- \autoFootnoteGrob #'NoteHead #'(0.5 . 1)
+ \footnote #'(0.5 . 1) #'Flag
\markup { The third note }
- e c4 d4
+ e\noBeam c4 d4
}
}
@end lilypond
-To annotate chorded notes, the @code{\autoFootnote} must come
-@emph{after} the note to which the footnote is being attached as a
-@code{TextScript}:
+Chorded notes pose no particular difficulty:
@lilypond[verbatim,quote,ragged-right,papersize=a8]
\book {
\header { tagline = ##f }
\relative c' {
<
- c-\autoFootnote #'(1 . -1.25) "Here is a C"
- es-\autoFootnote #'(2 . -0.25) \markup { \italic "An E-flat" }
- g-\autoFootnote #'(2 . 3) \markup { \bold "This is a G" }
+ \footnote #'(1 . -1.25) "Here is a C" c
+ \footnote #'(2 . -0.25) \markup { \italic "An E-flat" } es
+ \footnote #'(2 . 3) \markup { \bold "This is a G" } g
>1
}
}
are printed in order of descendancy; the higher the footnote, the
higher up in the list.}
-Here are some examples of automatically footnoted grobs, also showing
-the relative position of the footnotes to the tagline and copyright.
+Here are some more examples of footnoted grobs, also showing the
+relative position of the footnotes to the tagline and copyright.
@lilypond[verbatim,quote,ragged-right,papersize=a8]
\book {
\header { copyright = \markup { "Copyright 1970" } }
\relative c' {
- \autoFootnoteGrob #'DynamicText #'(-3 . 0)
- \markup { \bold Forte }
-
- \autoFootnoteGrob #'Slur #'(0 . 1.5)
- \markup { A slur }
- a'4\f(
-
- \autoFootnoteGrob #'Beam #'(0 . -2)
- \markup { Beam }
- b8)[ e]
-
- \autoFootnoteGrob #'Stem #'(1 . -1)
+ a'4-\footnote #'(-3 . 0) \markup { \bold Forte } \f
+ -\footnote #'(0 . 1.5) \markup { A slur } (
+ b8)-\footnote #'(0 . -2) \markup { Beam } [ e]
+ \footnote #'(1 . -1) #'Stem
\markup { \teeny { This is a stem } }
c4
-
- \autoFootnoteGrob #'AccidentalCautionary #'(0 . 0.5)
+ \footnote #'(0 . 0.5) #'AccidentalCautionary
\markup \italic { A cautionary accidental }
-
- \autoFootnoteGrob #'TextScript #'(0.5 . -0.5)
- \markup \italic { Slow Down }
- dis?4_"rit."
+ \footnote #'(1 . 1) "The note itself"
+ dis?4-\footnote #'(0.5 . -0.5) \markup \italic { Slow Down }
+ _"rit."
}
}
@end lilypond
@node Manual footnotes
@unnumberedsubsubsec Manual footnotes
-@funindex \footnote
-@funindex \footnoteGrob
@cindex footnotes, manual
-There are two commands used to create manual footnotes; @code{\footnote}
-for top-level @code{\markup} and chorded notes; and @code{\footnoteGrob}
-for individual grobs (and @code{\markup} when using @code{TextScripts}).
+Manually marked footnotes take an additional first markup argument
+@var{mark} for making the reference mark. In contrast to automatically
+generated footnote marks, they will not appear before the @var{footnote}
+markup at the bottom of the page: establishing the visual connection is
+left to the user. LilyPond will only make sure that the corresponding
+markup appears on the bottom of the same page.
-When annotating grobs, the @code{\footnote} command takes four
-arguments; the @var{Layout Object} to be annotated, the @var{(x . y)}
-position of the indicator and two @code{\markup} commands; the first is
-the indicator attached to the note or grob and the second is the
-footnote at the bottom of the page.
-
-The command @code{\footnoteGrob} must come @emph{after} the grob
-that the footnote footnote is annotating and attached as a
-@code{TextScript}:
+Other than that, the use is identical to that of automatically numbered
+footnotes.
@lilypond[verbatim,quote,ragged-right,papersize=a8]
\book {
\header { tagline = ##f }
\relative c' {
- a'4-\footnoteGrob #'NoteHead #'(0.5 . -2)
- "1" \markup { \italic "1. The first note" }
+ \footnote
+ "1" #'(0.5 . -2)
+ \markup { \italic "1. The first note" }
+ a'4
b8
- e-\footnoteGrob #'NoteHead #'(0.5 . 1)
- \markup { \bold "2" } "2. The second note"
+ \footnote
+ \markup { \bold "2" } #'(0.5 . 1)
+ "2. The second note"
+ e
c4
- d\p-\footnoteGrob #'DynamicText #'(0.5 . -1) "3" "3. Piano"
+ d-\footnote "3" #'(0.5 . -1) "3. Piano" \p
}
}
@end lilypond
-To annotate chorded notes, the @code{\footnote} must come @emph{after}
-the note that the footnote is annotating and attached as a
-@code{TextScript}:
+To annotate chorded notes with manual footnotes:
@lilypond[verbatim,quote,ragged-right,papersize=a8]
\book {
\header { tagline = ##f }
\relative c' {
<
- c-\footnote #'(1 . -1.25) "1" "1. C"
- es-\footnote #'(2 . -0.25)
- \markup { \bold "b" } "b. E-flat"
- g-\footnote #'(2 . 3) "3" \markup { \italic "iii. G" }
+ \footnote "1" #'(1 . -1.25) "1. C" c
+ \footnote
+ \markup { \bold "b" } #'(2 . -0.25) "b. E-flat" es
+ \footnote "3" #'(2 . 3) \markup { \italic "iii. G" } g
>1
}
}
\book {
\header { tagline = ##f }
\relative c' {
- \footnoteGrob #'DynamicText #'(-3 . 0)
- \markup { \teeny 1 }
- \markup { 1. \bold Forte }
-
- \footnoteGrob #'Slur #'(0 . 1.5)
- \markup { \teeny b }
- \markup { b. A slur }
- a'4\f(
-
- \footnoteGrob #'Beam #'(0 . -2)
- \markup { \teeny 3 }
- \markup { 3. Beam }
- b8)[ e]
-
- \footnoteGrob #'Stem #'(1 . -1)
- \markup { 4 }
+ a'4-\footnote
+ \markup { \teeny 1 } #'(-3 . 0)
+ \markup { 1. \bold Forte } \f
+ -\footnote
+ \markup { \teeny b } #'(0 . 1.5)
+ \markup { b. A slur } (
+ b8)-\footnote
+ \markup { \teeny 3 } #'(0 . -2)
+ \markup { 3. Beam } [
+ e]
+ \footnote
+ \markup { 4 } #'(1 . -1) #'Stem
\markup { \bold 4. { This is a stem } }
c4
-
- \footnoteGrob #'AccidentalCautionary #'(0 . 0.5)
+ \footnote
\markup \concat \teeny { "sharp (v)" }
+ #'(0 . 0.5) #'AccidentalCautionary
\markup \italic { v. A cautionary accidental }
-
- \footnoteGrob #'TextScript #'(0.5 . -0.5)
- \markup \concat \teeny { "a" }
- \markup \italic { a. Slow Down }
- dis?4_"rit."
-
- \breathe
- \footnoteGrob #'BreathingSign #'(1.5 . -0.25)
+ dis?4-\footnote
+ \markup \concat \teeny { "a" } #'(0.5 . -0.5)
+ \markup \italic { a. Slow Down } _"rit."
+ \footnote
\markup { \teeny \musicglyph #"rests.4" }
- \markup { \null }
+ #'(1.5 . -0.25)
+ \markup { \null } \breathe
}
}
@end lilypond
}
@end lilypond
-
@seealso
-Init files: @file{../ly/toc-init.ly}.
-
+Installed Files:
+@file{ly/toc-init.ly}.
@predefined
@funindex \table-of-contents
@ref{Automatic part combining},
@ref{Including LilyPond files}.
-
@ignore
@c This warning is more general than this placement implies.
@c Rests are not merged whether or not they come from tagged sections.
@c Should be deleted? -td
@knownissues
-
Multiple rests are not merged if you create a score with more
than one tagged section at the same place.
@end ignore
+
@node Using global settings
@unnumberedsubsubsec Using global settings
Notation Reference:
@ref{Including LilyPond files}.
+
@node Special characters
@subsection Special characters
}
\addlyrics { O \markup { \concat { Ph \char ##x0153 be! } } }
}
-\markup { "Copyright 2008--2011" \char ##x00A9 }
+\markup { "Copyright 2008--2012" \char ##x00A9 }
@end lilypond
@cindex copyright sign
@file{ly/text-replacements.ly}.
-
@node Controlling output
@section Controlling output
Document Format (PDF) and PostScript (PS). Scalable Vector
Graphics (SVG), Encapsulated PostScript (EPS) and Portable
Network Graphics (PNG) output formats are also available through
-command line options, see @rprogram{Command line options for
-lilypond}.
+command line options, see
+@rprogram{Basic command line options for LilyPond}.
@node Replacing the notation font
reverse the process.
@seealso
-Learning Manual: @rlearning{Other sources of information}.
+Learning Manual:
+@rlearning{Other sources of information}.
@knownissues
Gonville cannot be used to typeset @q{Ancient Music} notation and it is
\score @{
@var{...music...}
\midi @{
- \context @{
- \Score
- tempoWholesPerMinute = #(ly:make-moment 72 4)
- @}
+ \tempo 4 = 72
@}
@}
@end example
In this example the tempo is set to 72 quarter note
-beats per minute. This kind of tempo specification cannot take
-a dotted note length as an argument. If one is required, break
-the dotted note into smaller units. For example, a tempo of 90
-dotted quarter notes per minute can be specified as 270 eighth
-notes per minute:
-
-@example
-tempoWholesPerMinute = #(ly:make-moment 270 8)
-@end example
+beats per minute. @code{\tempo} is actually a music command for
+setting properties during the interpretation of music: in the
+context of output definitions like a @code{\midi} block, as a matter of
+courtesy those are reinterpreted as if they were context modifications.
@cindex MIDI context definitions
>>
\layout {}
\midi {
+ \tempo 2 = 72
\context {
\Score
- tempoWholesPerMinute = #(ly:make-moment 72 2)
midiMinimumVolume = #0.2
midiMaximumVolume = #0.5
}
>>
\layout {}
\midi {
- \context {
- \Score
- tempoWholesPerMinute = #(ly:make-moment 72 2)
- }
+ \tempo 2 = 72
}
}
@end lilypond
>>
\layout { }
\midi {
- \context {
- \Score
- tempoWholesPerMinute = #(ly:make-moment 72 2)
- }
+ \tempo 2 = 72
}
}
@end lilypond
projects / lilypond.git / blobdiff