Add '-dcrop' option to ps and svg backends

[lilypond.git] / Documentation / usage.tely

diff --git a/Documentation/usage.tely b/Documentation/usage.tely
index 53baccd8933033b21bbf7e9fe68e17e0b3eb00c8..cd2dbffb1cdc2e571ed8e9428b66f8d35eb24823 100644 (file)
--- a/Documentation/usage.tely
+++ b/Documentation/usage.tely
@@ -3,7 +3,8 @@
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
     When revising a translation, copy the HEAD committish of the
-    version that you are working on.  See TRANSLATION for details.
+    version that you are working on.  For details, see the Contributors'
+    Guide, node Updating translation committishes..
 @end ignore
 
 @setfilename lilypond-usage.info
@@ -18,10 +19,14 @@ LilyPond version @version{}.  In addition, it suggests some
 @qq{best practices} for efficient usage.
 @end macro
 
+@c `Usage' was born 1999-10-11 with this commit:
+@c release: 1.2.13
+@c author: Han-Wen Nienhuys
+@c commit: 0cf97b5cdceecbba937f43ac827f4065aad5001e
+@c   file: Documentation/user/invoking.itexi
+
 @macro copyrightDeclare
-Copyright @copyright{} 
-1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
-by the authors.
+Copyright @copyright{} 1999--2015 by the authors.
 @end macro
 
 @set FDL
@@ -50,7 +55,7 @@ by the authors.
 * Running lilypond::               Operation.
 * Updating files with convert-ly:: Updating input files.
 * lilypond-book::                  Integrating text and music.
-* Converting from other formats::  Converting to lilypond source format.
+* External programs::              Mixing LilyPond and other programs.
 * Suggestions for writing files::  Best practices and effective bug-fixing.
 
 Appendices
@@ -65,11 +70,12 @@ Appendices
 
 @contents
 
+@allowcodebreaks false
 
 @include usage/running.itely
 @include usage/updating.itely
 @include usage/lilypond-book.itely
-@include usage/converters.itely
+@include usage/external.itely
 @include usage/suggestions.itely
 
 @include fdl.itexi