axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Axiom-developer] Re: Pamphlets and LaTex


From: Stephen Wilson
Subject: [Axiom-developer] Re: Pamphlets and LaTex
Date: 17 Jul 2007 18:57:14 -0400
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4

Forward:
Stephen Wilson <address@hidden> writes:

> address@hidden writes:
> 
> > Weave is only required to generate axiom-internal documentation
> > when we want to do special case work. Even if the weave step is
> > not performed the files are still pure latex. Thus, 
> > 
> > \spadcommand{$a^2+b^2=c^2$}
> > 
> > is perfectly valid latex (and is used in my published book).
> > Anyone can latex the file and see typeset math as:
> > 
> >   2    2    2
> >  a  + b  = c
> > 
> > but the weave step, would also allow us to input such a command
> > to axiom and use it to create hyperdoc pages.
> 
> OK.  I understand.  I was confused, and for good reason, I think.  The
> construct itself is confusing.
> 
> \spadcommand{...}  means one thing when TeX sees it, and something
> else when the weave translator sees it.  We should not confuse such
> things.
> 
> 
> I cannot remember the terms, but hyperdoc has the ability, as you
> know, to perform evaluations which reference previous results.
> 
> You cannot have a pure latex file which typesets itself and exploits
> that kind of evaluation.  However a weave stage can connect with
> axiom, perform the evaluation, and insert pure latex which is a result
> of the evaluation.
> 
> Lets not overload the meaning of constructs used to write pamphlets.
> 
> I understand the convenience of being able to share a file which can
> be processed by anyone.  But what are the advantages of disguising
> meta information in that file?  What are the disadvantages of needing
> to weave a pamphlet to get that one thing you need to share?
> 
> 
> Steve





reply via email to

[Prev in Thread] Current Thread [Next in Thread]