Doc: Added \compoundMeter function to NR

Doc: Added \compoundMeter function to NR

Tracker 1776.

Added function to Polymetric Notation section removed old
snippets (which have been superceded by this function).

Also took the opportunity to make some minor grammatical changes
to make (hopefully) the other examples and their explanations
clearer.

Some style changes needed (used @subheading instead of @strong{})
Also removed other references to the snippet in the NR
and moved cindex entries to the new location.

[pkx166h, 2011-08-02 23:23:33]

Patch ready for review.

But also see

http://code.google.com/p/lilypond/issues/detail?id=1776#c6

as there are still some points I am not clear on on this function that may need
more doc additions.

[Janek Warchol, 2011-08-03 06:50:15]

I think the \compoundMeter description should be more detailed.

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1555: shown durations are multiplied by 3/5
(3/5 * 10/8 = 3/4).  It may be
I think these parentheses might be confusing.  One can think that the contents
of the parentheses are to be multiplied by the fraction before it.

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1638: \compoundMeter #'@var{(list of
numbers)}
the argument of \compoundMeter is a list of lists, not a list of numbers.  List
of numbers = #'(number number number ...) , list of lists = #'( (list) (list)
(list) ...) where each (list) is something like (number number number ...).
I think that the description should be overall more verbose, as this is easy to
be misunderstood.  See my comment in tracker issue
(http://code.google.com/p/lilypond/issues/detail?id=1776) for a detailed
explanation.

[Trevor Daniels, 2011-08-04 08:31:35]

Hi James
Needs a bit more work along the lines suggested by Janek.  This is quite a
tricky concept, and a little more explanation would help here (although maybe
not quite as verbose as Janek's helpful explanation - leave out the musical bits
:)  

Also, you can't just delete the unwanted snippets from the git tree - they'll
reappear at the next LSR update.  You'll need to delete them from
snippets/rhythms.snippet-list and change the entries in the LSR to remove them
from the docs.
Trevor

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1555: shown durations are multiplied by 3/5
(3/5 * 10/8 = 3/4).  It may be
On 2011/08/03 06:50:15, Janek Warchol wrote:
> I think these parentheses might be confusing.  One can think that the contents
of the parentheses are to be multiplied by the fraction before it.

The parentheses would be clear enough if we just reinsert "as" or "since" at
their start.

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1634: These can be easily created using the
@code{\compoundMeter} function.
drop "easily"

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1638: \compoundMeter #'@var{(list of
numbers)}
I agree.  First explain what a single list does, then move on to explain
multiple lists.

[Reinhold, 2011-08-04 11:12:21]

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1638: \compoundMeter #'@var{(list of
numbers)}
On 2011/08/03 06:50:15, Janek Warchol wrote:
> the argument of \compoundMeter is a list of lists, not a list of numbers.

Actually, it can be both. In the simple case, like (2+2+3)/8 (which is very
common in e.g. Serbian folk music), you only have one fraction with a sum in the
enumerator.

I would start with that "simpler" case of only one fraction and describe 
   \compoundMeter #'(2 3 3 8)
first. 
Then you can start from there and say that in the more complex case with more
fractions which are added, like 1/4 + 3/8, each fraction is expressed as above,
and all of them are put inside one list:
   \compoundMeter #'((1 4) (3 8))

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1638: \compoundMeter #'@var{(list of
numbers)}
BTW, what I would definitely mention here is that the automatic beaming and the
beam subdivisions are automatically derived from  the \compound meter. In
particular, if you have a measure of five eighth notes, 
   \compoundMeter #'(2 3 8)
will automatically beam them as 2 + 3 eighth notes, while
   \compoundMeter #'(3 2 8)
will automatically beam them as 3 + 2 eigth notes, and
   \compoundMeter #'(4 1 8)
will beam the first four and the print a single eigth note.

Speaking in more music theory terms: A compound meter does not only say how long
the measure is, but it also gives the information about the beat structure (the
"meter"), ie. which notes are slightly accented. That's why I didn't call it
\compoundTime, but \compoundMeter. Lilypond automatically uses that information,
too.

[pkx166h, 2011-08-04 21:56:35]

Second Draft. Hopefully I've covered everything without being too verbose or
talking through the code.

I also found some old 'scheme' code in the glossary and so updated that with the
new \compoundMeter function instead also removed another reference to the
snippet found in world.itely.

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1555: shown durations are multiplied by 3/5
(3/5 * 10/8 = 3/4).  It may be
On 2011/08/03 06:50:15, Janek Warchol wrote:
> I think these parentheses might be confusing.  One can think that the contents
> of the parentheses are to be multiplied by the fraction before it.

Only if you are a programmer :) it never even occurred to me to think of them
like that!

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1555: shown durations are multiplied by 3/5
(3/5 * 10/8 = 3/4).  It may be
On 2011/08/04 08:31:35, Trevor Daniels wrote:
> The parentheses would be clear enough if we just reinsert "as" or "since" at
> their start.

I used an 'en' dash. What do you think?

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1634: These can be easily created using the
@code{\compoundMeter} function.
On 2011/08/04 08:31:35, Trevor Daniels wrote:
> drop "easily"

Done.

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1638: \compoundMeter #'@var{(list of
numbers)}
On 2011/08/04 08:31:35, Trevor Daniels wrote:
> I agree.  First explain what a single list does, then move on to explain
> multiple lists.

Done.

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1638: \compoundMeter #'@var{(list of
numbers)}
On 2011/08/04 11:12:21, Reinhold wrote:
> On 2011/08/03 06:50:15, Janek Warchol wrote:
> > the argument of \compoundMeter is a list of lists, not a list of numbers.
> 
> Actually, it can be both. In the simple case, like (2+2+3)/8 (which is very
> common in e.g. Serbian folk music), you only have one fraction with a sum in
the
> enumerator.
> 
> I would start with that "simpler" case of only one fraction and describe 
>    \compoundMeter #'(2 3 3 8)
> first. 
> Then you can start from there and say that in the more complex case with more
> fractions which are added, like 1/4 + 3/8, each fraction is expressed as
above,
> and all of them are put inside one list:
>    \compoundMeter #'((1 4) (3 8))
> 

Done.

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1638: \compoundMeter #'@var{(list of
numbers)}
On 2011/08/04 11:12:21, Reinhold wrote:
> On 2011/08/03 06:50:15, Janek Warchol wrote:
> > the argument of \compoundMeter is a list of lists, not a list of numbers.
> 
> Actually, it can be both. In the simple case, like (2+2+3)/8 (which is very
> common in e.g. Serbian folk music), you only have one fraction with a sum in
the
> enumerator.
> 
> I would start with that "simpler" case of only one fraction and describe 
>    \compoundMeter #'(2 3 3 8)
> first. 
> Then you can start from there and say that in the more complex case with more
> fractions which are added, like 1/4 + 3/8, each fraction is expressed as
above,
> and all of them are put inside one list:
>    \compoundMeter #'((1 4) (3 8))
> 

Done.

http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.i...
Documentation/notation/rhythms.itely:1638: \compoundMeter #'@var{(list of
numbers)}
On 2011/08/04 11:12:21, Reinhold wrote:
> BTW, what I would definitely mention here is that the automatic beaming and
the
> beam subdivisions are automatically derived from  the \compound meter. In
> particular, if you have a measure of five eighth notes, 
>    \compoundMeter #'(2 3 8)
> will automatically beam them as 2 + 3 eighth notes, while
>    \compoundMeter #'(3 2 8)
> will automatically beam them as 3 + 2 eigth notes, and
>    \compoundMeter #'(4 1 8)
> will beam the first four and the print a single eigth note.
> 
> Speaking in more music theory terms: A compound meter does not only say how
long
> the measure is, but it also gives the information about the beat structure
(the
> "meter"), ie. which notes are slightly accented. That's why I didn't call it
> \compoundTime, but \compoundMeter. Lilypond automatically uses that
information,
> too.

That was a nice touch. Thanks, I have mentioned that.

[Janek Warchol, 2011-08-05 10:07:46]

2011/8/4  <reinhold.kainhofer@gmail.com>:
> I would definitely mention here that the automatic beaming
> and the beam subdivisions are automatically derived from  the \compound
> meter.

Are the subdivisions really used?  When i compile

{ \compoundMeter #'((2 3 4))  \repeat unfold 20 c'16 }

I get 8 sixteenths beamed together and then 12 sixteenths beamed
together (with no subdivisions), while i'd expect that every four
sixteenths there would be single beam insted of double beam (to be
precise, i'd expect a single beam between 4th&5th, 12th&13th and
16th&17th notes).
If this is unclear, i'll post an image when i'll get back to my
Lily-enabled computer.

> Speaking in more music theory terms: A compound meter does not only say
> how long the measure is, but it also gives the information about the
> beat structure (the "meter"), ie. which notes are slightly accented.
> That's why I didn't call it \compoundTime, but \compoundMeter. Lilypond
> automatically uses that information, too.

BTW, when i searched for "compound meter" on the web, virtually every
place i found said that compound meter is a meter in which beats are
not divided in two.  So, for example, 12/8 is a compound meter
(because it consists of 4 groups, three eights each).  Constructs like
(2+3)/4 are called additive meter, complex meter etc.  Are you sure
that compoundMeter is a appropriate name for this function?

cheers,
Janek

[Janek Warchol, 2011-08-05 11:02:38]

http://codereview.appspot.com/4837050/diff/9001/Documentation/music-glossary....
File Documentation/music-glossary.tely (right):

http://codereview.appspot.com/4837050/diff/9001/Documentation/music-glossary....
Documentation/music-glossary.tely:2114: \compoundMeter #'((3 8) (2 8) (4 8))
Nice catch!

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:1554: multiplied by 2/3 -- as 2/3 * 9/8 =
3/4 -- and in the third staff, the
either -- as ... -- or (as ...) is fine imo.

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:1642: single list of numbers, where each
number in the @code{#'@var{(list)}}
After some consideration i think that we should abandon explaining the fact that
\compoundMeter #'(2 2 2 8) == \compoundMeter #'((2 2 2 8)).  Typing two braces
more won't hurt anyone, while explaining how it works seems to be either
confusing ("was it a list of numbers or a list of lists?") or too long.

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:1644: listed is the @q{denominator}.
I find it a bit confusing: is each number a numerator or not?
I'd write it like that: the last number in the list is the denominator,
remaining numbers are written in numerator.
I find the description used in the regtest
(http://lilypond.org/doc/v2.15/input/regression/58/lily-ae87e9d8.ly) the most
clear and precise, but it uses mathematical terminology (fraction, summand)
which will probably cause problems for some users :(

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:1653: More complex meters can be
constructed using a @q{list of lists}.
I'd write "more lists as arguments" instead of "a @q{list of lists}"

[pkx166h, 2011-08-07 08:22:25]

On 2011/08/05 10:07:46, Janek Warchol wrote:
> 2011/8/4  <reinhold.kainhofer@gmail.com>:
> > I would definitely mention here that the automatic beaming
> > and the beam subdivisions are automatically derived from &nbsp;the \compound
> > meter.
> 
> Are the subdivisions really used?  
...

I have removed the original two paragraphs from the patch and added a simple
single sentence that gets the idea across that auto beam values will be
'adjusted' according to the new values set.

I think that is good enough for most users. They can figure it out for
themselves with the examples, and if they have questions for specific beaming
patterns they can ask the lists.

[pkx166h, 2011-08-07 08:22:47]

New Draft.

Thanks

James

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:1554: multiplied by 2/3 -- as 2/3 * 9/8 =
3/4 -- and in the third staff, the
On 2011/08/05 11:02:38, Janek Warchol wrote:
> either -- as ... -- or (as ...) is fine imo.

Done.

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:1642: single list of numbers, where each
number in the @code{#'@var{(list)}}
On 2011/08/05 11:02:38, Janek Warchol wrote:
> After some consideration i think that we should abandon explaining the fact
that
> \compoundMeter #'(2 2 2 8) == \compoundMeter #'((2 2 2 8)).  Typing two braces
> more won't hurt anyone, while explaining how it works seems to be either
> confusing ("was it a list of numbers or a list of lists?") or too long.

Done.

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:1644: listed is the @q{denominator}.
On 2011/08/05 11:02:38, Janek Warchol wrote:
> I find it a bit confusing: is each number a numerator or not?
> I'd write it like that: the last number in the list is the denominator,
> remaining numbers are written in numerator.
> I find the description used in the regtest
> (http://lilypond.org/doc/v2.15/input/regression/58/lily-ae87e9d8.ly) the most
> clear and precise, but it uses mathematical terminology (fraction, summand)
> which will probably cause problems for some users :(

Yes you are right, I was never comfortable with it, so looking at Wikipedia and
Yahoo, I have settled on 'Beat' and 'Note Value' which seems to be more
generally understood.

http://codereview.appspot.com/4837050/diff/9001/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:1653: More complex meters can be
constructed using a @q{list of lists}.
On 2011/08/05 11:02:38, Janek Warchol wrote:
> I'd write "more lists as arguments" instead of "a @q{list of lists}"

Done.

[Janek Warchol, 2011-08-07 12:30:06]

overall LGTM

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1643: come before it indicate the beat
value.
Funny, i'd say that "beat value" and "note value" mean the same...
I'd write "indicate the number of beats."  However, this results in excessive
repetition of word "number".

[Trevor Daniels, 2011-08-07 15:24:44]

Almost there - a couple of comments ...

http://codereview.appspot.com/4837050/diff/15001/Documentation/music-glossary...
File Documentation/music-glossary.tely (right):

http://codereview.appspot.com/4837050/diff/15001/Documentation/music-glossary...
Documentation/music-glossary.tely:2114: \compoundMeter #'((3 8) (2 8) (4 8))
\compoundMeter #'((3 8) (2 8) (3 8))

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1546: @code{\scaleDurations} function in
each staff to the common time
... function to scale the durations of the notes in each staff ...

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1555: shown durations are multiplied by 3/5
-- as 3/5 * 10/8 = 3/4.  It may be
I prefer brackets to show these parenthetical comments:
(because 2/3 * 9/8 = 3/4)

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1643: come before it indicate the beat
value.
I think it's clearer to say top and bottom of the time signature: 
... last number in the list is placed at the bottom of the time signature and
the numbers that come before it are placed as a summation at the top.  All but
the last number indicate the stress groupings and sum to the duration of the
measure.

[pkx166h, 2011-08-07 20:33:38]

New Draft.

Before I push this (and as Neil has just done an LSR update) do I still need to
run makelsr.py before applying this patch once it has been approved? 

I have removed one snippet from both dirs (snippets/new and snippets).

I'll get someone to remove the snippet from the LSR too.

http://codereview.appspot.com/4837050/diff/15001/Documentation/music-glossary...
File Documentation/music-glossary.tely (right):

http://codereview.appspot.com/4837050/diff/15001/Documentation/music-glossary...
Documentation/music-glossary.tely:2114: \compoundMeter #'((3 8) (2 8) (4 8))
On 2011/08/07 15:24:44, Trevor Daniels wrote:
> \compoundMeter #'((3 8) (2 8) (3 8))

Done.

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1546: @code{\scaleDurations} function in
each staff to the common time
On 2011/08/07 15:24:44, Trevor Daniels wrote:
> ... function to scale the durations of the notes in each staff ...

Done.

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1555: shown durations are multiplied by 3/5
-- as 3/5 * 10/8 = 3/4.  It may be
On 2011/08/07 15:24:44, Trevor Daniels wrote:
> I prefer brackets to show these parenthetical comments:
> (because 2/3 * 9/8 = 3/4)

I have no strong feelings either way. So Done.

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1643: come before it indicate the beat
value.
On 2011/08/07 15:24:44, Trevor Daniels wrote:
> I think it's clearer to say top and bottom of the time signature: 
> ... last number in the list is placed at the bottom of the time signature and
> the numbers that come before it are placed as a summation at the top.  All but
> the last number indicate the stress groupings and sum to the duration of the
> measure.

hmmm..I still think that is a bit awkward - I'm not sure 'summation' comes over
well for non-native English speakers looking at the NR. I also don't feel the
last sentence is necessary if the @lilyponds are good enough (that and we talk
about beaming anyway later). See what you think of my very simple change.

[Neil Puttock, 2011-08-07 21:47:48]

On 7 August 2011 21:33,  <pkx166h@gmail.com> wrote:

> Before I push this (and as Neil has just done an LSR update) do I still
> need to run makelsr.py before applying this patch once it has been
> approved?

Nope.

> I have removed one snippet from both dirs (snippets/new and snippets).

Don't forget to remove the translated texidocs too.

> I'll get someone to remove the snippet from the LSR too.

I'd leave it until we actually have an update*, though I have already
removed the `doc' tag to prevent the snippet reappearing with the next
LSR update.

* you could argue that we should leave it in case users aren't
prepared to update to the latest stable version

Cheers,
Neil

[Graham Percival (old account), 2011-08-08 00:38:50]

LGTM

[Janek Warchol, 2011-08-08 07:32:47]

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1555: shown durations are multiplied by 3/5
-- as 3/5 * 10/8 = 3/4.  It may be
On 2011/08/07 20:33:38, J_lowe wrote:
> On 2011/08/07 15:24:44, Trevor Daniels wrote:
> > I prefer brackets to show these parenthetical comments:
> > (because 2/3 * 9/8 = 3/4)
> 
> I have no strong feelings either way. So Done.

I like this.

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1643: come before it indicate the beat
value.
On 2011/08/07 20:33:38, J_lowe wrote:
> On 2011/08/07 15:24:44, Trevor Daniels wrote:
> > I think it's clearer to say top and bottom of the time signature: 
> > ... last number in the list is placed at the bottom of the time signature
and
> > the numbers that come before it are placed as a summation at the top.  All
but
> > the last number indicate the stress groupings and sum to the duration of the
> > measure.
> 
> hmmm..I still think that is a bit awkward - I'm not sure 'summation' comes
over
> well for non-native English speakers looking at the NR. I also don't feel the
> last sentence is necessary if the @lilyponds are good enough (that and we talk
> about beaming anyway later). See what you think of my very simple change.

I agree that the last sentence suggested by Treveor isn't necassary.
I think that if we change "summation" to "sum" in his proposal, it will be
understood by people.  In Wiktionary i see that word for sum is similar in many
languages.

http://codereview.appspot.com/4837050/diff/14002/Documentation/notation/rhyth...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/14002/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1643: before it, the bottom numbers.
It's the other way round - Last number goes to the bottom.

[pkx166h, 2011-08-08 21:40:23]

Draft 5 - removed all translation docs with this snippet in it too (for when it
is removed from LSR).



have at it.

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/15001/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1643: come before it indicate the beat
value.
On 2011/08/08 07:32:48, Janek Warchol wrote:
> On 2011/08/07 20:33:38, J_lowe wrote:
> > On 2011/08/07 15:24:44, Trevor Daniels wrote:
> > > I think it's clearer to say top and bottom of the time signature: 
> > > ... last number in the list is placed at the bottom of the time signature
> and
> > > the numbers that come before it are placed as a summation at the top.  All
> but
> > > the last number indicate the stress groupings and sum to the duration of
the
> > > measure.
> > 
> > hmmm..I still think that is a bit awkward - I'm not sure 'summation' comes
> over
> > well for non-native English speakers looking at the NR. I also don't feel
the
> > last sentence is necessary if the @lilyponds are good enough (that and we
talk
> > about beaming anyway later). See what you think of my very simple change.
> 
> I agree that the last sentence suggested by Treveor isn't necassary.
> I think that if we change "summation" to "sum" in his proposal, it will be
> understood by people.  In Wiktionary i see that word for sum is similar in
many
> languages.

Well I haven't made any changes since my last edit. See if this is ok.

http://codereview.appspot.com/4837050/diff/14002/Documentation/notation/rhyth...
File Documentation/notation/rhythms.itely (right):

http://codereview.appspot.com/4837050/diff/14002/Documentation/notation/rhyth...
Documentation/notation/rhythms.itely:1643: before it, the bottom numbers.
On 2011/08/08 07:32:48, Janek Warchol wrote:
> It's the other way round - Last number goes to the bottom.

Done.

[Trevor Daniels, 2011-08-08 22:09:09]

LGTM
Although I'm not sure about editing the other language files.  Best wait for
Francisco to comment.

[Neil Puttock, 2011-08-19 21:13:49]

LGTM.

[janek, 2011-08-22 19:08:38]

Just to make things clear,
LGTM
(and sorry for my long absence)
Thanks for your work and your patience, James!

Janek

[pkx166h, 2011-08-24 21:33:16]

On 2011/08/08 22:09:09, Trevor Daniels wrote:
> LGTM
> Although I'm not sure about editing the other language files.  Best wait for
> Francisco to comment.

Francisco, can you tell me if this patch is ok to go as I have touched some of
the translated docs to remove this snippet.

Thanks

[pkx166h, 2011-08-24 21:33:34]

On 2011/08/08 22:09:09, Trevor Daniels wrote:
> LGTM
> Although I'm not sure about editing the other language files.  Best wait for
> Francisco to comment.

Francisco, can you tell me if this patch is ok to go as I have touched some of
the translated docs to remove this snippet.

Thank

[janek, 2011-09-05 20:54:39]

James,
i see this patch is quite orphaned despite being very nice and ready-to-go. 
Shall i push it for you?

cheers,
Janek

[pkx166h, 2011-09-06 08:14:19]

Janek

On Mon, Sep 5, 2011 at 9:54 PM, <janek.lilypond@gmail.com> wrote:

> James,
> i see this patch is quite orphaned despite being very nice and
> ready-to-go.  Shall i push it for you?
>
> cheers,
> Janek
>
>
http://codereview.appspot.com/**4837050/<http://codereview.appspot.com/4837050/>
>

Thanks for the offer, that's nice of you, however the patch no longer
applies to current master.

:/

I need to make a new patch. It's because of a combination of things; I was
(and am still) waiting on Francisco to know if I can remove the old compound
meter examples in the snippet refs in the various translation tely files (I
have asked him for a review a couple of times and emailed directly but had
no response) and then I was away for a couple of weeks and the patched files
are now out of sync.

I'll try to get a new patch set uploaded asap. It's not forgotten (I also
let Colin know off list because he had said I could push it too), don't
worry.

-- 
--

James

[pacovila, 2011-09-09 23:36:12]

Hello all,

2011/9/6 Peekay Ex <pkx166h@gmail.com>:
> I need to make a new patch. It's because of a combination of things; I was
> (and am still) waiting on Francisco to know if I can remove the old compound
> meter examples in the snippet refs in the various translation tely files (I
> have asked him for a review a couple of times and emailed directly but had
> no response) and then I was away for a couple of weeks and the patched files
> are now out of sync.

Hello. I've found this in my recycle bin:

Re: Doc: Added \compoundMeter function to NR (issue 4837050)
http://lists.gnu.org/archive/html/lilypond-devel/2011-08/msg01029.html

Message headers include [Reply_to:] to 9 addresses, [To:] to 6
addresses, [Cc:] to 2 more addresses and none of them all is my own
address.  So, I am very sorry to say, it seems you forgot to cc me.  I
read and delete many messages based on the subject line and whether
the message is for me and this didn't, despite of including the word
Francisco in the body.  Sorry for that!

This has been a Very Bad Year (TM) for me and I hope things will
improve slowly from now on.  Thanks for your interest.

As for Rietveld 4837050, I can not oppose to removing references to a
non-existant snippet from translated docs. Thanks for this useful
work.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

[pkx166h, 2011-09-11 08:05:26]

New patch uploaded with corrected snippet edit

[Graham Percival (old account), 2011-09-11 14:28:43]

LGTM, not tested compile but I trust James.

[janek, 2011-09-11 19:42:04]

LGTM

[Neil Puttock, 2011-09-12 11:06:30]

LGTM.

[pkx166h, 2011-09-15 19:36:20]

Pushed as

c358ec6f8ed8f31b5fa1d97da6a2284b3759bdfd

Closing issue.