Hans,
the attached patch fixes three minor typos in xml-mkiv.tex.
I hope it helps,
Pablo
--
http://www.ousia.tk
--- /home/ousia/ctxbeta/tex/texmf-context/doc/context/sources/general/manuals/xml/xml-mkiv.tex 2018-04-04 00:58:49.000000000 +0200
+++ xml-mkiv.tex 2018-03-22 21:01:00.149431344 +0100
@@ -859,7 +859,7 @@
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|]
@@ -2347,7 +2347,7 @@
\stopxmlcmd
\startxmlcmd {\cmdbasicsetup{xmlinfo}}
- typeset the name in the element given by \cmdinternal {cd:node}
+ typeset the name if the element given by \cmdinternal {cd:node}
\stopxmlcmd
\startxmlcmd {\cmdbasicsetup{xmlpath}}
@@ -3366,7 +3366,7 @@
\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 +4332,7 @@
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
_______________________________________________
dev-context mailing list
[email protected]
https://mailman.ntg.nl/mailman/listinfo/dev-context
