Changes .tex files to get rid of warning

These files used what appears to be a deprecated syntax to invoke lilypond-book, resulting in these warnings:

lilypond-book.py: warning: deprecated ly-option used: 11pt=None
lilypond-book.py: warning: compatibility mode translation: staffsize=11

Applying these changes gets rid of those errors in make doc.

[PhilEHolmes, 2012-04-01 12:32:26]

Please review

[Graham Percival, 2012-04-01 13:23:05]

The .latex file just says "upload in progress".  Could you add it to the
exceptions (like .scm and .ps) as discussed somewhere in the CG?

Assuming that the change to the .latex file is just like the .lytex ones, please
push the whole thing directly to staging.
(I'd still like the .latex extension to be added to the exceptions, and could
you please push that change to the CG directly to staging as well)

[email_philholmes.net, 2012-04-01 14:16:57]

----- Original Message ----- 
From: <graham@percival-music.ca>
To: <PhilEHolmes@googlemail.com>; <julien.rioux@gmail.com>; <dak@gnu.org>
Cc: <lilypond-devel@gnu.org>; <reply@codereview-hr.appspotmail.com>
Sent: Sunday, April 01, 2012 2:23 PM
Subject: Re: Changes .tex files to get rid of warning (issue 5976055)


> The .latex file just says "upload in progress".  Could you add it to the
> exceptions (like .scm and .ps) as discussed somewhere in the CG?
>
> Assuming that the change to the .latex file is just like the .lytex
> ones, please push the whole thing directly to staging.
> (I'd still like the .latex extension to be added to the exceptions, and
> could you please push that change to the CG directly to staging as well)
>
> http://codereview.appspot.com/5976055/

It looked fine on Rietveld when I looked, and I couldn't find the exceptions 
bit in the CG, so it's pushed to staging as is.

--
Phil Holmes

[Graham Percival, 2012-04-01 16:09:53]

On Sun, Apr 01, 2012 at 03:16:52PM +0100, Phil Holmes wrote:
> It looked fine on Rietveld when I looked, and I couldn't find the
> exceptions bit in the CG, so it's pushed to staging as is.

Oops, we were smarter than I thought -- the exceptions are built
into git-cl precisely to avoid problems of people having to look
them up in the CG.

I've just pushed the .latex thing to the git-cl repo, so no futher
action is necessary.

- Graham

[Julien Rioux, 2012-04-02 08:12:40]

On Sun, Apr 1, 2012 at 2:32 PM,  <PhilEHolmes@googlemail.com> wrote:
> Reviewers: Julien Rioux, Graham Percival, dak,
>
> Message:
> Please review
>
> Description:
> These files used what appears to be a deprecated syntax to invoke
> lilypond-book, resulting in these warnings:
>
> lilypond-book.py: warning: deprecated ly-option used: 11pt=None
> lilypond-book.py: warning: compatibility mode translation: staffsize=11
>
> Applying these changes gets rid of those errors in make doc.
>
> Please review this at http://codereview.appspot.com/5976055/
>
> Affected files:
>  Documentation/usage/latex-lilypond-example.latex
>  M input/regression/lilypond-book/tex-comments.lytex
>  M input/regression/lilypond-book/tex-compatibility-mode.lytex
>  M input/regression/lilypond-book/tex-lilypond-inside-itemize.lytex
>  M input/regression/lilypond-book/tex-lilypond-inside-table.lytex
>
>
> Index: input/regression/lilypond-book/tex-compatibility-mode.lytex
> diff --git a/input/regression/lilypond-book/tex-compatibility-mode.lytex
> b/input/regression/lilypond-book/tex-compatibility-mode.lytex
> index
>
aab288e7b3504e235b72706b45e27688cade59ca..933b7ec4fd7d82fbcffd231baf0ded51d8cc2c0e
> 100644
> --- a/input/regression/lilypond-book/tex-compatibility-mode.lytex
> +++ b/input/regression/lilypond-book/tex-compatibility-mode.lytex
> @@ -5,6 +5,6 @@
>
>  A snippet with a deprecated option, triggering compatibility mode:
>
> -\lilypond[11pt,fragment]{c' e' g'}
> +\lilypond[staffsize=11,fragment]{c' e' g'}
>
>  \end{document}

This change to tex-compatibility-mode.tex makes no sense. The whole
point of this file is to test that deprecated options are still
supported.
--
Julien

[email_philholmes.net, 2012-04-02 09:11:08]

----- Original Message ----- 
From: "Julien Rioux" <julien.rioux@gmail.com>
To: <PhilEHolmes@googlemail.com>; <julien.rioux@gmail.com>; 
<graham@percival-music.ca>; <dak@gnu.org>; <lilypond-devel@gnu.org>; 
<reply@codereview-hr.appspotmail.com>
> > A snippet with a deprecated option, triggering compatibility mode:
> >
> > -\lilypond[11pt,fragment]{c' e' g'}
> > +\lilypond[staffsize=11,fragment]{c' e' g'}
> >
> > \end{document}
>
> This change to tex-compatibility-mode.tex makes no sense. The whole
> point of this file is to test that deprecated options are still
> supported.
> --
> Julien

Excellent catch - thanks, Julien.  I was in auto-correct mode.  How do you 
suggest we correct this?  I doubt we want this warning displayed. 
run-and-check?

--
Phil Holmes

[Julien Rioux, 2012-04-02 10:22:57]

On Mon, Apr 2, 2012 at 11:11 AM, Phil Holmes <email@philholmes.net> wrote:
> ----- Original Message ----- From: "Julien Rioux" <julien.rioux@gmail.com>
> To: <PhilEHolmes@googlemail.com>; <julien.rioux@gmail.com>;
> <graham@percival-music.ca>; <dak@gnu.org>; <lilypond-devel@gnu.org>;
> <reply@codereview-hr.appspotmail.com>
>
>> > A snippet with a deprecated option, triggering compatibility mode:
>> >
>> > -\lilypond[11pt,fragment]{c' e' g'}
>> > +\lilypond[staffsize=11,fragment]{c' e' g'}
>> >
>> > \end{document}
>>
>> This change to tex-compatibility-mode.tex makes no sense. The whole
>> point of this file is to test that deprecated options are still
>> supported.
>> --
>> Julien
>
>
> Excellent catch - thanks, Julien.  I was in auto-correct mode.  How do you
> suggest we correct this?  I doubt we want this warning displayed.
> run-and-check?
>
> --
> Phil Holmes
>
>

Yes I think run-and-check is fine for this.
--
Julien