All of the versions of latex I've tried on axiomunit_v2.tex
blow up on the \pdfoutput=1. bad karma has come to haunt me.
rather than trying to generate pdf files in latex i'd suggest
using latex to gen a .dvi file and then use dvipdfm or dvi2pdf.
dvi2pdf is a shell script that reads:
dvips -e 0 -
On Tuesday, November 29, 2005 9:34 PM C Y wrote:
>
> Tim Daly (root) wrote:
> > ...
> > (a) the code isn't linear,
> > (b) we eventually want it all available in a browser frontend
> > and
> > (c) a way to use this in graphs would give us a good "map"
> > ability
>
> As you can see in t
On Tuesday, November 29, 2005 11:04 PM C Y wrote:
>...
> Tim Daly (root) wrote:
> > i've never seen latex output a pdf. always a dvi.
> > this must be new behavior.
>
> I believe it is. This thread is another instance of someone seeing
> this behavior:
>
>
http://forums.gentoo.org/viewtopic-t-3
On Tuesday, November 29, 2005 11:37 PM C Y wrote:
> ...
> > The line breaker code (written by Robert Sutor - one of the
> > original Axiom developers) that we use with Axiom on both
> > MathAction and in the Windows version of the TeXmacs interface
> > is written in C. The original version was ru
--- "Page, Bill" <[EMAIL PROTECTED]> wrote:
>
> On Tuesday, November 29, 2005 9:56 PM Tim Daly (root) wrote:
> >
> > > I got a bit fancy and allowed automatic resizing of a
> > > couple of large equations based on the two margin sizes,
> > > but breqn would be a preferable solution there if t
On Tuesday, November 29, 2005 9:56 PM Tim Daly (root) wrote:
>
> > I got a bit fancy and allowed automatic resizing of a
> > couple of large equations based on the two margin sizes,
> > but breqn would be a preferable solution there if the
> > license is ever straightened out. (Or we implement
Perhaps I should clarify that breqn is not a standalone program but a
LaTeX package. \usepackage{breqn} is how you include it, IIRC. If
Axiom removes the need for it I would be very very interested to see
this - otherwise, given our preference for large margins I think we
should look more deeply i
--- root <[EMAIL PROTECTED]> wrote:
> > I got a bit fancy and allowed automatic resizing of a
> > couple of large equations based on the two margin sizes,
> > but breqn would be a preferable solution there if the
> > license is ever straightened out. (Or we implement our own
> > version of i
--- root <[EMAIL PROTECTED]> wrote:
> > > i'm DEEPLY opposed to conditional branching in tex
> > > documents.
> > > even if there is one good use i assure you some bright spot
> > > down the line will figure out a way to conditionally build
> > > algebra documents based on half-a-thousand switc
> > i'm DEEPLY opposed to conditional branching in tex documents.
> > even if there is one good use i assure you some bright spot
> > down the line will figure out a way to conditionally build
> > algebra documents based on half-a-thousand switches. and if
> > something gets skipped it is hard t
> > it would be cool to take the src/doc/endpapers.pamphlet and
> > make it display well on MathAction with hyperref links to the
> > algebra.
>
> Hmm :-). For the inattentive among us, what is endpapers.pamphlet
> again?
the old axiom hardcover book has two diagrams on the inside
covers of the
--- root <[EMAIL PROTECTED]> wrote:
> >
> > 1) hyperref (which I see you've already decided to include)
>
> agreed. this is important because
> (a) the code isn't linear,
> (b) we eventually want it all available in a browser frontend
> and
> (c) a way to use this in graphs would give us a
--- root <[EMAIL PROTECTED]> wrote:
> CY,
>
> I liked the 'axiomunit_diagramtest' version a lot.
> I'll have to try that with src/doc/endpaper.
> Can you post or send the diagram code?
Actually, the whole tex file is posted, I just didn't link to it ;-).
http://portal.axiom-developer.org/Memb
> I got a bit fancy and allowed automatic resizing of a couple of large
> equations based on the two margin sizes, but breqn would be a
> preferable solution there if the license is ever straightened out. (Or
> we implement our own version of it.)
if breqn is an equation line breaker we have one
Changes http://www.axiom-developer.org/zope/mathaction/PlayingTogether/diff
--
http://www.fortune.com/fortune/ceo/articles/0,15114,1135298-2,00.html
--
forwarded from http://www.axiom-developer.org/zope/mathaction/[EMAIL PROTECTED]
___
Axiom-developer m
Changes http://www.axiom-developer.org/zope/mathaction/PlayingTogether/diff
--
http://www.fortune.com/fortune/ceo/articles/0,15114,1135298-2,00.html
--
forwarded from http://www.axiom-developer.org/zope/mathaction/[EMAIL PROTECTED]
___
Axiom-developer m
Changes http://www.axiom-developer.org/zope/mathaction/PlayingTogether/diff
--
http://www.fortune.com/fortune/ceo/articles/0,15114,1135298-2,00.html
--
forwarded from http://www.axiom-developer.org/zope/mathaction/[EMAIL PROTECTED]
___
Axiom-developer m
CY,
I liked the 'axiomunit_diagramtest' version a lot.
I'll have to try that with src/doc/endpaper.
Can you post or send the diagram code?
re: 1 inch margins (2.54 cm for our other friends :-))
my book publisher told me that a 6 inch line was an industry standard
because, in their experience, it
--- "Page, Bill" <[EMAIL PROTECTED]> wrote:
> On Tuesday, November 29, 2005 4:14 PM C Y wrote:
> >
> > Well, still not approved for public visibility
>
> Sorry, I've been a bit busy with other things. Do you still
> want these documents approved or would you like to wait for a
> more final ver
> Call me old-fashioned, but in order to edit pamphlet files, I would get
> the arch-sources and do something locally and then submit. Only for
> small changes the web-access to the sources makes sense to me. Anyway,
> it is not quite clear to me how modifications to the sources made over
> the
>
> The thebibliography environment is superfluous if we agree on ONE big
> .bib file and UNIQUE BibKeys. It is even more flexible.
>
> > ===
> >
> > and now the way I work with these:
> >
> > =
>
> By the way, you need "dummyindex" because you have
> \input{${PROJECT}.ind} below. \printindex is enough.
>
> > \eject
> > \begin{thebibliography}{99}
> > \bibitem{1} nothing
> > \end{thebibliography}
> > <>=
> > \begin{theindex}
> > \item none
> > \end{theindex}
> > \printindex
> > \input
>
> For the .dvi generation I rather like to write a script so that the
> inverse search becomes available.
this comment is lost on me.
please explain in detail.
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/m
>
> I don't say it is generally a bad idea, but I cannot say that I like it.
> In particular, I don't see, why the variables TANGLE, WEAVE, etc. should
> be repeated in every file.
oh, this is an artifact of an OLD debate. people want to use their
"standard" version of notangle even though i ke
>
> > ===
> > and now the standard "tail":
> > ===
> > \section{Makefile}
> > <<*>>=
> > PROJECT=tpd
> > TANGLE=/usr/local/bin/NOTANGLE
> > WEAVE=/usr/local/bin/N
> Maybe you don't like it, but I use a slightly different approach in
> ALLPROSE. What comes out as defn and use in your case comes out in red
> and blue color in the index in ALLPROSE. And you would simply say:
> \defineterm{foo} and \useterm{foo}. Read the description of
> rhxterm.sty.nw on h
>
> For what it's worth, I would estimate I'll eventually ask to have the
> following available, since they are very standard and too big to reall
> :
>
> 1) hyperref (which I see you've already decided to include)
agreed. this is important because
(a) the code isn't linear,
(b) we eventually w
>
> So the focus is on providing the parts. In the spirit of ALLPROSE that
> could mean the following:
>
> 1) Write some chapters about the general idea.
> Then a chapter that lists the files names (of the files that form the
> contents of the book) together with a short description of what th
Greetings, and thanks Tim! I thought this was unnecessary with
2.6.8pre, no?
Take care,
root <[EMAIL PROTECTED]> writes:
> ===
> FAQ 36: Axiom won't build on FC3
> ===
> I also do not agree to the goal that each file is ONE literate program
> and in some sense stand alone. I, therefore, think that "head" and
> "tail" should not be part of a file, just the things that are inside the
> \begin{document} ... \end{document}.
>
> If you like a wrapper, write a litt
> > Each file I make into a "literate program" has a "head" and a "tail"
> > that contains essentially the same code for the same reasons. The only
> > major deviation is that I will occasionally include the "axiom.sty" file
> > in the literate document if it is meant to be stand-alone and the user
whew. hours worth of email! 95 new, nonspam emails!
> Many contributions consist of several packages, categories and domains, which
> are somehow related.
There are some clear relations. For instance, many files contain more than
one category, domain, or package (CDP).
The very highest level
> > I promised to give you some idea of the pamphlet and book file coding
> > "standards". This is the current "state of the world" which evolves
> > as I write more pamphlet files. However, as I re-edit old files I
> > modify them to conform to these standards.
>
> In ALLPROSE I have specifically
> My problem with HyperDoc is that there are quite a number of commands
> and no good documentation what they are for. I would clearly prefer my
> aldordoc.sty even though it does not cover all things HyperDoc can do.
we probably need to re-think the input language for the browser.
we can take u
===
FAQ 36: Axiom won't build on FC3
===
You need to turn off dynamic library load point randomization.
As root do:
echo 0 >/proc/sys/kernel/exec-shield
===
On Tuesday, November 29, 2005 4:14 PM C Y wrote:
>
> Well, still not approved for public visibility
Sorry, I've been a bit busy with other things. Do you still
want these documents approved or would you like to wait for a
more final version? No problem either way. I am just hesitating
because I a
On Tuesday, November 29, 2005 9:40 AM C Y wrote:
>
> I uploaded a variety of pdf and dvi files into my account on
> portal.axiom-developer.org, but apparently they need to be
> "published" to be visible to the world. I "submitted" them
> but I have no idea who is supposed to be on the other end t
Well, still not approved for public visibility but it looks like a
direct link to each file will allow folks to view them. This is a
collection of a variety of formatting options that can be achieved with
the options included in the preamble. For those who want the fanciest
result, I recommend th
I uploaded a variety of pdf and dvi files into my account on
portal.axiom-developer.org, but apparently they need to be "published"
to be visible to the world. I "submitted" them but I have no idea who
is supposed to be on the other end to complete the process.
Also, seeing as these are public dr
Changes http://page.axiom-developer.org/zope/mathaction/LaTeX/diff
--
\begin{axiom}
solve([x+y=a,x-y=b],[x,y])
\end{axiom}
--
forwarded from http://page.axiom-developer.org/zope/mathaction/[EMAIL PROTECTED]
___
Axiom-developer mailing list
Axiom-develo
Dear Tim,
well, i'm WAS planning to do a document-and-cleanup cycle on
axiom.sty so that (a) only the things that are used survive (there is
cruft from history in there (b) it formats nicely so i can append it
to stand-alone documents and (c) the macros are documented like
everything else. i hav
Changes http://page.axiom-developer.org/zope/mathaction/PlayingTogether/diff
--
\begin{axiom}
int(sin(sqrt(x)),x);
\end{axiom}
--
forwarded from http://page.axiom-developer.org/zope/mathaction/[EMAIL PROTECTED]
___
Axiom-developer mailing list
Axiom-d
Changes http://page.axiom-developer.org/zope/mathaction/AxiomInterface/diff
--
\begin{axiom}
[1/2, 3/4, 2/3]
\end{axiom}
--
forwarded from http://page.axiom-developer.org/zope/mathaction/[EMAIL PROTECTED]
___
Axiom-developer mailing list
Axiom-deve
Hi Clifford,
Here is the preamble I am currently using - for any more elaborate
posting I'll have to wait until I'm back home. I brought this one with
me but didn't have time to sort everything out.
\documentclass{article}
\usepackage{axiom}
\usepackage{ifthen}
\usepackage{fontenc}
The ifthe
Hi Tim,
root wrote:
Ralf,
I promised to give you some idea of the pamphlet and book file coding
"standards". This is the current "state of the world" which evolves
as I write more pamphlet files. However, as I re-edit old files I
modify them to conform to these standards.
In ALLPROSE I have s
Hi Tim,
root wrote:
Again: I think that our aim should be to make MathAction be the
*only* entry point to the Axiom world.
Email has one property that a website lacks. It forms a private
linear queue of work for me to accomplish (or not :-)).
Well, agreed. But you are certainly not new to Ax
Hi Martin,
Could you set up a page on MathAction of this discussion thread? Or
better, could someone tell me how to create a new page.
What you state here are some visions that should be recorded and not be
forgotten in the mailinglist-archive.
Martin Rubey wrote:
Ralf Hemmecke <[EMAIL PR
On Friday, November 25, 2005 4:51 AM Ralf Hemmecke wrote:
... I don't think that it is actually the amount of text
which is a problem, it is rather its organisation.
I agree partially. You are probably right that the amount is less of a problem
than it's organisation.
Exactly. If there is a
Here is a draft alternate page to be displayed when you on (2):
2'. http://www.axiom-developer.org/zope/mathaction/SandBoxFrontPage
Do you think that organization of this new page would be easier
to understand for new Axiom users?
Oh, just beautiful!!!
Ralf
Page, Bill wrote:
On Friday, November 25, 2005 4:51 AM Ralf Hemmecke wrote:
Bill Page wrote:
...
Perhaps this is a good time to suggest that we disconnect the
axiom-developer email list from the Axiom Wiki web site?
Good idea. I usually just remove those emails. A much better
idea would be t
50 matches
Mail list logo
