On 17-3-2010 22:27, Hans van der Meer wrote:
Took me quite some time to discover:
\startxmlsetups xml:common:tex
\xmlflushcontext{#1}{}
\stopxmlsetups
but worthwhile because it seems to do what I wanted.
that's indeed a new one (added recently), there's also a filter:
\xmlfilter{#1}{/whateve
Am 17.03.10 14:20, schrieb Hans van der Meer:
I do not understand the following. Running the Schuster code exactly
as it is, the enclosure works. If however I incorporate
the data from file instead of through \savebuffer, then it doesn't work.
\savebuffer writes the content into the external fi
Took me quite some time to discover:
\startxmlsetups xml:common:tex
\xmlflushcontext{#1}{}
\stopxmlsetups
but worthwhile because it seems to do what I wanted.
Hans van der Meer
On 17 mrt 2010, at 13:46, Hans Hagen wrote:
On 17-3-2010 12:14, Wolfgang Schuste
On 17-3-2010 14:09, Hans van der Meer wrote:
Strange. First ran the Schuster code and got two bold outputs.
Then changing to the Hagen code (xmlraw) the -enclosed code gives:
"This is bold text.
That code doesn't work where the first did. How come?
well, it depends on what you want ... Wolfgang
I do not understand the following. Running the Schuster code exactly
as it is, the enclosure works. If however I incorporate
the data from file instead of through \savebuffer, then it doesn't work.
What crucial detail am I missing here?
Hans van der Meer
On 17 mrt 2010, at 12:14, Wolfgan
Strange. First ran the Schuster code and got two bold outputs.
Then changing to the Hagen code (xmlraw) the -enclosed code gives:
"This is bold text.
That code doesn't work where the first did. How come?
On 17 mrt 2010, at 13:46, Hans Hagen wrote:
On 17-3-2010 12:14, Wolfgang Schuster wrote:
On 17-3-2010 12:14, Wolfgang Schuster wrote:
\startxmlsetups xml:tex
\disableXML
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:tex
\xmlraw{#1}{}
\stopxmlsetups
-
Hans Ha
Am 17.03.10 12:03, schrieb Hans van der Meer:
Yes, I know that and already have made a setup for common commands
like =\bf, =\hairline etc. My point however is: How to avoid
the need to rewrite in this manner all ConTeXt macros one needs?
Maybe there is a way to let ConTeXt interpret the CDATA c
On 17 mrt 2010, at 11:49, Philipp Gesang wrote:
On 2010-03-17 <11:28:30>, Hans van der Meer wrote:
Typesetting material containing macro's from inside a xml-node does
not give TeX-ed results.
How can this be accomplished?
Hi Hans,
I'm using extra tags with setups because no TeX code seems to
On 2010-03-17 <11:28:30>, Hans van der Meer wrote:
> Typesetting material containing macro's from inside a xml-node does
> not give TeX-ed results.
> How can this be accomplished?
Hi Hans,
I'm using extra tags with setups because no TeX code seems to be
processed directly from the xml file.
---8<
Typesetting material containing macro's from inside a xml-node does
not give TeX-ed results.
How can this be accomplished?
Minimal example ConTeXt code:
\startxmlsetups xml:testsetups
\xmlsetsetup{test}{test}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:testsetups}
\startxmlsetups x
11 matches
Mail list logo
