summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/xmltex/base/manual.xml
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/xmltex/base/manual.xml')
-rw-r--r--Master/texmf-dist/doc/xmltex/base/manual.xml46
1 files changed, 26 insertions, 20 deletions
diff --git a/Master/texmf-dist/doc/xmltex/base/manual.xml b/Master/texmf-dist/doc/xmltex/base/manual.xml
index aec2851b949..610938913ff 100644
--- a/Master/texmf-dist/doc/xmltex/base/manual.xml
+++ b/Master/texmf-dist/doc/xmltex/base/manual.xml
@@ -35,6 +35,8 @@
<revisionDesc>
<list>
<head></head>
+ <item><date>February 2nd 2000</date>
+ <name>David Carlisle</name>Updated)</item>
<item><date>January 24th 2000</date>
<name>David Carlisle</name>Updated)</item>
<item><date>January 19th 2000</date>
@@ -60,7 +62,7 @@
<titlePart type="main">xmltex: A non validating (and not 100%
conforming) namespace aware XML parser implemented in &TeX;</titlePart>
</docTitle>
- <docDate>Date: 2000-01-24</docDate>
+ <docDate>Date: 2000-02-02</docDate>
<docAuthor rend="email">davidc@nag.co.uk</docAuthor>
<docAuthor>David Carlisle</docAuthor>
</front>
@@ -306,15 +308,11 @@ XML document may also be used (which is loaded immediately after
<div id="stopping">
<head>Stopping xmltex</head>
-<p>In tracing mode, xmltex will stop after the end of the document
-element has been processed. In the normal processing mode xmltex
-does not currently automatically stop &TeX; processing. After
-the document has completed &TeX; will move to the interactive
-<code>*</code> prompt (from which you might want to exit with
-<code><![CDATA[<?xmltex stop?>]]></code>). Normally the
-end code specified for the document element should execute
-<code>\end{document}</code> and so stop processing and avoid the
-<code>*</code> prompt.
+<p>xmltex should stop after the end of the document
+element has been processed. If things go wrong and
+you end up at the interactive
+<code>*</code> prompt you might want to exit with
+<code><![CDATA[<?xmltex \stop?>]]></code>).
</p>
</div>
@@ -455,6 +453,10 @@ the parent of the current element.</p>
argument. It may be particularly useful for redefining `fixed strings'
that are generated by &LaTeX; document classes to use any special
typesetting rules specified for individual characters.</p>
+<p>It should also be used for defining any strings used to
+in comparison tests with strings occurring in the XML document.
+Using <code>\XMLstring</code> rather than <code>\def</code> ensures
+that the characters and encodings in the string are correctly normalised.</p>
</item>
@@ -484,9 +486,10 @@ validating parser. It fails in the following respects.
parsed entities and parameter entities are essentially treated as
&TeX; macros, and nonparsed entities are saved along with their
NDATA type, for use presumably by <code>\includegraphics</code>.</p>
-<p> What is not currently done, but mandated by the XML 1.0
- Recommendation is that default attributes are read from the internal
- subset. (This might be added later.)</p>
+<p>Attribute defaults are processed in the local subset of the dtd, however
+ note that this is `namespace unaware' defaulting and only applies to
+ elements using the same prefix and local name, unlike the defaulting
+ done by <code>\XMLattribute</code>. </p>
</item>
<item><p> Support for encodings depends on having an encoding mapping
file. Any 8bit encoding that matches Unicode for the first 127 positions
@@ -542,12 +545,8 @@ source.</p>
</item>
<item><p> A second different mechanism is available, to use XML processing
instructions. A Processing Instruction of the form:
-<gi>?xmltex</gi> <emph>name</emph> {<emph>arg1</emph>} {<emph>arg1</emph>} &ldots; <code>?></code>
-will be executed as the &TeX; command:
-\<emph>name</emph> {<emph>arg1</emph>} {<emph>arg1</emph>} &ldots;</p>
-<p>Note that <emph>only</emph> the first name will be converted into a &TeX;
-command, any arguments should only contain character strings.
-</p>
+<gi>?xmltex</gi> <emph>&TeX; commands</emph> <code>?></code>
+will execute the &TeX; commands.</p>
</item>
</list>
@@ -696,7 +695,14 @@ For example the code for MathMl frac might be
</item>
<item><p><code>\xmltexthreechildren\csa\csb\csc#1</code></p>
-<p>As above, but more so.</p>
+<p>As above, but more so.</p></item>
+
+<item><p><code>\xmltexforall\csa{#1}</code></p>
+<p>The &TeX; command <code>\csa</code> is called repeatedly,
+taking each child element of the current element as argument
+on each iteration. As a convenience the command <code>\xml@name</code>
+is defined before each iteration to have the (internal, normalised)
+name of the element being processed.</p>
</item>
<item><p><code>\NDATAEntity\csa\csb\attvalue</code></p>