[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LM 4.5: dead link

From: Trevor Daniels
Subject: Re: LM 4.5: dead link
Date: Mon, 30 Sep 2013 15:21:39 +0100

Federico Bruni wrote Sunday, September 29, 2013 3:33 PM

> 2013/9/29 David Kastrup <address@hidden>
>> Federico Bruni <address@hidden> writes:
>> > for the record, I've solved by adding a double backslash in the italian
>> > file, as suggested here:
>> > http://lists.gnu.org/archive/html/lilypond-devel/2008-08/msg00206.html
>> That sounds like an unrobust solution as it depends on a particular
>> erroneous behavior.  It's quite likely that this will not work
>> identically across several versions of Texinfo (Texinfo 5.0 may be
>> different) and across different backends.
> it's just a temporary solution until the node name in the english file is
> fixed.
> I hope someone can deal with this, I don't know the doc policy

It seems a backslash in a node name causes no problems for
references within the same manual, but cross-references across
manuals fail.  The correct way of dealing with this is to drop the
backslash from the node name and encode it using the bs{}
macro in the heading.  Here's an example from changing-defaults.itely:

@node The set command
@subsection The @address@hidden command

I see there are several node names in the documentation that include
native backslashes, but only the one noted above is used in a 
reference across manuals.  I'll fix ref_check.py to check for backslash
in note names to give a warning, and amend all the instances in the
documentation.  Oh, and add a note to the CG.

@bug Squad: could you please raise an issue to track this


reply via email to

[Prev in Thread] Current Thread [Next in Thread]