axiom-developer
[Top][All Lists]

## Re: [Axiom-developer] Re: Axiom Book

 From: David MENTRE Subject: Re: [Axiom-developer] Re: Axiom Book Date: Sat, 19 Jun 2004 19:27:07 +0200 User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

```Hello,

> I hate to ask this because I'm quite sure it's a stupid question, but
> how does the book.pamphlet file differ from regular latex?

In no way for book.pamphlet.

>  If I were organizing it my instinct would be to break it down into
> individual latex files for each chapter, to make things more
> managable, but I'm assuming there's a reason for everything being in
> one file due to the pamphlet superstructure.

As far as I recall, noweb (for noweb -> latex conversion) can only
manage one file at a time. It does not handle tex input files.

> There are ways, at least in regular latex, to conditionalize things
> like  \usepackage statements.  If that can function in the pamphlet
> environment than unless a pdf is being created latex won't even mess
> with the other stuff.  I'll see if I can take a stab at it.

I think the most important point regarding the book is to have the

> Fuzzy?  Do you mean poor fonts?  As far as graphics go...  there are
> some things that can be done, but for the maxima book we have two
> copies of all graphics - ps and png I believe are the formats we use.
> (Which reminds me - I need to check if a pdf graphic option would be
> better.)  Did you want to have only one version of a graphic that is
> handled at runtime?

Right now, the graphics are in eps format (but with no bounding boxes in
some cases. It blocks me to convert the graphics to pdf. However I'm for
from a postscript specialist). From an engineering point of view, the
best solution would be to have the reference graphic in one format that
can be translated in needed formats by the Makefile.

>
> Oh, he might have done most of this already then :-).  Archive time.

:) Just pdflatex.

> Ah yes, graphics.  That reminds me - what are Axiom's eventual plans
> for graph output?  Does Axiom have its own internal code, or will it
> need to use something like gnuplot?

If I remember correctly, Tim is resurrecting Axiom's original graphics
code.

> Probably the time to look into that sort of thing will be more when
> Axiom is reaching a "polished, 1.0" status where we can package it and
> market it to non-developers.

Regarding the 1.0 status, the lacking points are:

1. Axiom book in PDF with graphics;

[done for pdf. Nobody is working on the graphics]

2. Define if the current found bugs are release critical or not. If
yes, fix them. If not, document them (and reduce the priority in the
1-3 range);

[nobody is working on the bugs, except martin and william]

3. Have a wroking graphics module.

[I think tim is working on this]

Yours,
d.
--