Issue 3229: Prefer \relative { ... } over \relative x'' { ... }

Issue 3229: Prefer \relative { ... } over \relative x'' { ... }

As a followup to the commits for issue 3245, this conversion rule
replaces uses of \relative with reference pitch by those without
reference pitch for a number of patterns where convert-ly can detect the
first actual note reliably.

The rule is prepared to skip over files containing \include or \language
with a non-c-using notename language since the patterns do not work for
them.

However, this part of the rule is disabled in this commit as it turns
out that the LilyPond code base converts well (and more thoroughly)
without it.

[Keith, 2015-05-12 06:16:38]

https://codereview.appspot.com/235000043/diff/1/Documentation/notation/pitche...
File Documentation/notation/pitches.itely (right):

https://codereview.appspot.com/235000043/diff/1/Documentation/notation/pitche...
Documentation/notation/pitches.itely:169: like @code{\relative @{ gis''' @dots{}
@}}
Probably you'll want to reverse the convert-ly to the text that talks about the
option to use \relative c'''{}

https://codereview.appspot.com/235000043/diff/1/Documentation/notation/rhythm...
File Documentation/notation/rhythms.itely (right):

https://codereview.appspot.com/235000043/diff/1/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:450: >>>>>>> Run
scripts/auxiliar/update-with-convert-ly.sh
A few merge-failure reports made it into this upload, somehow.

[dak, 2015-05-12 07:23:58]

https://codereview.appspot.com/235000043/diff/1/Documentation/notation/pitche...
File Documentation/notation/pitches.itely (right):

https://codereview.appspot.com/235000043/diff/1/Documentation/notation/pitche...
Documentation/notation/pitches.itely:169: like @code{\relative @{ gis''' @dots{}
@}}
On 2015/05/12 06:16:37, Keith wrote:
> Probably you'll want to reverse the convert-ly to the text that talks about
the
> option to use \relative c'''{}

Well, it was more or less understood that this conversion would require a
followup rewrite.  I've just taken a look at some other commit messages and
there is, for example,

commit 6e4e9c4eacb94d68c11fd6b9062da4f724114860
Author: David Kastrup <dak@gnu.org>
Date:   Fri Oct 18 12:29:37 2013 +0200

    Run scripts/auxiliar/update-with-convert-ly.sh
    
    Actually, this is an understatement.  This is the result of
    
    scripts/auxiliar/update-with-convert-ly.sh
    git checkout HEAD ly/{engraver,music-functions,property}-init.ly
input/regression/display-lily-tests.ly Documentation/{,*/}learning/*.itely
    
    and then committing.

In a similar vein, it may be possible/feasible to exempt certain files or
directories here from the conversion if we figure out that we are likely to
cause more damage than good.

However, given the extensiveness of the patterns, it is likely less effort to
manually change passages back that are negatively affected.  More likely than
not, in chapters talking explicitly about pitches.

https://codereview.appspot.com/235000043/diff/1/Documentation/notation/rhythm...
File Documentation/notation/rhythms.itely (right):

https://codereview.appspot.com/235000043/diff/1/Documentation/notation/rhythm...
Documentation/notation/rhythms.itely:450: >>>>>>> Run
scripts/auxiliar/update-with-convert-ly.sh
On 2015/05/12 06:16:37, Keith wrote:
> A few merge-failure reports made it into this upload, somehow.

Yeah, bummer.  Since I'll be rerunning the conversion, they won't be in the
final version (if I don't repeat the rebase mistake I apparently did), but it's
unnerving that the affected files still had no problem passing Patchy.