Patch should be pasted at the end of the email. Please read them all and
decide which should be implemented as appropriate. Also let me know if any
problems result from my work; I think I kept it all in tact for how the file
formats go. Feedback appreciated.
'crosslinked' should either be 'cross-linked' or 'cross linked'; patch
changes is 'cross linked'.
Windows program NotePad should be Notepad (unless perhaps a different
program called Note'P'ad was being mentioned instead of Note'pad', or if it
has changed sometime before or after windows98se). Patch includes change.
Is 'octavation' a word? I understand what it should mean, but I haven't seen
it outside of lilypond. No patch submitted.
Is 'prepending' a word, I'll check more sources, but cannot seem to find a
reference to it.
(de)crescendi could also be spelled (de)crescendos. Spellcheckers often
think the 'i' was s typo for 'o', so I saw this. No patch submitted as either
way is correct by what I know.
Should 'upstep' be 'up step'? No patch included.
'barlines' should be 'bar lines'. Patch includes changes.
'keysignature' should be 'key signature'. Patch includes change.
'linebreaks' should be 'line breaks'
Should 'wildcards' be 'wild cards'? Not patched.
Should 'autobeamer' be 'auto beamer'? 1 occurrence. Patch included.
'behaviour' changed to 'behavior'; localization would make a difference here
as to which should be used if 'behaviour' is used in some countries as a word
like I think it is.
'cancelled' changed to 'canceled'. If this fix is specifically not
preferred, let me know; I guess some people use cancelled, but I've found
most documentation explaining usage of cancelled to cross over and begin just
saying it as canceled. Now that I made several changes, I wonder if it is a
time related choice. Maybe I switch between them. Numerous (but probably not
all) patches. Should they be implemented?
'multivoice' changed to 'multi voice'. Patch included.
I need sleep, so I will have to resume later; here is the current state. I'll
focus more on content/grammar after spelling questions/issues are pretty much
straightened out.
Index: Documentation/user/internals.itely
===================================================================
RCS file: /cvsroot/lilypond/lilypond/Documentation/user/internals.itely,v
retrieving revision 1.71
diff -u -3 -p -u -r1.71 internals.itely
--- Documentation/user/internals.itely 22 Feb 2004 21:47:27 -0000 1.71
+++ Documentation/user/internals.itely 27 Feb 2004 07:07:53 -0000
@@ -516,7 +516,7 @@ When it is installed, the following link
@menu
* Inline Scheme::
* Input variables and Scheme::
-* Scheme datatypes::
+* Scheme data types::
* Assignments::
@end menu
@@ -602,8 +602,8 @@ written as
[EMAIL PROTECTED] Scheme datatypes
[EMAIL PROTECTED] Scheme datatypes
[EMAIL PROTECTED] Scheme data types
[EMAIL PROTECTED] Scheme data types
Scheme is used to glue together different program modules. To aid this
glue function, many LilyPond specific object types can be passed as
Index: Documentation/user/introduction.itely
===================================================================
RCS file: /cvsroot/lilypond/lilypond/Documentation/user/introduction.itely,v
retrieving revision 1.74
diff -u -3 -p -u -r1.74 introduction.itely
--- Documentation/user/introduction.itely 24 Feb 2004 22:14:30 -0000
1.74
+++ Documentation/user/introduction.itely 27 Feb 2004 07:07:54 -0000
@@ -510,7 +510,7 @@ numbers and operators.
In effect, the input format is a language, and the rules of that
language can be specified succinctly with a so-called context-free
-grammar. The grammar formally specificies what types of input form
+grammar. The grammar formally specifies what types of input form
valid `sentences'. Reading such languages, and splitting them into
grammatical structures is a problem with standard solutions.
Moreover, rigid definitions make the format easier to understand: a
@@ -674,7 +674,7 @@ Program reference
(available @uref{../lilypond-internals/lilypond-internals.html,here})
@end ifhtml
-The program reference is a set of heavily crosslinked HTML pages,
+The program reference is a set of heavily cross linked HTML pages,
which documents the nit-gritty details of each and every LilyPond
class, object and function. It is produced directly from the
formatting definitions used.
@@ -696,7 +696,7 @@ have clickable links.
After you have gone through the tutorial, you should be able to write
input files. In practice, writing files from scratch turns out to be
-intimidating. To give you a headstart, we have collected a number of
+intimidating. To give you a head start, we have collected a number of
often-used formats in example files. These files can be used as a
start: simply copy the template, and add notes in the appropriate
places.
@@ -720,7 +720,7 @@ big HTML document, with pictures and exp
This collection of files tests each notation and engraving feature of
LilyPond in one file. The collection is primarily there to help us
-debug problems, but it can be instructive to see how we excercise the
+debug problems, but it can be instructive to see how we exercise the
program. The format is like the tips and tricks document.
@end itemize
@@ -748,7 +748,7 @@ usually found in the directory @file{/us
@cindex internal documentation
@cindex Scheme
@cindex extending lilypond
[EMAIL PROTECTED] bugreport
[EMAIL PROTECTED] bug report
@cindex index
Finally, this and all other manuals, are available online both as PDF
Index: Documentation/user/preface.itely
===================================================================
RCS file: /cvsroot/lilypond/lilypond/Documentation/user/preface.itely,v
retrieving revision 1.35
diff -u -3 -p -u -r1.35 preface.itely
--- Documentation/user/preface.itely 13 Feb 2004 00:57:16 -0000 1.35
+++ Documentation/user/preface.itely 27 Feb 2004 07:07:54 -0000
@@ -94,13 +94,13 @@ pieces of sheet music. Seeing that stil
pleasant way.
Our users not only give us good vibes by using our program, many of
-them also help us by giving suggestions and sending bugreports. So
+them also help us by giving suggestions and sending bug reports. So
first and foremost, we would like to thank all users that sent us
-bugreports, gave suggestions or contributed in any other way to
+bug reports, gave suggestions or contributed in any other way to
LilyPond.
We would also like to thank the following people: Mats Bengtsson for
-the incountable number of questions he answered on the mailing list,
+the uncountable number of questions he answered on the mailing list,
and Rune Zedeler for his energy in finding and fixing bugs. Nicola
Bernardini for inviting us to his workshop on music publishing, which
was truly a masterclass, and Heinz Stolba and James Ingram for
Index: Documentation/user/refman.itely
===================================================================
RCS file: /cvsroot/lilypond/lilypond/Documentation/user/refman.itely,v
retrieving revision 1.453
diff -u -3 -p -u -r1.453 refman.itely
--- Documentation/user/refman.itely 27 Feb 2004 01:07:13 -0000 1.453
+++ Documentation/user/refman.itely 27 Feb 2004 07:07:57 -0000
@@ -721,7 +721,7 @@ c d b bes a g c2 }
Long notes can be converted automatically to tied notes. This is done
by replacing the @internalsref{Note_heads_engraver} by the
@internalsref{Completion_heads_engraver}.
-In the following examples, notes crossing the barline are split and tied.
+In the following examples, notes crossing the bar line are split and tied.
@lilypond[noindent,verbatim,relative=1]
@@ -795,7 +795,7 @@ Examples: @inputfileref{input/test,staff
@refbugs
If a staff is ended halfway a piece, the staff symbol may not end
-exactly on the barline.
+exactly on the bar line.
@node Key signature
@@ -838,7 +838,7 @@ This command sets the context property
can be specified by setting this property directly.
Accidentals and key signatures often confuse new users, because
-unaltered notes get natural signs depending on the keysignature. The
+unaltered notes get natural signs depending on the key signature. The
tutorial explains why this is so in @ref{More about pitches}.
@refbugs
@@ -950,7 +950,7 @@ the staff. They are created by invoking
The @code{set-octavation} function also takes -1 (for 8va bassa) and 2
(for 15ma) as arguments. Internally the function sets the properties
[EMAIL PROTECTED] (eg. to @code{"8va"}) and
[EMAIL PROTECTED] (e.g. to @code{"8va"}) and
@code{centralCPosition}. For overriding the text of the bracket, set
@code{ottavation} after invoking @code{set-octavation}, i.e.,
@@ -1089,12 +1089,12 @@ off.
Bar lines delimit measures, but are also used to indicate repeats.
Normally, they are inserted automatically. Line breaks may only
-happen on barlines.
+happen on bar lines.
@syntax
Special types
-of barlines can be forced with the @code{\bar} command:
+of bar lines can be forced with the @code{\bar} command:
@c
@lilypond[relative=1,fragment,verbatim]
c4 \bar "|:" c4
@@ -1114,11 +1114,11 @@ c4
\bar "|." c
\bar ":" c
@end lilypond
-For allowing linebreaks, there is a special command,
+For allowing line breaks, there is a special command,
@example
\bar "empty"
@end example
-This will insert an invisible barline, and allow linebreaks at this
+This will insert an invisible bar line, and allow line breaks at this
point.
In scores with many staves, a @code{\bar} command in one staff is
@@ -1167,7 +1167,7 @@ lines that span staves are @internalsref
@cindex bar lines at start of system
@cindex start of system
-The barlines at the start of each system are
+The bar lines at the start of each system are
@internalsref{SystemStartBar}, @internalsref{SystemStartBrace}, and
@internalsref{SystemStartBracket}. Only one of these types is created
in every context, and that type is determined by the property
@@ -1507,7 +1507,7 @@ So, while it is possible to have differe
beams and sixteenth beams, a beam that contains both eight and
sixteenth notes will use the rules for the sixteenth beam.
-In the example below, the autobeamer makes eight beams and sixteenth
+In the example below, the auto beamer makes eight beams and sixteenth
end at 3 eights; the third beam can only be corrected by specifying
manual beaming.
@@ -1554,20 +1554,20 @@ supplied, @code{Staff} is the default.
The following styles are supported:
@table @code
@item default
- This is the default typesetting behaviour. It should correspond
+ This is the default typesetting behavior. It should correspond
to 18th century common practice: Accidentals are
remembered to the end of the measure in which they occur and
only on their own octave.
@item voice
@c
- The normal behaviour is to remember the accidentals on
+ The normal behavior is to remember the accidentals on
Staff-level. This variable, however, typesets accidentals
individually for each voice. Apart from that, the rule is similar to
@code{code}.
This leads to some weird and often unwanted results
- because accidentals from one voice do not get cancelled in other
+ because accidentals from one voice do not get canceled in other
voices:
@lilypond[raggedright,relative,fragment,verbatim,quote]
\context Staff <<
@@ -1588,8 +1588,8 @@ instead.
This rule corresponds to the common practice in the 20th
century.
This rule prints the same accidentals as @code{default}, but temporary
- accidentals also are cancelled in other octaves. Furthermore,
- in the same octave, they also get cancelled in the following
+ accidentals also are canceled in other octaves. Furthermore,
+ in the same octave, they also get canceled in the following
measure:
@lilypond[raggedright,fragment,verbatim]
Index: Documentation/user/tutorial.itely
===================================================================
RCS file: /cvsroot/lilypond/lilypond/Documentation/user/tutorial.itely,v
retrieving revision 1.185
diff -u -3 -p -u -r1.185 tutorial.itely
--- Documentation/user/tutorial.itely 27 Feb 2004 01:07:14 -0000 1.185
+++ Documentation/user/tutorial.itely 27 Feb 2004 07:07:57 -0000
@@ -339,7 +339,7 @@ File/Print inside your viewing program.
On Windows, the same procedure should work. The terminal is started by
clicking on the LilyPond or Cygwin icon. Any text editor (such as
-NotePad, Emacs or Vim) may be used to edit the LilyPond file.
+Notepad, Emacs or Vim) may be used to edit the LilyPond file.
To view the PDF file, try the following:
@itemize
@@ -1390,7 +1390,7 @@ More information on formatting piano mus
When the music is converted from notes to print it is interpreted
in left-to-right order. This is similar to what happens when we read
music. During this step context-sensitive information such as the
-accidentals to print, and where barlines must be placed, are stored in
+accidentals to print, and where bar lines must be placed, are stored in
variables. These variables are called @emph{context properties}.
The properties can also be manipulated from input files. Consider this input:
@example
@@ -1644,7 +1644,7 @@ places. The following example uses the a
@end example
More information on the possible uses of identifiers is in the
-technical manual, in @ref{Scheme datatypes}.
+technical manual, in @ref{Scheme data types}.
@node An orchestral part
_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
