lilypond-devel
[Top][All Lists]

## Re: Using \\ in a texinfo macro argument generates \ in html, but \\ in

 From: Graham Percival Subject: Re: Using \\ in a texinfo macro argument generates \ in html, but \\ in pdf Date: Mon, 31 Mar 2008 13:14:58 -0700

On Mon, 31 Mar 2008 22:00:06 +0200

> Am Montag, 31. M__rz 2008 schrieb Karl Berry:
> > @set backslash \
> > and then using @value{backslash} in the actual argument?
> >
> > Or
> >
> > @macro backslash
> > \\
> > @end macro
> > and then @backslash{}?
> >
> > Do either of those work?
>
> Yes, thanks, both of them work fine (the second one is easier to

@c we need this since @q{\} doesn't work with makeinfo 4.8 --
@set backslash \

> Graham (that's one of our Lilypond documentation team), which one is
> better for lilypond?

Umm.  As I understand it, we need to rewrite something like this:
@warning{each note is relative to the previous note in
the input, not relative to the @code{c''} in the initial
@code{\\relative} command.}

into this:
@warning{each note is relative to the previous note in
the input, not relative to the @code{c''} in the initial

?

Well, if it needs to be done, we can do it.  It makes the docs
slightly harder to work with, but that's still better than having
incorrect output.

This only applies to @code{} that appears inside @warning{}, or
other macros, right?  We have over a thousand "@code{\foo}"
strings inside the docs, and I'd really rather not rewrite them
all.

Reinhold, could you modify macros.itely and tutorial.itely (search
for "FIXME") accordingly, as well as writing-texinfo.txt (search
for "warning", and add @bs{} to the list of commands).

Cheers,
- Graham