* Werner LEMBERG wrote on Sat, Jul 31, 2010 at 01:52:23PM CEST: > > > > Additionally, we want two spaces after a full stop in the source > > > documentation files. > > > > Ah, well, lemme see what I can do. > > :-) We have a style guide; say `info lilypond-contributor' (I just > see that there isn't a proper menu entry for it in the `dir' file) and > go to the `Text formatting' node.
Here we go with spacing after end of sentence. The first patch has changes that are not purely white space, the second one adds missing space where needed and is bzip2'ed for size, the third one removes extra spaces. Cheers, Ralf
>From 779bf9ec922e72dbe207684cce549404c9ac6006 Mon Sep 17 00:00:00 2001
From: Ralf Wildenhues <ralf.wildenh...@gmx.de>
Date: Sun, 1 Aug 2010 11:36:47 +0200
Subject: [PATCH 1/9] Doc: fix period and colon placement in a couple of
instances.
---
Documentation/contributor/programming-work.itexi | 6 +++---
Documentation/contributor/release-work.itexi | 2 +-
Documentation/included/compile.itexi | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/contributor/programming-work.itexi
b/Documentation/contributor/programming-work.itexi
index ddf57c9..aa8da23 100644
--- a/Documentation/contributor/programming-work.itexi
+++ b/Documentation/contributor/programming-work.itexi
@@ -1894,15 +1894,15 @@ A Music + Music_output_def object leads to a
Global_context object (see
ly_run_translator ())
During interpreting, Global_context + Music leads to a bunch of
-Contexts. (see Global_translator::run_iterator_on_me () )
+Contexts (see Global_translator::run_iterator_on_me ()).
After interpreting, Global_context contains a Score_context (which
contains staves, lyrics etc.) as a child. Score_context::get_output ()
spews a Music_output object (either a Paper_score object for notation
or Performance object for MIDI).
-The Music_output object is the entry point for the backend. (see
-ly_render_output () )
+The Music_output object is the entry point for the backend (see
+ly_render_output ()).
The main steps of the backend itself are in
diff --git a/Documentation/contributor/release-work.itexi
b/Documentation/contributor/release-work.itexi
index 10bf481..b1a79e4 100644
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -231,7 +231,7 @@ Before release:
* write preface section for manual.
-* submit pots for translation : send url of tarball to
+* submit pots for translation: send url of tarball to
translation@@iro.umontreal.ca, mentioning lilypond-VERSION.pot
* Check reg test
diff --git a/Documentation/included/compile.itexi
b/Documentation/included/compile.itexi
index e36661d..7f023f0 100644
--- a/Documentation/included/compile.itexi
+++ b/Documentation/included/compile.itexi
@@ -1144,8 +1144,8 @@ Contributor's Guide}.
@item To retrieve the Lilypond source code from @code{git},
copy-and-paste each command from the CG @qq{Main source code}
-section into the terminal. (paste into the terminal with keystroke
-...@code{ctrl+shift+v})
+section into the terminal (paste into the terminal with keystroke
+...@code{ctrl+shift+v}).
@item Prepare to build Lilypond by running the configuration script.
Type
--
1.7.2.rc3.47.g996ce
0002-Doc-ensure-two-spaces-after-end-of-sentence.patch.bz2
Description: Binary data
>From 2bae10f7fc77359d1fd19eac206d594f738a5d2f Mon Sep 17 00:00:00 2001
From: Ralf Wildenhues <ralf.wildenh...@gmx.de>
Date: Sun, 1 Aug 2010 10:59:37 +0200
Subject: [PATCH 3/9] Doc: ensure not more than two spaces after end of sentence.
---
Documentation/included/compile.itexi | 2 +-
Documentation/learning/tweaks.itely | 2 +-
Documentation/notation/ancient.itely | 2 +-
Documentation/notation/changing-defaults.itely | 2 +-
Documentation/notation/chords.itely | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/included/compile.itexi
b/Documentation/included/compile.itexi
index 0663f03..6178d6d 100644
--- a/Documentation/included/compile.itexi
+++ b/Documentation/included/compile.itexi
@@ -858,7 +858,7 @@ exec /opt/local/bin/pngtopnm "$@"
LilyPond comes with an extensive suite that exercises the entire
-program. This suite can be used to test that the binary has
+program. This suite can be used to test that the binary has
been built correctly.
The test suite can be executed with:
diff --git a/Documentation/learning/tweaks.itely
b/Documentation/learning/tweaks.itely
index 8c29eec..2d3d46e 100644
--- a/Documentation/learning/tweaks.itely
+++ b/Documentation/learning/tweaks.itely
@@ -2518,7 +2518,7 @@ affecting anything else.
@cindex positions property
This is most useful for manually adjusting the slope and height
-of beams, slurs, and tuplets. It takes a pair of numbers
+of beams, slurs, and tuplets. It takes a pair of numbers
giving the position of the left and right ends of the beam, slur,
etc. relative to the center line of the staff. Units are
staff-spaces. Note, though, that slurs and phrasing slurs cannot
diff --git a/Documentation/notation/ancient.itely
b/Documentation/notation/ancient.itely
index c2a4c07..106e68d 100644
--- a/Documentation/notation/ancient.itely
+++ b/Documentation/notation/ancient.itely
@@ -699,7 +699,7 @@ scope for mensural notation).
@cindex rests, ancient
Use the @code{style} property of grob @code{Rest} to select
-ancient rests. Supported styles are @code{classical},
+ancient rests. Supported styles are @code{classical},
@code{neomensural}, and @code{mensural}. @code{classical} differs
from the @code{default} style only in that the quarter rest looks
like a horizontally mirrored 8th rest. The @code{mensural} and
diff --git a/Documentation/notation/changing-defaults.itely
b/Documentation/notation/changing-defaults.itely
index 682c8e3..6c4e96a 100644
--- a/Documentation/notation/changing-defaults.itely
+++ b/Documentation/notation/changing-defaults.itely
@@ -2401,7 +2401,7 @@ a
For some layout objects, the @code{minimum-length} property becomes
effective only if the @code{set-spacing-rods} procedure is called
explicitly. To do this, the @code{springs-and-rods} property should
-be set to @code{ly:spanner::set-spacing-rods}. For example,
+be set to @code{ly:spanner::set-spacing-rods}. For example,
the minimum length of a glissando has no effect unless the
@code{springs-and-rods} property is set:
diff --git a/Documentation/notation/chords.itely
b/Documentation/notation/chords.itely
index da052ad..4b122bc 100644
--- a/Documentation/notation/chords.itely
+++ b/Documentation/notation/chords.itely
@@ -552,7 +552,7 @@ properly if entered using simultaneous music.
There is no unique system for naming chords. Different musical
traditions use different names for the same set of chords. There
-are also different symbols displayed for a given chord name. The
+are also different symbols displayed for a given chord name. The
names and symbols displayed for chord names are customizable.
@cindex jazz chords
--
1.7.2.rc3.47.g996ce
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
