From: Carl Sorensen <c_sorensen@byu.edu>
Date: Thu, 15 Apr 2010 03:24:12 +0000 (-0600)
Subject: Doc: Add links to troubleshooting to Learning Manual
X-Git-Tag: release/2.13.18-1~6
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=1ef29afb6ea292c86ce25f7c53e3e3737beb5aef;p=lilypond.git

Doc: Add links to troubleshooting to Learning Manual
---

diff --git a/Documentation/learning/tutorial.itely b/Documentation/learning/tutorial.itely
index da4acb948d..0b55738695 100644
--- a/Documentation/learning/tutorial.itely
+++ b/Documentation/learning/tutorial.itely
@@ -20,6 +20,7 @@ This chapter gives a basic introduction to working with LilyPond.
 @menu
 * Compiling a file::
 * How to write input files::
+* What if it doesn't work::
 * How to read the manuals::
 @end menu
 
@@ -567,6 +568,43 @@ comments:
 @end itemize
 
 
+@node What if it doesn't work
+@section What if it doesn't work
+
+@cindex troubleshooting
+
+Sometimes LilyPond doesn't produce the output you expect.  This
+section provides some links to help you solve the problems you
+might encounter.
+
+
+@menu
+* General troubleshooting tips::
+* Some common errors::
+@end menu
+
+@node General troubleshooting tips
+@subsection General troubleshooting tips
+
+Troubleshooting LilyPond problems can be challenging for
+people who are used to a graphical interface, because invalid
+input files can be created.  When this happens, a logical approach
+is the best way to identify and solve the problem.  Some guidelines
+to help you learn to do this are provided in @rprogram{Troubleshooting}.
+
+
+@node Some common errors
+@subsection Some common errors
+
+@cindex common errors
+@cindex errors, common
+
+There are a few common errors that are difficult to troubleshoot
+based simply on the error messages that are displayed.  These are
+described in @rprogram{Common errors}.
+
+
+
 @node How to read the manuals
 @section How to read the manuals