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 c109df7b28ec497d7826252853cd8fde669786dd..6686f3fcfdf94c9cc3122512c1f310523e27a47c 100644 (file)
--- 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 c044cb119f9e5372a48bb0f958c7173299e8d11b..8ec83109257cab3caf67d76f1ea682a9ef9285ba 100644 (file)
--- 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.