From 88da77553a3b898874f578810b1bc451382aceff Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Sat, 6 Oct 2007 15:18:16 -0700 Subject: [PATCH] Use @itemize without specifying @bullet. --- Documentation/user/README.txt | 4 +++- Documentation/user/ancient.itely | 10 +++++----- Documentation/user/changing-defaults.itely | 16 ++++++++-------- Documentation/user/converters.itely | 2 +- Documentation/user/install.itely | 6 +++--- Documentation/user/introduction.itely | 12 ++++++------ Documentation/user/macros.itexi | 2 +- Documentation/user/non-music.itely | 6 +++--- Documentation/user/programming-interface.itely | 4 ++-- Documentation/user/rhythms.itely | 2 +- Documentation/user/staff.itely | 4 ++-- Documentation/user/text.itely | 2 +- Documentation/user/tweaks.itely | 4 ++-- Documentation/user/vocal.itely | 4 ++-- Documentation/user/working.itely | 8 ++++---- 15 files changed, 44 insertions(+), 42 deletions(-) diff --git a/Documentation/user/README.txt b/Documentation/user/README.txt index 797cc6338c..fa03b57a60 100644 --- a/Documentation/user/README.txt +++ b/Documentation/user/README.txt @@ -145,7 +145,7 @@ main docs 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 @@ -153,6 +153,8 @@ main docs @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. diff --git a/Documentation/user/ancient.itely b/Documentation/user/ancient.itely index 2082af9acf..06e483a482 100644 --- a/Documentation/user/ancient.itely +++ b/Documentation/user/ancient.itely @@ -20,7 +20,7 @@ and Gregorian Chant notation. There is also limited support for figured bass notation. Many graphical objects provide a @code{style} property, see -@itemize @bullet +@itemize @item @ref{Ancient note heads}, @item @@ -44,7 +44,7 @@ In addition to the standard articulation signs described in section @ref{Articulations}, specific articulation signs for ancient notation are provided. -@itemize @bullet +@itemize @item @ref{Ancient articulations} @end itemize @@ -54,7 +54,7 @@ in terms of just changing a style property of a graphical object or adding articulation signs. Some notational concepts are introduced specifically for ancient notation, -@itemize @bullet +@itemize @item @ref{Custodes}, @item @@ -69,7 +69,7 @@ how to customize a context, you may have a look at the predefined 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 @@ -79,7 +79,7 @@ staff contexts, and directly go ahead with the note entry, There is limited support for figured bass notation which came up during the baroque period. -@itemize @bullet +@itemize @item @ref{Figured bass} @end itemize diff --git a/Documentation/user/changing-defaults.itely b/Documentation/user/changing-defaults.itely index 9bffbc362c..9aece75879 100644 --- a/Documentation/user/changing-defaults.itely +++ b/Documentation/user/changing-defaults.itely @@ -39,7 +39,7 @@ but is also included with the LilyPond documentation package. 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. @@ -471,7 +471,7 @@ In order to add a rule to the list, use #(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". @@ -729,7 +729,7 @@ For scores with only one voice and one staff, contexts are 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. @@ -1621,7 +1621,7 @@ Fingering objects are created by: @internalsref{Fingering_engraver} and 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: @@ -1685,7 +1685,7 @@ Each layout object may have several functions as a notational or 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. @@ -1848,7 +1848,7 @@ applied. 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 @@ -1972,7 +1972,7 @@ property (modified with @code{\set}) was created. There are a few classes of difficult adjustments. -@itemize @bullet +@itemize @item @@ -1995,7 +1995,7 @@ objects have been split over different systems. 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 diff --git a/Documentation/user/converters.itely b/Documentation/user/converters.itely index 8b39478200..f843f2e978 100644 --- a/Documentation/user/converters.itely +++ b/Documentation/user/converters.itely @@ -258,7 +258,7 @@ there are some external tools that also generate LilyPond files. These tools include -@itemize @bullet +@itemize @item @uref{http://@/denemo@/.sourceforge@/.net/,Denemo}, a graphical score editor. @item diff --git a/Documentation/user/install.itely b/Documentation/user/install.itely index 0e62f977f6..7af585088a 100644 --- a/Documentation/user/install.itely +++ b/Documentation/user/install.itely @@ -83,7 +83,7 @@ mingw - Windows x86 Download source -@itemize @bullet +@itemize @item tarballs from @uref{http://lilypond.org/download/} by HTTP. @item tarballs from @@ -159,7 +159,7 @@ header files and libraries. 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). @@ -190,7 +190,7 @@ make web 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 diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely index 9fd63a7e3b..2005ab9bbf 100644 --- a/Documentation/user/introduction.itely +++ b/Documentation/user/introduction.itely @@ -243,7 +243,7 @@ programming language; the program's functionality was set in stone by 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 @@ -705,7 +705,7 @@ some key concepts in easy terms. It is recommended to read these chapters in a linear fashion. -@itemize @bullet +@itemize @item @ifhtml @@ -743,7 +743,7 @@ All of this needs to be rewritten after GDP, anyway. @ignore -@itemize @bullet +@itemize @item @emph{@r ef{Basic notation}}, @@ -787,7 +787,7 @@ explains how to create music functions. This book contains useful reference charts. -@itemize @bullet +@itemize @item @ifhtml The @@ -836,7 +836,7 @@ is a complete index. This book explains how to execute the program and how to integrate LilyPond notation with other programs. -@itemize @bullet +@itemize @item @emph{@rprogram{Install}}, @@ -872,7 +872,7 @@ formats to the @code{.ly} format. There are a number of other places which may be very valuable. -@itemize @bullet +@itemize @cindex idiom @cindex jargon @cindex terminology diff --git a/Documentation/user/macros.itexi b/Documentation/user/macros.itexi index d3ff6cc7ec..312e0485b1 100644 --- a/Documentation/user/macros.itexi +++ b/Documentation/user/macros.itexi @@ -26,7 +26,7 @@ @quotation @quotation @cartouche -@strong{Note:} \TEXT\ +@b{Note:} \TEXT\ @end cartouche @end quotation @end quotation diff --git a/Documentation/user/non-music.itely b/Documentation/user/non-music.itely index 787e747674..558835dbe7 100644 --- a/Documentation/user/non-music.itely +++ b/Documentation/user/non-music.itely @@ -49,7 +49,7 @@ these files end with @samp{.ly}. 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 @@ -165,7 +165,7 @@ toplevel 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} @@ -875,7 +875,7 @@ the @code{tocItemMarkup} definition. 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. diff --git a/Documentation/user/programming-interface.itely b/Documentation/user/programming-interface.itely index e6ba1c6471..e26293b43f 100644 --- a/Documentation/user/programming-interface.itely +++ b/Documentation/user/programming-interface.itely @@ -404,7 +404,7 @@ it takes up time. Time is a rational number that measures the length 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 @@ -1219,7 +1219,7 @@ where @var{proc} is a Scheme function, taking three arguments. 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. diff --git a/Documentation/user/rhythms.itely b/Documentation/user/rhythms.itely index d5cc9e709d..57b8cd2e1e 100644 --- a/Documentation/user/rhythms.itely +++ b/Documentation/user/rhythms.itely @@ -1724,7 +1724,7 @@ Setting this property only affects the ideal spacing between 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 diff --git a/Documentation/user/staff.itely b/Documentation/user/staff.itely index 2476c786ed..4fec973d42 100644 --- a/Documentation/user/staff.itely +++ b/Documentation/user/staff.itely @@ -48,7 +48,7 @@ Two or more staves can be grouped vertically in a 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. @@ -644,7 +644,7 @@ smaller = { Here are a couple of hints for successful cue notes -@itemize @bullet +@itemize @item Cue notes have smaller font sizes. diff --git a/Documentation/user/text.itely b/Documentation/user/text.itely index 148a4f9697..38f2322a84 100644 --- a/Documentation/user/text.itely +++ b/Documentation/user/text.itely @@ -591,7 +591,7 @@ Schoolbook, the sans and typewriter to whatever the Pango 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. diff --git a/Documentation/user/tweaks.itely b/Documentation/user/tweaks.itely index 7f1b7702f6..224f28d91b 100644 --- a/Documentation/user/tweaks.itely +++ b/Documentation/user/tweaks.itely @@ -216,7 +216,7 @@ object (like slurs or beams) are documented in the Program Reference. However, many layout objects share properties which can be used to apply generic tweaks. -@itemize @bullet +@itemize @cindex padding @@ -348,7 +348,7 @@ outside the scope of this manual; users should be warned that 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/} diff --git a/Documentation/user/vocal.itely b/Documentation/user/vocal.itely index e7a339e562..8241fd6b81 100644 --- a/Documentation/user/vocal.itely +++ b/Documentation/user/vocal.itely @@ -12,7 +12,7 @@ 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 @@ -269,7 +269,7 @@ Lyrics are printed by interpreting them in the context called 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} diff --git a/Documentation/user/working.itely b/Documentation/user/working.itely index 4f424544b0..26b1fc6214 100644 --- a/Documentation/user/working.itely +++ b/Documentation/user/working.itely @@ -37,7 +37,7 @@ As long as LilyPond can understand your files and produces the output 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. @@ -68,7 +68,7 @@ structured in order to be easier (or header) to update. 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 @@ -122,7 +122,7 @@ problems if you rearrange your music later. 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 @@ -147,7 +147,7 @@ best. 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 -- 2.39.5