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[quote]{editorial-headword.ly}
14 This section discusses the various ways to change the appearance of
15 notes and add analysis or educational emphasis.
23 @node Inside the staff
24 @subsection Inside the staff
26 This section discusses how to add emphasis to elements that are
30 * Selecting notation font size::
31 * Fingering instructions::
38 @node Selecting notation font size
39 @unnumberedsubsubsec Selecting notation font size
42 @cindex font size, selecting
43 @cindex selecting font size
45 The font size of notation elements may be altered. It does not
46 change the size of variable symbols, such as beams or slurs.
48 @lilypond[quote,fragment,relative=2,verbatim,ragged-right]
63 @cindex font size scaling
65 Internally, this sets the @code{fontSize} property. This in turns
66 causes the @code{font-size} property to be set in all layout
67 objects. The value of @code{font-size} is a number indicating the
68 size relative to the standard size for the current staff height.
69 Each step up is an increase of approximately 12% of the font size.
70 Six steps is exactly a factor two. The Scheme function
71 @code{magstep} converts a @code{font-size} number to a scaling
72 factor. The @code{font-size} property can also be set directly,
73 so that only certain layout objects are affected.
75 @lilypond[quote,fragment,relative=2,verbatim,ragged-right]
78 \override NoteHead #'font-size = #-4
80 \override Script #'font-size = #2
82 \override Stem #'font-size = #-5
86 @cindex standard font size
87 @cindex font size, standard
89 Font size changes are achieved by scaling the design size that is
90 closest to the desired size. The standard font size (for
91 @code{font-size} equals 0), depends on the standard staff height.
92 For a 20pt staff, a 10pt font is selected.
94 The @code{font-size} property can only be set on layout objects
95 that use fonts. These are the ones supporting the
96 @code{font-interface} layout interface.
104 @funindex \normalsize
114 @lsrdir{Editorial,Editorial-annotations}.
117 @internalsref{font-interface}.
120 @node Fingering instructions
121 @unnumberedsubsubsec Fingering instructions
124 @cindex finger change
126 Fingering instructions can be entered using
127 @var{note}-@var{digit}:
129 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
133 Markup texts may be used for finger changes.
135 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
136 c4-1 d-2 f-4 c^\markup { \finger "2 - 3" }
141 You can use the thumb-script (e.g., in cello music)to indicate that a
142 note should be played with the thumb.
144 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
145 <a_\thumb a'-3>2 <b_\thumb b'-3>
148 @cindex fingering chords
149 @cindex chords, fingering
151 Fingerings for chords can also be added to individual notes of the
152 chord by adding them after the pitches.
154 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
155 < c-1 e-2 g-3 b-5 >2 < d-1 f-2 a-3 c-5 >
158 Fingering instructions may be manually placed above or below the
159 staff, see @ref{Controlling direction and placement}.
163 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
164 {controlling-the-placement-of-chord-fingerings.ly}
170 @ref{Controlling direction and placement}
173 @lsrdir{Editorial,Editorial-annotations}.
176 @internalsref{Fingering}.
180 @unnumberedsubsubsec Hidden notes
183 @cindex Invisible notes
184 @cindex Transparent notes
186 @funindex \unHideNotes
188 Hidden (or invisible or transparent) notes can be useful in
189 preparing theory or composition exercises.
191 @lilypond[quote,ragged-right,verbatim,relative=2,fragment]
205 @code{\hideNotes}, @code{\unHideNotes}
210 @lsrdir{Editorial,Editorial-annotations}.
213 @node Coloring objects
214 @unnumberedsubsubsec Coloring objects
216 @cindex colored objects
218 @cindex coloring objects
219 @cindex colored notes
220 @cindex coloring notes
221 @cindex notes, colored
223 Individual objects may be assigned colors. You may use the color
224 names listed in the @ref{List of colors}.
226 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
227 \override NoteHead #'color = #red
229 \override NoteHead #'color = #(x11-color 'LimeGreen)
231 \override Stem #'color = #blue
237 The full range of colors defined for X11 can be accessed by using
238 the Scheme function @code{x11-color}. The function takes one
239 argument; this can be a symbol in the form @var{'FooBar} or a
240 string in the form @var{"FooBar"}. The first form is quicker to
241 write and is more efficient. However, using the second form it is
242 possible to access X11 colors by the multi-word form of its name.
244 If @code{x11-color} cannot make sense of the parameter then the
245 color returned defaults to black.
247 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
248 \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
249 \set Staff.instrumentName = \markup {
250 \with-color #(x11-color 'navy) "Clarinet"
254 \override Beam #'color = #(x11-color "medium turquoise")
256 \override Accidental #'color = #(x11-color 'DarkRed)
258 \override NoteHead #'color = #(x11-color "LimeGreen")
260 % this is deliberate nonsense; note that the stems remain black
261 \override Stem #'color = #(x11-color 'Boggle)
265 You can get exact RGB colors by specifying the rgb-color number.
267 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
268 \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
269 \set Staff.instrumentName = \markup {
270 \with-color #(x11-color 'navy) "Clarinet"
274 \override Stem #'color = #(rgb-color 0 0 0)
277 \override Stem #'color = #(rgb-color 1 1 1)
280 \override Stem #'color = #(rgb-color 0 0 0.5)
287 @ref{List of colors}, @ref{Objects connected to
291 @lsrdir{Editorial,Editorial-annotations}.
294 An x11 color is not necessarily exactly the same shade as a
295 similarly named normal color.
297 Not all x11 colors are distinguishable in a web browser i.e. a web browser
298 might not display a difference between 'LimeGreen and 'ForestGreen. For
299 web use normal colors are recommended (i.e. #blue, #green, #red).
302 Notes in a chord cannot be colored with @code{\override}; use
303 @code{\tweak} instead, see @ref{Objects connected to the input}.
307 @unnumberedsubsubsec Parentheses
311 @cindex notes, parenthesized
314 Objects may be parenthesized by prefixing @code{\parenthesize} to
315 the music event. This only functions inside chords; to
316 parenthesize a single note it must be enclosed with @code{<>} as
319 FIXME: after 2.11.44 is out,
320 @c \parenthesize c4-. \parenthesize r4 \parenthesize <c e g>4->
322 @lilypond[quote,relative=2,fragment,verbatim,ragged-right]
323 c2 < \parenthesize d>
326 Non-note objects may be parenthesized as well.
328 @lilypond[quote,relative=2,fragment,verbatim,ragged-right]
329 < c d g >2-\parenthesize -. d
335 @lsrdir{Editorial,Editorial-annotations}.
339 Rests cannot be parenthesized.
343 @unnumberedsubsubsec Stems
347 Whenever a note is found, a @code{Stem} object is created
348 automatically. For whole notes and rests, they are also created but
357 @funindex \stemNeutral
363 @cindex stem, direction
366 @cindex stem, neutral
368 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
369 {default-direction-of-stems-on-the-center-line-of-the-staff.ly}
373 @ref{Controlling direction and placement}.
376 @lsrdir{Editorial,Editorial-annotations}.
379 @node Outside the staff
380 @subsection Outside the staff
382 This section discusses how to add emphasis to elements in the staff
383 from outside of the staff.
388 * Analysis brackets::
392 @unnumberedsubsubsec Balloon help
394 Elements of notation can be marked and named with the help of a
395 square balloon. The primary purpose of this feature is to explain
398 @lilypond[quote,verbatim,fragment,ragged-right,relative=2]
399 \new Voice \with { \consists "Balloon_engraver" }
401 \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" }
403 \balloonGrobText #'Rest #' (-4 . -4) \markup { "I'm a rest" }
405 <c, g'-\balloonText #'(-2 . -2) \markup { "I'm a note head" } c>2.
409 There are two music functions, @code{balloonGrobText} and
410 @code{balloonText}; The former is used like @code{\once \override} to
411 attach text to any grob, and the latter is used like @code{ \tweak},
412 typically within chords, to attach text to an individual note.
415 @cindex notation, explaining
420 @lsrdir{Editorial,Editorial-annotations}.
423 @internalsref{text-balloon-interface}.
427 @unnumberedsubsubsec Grid lines
429 Vertical lines can be drawn between staves synchronized with the
432 @lilypond[quote,verbatim,ragged-right]
437 \consists "Grid_point_engraver"
438 % this sets the grid interval to 1 quarternote (crotchet)
439 gridInterval = #(ly:make-moment 1 4)
444 % by default this centers grid lines horizontally below and to the
445 % left side of the notehead, the grid lines extend from
446 % the middle lines of each staff
447 \consists "Grid_line_span_engraver"
469 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
470 {grid-lines-changing-their-appearance.ly}
476 @lsrdir{Editorial,Editorial-annotations}.
481 @node Analysis brackets
482 @unnumberedsubsubsec Analysis brackets
485 @cindex phrasing brackets
486 @cindex musicological analysis
487 @cindex note grouping bracket
489 Brackets are used in musical analysis to indicate structure in musical
490 pieces. LilyPond supports a simple form of horizontal brackets.
492 @lilypond[quote,verbatim,ragged-right]
495 \Staff \consists "Horizontal_bracket_engraver"
504 Analysis brackets may be nested.
506 @lilypond[quote,verbatim,ragged-right]
509 \Staff \consists "Horizontal_bracket_engraver"
513 c4\startGroup\startGroup
516 d4\stopGroup\stopGroup
523 @lsrdir{Editorial,Editorial-annotations}.
526 @internalsref{HorizontalBracket},
527 @internalsref{Horizontal_bracket_engraver},
528 @internalsref{Staff}.