CVSROOT: /cvsroot/lilypond
Module name: lilypond
Branch:
Changes by: Graham Percival <[EMAIL PROTECTED]> 05/05/26 19:15:08
Modified files:
. : ChangeLog
Documentation/user: advanced-notation.itely basic-notation.itely
global.itely instrument-notation.itely
introduction.itely invoking.itely
lilypond.tely tutorial.itely
Log message:
Rearranging, editing, clean-up.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ChangeLog.diff?tr1=1.3664&tr2=1.3665&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/advanced-notation.itely.diff?tr1=1.29&tr2=1.30&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/basic-notation.itely.diff?tr1=1.22&tr2=1.23&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/global.itely.diff?tr1=1.13&tr2=1.14&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/instrument-notation.itely.diff?tr1=1.32&tr2=1.33&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/introduction.itely.diff?tr1=1.139&tr2=1.140&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/invoking.itely.diff?tr1=1.32&tr2=1.33&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/lilypond.tely.diff?tr1=1.130&tr2=1.131&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/tutorial.itely.diff?tr1=1.257&tr2=1.258&r1=text&r2=text
Patches:
Index: lilypond/ChangeLog
diff -u lilypond/ChangeLog:1.3664 lilypond/ChangeLog:1.3665
--- lilypond/ChangeLog:1.3664 Thu May 26 12:57:16 2005
+++ lilypond/ChangeLog Thu May 26 19:15:07 2005
@@ -1,3 +1,10 @@
+2005-05-26 Graham Percival <[EMAIL PROTECTED]>
+
+ * Documentation/user/lilypond.tely, advanced-notation.itely,
+ basic-notation.itely, instrument-notation.itely, global.itely,
+ introduction.itely, tutorial.itely: rearranging, editing,
+ clean-up.
+
2005-05-26 Han-Wen Nienhuys <[EMAIL PROTECTED]>
* lily/pfb.cc (LY_DEFINE): progress indication for opening ttf and
Index: lilypond/Documentation/user/advanced-notation.itely
diff -u lilypond/Documentation/user/advanced-notation.itely:1.29
lilypond/Documentation/user/advanced-notation.itely:1.30
--- lilypond/Documentation/user/advanced-notation.itely:1.29 Thu May 26
00:09:53 2005
+++ lilypond/Documentation/user/advanced-notation.itely Thu May 26 19:15:08 2005
@@ -18,7 +18,6 @@
* Contemporary notation::
* Educational use::
* Automatic notation::
-* Other::
@end menu
@@ -201,6 +200,9 @@
@end lilypond
@noindent
+See @ref{Overview of text markup commands} for a list of all
+commands.
+
@code{\markup} is primarily used for @internalsref{TextScript}s,
but it can also be used anywhere text is called in lilypond
@@ -270,6 +272,8 @@
@seealso
+This manual: @ref{Overview of text markup commands}.
+
Program reference: @internalsref{TextScript}.
Init files: @file{scm/@/new@/-markup@/.scm}.
@@ -1443,6 +1447,7 @@
@menu
* Polymetric notation::
+* Time administration::
* Clusters::
* Special fermatas::
* Special noteheads::
@@ -1579,6 +1584,53 @@
aligned vertically, but bar lines distort the regular spacing.
[EMAIL PROTECTED] Time administration
[EMAIL PROTECTED] Time administration
+
[EMAIL PROTECTED] Time administration
+
+Time is administered by the @internalsref{Time_signature_engraver},
+which usually lives in the @internalsref{Score} context. The
+bookkeeping deals with the following variables
+
[EMAIL PROTECTED] @code
[EMAIL PROTECTED] currentBarNumber
+The measure number.
+
[EMAIL PROTECTED] measureLength
+The length of the measures in the current time signature. For a 4/4
+time this [EMAIL PROTECTED], and for 6/8 it is 3/4.
+
[EMAIL PROTECTED] measurePosition
+The point within the measure where we currently are. This quantity
+is reset [EMAIL PROTECTED] whenever it exceeds @code{measureLength}. When that
+happens, @code{currentBarNumber} is incremented.
+
[EMAIL PROTECTED] timing
+If set to true, the above variables are updated for every time
+step. When set to false, the engraver stays in the current measure
+indefinitely.
[EMAIL PROTECTED] table
+
+Timing can be changed by setting any of these variables explicitly.
+In the next example, the 4/4 time signature is printed, but
[EMAIL PROTECTED] is set to 5/4. After a while, the measure is
+shortened by 1/8, by setting @code{measurePosition} to 7/8 at 2/4
+in the measure, so the next bar line will fall at 2/4 + 3/8. The
+3/8 arises because 5/4 normally has 10/8, but we have manually
+set the measure position to be 7/8 and 10/8 - 7/8 = 3/8.
+
[EMAIL PROTECTED],raggedright,verbatim,relative,fragment]
+\set Score.measureLength = #(ly:make-moment 5 4)
+c1 c4
+c1 c4
+c4 c4
+\set Score.measurePosition = #(ly:make-moment 7 8)
+b8 b b
+c4 c1
[EMAIL PROTECTED] lilypond
+
+
@node Clusters
@subsection Clusters
@@ -2330,60 +2382,3 @@
[EMAIL PROTECTED] Other
[EMAIL PROTECTED] Other
-
-FIXME:
-It's the dreaded ``what on earth should I do with this stuff'' section! Yay!
-
[EMAIL PROTECTED]
-* Time administration::
[EMAIL PROTECTED] menu
-
-
[EMAIL PROTECTED] Time administration
[EMAIL PROTECTED] Time administration
-
-Time is administered by the @internalsref{Time_signature_engraver},
-which usually lives in the @internalsref{Score} context.
-The bookkeeping deals with the following variables
-
[EMAIL PROTECTED] @code
[EMAIL PROTECTED] currentBarNumber
-The measure number.
-
[EMAIL PROTECTED] measureLength
-The length of the measures in the current time signature. For a 4/4
-time this [EMAIL PROTECTED], and for 6/8 it is 3/4.
-
[EMAIL PROTECTED] measurePosition
-The point within the measure where we currently are. This quantity
-is reset [EMAIL PROTECTED] whenever it exceeds @code{measureLength}. When that
-happens, @code{currentBarNumber} is incremented.
-
[EMAIL PROTECTED] timing
-If set to true, the above variables are updated for every time
-step. When set to false, the engraver stays in the current measure
-indefinitely.
[EMAIL PROTECTED] table
-
-Timing can be changed by setting any of these variables explicitly.
-In the next example, the 4/4 time signature is printed, but
[EMAIL PROTECTED] is set to 5/4. After a while, the measure is
-shortened by 1/8, by setting @code{measurePosition} to 7/8 at 2/4
-in the measure, so the next bar line will fall at 2/4 + 3/8. The
-3/8 arises because 5/4 normally has 10/8, but we have manually
-set the measure position to be 7/8 and 10/8 - 7/8 = 3/8.
-
[EMAIL PROTECTED],raggedright,verbatim,relative,fragment]
-\set Score.measureLength = #(ly:make-moment 5 4)
-c1 c4
-c1 c4
-c4 c4
-\set Score.measurePosition = #(ly:make-moment 7 8)
-b8 b b
-c4 c1
[EMAIL PROTECTED] lilypond
-
-
-
Index: lilypond/Documentation/user/basic-notation.itely
diff -u lilypond/Documentation/user/basic-notation.itely:1.22
lilypond/Documentation/user/basic-notation.itely:1.23
--- lilypond/Documentation/user/basic-notation.itely:1.22 Thu May 26
00:09:54 2005
+++ lilypond/Documentation/user/basic-notation.itely Thu May 26 19:15:08 2005
@@ -2716,7 +2716,7 @@
@lilypond[quote,verbatim,fragment,linewidth=8.0\cm]
\unfoldRepeats {
\repeat tremolo 8 {c'32 e' }
- \repeat percent 4 { c''8 d'' }
+ \repeat percent 2 { c''8 d'' }
\repeat volta 2 {c'4 d' e' f'}
\alternative {
{ g' a' a' g' }
Index: lilypond/Documentation/user/global.itely
diff -u lilypond/Documentation/user/global.itely:1.13
lilypond/Documentation/user/global.itely:1.14
--- lilypond/Documentation/user/global.itely:1.13 Tue May 24 19:18:59 2005
+++ lilypond/Documentation/user/global.itely Thu May 26 19:15:08 2005
@@ -13,7 +13,6 @@
@menu
* Paper output::
* Sound output::
-* LilyPond files::
@end menu
@@ -1023,148 +1022,3 @@
the list of MIDI instruments, the Grand Piano (@code{"acoustic grand"})
instrument is used.
-
-
[EMAIL PROTECTED] LilyPond files
[EMAIL PROTECTED] LilyPond files
-
[EMAIL PROTECTED]
-* File structure::
-* Including LilyPond files::
[EMAIL PROTECTED] menu
-
-
[EMAIL PROTECTED] File structure
[EMAIL PROTECTED] File structure
-
-The major part of this manual is concerned with entering various
-forms of music in LilyPond. However, many music expressions are not
-valid input on their own, for example, a @code{.ly} file containing
-only a note
[EMAIL PROTECTED]
-c'4
[EMAIL PROTECTED] example
-
[EMAIL PROTECTED]
-will result in a parsing error. Instead, music should be inside other
-expressions, which may be put in a file by themselves. Such
-expressions are called toplevel expressions. This section enumerates
-them all.
-
-A @code{.ly} file contains any number of toplevel expressions, where a
-toplevel expression is one of the following
-
[EMAIL PROTECTED] @bullet
[EMAIL PROTECTED]
-An output definition, such as @code{\paper}, @code{\midi}, and
[EMAIL PROTECTED] Such a definition at the toplevel changes the default
-settings for the block entered.
-
[EMAIL PROTECTED]
-A @code{\header} block. This sets the global header block. This
-is the block containing the definitions for book-wide settings, like
-composer, title, etc.
-
[EMAIL PROTECTED]
-An @code{\addquote} statement. See @ref{Quoting other voices}
-for more information.
-
[EMAIL PROTECTED]
-A @code{\score} block. This score will be collected with other
-toplevel scores, and combined as a single @code{\book}.
-
-This behavior can be changed by setting the variable
[EMAIL PROTECTED] at toplevel. The default handler is
-defined in the init file @file{scm/@/lily@/.scm}.
-
[EMAIL PROTECTED]
-A @code{\book} block logically combines multiple movements
-(i.e., multiple @code{\score} blocks) in one document. A number of
[EMAIL PROTECTED] creates a single output file, where all movement are
-concatenated.
-
-This behavior can be changed by setting the variable
[EMAIL PROTECTED] at toplevel. The default handler is
-defined in the init file @file{scm/@/lily@/.scm}.
-
[EMAIL PROTECTED]
-A compound music expression, such as
[EMAIL PROTECTED]
[EMAIL PROTECTED] c'4 d' e'2 @}
[EMAIL PROTECTED] example
-
-This will add the piece in a @code{\score} and format it in a
-single book together with all other toplevel @code{\score}s and music
-expressions.
-
-This behavior can be changed by setting the variable
[EMAIL PROTECTED] at toplevel. The default handler is
-defined in the init file @file{scm/@/lily@/.scm}.
-
[EMAIL PROTECTED]
-A markup text, a verse for example
[EMAIL PROTECTED]
-\markup @{
- 2. The first line verse two.
[EMAIL PROTECTED]
[EMAIL PROTECTED] example
-
-Markup texts are rendered above, between or below the scores or music
-expressions, wherever they appear.
-
[EMAIL PROTECTED]
-An indentifier, such as
[EMAIL PROTECTED]
-foo = @{ c4 d e d @}
[EMAIL PROTECTED] example
-
-This can be used later on in the file by entering @code{\foo}. The
-name of an identifier should have alphabetic characters only; no
-numbers, underscores or dashes.
-
[EMAIL PROTECTED] itemize
-
-The following example shows three things that may be entered at
-toplevel
-
[EMAIL PROTECTED]
-\layout @{
- % movements are non-justified by default
- raggedright = ##t
[EMAIL PROTECTED]
-
-\header @{
- title = "Do-re-mi"
[EMAIL PROTECTED]
-
[EMAIL PROTECTED] c'4 d' e2 @}
[EMAIL PROTECTED] example
-
-
-At any point in a file, any of the following lexical instructions can
-be entered:
-
[EMAIL PROTECTED] @bullet
[EMAIL PROTECTED] @code{\version}
[EMAIL PROTECTED] @code{\include}
[EMAIL PROTECTED] @code{\renameinput}
[EMAIL PROTECTED] itemize
-
-
[EMAIL PROTECTED] Including LilyPond files
[EMAIL PROTECTED] Including LilyPond files
-
[EMAIL PROTECTED] @code{\include}
[EMAIL PROTECTED] including files
-
-A large project may be split up into separate files. To refer to another
-file, use
-
[EMAIL PROTECTED]
-\include "otherfile.ly"
[EMAIL PROTECTED] example
-
-For example, you may write separate files for each instrument part and
-create a ``full score'' file which brings together the individual
-instrument files.
-
Index: lilypond/Documentation/user/instrument-notation.itely
diff -u lilypond/Documentation/user/instrument-notation.itely:1.32
lilypond/Documentation/user/instrument-notation.itely:1.33
--- lilypond/Documentation/user/instrument-notation.itely:1.32 Mon May 23
19:29:14 2005
+++ lilypond/Documentation/user/instrument-notation.itely Thu May 26
19:15:08 2005
@@ -830,50 +830,42 @@
next one. Such a line is called an extender line, and it is entered as
[EMAIL PROTECTED]'.
[EMAIL PROTECTED]
-FIXME: check that this compiles and displays correctly. I don't want
-to commit this part blindly.
-
In tighly engraved music, hyphens can be removed. In some languages
(e.g. German and Hungarian), hyphens should not disappear, since
spelling depends on hyphenation. For that purpose, hyphens can be
forced to remain by overriding @code{minimum-length} of
the @code{LyricHyphen} grob.
-(code from 2.2)
[EMAIL PROTECTED],verbatim,raggedright]
\score {
-<< \notes \new Staff \relative c'' { \time 1/4 c16[ c c c]
-\time 1/4
-c16[ c c c]
-\time 1/4
-c16[ c c c]
-
-}
- \lyrics \new Lyrics \with {
- % Otherwise lyrics are so far apart that hyphens don't disappear
- \override SeparationItem #'padding = #0.0
- }{ bla -- bla -- bla -- bla --
- bla -- bla -- bla -- bla --
-
- \override LyricHyphen #'minimum-length = #0.7
- \override LyricHyphen #'spacing-procedure =
- #Hyphen_spanner::set_spacing_rods
-
- bla -- bla -- bla -- bla
- }>>
- \paper {
- indent = 0.0 \cm
- linewidth = 3.4 \cm
-
- \context {
- \StaffContext \remove "Time_signature_engraver"
- }
-
- }
-
-}
[EMAIL PROTECTED] ignore
-
+<<
+ \new Staff \relative c'' {
+ \time 1/4 c16 c c c c16 c c c c16 c c c
+ } % closes notes
+ \lyricmode { \new Lyrics
+ \with {
+ \override SeparationItem #'padding = #0.0
+ % Otherwise lyrics are so far apart that hyphens don't disappear
+ } % closes with
+ {
+ An -- ti -- cons -- ti --
+ tu -- tion -- nel -- le --
+ \override LyricHyphen #'minimum-length = #0.7
+ \override LyricHyphen #'spacing-procedure =
+ #Hyphen_spanner::set_spacing_rods
+ men -- taire -- ment. ouf~!
+ } % closes lyrics
+ } %closes lyricmode
+>>
+\layout {
+ indent = 0.0 \cm
+ linewidth = 3.4 \cm
+ \context {
+ \Staff \remove "Time_signature_engraver"
+ } % closes context
+} % closes layout
+} % closes score
[EMAIL PROTECTED] lilypond
@seealso
Index: lilypond/Documentation/user/introduction.itely
diff -u lilypond/Documentation/user/introduction.itely:1.139
lilypond/Documentation/user/introduction.itely:1.140
--- lilypond/Documentation/user/introduction.itely:1.139 Tue May 24
19:18:59 2005
+++ lilypond/Documentation/user/introduction.itely Thu May 26 19:15:08 2005
@@ -259,9 +259,6 @@
head objects are used to produce their symbol is changed during the music
fragment.
[EMAIL PROTECTED] FIXME: this example has errors:
[EMAIL PROTECTED] programming error: Grob `NoteHead' has no interface for
property `text'
[EMAIL PROTECTED] Continuing; crossing fingers
@lilypond[quote,raggedright]
#(define (mc-squared grob orig current)
(let ((interfaces (ly:grob-property grob 'interfaces))
Index: lilypond/Documentation/user/invoking.itely
diff -u lilypond/Documentation/user/invoking.itely:1.32
lilypond/Documentation/user/invoking.itely:1.33
--- lilypond/Documentation/user/invoking.itely:1.32 Mon May 9 05:29:48 2005
+++ lilypond/Documentation/user/invoking.itely Thu May 26 19:15:08 2005
@@ -6,11 +6,13 @@
@menu
-* Invoking lilypond::
-* Error messages::
-* Updating files with convert-ly::
-* Reporting bugs::
-* Editor support::
+* Invoking lilypond::
+* Error messages::
+* Updating files with convert-ly::
+* Reporting bugs::
+* Editor support::
+* File structure::
+* Including LilyPond files::
@end menu
@node Invoking lilypond
@@ -489,18 +491,18 @@
@ignore
Copy and paste from CVS, last updated
-Feb 14, 2005
+May 26, 2005
http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lily-bugs/bugs/convert-ly.txt?rev=HEAD&content-type=text/plain
@end ignore
@verbatim
-There are a few things that the convert-ly cannot handle. Here's a
-list of limitations that the community has complained about.
+There are a few things that the convert-ly cannot handle. Here's a list of
limitations
+that the community has complained about.
-This bug report structure has been chosen because convert-ly has a
-structure that doesn't allow to smoothly implement all needed changes.
-Thus this is just a wishlist, placed here for reference.
+This bug report structure has been chosen because convert-ly has a structure
that doesn't
+allow to smoothly implement all needed changes. Thus this is just a wishlist,
placed
+here for reference.
1.6->2.0:
Doesn't always convert figured bass correctly, specifically things like {<
>}. Mats' comment on working around this:
@@ -508,16 +510,36 @@
on it, I first replaced all occurencies of '{<' to some dummy like '{#'
and similarly I replaced '>}' with '&}'. After the conversion, I could
then change back from '{ #' to '{ <' and from '& }' to '> }'.
- Doesn't convert all text markup correctly. Only very simple cases are fixed.
+ Doesn't convert all text markup correctly. In the old markup syntax,
+ it was possible to group a number of markup commands together within
parentheses, e.g.
+ -#'((bold italic) "string")
+ This will incorrectly be converted into
+ -\markup{{\bold italic} "string"}
+ instead of the correct
+ -\markup{\bold \italic "string"}
2.0->2.2:
Doesn't handle \partcombine
Doesn't do \addlyrics => \lyricsto, this breaks some scores with multiple
stanzas.
+2.0->2.4:
+ \magnify isn't changed to \fontsize.
+ - \magnify #m => \fontsize #f, where f = 6ln(m)/ln(2)
+ remove-tag isn't changed.
+ - \applymusic #(remove-tag '. . .) => \keepWithTag #'. . .
+ firstpagenumber isn't changed.
+ - firstpagenumber no => printfirstpagenumber = ##f
+ Line breaks in header strings aren't converted.
+ - \\\\ as line break in \header strings => \markup \center-align <
+ "First Line" "Second Line" >
+ Crescendo and decrescendo terminators aren't converted.
+ - \rced => \!
+ - \rc => \!
2.2->2.4:
\turnOff (used in \set Staff.VoltaBracket = \turnOff) is not properly
converted.
2.4.2->2.5.9
\markup{ \center-align <{ ... }> } should be converted to:
\markup{ \center-align {\line { ... }} }
but now, \line is missing.
+
@end verbatim
@@ -550,7 +572,7 @@
It seems that placement of accidentals is broken. In the
following example, the accidental touches the note head.
-Using Mac OSX 10.3.5, fink package lilypond-unstable
+Using Mac OSX 10.3.7, fink package lilypond-devel
\version "2.5.18"
\relative c''@{
@@ -617,3 +639,137 @@
of a symbol in the graphical output. See @ref{Point and click}.
[EMAIL PROTECTED] File structure
[EMAIL PROTECTED] File structure
+
+The major part of this manual is concerned with entering various
+forms of music in LilyPond. However, many music expressions are not
+valid input on their own, for example, a @code{.ly} file containing
+only a note
[EMAIL PROTECTED]
+c'4
[EMAIL PROTECTED] example
+
[EMAIL PROTECTED]
+will result in a parsing error. Instead, music should be inside other
+expressions, which may be put in a file by themselves. Such
+expressions are called toplevel expressions. This section enumerates
+them all.
+
+A @code{.ly} file contains any number of toplevel expressions, where a
+toplevel expression is one of the following
+
[EMAIL PROTECTED] @bullet
[EMAIL PROTECTED]
+An output definition, such as @code{\paper}, @code{\midi}, and
[EMAIL PROTECTED] Such a definition at the toplevel changes the default
+settings for the block entered.
+
[EMAIL PROTECTED]
+A @code{\header} block. This sets the global header block. This
+is the block containing the definitions for book-wide settings, like
+composer, title, etc.
+
[EMAIL PROTECTED]
+An @code{\addquote} statement. See @ref{Quoting other voices}
+for more information.
+
[EMAIL PROTECTED]
+A @code{\score} block. This score will be collected with other
+toplevel scores, and combined as a single @code{\book}.
+
+This behavior can be changed by setting the variable
[EMAIL PROTECTED] at toplevel. The default handler is
+defined in the init file @file{scm/@/lily@/.scm}.
+
[EMAIL PROTECTED]
+A @code{\book} block logically combines multiple movements
+(i.e., multiple @code{\score} blocks) in one document. A number of
[EMAIL PROTECTED] creates a single output file, where all movement are
+concatenated.
+
+This behavior can be changed by setting the variable
[EMAIL PROTECTED] at toplevel. The default handler is
+defined in the init file @file{scm/@/lily@/.scm}.
+
[EMAIL PROTECTED]
+A compound music expression, such as
[EMAIL PROTECTED]
[EMAIL PROTECTED] c'4 d' e'2 @}
[EMAIL PROTECTED] example
+
+This will add the piece in a @code{\score} and format it in a
+single book together with all other toplevel @code{\score}s and music
+expressions.
+
+This behavior can be changed by setting the variable
[EMAIL PROTECTED] at toplevel. The default handler is
+defined in the init file @file{scm/@/lily@/.scm}.
+
[EMAIL PROTECTED]
+A markup text, a verse for example
[EMAIL PROTECTED]
+\markup @{
+ 2. The first line verse two.
[EMAIL PROTECTED]
[EMAIL PROTECTED] example
+
+Markup texts are rendered above, between or below the scores or music
+expressions, wherever they appear.
+
[EMAIL PROTECTED]
+An indentifier, such as
[EMAIL PROTECTED]
+foo = @{ c4 d e d @}
[EMAIL PROTECTED] example
+
+This can be used later on in the file by entering @code{\foo}. The
+name of an identifier should have alphabetic characters only; no
+numbers, underscores or dashes.
+
[EMAIL PROTECTED] itemize
+
+The following example shows three things that may be entered at
+toplevel
+
[EMAIL PROTECTED]
+\layout @{
+ % movements are non-justified by default
+ raggedright = ##t
[EMAIL PROTECTED]
+
+\header @{
+ title = "Do-re-mi"
[EMAIL PROTECTED]
+
[EMAIL PROTECTED] c'4 d' e2 @}
[EMAIL PROTECTED] example
+
+
+At any point in a file, any of the following lexical instructions can
+be entered:
+
[EMAIL PROTECTED] @bullet
[EMAIL PROTECTED] @code{\version}
[EMAIL PROTECTED] @code{\include}
[EMAIL PROTECTED] @code{\renameinput}
[EMAIL PROTECTED] itemize
+
+
[EMAIL PROTECTED] Including LilyPond files
[EMAIL PROTECTED] Including LilyPond files
+
[EMAIL PROTECTED] @code{\include}
[EMAIL PROTECTED] including files
+
+A large project may be split up into separate files. To refer to another
+file, use
+
[EMAIL PROTECTED]
+\include "otherfile.ly"
[EMAIL PROTECTED] example
+
+For example, you may write separate files for each instrument part and
+create a ``full score'' file which brings together the individual
+instrument files.
+
Index: lilypond/Documentation/user/lilypond.tely
diff -u lilypond/Documentation/user/lilypond.tely:1.130
lilypond/Documentation/user/lilypond.tely:1.131
--- lilypond/Documentation/user/lilypond.tely:1.130 Tue May 24 19:18:59 2005
+++ lilypond/Documentation/user/lilypond.tely Thu May 26 19:15:08 2005
@@ -5,16 +5,21 @@
@afourpaper
@end iftex
[EMAIL PROTECTED] GNU music project
[EMAIL PROTECTED]
+
@ignore
+(I think)
+Current version of the manual: 2.5.18
+Please update this whenever you run convert-ly on the docs.
+
+%%%%%
+
Distributions will want to install lilypond.info in postinstall, doing:
install-info --info-dir=/usr/share/info out/lilypond.info
[EMAIL PROTECTED] ignore
-
[EMAIL PROTECTED] GNU music project
[EMAIL PROTECTED]
[EMAIL PROTECTED]
+%%%%%
* Prepend GNU for dir, must be unique.
Index: lilypond/Documentation/user/tutorial.itely
diff -u lilypond/Documentation/user/tutorial.itely:1.257
lilypond/Documentation/user/tutorial.itely:1.258
--- lilypond/Documentation/user/tutorial.itely:1.257 Wed May 18 04:36:41 2005
+++ lilypond/Documentation/user/tutorial.itely Thu May 26 19:15:08 2005
@@ -213,7 +213,6 @@
@[EMAIL PROTECTED] are macro files for VIM addicts, and there
is a @code{LilyPond-mode} for Emacs addicts. If they have not been
installed already, refer to
[EMAIL PROTECTED] FIXME lousy reference.
the file @file{INSTALL.txt}.} In your text editor, enter the following
input and save the file as @file{test.ly}
_______________________________________________
Lilypond-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-cvs
