On 21 April 2014 14:39, Ralf Hemmecke <[email protected]> wrote: >> What is the appeal of reStructureText? Why is this an important >> goal to you? > > The documentation especially the ++ stuff should be readable also > in plain text form. So it's more for the ++ stuff that I want to go > reStructuredText+Sphinx.
Do you mean changing the source code in .spad files, i.e. no longer use a subset of LaTeX? Do you find their contents difficult to read? Can you give an example? > I'm not so much in favour of the book format, since I think that > only a few people are really printing the book. Printing might be unlikely but there is still the possibility of publishing an actual FriCAS book at one of the self-publishing sites such as Lulu. For example: http://www.lulu.com/shop/timothy-daly/axiom-volume-1-tutorial/paperback/product-243128.html There might be some advantage for people using FriCAS in courses etc. if a hard copy could be purchased at regular book stores or on Amazon.com. > > Most important to me is that the content of the book always present the > latest release and can be referred to via URL. > >>> I've added a LaTeXFormat domain. Unfortunately, that is not perfect, >>> since breqn.sty doesn't seem to like additional braces around a >>> math formula. Then it simply doesn't break. So LaTeXFormat needs >>> a complete rewrite. >> >> A complete re-write to remove extra braces? > > Well, if you have a better idea to remove needless groups... > I cannon simply remove the first and the last brace, because I might > have somthing like "{...}{...}". > Can you give an example that produces extra braces? I would like to help analyze the problem but the examples I tried so far do not produce extra braces when I look at the output from )set output tex on. >>> What is worse, some output in the .htex files LEXTRIPK REGSET >>> XPR ZDSOLVE is to long for breqn to swallow. > >> That is very unfortunate. > > No, not really. These things were not in the original book. So they just > have to be more carefully crafted so that the output will not be too > long. That should be doable. Nobody is interested to read a book with a > 2-page formula. What bothers me a bit more is overly long toplevel > \frac. I have a workaround, but it's ugly and not always working. > OK. But a general solution for breaking FriCAS TeX/LaTeX output might still be very desirable, for example for use on axiom-wiki. -- 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.
