Hello, 2013/9/30 Trevor Daniels <t.dani...@treda.co.uk>
> > > 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 @code{@bs{}set} 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 > > This has been added as http://code.google.com/p/lilypond/issues/detail?id=3590 -- Marek bug squad member _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond