On 10/19/2014 12:14 AM, Bill Page wrote: > using the new tex formatter. There are numerous cases where breqn > fails to break the output generated by FriCAS which was properly > processed by texbreaker.
Yes. OK. You can modify the table of how code is generated in tex.spad so that it basically generates the same structure as the old tex.spad. Then you pipe the output through texbreak and have a "wonderfully" broken tex expression. Unfortunately texbreak is too tailored for the old tex output. Modifying tex.spad to output modern latex automatically means that texbreak (as is) will not work. I'm not interested in working on texbreak.c. It's basically undocumented and one would have to figure out it's design from the C code. > But I am beginning to think that the number of cases where breqn > fails is making it seem rather impractical to convert axiom-wiki to > the new format. Yes, maybe. I find the whole idea of showing TeX rendered output impractical. There is the problem of line breaking and one cannot cut&paste (part of) the output. (La)TeX output seems only relevant to me, if one wants to include an expression in a paper or book. But then there is still a chance to break overly long lines by hand. Otherwise the output cell should simply be horizontally scrollable. > One experiment that I might try is to use both > texbreaker and the new format with breqn. But in the new format > there is a lot of FriCAS-specific markup of I don't know how it is > going to turn out. As I said above, if you don't match the new tex output with what texbreak.c understands (either changing one or the other), breaking a line properly will not work even if you pipe the generated tex code through texbreak. Ralf -- 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.
