Re: backward compatibility and more

> Um, could you cite an example for me?

If there is 
@code{something @b{otherthing}}
makeinfo will do
<code>something </code><b>otherthing</b><code></code>

> please see the GNU Info documentation for texi2html (`info texi2html').
> That seems to be what a lot of other GNU projects are doing nowadays.

Right.

> Roff?  Doesn't that have something to do with man pages?  Could you dump
> the info manual into a roff file and call it a man page?  A simple
> script could add a man header that suggests GNU Info for easier navigation.

roff is a formatting system. It is used for man pages, but not only. In the
texi2html manual case the man pages macros aren't suitable, because there
is nothing for chapters, or footnotes or index, and a man page has a specific
layout.

In the init file I made to convert to roff, I used the 'me' macros (as 
texi2roff does) as these are macros intended for manuals. 

If you want to have a look, to convert a manual to roff, using the me 
macros and view it, with texi2html doing the conversion, I do the following:

texi2html --init roff.init --out - manual.texi | groff -me -Tutf8 | less -R 
 
I indicate to groff that the me macro package is used. But it isn't a man page.

> Alternatively, I haven't played with it much, but I think there is a set
> of Perl scripts out there called "Help2Man" which convert the output of
> a program's --help output into a simple man page.  I could look at that
> with a note to read the GNU Info documentation as fairly complete.

Maybe it could be enough. However it seems to me that a real manual page 
is better.

Pat