Hello Robert,
> Oh, I forgotten to mention, that
> the Lisp code is available at
> http://130.83.61.160/~robert/mactex2ooo.lisp
I have looked at the lisp code -- it appears that it was constructed
by cloning mactex.lisp and doing a global search & replace tex -> ooo,
and changing the output strings accordingly.
That has the desired effect, but I consider it generally inadvisable
to maintain parallel versions of functions; if there are changes
to mactex.lisp it would be necessary to review the ooo code and
propagate the changes through it. The mactex code is complex
enough that maintaining two versions of it would be painful
and error-prone.
I believe the best way to implement OpenOffice output is for
mactex2ooo.lisp to only reassign the tex properties and
maybe reimplement a function or two. Instead of creating
new ooo properties, I would suggest modifying the tex properties
(i.e. write (defprop %erf " erf " texword) instead of (defprop %erf "
erf " oooword)).
mactex2ooo.lisp can be a share file and then a user could say
load ("mactex2ooo"); if they want to get OpenOffice output.
(If there were a way to select a TeX flavor, we could make
OpenOffice one of the choices. I think clobbering the tex
properties is the most workable solution at present.
If/when we devise a flavor system, OO can have its
own set of properties.)
I'll take a look at mactex2ooo.lisp and see if I can extract
the parts that are necessary to enable OpenOffice output
and put them in a separate file. I believe that file would be a
lot shorter and simpler than mactex2ooo.lisp.
Thanks a lot for your interest in Maxima! Hope this helps,
Robert Dodier