>>>>> "Mike" == Mike Clarkson <michael@internetdiscovery.com> writes:
Mike> At 11:24 AM 6/3/02 -0400, Raymond Toy wrote:
>> 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.
Mike> Yes - I converted the CMUCL documentation from Scribe to LaTeXinfo for
Mike> them. I also wrote LaTeXinfo, but didn't have any time to support it.
I didn't know that. Thanks! I've only seen the LaTeXinfo version of
the CMUCL User's manual.
Mike> These days' I think it's easier to move the LaTeXinfo style over to the
Mike> Python macros, just because it's more or less isomorphic, and it's actively
Mike> supported. It generates info, pdf, dvi and html. I'll work on this on the
I'm not familiar with these "Python" macros so I can't say.
Mike> Overall, so you think it's a better starting point than the current TeXinfo
Mike> docs? I can convert TeXinfo into LaTeXinfo automatically, so if there are
Mike> entire sections that need adding from the current docs, I should be able
Mike> to do that easily.
I don't really care as long as the final result is in some format that
is currently supported and looks as if it will be supported for a long
time. The only constraint now is that, whatever is used, we can
generate info files out of it. Unless, of course, someone wants to
change how maxima's describe works. :-) This is acceptable to me as
long as it provides plain text output.
Ray