On 7-3-2010 18:29, Philipp Gesang wrote:
So in this case, you would have \xmlinclude{test}{afile}{file}.
Yes, that did it. I thoroughly confused the notion of “lpath” in
xml-mkiv.pdf.
it's not xpath but shares quite some properties with it
To actually make use of inc.xml in the current
On 2010-03-08 10:57:00, Hans Hagen wrote:
On 7-3-2010 18:29, Philipp Gesang wrote:
So in this case, you would have \xmlinclude{test}{afile}{file}.
Yes, that did it. I thoroughly confused the notion of “lpath” in
xml-mkiv.pdf.
it's not xpath but shares quite some properties with it
Well,
On 8-3-2010 13:30, Philipp Gesang wrote:
Will there be documentation on the lua internals? It is tedious tracing
things down all the way through ConTeXt - lxml-ini - lxml-tex -
lxml-aux to find out (or not) what they're supposed to do.
once i know what will be exposed, yes,
Hans
On Mar 8, 2010, at 10:57 AM, Hans Hagen wrote:
xml in mkiv is still somewhat experimental although the commands and
interfaces will stay; the current implementation is the second one and has
the advanage that it stays closer to xpath and also is more roundtrip safe
(tables of contents and
On 8-3-2010 20:33, Thomas A. Schmitz wrote:
On Mar 8, 2010, at 10:57 AM, Hans Hagen wrote:
xml in mkiv is still somewhat experimental although the commands and interfaces
will stay; the current implementation is the second one and has the advanage
that it stays closer to xpath and also is
On 8-3-2010 21:55, Thomas A. Schmitz wrote:
context --environment=ourenvironment maps1.html
ah, context can recognize a couple of suffixes but ignores html so just use
--forcexml
which will add the wrapper (future versions will not use the wrapper but
that's sort of hidden anyway)
we
On Mar 8, 2010, at 10:04 PM, Hans Hagen wrote:
ah, context can recognize a couple of suffixes but ignores html so just use
--forcexml
which will add the wrapper (future versions will not use the wrapper but
that's sort of hidden anyway)
Excellent, I will add this somewhere to the
Hi again,
now that everybody should be back from DANTE2010, I'll try that one
again:
what is the recommended way of including an xml tree from one file in
another? Right now I'm stuck with the following
[ ... ] snip
Personally, I'd prefer some include method like file entities (!ENTITY
Philipp Gesang wrote:
Hi again,
now that everybody should be back from DANTE2010, I'll try that one
again:
what is the recommended way of including an xml tree from one file in
another? Right now I'm stuck with the following
[ ... ] snip
Personally, I'd prefer some include method like file
Good evening,
On 2010-03-07 13:52:34, Taco Hoekwater wrote:
\startxmlsetups xml:afile
\section{Filename \xmlatt{#1}{file}}
%\xmlinclude{test} { } {\xmlatt{#1}{file}}
%\xmlinclude{test} {/*} {\xmlatt{#1}{file}}
%\xmlinclude{test} {/sect}
Hi all,
what is the recommended way of including an xml tree from one file in
another? Right now I'm stuck with the following
\startxmlsetups xml:inc
\xmlprocessfile{inc}{\xmlatt{#1}{file}}{}
\stopxmlsetups
combined with inc file=inc.xml/ in the xml source. But although the
content of
11 matches
Mail list logo
