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 @unnumberedsubsubsec 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=1,verbatim]
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=1,verbatim]
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}.
103 Internals Reference: @internalsref{font-interface}.
106 @node Fingering instructions
107 @unnumberedsubsubsec Fingering instructions
110 @cindex finger change
112 Fingering instructions can be entered using
115 @var{note}-@var{digit}
118 For finger changes, use markup texts
120 @lilypond[quote,verbatim,ragged-right,fragment,relative=1]
122 c^\markup { \finger "2 - 3" }
128 You can use the thumb-script to indicate that a note should be
129 played with the thumb (e.g., in cello music)
131 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
132 <a_\thumb a'-3>8 <b_\thumb b'-3>
135 @cindex fingering chords
136 @cindex chords, fingering
138 Fingerings for chords can also be added to individual notes of the
139 chord by adding them after the pitches
141 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
148 You may exercise greater control over fingering chords by setting
149 @code{fingeringOrientations}
151 @lilypond[quote,verbatim,ragged-right,fragment,relative=1]
152 \set fingeringOrientations = #'(left down)
153 <c-1 es-2 g-4 bes-5 > 4
154 \set fingeringOrientations = #'(up right down)
155 <c-1 es-2 g-4 bes-5 > 4
158 Using this feature, it is also possible to put fingering
159 instructions very close to note heads in monophonic music,
161 @lilypond[verbatim,ragged-right,quote,fragment]
162 \set fingeringOrientations = #'(right)
169 Snippets: @lsrdir{editorial}.
171 Internals Reference: @internalsref{Fingering}.
173 Examples: @c @lsr{expressive,fingering-chords.ly}
178 @unnumberedsubsubsec Hidden notes
181 @cindex Invisible notes
182 @cindex Transparent notes
185 @funindex \unHideNotes
187 Hidden (or invisible or transparent) notes can be useful in
188 preparing theory or composition exercises.
190 @lilypond[quote,ragged-right,verbatim,relative=2,fragment]
199 @node Coloring objects
200 @unnumberedsubsubsec Coloring objects
202 Individual objects may be assigned colors. You may use the color
203 names listed in the @ref{List of colors}.
205 @lilypond[quote,ragged-right,verbatim,fragment,relative=1]
206 \override NoteHead #'color = #red
208 \override NoteHead #'color = #(x11-color 'LimeGreen)
210 \override Stem #'color = #blue
214 The full range of colors defined for X11 can be accessed by using
215 the Scheme function x11-color. The function takes one argument
219 \override Beam #'color = #(x11-color 'MediumTurquoise)
225 \override Beam #'color = #(x11-color "MediumTurquoise")
228 The first form is quicker to write and is more efficient.
229 However, using the second form it is possible to access X11 colors
230 by the multi-word form of its name
233 \override Beam #'color = #(x11-color "medium turquoise")
236 If x11-color cannot make sense of the parameter then the color
237 returned defaults to black. It should be obvious from the final
238 score that something is wrong.
240 This example illustrates the use of x11-color. Notice that the
241 stem color remains black after being set to (x11-color 'Boggle),
242 which is deliberate nonsense.
244 @lilypond[quote,ragged-right,verbatim]
246 \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
247 \set Staff.instrumentName = \markup {
248 \with-color #(x11-color 'navy) "Clarinet"
252 \override Beam #'color = #(x11-color "medium turquoise")
254 \override NoteHead #'color = #(x11-color "LimeGreen")
256 \override Stem #'color = #(x11-color 'Boggle)
263 you can get exact RGB colors by specifying
266 \override Stem #'color = #(rgb-color 0 0 0)
268 \override Stem #'color = #(rgb-color 1 1 1)
270 \override Stem #'color = #(rgb-color 0 0 0.5)
275 Appendix: @ref{List of colors}.
279 Not all x11 colors are distinguishable in a web browser. For web
280 use normal colors are recommended.
282 An x11 color is not necessarily exactly the same shade as a
283 similarly named normal color.
285 Notes in a chord cannot be colored with @code{\override}; use
286 @code{\tweak} instead. See @ref{Objects connected to the input},
291 @unnumberedsubsubsec Parentheses
295 @cindex notes, parenthesized
297 Objects may be parenthesized by prefixing @code{\parenthesize} to
300 @lilypond[relative=2,fragment,verbatim,ragged-right]
308 This only functions inside chords, to parenthesize a single note it
309 must be enclosed with @code{<>} as if it is a chord.
312 < \parenthesize NOTE>
317 @unnumberedsubsubsec Stems
319 Whenever a note is found, a @internalsref{Stem} object is created
320 automatically. For whole notes and rests, they are also created
329 @funindex \stemNeutral
335 To change the direction of stems on the center line of the staff, use
337 @lilypond[quote,ragged-right,fragment,relative=2,verbatim]
339 \override Stem #'neutral-direction = #up
341 \override Stem #'neutral-direction = #down
346 @node Outside the staff
347 @subsection Outside the staff
353 * Blank music sheet::
354 * Analysis brackets::
358 @unnumberedsubsubsec Balloon help
360 Elements of notation can be marked and named with the help of a
361 square balloon. The primary purpose of this feature is to explain
364 The following example demonstrates its use.
366 @lilypond[quote,verbatim,fragment,ragged-right,relative=2]
367 \new Voice \with { \consists "Balloon_engraver" }
369 \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" }
370 <f-\balloonText #'(-2 . -2) \markup { "I'm a note head" } >8
375 There are two music functions, @code{balloonText} and
376 @code{balloonGrobText}. The latter takes the name of the grob to
377 adorn, while the former may be used as an articulation on a note.
378 The other arguments are the offset and the text of the label.
381 @cindex notation, explaining
385 Internals Reference: @internalsref{text-balloon-interface}.
389 @unnumberedsubsubsec Grid lines
391 Vertical lines can be drawn between staves synchronized with the
394 @lilypond[ragged-right,quote,verbatim]
398 \consists "Grid_point_engraver" %% sets of grid
399 gridInterval = #(ly:make-moment 1 4)
404 \consists "Grid_line_span_engraver"
405 %% centers grid lines horizontally below note heads
406 \override NoteColumn #'X-offset = #-0.5
417 %% centers grid lines vertically
418 \override Score.GridLine #'extra-offset = #'( 0.0 . 1.0 )
428 Examples: @lsrdir{education}
431 @node Blank music sheet
432 @unnumberedsubsubsec Blank music sheet
434 @cindex Sheet music, empty
435 @cindex Staves, blank sheet
437 A blank music sheet can be produced also by using invisible notes,
438 and removing @code{Bar_number_engraver}.
441 @lilypond[quote,verbatim]
442 \layout{ indent = #0 }
444 \repeat unfold 2 % Change this for more lines.
449 \override TimeSignature #'transparent = ##t
450 % un-comment this line if desired
451 % \override Clef #'transparent = ##t
453 \remove Bar_number_engraver
456 % modify these to get the staves you want
457 \new Staff \emptymusic
458 \new TabStaff \emptymusic
463 @node Analysis brackets
464 @unnumberedsubsubsec Analysis brackets
467 @cindex phrasing brackets
468 @cindex musicological analysis
469 @cindex note grouping bracket
471 Brackets are used in musical analysis to indicate structure in
472 musical pieces. LilyPond supports a simple form of nested
473 horizontal brackets. To use this, add the
474 @internalsref{Horizontal_bracket_engraver} to the
475 @internalsref{Staff} context. A bracket is started with
476 @code{\startGroup} and closed with @code{\stopGroup}.
478 @lilypond[quote,ragged-right,verbatim]
481 c4\startGroup\startGroup
484 c4\stopGroup\stopGroup
488 \Staff \consists "Horizontal_bracket_engraver"
494 Internals Reference: @internalsref{HorizontalBracket}.