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
37 The easiest method of setting the font size of any context is by
38 setting the @code{fontSize} property.
40 @lilypond[quote,fragment,relative=1,verbatim]
49 It does not change the size of variable symbols, such as beams or
52 Internally, the @code{fontSize} context property will cause the
53 @code{font-size} property to be set in all layout objects. The
54 value of @code{font-size} is a number indicating the size relative
55 to the standard size for the current staff height. Each step up
56 is an increase of approximately 12% of the font size. Six steps
57 is exactly a factor two. The Scheme function @code{magstep}
58 converts a @code{font-size} number to a scaling factor. The
59 @code{font-size} property can also be set directly, so that only
60 certain layout objects are affected.
62 @lilypond[quote,fragment,relative=1,verbatim]
64 \override NoteHead #'font-size = #-4
66 \override NoteHead #'font-size = #3
70 Font size changes are achieved by scaling the design size that is
71 closest to the desired size. The standard font size (for
72 @code{font-size} equals 0), depends on the standard staff height.
73 For a 20pt staff, a 10pt font is selected.
75 The @code{font-size} property can only be set on layout objects
76 that use fonts. These are the ones supporting the
77 @internalsref{font-interface} layout interface.
81 The following commands set @code{fontSize} for the current voice:
91 @node Fingering instructions
92 @unnumberedsubsubsec Fingering instructions
97 Fingering instructions can be entered using
100 @var{note}-@var{digit}
103 For finger changes, use markup texts
105 @lilypond[quote,verbatim,ragged-right,fragment,relative=1]
107 c^\markup { \finger "2 - 3" }
110 You can use the thumb-script to indicate that a note should be
111 played with the thumb (e.g., in cello music)
113 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
114 <a_\thumb a'-3>8 <b_\thumb b'-3>
117 Fingerings for chords can also be added to individual notes of the
118 chord by adding them after the pitches
120 @lilypond[quote,verbatim,ragged-right,fragment,relative=2]
127 You may exercise greater control over fingering chords by setting
128 @code{fingeringOrientations}
130 @lilypond[quote,verbatim,ragged-right,fragment,relative=1]
131 \set fingeringOrientations = #'(left down)
132 <c-1 es-2 g-4 bes-5 > 4
133 \set fingeringOrientations = #'(up right down)
134 <c-1 es-2 g-4 bes-5 > 4
137 Using this feature, it is also possible to put fingering
138 instructions very close to note heads in monophonic music,
140 @lilypond[verbatim,ragged-right,quote,fragment]
141 \set fingeringOrientations = #'(right)
148 Internals Reference: @internalsref{Fingering}.
150 Examples: @lsr{expressive,fingering-chords.ly}
155 @unnumberedsubsubsec Hidden notes
158 @cindex Invisible notes
159 @cindex Transparent notes
162 @funindex \unHideNotes
164 Hidden (or invisible or transparent) notes can be useful in
165 preparing theory or composition exercises.
167 @lilypond[quote,ragged-right,verbatim,relative=2,fragment]
176 @node Coloring objects
177 @unnumberedsubsubsec Coloring objects
179 Individual objects may be assigned colors. You may use the color
180 names listed in the @ref{List of colors}.
182 @lilypond[quote,ragged-right,verbatim,fragment,relative=1]
183 \override NoteHead #'color = #red
185 \override NoteHead #'color = #(x11-color 'LimeGreen)
187 \override Stem #'color = #blue
191 The full range of colors defined for X11 can be accessed by using
192 the Scheme function x11-color. The function takes one argument
196 \override Beam #'color = #(x11-color 'MediumTurquoise)
202 \override Beam #'color = #(x11-color "MediumTurquoise")
205 The first form is quicker to write and is more efficient.
206 However, using the second form it is possible to access X11 colors
207 by the multi-word form of its name
210 \override Beam #'color = #(x11-color "medium turquoise")
213 If x11-color cannot make sense of the parameter then the color
214 returned defaults to black. It should be obvious from the final
215 score that something is wrong.
217 This example illustrates the use of x11-color. Notice that the
218 stem color remains black after being set to (x11-color 'Boggle),
219 which is deliberate nonsense.
221 @lilypond[quote,ragged-right,verbatim]
223 \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
224 \set Staff.instrumentName = \markup {
225 \with-color #(x11-color 'navy) "Clarinet"
229 \override Beam #'color = #(x11-color "medium turquoise")
231 \override NoteHead #'color = #(x11-color "LimeGreen")
233 \override Stem #'color = #(x11-color 'Boggle)
240 you can get exact RGB colors by specifying
243 \override Stem #'color = #(rgb-color 0 0 0)
245 \override Stem #'color = #(rgb-color 1 1 1)
247 \override Stem #'color = #(rgb-color 0 0 0.5)
252 Appendix: @ref{List of colors}.
256 Not all x11 colors are distinguishable in a web browser. For web
257 use normal colors are recommended.
259 An x11 color is not necessarily exactly the same shade as a
260 similarly named normal color.
262 Notes in a chord cannot be colored with @code{\override}; use
263 @code{\tweak} instead. See @ref{Objects connected to the input},
268 @unnumberedsubsubsec Parentheses
272 @cindex notes, parenthesized
274 Objects may be parenthesized by prefixing @code{\parenthesize} to
277 @lilypond[relative=2,fragment,verbatim,ragged-right]
285 This only functions inside chords, to parenthesize a single note it
286 must be enclosed with @code{<>} as if it is a chord.
289 < \parenthesize NOTE>
294 @unnumberedsubsubsec Stems
296 Whenever a note is found, a @internalsref{Stem} object is created
297 automatically. For whole notes and rests, they are also created
306 @funindex \stemNeutral
312 To change the direction of stems in the middle of the staff, use
314 @lilypond[quote,ragged-right,fragment,relative=2,verbatim]
316 \override Stem #'neutral-direction = #up
318 \override Stem #'neutral-direction = #down
323 @node Outside the staff
324 @subsection Outside the staff
330 * Blank music sheet::
331 * Analysis brackets::
335 @unnumberedsubsubsec Balloon help
337 Elements of notation can be marked and named with the help of a
338 square balloon. The primary purpose of this feature is to explain
341 The following example demonstrates its use.
343 @lilypond[quote,verbatim,fragment,ragged-right,relative=2]
344 \new Voice \with { \consists "Balloon_engraver" }
346 \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" }
347 <c-\balloonText #'(-2 . -2) \markup { "I'm a notehead" } >8
352 There are two music functions, @code{balloonText} and
353 @code{balloonGrobText}. The latter takes the name of the grob to
354 adorn, while the former may be used as an articulation on a note.
355 The other arguments are the offset and the text of the label.
358 @cindex notation, explaining
362 Internals Reference: @internalsref{text-balloon-interface}.
366 @unnumberedsubsubsec Grid lines
368 Vertical lines can be drawn between staves synchronized with the
371 @lilypond[ragged-right,quote,verbatim]
375 \consists "Grid_point_engraver" %% sets of grid
376 gridInterval = #(ly:make-moment 1 4)
381 \consists "Grid_line_span_engraver"
382 %% centers grid lines horizontally below noteheads
383 \override NoteColumn #'X-offset = #-0.5
394 %% centers grid lines vertically
395 \override Score.GridLine #'extra-offset = #'( 0.0 . 1.0 )
405 Examples: @lsrdir{education}
408 @node Blank music sheet
409 @unnumberedsubsubsec Blank music sheet
411 @cindex Sheet music, empty
412 @cindex Staves, blank sheet
414 A blank music sheet can be produced also by using invisible notes,
415 and removing @code{Bar_number_engraver}.
418 @lilypond[quote,verbatim]
419 \layout{ indent = #0 }
421 \repeat unfold 2 % Change this for more lines.
426 \override TimeSignature #'transparent = ##t
427 % un-comment this line if desired
428 % \override Clef #'transparent = ##t
430 \remove Bar_number_engraver
433 % modify these to get the staves you want
434 \new Staff \emptymusic
435 \new TabStaff \emptymusic
440 @node Analysis brackets
441 @unnumberedsubsubsec Analysis brackets
444 @cindex phrasing brackets
445 @cindex musicological analysis
446 @cindex note grouping bracket
448 Brackets are used in musical analysis to indicate structure in
449 musical pieces. LilyPond supports a simple form of nested
450 horizontal brackets. To use this, add the
451 @internalsref{Horizontal_bracket_engraver} to the
452 @internalsref{Staff} context. A bracket is started with
453 @code{\startGroup} and closed with @code{\stopGroup}.
455 @lilypond[quote,ragged-right,verbatim]
458 c4\startGroup\startGroup
461 c4\stopGroup\stopGroup
465 \Staff \consists "Horizontal_bracket_engraver"
471 Internals Reference: @internalsref{HorizontalBracket}.