This makes it easier to avoid forgetting the `@noindent'.
-* in @itemize, use @item on a separate line like this:
+* in @itemize use @item on a separate line like this:
@itemize
@item
Foo
@item
Bar
+ Do not use @itemize @bullet.
+
* Use @q instead of `...' and @qq instead of ``...''. The latter macro
should be used with care since we use `...' as the default quoting
throughout the manual, except for things related to direct speech.
figured bass notation.
Many graphical objects provide a @code{style} property, see
-@itemize @bullet
+@itemize
@item
@ref{Ancient note heads},
@item
@ref{Articulations}, specific articulation signs for ancient notation
are provided.
-@itemize @bullet
+@itemize
@item
@ref{Ancient articulations}
@end itemize
adding articulation signs. Some notational concepts are introduced
specifically for ancient notation,
-@itemize @bullet
+@itemize
@item
@ref{Custodes},
@item
contexts. Use them to set up predefined style-specific voice and
staff contexts, and directly go ahead with the note entry,
-@itemize @bullet
+@itemize
@item
@ref{Gregorian Chant contexts},
@item
There is limited support for figured bass notation which came
up during the baroque period.
-@itemize @bullet
+@itemize
@item
@ref{Figured bass}
@end itemize
There are four areas where the default settings may be changed:
-@itemize @bullet
+@itemize
@item
Automatic notation: changing the automatic creation of notation
elements. For example, changing the beaming rules.
#(override-auto-beam-setting '(be p q n m) a b [context])
@end example
-@itemize @bullet
+@itemize
@item @code{be} is either "begin" or "end".
created automatically. For more complex scores, it is necessary to
create them by hand. There are three commands that do this.
-@itemize @bullet
+@itemize
@item
The easiest command is @code{\new}, and it also the quickest to type.
By following related links inside the program reference, we can follow the
flow of information within the program:
-@itemize @bullet
+@itemize
@item @internalsref{Fingering}:
@internalsref{Fingering} objects are created by:
typographical element. For example, the Fingering object
has the following aspects
-@itemize @bullet
+@itemize
@item
Its size is independent of the horizontal spacing, unlike slurs or beams.
This technique only works for objects that are directly connected to
an @internalsref{Event} from the input, for example
-@itemize @bullet
+@itemize
@item note heads, caused by chord-pitch (i.e., notes inside a chord)
@item articulation signs, caused by articulation instructions
@end itemize
There are a few classes of difficult adjustments.
-@itemize @bullet
+@itemize
@item
In the following example, we define a procedure
@code{my-callback}. This procedure
-@itemize @bullet
+@itemize
@item
determines if we have been split across line breaks
@item
These tools include
-@itemize @bullet
+@itemize
@item
@uref{http://@/denemo@/.sourceforge@/.net/,Denemo}, a graphical score editor.
@item
Download source
-@itemize @bullet
+@itemize
@item tarballs from
@uref{http://lilypond.org/download/} by HTTP.
@item tarballs from
Running LilyPond requires proper installation of the following software
-@itemize @bullet
+@itemize
@item @uref{http://www.freetype.org/,Freetype} (version 2.1.10 or newer).
@item @uref{http://www.freetype.org/,FontConfig} (version 2.2).
Building the website requires some additional tools and packages
-@itemize @bullet
+@itemize
@item The @uref{http://netpbm.sourceforge.net/,netpbm utilities}
@item ImageMagick
@item International fonts (see input/regression/utf-8.ly for hints
the developers. That proved to be unsatisfactory for a number of
reasons:
-@itemize @bullet
+@itemize
@item When LilyPond makes mistakes,
users need to override formatting decisions. Therefore, the user must
have access to the formatting engine. Hence, rules and settings cannot
chapters in a linear fashion.
-@itemize @bullet
+@itemize
@item
@ifhtml
@ignore
-@itemize @bullet
+@itemize
@item
@emph{@r ef{Basic notation}},
This book contains useful reference charts.
-@itemize @bullet
+@itemize
@item
@ifhtml
The
This book explains how to execute the program and how to integrate
LilyPond notation with other programs.
-@itemize @bullet
+@itemize
@item
@emph{@rprogram{Install}},
There are a number of other places which may be very valuable.
-@itemize @bullet
+@itemize
@cindex idiom
@cindex jargon
@cindex terminology
@quotation
@quotation
@cartouche
-@strong{Note:} \TEXT\
+@b{Note:} \TEXT\
@end cartouche
@end quotation
@end quotation
A @code{.ly} file contains any number of toplevel expressions, where a
toplevel expression is one of the following
-@itemize @bullet
+@itemize
@item
An output definition, such as @code{\paper}, @code{\midi}, and
@code{\layout}. Such a definition at the toplevel changes the default
At any point in a file, any of the following lexical instructions can
be entered:
-@itemize @bullet
+@itemize
@item @code{\version}
@item @code{\include}
@item @code{\sourcefilename}
New commands and markups may also be defined to build more elaborated
table of contents:
-@itemize @bullet
+@itemize
@item first, define a new markup variable in the @code{\paper} block
@item then, define a music function which aims at adding a toc element
using this markup paper variable.
of a piece of music in whole notes.
A music object has three kinds of types:
-@itemize @bullet
+@itemize
@item
music name: Each music expression has a name. For example, a note
leads to a @internalsref{NoteEvent}, and @code{\simultaneous} leads to
When interpreted, the function @var{proc} is called for every layout
object found in the context @var{context}, with the following
arguments:
-@itemize @bullet
+@itemize
@item the layout object itself,
@item the context where the layout object was created, and
@item the context where @code{\applyOutput} is processed.
consecutive notes. For true proportional notation, the following
settings are also required.
-@itemize @bullet
+@itemize
@item True proportional notation requires that symbols are allowed
to overstrike each other. That is achieved by removing the
Many scores consist of more than one staff. These staves can be
grouped in several different ways:
-@itemize @bullet
+@itemize
@item
In a @internalsref{GrandStaff}, the group is started with a brace
at the left, and bar lines are connected between the staves.
Here are a couple of hints for successful cue notes
-@itemize @bullet
+@itemize
@item
Cue notes have smaller font sizes.
installation defaults to.
-@itemize @bullet
+@itemize
@item @code{font-encoding}
is a symbol that sets layout of the glyphs. This should only be
set to select different types of non-text fonts, e.g.
Reference. However, many layout objects share properties which can be
used to apply generic tweaks.
-@itemize @bullet
+@itemize
@cindex padding
a substantial amount of technical knowledge or time is required
to understand these files.
-@itemize @bullet
+@itemize
@item Linux: @file{@var{installdir}/lilypond/usr/share/lilypond/current/}
Since LilyPond input files are text, there are two issues to
consider when working with vocal music:
-@itemize @bullet
+@itemize
@item
Song texts must be entered as text, not notes. For example, the
input@tie{}@code{d} should be interpreted as a one letter syllable, not the
There are two main methods to specify the horizontal placement
of the syllables:
-@itemize @bullet
+@itemize
@item
by automatically aligning
the lyrics to a melody or other voice of music, using @code{\addlyrics}
that you want, it doesn't matter what your files look like. However,
there are a few other things to consider when writing lilypond files.
-@itemize @bullet
+@itemize
@item What if you make a mistake? The structure of a lilypond
file can make certain errors easier (or harder) to find.
Here are a few suggestions that can help you to avoid or fix
problems:
-@itemize @bullet
+@itemize
@item @strong{Include @code{\version} numbers in every file}. Note that all
templates contain @code{\version} information. We
highly recommend that you always include the @code{\version}, no matter
If you are entering music from an existing score (i.e., typesetting a
piece of existing sheet music),
-@itemize @bullet
+@itemize
@item Enter one manuscript (the physical copy) system at a time (but still
only one bar per line of text), and
When working on a large project, having a clear structure to your
lilypond files becomes vital.
-@itemize @bullet
+@itemize
@item @strong{Use an variable for each voice}, with a minimum of
structure inside the definition. The structure of the
projects / lilypond.git / commitdiff