From c6152932c5610e7ac834066d8dbea8f9af31260c Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Sat, 17 Oct 2009 22:09:25 +0100 Subject: [PATCH] Doc build: fix broken xrefs. --- Documentation/extending/programming-interface.itely | 2 +- Documentation/extending/scheme-tutorial.itely | 2 +- Documentation/learning/fundamental.itely | 3 ++- Documentation/learning/tutorial.itely | 2 +- Documentation/learning/tweaks.itely | 2 +- Documentation/notation/changing-defaults.itely | 2 +- Documentation/usage/lilypond-book.itely | 2 +- Documentation/usage/running.itely | 2 +- Documentation/usage/suggestions.itely | 10 +++++----- 9 files changed, 14 insertions(+), 13 deletions(-) diff --git a/Documentation/extending/programming-interface.itely b/Documentation/extending/programming-interface.itely index 471276f0b4..cfde6b712c 100644 --- 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 fbd8879a11..20fe66e381 100644 --- 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 171e9618e1..9ca845a196 100644 --- 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 f048922cbc..31993eb0b3 100644 --- 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 9c0b98edba..921751667b 100644 --- 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 ef8e5f737c..61ad048b5f 100644 --- 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 7fe3090315..097219a020 100644 --- 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 03a822fd2b..d92e6f1403 100644 --- 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 dc1cb14f6c..e3df2fd7f1 100644 --- 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} + -- 2.39.5