Re: [PATCH] Spelling fixes
Stefan, On 21 January 2012 07:23, Stefan Weil s...@weilnetz.de wrote: Am 21.01.2012 00:10, schrieb Pavel Roskin: On Fri, 20 Jan 2012 17:58:47 +0100 Stefan Weils...@weilnetz.de wrote: Hi, tre my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. By the way, somebody please run codespell on the Lilypond sources: http://git.profusion.mobi/cgit.cgi/lucas/codespell/ Hi Pavel, that's what I did. I started with three patches, but as soon as I know that they are accepted, more will follow. Your two patches have been opened as http://code.google.com/p/lilypond/issues/detail?id=2237 http://code.google.com/p/lilypond/issues/detail?id=2238 The code is uploaded for review and comment to http://codereview.appspot.com/5562043 and http://codereview.appspot.com/5561053 I 'own' these issues but if you get reqests for changes you can just upload the changes to 'codereview' yourself (if you know how to do that) or you can attach any corrected patches to the code.google issues and I can re-submit them. The process is documented here: http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers (start at 'reviews' in this case) -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Spelling fixes
Stefan, On 21 January 2012 07:23, Stefan Weil s...@weilnetz.de wrote: Am 21.01.2012 00:10, schrieb Pavel Roskin: On Fri, 20 Jan 2012 17:58:47 +0100 Stefan Weils...@weilnetz.de wrote: Hi, tre my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. By the way, somebody please run codespell on the Lilypond sources: http://git.profusion.mobi/cgit.cgi/lucas/codespell/ Hi Pavel, that's what I did. I started with three patches, but as soon as I know that they are accepted, more will follow. http://code.google.com/p/lilypond/issues/detail?id=2237 (the texidoc corrections) Has been approved and pushed to our staging branch. It will be merged in to the master branch soon. Thanks for the patch. The other I am leaving the other for a more thorough review -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
[PATCH] Spelling fixes
Hi,
my last two patches were sent inline (with git send-email),
but I just learned that they should have been appended instead.
So here are both patches again. Both fix some spelling issues.
Kind regards,
Stefan Weil
From 808f92bccd5efff1348d614209d933da98f37ac2 Mon Sep 17 00:00:00 2001
From: Stefan Weil s...@weilnetz.de
Date: Thu, 19 Jan 2012 22:39:31 +0100
Subject: [PATCH] Fix spelling in input/regression/*.ly
accomodate - accommodate
adn - and
eigth - eighth
excercise - exercise
inbetween - between
occurence - occurrence
refered - referred
supressed - suppressed
Signed-off-by: Stefan Weil s...@weilnetz.de
---
input/regression/backend-excercise.ly |2 +-
input/regression/markup-scheme.ly |2 +-
input/regression/mozart-hrn3-rondo.ily |2 +-
input/regression/multi-measure-rest-text.ly |2 +-
input/regression/nested-fill-lines.ly |2 +-
input/regression/page-label.ly |2 +-
input/regression/rest-polyphonic-2.ly |2 +-
input/regression/spacing-short-notes.ly |2 +-
input/regression/tie-single.ly |2 +-
9 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/input/regression/backend-excercise.ly b/input/regression/backend-excercise.ly
index 0612002..ba4af11 100644
--- a/input/regression/backend-excercise.ly
+++ b/input/regression/backend-excercise.ly
@@ -1,5 +1,5 @@
\header {
- texidoc = Excercise all output functions
+ texidoc = Exercise all output functions
}
\version 2.14.0
diff --git a/input/regression/markup-scheme.ly b/input/regression/markup-scheme.ly
index fa71686..5dea41d 100644
--- a/input/regression/markup-scheme.ly
+++ b/input/regression/markup-scheme.ly
@@ -10,7 +10,7 @@
%{
-For maintenance reasons, we don't excercise the entire markup command set.
+For maintenance reasons, we don't exercise the entire markup command set.
%}
diff --git a/input/regression/mozart-hrn3-rondo.ily b/input/regression/mozart-hrn3-rondo.ily
index aeeb211..8e45355 100644
--- a/input/regression/mozart-hrn3-rondo.ily
+++ b/input/regression/mozart-hrn3-rondo.ily
@@ -130,7 +130,7 @@ rondo = \relative c' {
fis[ g gis]
a[ bes b]\!
- %% EB does the slur in the Rondo differently from the 1st adn 2nd time.
+ %% EB does the slur in the Rondo differently from the 1st and 2nd time.
%% why. Should check with MS.
\rondotheme
diff --git a/input/regression/multi-measure-rest-text.ly b/input/regression/multi-measure-rest-text.ly
index 2e2d432..73e1218 100644
--- a/input/regression/multi-measure-rest-text.ly
+++ b/input/regression/multi-measure-rest-text.ly
@@ -6,7 +6,7 @@
Texts may be added to the multi-measure rests.
By setting the appropriate @code{spacing-procedure}, we can make
-measures stretch to accomodate wide texts.
+measures stretch to accommodate wide texts.
diff --git a/input/regression/nested-fill-lines.ly b/input/regression/nested-fill-lines.ly
index f4236ea..011cc90 100644
--- a/input/regression/nested-fill-lines.ly
+++ b/input/regression/nested-fill-lines.ly
@@ -4,7 +4,7 @@
{
texidoc =
-Nested fill-lines should work properly. In this example, both occurences
+Nested fill-lines should work properly. In this example, both occurrences
of FOO should be centered.
diff --git a/input/regression/page-label.ly b/input/regression/page-label.ly
index 143d685..a369640 100644
--- a/input/regression/page-label.ly
+++ b/input/regression/page-label.ly
@@ -2,7 +2,7 @@
\header {
texidoc = Page labels may be placed inside music or at top-level,
-and refered to in markups.
+and referred to in markups.
}
#(set-default-paper-size a6)
diff --git a/input/regression/rest-polyphonic-2.ly b/input/regression/rest-polyphonic-2.ly
index 23af88f..e009dcf 100644
--- a/input/regression/rest-polyphonic-2.ly
+++ b/input/regression/rest-polyphonic-2.ly
@@ -3,7 +3,7 @@
texidoc = Rests avoid notes. Each rest is moved in the direction
of the stems in its voice. Rests may overlap other rests in voices
with the same stem direction, in which case a warning is given, but
-is supressed if the rest has a pitch.
+is suppressed if the rest has a pitch.
}
diff --git a/input/regression/spacing-short-notes.ly b/input/regression/spacing-short-notes.ly
index d05ef1d..47786b0 100644
--- a/input/regression/spacing-short-notes.ly
+++ b/input/regression/spacing-short-notes.ly
@@ -4,7 +4,7 @@
texidoc = Notes that are shorter than the common shortest note get a
space (i.e. without the space needed for the note) proportional to
-their duration. So, the 16th notes get 1/2 of the space of an eigth note.
+their duration. So, the 16th notes get 1/2 of the space of an eighth note.
The total distance for a 16th (which includes note head) is 3/4 of the
eighth note.
diff --git a/input/regression/tie-single.ly b/input/regression/tie-single.ly
index 899c927..f7b96fe 100644
--- a/input/regression/tie-single.ly
+++ b/input/regression/tie-single.ly
@@ -11,7 +11,7 @@
@item short ties
Re: [PATCH] Spelling fixes
On Fri, 20 Jan 2012 17:58:47 +0100 Stefan Weil s...@weilnetz.de wrote: Hi, my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. By the way, somebody please run codespell on the Lilypond sources: http://git.profusion.mobi/cgit.cgi/lucas/codespell/ It find so much stuff that perhaps somebody with commit access and good knowledge of the code could do it more effectively without bothering others. It's funny that codespell even found a mistake in German text (Probelm). There are some false positives, such as upto, portugues and \openin. Also, we probably don't want to fix old changelogs. -- Regards, Pavel Roskin ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Spelling fixes
Hello, On 20 January 2012 16:58, Stefan Weil s...@weilnetz.de wrote: Hi, my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. Kind regards, Stefan Weil I'd offer to manage these but I guess it is better handled by someone who understands the translation branches? -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Spelling fixes
2012/1/21 James pkx1...@gmail.com: Hello, On 20 January 2012 16:58, Stefan Weil s...@weilnetz.de wrote: Hi, my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. Kind regards, Stefan Weil I'd offer to manage these but I guess it is better handled by someone who understands the translation branches? These patches can be applied directly onto the staging branch. They only touch comments ant deprecated strings, or English texts whose translations don't need fixings. Translation branches explained: We have a single translation branch. Its name is lilypond/translation. Every often, any changes from master branch are merged on it. Translation changes are merged, in turn, onto the staging branch. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Spelling fixes
Am 21.01.2012 00:10, schrieb Pavel Roskin: On Fri, 20 Jan 2012 17:58:47 +0100 Stefan Weils...@weilnetz.de wrote: Hi, tre my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. By the way, somebody please run codespell on the Lilypond sources: http://git.profusion.mobi/cgit.cgi/lucas/codespell/ Hi Pavel, that's what I did. I started with three patches, but as soon as I know that they are accepted, more will follow. Cheers, Stefan ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
