+2003-08-08 Han-Wen Nienhuys <hanwen@cs.uu.nl>
+
+ * Documentation/topdocs/INSTALL.texi (Top): change GUILE
+ requirements.
+
+ * buildscripts/mutopia-index.py (read_lilypond_header): update
+ mutopia-index.py to 1.4 syntax [sic]
+
2003-08-07 Heikki Junes <hjunes@cc.hut.fi>
* make/lilypond.mandrake.spec.in: remove menu, sync with redhat-spec.
2003-08-07 Han-Wen Nienhuys <hanwen@cs.uu.nl>
+ * Documentation/index.html.in: url for regression pdf
+
+ * Documentation/user/cheatsheet.itely (Cheat sheet): single staff.
+
+ * Documentation/user/tutorial.itely (Piano staves): s/staffs/staves/g
+
+ * make/lilypond.redhat.spec.in (Buildrequires): texinfo >= 4.6 reqd.
+
+ * VERSION: 1.8.0 released
+
* GNUmakefile.in (local-WWW-post): footify build fix.
* configure.in: require GUILE 1.6.4
@item @uref{http://www.python.org,Python} (version 2.1 or newer).
-@item @uref{http://www.gnu.org/software/guile/guile.html,GUILE} (version 1.6.4 or newer).
+@item @uref{http://www.gnu.org/software/guile/guile.html,GUILE} (version 1.6.0 or newer).
@item @uref{ftp://ftp.gnu.org/gnu/make/,GNU Make} (version 3.78 or newer),
@itemize @bullet
@item @TeX{}.
@item Xdvi and Ghostscript.
-@item @uref{http://www.gnu.org/software/guile/guile.html,GUILE} 1.6.4, or newer.
+@item @uref{http://www.gnu.org/software/guile/guile.html,GUILE} 1.6.0, or newer.
@end itemize
For running LilyPond successfully
@end lilypond
In scores with many staves, a @code{\bar} command in one staff is
-automatically applied to all staffs. The resulting bar lines are
+automatically applied to all staves. The resulting bar lines are
connected between different staves of a @internalsref{StaffGroup}:
@c
@lilypond[fragment, verbatim]
The bar line objects that are created at @internalsref{Staff} level
-are called @internalsref{BarLine}, the bar lines that span staffs are
+are called @internalsref{BarLine}, the bar lines that span staves are
@internalsref{SpanBar}s.
@cindex bar lines at start of system
A score that starts with an @code{\grace} section needs an explicit
@code{\context Voice} declaration, otherwise the main note and grace
-note end up on different staffs.
+note end up on different staves.
Grace note synchronization can also lead to surprises. Staff notation,
such as key signatures, barlines, etc. are also synchronized. Take
Normally, this will put the lyrics below the staff. For different or
more complex orderings, the best way is to setup the hierarchy of
-staffs and lyrics first, e.g.
+staves and lyrics first, e.g.
@example
\context ChoirStaff \notes <
\context Lyrics = LA @{ s1 @}
* Transpose::
* Multi measure rests::
* Automatic part combining::
-* Hiding staffs::
+* Hiding staves::
* Sound output for transposing instruments::
@end menu
@node Multiple staff contexts
@subsection Multiple staff contexts
-Polyphonic scores consist of many staffs. These staffs can be
+Polyphonic scores consist of many staves. These staves can be
constructed in three different ways:
@itemize @bullet
@item The group is started with a brace at the left. This is done with the
@subsection Instrument names
In an orchestral score, instrument names are printed left side of the
-staffs.
+staves.
This can be achieved by setting @internalsref{Staff}.@code{instrument}
and @internalsref{Staff}.@code{instr}. This will print a string before
@cindex @code{Voice_engraver}
@cindex @code{A2_engraver}
-@node Hiding staffs
-@subsection Hiding staffs
+@node Hiding staves
+@subsection Hiding staves
@cindex Frenched scores
-@cindex Hiding staffs
+@cindex Hiding staves
In orchestral scores, staff lines that only have rests are usually
removed. This saves some space. This style is called `French Score'.
switched on by default. When these line of these contexts turn out
empty after the line-breaking process, they are removed.
-For normal staffs, a specialized @internalsref{Staff} context is
-available, which does the same: staffs containing nothing (or only
+For normal staves, a specialized @internalsref{Staff} context is
+available, which does the same: staves containing nothing (or only
multi measure rests) are removed. The context definition is stored in
@code{\RemoveEmptyStaffContext} variable. Observe how the second staff
in this example disappears in the second line:
* Listening to output::
* Titling::
* Single staff polyphony::
-* Piano staffs::
+* Piano staves::
* Setting variables::
* Fine tuning layout::
* Organizing larger pieces::
More features of polyphonic typesetting are in the notation manual
in @ref{Polyphony}.
-@node Piano staffs
-@section Piano staffs
+@node Piano staves
+@section Piano staves
@cindex staff switch, manual
@cindex cross staff voice, manual
@cindex @code{\translator}
-Piano music is always typeset in two staffs connected by a brace.
+Piano music is always typeset in two staves connected by a brace.
Printing such a staff is done similar to the polyphonic example in
@ref{Combining music into compound expressions}:
@example