X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fuser%2Feditorial.itely;h=674605cb26caa2b4804133e15c4501871f2d8735;hb=76c76ae6a8328b0ad69f183cc7c36e166f15bd05;hp=139a0c6113d66d2f75108e5bd93087e3640c3b16;hpb=cd8c1d130352a5e2ccc070ee55a877a430e3ca58;p=lilypond.git diff --git a/Documentation/user/editorial.itely b/Documentation/user/editorial.itely index 139a0c6113..674605cb26 100644 --- a/Documentation/user/editorial.itely +++ b/Documentation/user/editorial.itely @@ -85,7 +85,7 @@ The @code{font-size} property can only be set on layout objects that 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: @@ -142,7 +142,7 @@ chord by adding them after the pitches. @end lilypond -@commonprop +@snippets @code{fingeringOrientations} are used to control where the fingering numbers are placed. @@ -193,6 +193,10 @@ b c @end lilypond +@predefined + +@code{\hideNotes}, @code{\unHideNotes} + @seealso Snippets: @lsrdir{Editorial,Editorial-annotations}. @@ -223,55 +227,35 @@ e @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 - -or a string +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. -@example -\override Beam #'color = #(x11-color "MediumTurquoise") -@end example - -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 - -@example -\override Beam #'color = #(x11-color "medium turquoise") -@end example +If @code{x11-color} cannot make sense of the parameter then the +color returned defaults to black. -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. - -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. - -@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'' +@lilypond[quote,ragged-right,verbatim,fragment,relative=2] +\override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2) +\set Staff.instrumentName = \markup { + \with-color #(x11-color 'navy) "Clarinet" } +gis4 a +\override Beam #'color = #(x11-color "medium turquoise") +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 @end lilypond You can get exact RGB colors by specifying the rgb-color number. -@lilypond[quote,ragged-right,verbatim] +@lilypond[quote,ragged-right,verbatim,fragment,relative=2] { \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2) \set Staff.instrumentName = \markup { @@ -298,14 +282,14 @@ the input}. Snippets: @lsrdir{Editorial,Editorial-annotations}. -@refbugs -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. (#blue, -#green, #red) - +@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}, @@ -321,33 +305,20 @@ for details. @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 ->2-\parenthesize -. -d g -< - c - \parenthesize fis -> +c2 < \parenthesize d> +<\parenthesize e> 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. - -@example -< \parenthesize NOTE> -@end example +Non-note objects may be parenthesized as well. @lilypond[relative=2,fragment,verbatim,ragged-right] -c4 -<\parenthesize d> -g -<\parenthesize d> +< c \parenthesize d g >2-\parenthesize -. d +g < c, \parenthesize fis > @end lilypond @seealso @@ -364,7 +335,7 @@ Whenever a note is found, a @code{Stem} object is created automatically. For whole notes and rests, they are also created but made invisible. -@refcommands +@predefined @funindex \stemUp @code{\stemUp}, @@ -374,7 +345,7 @@ made invisible. @code{\stemNeutral}. -@commonprop +@snippets @cindex stem, direction @cindex stem, up @@ -417,16 +388,19 @@ The following example demonstrates its use. @lilypond[quote,verbatim,fragment,ragged-right,relative=2] \new Voice \with { \consists "Balloon_engraver" } -{ - \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" } - 8 -} + { + \time 2/4 + \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" } + a'8 + 4. + } @end lilypond 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 @@ -448,15 +422,19 @@ notes. \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 + %% centers grid lines horizontally below note heads by default + %the grid lines are aligned with the left side of the notehead \override NoteColumn #'X-offset = #-0.5 + % this moves them to the right half a staff space } \new ChoirStaff << @@ -467,8 +445,9 @@ notes. } } \new Staff { - %% centers grid lines vertically \override Score.GridLine #'extra-offset = #'( 0.0 . 1.0 ) + % by default the grid lines join the middle line of each staff, + % this moves them up one staff space \stemDown \clef bass \relative c {