Remove @itemize around headings

[lilypond.git] / Documentation / user / introduction.itely

diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely
index a27989416d10c745e94b20372b4f8f44654e8660..5cda80ffeb655ba5f2ab453728cfc4ebec119f02 100644 (file)
--- a/Documentation/user/introduction.itely
+++ b/Documentation/user/introduction.itely
@@ -1,5 +1,5 @@
 @c -*- coding: utf-8; mode: texinfo; -*-
 @c -*- coding: utf-8; mode: texinfo; -*-

-@c This file is part of lilypond.tely
+@c This file is part of lilypond-learning.tely

 @ignore
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
 @ignore
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 


@@ -7,6 +7,8 @@
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 

+@c \version "2.11.38"
+

 @node Introduction
 @chapter Introduction
 
 @node Introduction
 @chapter Introduction
 


@@ -87,9 +89,8 @@ computer edition.
 @end ifnottex
 @end ifnotinfo
 @ifinfo
 @end ifnottex
 @end ifnotinfo
 @ifinfo

-@c workaround for makeinfo-4.6: line breaks and multi-column cookies
-@image{henle-flat-bw,,,png} @image{baer-flat-bw,,,png}
-@image{lily-flat-bw,,,png}
+@image{lilypond/henle-flat-bw,,,png} @image{lilypond/baer-flat-bw,,,png}
+@image{lilypond/lily-flat-bw,,,png}

 @end ifinfo
 
 @item @tab
 @end ifinfo
 
 @item @tab


@@ -243,7 +244,7 @@ programming language; the program's functionality was set in stone by
 the developers.  That proved to be unsatisfactory for a number of
 reasons:
 
 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
 @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


@@ -540,7 +541,7 @@ context.  The Score context is the top level notation context.
 
 @seealso
 
 
 @seealso
 

-Program reference: @internalsref{Contexts}.
+Internals Reference: @internalsref{Contexts}.

 
 @lilypond[quote,ragged-right]
 \include "engraver-example.ily"
 
 @lilypond[quote,ragged-right]
 \include "engraver-example.ily"


@@ -569,14 +570,18 @@ The syntax is also the user-interface for LilyPond, hence it is easy
 to type
 
 @example
 to type
 
 @example

-c'4 d'8
+@{
+  c'4 d'8
+@}

 @end example
 
 @noindent
 a quarter note C1 (middle C) and an eighth note D1 (D above middle C)
 
 @end example
 
 @noindent
 a quarter note C1 (middle C) and an eighth note D1 (D above middle C)
 

-@lilypond[quote,fragment]
-c'4 d'8
+@lilypond[quote]
+{
+  c'4 d'8
+}

 @end lilypond
 
 On a microscopic scale, such syntax is easy to use.  On a larger
 @end lilypond
 
 On a microscopic scale, such syntax is easy to use.  On a larger


@@ -651,8 +656,11 @@ of music engraving into a computer program.  Thanks to all that hard
 work, the program can now be used to perform useful tasks.  The
 simplest application is printing notes.
 
 work, the program can now be used to perform useful tasks.  The
 simplest application is printing notes.
 

-@lilypond[quote,relative=1,fragment]
-\time 2/4 c4 c g'4 g a4 a g2
+@lilypond[quote,relative=1]
+{
+  \time 2/4
+  c4 c g'4 g a4 a g2
+}

 @end lilypond
 
 @noindent
 @end lilypond
 
 @noindent


@@ -690,22 +698,20 @@ to mix music and text in documents.
 @node About this manual
 @section About this manual
 
 @node About this manual
 @section About this manual
 

-There are two manuals about LilyPond: the @emph{user manual} (this
-document), and @emph{program usage}.
-
+FIXME: needs almost-complete rewrite.  -gp

 
 

-@subheading User manual
+There are four manuals about LilyPond: the @emph{Learning Manual},
+the @emph{Notation Reference}, the @emph{Application Usage}, and the
+@emph{Internals Reference}.

 
 

-The manual is divided into three books.

 
 

-@subsubheading Learning manual
+@subheading Learning Manual (LM)

 
 This book explains how to begin learning LilyPond, as well as explaining
 some key concepts in easy terms.  It is recommended to read these
 chapters in a linear fashion.
 
 
 This book explains how to begin learning LilyPond, as well as explaining
 some key concepts in easy terms.  It is recommended to read these
 chapters in a linear fashion.
 

-
-@itemize @bullet
+@itemize

 
 @item
 @ifhtml
 
 @item
 @ifhtml


@@ -716,8 +722,8 @@ gives a gentle introduction to typesetting music.  First time
 users should start here.
 
 @item
 users should start here.
 
 @item

-@emph{@ref{Putting it all together}},
-explains some general concepts about the lilypond file format.  If
+@emph{@ref{Fundamental concepts}},
+explains some general concepts about the LilyPond file format.  If

 you are not certain where to place a command, read this chapter!
 
 @item
 you are not certain where to place a command, read this chapter!
 
 @item


@@ -733,7 +739,7 @@ produces.
 @end itemize
 
 
 @end itemize
 
 

-@subsubheading Notation reference
+@subheading Notation Reference (NR)

 
 This book explains all the LilyPond commands which produce notation.  It
 assumes that readers are familiar with the concepts in the Learning
 
 This book explains all the LilyPond commands which produce notation.  It
 assumes that readers are familiar with the concepts in the Learning


@@ -743,7 +749,7 @@ All of this needs to be rewritten after GDP, anyway.
 
 @ignore
 
 
 @ignore
 

-@itemize @bullet
+@itemize

 
 @item
 @emph{@r ef{Basic notation}},
 
 @item
 @emph{@r ef{Basic notation}},


@@ -787,7 +793,7 @@ explains how to create music functions.
 
 This book contains useful reference charts.
 
 
 This book contains useful reference charts.
 

-@itemize @bullet
+@itemize

 @item
 @ifhtml
 The
 @item
 @ifhtml
 The


@@ -831,12 +837,13 @@ is a complete index.
 
 @end ignore
 
 
 @end ignore
 

+

 @subheading Program usage
 
 This book explains how to execute the program and how to integrate
 LilyPond notation with other programs.
 
 @subheading Program usage
 
 This book explains how to execute the program and how to integrate
 LilyPond notation with other programs.
 

-@itemize @bullet
+@itemize

 
 @item
 @emph{@rprogram{Install}},
 
 @item
 @emph{@rprogram{Install}},


@@ -854,7 +861,7 @@ section explains how to upgrade input files from previous versions of
 LilyPond.
 
 @item
 LilyPond.
 
 @item

-@emph{@rprogram{LilyPond-book}},
+@emph{@rprogram{lilypond-book}},

 explains the details behind creating
 documents with in-line music examples, like this manual.
 
 explains the details behind creating
 documents with in-line music examples, like this manual.
 


@@ -872,7 +879,7 @@ formats to the @code{.ly} format.
 
 There are a number of other places which may be very valuable.
 
 
 There are a number of other places which may be very valuable.
 

-@itemize @bullet
+@itemize

 @cindex idiom
 @cindex jargon
 @cindex terminology
 @cindex idiom
 @cindex jargon
 @cindex terminology


@@ -898,7 +905,7 @@ advisable to consult the glossary.
 @item
 The
 @ifhtml
 @item
 The
 @ifhtml

-@uref{source/input/lsr/collated-files.html,Snippets}
+@uref{source/input/lsr/lilypond-snippets/index.html,Snippets}

 @end ifhtml
 @ifnothtml
 Snippets
 @end ifhtml
 @ifnothtml
 Snippets


@@ -912,10 +919,10 @@ Repository}.  This website also has a searchable LilyPond manual.
 @item
 The
 @iftex
 @item
 The
 @iftex

-Program reference
+Internals Reference

 @end iftex
 @ifnottex
 @end iftex
 @ifnottex

-@ref{Top,Program reference,,lilypond-internals}
+@ref{Top,Internals Reference,,lilypond-internals}

 @end ifnottex
 is a set of heavily cross linked HTML pages, which document the
 nitty-gritty details of each and every LilyPond class, object, and
 @end ifnottex
 is a set of heavily cross linked HTML pages, which document the
 nitty-gritty details of each and every LilyPond class, object, and


@@ -957,7 +964,7 @@ initialization and example files.  Throughout this manual, we refer to
 input files relative to the top-directory of the source archive.  For
 example, @file{input/@/lsr/@/dirname/@/bla@/.ly} may refer to the file
 @file{lilypond@/2.x.y/@/input/@/lsr/@/dirname/@/bla@/.ly}.  On binary
 input files relative to the top-directory of the source archive.  For
 example, @file{input/@/lsr/@/dirname/@/bla@/.ly} may refer to the file
 @file{lilypond@/2.x.y/@/input/@/lsr/@/dirname/@/bla@/.ly}.  On binary

-packages for the Unix platform, the documentation and examples can
+packages for the UNIX platform, the documentation and examples can

 typically be found somewhere below
 @file{/usr/@/share/@/doc/@/lilypond/}.  Initialization files, for
 example @file{scm/@/lily@/.scm}, or @file{ly/@/engraver@/-init@/.ly},
 typically be found somewhere below
 @file{/usr/@/share/@/doc/@/lilypond/}.  Initialization files, for
 example @file{scm/@/lily@/.scm}, or @file{ly/@/engraver@/-init@/.ly},


@@ -969,7 +976,7 @@ are usually found in the directory @file{/usr/@/share/@/lilypond/}.
 @cindex lilypond-internals
 @cindex internal documentation
 @cindex Scheme
 @cindex lilypond-internals
 @cindex internal documentation
 @cindex Scheme

-@cindex extending lilypond
+@cindex extending LilyPond

 @cindex index
 
 Finally, this and all other manuals, are available online both as PDF
 @cindex index
 
 Finally, this and all other manuals, are available online both as PDF