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.
11 @node Editorial annotations
12 @section Editorial annotations
14 @lilypondfile[quote]{editorial-headword.ly}
16 This section discusses the various ways to change the appearance of
17 notes and add analysis or educational emphasis.
25 @node Inside the staff
26 @subsection Inside the staff
28 This section discusses how to add emphasis to elements that are
32 * Selecting notation font size::
33 * Fingering instructions::
40 @node Selecting notation font size
41 @unnumberedsubsubsec Selecting notation font size
43 @cindex font size (notation)
44 @cindex selecting font size (notation)
46 The font size of notation elements may be altered. It does not
47 change the size of variable symbols, such as beams or slurs.
49 @warning{For @strong{text} font sizes, see
50 @ref{Common markup commands}.}
52 @lilypond[quote,fragment,relative=2,verbatim,ragged-right]
67 @cindex font size (notation) scaling
69 Internally, this sets the @code{fontSize} property. This in turn
70 causes the @code{font-size} property to be set in all layout
71 objects. The value of @code{font-size} is a number indicating the
72 size relative to the standard size for the current staff height.
73 Each step up is an increase of approximately 12% of the font size.
74 Six steps is exactly a factor of two. The Scheme function
75 @code{magstep} converts a @code{font-size} number to a scaling
76 factor. The @code{font-size} property can also be set directly,
77 so that only certain layout objects are affected.
79 @lilypond[quote,fragment,relative=2,verbatim,ragged-right]
82 \override NoteHead #'font-size = #-4
84 \override Script #'font-size = #2
86 \override Stem #'font-size = #-5
90 @cindex standard font size (notation)
91 @cindex font size (notation), standard
93 Font size changes are achieved by scaling the design size that is
94 closest to the desired size. The standard font size (for
95 @code{font-size = #0}), depends on the standard staff height.
96 For a 20pt staff, a 10pt font is selected.
98 The @code{font-size} property can only be set on layout objects
99 that use fonts. These are the ones supporting the
100 @code{font-interface} layout interface.
110 @funindex \normalsize
120 @lsrdir{Editorial,Editorial-annotations}.
123 @internalsref{fontSize},
124 @internalsref{font-size},
125 @internalsref{font-interface}.
128 @node Fingering instructions
129 @unnumberedsubsubsec Fingering instructions
132 @cindex finger change
134 Fingering instructions can be entered using
135 @var{note}-@var{digit}:
137 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
141 Markup texts may be used for finger changes.
143 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
144 c4-1 d-2 f-4 c^\markup { \finger "2 - 3" }
149 You can use the thumb-script (e.g., in cello music) to indicate that a
150 note should be played with the thumb.
152 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
153 <a_\thumb a'-3>2 <b_\thumb b'-3>
156 @cindex fingering chords
157 @cindex chords, fingering
159 Fingerings for chords can also be added to individual notes of the
160 chord by adding them after the pitches.
162 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
163 <c-1 e-2 g-3 b-5>2 <d-1 f-2 a-3 c-5>
166 Fingering instructions may be manually placed above or below the
167 staff, see @ref{Controlling direction and placement}.
171 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
172 {controlling-the-placement-of-chord-fingerings.ly}
178 @ref{Controlling direction and placement}
181 @lsrdir{Editorial,Editorial-annotations}.
184 @internalsref{FingeringEvent},
185 @internalsref{fingering-event},
186 @internalsref{Fingering_engraver},
187 @internalsref{New_fingering_engraver},
188 @internalsref{Fingering}.
192 @unnumberedsubsubsec Hidden notes
195 @cindex invisible notes
196 @cindex transparent notes
198 @funindex \unHideNotes
200 Hidden (or invisible or transparent) notes can be useful in
201 preparing theory or composition exercises.
203 @lilypond[quote,ragged-right,verbatim,relative=2,fragment]
215 Notation objects which are attached to invisible notes are still
218 @lilypond[quote,ragged-right,verbatim,relative=2,fragment]
228 @funindex \unHideNotes
229 @code{\hideNotes}, @code{\unHideNotes}
234 @lsrdir{Editorial,Editorial-annotations}.
237 @internalsref{Note_spacing_engraver},
238 @internalsref{NoteSpacing}.
241 @node Coloring objects
242 @unnumberedsubsubsec Coloring objects
244 @cindex colored objects
246 @cindex coloring objects
247 @cindex colored notes
248 @cindex coloring notes
249 @cindex notes, colored
251 Individual objects may be assigned colors. Valid color names
252 are listed in the @ref{List of colors}.
254 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
255 \override NoteHead #'color = #red
257 \override NoteHead #'color = #(x11-color 'LimeGreen)
259 \override Stem #'color = #blue
265 The full range of colors defined for X11 can be accessed by using
266 the Scheme function @code{x11-color}. The function takes one
267 argument; this can be a symbol in the form @var{'FooBar} or a
268 string in the form @var{"FooBar"}. The first form is quicker to
269 write and is more efficient. However, using the second form it is
270 possible to access X11 colors by the multi-word form of its name.
272 If @code{x11-color} cannot make sense of the parameter then the
273 color returned defaults to black.
275 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
276 \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
277 \set Staff.instrumentName = \markup {
278 \with-color #(x11-color 'navy) "Clarinet"
282 \override Beam #'color = #(x11-color "medium turquoise")
284 \override Accidental #'color = #(x11-color 'DarkRed)
286 \override NoteHead #'color = #(x11-color "LimeGreen")
288 % this is deliberate nonsense; note that the stems remain black
289 \override Stem #'color = #(x11-color 'Boggle)
293 Exact RGB colors can be specified using the Scheme function
296 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
297 \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
298 \set Staff.instrumentName = \markup {
299 \with-color #(x11-color 'navy) "Clarinet"
303 \override Stem #'color = #(rgb-color 0 0 0)
306 \override Stem #'color = #(rgb-color 1 1 1)
309 \override Stem #'color = #(rgb-color 0 0 0.5)
316 @ref{List of colors}, @ref{Objects connected to
320 @lsrdir{Editorial,Editorial-annotations}.
323 An X11 color is not necessarily exactly the same shade as a
324 similarly named normal color.
326 Not all X11 colors are distinguishable in a web browser, i.e.,
327 a web browser might not display a difference between @code{'LimeGreen}
328 and @code{'ForestGreen}. For web use normal colors are recommended
329 (i.e., @code{#blue}, @code{#green}, @code{#red}).
332 Notes in a chord cannot be colored with @code{\override}; use
333 @code{\tweak} instead, see @ref{Objects connected to the input}.
337 @unnumberedsubsubsec Parentheses
341 @cindex notes, parenthesized
344 Objects may be parenthesized by prefixing @code{\parenthesize} to
345 the music event. When prefixed to a chord, it parenthesizes every
346 note. Individual notes inside a chord may also be parenthesized.
348 @lilypond[quote,relative=2,fragment,verbatim,ragged-right]
350 c2 \parenthesize <c e g>
351 c2 <c \parenthesize e g>
354 Non-note objects may be parenthesized as well.
356 @lilypond[quote,relative=2,fragment,verbatim,ragged-right]
357 c2-\parenthesize -. d
364 @lsrdir{Editorial,Editorial-annotations}.
367 @internalsref{Parenthesis_engraver},
368 @internalsref{ParenthesesItem},
369 @internalsref{parentheses-interface}.
373 Parenthesizing a chord prints parentheses around each individual
374 note, instead of a single large parenthesis around the entire
379 @unnumberedsubsubsec Stems
383 Whenever a note is found, a @code{Stem} object is created
384 automatically. For whole notes and rests, they are also created but
393 @funindex \stemNeutral
399 @cindex stem, direction
402 @cindex stem, neutral
404 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
405 {default-direction-of-stems-on-the-center-line-of-the-staff.ly}
409 @ref{Controlling direction and placement}.
412 @lsrdir{Editorial,Editorial-annotations}.
415 @internalsref{Stem_engraver},
417 @internalsref{stem-interface}.
420 @node Outside the staff
421 @subsection Outside the staff
423 This section discusses how to add emphasis to elements in the staff
424 from outside of the staff.
429 * Analysis brackets::
433 @unnumberedsubsubsec Balloon help
435 Elements of notation can be marked and named with the help of a
436 square balloon. The primary purpose of this feature is to explain
439 @lilypond[quote,verbatim,fragment,ragged-right,relative=2]
440 \new Voice \with { \consists "Balloon_engraver" }
442 \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" }
444 \balloonGrobText #'Rest #'(-4 . -4) \markup { "I'm a rest" }
446 <c, g'-\balloonText #'(-2 . -2) \markup { "I'm a note head" } c>2.
451 @cindex notation, explaining
453 There are two music functions, @code{balloonGrobText} and
454 @code{balloonText}; the former is used like @code{\once \override} to
455 attach text to any grob, and the latter is used like @code{\tweak},
456 typically within chords, to attach text to an individual note.
460 @funindex ballonLengthOn
461 @funindex ballonLengthOff
462 @code{\balloonLengthOn}, @code{\balloonLengthOff}
467 @lsrdir{Editorial,Editorial-annotations}.
470 @internalsref{Balloon_engraver},
471 @internalsref{BalloonTextItem},
472 @internalsref{balloon-interface}.
476 @unnumberedsubsubsec Grid lines
478 Vertical lines can be drawn between staves synchronized with the
481 @lilypond[quote,verbatim,ragged-right]
486 \consists "Grid_point_engraver"
487 % set the grid interval to one quarter note
488 gridInterval = #(ly:make-moment 1 4)
492 % by default this centers grid lines horizontally below
493 % and to the left side of the note head, the grid lines
494 % extending from the middle lines of each staff
495 \consists "Grid_line_span_engraver"
501 \new Staff \relative c'' {
505 \new Staff \relative c {
516 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
517 {grid-lines-changing-their-appearance.ly}
523 @lsrdir{Editorial,Editorial-annotations}.
526 @internalsref{Grid_line_span_engraver},
527 @internalsref{Grid_point_engraver},
528 @internalsref{GridLine},
529 @internalsref{GridPoint},
530 @internalsref{grid-line-interface},
531 @internalsref{grid-point-interface}.
534 @node Analysis brackets
535 @unnumberedsubsubsec Analysis brackets
538 @cindex phrasing brackets
539 @cindex musicological analysis
540 @cindex note grouping bracket
542 Brackets are used in musical analysis to indicate structure in musical
543 pieces. Simple horizontal brackets are supported.
545 @lilypond[quote,verbatim,ragged-right]
549 \consists "Horizontal_bracket_engraver"
558 Analysis brackets may be nested.
560 @lilypond[quote,verbatim,ragged-right]
564 \consists "Horizontal_bracket_engraver"
568 c4\startGroup\startGroup
571 d4\stopGroup\stopGroup
578 @lsrdir{Editorial,Editorial-annotations}.
581 @internalsref{Horizontal_bracket_engraver},
582 @internalsref{HorizontalBracket},
583 @internalsref{horizontal-bracket-interface},
584 @internalsref{Staff}.