Doc: resolve various FIXMEs.

Downgrading a FIXME to a TODO is still a "resolution".  Of a sort.

diff --git a/Documentation/essay/literature.itely b/Documentation/essay/literature.itely
index 2ebc7a300da37b8f85db94f1d5445748eed89f3c..79238d0f59ae63ea97575419457eb483f8234d78 100644 (file)
--- a/Documentation/essay/literature.itely
+++ b/Documentation/essay/literature.itely
@@ -13,7 +13,7 @@
 @node Literature list
 @chapter Literature list
 
 @node Literature list
 @chapter Literature list
 

-FIXME: blah
+Here are lists of references used in LilyPond.

 
 @menu
 * Short literature list::
 
 @menu
 * Short literature list::

diff --git a/Documentation/included/compile.itexi b/Documentation/included/compile.itexi
index 9a47a9e3584344ad82857f4fb71a0a9589c448f0..c124b84d2f81c2ab7aff7074adc8975d03f10ff8 100644 (file)
--- a/Documentation/included/compile.itexi
+++ b/Documentation/included/compile.itexi
@@ -315,10 +315,9 @@ make help
 
 @noindent
 from every directory in the build tree.  Most targets for
 
 @noindent
 from every directory in the build tree.  Most targets for

-documentation maintenance are available from @file{Documentation/};
-@c FIXME: xref to CG
-for more information, see the Contributor's Guide, section
-@emph{Documentation work}.
+documentation maintenance are available from
+@file{Documentation/}.  For more information, see
+@rcontrib{Documentation work}.

 
 The makefile variable @code{QUIET_BUILD} may be set to @code{1} for a
 less verbose build output, just like for building the programs.
 
 The makefile variable @code{QUIET_BUILD} may be set to @code{1} for a
 less verbose build output, just like for building the programs.

diff --git a/Documentation/included/generating-output.itexi b/Documentation/included/generating-output.itexi
index 5b725ecf39daefdccfbef5bebfa7fe12b78d1afa..240d7749b821596dd0df8e609e3d27716d016922 100644 (file)
--- a/Documentation/included/generating-output.itexi
+++ b/Documentation/included/generating-output.itexi
@@ -1,5 +1,6 @@
 @c -*- coding: utf-8; mode: texinfo; -*-
 @c -*- coding: utf-8; mode: texinfo; -*-

-@c This file is part of FIXME
+@c This file is part of web/download.itexi and
+@c learning/tutorial.itely

 
 @c This is about "compiling" a lilypond file
 @c (Learning 1 Tutorial), **not** compiling the
 
 @c This is about "compiling" a lilypond file
 @c (Learning 1 Tutorial), **not** compiling the

diff --git a/Documentation/included/helpus.itexi b/Documentation/included/helpus.itexi
index b850e9066d6a8113a0e4f91d3516f903f491f088..8386924febcb7ad8bbbfb499739dea3340032587 100644 (file)
--- a/Documentation/included/helpus.itexi
+++ b/Documentation/included/helpus.itexi
@@ -1,5 +1,6 @@
 @c -*- coding: utf-8; mode: texinfo; -*-
 @c -*- coding: utf-8; mode: texinfo; -*-

-@c This file is part of FIXME
+@c This file is part of web/community.itexi and
+@c contributor/introduction.itely

 
 @macro helpusNeed
 @subheading We need you!
 
 @macro helpusNeed
 @subheading We need you!

diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely
index 94899d1e0edb01043d221194835f659bbfe271e9..10b26405b6699da5a92a688e96a34ff9d28d33cf 100644 (file)
--- a/Documentation/notation/changing-defaults.itely
+++ b/Documentation/notation/changing-defaults.itely
@@ -2979,7 +2979,7 @@ The locations of the end-points of the spanner are computed
 on-the-fly for every graphic object, but it is possible to
 override these:
 
 on-the-fly for every graphic object, but it is possible to
 override these:
 

-@c FIXME Complete
+@c TODO Complete

 @lilypond[relative=2,ragged-right,verbatim,fragment]
 e2 \glissando f
 \once \override Glissando #'(bound-details right Y) = #-2
 @lilypond[relative=2,ragged-right,verbatim,fragment]
 e2 \glissando f
 \once \override Glissando #'(bound-details right Y) = #-2


@@ -3411,7 +3411,7 @@ e
 @node Vertical grouping of grobs
 @subsection Vertical grouping of grobs
 
 @node Vertical grouping of grobs
 @subsection Vertical grouping of grobs
 

-@c FIXME Expand this section
+@c TODO Expand this section

 
 The VerticalAlignment and VerticalAxisGroup grobs work together.
 VerticalAxisGroup groups together different grobs like Staff, Lyrics,
 
 The VerticalAlignment and VerticalAxisGroup grobs work together.
 VerticalAxisGroup groups together different grobs like Staff, Lyrics,

diff --git a/Documentation/notation/spacing.itely b/Documentation/notation/spacing.itely
index 2003bff181a23004a65bb172628cf979f2338126..9a5a7bea28194e1bccdc1deaabc30a8dc847ddab 100644 (file)
--- a/Documentation/notation/spacing.itely
+++ b/Documentation/notation/spacing.itely
@@ -554,7 +554,7 @@ increased by one.  Default: @code{##f}.
 
 @ignore
 
 
 @ignore
 

-FIXME: this variable is used, but I don't know what it does. -pm
+TODO: this variable is used, but I don't know what it does. -pm

 @item blank-after-score-page-force
 @funindex blank-after-score-page-force
 
 @item blank-after-score-page-force
 @funindex blank-after-score-page-force
 

diff --git a/Documentation/notation/vocal.itely b/Documentation/notation/vocal.itely
index 44f4b8c8aa723a4edcd390a23d3e9c06410dd08d..34c3f764ef628b6d26dfb71c033b8dbd260e92cd 100644 (file)
--- a/Documentation/notation/vocal.itely
+++ b/Documentation/notation/vocal.itely
@@ -156,7 +156,7 @@ Notation Reference:
 @cindex spaces, in lyrics
 @cindex quotes, in lyrics
 
 @cindex spaces, in lyrics
 @cindex quotes, in lyrics
 

-@c FIXME: this section is to be rewritten.
+@c TODO: this section is to be rewritten.

 Since LilyPond input files are text, there is at least one
 issue to consider when working with vocal music:
 song texts must be interpreted as text, not notes.  For example, the
 Since LilyPond input files are text, there is at least one
 issue to consider when working with vocal music:
 song texts must be interpreted as text, not notes.  For example, the


@@ -301,7 +301,7 @@ Internals Reference:
 @rinternals{LyricSpace}.
 
 
 @rinternals{LyricSpace}.
 
 

-@c FIXME: this title has to be changed (possible confusion with LM) -vv
+@c TODO: this title has to be changed (possible confusion with LM) -vv

 @node Setting simple songs
 @unnumberedsubsubsec Setting simple songs
 
 @node Setting simple songs
 @unnumberedsubsubsec Setting simple songs
 


@@ -395,7 +395,7 @@ The final input would resemble
 @end example
 
 @ignore
 @end example
 
 @ignore

-@c FIXME
+@c TODO

 http://code.google.com/p/lilypond/issues/detail?id=329
 The problem cannot be reproduced.
 The following has no sense, because the issue seems to be fixed.
 http://code.google.com/p/lilypond/issues/detail?id=329
 The problem cannot be reproduced.
 The following has no sense, because the issue seems to be fixed.


@@ -441,7 +441,7 @@ Internals Reference:
 @funindex \addlyrics
 @funindex \lyricsto
 
 @funindex \addlyrics
 @funindex \lyricsto
 

-@c FIXME: this stuff is to be rewritten. -vv
+@c TODO: this stuff is to be rewritten. -vv

 
 Aligning of text with melodies can be made automatically, but if you
 specify the durations of the syllables it can also be made manually.
 
 Aligning of text with melodies can be made automatically, but if you
 specify the durations of the syllables it can also be made manually.


@@ -646,7 +646,7 @@ single syllable; such vocalises are called melismas, or melismata.
 You can define melismata entirely in the lyrics, by entering @code{_}
 for every extra note that has to be added to the melisma.
 
 You can define melismata entirely in the lyrics, by entering @code{_}
 for every extra note that has to be added to the melisma.
 

-@c FIXME: clarify: __ is used to crate a lyric extender,
+@c TODO: clarify: __ is used to crate a lyric extender,

 @c _ is used to add a note to a melisma, so both __ and _ are needed.
 
 @c verbose! --FV
 @c _ is used to add a note to a melisma, so both __ and _ are needed.
 
 @c verbose! --FV


@@ -803,7 +803,7 @@ TBC
 @node Specific uses of lyrics
 @subsection Specific uses of lyrics
 
 @node Specific uses of lyrics
 @subsection Specific uses of lyrics
 

-@c FIXME This whole section is to be reorganized. -vv
+@c TODO This whole section is to be reorganized. -vv

 
 Often, different stanzas of one song are put to one melody in slightly
 differing ways.  Such variations can still be captured with
 
 Often, different stanzas of one song are put to one melody in slightly
 differing ways.  Such variations can still be captured with


@@ -1214,7 +1214,7 @@ This is achieved with
 Here, @code{alternative} is the name of the @code{Voice} context
 containing the triplet.
 
 Here, @code{alternative} is the name of the @code{Voice} context
 containing the triplet.
 

-@c FIXME: make this easier to understand -vv
+@c TODO: make this easier to understand -vv

 This command must be one syllable too early, before @q{Ty} in this
 case.  In other words, changing the associatedVoice happens one step
 later than expected.  This is for technical reasons, and it is not a
 This command must be one syllable too early, before @q{Ty} in this
 case.  In other words, changing the associatedVoice happens one step
 later than expected.  This is for technical reasons, and it is not a

diff --git a/Documentation/usage/external.itely b/Documentation/usage/external.itely
index 3f70d971bb2b917d7419a6b90fc14d093c2fe95d..49fd542f8f716a3fd150d2e0f5fa394da526f8b7 100644 (file)
--- a/Documentation/usage/external.itely
+++ b/Documentation/usage/external.itely
@@ -13,8 +13,7 @@
 @node External programs
 @chapter External programs
 
 @node External programs
 @chapter External programs
 

-FIXME: blah blah
-
+LilyPond can interact with other programs in various ways.

 
 @menu
 * Point and click::
 
 @menu
 * Point and click::


@@ -579,7 +578,11 @@ lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png myfile.ly
 @node Independent includes
 @section Independent @code{include}s
 
 @node Independent includes
 @section Independent @code{include}s
 

-FIXME: blah blah
+Some people have written large (and useful!) code that can be
+shared between projects.  This code might eventually make its way
+into LilyPond itself, but until that happens, you must download
+and @code{\include} them manually.
+

 
 @menu
 * MIDI articulation::
 
 @menu
 * MIDI articulation::


@@ -589,6 +592,6 @@ FIXME: blah blah
 @node MIDI articulation
 @subsection MIDI articulation
 
 @node MIDI articulation
 @subsection MIDI articulation
 

-stub for info about Dr. Peter Chubb's @file{articulate.ly}
+TODO stub for info about Dr. Peter Chubb's @file{articulate.ly}