Changes from LSR doc run

A huge patch which is generated from a makeLSR run from the docs tarball downloaded from the LSR on 20 July.  Note that almost all changes are makeLSR updating the LSR address and changing the version to 2.18.0.  I'm not sure why it changes the version, but it seems the default when updating from the tarball.  There are a few other changes, which are changes that one or other LSR author has made since the last import.

[PhilEHolmes, 2014-07-20 14:59:45]

Corrected patch

[PhilEHolmes, 2014-07-20 15:06:20]

Please review.

[Jean-Charles, 2014-07-20 15:28:13]

I just picked one file, but there might be some other occurrences of such
"things".

https://codereview.appspot.com/116040043/diff/20001/Documentation/snippets/an...
File
Documentation/snippets/ancient-notation-template----modern-transcription-of-mensural-music.ly
(right):

https://codereview.appspot.com/116040043/diff/20001/Documentation/snippets/an...
Documentation/snippets/ancient-notation-template----modern-transcription-of-mensural-music.ly:88:
\once \once \hide NoteHead c'1 |
Why this doubled "\once"?

https://codereview.appspot.com/116040043/diff/20001/Documentation/snippets/an...
Documentation/snippets/ancient-notation-template----modern-transcription-of-mensural-music.ly:124:
\once \once \hide NoteHead g1 |
idem

https://codereview.appspot.com/116040043/diff/20001/Documentation/snippets/an...
Documentation/snippets/ancient-notation-template----modern-transcription-of-mensural-music.ly:160:
\once \once \hide NoteHead e'1 |
idem

https://codereview.appspot.com/116040043/diff/20001/Documentation/snippets/an...
Documentation/snippets/ancient-notation-template----modern-transcription-of-mensural-music.ly:192:
\once \once \hide NoteHead e1 |
idem

[PhilEHolmes, 2014-07-20 15:35:34]

Adds new files from LSR

[email_philholmes.net, 2014-07-20 15:45:14]

----- Original Message ----- 
From: <lilyfan@orange.fr>
To: <PhilEHolmes@googlemail.com>
Cc: <lilypond-devel@gnu.org>; <reply@codereview-hr.appspotmail.com>
Sent: Sunday, July 20, 2014 4:28 PM
Subject: Re: Changes from LSR doc run (issue 116040043 by 
PhilEHolmes@googlemail.com)


>I just picked one file, but there might be some other occurrences of
> such "things".
>
>
>
https://codereview.appspot.com/116040043/diff/20001/Documentation/snippets/an...
> File
>
Documentation/snippets/ancient-notation-template----modern-transcription-of-mensural-music.ly
> (right):
>
>
https://codereview.appspot.com/116040043/diff/20001/Documentation/snippets/an...
>
Documentation/snippets/ancient-notation-template----modern-transcription-of-mensural-music.ly:88:
> \once \once \hide NoteHead c'1 |
> Why this doubled "\once"?

Copy and paste error.  Unfortunately it's not trivial to correct "properly" 
within this patch.  I've corrected the file in the LSR and this will 
therefore be corrected when I next run makelsr from the tarball.  That will 
need to be a new patch, because I've also done work on snippets/new in the 
interim.  I think we can live with a duplicate \once in the docs for a 
couple of days.

> https://codereview.appspot.com/116040043/

--
Phil Holmes 

[Jean-Charles, 2014-07-20 15:58:11]

On 2014/07/20 15:45:14, email_philholmes.net wrote:
> […]
>
Documentation/snippets/ancient-notation-template----modern-transcription-of-mensural-music.ly:88:
> > \once \once \hide NoteHead c'1 |
> > Why this doubled "\once"?
> 
> Copy and paste error.  Unfortunately it's not trivial to correct "properly" 
> within this patch.  I've corrected the file in the LSR and this will 
> therefore be corrected when I next run makelsr from the tarball.  That will 
> need to be a new patch, because I've also done work on snippets/new in the 
> interim.  I think we can live with a duplicate \once in the docs for a 
> couple of days.
> 

As I cannot do any serious work because of a stormy weather (already 3 power
breakages),
I'm reviewing each file, and let you know if I find something else…

Cheers.

[dak, 2014-07-20 16:37:01]

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ad...
File
Documentation/snippets/adding-indicators-to-staves-which-get-split-after-a-break.ly
(right):

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ad...
Documentation/snippets/adding-indicators-to-staves-which-get-split-after-a-break.ly:22:
%{ Original snippet :
An outcommented "original snippet"?  If the original snippet is of separate
value, it should be a separate snippet.

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ad...
Documentation/snippets/adding-indicators-to-staves-which-get-split-after-a-break.ly:136:
%%%%%%%%%%%%%%%%%%%%%%% ATTENTION %%%%%%%%%%%%%%%%%%%%%%%%
Big block comments in French?

In this form I'd lean towards removing the snippet from the import list if
that's feasible.

[mail_philholmes.net, 2014-07-20 16:49:33]

----- Original Message ----- 
From: <dak@gnu.org>
To: <PhilEHolmes@googlemail.com>; <lilyfan@orange.fr>; 
<email@philholmes.net>
Cc: <reply@codereview-hr.appspotmail.com>; <lilypond-devel@gnu.org>
Sent: Sunday, July 20, 2014 5:37 PM
Subject: Re: Changes from LSR doc run (issue 116040043 
byPhilEHolmes@googlemail.com)


>
>
https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ad...
> File
>
Documentation/snippets/adding-indicators-to-staves-which-get-split-after-a-break.ly
> (right):
>
>
https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ad...
>
Documentation/snippets/adding-indicators-to-staves-which-get-split-after-a-break.ly:22:
> %{ Original snippet :
> An outcommented "original snippet"?  If the original snippet is of
> separate value, it should be a separate snippet.
>
>
https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ad...
>
Documentation/snippets/adding-indicators-to-staves-which-get-split-after-a-break.ly:136:
> %%%%%%%%%%%%%%%%%%%%%%% ATTENTION %%%%%%%%%%%%%%%%%%%%%%%%
> Big block comments in French?
>
> In this form I'd lean towards removing the snippet from the import list
> if that's feasible.
>
> https://codereview.appspot.com/116040043/

It is, but as a singer, I find that this is a valuable snippet.  I'll tidy 
it up in the LSR, so (as with the previous comment) I can't fix this patch, 
but will fix the snippet in a following patch.

--
Phil Holmes 

[Jean-Charles, 2014-07-20 17:24:44]

Good job! Thanks!

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ed...
File Documentation/snippets/editorial-headword.ly (right):

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ed...
Documentation/snippets/editorial-headword.ly:22: %%
http://lsr.dsi.unimi.it/LSR/Snippet?id=627
should read lsr.di.unimi

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/pi...
File Documentation/snippets/piano-template-simple.ly (right):

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/pi...
Documentation/snippets/piano-template-simple.ly:19: %%
http://lsr.dsi.unimi.it/LSR/Item?id=354
should read lsr.di.unimi

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/pr...
File
Documentation/snippets/printing-a-repeat-sign-at-the-beginning-of-a-piece.ly
(right):

https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/pr...
Documentation/snippets/printing-a-repeat-sign-at-the-beginning-of-a-piece.ly:29:
% A <code>|:</code> bar line can be printed at the beginning of a piece, by
overriding the relevant property:
A @code{|:}

[Jean-Charles, 2014-07-20 17:36:52]

On 2014/07/20 16:49:33, mail_philholmes.net wrote:
> ----- Original Message ----- 
> From: <mailto:dak@gnu.org>
>
https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ad...
> > File
> >
>
Documentation/snippets/adding-indicators-to-staves-which-get-split-after-a-break.ly
> > (right):
> >
>
https://codereview.appspot.com/116040043/diff/30001/Documentation/snippets/ad...
> >
>
Documentation/snippets/adding-indicators-to-staves-which-get-split-after-a-break.ly:136:
> > %%%%%%%%%%%%%%%%%%%%%%% ATTENTION %%%%%%%%%%%%%%%%%%%%%%%%
> > Big block comments in French?
> >
> > In this form I'd lean towards removing the snippet from the import list
> > if that's feasible.
> >
> 
> It is, but as a singer, I find that this is a valuable snippet.  I'll tidy 
> it up in the LSR, so (as with the previous comment) I can't fix this patch, 
> but will fix the snippet in a following patch.
> 

Either ping Pierre to update this warning and word it in English (X-translation
to be adapted according to the key signature).

[PhilEHolmes, 2014-07-23 08:31:26]

Tackles previous comments; some snippets/new deleted

[PhilEHolmes, 2014-07-24 14:19:16]

Further updates in LSR