Re: Make documentation reflect presence of \tuplet (issue 7220052)

[dak]

Reviewers: Keith,

Message:
On 2013/01/29 04:47:13, Keith wrote:
> Looks great.

> You can simplify the version in changes.  The two tuplets sharing
share one beam
> catches the eye, but that was not the change.

Right.  This was a cut&paste job from the notation manual where the
intent was to _also_ illustrate that beaming and tuplet bracketing are
not necessarily the same.  But you are quite correct that this
particular lesson is not part of the changes.

> I wrote a version below imagining
> a reader who has forgotten that the fraction in \times is backwards,
and didn't
> yet notice that LilyPond commands can have optional arguments. Use
what you
> like.

I'll use a slightly edited version.  It does not make sense to use
@code{t/n} along with @var{t} since @var uses a different font and even
uppercasing in info files.  As a mathematician, I am not really enthused
with "reverse order in the fraction" as a description, but then the
whole last sentence warrants rewriting.

If you consider that description better than the original, you might
want to look over the entries in learning and notation.  The original
entries for \times very much focused on explaining things in a way and
order that makes the "fraction order" choice appear less strange.
Rewriting this felt somewhat awkward, so I might not have arrived at the
best solution.

Description:
Make documentation reflect presence of \tuplet

This is a followup issue to the changes introduced by issue 3095.

Please review this at https://codereview.appspot.com/7220052/

Affected files:
  M Documentation/changes.tely
  M Documentation/contributor/administration.itexi
  M Documentation/learning/common-notation.itely
  M Documentation/music-glossary.tely
  M Documentation/notation/rhythms.itely
  M Documentation/notation/simultaneous.itely
  A + Documentation/snippets/new/changing-the-tuplet-number.ly
  A  
Documentation/snippets/new/entering-several-tuplets-using-only-one--times-command.ly