@node Editorial annotations
@section Editorial annotations
-@lilypondfile[ragged-right,line-width=16\cm,staffsize=16,quote]
-{editorial-headword.ly}
+@lilypondfile[quote]{editorial-headword.ly}
+
+This section discusses the various ways to change the appearance of
+notes and add analysis or educational emphasis.
@menu
* Inside the staff::
@node Inside the staff
@subsection Inside the staff
+This section discusses how to add emphasis to elements that are
+inside the staff.
@menu
* Selecting notation font size::
The easiest method of setting the font size of any context is by
setting the @code{fontSize} property.
-@lilypond[quote,fragment,relative=1,verbatim]
-c8
+@lilypond[quote,fragment,relative=2,verbatim,ragged-right]
+c4
\set fontSize = #-4
c f
\set fontSize = #3
-g
+g8 a
@end lilypond
@noindent
@code{font-size} property can also be set directly, so that only
certain layout objects are affected.
-@lilypond[quote,fragment,relative=1,verbatim]
-c8
+@lilypond[quote,fragment,relative=2,verbatim,ragged-right]
+c4
\override NoteHead #'font-size = #-4
c f
\override NoteHead #'font-size = #3
-g
+g8 a
@end lilypond
@cindex standard font size
use fonts. These are the ones supporting the @code{font-interface}
layout interface.
-@refcommands
+@predefined
The following commands set @code{fontSize} for the current voice:
Fingering instructions can be entered using
@var{note}-@var{digit}:
+Fingering instructions may be manually placed above or below the
+staff, see @ref{Controlling direction and placement}.
+
@lilypond[quote,verbatim,ragged-right,fragment,relative=2]
c4-1 d-2 f-4 e-3
@end lilypond
note should be played with the thumb.
@lilypond[quote,verbatim,ragged-right,fragment,relative=2]
-<a_\thumb a'-3>8 <b_\thumb b'-3>
+<a_\thumb a'-3>2 <b_\thumb b'-3>
@end lilypond
@cindex fingering chords
@end lilypond
-@commonprop
+@snippets
@code{fingeringOrientations} are used to control where the fingering
numbers are placed.
@cindex Hidden notes
@cindex Invisible notes
@cindex Transparent notes
-
@funindex \hideNotes
@funindex \unHideNotes
preparing theory or composition exercises.
@lilypond[quote,ragged-right,verbatim,relative=2,fragment]
-c4 d4
+c4 d
\hideNotes
-e4 f4
+e4 f
\unHideNotes
-g4 a
+g a
+\hideNotes
+b
+\unHideNotes
+c
@end lilypond
+@predefined
+
+@code{\hideNotes}, @code{\unHideNotes}
+
@seealso
Snippets: @lsrdir{Editorial,Editorial-annotations}.
Individual objects may be assigned colors. You may use the color
names listed in the @ref{List of colors}.
-@lilypond[quote,ragged-right,verbatim,fragment,relative=1]
+@lilypond[quote,ragged-right,verbatim,fragment,relative=2]
\override NoteHead #'color = #red
c4 c
\override NoteHead #'color = #(x11-color 'LimeGreen)
@cindex x11-color
The full range of colors defined for X11 can be accessed by using
-the Scheme function x11-color. The function takes one argument
-that can be a symbol
-
-@example
-\override Beam #'color = #(x11-color 'MediumTurquoise)
-@end example
+the Scheme function @code{x11-color}. The function takes one
+argument; this can be a symbol in the form @var{'FooBar} or a
+string in the form @var{"FooBar"}. The first form is quicker to
+write and is more efficient. However, using the second form it is
+possible to access X11 colors by the multi-word form of its name.
-or a string
+If @code{x11-color} cannot make sense of the parameter then the
+color returned defaults to black.
-@example
-\override Beam #'color = #(x11-color "MediumTurquoise")
-@end example
+@lilypond[quote,ragged-right,verbatim,fragment,relative=2]
-The first form is quicker to write and is more efficient.
-However, using the second form it is possible to access X11 colors
-by the multi-word form of its name
+\override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
+\set Staff.instrumentName = \markup {
+ \with-color #(x11-color 'navy) "Clarinet"
+}
-@example
+gis8 a
\override Beam #'color = #(x11-color "medium turquoise")
-@end example
+gis a
+\override Accidental #'color = #(x11-color 'DarkRed)
+gis a
+\override NoteHead #'color = #(x11-color "LimeGreen")
+gis a
+% this is deliberate nonsense; note that the stems remain black
+\override Stem #'color = #(x11-color 'Boggle)
+b2 cis
-If x11-color cannot make sense of the parameter then the color
-returned defaults to black. It should be obvious from the final
-score that something is wrong.
+@end lilypond
-This example illustrates the use of x11-color. Notice that the
-stem color remains black after being set to (x11-color 'Boggle),
-which is deliberate nonsense.
+You can get exact RGB colors by specifying the rgb-color number.
+
+@lilypond[quote,ragged-right,verbatim,fragment,relative=2]
-@lilypond[quote,ragged-right,verbatim]
-{
\override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
\set Staff.instrumentName = \markup {
\with-color #(x11-color 'navy) "Clarinet"
}
- \time 2/4
- gis''8 a''
- \override Beam #'color = #(x11-color "medium turquoise")
- gis'' a''
- \override NoteHead #'color = #(x11-color "LimeGreen")
- gis'' a''
- \override Stem #'color = #(x11-color 'Boggle)
- gis'' a''
-}
-@end lilypond
-
-
-TODO
-you can get exact RGB colors by specifying
-
-% black
-\override Stem #'color = #(rgb-color 0 0 0)
-% white
-\override Stem #'color = #(rgb-color 1 1 1)
-% dark blue
-\override Stem #'color = #(rgb-color 0 0 0.5)
+
+ %black
+ \override Stem #'color = #(rgb-color 0 0 0)
+ gis8 a
+ % white
+ \override Stem #'color = #(rgb-color 1 1 1)
+ gis8 a
+ % dark blue
+ \override Stem #'color = #(rgb-color 0 0 0.5)
+ gis4 a
+@end lilypond
@seealso
Snippets: @lsrdir{Editorial,Editorial-annotations}.
-@refbugs
-Not all x11 colors are distinguishable in a web browser. For web
-use normal colors are recommended.
-
+@knownissues
An x11 color is not necessarily exactly the same shade as a
-similarly named normal color.
+similarly named normal color.
+
+Not all x11 colors are distinguishable in a web browser i.e. a web browser
+might not display a difference between 'LimeGreen and 'ForestGreen. For
+web use normal colors are recommended (i.e. #blue, #green, #red).
+
Notes in a chord cannot be colored with @code{\override}; use
-@code{\tweak} instead. See @ref{Objects connected to the input},
-for details.
+@code{\tweak} instead, see @ref{Objects connected to the input}.
@node Parentheses
@cindex parentheses
Objects may be parenthesized by prefixing @code{\parenthesize} to
-the music event,
+the music event. This only functions inside chords; to
+parenthesize a single note it must be enclosed with @code{<>} as
+if it is a chord.
@lilypond[relative=2,fragment,verbatim,ragged-right]
-<
- c
- \parenthesize d
- g
->4-\parenthesize -.
+c2 < \parenthesize d>
@end lilypond
-This only functions inside chords, to parenthesize a single note it
-must be enclosed with @code{<>} as if it is a chord.
+Non-note objects may be parenthesized as well.
-@example
-< \parenthesize NOTE>
-@end example
+@lilypond[relative=2,fragment,verbatim,ragged-right]
+< c d g >2-\parenthesize -. d
+@end lilypond
@seealso
automatically. For whole notes and rests, they are also created but
made invisible.
-@refcommands
+@predefined
@funindex \stemUp
@code{\stemUp},
@code{\stemNeutral}.
-@commonprop
+@snippets
@cindex stem, direction
@cindex stem, up
@node Outside the staff
@subsection Outside the staff
+This section discusses how to add emphasis to elements in the staff
+from outside of the staff.
@menu
* Balloon help::
* Grid lines::
-* Blank music sheet::
* Analysis brackets::
@end menu
@lilypond[quote,verbatim,fragment,ragged-right,relative=2]
\new Voice \with { \consists "Balloon_engraver" }
-{
- \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" }
- <f-\balloonText #'(-2 . -2) \markup { "I'm a note head" } >8
-}
+ {
+ \time 2/4
+ \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" }
+ a8
+ <c, g'-\balloonText #'(-2 . -2) \markup { "I'm a note head" }
+c>4.
+ }
+
@end lilypond
-@noindent
There are two music functions, @code{balloonGrobText} and
-@code{balloonText}; the former takes the name of the grob to adorn,
-while the latter may be used as an articulation on a note. The other
-arguments are the offset and the text of the label.
+@code{balloonText}; The former is used like \once \override to
+attach text to any grob, and the latter is used like \tweak,
+typically within chords, to attach text to an individual note.
@cindex balloon
@cindex notation, explaining
\layout {
\context {
\Staff
- \consists "Grid_point_engraver" %% sets of grid
+ \consists "Grid_point_engraver"
+ % sets up grids
gridInterval = #(ly:make-moment 1 4)
+ % this sets the grid interval to 1 quarternote (crotchet)
}
}
\new Score \with {
\consists "Grid_line_span_engraver"
- %% centers grid lines horizontally below note heads
- \override NoteColumn #'X-offset = #-0.5
+ %% by default this centers grid lines horizontally below and to the
+ % left side of the notehead, the grid lines extend from
+ % the middle lines of each staff
}
\new ChoirStaff <<
}
}
\new Staff {
- %% centers grid lines vertically
- \override Score.GridLine #'extra-offset = #'( 0.0 . 1.0 )
\stemDown
\clef bass
\relative c {
>>
@end lilypond
-@seealso
-
-Snippets: @lsrdir{Editorial,Editorial-annotations}.
-
-
-@node Blank music sheet
-@subsubsection Blank music sheet
-
-@cindex sheet music, empty
-@cindex staves, blank sheet
-@cindex blank staff paper
-@cindex staff paper, blank
+To change the grid lines use \override.
-A blank music sheet can be produced also by using invisible notes,
-and removing @code{Bar_number_engraver}.
-
-@lilypond[quote,verbatim]
-\layout{ indent = #0 }
-emptymusic = {
- \repeat unfold 2 % Change this for more lines.
- { s1\break }
- \bar "|."
+@lilypond[ragged-right,quote,verbatim]
+\layout {
+ \context {
+ \Staff
+ \consists "Grid_point_engraver"
+ % sets up grids
+ gridInterval = #(ly:make-moment 1 4)
+ % this sets the grid interval to 1 quarternote (crotchet)
+ }
}
+
\new Score \with {
- \override TimeSignature #'transparent = ##t
-% un-comment this line if desired
-% \override Clef #'transparent = ##t
- defaultBarType = #""
- \remove Bar_number_engraver
-} <<
-
-% modify these to get the staves you want
- \new Staff \emptymusic
- \new TabStaff \emptymusic
+ \consists "Grid_line_span_engraver"
+ \override NoteColumn #'X-offset = #-0.5
+ % this moves them to the right half a staff space
+}
+
+\new ChoirStaff <<
+ \new Staff {
+ \stemUp
+ \relative {
+ c'4. d8 e8 f g4
+ }
+ }
+ \new Staff {
+ \override Score.GridLine #'extra-offset = #'( 0.0 . 1.0 )
+ % this moves them up one staff space from the default position
+ \stemDown
+ \clef bass
+ \relative c {
+ c4 g' f e
+ }
+ }
>>
@end lilypond
Snippets: @lsrdir{Editorial,Editorial-annotations}.
+
+
@node Analysis brackets
@subsubsection Analysis brackets
\layout {
\context {
\Staff \consists "Horizontal_bracket_engraver"
-}}}
+ }
+ }
+}
@end lilypond
@seealso
Internals Reference: @internalsref{HorizontalBracket},
@internalsref{Horizontal_bracket_engraver}, @internalsref{Staff}.
-