]> git.donarmstrong.com Git - lilypond.git/blobdiff - Documentation/notation/changing-defaults.itely
Merge branch 'lilypond/translation' of ssh://jomand@git.sv.gnu.org/srv/git/lilypond
[lilypond.git] / Documentation / notation / changing-defaults.itely
index bb1013e249b93448b5fb3bbfb098a5687de3e8d9..5ea8a2ebb5cef9e2f9ba9d559e61f75febdf58f1 100644 (file)
@@ -744,6 +744,22 @@ after calling @code{\RemoveEmptyStaffContext}, ie
 @node Defining new contexts
 @subsection Defining new contexts
 
+@cindex contexts, defining new
+@cindex engravers, including in contexts
+
+@funindex \alias
+@funindex alias
+@funindex \name
+@funindex name
+@funindex \type
+@funindex type
+@funindex \consists
+@funindex consists
+@funindex \accepts
+@funindex accepts
+@funindex \denies
+@funindex denies
+
 Specific contexts, like @code{Staff} and @code{Voice}, are made of
 simple building blocks.  It is possible to create new types of
 contexts with different combinations of engraver plug-ins.
@@ -1417,8 +1433,11 @@ such as
 
 
 @seealso
-Internals: @rinternals{OverrideProperty}, @rinternals{RevertProperty},
-@rinternals{PropertySet}, @rinternals{Backend}, and
+Internals:
+@rinternals{OverrideProperty},
+@rinternals{RevertProperty},
+@rinternals{PropertySet},
+@rinternals{Backend},
 @rinternals{All layout objects}.
 
 
@@ -2024,7 +2043,8 @@ The default order in which contexts are laid out and the
 
 @seealso
 Learning Manual:
-@rlearning{An extra staff appears}.
+@rprogram{An extra staff appears}.
+
 
 @node Distances and measurements
 @subsection Distances and measurements
@@ -2412,8 +2432,10 @@ hairpins with @code{\!}.
 
 
 @seealso
-Internals Reference: @rinternals{TextSpanner},
-@rinternals{Glissando}, @rinternals{VoiceFollower},
+Internals Reference:
+@rinternals{TextSpanner},
+@rinternals{Glissando},
+@rinternals{VoiceFollower},
 @rinternals{TrillSpanner},
 @rinternals{line-spanner-interface}.
 
@@ -2561,7 +2583,7 @@ beginning of a line.  Or to be more precise, before a line break,
 where there is no line break, or after a line break.
 
 Alternatively, these eight combinations may be specified
-by pre-defined functions, defined in @file{scm/output-lib.scm},
+by pre-defined functions, defined in @file{scm/@/output@/-lib@/.scm},
 where the last three columns indicate whether the layout objects
 will be visible in the positions shown at the head of the columns: