From: Denis Maier via ntg-context <ntg-context@ntg.nl>
To: <ntg-context@ntg.nl>
Cc: denis.maier@unibe.ch
Subject: Do environment files add implicit \starttext ... \stopttext
Date: Tue, 15 Nov 2022 12:22:06 +0000 [thread overview]
Message-ID: <406fe736fe764a359a33ea605652b8cb@unibe.ch> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1641 bytes --]
Hi,
if I process an XML buffer, I've noticed I need to wrap the \xmlprocessbuffer in a \starttext ... \stoptext pair.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\startbuffer[test]
<?xml version='1.0' standalone='yes?>
<document>
<p>a paragraph of text</p>
<p>another paragraph of text</p>
</document>
\stopbuffer
\startxmlsetups xml:demo
\xmlsetsetup{\xmldocument}{document|p}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:demo}
\startxmlsetups xml:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:p
\xmlflush{#1}\endgraf
\stopxmlsetups
\starttext
\xmlprocessbuffer{test}{test}{}
\stoptext
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
However, if I have the XML and the setups in dedicated files, there seems to be no need for \starttext ... \stoptext.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% text.xml
<?xml version='1.0' standalone='yes?>
<document>
<p>a paragraph of text</p>
<p>another paragraph of text</p>
</document>
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% setups.tex
\startxmlsetups xml:demo
\xmlsetsetup{\xmldocument}{document|p}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:demo}
\startxmlsetups xml:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:p
\xmlflush{#1}\endgraf
\stopxmlsetups
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Running
context text.xml -environment=setups.tex
gives me a proper PDF without errors.
Therefore my question:
Does the use -environment automatically wrap the processed file in \starttext ... stoptext ?
If not, what's the reason for this behaviour? Am I missing something?
Best,
Denis
[-- Attachment #1.2: Type: text/html, Size: 6282 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2022-11-15 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 12:22 Denis Maier via ntg-context [this message]
2022-11-15 15:06 ` Pablo Rodriguez via ntg-context
2022-11-16 9:30 ` Denis Maier via ntg-context
2022-11-18 14:52 ` Wolfgang Schuster via ntg-context
2022-11-18 15:15 ` Pablo Rodriguez via ntg-context
2022-11-16 17:45 ` Wolfgang Schuster via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=406fe736fe764a359a33ea605652b8cb@unibe.ch \
--to=ntg-context@ntg.nl \
--cc=denis.maier@unibe.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).