From: James Lowe <pkx166h@gmail.com>
Date: Wed, 17 Feb 2016 11:03:54 +0000 (+0000)
Subject: Doc: NR and Usage - improved links for SVG
X-Git-Tag: release/2.19.37-1~10
X-Git-Url: https://git.donarmstrong.com/?p=lilypond.git;a=commitdiff_plain;h=1dca301bb94bbd34e159afc4b769ddc70f058b41

Doc: NR and Usage - improved links for SVG

Issue 4774

Added a few extra words
and an @ref so that users
do not miss some 'extra'
considerations when SVG
is the intended output
file type.
---

diff --git a/Documentation/notation/input.itely b/Documentation/notation/input.itely
index c109df7b28..6686f3fcfd 100644
--- a/Documentation/notation/input.itely
+++ b/Documentation/notation/input.itely
@@ -2729,11 +2729,10 @@ voices and staves, saving even more time.
 @cindex EPS output
 
 The default output formats for the printed score are Portable
-Document Format (PDF) and PostScript (PS).  Scalable Vector
-Graphics (SVG), Encapsulated PostScript (EPS) and Portable
-Network Graphics (PNG) output formats are also available through
-command line options, see
-@rprogram{Basic command line options for LilyPond}.
+Document Format (PDF) and PostScript (PS).  Portable
+Network Graphics (PNG), Scalable Vector Graphics (SVG) and Encapsulated
+PostScript (EPS) output is available through the command line option,
+see @rprogram{Basic command line options for LilyPond}.
 
 
 @node Replacing the notation font
diff --git a/Documentation/usage/running.itely b/Documentation/usage/running.itely
index c044cb119f..8ec8310925 100644
--- a/Documentation/usage/running.itely
+++ b/Documentation/usage/running.itely
@@ -246,6 +246,10 @@ which formats should be written.  Choices for @code{format} are
 
 Example: @code{lilypond -fpng @var{filename}.ly}
 
+@noindent
+For @code{svg} and @code{eps} formats use the @code{-dbackend} option.
+See @ref{Advanced command line options for LilyPond}.
+
 @item -h, --help
 Show a summary of usage.