Re: Patch: doc typo
On 3/4/11, Andrew Hawryluk wrote:
> Thanks!
> {dumb typo} * 2
Thanks, pushed.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch: doc typo
On Tue, Mar 1, 2011 at 9:54 PM, Werner LEMBERG wrote:
>
>> +requires additional calculations. To speed up processing slighty, this
> ^^^
>
> slightly :-)
>
>
> Werner
>
Thanks!
{dumb typo} * 2
From e154cf8e2e3cbed2a2fed9876d92d57f127637ff Mon Sep 17 00:00:00 2001
From: Andrew Hawryluk
Date: Tue, 1 Mar 2011 20:35:34 -0700
Subject: [PATCH] Doc: typos in vocals.
---
Documentation/notation/vocal.itely |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/notation/vocal.itely b/Documentation/notation/vocal.itely
index e63729b..b337d26 100644
--- a/Documentation/notation/vocal.itely
+++ b/Documentation/notation/vocal.itely
@@ -1159,7 +1159,7 @@ To make this change for all lyrics in the score, set the property in the
@c TODO: move to LSR -vv
Checking to make sure that text scripts and lyrics are within the margins
-required additional calculations. To speed up processing slighty, this
+requires additional calculations. To speed up processing slightly, this
feature can be disabled:
@example
--
1.7.1
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch: doc typo
> +requires additional calculations. To speed up processing slighty, this ^^^ slightly :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Patch: doc typo
Just found a dumb typo in my recent edits (regarding keep-inside-line = ##t). Thanks! From b5900c53d179cbff1c08e3ff5c78ec2adf14fff1 Mon Sep 17 00:00:00 2001 From: Andrew Hawryluk Date: Tue, 1 Mar 2011 20:35:34 -0700 Subject: [PATCH] Doc: typo in vocals. --- Documentation/notation/vocal.itely |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Documentation/notation/vocal.itely b/Documentation/notation/vocal.itely index e63729b..99d0353 100644 --- a/Documentation/notation/vocal.itely +++ b/Documentation/notation/vocal.itely @@ -1159,7 +1159,7 @@ To make this change for all lyrics in the score, set the property in the @c TODO: move to LSR -vv Checking to make sure that text scripts and lyrics are within the margins -required additional calculations. To speed up processing slighty, this +requires additional calculations. To speed up processing slighty, this feature can be disabled: @example -- 1.7.1 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: patch: doc typo fixes/etc
Thanks so much! I applied the patch.
Comments are a bit weird; this worked:
%{
foo %{ bar %}
%}
...music...
but this didn't:
%{
foo %{ bar %} baz
%}
...music...
It seems simpler to say that comments don't nest. :)
Cheers,
- Graham
Mike Coleman wrote:
Lilypond is very cool!
Here's a short patch that fixes a few documentation typos and also
clarifies a couple of minor points.
In the patch, I say that comments do not nest, but I didn't verify
this. If they do, this'll need correcting.
The other clarification tries to smooth out the comparison to other
languages. Technically, it's not the case, for example, that most
programming languages use { } to enclose expressions.
Regards,
Mike
From c367521fe65ff61c50dcb918ce35cf31613ccebf Mon Sep 17 00:00:00 2001
From: Michael Coleman <[EMAIL PROTECTED]>
Date: Wed, 27 Jun 2007 21:34:58 -0500
Subject: [PATCH] Fix doc typos/etc, plus a couple of clarifications.
---
Documentation/user/basic-notation.itely |2 +-
Documentation/user/instrument-notation.itely |2 +-
Documentation/user/tutorial.itely| 14 +++---
Documentation/user/tweaks.itely |4 ++--
4 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/Documentation/user/basic-notation.itely
b/Documentation/user/basic-notation.itely
index 723bdf0..afcd338 100644
--- a/Documentation/user/basic-notation.itely
+++ b/Documentation/user/basic-notation.itely
@@ -1054,7 +1054,7 @@ These voices are all separate from the voice that
contains the notes just
outside the @code{<< \\ >>} construct. This should be noted when making
changes at the voice level. This also means that slurs and ties cannot go
into or out of a @code{<< \\ >>} construct. Conversely, parallel voices
-from separate @code{<< \\ >>} constructs on the same staff are the the
+from separate @code{<< \\ >>} constructs on the same staff are the
same voice. Here is the same example, with different noteheads for each
voice. Note that the change to the note-head style in the main voice does
not affect
diff --git a/Documentation/user/instrument-notation.itely
b/Documentation/user/instrument-notation.itely
index 28fa837..80c7883 100644
--- a/Documentation/user/instrument-notation.itely
+++ b/Documentation/user/instrument-notation.itely
@@ -4586,7 +4586,7 @@ figures below the notes, use
When using figured bass above the staff with extender lines and
@code{implicitBassFigures} the lines may become swapped around.
Maintaining order consistently will be impossible when multiple figures
-have overlapping extender lines. To avoid this problem, plese
+have overlapping extender lines. To avoid this problem, please
use @code{stacking-dir} on @code{BassFigureAlignment}.
diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index c54307d..5c8c2aa 100644
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -383,8 +383,8 @@ see @ref{Clef}.
@node Working on text files
@subsection Working on text files
-LilyPond input files are treated like files in most programming languages:
-they are case sensitive, white-space insensitive, expressions are
+LilyPond input files are similar to source files in many common programming
languages.
+They are case sensitive, and white-space is generally equivalent. Expressions
are
formed with curly braces @{ @}, and comments are denoted with @code{%} or
@[EMAIL PROTECTED] ... [EMAIL PROTECTED]
@@ -440,7 +440,7 @@ There are two types of comments. The percent symbol @samp{%}
introduces a line comment; anything after @samp{%} on that line is
ignored. A block comment marks a whole section of music
input as a comment. Anything that is enclosed in @[EMAIL PROTECTED] and
@[EMAIL PROTECTED] is
-ignored. The following fragment shows possible uses for comments
+ignored. (Comments do not nest.) The following fragment shows possible uses
for comments
@example
% notes for twinkle twinkle follow
@@ -572,7 +572,7 @@ a
@subheading Warning: key signatures and pitches
To determine whether to print an accidental, LilyPond examines the
-pitches and the key signature. The key signature only effects
+pitches and the key signature. The key signature only affects
the @emph{printed} accidentals, not the actual pitches! This is a
feature that often causes confusion to newcomers, so let us explain it
in more detail.
@@ -1463,12 +1463,12 @@ piece or two. Start with one of the @ref{Templates},
and
add notes. If you need any notation that was not covered in the
tutorial, look at the Notation Reference, starting with
@ref{Basic notation}. If you want to write for an instrument
-ensemble which is not covered in the templates,
+ensemble that is not covered in the templates,
take a look at @ref{Extending the templates}.
Once you have written a few short pieces, read the rest of
the Learning Manual (chapte
patch: doc typo fixes/etc
Lilypond is very cool!
Here's a short patch that fixes a few documentation typos and also
clarifies a couple of minor points.
In the patch, I say that comments do not nest, but I didn't verify
this. If they do, this'll need correcting.
The other clarification tries to smooth out the comparison to other
languages. Technically, it's not the case, for example, that most
programming languages use { } to enclose expressions.
Regards,
Mike
From c367521fe65ff61c50dcb918ce35cf31613ccebf Mon Sep 17 00:00:00 2001
From: Michael Coleman <[EMAIL PROTECTED]>
Date: Wed, 27 Jun 2007 21:34:58 -0500
Subject: [PATCH] Fix doc typos/etc, plus a couple of clarifications.
---
Documentation/user/basic-notation.itely |2 +-
Documentation/user/instrument-notation.itely |2 +-
Documentation/user/tutorial.itely| 14 +++---
Documentation/user/tweaks.itely |4 ++--
4 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/Documentation/user/basic-notation.itely b/Documentation/user/basic-notation.itely
index 723bdf0..afcd338 100644
--- a/Documentation/user/basic-notation.itely
+++ b/Documentation/user/basic-notation.itely
@@ -1054,7 +1054,7 @@ These voices are all separate from the voice that contains the notes just
outside the @code{<< \\ >>} construct. This should be noted when making
changes at the voice level. This also means that slurs and ties cannot go
into or out of a @code{<< \\ >>} construct. Conversely, parallel voices
-from separate @code{<< \\ >>} constructs on the same staff are the the
+from separate @code{<< \\ >>} constructs on the same staff are the
same voice. Here is the same example, with different noteheads for each
voice. Note that the change to the note-head style in the main voice does
not affect
diff --git a/Documentation/user/instrument-notation.itely b/Documentation/user/instrument-notation.itely
index 28fa837..80c7883 100644
--- a/Documentation/user/instrument-notation.itely
+++ b/Documentation/user/instrument-notation.itely
@@ -4586,7 +4586,7 @@ figures below the notes, use
When using figured bass above the staff with extender lines and
@code{implicitBassFigures} the lines may become swapped around.
Maintaining order consistently will be impossible when multiple figures
-have overlapping extender lines. To avoid this problem, plese
+have overlapping extender lines. To avoid this problem, please
use @code{stacking-dir} on @code{BassFigureAlignment}.
diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index c54307d..5c8c2aa 100644
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -383,8 +383,8 @@ see @ref{Clef}.
@node Working on text files
@subsection Working on text files
-LilyPond input files are treated like files in most programming languages:
-they are case sensitive, white-space insensitive, expressions are
+LilyPond input files are similar to source files in many common programming languages.
+They are case sensitive, and white-space is generally equivalent. Expressions are
formed with curly braces @{ @}, and comments are denoted with @code{%} or
@[EMAIL PROTECTED] ... [EMAIL PROTECTED]
@@ -440,7 +440,7 @@ There are two types of comments. The percent symbol @samp{%}
introduces a line comment; anything after @samp{%} on that line is
ignored. A block comment marks a whole section of music
input as a comment. Anything that is enclosed in @[EMAIL PROTECTED] and @[EMAIL PROTECTED] is
-ignored. The following fragment shows possible uses for comments
+ignored. (Comments do not nest.) The following fragment shows possible uses for comments
@example
% notes for twinkle twinkle follow
@@ -572,7 +572,7 @@ a
@subheading Warning: key signatures and pitches
To determine whether to print an accidental, LilyPond examines the
-pitches and the key signature. The key signature only effects
+pitches and the key signature. The key signature only affects
the @emph{printed} accidentals, not the actual pitches! This is a
feature that often causes confusion to newcomers, so let us explain it
in more detail.
@@ -1463,12 +1463,12 @@ piece or two. Start with one of the @ref{Templates}, and
add notes. If you need any notation that was not covered in the
tutorial, look at the Notation Reference, starting with
@ref{Basic notation}. If you want to write for an instrument
-ensemble which is not covered in the templates,
+ensemble that is not covered in the templates,
take a look at @ref{Extending the templates}.
Once you have written a few short pieces, read the rest of
the Learning Manual (chapters 3-5). There's nothing wrong
-with reading them now, of course! However, the rest of the
+with reading it now, of course! However, the rest of the
Learning Manual assumes that you are familiar with
LilyPond input. You may wish to skim these chapters right
now, and come back to them after you have more experience.
@@ -1483,7 +1483,7 @@ examp
