Re: Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command")

[Graham Percival]

On Mon, 11 Aug 2008 22:43:30 +0200
Reinhold Kainhofer <address@hidden> wrote:

> Although the texinfo manual does not explicitly forbid it, using
> backslashes in node names causes problems with both texi2pdf and
> texi2html: 
> 
> - -) texi2pdf throws an error (I don't know why, because "@" is the
> command prefix  and not "\" ...). We never ran into this problem yet,
> because we don't create PDFs for translated manuals yet. The only
> place with a link to a node with a backslash ("The \override
> command") is in the German and French translations of tweaks.itely
> (but not in the original English version...)

That's a pity, but if that's the technical limitation, that's the
technical limitation.

> As a solution I propose to remove the backslash from the node names
> and the xrefs, so links will work. They can/should stay in the
> section titles, which are not used for the links anyway. There they
> don't cause any errors anyway.
>
> We already use node names with the @code removed, so this should not
> be an issue. The only thing is that the file names will be different,
> but I don't regard this as an issue, either, since all links within
> our docs are automatically generated anyway.

Hmm.  I'm not wild about having different names for @node and
@subsubsection commands.  OTOH, "the \set command" helps to
reinforce the \ in \set; "the set command" just doesn't have the
same ring to it.  (even if the *set* is in @code)

So you'd simply remove all the \ from node names, while leaving
the @subsection names untouched?  I guess that's the best
compromise.


Please detail this in policy.txt or texinfo-writing.txt... hmm,
probably the latter one.  Ditto for any other issues that you've
discovered, or will discover.

Cheers,
- Graham