1 files changed, 19 insertions, 19 deletions
diff --git a/tex/context/base/xtag-pre.tex b/tex/context/base/xtag-pre.tex
index 71ea6d04f..5491c3e7c 100644
--- a/tex/context/base/xtag-pre.tex
+++ b/tex/context/base/xtag-pre.tex
@@ -1,5 +1,5 @@
 %D \module
-%D   [       file=xtag-pre,
+%D   [       filefile=xtag-pre,
 %D        version=2000.12.20,
 %D          title=\CONTEXT\ XML Support,
 %D       subtitle=Predefined Things,
@@ -92,8 +92,8 @@
 \def\setupXMLfile{\dodoubleargument\getparameters[\??xf]}
 
 \setupXMLfile
-  [\c!tussen=\blanko,
-   \c!niveau=1]
+  [\c!inbetween=\blank,
+   \c!level=1]
 
 \fetchruntimecommand\showXMLfile  {\f!xtagprefix\s!run}
 \fetchruntimecommand\showXMLbuffer{\f!xtagprefix\s!run}
@@ -116,20 +116,20 @@
 
 %D The comment escape has the form:
 %D
-%D \starttypen
+%D \starttyping
 %D <!-- a couple of remarks -->
-%D \stoptypen
+%D \stoptyping
 
 \defineXMLescape [--] {\gobbleuntil{-->}}
 
 %D The \type {CDATA} escape is kind of unique in its
 %D strange syntax.
 %D
-%D \starttypen
+%D \starttyping
 %D <!CDATA[it starts here
 %D whatever you like to be shown verbatim
 %D and ends here]]>
-%D \stoptypen
+%D \stoptyping
 %D
 %D Watch this rather obscure definition (we need to pass an
 %D \type {[} to the macro.
@@ -155,11 +155,11 @@
 \defineXMLescape [CDATA]
   {\executeifdefined{XMLcdatamethod\number\XMLcdatamethod}{\begingroup\processXMLcdata}}
 
-%D \starttypen
+%D \starttyping
 %D <!ENTITY crap "very new [&#x7B;] crap">
 %D <!ENTITY crap SYSTEM "crapfile.xml">
 %D <!ENTITY crap SYSTEM "crapfile.pdf" NDATA ignoredanyway>
-%D \stoptypen
+%D \stoptyping
 
 \defineXMLescape [ENTITY] \handleXMLentityescape
 
@@ -275,7 +275,7 @@
 %D because the possibility to process \CONTEXT\ commands is
 %D gone.
 
-\setupXMLprocessing[\c!commando=\v!ja]
+\setupXMLprocessing[\c!command=\v!yes]
 
 %\def\contextXMLcommand#1%
 %  {\doif\@@xpcommando\v!ja
@@ -286,7 +286,7 @@
 %      \popmacro\disableXML}}
 
 \def\contextXMLcommand#1% we don't use #1 here
-  {\doif\@@xpcommando\v!ja
+  {\doif\@@xpcommand\v!yes
      {\disableXML\scantokens\@EA{\currentXMLprocess}\enableXML}}
 
 %D The indirect method (using the macro \type
@@ -295,9 +295,9 @@
 %D definition, and given that \ETEX\ is used, we can now
 %D say:
 %D
-%D \starttypen
+%D \starttyping
 %D <?context-command {\bf Start Of Some \TeX\ Text} ?>
-%D \stoptypen
+%D \stoptyping
 %D
 %D A non||\ETEX\ solution is also possible, using buffers,
 %D but for the moment we assume that \ETEX\ is used.
@@ -359,24 +359,24 @@
 
 %D Say that a file contains blocks like the following:
 %D
-%D \starttypen
+%D \starttyping
 %D <?context-block begin whatevername ?>
 %D
 %D <to/> <be> <or/> maybe <not/> so much <to/> </be>
 %D
 %D <?context-block end whatevername ?>
-%D \stoptypen
+%D \stoptyping
 %D
 %D The following commands will show only this block:
 %D
-%D \starttypen
+%D \starttyping
 %D \videXMLcontextblock[whatevername] \showXMLfile{yourfile}
-%D \stoptypen
+%D \stoptyping
 %D
 %D You can also mark blocks in the following way, thereby
 %D saving yourself some work:
 %D
-%D \starttypen
+%D \starttyping
 %D <?context-block what ?>
 %D
 %D <what>What do you want?</what>
@@ -386,7 +386,7 @@
 %D <how>How do you want?</how>
 %D
 %D <?context-block done ?>
-%D \stoptypen
+%D \stoptyping
 
 % yet undocumented and experimental