1 files changed, 84 insertions, 3 deletions
diff --git a/doc/context/sources/general/manuals/xml/xml-mkiv.tex b/doc/context/sources/general/manuals/xml/xml-mkiv.tex
index 80d51532f..0f9c74662 100644
--- a/doc/context/sources/general/manuals/xml/xml-mkiv.tex
+++ b/doc/context/sources/general/manuals/xml/xml-mkiv.tex
@@ -288,7 +288,6 @@ code can be used as starting point:
 
 \starttyping
 \startxmlsetups xml:demo:base
-  \xmlsetsetup{#1}{*}{-}
   \xmlsetsetup{#1}{document|section|p}{xml:demo:*}
 \stopxmlsetups
 
@@ -1275,6 +1274,15 @@ The following commands return strings. Normally these are used in tests.
     returns the last attribute found (this avoids a lookup)
 \stopxmlcmd
 
+\startxmlcmd {\cmdbasicsetup{xmlsetatt}}
+    set the value of attribute \cmdinternal {cd:name}
+\stopxmlcmd
+
+\startxmlcmd {\cmdbasicsetup{xmlsetattribute}}
+    set the value of attribute \cmdinternal {cd:name} for each match of \cmdinternal
+    {cd:lpath}
+\stopxmlcmd
+
 \stopsection
 
 \startsection[title={manipulation}]
@@ -1610,6 +1618,80 @@ mechanism for other purposes as well.
 
 \stopsection
 
+\startsection[title={Parameters}]
+
+\startbuffer[test]
+<something whatever="alpha">
+    <what>
+        beta
+    </what>
+</something>
+\stopbuffer
+
+\startbuffer
+\startxmlsetups xml:mysetups
+    \xmlsetsetup{\xmldocument}{*}{xml:*}
+\stopxmlsetups
+
+\xmlregistersetup{xml:mysetups}
+
+\startxmlsetups xml:something
+    parameter : \xmlpar   {#1}{whatever}\par
+    attribute : \xmlatt   {#1}{whatever}\par
+    text      : \xmlfirst {#1}{what}    \par
+                \xmlsetpar{#1}{whatever}{gamma}
+    parameter : \xmlpar   {#1}{whatever}\par
+    \xmlflush{#1}
+\stopxmlsetups
+
+\startxmlsetups xml:what
+    what: \xmlflush{#1}\par
+    parameter : \xmlparam{#1}{..}{whatever}\par
+\stopxmlsetups
+
+\xmlprocessbuffer{main}{test}{}
+\stopbuffer
+
+Say that we have this \XML\ blob:
+
+\typebuffer[test]
+
+With:
+
+\typebuffer
+
+we get:
+
+\getbuffer
+
+Parameters are stored with a node.
+
+\startxmlcmd {\cmdbasicsetup{xmlpar}}
+    returns the value of parameter \cmdinternal {cd:name} or empty if no such
+    parameter exists
+\stopxmlcmd
+
+\startxmlcmd {\cmdbasicsetup{xmlparam}}
+    finds a first match for \cmdinternal {cd:lpath} at \cmdinternal {cd:node} and
+    returns the value of parameter \cmdinternal {cd:name} or empty if no such
+    parameter exists
+\stopxmlcmd
+
+\startxmlcmd {\cmdbasicsetup{xmllastpar}}
+    returns the last parameter found (this avoids a lookup)
+\stopxmlcmd
+
+\startxmlcmd {\cmdbasicsetup{xmlsetpar}}
+    set the value of parameter \cmdinternal {cd:name}
+\stopxmlcmd
+
+\startxmlcmd {\cmdbasicsetup{xmlsetparam}}
+    set the value of parameter \cmdinternal {cd:name} for each match of \cmdinternal
+    {cd:lpath}
+\stopxmlcmd
+
+\stopsection
+
 \stopchapter
 
 \startchapter[title={Expressions and filters}]
@@ -1779,7 +1861,6 @@ In addition, \type {=} equals \type {==} and \type {!=} is the same as \type
 
 \stopsection
 
-
 \startsection[title={css selectors}]
 
 \startbuffer[selector-001]
@@ -1838,7 +1919,7 @@ supported too. In fact, you can combine both methods. Depending on what you
 select, the \CSS\ one can be a little bit faster too. It has the advantage that
 one can select more in one go but at the same time looks a bit less attractive.
 This method was added just to show that it can be done but might be useful too. A
-selector is gogen between curly braces (after all \CSS\ uses them and they have no
+selector is given between curly braces (after all \CSS\ uses them and they have no
 function yet in the parser.
 
 \starttyping