objects.
* scm/documentation-generate.scm (string-append): add syncodeindex
* Documentation/user/tutorial.itely (A lead sheet): use \chords
for tutoring chord names.
* Documentation/user/lilypond.tely: remove @authors.
+2004-10-24 Han-Wen Nienhuys <hanwen@xs4all.nl>
+
+ * Documentation/user/macros.itexi: use findex functions/internals
+ objects.
+
+ * scm/documentation-generate.scm (string-append): add syncodeindex
+
+ * Documentation/user/tutorial.itely (A lead sheet): use \chords
+ for tutoring chord names.
+
+ * Documentation/user/lilypond.tely: remove @authors.
+
2004-10-23 Werner Lemberg <wl@gnu.org>
* scm/framework-tex.scm (dump-page): Add width to \lybox call.
2004-10-23 Han-Wen Nienhuys <hanwen@xs4all.nl>
+ * VERSION (PACKAGE_NAME): release 2.3.23
+
* scm/framework-tex.scm (convert-to-ps): add -E if filename
contains .preview.
* Documentation/user/macros.itexi: add \global to definitions for
feta macros.
- * po/fr.po (Module): updated po file.
+ * po/fr.po: updated po file.
* po/de.po: updated po file.
* Documentation/user/notation.itely: Minor corrections.
* Documentation/user/tutorial.itely: Minor corrections.
-
+
2004-10-11 Jan Nieuwenhuizen <janneke@gnu.org>
* scm/framework-ps.scm (page-header): Fix Layout renaming bug.
@node Top, , ,
@top
-@unnumbered New features in 2.3 since 2.2
+@unnumbered New features in 2.4 since 2.2
@itemize @bullet
@item @code{\bookpaper} and @code{\paper} have been renamed to
@item JEdit
-There exists a plugin for @uref{http://www.jedit.org/,jEdit}. Refer to
-the @uref{http://lily4jedit.sourceforge.net,plugin website} for more
-information.
+The @uref{http://www.jedit.org/,jEdit} editor has a LilyPond plugin.
+This plugin includes a DVI viewer, integrated help and viewing via
+GhostScript. It can be installed by doing @key{Plugins > Plugin
+Manager}, and selecting @code{LilyTool} from the @key{Install} tab.
@end table
-For both VIM and Emacs editors, there is also a facility to jump in
-the input file to the source of errors in the graphical output. See
-@ref{Point and click}.
+All these editors can be made to jump in the input file to the source
+of a symbol in the graphical output. See @ref{Point and click}.
@end ifhtml
+@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
\score {
\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
@c using @ref without punctuation is OK without for formats other than info
@ref{\NAME\,,,lilypond-internals}@c
@c should we do this?
-@cindex @code{\NAME\}
+@findex \NAME\
@end macro
@c what is this? -- jcn
@c should we do this?
@c using @ref without punctuation is OK without for formats other than info
@ref{\NODENAME\,,\NAME\,lilypond-internals}@c
- @cindex @code{\NAME\}
+ @findex \NAME\
@end macro
@macro inputfileref{DIR,NAME}
@c @uref{../lilypond-internals/\NAME\.html,\NAME\}@c
@inforef{\NAME\,,lilypond-internals}@c
@c should we do this?
- @cindex @code{\NAME\}
+ @findex @code{\NAME\}
@end macro
@macro hyphenatedinternalsref{NAME,NODENAME}
@c @uref{../lilypond-internals/\NODENAME\.html,\NAME\}@c
@inforef{\NODENAME\,,lilypond-internals}@c
@c should we do this?
- @cindex @code{\NAME\}
+ @findex @code{\NAME\}
@end macro
@macro inputfileref{DIR,NAME}
@c **** INFO ****
@macro internalsref{NAME}
@inforef{\NAME\,,lilypond/lilypond-internals}@c
-@cindex \NAME\@c
+@findex \NAME\@c
@end macro
@macro hyphenatedinternalsref{NAME,NODENAME}
@c FIXME: suspicious info file name?
@inforef{\NODENAME\,,lilypond-internals}@c
@c should we do this?
-@cindex @code{\NAME\}
+@findex @code{\NAME\}
@end macro
@macro inputfileref{DIR,NAME}
@c **** TEX ****
@macro internalsref{NAME}@c
-@cindex @code{\NAME\} @c
+@findex \NAME\ @c
@code{\NAME\}@c
@end macro
@macro context{NAME}@c
@code{\NAME\}@c should use internalsref
-@cindex \NAME\@c
+@findex \NAME\@c
@end macro
@c --hwn
@macro refcommand{WHAT}
-@cindex @code{\WHAT\}
-@code{\WHAT\},
+@findex \WHAT\
+@code{\WHAT\}
@end macro
* Chord name chart::
* MIDI instruments::
* The Feta font::
-* All context properties::
-* Layout properties::
@end menu
@lilypondfile[noindent]{parmesan16list.ly}
-
+@ignore
@node All context properties
-@appendixsec All context properties
+@a ppendixsec All context properties
-@include context-properties.tely
+@i nclude context-properties.tely
@node Layout properties
-@appendixsec Layout properties
+@ap pendixsec Layout properties
-@include layout-properties.tely
+@in clude layout-properties.tely
+@end ignore
@item an editor with a client/server interface (or a lightweight GUI
editor):
+
@cindex editor
@itemize @bullet
@cindex GVim
@cindex Vim
+
+@item jEdit. jEdit is an editor written in Java with extensive plug-in
+support. The LilyPond plugin for jEdit comes with an DVI
+viewer, which is preconfigured for point-and-click.
+
+@cindex jEdit
+
@end itemize
@end itemize
Utrecht/Eindhoven, The Netherlands, July 2002.
@menu
-* Notes for version 3.0::
+* Notes for version 2.4::
@end menu
-@node Notes for version 3.0
-@unnumberedsec Notes for version 3.0
+@node Notes for version 2.4
+@unnumberedsec Notes for version 2.4
-The most important developments in 3.0 are related. In LilyPond 3.0,
+The most important developments in 2.4 are related. In LilyPond 2.4
@TeX{} is no longer strictly necessary to engrave music. This is
because LilyPond can now also layout pages and determine page breaks.
Another notable feature is the syntax, which has been simplified even
is best to mark contexts explicitly. This ensures that each fragment
gets its own stave.
-There are several types of contexts: @code{Staff}, @code{Voice} and
-@code{Score} handle melodic notation. Other contexts are also
-@code{Lyrics} (for setting lyric texts) and @code{ChordNames} (for
-printing chord names).
-
+There are several types of contexts. @code{Staff}, @code{Voice} and
+@code{Score} handle melodic notation, while @code{Lyrics} sets lyric
+texts and @code{ChordNames} prints chord names.
In terms of syntax, prepending @code{\new} to a music expression
creates a bigger music expression. In this way it resembles the minus
@cindex chords
@cindex chord names
+@c TODO: revise this, \chords { } is shorter and more intuitive.
+
In popular music, it is common to denote accompaniment with chord names.
Such chords can be entered like notes,
Now each pitch is read as the root of a chord instead of a note.
This mode is switched on with @code{\chordmode}
-
Other chords can be created by adding modifiers after a colon. The
following example shows a few common modifiers
-@lilypond[quote,verbatim]
+@lilypond[quote,verbatim,raggedright]
\chordmode { c2 f4:m g4:maj7 gis1:dim7 }
@end lilypond
For lead sheets, chords are not printed on staves, but as names on a
-line of themselves. Hence, we have to override the context with
-@code{\new}, rendering the music expression in a @code{ChordNames}
-context
-
-@lilypond[quote,verbatim]
- \chordmode { c2 f4.:m g4.:maj7 gis8:dim7 }
+line of themselves. This is achieved by using @code{\chords} instead
+of @code{\chordmode}. This uses the same syntax as @code{\chordmode},
+but renders the notes in a @code{ChordNames} context, with the
+following result.
+
+@lilypond[quote,verbatim,raggedright]
+ \chords { c2 f4.:m g4.:maj7 gis8:dim7 }
@end lilypond
@cindex lead sheet
@example
<<
- \chordmode @{ @emph{chords} @}
+ \chords @{ @emph{chords} @}
@emph{the melody}
\addlyrics @{ @emph{the text} @}
>>
@lilypond[quote,raggedright]
<<
- \chordmode { r2 c:sus4 f }
+ \chords { r2 c:sus4 f }
\relative {
r4 c' \times 2/3 { f g g }
\times 2/3 { g4( a2) }
projects / lilypond.git / commitdiff