Eli Zaretskii <[EMAIL PROTECTED]> writes:
> On 28 Jun 2000, Niels M�ller wrote:
>
> > Personally, I like info and makeinfo, (except for the broken handling
> > of latin-1 characters, I haven't yet been able to get them right in
> > both info and TeX).
>
> 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.
> > I don't want to convert an entire texinfo manual to a man page. I want
> > to create reasonably short man pages from selected nodes in the input
> > file, in particular the "Invoking ..."-style nodes.
>
> Does this do what you want:
>
> info foo --usage --subnodes > foo.man
That's almost what I want (I didn't find it because I was looking
for options to makeinfo, not info). Thanks for the hint.
info --node "Invoking lsh" --subnodes --usage -f ./lsh.info >lsh.man
seems to give reasonable output. Now, I'm not very familiar with the
way man pages are set up and installed, but I think it would be even
better to get output in *roff, using formatting that follows the
conventions for man pages more closely (I.e. headings in uppercase in
the left margin, boldface for @sample and @command, underline for
@var, etc).
> In fact, "info --usage" was designed to replace the man pages
> entirely, since it gives you an immediate access to the usage section
> of the manual. If that is not enough to replace the man pages, please
> tell what's missing.
Well, the main problem is that it is novel; people expect to be able
to type man command and get information in the traditional style. ;-/
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?
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.
Reards,
/Niels
