From: Trevor Daniels Date: Thu, 1 Jan 2009 12:49:58 +0000 (+0000) Subject: Docs: NR 3.3.1 Fix refs X-Git-Tag: release/2.12.2-1~32^2~17^2~7^2 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=d26834822dca971c9c4e13cd49bfe469cced95a1;p=lilypond.git Docs: NR 3.3.1 Fix refs --- diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely index b87520ca1f..a9facc6bb8 100644 --- a/Documentation/user/input.itely +++ b/Documentation/user/input.itely @@ -884,19 +884,21 @@ and in main.ly write Files which are to be included in many scores may be placed in the LilyPond directory @file{../ly}. (The location of this -directory is installation-dependent - see @rlearning{Other sources -of information}). These files can then be included simply by -naming them on an @code{\include} statement. This is how the -language-dependent files like @file{english.ly} are included. +directory is installation-dependent - see +@rlearning{Other sources of information}). These files can then +be included simply by naming them on an @code{\include} statement. +This is how the language-dependent files like @file{english.ly} are +included. LilyPond includes a number of files by default when you start the program. These includes are not apparent to the user, but the files may be identified by running @code{lilypond --verbose} from the command line. This will display a list of paths and files that LilyPond uses, along with much other information. Alternatively, -the more important of these files are discussed in @rlearning{Other -sources of information}. These files may be edited, but changes to -them will be lost on installing a new version of LilyPond. +the more important of these files are discussed in +@rlearning{Other sources of information}. These files may be +edited, but changes to them will be lost on installing a new +version of LilyPond. Some simple examples of using @code{\include} are shown in @rlearning{Scores and parts}.