Ralf Hemmecke wrote:
>
> >> In GUESSPI.htex the output is simply to long. LaTeX seems not to be able
> >> to work properly on it. Since showing the actual input is not too
> >> relevant for the demonstration of guessPRec, i've simply suppressed the
> >> output of the first command.
> >>
> >> The problem in LLLRED.htex is that my script assumes that \free and
> >> \bound appears on the same line as \spadcommand (otherwise I would have
> >> to count braces). Yes it might make the lines overlong, but I don't
> >> consider that a big issue.
> >>
> >> Waldek, may I commit?
> >
> > OK. In the long run it would be better to get rid of such
> > limitations, but for now OK.
>
> Waldek, I understand, that you want the \free-\bound-on-the-same-line
> restriction go away. I don't think that is worth the effort.
> My view on this is that it is easy to put them on the same line and
> furthermore the .htex stuff is anyway bad. There is no future for HyperDoc.
>
> My laptop now has 4K resolution. HyperDoc is almost unreadable. Who
> knows nowadays how to change the fonts via .Xresources? And it's unclear
> whether it would actually solve the problem.
>
> As for the long output in GUESSPI ... That shouldn't be a problem
> either. The original Axiom developers have chosen examples to be small
> and still illustrative (and the probably always had in mind that it will
> end up in a printed book). Shouldn't we design it in the same way?
>
> So I currently see no reason for me to act.
Hyperdoc program may be obsolte, but it works resonably well and
we have nothing that works better. And AFAICS competition have
shiny stuff that really is not better (and frequently worse) than
Hyperdoc.
More important, we need a documentation format. .tex format
allows including actial FriCAS output of examples and has math
support. It is based on widely used system, that is LaTeX.
I do not think that there is better format around -- there
are formats easier for machine processing but really not
suitable for writing by hand (various *ML variants) and
there are simple formats which IIUC lack features.
Not, both requirements to put things on a single line and
limits on size of expressing should be obsolete. Sometimes
minimal example have to be big and both of the above
are problematic then. Note that original authors developed
texbreaker program. You say "obsolete", but if new things
can not do what the old did the new thing actually is
obsolte and the old one is state of the art.
--
Waldek Hebisch
--
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 https://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.
