Doc build: fix broken xrefs.

diff --git a/Documentation/extending/programming-interface.itely b/Documentation/extending/programming-interface.itely
index 471276f0b41c709ec37c8ffd92e559e83ab5da91..cfde6b712cc8d4d1d1a29f9eb64a979d2b690386 100644 (file)
--- a/Documentation/extending/programming-interface.itely
+++ b/Documentation/extending/programming-interface.itely
@@ -14,7 +14,7 @@
 
 Advanced tweaks may be performed by using Scheme.  If you are
 not familiar with Scheme, you may wish to read our
-@rlearning{Scheme tutorial}.
+@ref{Scheme tutorial}.
 
 @menu
 * Music functions::

diff --git a/Documentation/extending/scheme-tutorial.itely b/Documentation/extending/scheme-tutorial.itely
index fbd8879a11ca50ce38a87d1c4522d5c296381b16..20fe66e381aa99808befa1322f03c96cdd7ecb86 100644 (file)
--- a/Documentation/extending/scheme-tutorial.itely
+++ b/Documentation/extending/scheme-tutorial.itely
@@ -269,7 +269,7 @@ commands like
 @code{\override TextScript #'extra-offset = ( 1 . -1)}.  But
 we have even more power if we use Scheme.  For a full explanation
 of this, see the @ref{Scheme tutorial}, and
-@ruser{Interfaces for programmers}.
+@ref{Interfaces for programmers}.
 
 We can use Scheme to simply @code{\override} commands,
 

diff --git a/Documentation/learning/fundamental.itely b/Documentation/learning/fundamental.itely
index 171e9618e1adaa9846ed161aef4f72e6da463544..9ca845a196fc425fbdbe51728f6fbe882704b96e 100644 (file)
--- a/Documentation/learning/fundamental.itely
+++ b/Documentation/learning/fundamental.itely
@@ -3031,7 +3031,8 @@ padText =
 @end lilypond
 
 Using variables is also a good way to reduce work if the
-LilyPond input syntax changes (see @rprogram{Updating old input files}).  If
+LilyPond input syntax changes (see
+@rprogram{Updating files with convert-ly}).  If
 you have a single definition (such as @code{\dolce}) for all your
 input files (see @ref{Style sheets}), then if the syntax changes, you
 only need to update your single @code{\dolce} definition,

diff --git a/Documentation/learning/tutorial.itely b/Documentation/learning/tutorial.itely
index f048922cbc18d9056fee38abe628a77b284039b9..31993eb0b3b7ac80523e56755bcf58f992b26c41 100644 (file)
--- a/Documentation/learning/tutorial.itely
+++ b/Documentation/learning/tutorial.itely
@@ -9,7 +9,7 @@
 
 @c \version "2.12.0"
 
-@node Tutorial 
+@node Tutorial
 @chapter Tutorial
 
 This chapter gives a basic introduction to working with LilyPond.

diff --git a/Documentation/learning/tweaks.itely b/Documentation/learning/tweaks.itely
index 9c0b98edba1b943022a5e66c9f6e408590d6f96f..921751667b1c9bf0013476da2a1afabdf50f1c9c 100644 (file)
--- a/Documentation/learning/tweaks.itely
+++ b/Documentation/learning/tweaks.itely
@@ -305,7 +305,7 @@ a b c
 There is another form of the override command,
 @code{\overrideProperty}, which is occasionally required.
 We mention it here for completeness, but for details see
-@ruser{Difficult tweaks}.
+@rextend{Difficult tweaks}.
 @c Maybe explain in a later iteration  -td
 
 @strong{\tweak command}

diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely
index ef8e5f737cd9dc57e4560553b092f88e23c2077e..61ad048b5f823840565ee0656b6ea3121e45e9a7 100644 (file)
--- a/Documentation/notation/changing-defaults.itely
+++ b/Documentation/notation/changing-defaults.itely
@@ -36,7 +36,7 @@ Internally, LilyPond uses Scheme (a LISP dialect) to provide
 infrastructure.  Overriding layout decisions in effect accesses the
 program internals, which requires Scheme input.  Scheme elements are
 introduced in a @code{.ly} file with the hash mark
-@code{#}.@footnote{@rlearning{Scheme tutorial}, contains a short tutorial
+@code{#}.@footnote{@rextend{Scheme tutorial}, contains a short tutorial
 on entering numbers, lists, strings, and symbols in Scheme.}
 
 

diff --git a/Documentation/usage/lilypond-book.itely b/Documentation/usage/lilypond-book.itely
index 7fe30903156d3239d4ebdcf4fbaf5d222015e01c..097219a020ae686099d156eb848f66a3b9a5e8a8 100644 (file)
--- a/Documentation/usage/lilypond-book.itely
+++ b/Documentation/usage/lilypond-book.itely
@@ -990,7 +990,7 @@ message like @qq{Output would overwrite input file}.
 
 These templates are for use with @code{lilypond-book}.  If you're not familiar
 with this program, please refer to 
-@rprogram{lilypond-book}.
+@ref{lilypond-book}.
 
 @subsection LaTeX
 

diff --git a/Documentation/usage/running.itely b/Documentation/usage/running.itely
index 03a822fd2b2ad409520068ceb60d2865a1b1feb7..d92e6f140318a6c4bff29361940248f098dca5a4 100644 (file)
--- a/Documentation/usage/running.itely
+++ b/Documentation/usage/running.itely
@@ -29,7 +29,7 @@ This chapter details the technicalities of running LilyPond.
 @section Normal usage
 
 Most users run LilyPond through a GUI; if you have not done so
-already, read @rlearning{Introduction}.  If you use an alternate
+already, please read the @rlearning{Tutorial}.  If you use an alternate
 editor to write lilypond files, see the documentation for that
 program.
 

diff --git a/Documentation/usage/suggestions.itely b/Documentation/usage/suggestions.itely
index dc1cb14f6c5592a8bed384d57705cb06cb4bfca3..e3df2fd7f148b5e914542c3e9381de91d7f45a42 100644 (file)
--- a/Documentation/usage/suggestions.itely
+++ b/Documentation/usage/suggestions.itely
@@ -601,8 +601,8 @@ copy out\myproject.pdf MyProject.pdf
 
 
 @seealso
-Application Usage:
-FIXME
-@c @rprogram{Setup for MacOS X},
-@rprogram{Command-line usage},
-@rprogram{lilypond-book}
+
+This manual:
+@ref{Command-line usage},
+@ref{lilypond-book}
+