* Documentation/user/tutorial.itely: minor editing.
+ * Documentation/user/examples.itely: tiny editing.
+
2004-08-28 Han-Wen Nienhuys <hanwen@xs4all.nl>
* Documentation/user/advanced.itely: removed.
bassWords = \lyrics { ho4 ho ho ho }
\score {
- \context StaffGroup <<
+ \context ChoirStaff <<
\context Lyrics = sopranos { s1 }
\context Staff = women <<
\context Voice = sopranos { \voiceOne << \global \sopMusic >> }
}
\score {
- {
- c'4
- }
-}
+ \header {
+ piece = "piece1"
+ opus = "opus1"
+ }
+ { c'4 }
+}
+
+\score {
+ \header {
+ piece = "piece2"
+ opus = "opus2"
+ }
+ { c'4 }
+}
@end lilypond
* More staves::
* Adding articulation marks to notes::
* Combining notes into chords::
-* Basic rhythmical commands::
+* Advanced rhythmic commands::
* Commenting input files::
* Printing lyrics::
* A lead sheet::
-@node Basic rhythmical commands
-@section Basic rhythmical commands
+@node Advanced rhythmic commands
+@section Advanced rhythmic commands
@cindex pickup
@cindex anacruse
@example
% notes for twinkle twinkle follow
-c4 c g' g a a
+c4 c g' g a a g2
%@{
This line, and the notes below
%@}
@end example
+@c FIXME
+@c This is good info, but I wouldn't call it a comment. IMO it should
+@c be moved somewhere else. I don't know exactly where yet, but I'll
+@c resolve it soon. -GP
+
@cindex versioning
There is a special statement that is a kind of comment. The @code{\version}
@noindent
These annotations make future upgrades of LilyPond go more
-smoothly. Changes in the syntax are handled with a special program,
+smoothly. Changes in the syntax are handled with a special program,
@file{convert-ly} (see @ref{Invoking convert-ly}), and it uses
@code{\version} to determine what rules to apply.