lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond ./ChangeLog Documentation/user/example...


From: Mats Bengtsson
Subject: Re: lilypond ./ChangeLog Documentation/user/example...
Date: Mon, 27 Jun 2005 11:08:17 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511



Graham Percival wrote:
CVSROOT:        /cvsroot/lilypond
Module name:    lilypond
Branch:         
Changes by:     Graham Percival <address@hidden>  05/06/23 16:53:47
 ...

diff -u lilypond/Documentation/user/examples.itely:1.38 
lilypond/Documentation/user/examples.itely:1.39
--- lilypond/Documentation/user/examples.itely:1.38     Tue May  3 11:29:34 2005
+++ lilypond/Documentation/user/examples.itely  Thu Jun 23 16:53:47 2005
@@ -1402,6 +1402,7 @@
@example
 address@hidden@}
address@hidden@}
 address@hidden@}

As long as the user has to include the line himself, it's much better
to use the normal command \usepackage, instead of \RequirePackage
(which is intended to be used only within packages, where it loads the
package only of the user has not already done it), so the manual should
say:
address@hidden@}
address@hidden@}
address@hidden@}

My previous comments on using \RequirePackage where only intended for
the automatically generated code in lilypond-book.


 Normal LaTeX text.
Index: lilypond/Documentation/user/lilypond-book.itely
diff -u lilypond/Documentation/user/lilypond-book.itely:1.117 
lilypond/Documentation/user/lilypond-book.itely:1.118
--- lilypond/Documentation/user/lilypond-book.itely:1.117       Mon Jun 13 
10:06:37 2005
+++ lilypond/Documentation/user/lilypond-book.itely     Thu Jun 23 16:53:47 2005
@@ -190,7 +190,16 @@
 @end example
Running @command{lilypond-book} yields a file that can be further
-processed with address@hidden
+processed with address@hidden  Since @command{lilypond-book} produces
+lilypond snippets as @address@hidden@}}, you must
+add
+
address@hidden
address@hidden@}
address@hidden example

Same thing here, where it even could be worth mentioning that both
\usepackage{graphics} or \usepackage{graphicx} will work equally well.

   /Mats




reply via email to

[Prev in Thread] Current Thread [Next in Thread]