Guide, node Updating translation committishes..
@end ignore
-@c \version "2.12.0"
+@c \version "2.17.11"
@node Editorial annotations
@section Editorial annotations
@lilypond[verbatim,quote,relative=2]
\set fontSize = #3
c4.-> d8---3
-\override NoteHead #'font-size = #-4
+\override NoteHead.font-size = #-4
c4.-> d8---3
-\override Script #'font-size = #2
+\override Script.font-size = #2
c4.-> d8---3
-\override Stem #'font-size = #-5
+\override Stem.font-size = #-5
c4.-> d8---3
@end lilypond
@code{\huge}.
@endpredefined
-
@seealso
Snippets:
@rlsr{Editorial annotations}.
@funindex finger
Fingering instructions can be entered using
-@var{note}-@var{digit}:
+@samp{@var{note}-@var{digit}}:
@lilypond[verbatim,quote,relative=2]
c4-1 d-2 f-4 e-3
@end lilypond
-Markup texts may be used for finger changes.
+Markup texts or strings may be used for finger changes.
@lilypond[verbatim,quote,relative=2]
-c4-1 d-2 f-4 c^\markup { \finger "2 - 3" }
+c4-1 d-2 f\finger \markup \tied-lyric #"4~3" c\finger "2 - 3"
@end lilypond
@cindex thumb-script
@funindex \thumb
@funindex thumb
-A thumb-script can be added (e.g., in cello music) to indicate
+A thumb-script can be added (e.g. cello music) to indicate
that a note should be played with the thumb.
@lilypond[verbatim,quote,relative=2]
@cindex fingering instructions for chords
@cindex chords, fingering
-Fingerings for chords can also be added to individual notes of the
-chord by adding them after the pitches.
+Fingerings for chords can also be added to individual notes by
+adding them after the pitches.
@lilypond[verbatim,quote,relative=2]
<c-1 e-2 g-3 b-5>2 <d-1 f-2 a-3 c-5>
@snippets
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
{controlling-the-placement-of-chord-fingerings.ly}
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{allowing-fingerings-to-be-printed-inside-the-staff.ly}
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{avoiding-collisions-with-chord-fingerings.ly}
-
@seealso
Notation Reference:
-@ref{Direction and placement}
+@ref{Direction and placement}.
Snippets:
@rlsr{Editorial annotations}.
@rinternals{New_fingering_engraver},
@rinternals{Fingering}.
+@knownissues
+By default, numbers greater than 9 are not supported using
+@samp{@var{note}-@var{digit}}.
+
@node Hidden notes
@unnumberedsubsubsec Hidden notes
c
@end lilypond
-Notation objects which are attached to invisible notes are still
-visible.
+Note heads, stems, and flags, and rests are invisible. Beams
+are invisible if they start on a hidden note. Objects that are
+attached to invisible notes are still visible.
@lilypond[verbatim,quote,relative=2]
-c4( d)
+e8(\p f g a)--
\hideNotes
-e4(\p f)--
+e8(\p f g a)--
@end lilypond
@code{\unHideNotes}.
@endpredefined
-
@seealso
Learning Manual:
@rlearning{Visibility and color of objects}.
are listed in the @ref{List of colors}.
@lilypond[verbatim,quote,relative=2]
-\override NoteHead #'color = #red
+\override NoteHead.color = #red
c4 c
-\override NoteHead #'color = #(x11-color 'LimeGreen)
+\override NoteHead.color = #(x11-color 'LimeGreen)
d
-\override Stem #'color = #blue
+\override Stem.color = #blue
e
@end lilypond
The full range of colors defined for X11 can be accessed by using
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.
+argument; this can be a symbol in the form @code{'@var{FooBar}} or
+a string in the form @code{"@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.
If @code{x11-color} cannot make sense of the parameter then the
color returned defaults to black.
@lilypond[verbatim,quote,relative=2]
-\override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
+\override Staff.StaffSymbol.color = #(x11-color 'SlateBlue2)
\set Staff.instrumentName = \markup {
\with-color #(x11-color 'navy) "Clarinet"
}
gis8 a
-\override Beam #'color = #(x11-color "medium turquoise")
+\override Beam.color = #(x11-color "medium turquoise")
gis a
-\override Accidental #'color = #(x11-color 'DarkRed)
+\override Accidental.color = #(x11-color 'DarkRed)
gis a
-\override NoteHead #'color = #(x11-color "LimeGreen")
+\override NoteHead.color = #(x11-color "LimeGreen")
gis a
% this is deliberate nonsense; note that the stems remain black
-\override Stem #'color = #(x11-color 'Boggle)
+\override Stem.color = #(x11-color 'Boggle)
b2 cis
@end lilypond
@code{rgb-color}.
@lilypond[verbatim,quote,relative=2]
-\override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
+\override Staff.StaffSymbol.color = #(x11-color 'SlateBlue2)
\set Staff.instrumentName = \markup {
\with-color #(x11-color 'navy) "Clarinet"
}
-\override Stem #'color = #(rgb-color 0 0 0)
+\override Stem.color = #(rgb-color 0 0 0)
gis8 a
-\override Stem #'color = #(rgb-color 1 1 1)
+\override Stem.color = #(rgb-color 1 1 1)
gis8 a
-\override Stem #'color = #(rgb-color 0 0 0.5)
+\override Stem.color = #(rgb-color 0 0 0.5)
gis4 a
@end lilypond
-
@seealso
Notation Reference:
@ref{List of colors}, @ref{The
Snippets:
@rlsr{Editorial annotations}.
-
@cindex x11 color
@cindex colored notes in chords
@cindex notes, colored in chords
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 @code{'LimeGreen}
-and @code{'ForestGreen}. For web use normal colors are recommended
-(i.e., @code{#blue}, @code{#green}, @code{#red}).
-
+a web browser might not display a difference between @code{LimeGreen}
+and @code{ForestGreen}. For web use normal colors are recommended
+(i.e., @code{blue}, @code{green}, @code{red}).
Notes in a chord cannot be colored with @code{\override}; use
@code{\tweak} instead, see @ref{The tweak command}.
@cindex notes, ghost
@cindex notes, parenthesized
@cindex parentheses
+@cindex brackets
@funindex \parenthesize
@funindex parenthesize
c2 \parenthesize r
@end lilypond
-
@seealso
Snippets:
@rlsr{Editorial annotations}.
@rinternals{ParenthesesItem},
@rinternals{parentheses-interface}.
-
@knownissues
-
Parenthesizing a chord prints parentheses around each individual
note, instead of a single large parenthesis around the entire
chord.
@snippets
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
{default-direction-of-stems-on-the-center-line-of-the-staff.ly}
-
@seealso
Notation Reference:
@ref{Direction and placement}.
}
@end lilypond
-
@predefined
@code{\balloonLengthOn},
@code{\balloonLengthOff}.
@endpredefined
-
@seealso
Snippets:
@rlsr{Editorial annotations}.
\context {
\Staff
\consists "Grid_point_engraver"
- gridInterval = #(ly:make-moment 1 4)
+ gridInterval = #(ly:make-moment 1/4)
}
\context {
\Score
@snippets
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
{grid-lines--changing-their-appearance.ly}
-
@seealso
Snippets:
@rlsr{Editorial annotations}.
}
@end lilypond
-
@seealso
Snippets:
@rlsr{Editorial annotations}.
@rinternals{HorizontalBracket},
@rinternals{horizontal-bracket-interface},
@rinternals{Staff}.
-
projects / lilypond.git / blobdiff