DOE-Maxima reference manual



At 11:24 AM 6/3/02 -0400, Raymond Toy wrote:
>>>>>> "Mike" == Mike Clarkson <michael@internetdiscovery.com> writes:
>
>    Mike> I'll send you a copy of the source, and I'll try to send a PDF.
>    Mike> This format is LaTexinfo which can generate info files, which I
believe
>    Mike> is what DESCRIBE uses.I t also uses latex2html which makes a
table of
>
>DESCRIBE uses info files so if LaTeXinfo produces info files, then
>describe will be happy.
>
>    Mike> lablels (labels.pl) which is also easy to parse for pointers the
same
>    Mike> was as info. Also I think I have a texinfo->LaTeXinfo converter
so that
>    Mike> if there were any sections of the current texinfo files that
needed adding
>    Mike> to what I've done, it should be fairly simple to include them.
>
>FWIW, the CMUCL user's manual used to be in LaTeXinfo, but it seemed
>as if LaTeXinfo was no longer supported so it all got converted to
>just LaTeX.  Hevea is used to convert that to HTML.

Yes - I converted the CMUCL documentation from Scribe to LaTeXinfo for
them. I also wrote LaTeXinfo, but didn't have any time to support it.

These days' I think it's easier to move the LaTeXinfo style over to the
Python macros, just because it's more or less isomorphic, and it's actively
supported. It generates info, pdf, dvi and html. I'll work on this on the
Maxima manual as I've been meaning to "bite the bullet" and do this for all
of my documentation that's currently in LaTeXinfo (a lot :-).

Overall, so you think it's a better starting point than the current TeXinfo
docs? I can convert TeXinfo into LaTeXinfo automatically, so if there are
entire sections that need adding from the current docs, I should be able
to do that easily.

Mike.