[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Axiom-developer] RE: [Texmacs-dev] Axiom and TeXmacs
From: |
Joris van der Hoeven |
Subject: |
[Axiom-developer] RE: [Texmacs-dev] Axiom and TeXmacs |
Date: |
Sat, 23 Nov 2002 09:19:09 +0100 (MET) |
> > Maybe we should preprocess the pamphlet file using Perl
> > before doing the conversion. I think that Stéphane
> > Payrard might be willing to help us with that.
>
> If I understand you correctly, I do not think a Perl
> filter is a good approach. I have nothing against Perl
> as such, its just that I think the goal should be more
> than loading a pamphlet file into TeXmacs in a readable
> manner.
>
> I think there should be a new File->Import->Pamphlet
> option for this case. The result of importing a pamphlet
> should be a TeXmacs document with a folded structure.
> The code chunks should appear folded into the document so
> that when viewed or printed with a style called "weave"
> for example, the result would be the same as the output
> of
>
> noweave | latex
>
> A different style which displayed the contents of the
> folded chunks could be used for editing. Code chunks
> have to be named and will also have references to
> other code chunks embedded in them.
Well, as I understand it, the pamphlet format is
a LaTeX with special escape sequences for dealing
with code or other special markup. Therefore,
I think that the best way of importing such files
is to first convert it to standard LaTeX
(with possible pamphlet-specific commands),
with a language like Perl, and next convert
the result to TeXmacs using the standard input filter.
> Perhaps it would be nicer if TeXmacs was able to
> expand and collapse folds on demand. It is not really
> clear to me hold folding is intended to work in TeXmacs.
> I wasn't able to find any documentation about it and
> my experiments with it so far have not produced a clear
> picture. Perhaps it is still largely in the planning
> stage?
Yes, this will be dealt with sometime next year.
> Finally there should be an new File->Export->Tangle
> menu option that would generate code and be equivalent
> to
>
> notangle
>
> which expands the code chunks starting with the root
> <<*>>= and including all the referenced code chunks
> in the whole tree structure.
Yes, that should not be difficult.
> We could also have a Tools->Selections->Export->Tangle
> option that applies notangle starting with a selected
> code chunk instead of the root.
Yes, we systematically do that for all formats.
> > > Joris, can you point me at some specific part of
> > > the TeXmacs docs that will help us develop a pamphlet
> > > "style" file. A style file that properly handle
> > > noweb vanilla output would be quite useful.
> >
> > Help -> Styles
> >
> > Unfortunately, the documentation is very incomplete,
> > because the support for writing style files will be
> > much improved at a not yet specified date...
>
> Perhaps it would help to be able to look at some
> existing styles that do something similar to what
> we want. What would you recommend?
I think that we first need to know what you already have.
Also: how much documentation does already exist in
the pamphlet format?