Eli Zaretskii <[EMAIL PROTECTED]> writes:
> On 29 Jun 2000, Niels M�ller wrote:
>
> > If I enter `M�ller� directly in the source file, it looks fine in
> > info, but in TeX output, the � is lost, so in the paper copy the
> > string appears as `Mller�. On the other hand, if I write `M@"oller� in
> > the input file, the TeX output gets right, but in the info output I
> > get `M"oller�. I haven't been able to figure out what to write in
> > order to get correct output in both info and TeX.
>
> You can't do that currently, unless you use @iftex and @ifnottex.
The Right Thing is probably to write the source file in latin-1 (or
whatever charset seems approriate), use @documentencoding ISO-8859-1,
and fix texinfo.tex to deal with that. I'm no TeXpert, but at least
there are LaTeX packages that do similar things. But I think that's on
the texinfo TODO list already.
Haing to use @iftex is quite annoying, when you have simple words like
`caf� which appear now and then in the running text.
> > I haven't used info --usage much, but it seems not to work quite as
> > advertised. At least not on my manual (which also contains "Invoking
> > foo" nodes for several commands). When I type
> >
> > info -f ./lsh.info --usage lsh
> >
> > it brings up the "lsh basics" node (which is a tutorial section)
> > rather than the reference section "Invoking lsh". Is there any special
> > markup I can use in my sourcefile to help info --usage choose the
> > right node?
>
> You need to follow GNU standards: the "Invoking" node should be in the
> first-level or second-level menu in the manual.
It is. The top level menu is
@menu
* Introduction::
* Installation::
* Getting started::
* Invoking lsh::
* Invoking lshd::
* Terminology::
* Concept Index::
(there's also a conventional @detailmenu, if that matters). The
reference Invoking-style nodes are there. The Getting started node
includes the menu
@menu
* lsh basics:: Connection with lsh
* tcpip forwarding:: Forwarding @acronym{TCP/IP} ports
* lshd basics:: Starting the lshd deamon
* public-key:: Using public-keys
* srp:: Using SRP authentication
* sexp:: Examining keys and other S-exp files.
* Converting keys::
@end menu
That's where the "lsh basics" node found by info --usage lsh lives. I
think it would be a good thing to add a new magic word
@usage lsh
to tell makeinfo and info which node contains command line options for
a given program. Perhaps one should also have an alternative
@usagetree lsh
to say that subnodes are essential; this should not matter much for
interactive info, but it would be useful for tools (like the man-page
tool I'd like to see) that extracts the relevant information into a
single, smaller, file. In general, I think it is better to use
explicit markup than to rely in heuristics.
BTW, non-interactive use of info --usage >some-file.txt seems to dump
the entire info file, not just the invocation node. For example,
info --usage gcc
starts interactive info on the right node, but
info --usage gcc |less
displays the entire gcc manual. Is that intentional?
/Niels
