[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
@code vs. @t for node names
From: |
Karl Berry |
Subject: |
@code vs. @t for node names |
Date: |
Tue, 15 Jan 2013 18:04:35 GMT |
Hmm. I've been converting all the Texinfo manual node names to use
@-commands, as in
@node @code{makeinfo} Pointer Creation
This generates:
File: texinfo, Node: 'makeinfo' Pointer Creation, Next: '@anchor', Prev:
'@node', Up: Nodes
6.2 'makeinfo' Pointer Creation
===============================
But now I'm wondering if it would be better to use @t than @code. Then
there wouldn't be the 'quotes' in the node name, which seem like they
just get in the way. As in:
@node @t{makeinfo} Pointer Creation
generating
File: texinfo, Node: makeinfo Pointer Creation, Next: @anchor, Prev:
@node, Up: Nodes
(As far as I know all of the usual markup commands generate 'quotes'.)
Using @t will mean the output in TeX/HTML will still correctly use the
typewriter font, which was one of the main reasons I wanted to do this.
But before I switch everything again, I thought I'd ask ... any problems
with @t for this come to mind? Better alternatives? ?
Thanks,
k
- @code vs. @t for node names,
Karl Berry <=