On 29 Jun 2000, Niels M�ller wrote:
> > AFAIK, makeinfo and info are supposed to be 8-bit clean, so you should
> > not have any problems with latin-1. Please elaborate, with examples,
> > if possible.
>
> 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.
I thought you were saying that it's entirely impossible to put Latin-1
characters into a Texinfo document.
> info --node "Invoking lsh" --subnodes --usage -f ./lsh.info >lsh.man
If you use --node, --usage is redundant. --usage is supposed to find the
correct node byu itself, without asking the user to intuit it.
> 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.
> How does info --usage figure out which info file to open, if there are
> more than one command described in each info file? For instance info
> --usage lshd should read lsh.info.
It gets to the same point where "info lshd" gets you, and then looks for
the Invocation node around there. The heuristics is complex (becaus many
manuals don't follow the standards), so if you want to understand it,
please look at the sources of Info.
