1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. See TRANSLATION for details.
9 @node Editorial annotations
10 @section Editorial annotations
12 @lilypondfile[ragged-right,line-width=16\cm,staffsize=16,quote]
13 {editorial-headword.ly}
21 @node Inside the staff
22 @subsection Inside the staff
26 * Selecting notation font size::
27 * Fingering instructions::
34 @node Selecting notation font size
35 @subsubsection Selecting notation font size
38 @cindex font size, selecting
39 @cindex selecting font size
41 The easiest method of setting the font size of any context is by
42 setting the @code{fontSize} property.
44 @lilypond[quote,fragment,relative=2,verbatim,ragged-right]
53 It does not change the size of variable symbols, such as beams or
56 @cindex font size scaling
58 Internally, the @code{fontSize} context property will cause the
59 @code{font-size} property to be set in all layout objects. The
60 value of @code{font-size} is a number indicating the size relative
61 to the standard size for the current staff height. Each step up
62 is an increase of approximately 12% of the font size. Six steps
63 is exactly a factor two. The Scheme function @code{magstep}
64 converts a @code{font-size} number to a scaling factor. The
65 @code{font-size} property can also be set directly, so that only
66 certain layout objects are affected.
68 @lilypond[quote,fragment,relative=2,verbatim,ragged-right]
70 \override NoteHead #'font-size = #-4
72 \override NoteHead #'font-size = #3
76 @cindex standard font size
77 @cindex font size, standard
79 Font size changes are achieved by scaling the design size that is
80 closest to the desired size. The standard font size (for
81 @code{font-size} equals 0), depends on the standard staff height.
82 For a 20pt staff, a 10pt font is selected.
84 The @code{font-size} property can only be set on layout objects that
85 use fonts. These are the ones supporting the @code{font-interface}
90 The following commands set @code{fontSize} for the current voice:
101 Snippets: @lsrdir{Editorial,Editorial-annotations}.
103 Internals Reference: @internalsref{font-interface}.
106 @node Fingering instructions
107 @subsubsection Fingering instructions
110 @cindex finger change
112 Fingering instructions can be entered using
113 @var{note}-@var{digit}:
115 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
119 Use markup texts for finger changes.
121 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
122 c4-1 d-2 f-4 c^\markup { \finger "2 - 3" }
127 You can use the thumb-script (e.g., in cello music)to indicate that a
128 note should be played with the thumb.
130 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
131 <a_\thumb a'-3>2 <b_\thumb b'-3>
134 @cindex fingering chords
135 @cindex chords, fingering
137 Fingerings for chords can also be added to individual notes of the
138 chord by adding them after the pitches.
140 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
141 < c-1 e-2 g-3 b-5 >2 < d-1 f-2 a-3 c-5 >
147 @code{fingeringOrientations} are used to control where the fingering
150 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
151 \set fingeringOrientations = #'(left)
153 \set fingeringOrientations = #'(down)
155 \set fingeringOrientations = #'(right)
157 \set fingeringOrientations = #'(up)
159 \set fingeringOrientations = #'(left down)
161 \set fingeringOrientations = #'(up right down)
167 Snippets: @lsrdir{Editorial,Editorial-annotations}.
169 Internals Reference: @internalsref{Fingering}.
173 @subsubsection Hidden notes
176 @cindex Invisible notes
177 @cindex Transparent notes
179 @funindex \unHideNotes
181 Hidden (or invisible or transparent) notes can be useful in
182 preparing theory or composition exercises.
184 @lilypond[quote,ragged-right,verbatim,relative=2,fragment]
198 @code{\hideNotes}, @code{\unHideNotes}
202 Snippets: @lsrdir{Editorial,Editorial-annotations}.
205 @node Coloring objects
206 @subsubsection Coloring objects
208 @cindex colored objects
210 @cindex coloring objects
211 @cindex colored notes
212 @cindex coloring notes
213 @cindex notes, colored
215 Individual objects may be assigned colors. You may use the color
216 names listed in the @ref{List of colors}.
218 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
219 \override NoteHead #'color = #red
221 \override NoteHead #'color = #(x11-color 'LimeGreen)
223 \override Stem #'color = #blue
229 The full range of colors defined for X11 can be accessed by using
230 the Scheme function @code{x11-color}. The function takes one
231 argument; this can be a symbol in the form @var{'FooBar} or a
232 string in the form @var{"FooBar"}. The first form is quicker to
233 write and is more efficient. However, using the second form it is
234 possible to access X11 colors by the multi-word form of its name.
236 If @code{x11-color} cannot make sense of the parameter then the
237 color returned defaults to black.
239 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
240 \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
241 \set Staff.instrumentName = \markup {
242 \with-color #(x11-color 'navy) "Clarinet"
245 \override Beam #'color = #(x11-color "medium turquoise")
247 \override Accidental #'color = #(x11-color 'DarkRed)
249 \override NoteHead #'color = #(x11-color "LimeGreen")
252 % this is deliberate nonsense; note that the stems remain black
253 \override Stem #'color = #(x11-color 'Boggle)
257 You can get exact RGB colors by specifying the rgb-color number.
259 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
261 \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
262 \set Staff.instrumentName = \markup {
263 \with-color #(x11-color 'navy) "Clarinet"
268 \override Stem #'color = #(rgb-color 0 0 0)
271 \override Stem #'color = #(rgb-color 1 1 1)
274 \override Stem #'color = #(rgb-color 0 0 0.5)
281 Notation Reference: @ref{List of colors}, @ref{Objects connected to
284 Snippets: @lsrdir{Editorial,Editorial-annotations}.
287 An x11 color is not necessarily exactly the same shade as a
288 similarly named normal color.
290 Not all x11 colors are distinguishable in a web browser i.e. a web browser
291 might not display a difference between 'LimeGreen and 'ForestGreen. For
292 web use normal colors are recommended (i.e. #blue, #green, #red).
295 Notes in a chord cannot be colored with @code{\override}; use
296 @code{\tweak} instead. See @ref{Objects connected to the input},
301 @subsubsection Parentheses
305 @cindex notes, parenthesized
308 Objects may be parenthesized by prefixing @code{\parenthesize} to
311 @lilypond[relative=2,fragment,verbatim,ragged-right]
324 This only functions inside chords, to parenthesize a single note it
325 must be enclosed with @code{<>} as if it is a chord.
328 < \parenthesize NOTE>
331 @lilypond[relative=2,fragment,verbatim,ragged-right]
340 Snippets: @lsrdir{Editorial,Editorial-annotations}.
348 Whenever a note is found, a @code{Stem} object is created
349 automatically. For whole notes and rests, they are also created but
358 @funindex \stemNeutral
364 @cindex stem, direction
367 @cindex stem, neutral
369 To change the direction of stems on the center line of the staff, use
371 @lilypond[quote,ragged-right,fragment,relative=2,verbatim]
373 \override Stem #'neutral-direction = #up
375 \override Stem #'neutral-direction = #down
381 Snippets: @lsrdir{Editorial,Editorial-annotations}.
384 @node Outside the staff
385 @subsection Outside the staff
391 * Analysis brackets::
395 @subsubsection Balloon help
397 Elements of notation can be marked and named with the help of a
398 square balloon. The primary purpose of this feature is to explain
401 The following example demonstrates its use.
403 @lilypond[quote,verbatim,fragment,ragged-right,relative=2]
404 \new Voice \with { \consists "Balloon_engraver" }
407 \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" }
409 <c' g'-\balloonText #'(-2 . -2) \markup { "I'm a note head" }
414 There are two music functions, @code{balloonGrobText} and
415 @code{balloonText}; The former is used like \once \override to
416 attach text to any grob, and the latter is used like \tweak,
417 typically within chords, to attach text to an individual note.
420 @cindex notation, explaining
424 Snippets: @lsrdir{Editorial,Editorial-annotations}.
426 Internals Reference: @internalsref{text-balloon-interface}.
430 @subsubsection Grid lines
432 Vertical lines can be drawn between staves synchronized with the
435 @lilypond[ragged-right,quote,verbatim]
439 \consists "Grid_point_engraver" %% sets of grid
440 gridInterval = #(ly:make-moment 1 4)
445 \consists "Grid_line_span_engraver"
446 %% centers grid lines horizontally below note heads
447 \override NoteColumn #'X-offset = #-0.5
458 %% centers grid lines vertically
459 \override Score.GridLine #'extra-offset = #'( 0.0 . 1.0 )
471 Snippets: @lsrdir{Editorial,Editorial-annotations}.
476 @node Analysis brackets
477 @subsubsection Analysis brackets
480 @cindex phrasing brackets
481 @cindex musicological analysis
482 @cindex note grouping bracket
484 Brackets are used in musical analysis to indicate structure in musical
485 pieces. LilyPond supports a simple form of nested horizontal
486 brackets. To use this, add the @code{Horizontal_bracket_engraver} to
487 the @code{Staff} context. A bracket is started with
488 @code{\startGroup} and closed with @code{\stopGroup}.
490 @lilypond[quote,ragged-right,verbatim]
493 c4\startGroup\startGroup
496 c4\stopGroup\stopGroup
500 \Staff \consists "Horizontal_bracket_engraver"
508 Snippets: @lsrdir{Editorial,Editorial-annotations}.
510 Internals Reference: @internalsref{HorizontalBracket},
511 @internalsref{Horizontal_bracket_engraver}, @internalsref{Staff}.