X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fnotation%2Feditorial.itely;h=56c05e8335c1a701f4d785435107fe78382b0b7d;hb=4ca01b6da8d60b0d8575be05ae974429c91becd5;hp=eec43dd741bcd24dada7446df197e6d452cecd9b;hpb=69f0ec479a6ade46d0a227755bb02562112c6743;p=lilypond.git

diff --git a/Documentation/notation/editorial.itely b/Documentation/notation/editorial.itely
index eec43dd741..56c05e8335 100644
--- a/Documentation/notation/editorial.itely
+++ b/Documentation/notation/editorial.itely
@@ -3,10 +3,11 @@
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
     When revising a translation, copy the HEAD committish of the
-    version that you are working on.  See TRANSLATION for details.
+    version that you are working on.  For details, see the Contributors'
+    Guide, node Updating translation committishes..
 @end ignore
 
-@c \version "2.12.0"
+@c \version "2.14.0"
 
 @node Editorial annotations
 @section Editorial annotations
@@ -148,7 +149,7 @@ Internals Reference:
 @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
@@ -165,7 +166,7 @@ c4-1 d-2 f-4 c^\markup { \finger "2 - 3" }
 @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]
@@ -176,8 +177,8 @@ that a note should be played with the thumb.
 @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>
@@ -188,19 +189,19 @@ staff, see @ref{Direction and placement}.
 
 @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}.
@@ -212,6 +213,10 @@ Internals Reference:
 @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
@@ -260,6 +265,14 @@ e4(\p f)--
 
 
 @seealso
+Learning Manual:
+@rlearning{Visibility and color of objects}.
+
+Notation Reference:
+@ref{Invisible rests},
+@ref{Visibility of objects},
+@ref{Hiding staves}.
+
 Snippets:
 @rlsr{Editorial annotations}.
 
@@ -302,10 +315,11 @@ e
 
 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.
@@ -373,9 +387,9 @@ An X11 color is not necessarily exactly the same shade as a
 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
@@ -403,7 +417,7 @@ c2 \parenthesize <c e g>
 c2 <c \parenthesize e g>
 @end lilypond
 
-Non-note objects may be parenthesized as well. For articulations, 
+Non-note objects may be parenthesized as well.  For articulations,
 a hyphen is needed before the @code{\parenthesize} command.
 
 @lilypond[verbatim,quote,relative=2]
@@ -464,7 +478,7 @@ Stems may be manually placed to point up or down; see
 
 @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}
 
 
@@ -619,7 +633,7 @@ lines.
 
 @snippets
 
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
 {grid-lines--changing-their-appearance.ly}