Ralf,
Looks like I misunderstood your question. Try
\ifOption{foo}{...true part...}{...false part...}
-eitan
> Well, that is not my point. I could write those simple things myself.
> The problem is that there is no reliable way to get access to the TeX
> string that appears inside al
Well, that is not my point. I could write those simple things myself.
The problem is that there is no reliable way to get access to the TeX
string that appears inside all the htlatex like scripts.
If I get access to that and also to the parameters of tex4ht and t4ht,
that would make me happy.
Ralf,
Some users devised scripts along the following lines.
latex ...
bibtex...call, if needed
makeindex... call, if needed
latex ...repeat until the dvi file doesn't change
tex4ht ...
t4ht ...
I never tried those scripts, but I believe I have one somewhere
Hi Eitan,
I must admit that I don't quite understand the script htlatex.
It basically has the form
latex ...
latex ...
latex ...
tex4ht ...
t4ht ...
I am somehow missing a call to bibtex and also a call to makeindex.
Is there a script that lets me run just one "latex" part (with the
argument
On November 23, 2005 11:49 PM Tim Daly (root) wrote:
>
> methinks you could help the axiom portal/sandbox/wiki by
> doing what you suggested to ralf. we need a 1-2 page
> executive overview of the axiom site. i didn't know about
> axiom portal's ability to do uploads or i would have
> suggested it
Bill,
methinks you could help the axiom portal/sandbox/wiki by doing
what you suggested to ralf. we need a 1-2 page executive overview
of the axiom site. i didn't know about axiom portal's ability to
do uploads or i would have suggested it.
perhaps posting a couple 1-pagers (man pages?) to axiom-
On November 23, 2005 6:29 PM Tim Daly (root) wrote:
> ...
> C Y wrote:
> > Oh, related question - is there a place where I can upload
> > example pdf and dvi documents?
>
> do you have a userid on axiom-developer.org? we could set up
> one that has web access.
>
A userid on axiom-developer.or
> OK. Would it be alright if I post an example of what I have done, if
> nothing else to outline the issues I would like to address? I'm all
> for better ways to solve them (lord knows I don't know the best ones!)
> but I would like to describe what I have done and why, in case there is
> any mer
--- root <[EMAIL PROTECTED]> wrote:
> CY,
>
> i started a reply to your latex work a while ago but i guess
> i never sent the email. broken down to its essence i have
> objections to using conditional code in a latex document. if
> we start down that path we end up with the whole "C" define
>
On November 23, 2005 1:34 PM Tim Daly (root) wrote:
>
> Ralf Hemmecke wrote:
> > I like that. Does this mean that these volume would also
> > contain all the code? That is exacly what I'd like to see.
>
> yes, each volume subsumes the code for those portions of the
> system. i'm gradually "combi
CY,
i started a reply to your latex work a while ago but i guess i never
sent the email. broken down to its essence i have objections to
using conditional code in a latex document. if we start down that
path we end up with the whole "C" define horror show. C introduced
#ifdef and #include .h, bot
> I like that. Does this mean that these volume would also contain all the
> code? That is exacly what I'd like to see.
yes, each volume subsumes the code for those portions of the system.
i'm gradually "combing" the code into the files.
> Tim you are referring to the license problem. Well, I di
Hi Tim,
one document per file was the original approach and was forced on me
because there was so much to convert. the new plan is to break the
system into volumes. on my machine i currently have 10 book volumes:
vol 1: tutorial
vol 2: programming
vol 3: reference
vol 4: developers guide
> That is fine, or nearly fine, say. ALLPROSE tries to produce one
> document, so all pamphlet files are handed over to noweave as one big
> file so that cross-referencing can be done via hyperref. In fact, also
> noweb adds some cross-references and indices.
one document per file was the origina
--- Ralf Hemmecke <[EMAIL PROTECTED]> wrote:
> What I could provide for Axiom would be to extract several
> parts of ALLPROSE, so that an Axiom developer could produce a
> hyperlinked .dvi file (with "inverse search" enabled, ie,
> clicking on the .dvi file opens your favourite editor and
> jum
root wrote:
despite the missing .sty file it works!
this is cool. we have to import this technology into axiom.
If you like.
of course it appears that you've licensed it under GPL and
we'd need your permission to include it under a second BSD
license.
It took me quite a long time to read th
root wrote:
i downloaded rhxterm.sty, put it in misc and ran texhash.
now it cannot find 'typeoutframed.sty' and neither can google.
I don't use that file. It's just framed.sty.
Ralf
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http
typo in Makefile s/programms/programs/
typo in Makefile s/environemnt/environment/
Thank you for that.
\xALLPROSE{} expands to nothing
\xAldor{} expands to nothing
\xPerl{} expands to nothing
\xNoweb{} expands to nothing
I don't understand. These commands are defined properly in
allprose.sty
That file is not in the allprose distribution. You have to get it from
http://www.hemmecke.de/aldor subpage ALLPROSE. There I list a few style
files that are needed for ALLPROSE.
Maybe I should make my distribution a bit bigger and pack up the other
style files, into the distro. I have not don
19 matches
Mail list logo
