Re: backslashes in escape rules

[John Mandereau]

On 2008/07/05 02:05 -0700, Graham Percival wrote:
> On Sat, 05 Jul 2008 09:51:36 +0200
> John Mandereau <address@hidden> wrote:
> > I guess the motivation for using "foo" iso. "\\\\foo" for regexp
> > substitution is making docs updating easier, as running text or
> > comments sometimes mention the command name without the backslash.
> 
> That should never happen.

It does:
Documentation/user/staff.itely:1063:In earlier versions of LilyPond (pre 
2.11), @code{addQuote} was


>   If people use commands in the running
> text at all -- which they're supposed to avoid if at all possible
> -- then they should *definitely* use "\foo".

I agree.

Speaking of conversion rules, is it a good idea to have multiple rules
for one version?  This has no importance from the technical side, but
this looks awkward in convert-ly messages, so I vote for having at most
one rule per version.

I'd also recommend to use convert-ly compiled by 'make
all' (out/bin/convert-ly from top of the compilation tree) to update the
docs, as stated in README; I didn't rebuild the docs with your last
changes, but I wouldn't be surprised if docs build failed on
translations or on other places because of old commands in ly code.
I've just done this and will push as soon as 'make web' succeeds.

Cheers,
John