-\input texinfo @c -*-texinfo-*-
+\input texinfo @c -*- coding: latin-1; mode: texinfo; -*-
@setfilename lilypond.info
@settitle GNU LilyPond
@iftex
@c prepend GNU for dir, must be unique
@c do not list the `lilypond' node at toplevel, so that `info lilypond'
@c goes to Top.
-@c * lilypond: (lilypond/lilypond)Invoking LilyPond. Titling LilyPond scores.
+@c * lilypond: (lilypond/lilypond)Running LilyPond. Invoking the
+@c LilyPond program.
* GNU LilyPond: (lilypond/lilypond). The GNU music typesetter.
* convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions.
* midi2ly: (lilypond/lilypond)Invoking midi2ly. Importing MIDI.
HINTS FOR STYLE
+* Do not forget to create @cindex entries for new sections of text.
+
* Try not to use punctuation between introductocing sentence and
display material (verbatim, music, example code).
* Abbrevs in caps, e.g. HTML, DVI, MIDI, etc.
+* Colon usage
+ 0. Do not use a colon to introduce examples, sentences just continue
+
+ in the display material.
+
+ 1. To introduce lists
+ 2. When beginning a quote: "So, he said,..."
+ This usage is rarer. Americans often just use a comma.
+ 3. When adding a defining example at the end of a sentence.
+
@end ignore
@ifhtml
@end ifhtml
+@documentlanguage en
+@documentencoding ISO-8859-1
+
+@syncodeindex fn cp
+@syncodeindex ky cp
+@syncodeindex pg cp
+@syncodeindex tp cp
+@syncodeindex vr cp
+
+
@titlepage
@title GNU LilyPond
@subtitle The music typesetter
-@author Han-Wen Nienhuys
-@author Jan Nieuwenhuizen
-@author J@"{u}rgen Reuter
-@author Rune Zedeler
+@author The LilyPond development team
@vskip 20pt
-
+@c Not yet debugged or reported. This crashes gs-8.01:
+@c compiling gs-8.01 right now... -- jcn
@lilypond[raggedright]
\score {
- \context Lyrics \notes {
+ \context Lyrics {
\override Score.RehearsalMark #'self-alignment-X = #LEFT
+ \override Score.RehearsalMark #'font-size = #-2
\mark #(ly:export (string-append
"(For LilyPond version " (lilypond-version) ")"))
s2
}
- \paper {
+ \layout {
indent = 0.0\pt
raggedright = ##t
}
}
@end lilypond
-
@end titlepage
@top GNU LilyPond --- The music typesetter
@c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
-This is the user manual for GNU LilyPond 2.1.x series.
+This is the user manual for GNU LilyPond 2.3.x series.
@ifhtml
(See the bottom of this page for the exact version number).
@end ifhtml
* Preface:: Preface.
* Introduction:: What, Why, How.
* Tutorial:: A tutorial introduction.
+* Example templates:: Larger examples
* Notation manual:: All notation supported, and how to
produce it.
+* Sound:: Producing MIDI output
* Changing defaults:: Tuning output.
-* Invoking LilyPond:: Operation.
+* Interfaces for programmers::
+* Running LilyPond:: Operation.
* Converting from other formats:: Converting to lilypond source format.
-* lilypond-book manual:: Integrating text and music with lilypond-book.
-* Unified index::
-* Notation manual details::
+* Integrating text and music:: Integrating text and music with lilypond-book.
* Literature list::
-* Interfaces for programmers::
-* Cheat sheet::
+* Scheme tutorial::
+* Notation manual details::
+* Point and click::
+* Unified index::
* GNU Free Documentation License:: FDL.
+* Cheat sheet::
@end menu
@end ifnottex
@include preface.itely
@include introduction.itely
@include tutorial.itely
+@include examples.itely
+@include invoking.itely
@include notation.itely
+@include sound-output.itexi
@include changing-defaults.itely
-@include invoking.itexi
+@include programming-interface.itely
@include lilypond-book.itely
@include converters.itely
@c FIXME: Index has two alphabetically sorted lists @code vs plain?
-@node Unified index
-@unnumbered Unified index
-
-@printindex cp
-@include notation-appendices.itely
@include literature.itely
+@include scheme-tutorial.itely
+@include notation-appendices.itely
+@include point-and-click.itely
-@include programming-interface.itely
+@node Unified index
+@appendix Unified index
-@include cheatsheet.itely
+@printindex cp
@include fdl.itexi
+@include cheatsheet.itely
+
@bye