diff options
Diffstat (limited to 'doc/context/sources/general/manuals/xml/xml-mkiv.tex')
| -rw-r--r-- | doc/context/sources/general/manuals/xml/xml-mkiv.tex | 25 |
1 files changed, 21 insertions, 4 deletions
diff --git a/doc/context/sources/general/manuals/xml/xml-mkiv.tex b/doc/context/sources/general/manuals/xml/xml-mkiv.tex index 8550badec..37f321646 100644 --- a/doc/context/sources/general/manuals/xml/xml-mkiv.tex +++ b/doc/context/sources/general/manuals/xml/xml-mkiv.tex @@ -859,7 +859,7 @@ commands that were used when testing this interface and we see no reason to remove them. Some obscure ones are used in modules and after a while even I often forget that they exist. To give you an idea of what commands are important we show their use in generating the \CONTEXT\ command definitions (\type -{x-set-11.mkiv}) per Januari 2016: +{x-set-11.mkiv}) per January 2016: \startcolumns[n=2,balance=yes] \starttabulate[|l|r|] @@ -1502,6 +1502,23 @@ and an \cmdinternal {cd:lpath} as second: {cd:false} otherwise \stopxmlcmd +\startxmlcmd {\cmdbasicsetup{xmldoifatt}} + expands to \cmdinternal {cd:true} when the attribute matching \cmdinternal + {cd:node} and the name given as second argument matches the third argument +\stopxmlcmd + +\startxmlcmd {\cmdbasicsetup{xmldoifnotatt}} + expands to \cmdinternal {cd:true} when the attribute matching \cmdinternal + {cd:node} and the name given as second argument differs from the third + argument +\stopxmlcmd + +\startxmlcmd {\cmdbasicsetup{xmldoifelseatt}} + expands to \cmdinternal {cd:true} when the attribute matching \cmdinternal + {cd:node} and the name given as second argument matches the third argument + and to \cmdinternal {cd:false} otherwise +\stopxmlcmd + \startxmlcmd {\cmdbasicsetup{xmldoifelseempty}} expands to \cmdinternal {cd:true} when the node matching \cmdinternal {cd:lpath} at node \cmdinternal {cd:node} is empty and to \cmdinternal @@ -1814,7 +1831,7 @@ The following then applies: In most cases the \type {position} test is more restrictive than the \type {match} test. -You can pass your own functions too. Such functions are defined in the the \type +You can pass your own functions too. Such functions are defined in the \type {xml.expressions} namespace. We have defined a few shortcuts: \starttabulate[|l|l|] @@ -3366,7 +3383,7 @@ and the second call will give unexpected results. You can overcome this with: \stoptyping Does it pay off? Here are some timings of a 10.000 times text and lookup -like the previous (on a decent Januari 2016 laptop): +like the previous (on a decent January 2016 laptop): \starttabulate[|r|l|] \NC 0.239 \NC \type {\xmldoif {...} {...}} \NC \NR @@ -4332,7 +4349,7 @@ dollars and percent signs would have no special meaning. In fact, it would be rather useless as interpreting commands are triggered by such characters. Any formatting or coding system needs such characters. Take \XML: angle brackets and ampersands are really special. So, no matter what system we use, we do have to -deal with the (common) case where these characters need to be sees as they are. +deal with the (common) case where these characters need to be seen as they are. Normally escaping is the solution. The \CONTEXT\ interface for \XML\ suffers from this as well. You really don't |