Doc: clean up @file{} entries

[lilypond.git] / Documentation / notation / notation-appendices.itely

diff --git a/Documentation/notation/notation-appendices.itely b/Documentation/notation/notation-appendices.itely
index 7fdbe53ae5678b0d7c5b00c5eab17cc2a5dc3fb9..0669a5933e35c637147f27b3eeb5cf3409d634b4 100644 (file)
--- a/Documentation/notation/notation-appendices.itely
+++ b/Documentation/notation/notation-appendices.itely
@@ -8,29 +8,11 @@
     Guide, node Updating translation committishes..
 @end ignore
 
-@c \version "2.12.0"
+@c \version "2.13.36"
 
 @node Notation manual tables
 @appendix Notation manual tables
 
-@c Please do not delete the following @ignore block.
-@ignore
-Note for editors and translators: In the following menu, two entries
-are needed to link to a pair of automatically generated sections.
-Please keep them and, if using emacs, do not run
-texinfo-all-menus-update without manually restoring them back.  These
-menu entries are:
-
-* Text markup commands::
-* Text markup list commands::
-
-and they should go just after
-* Note head styles::
-
-and just before
-* List of articulations::
-@end ignore
-
 @menu
 * Chord name chart::
 * Common chord modifiers::
@@ -214,11 +196,11 @@ Minor-major seventh
 @tab
 Minor triad, major seventh
 @tab
-@code{maj7.3-}
+@code{m7+}
 @tab
 @lilypond[line-width=3\cm,noragged-right, notime]
 \chordmode {
-  c1:maj7.3-
+  c1:m7+
 }
 @end lilypond
 
@@ -404,6 +386,33 @@ Perfect fourth, perfect fifth
 }
 @end lilypond
 
+@item
+Power chord (two-voiced)
+@tab
+Perfect fifth
+@tab
+@code{1.5}
+@tab
+@lilypond[line-width=3\cm,noragged-right, notime]
+\chordmode {
+  \powerChords
+  c1:1.5
+}
+@end lilypond
+
+@item
+Power chord (three-voiced)
+@tab
+Perfect fifth, octave
+@tab
+@code{1.5.8}
+@tab
+@lilypond[line-width=3\cm,noragged-right, notime]
+\chordmode {
+  \powerChords
+  c1:1.5.8
+}
+@end lilypond
 
 @end multitable
 
@@ -853,10 +862,21 @@ The following styles may be used for note heads.
 
 @lilypondfile[noindent]{note-head-style.ly}
 
+
+@node Text markup commands
+@appendixsec Text markup commands
+
 @include markup-commands.tely
 
+
+@node Text markup list commands
+@appendixsec Text markup list commands
+
+The following commands can all be used with @code{\markuplines}:
+
 @include markup-list-commands.tely
 
+
 @node List of articulations
 @appendixsec List of articulations
 
@@ -1020,7 +1040,7 @@ or in the source code.
 
 An association list or @strong{alist} for short is a Scheme pair
 which associates a value with a key: @w{@code{(key . value)}}.  For
-example, in @file{scm/lily.scm}, the alist
+example, in @file{scm/@/lily@/.scm}, the alist
 @w{@qq{type-p-name-alist}} associates certain type predicates
 (e.g.@tie{}@code{ly:music?}) with names (e.g.@tie{}@qq{music}) so
 that type-check failures can be reported with a console message that
@@ -1161,10 +1181,10 @@ Internals Reference:
 A @strong{lexer} is a program which converts a sequence of
 characters into a sequence of tokens, a process called lexical
 analysis.  The LilyPond lexer converts the stream obtained from an
-input @file{.ly} file into a tokenized stream more suited to the
+input @file{@/.ly} file into a tokenized stream more suited to the
 next stage of processing - parsing, for which see @ref{parser}.
 The LilyPond lexer is built with Flex from the lexer file
-@file{lily/lexer.ll} which contains the lexical rules.  This file
+@file{lily/@/lexer@/.ll} which contains the lexical rules.  This file
 is part of the source code and is not included in the LilyPond
 binary installation.
 
@@ -1213,7 +1233,7 @@ tree of tokens whose root is the grammar's start symbol.  If this
 cannot be achieved the file is invalid and an appropriate error
 message is produced.  The syntactic groupings and the rules for
 constructing the groupings from their parts for the LilyPond syntax
-are defined in @file{lily/parser.yy} and shown in Backus Normal Form
+are defined in @file{lily/@/parser@/.yy} and shown in Backus Normal Form
 (BNF) in @ref{LilyPond grammar}.  This file is used to build the
 parser during the program build by the parser generator, Bison.  It
 is part of the source code and is not included in the LilyPond
@@ -1243,7 +1263,7 @@ These are variables defined directly in Scheme.  Their direct
 use by users is strongly discouraged, because their scoping
 semantics can be confusing.
 
-When the value of such a variable is changed in a @code{.ly} file,
+When the value of such a variable is changed in a @file{@/.ly} file,
 the change is global, and unless explicitly reverted, the new value
 will persist to the end of the file, affecting subsequent
 @code{\score} blocks as well as external files added with the
@@ -1302,7 +1322,7 @@ smobs are created from C++ objects through macros.  There are two
 types of smob objects: simple smobs, intended for simple immutable
 objects like numbers, and complex smobs, used for objects with
 identities.  If you have access to the LilyPond sources, more
-information can be found in @file{lily/includes/smob.hh}.
+information can be found in @file{lily/@/includes/@/smob@/.hh}.
 
 @node stencil
 @unnumberedsubsec stencil