"Bill Page" <[EMAIL PROTECTED]> writes:
...
>> ...
>> > | 2) The Axiom Wiki FrontPage has more graphics including an
>> > |example Axiom output graphic.
>> >
>> > That, from my perspective, contributes to the "visual load".
>>
>> I agree with this,
>
> :( Well, I really like the example ... in
Arthur Ralfs [EMAIL PROTECTED] wrote:
> Hello,
>
> I'm working on a tex to mathml program in C. It's rudimentary and
> only meant to transform the stuff between the $$ signs that comes
> out of axiom so it can be displayed in firefox. However it seems
> to work so I thought I should make it avai
In order to remove the need to distribute a version of noweb with Axiom,
we must modify the sources a bit.
I've run every .pamphlet file from silver/branches/build-improvements
through noweb.
There are the following problems
notangle src/hyper/token.pamphlet > dummy
undefined chunk name: <>
Hi Gaby,
it turned out that it is not totally easy to mimic the behaviour of
notangle, in particular if multiline chunks have to be indented correctly.
Below you find rhxtangle.pl.pamphlet. I hope you find it useful to drop
the initial noweb dependency for the configuration phase of Axiom.
On August 5, 2006 6:07 PM Arthur Ralfs wrote:
>
> I'm working on a tex to mathml program in C. It's rudimentary
> and only meant to transform the stuff between the $$ signs that
> comes out of axiom so it can be displayed in firefox. However
> it seems to work so I thought I should make it avail
Hello,
I'm working on a tex to mathml program in C. It's rudimentary and
only meant to transform the stuff between the $$ signs that comes
out of axiom so it can be displayed in firefox. However it seems
to work so I thought I should make it available in case someone
was interested.
My quest
> A question Tim, if I may. In looking at sys-pkg.lisp, it seems like
> there are a rather large number of import and export commands contained
> there. Is this normal in lisp to have to hand-import and hand-export
> so many symbols? Also, I'm a bit confused by the BOOT and VMLISP
> package rela
--- Ralf Hemmecke <[EMAIL PROTECTED]> wrote:
> 1) If you need to edit the pamphlet files to make them work in the
> context of a big book. That sounds as if you have too much time to
> spare.
Not really. I take it you regard the idea as frivolous?
> 2) Where are our priorities? Improving LaTe
--- root <[EMAIL PROTECTED]> wrote:
> > 2. I noticed a lot of implementation specific code having to do
> > with things like (system:getenv $AXIOM) - is the plan to write some
> > generic macros to handle these operations and get all of the
> > implementation specific logic into one file?
>
> An
Hi,
This patchlet adds support for the traditional
./configure && make && make install
There no longer should be a need to set and export the variables AXIOM
and PATH before doing make.
The other version I had was doing a major overhall of toplevel
Makefile. To allow people follow th
Hi,
here are some minor modifications of bookvol1 and ComputerTutorial.
In bookvol1 there were two nearly identical sections about the "%"
macro. I removed one and moved a short explanation to the place "%" is
used the first time.
In ComputerTutorial I changed all occurences of "\<\<" in verbati
Hi Tim,
The toplevel Makefile.dvi gets copied in the installation directory
twice:
* once at part of
all: noweb ${MNT}/${SYS}/bin/Makefile.pamphlet
@ echo 1 making a ${SYS} system, PART=${PART}
SUBPART=${SUBPART}
@ echo 2 Environment ${ENV}
root <[EMAIL PROTECTED]> writes:
| > | patched. fixed in the next release. --t
| > |
| > | (no, i still don't have SVN working. there is no time)
| >
| > Then, please could send a patch to the list?
|
|
| I now have a working subversion and will look at keeping silver
| up to date with patch
On 08/04/2006 11:16 PM, Bill Page wrote:
Ralf,
On August 4, 2006 12:23 PM you wrote:
...
But may I ask you why there is still a link
"Literate Source"
on the FrontPage? What were your reasons for leaving it
just next to "Source Code"? I think that is confusing.
There should be just ONE link
> I guess we should make some kind of effort to coordinate this> and make sure everything is upto date and in sync before deciding
> how best to proceed with large scale edits. No?Yes. Now we have Gold=stable, Silver=unstable, and several testingbranches. See http://wiki.axiom-developer.org/AxiomSo
Oh, that might be true. But what does that help if you want to combine
pamphlets from different authors who use conflicting latex packages???
Obviously, it doesn't. However, I'm hopeful that such conflicts will either
be minimal and easily resolved, or we can improve the latex packages
themse
See my previous email about the
http://wiki.axiom-developer.org/book--main--1
pamphlet files. All of these volumes can be updated directly through
the web. We can create diffs of these against the versions in the
current source distribution and vice versa. Maybe we could even
hack together a go
17 matches
Mail list logo
