Use @dots{} instead of ... in notation manual where appropriate

Use @dots{} instead of ... in notation manual where appropriate

This uses a typographically preferable variant, and also may render
better in Info format in some circumstances.

[Jean-Charles, 2013-06-04 18:17:21]

There is also

notation/rhythms.itely:2320:If a manual beam is specified with @code{[..]} set
the beam

For the rest, LGTM

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/changing...
File Documentation/notation/changing-defaults.itely (right):

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/changing...
Documentation/notation/changing-defaults.itely:678: @emph{..music..}
@emph{@dots{}music@dots{}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:101: delimited by @code{%@{ .. %@}} may be
placed anywhere within an
delimited by @code{%@{@dots{}%@}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:136: @var{..music..}
@var{@dots{}music@dots{}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:144: @var{..text..}
@var{@dots{}text@dots{}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:155: @var{..}
@var{@dots{}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:158: @var{..}
@var{@dots{}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:161: @var{..}
@var{@dots{}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:185: ..text of second verse..
@dots{}text of second verse@dots{}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:188: ..text of third verse..
@dots{}text of third verse@dots{}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:484: A multi-line comment delimited by
@code{%@{ .. %@}}.
delimited by @code{%@{ @dots{} %@}}.

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:2964: @var{..music..}
@var{@dots{}music@dots{}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:2965: \layout @{ .. @}
\layout @{ @dots{} @}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:2968: \unfoldRepeats @var{..music..}
\unfoldRepeats @var{@dots{}music@dots{}}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/input.it...
Documentation/notation/input.itely:2969: \midi @{ .. @}
\midi @{ @dots{} @}

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultan...
File Documentation/notation/simultaneous.itely (right):

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultan...
Documentation/notation/simultaneous.itely:49: @funindex <...>
@funindex <@dots{}>

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultan...
Documentation/notation/simultaneous.itely:382: @funindex \voiceOne ...
\voiceFour
@funindex \voiceOne @dots{} \voiceFour

[dak, 2013-06-04 18:30:59]

Also treat instances of ..

[dak, 2013-06-04 18:33:41]

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultan...
File Documentation/notation/simultaneous.itely (right):

https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultan...
Documentation/notation/simultaneous.itely:49: @funindex <...>
On 2013/06/04 18:17:21, Jean-Charles wrote:
> @funindex <@dots{}>

No, the index is something that one looks literally for in Info files.  So it
should not contain Texinfo sequences.

[Jean-Charles, 2013-06-04 18:36:06]

On 2013/06/04 18:33:41, dak wrote:
>
https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultan...
> Documentation/notation/simultaneous.itely:49: @funindex <...>
> On 2013/06/04 18:17:21, Jean-Charles wrote:
> > @funindex <@dots{}>
> 
> No, the index is something that one looks literally for in Info files.  So it
> should not contain Texinfo sequences.

OK, sorry.

[dak, 2013-06-05 10:45:26]

lilyfan@orange.fr writes:

> There is also
>
> notation/rhythms.itely:2320:If a manual beam is specified with
> @code{[..]} set the beam

Oh.  That happens when you do search and replace on ... only.

-- 
David Kastrup

[Graham Percival, 2013-06-06 21:31:40]

I find ... easier to read in texinfo source rather than @dots{}, but oh well.  I
won't object to the patch.

[dak, 2013-06-06 23:40:55]

On 2013/06/06 21:31:40, Graham Percival wrote:
> I find ... easier to read in texinfo source rather than @dots{}, but oh well. 
I
> won't object to the patch.

Well, you'll see that I did not change any ... inside of a comment or @ignore
section.  Which is where ... is only in the Texinfo source.  So where _only_
source readability is concerned, I'm in concord with your desire.

But Texinfo is not a markdown language.  It is not intended as the normal form
of reading a document.  The readability of the target format takes priority.  I
have to admit that the actual motivation was Info getting confused about ... in
connection with a cross reference.  But the change nevertheless makes sense as
it results in visual consistency.