On 17 October 2014 12:54, Ralf Hemmecke <[email protected]> wrote: >> OK. Such extensive changes however make me think that maybe >> defining this as a new output format > > And then throw away the buggy tex output?
Well, what works now could continue to work ... > And later redefine to )set output tex on, because the old code > is gone? > I would not bother to redefine )set output tex. There is no urgent need to get rid of the old code. I would just freeze the existing stuff and invent a new output format, )set output latex on promote its use, and try to maintain the new code. This would make it a lot easier to migrate something fairly complex like axiom-wiki. Maybe at some point in the (far?) future the old output format could be declared obsolete and removed. I suppose at that by that time there might be a lot of other stuff that might be considered obsolete too. > As I said, I don't insist on putting the new tex.spad into the new > release. I think it would be good it get it into the release as soon as possible. Maintaining a separate branch makes it awkward for people to try it. The important thing is that it should not disrupt things that work now. > I'd like to have access to a copy of the new axiom-wiki VM so > that can figure out how to make the new tex.spad work with it I had a problem with my old copy of axiom-wiki so about a year ago I asked Waldek for a copy of what was running on his server. As I recall it was about a 10 Gb download, maybe less, large but not impossible. > Of course, I don't want to do this on the running system. > >> Thanks. Actually what we have on axiom wiki is significantly older: > > :-( I expect that it wont be hard to upgrade the tex/latex versions, it's just not as easy as apt-get. > > Maybe some day the old axiom-wiki and the 5 years old underlying > ubuntu will just fall apart. I think that this is not likely now that we have good virtual machine support and backups. The old version of the OS and back-end web application (Zope) is hidden on a isolated VM, while the front-end web server runs directly on an up-to-date host server. But perhaps at some point no one will be willing to run it any more. > I guess, one would have to upgrade at least some > of the latex packages, but that might lead to yet unknown problems > elsewhere. Unfortunately upgrading plone probably leads to not having > zwiki anymore, but that's a prerequisite for the axiom-wiki. I don't > think, I will spend a lot of time on maintaining axiom-wiki. > We don't use Plone any more. Although it might still be running on the axiom-wiki VM, I don't think Waldek exposes what used to be known as axiom-portal to the front-end web server. >> http://axiom-wiki.newsynthesis.org/LatexTemplate > > Wow. Impressive. > Yes, it's a mess. > How is mathaction working? Latex enviroment -> dvi -> ps -> png? What is > the procedure? > Yes, approximately. If you get into a situation where you are trying to work on this, I would be glad to help point you to the right code - at least to the extent that I can recall and find it again myself. > Let me go through the list... > > usc and utf8x: why is ucs needed? is'nt utf8 (no x) enough? > > bbm, mathrsfs: really used anywhere? > > pstricks: there are such tricks on axiom-wiki? > > pst-grad,pst-plot: is this necessary for fricas-generated picS? Or where? > > \textalpha .. \textOmega: no problem > > xy: which page uses that? > > amsmath .. amsthm: not problematic > > graphviz: no idea > sagetex: Oh... I stop here. That's probably including a lot of other stuff. > Your guess is as good as mine on most of this stuff. All of it was interesting for some reason at one time. > Please first tell me how mathaction processes a page. > To me it would look much better to create separate files for each > > \begin{axiom} ... \end{axiom} > \begin{sage} .. \end{sage} > > environment separately and then only have the packages preloaded that > apply to those environments and not one big style file (like this > LatexTemplate for *all* the environments. But it seems that is currently > not done this way. > The individual "code" sections such as \begin{axiom} ... \end{axiom} \begin{spad} .. \end{spad} \begin{reduce} ... \end{reduce} \begin{sage} .. \end{sage} are first processed by running the associated external programs and then these sections are replaced with generate LaTeX fragments. The page itself might contain other LaTeX fragments coded directly by the user. This pre-processing step is what was added to the original LatexWiki code on which mathaction was based. LatexWiki in turn depended on ZWiki, and ZWiki depends on an older version of Zope and Python, etc. The processing step that converts the Latex fragments into png and HTML is done by the (mostly) original LatexWiki code and the final conversion of reStructuredText content is done by ZWiki code. Bill. -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/fricas-devel. For more options, visit https://groups.google.com/d/optout.
