summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html15
1 files changed, 8 insertions, 7 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html
index c57bf09c5cc..0c44154df64 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html
@@ -11,18 +11,19 @@ systems. How, then, is a new version of TeX checked?
of tests to check that his software runs: those who port TeX and
its friends to other platforms do indeed perform such tests.
<p/>Knuth, however, provides a &#8216;conformance test&#8217; for both TeX
-(<code>trip</code>) and Metafont (<code>trap</code>).
+(<i>trip</i>) and Metafont (<i>trap</i>).
He characterises these as &#8216;torture tests&#8217;: they are designed not to
check the obvious things that ordinary typeset documents, or font
designs, will exercise, but rather to explore small alleyways off the
main path through the code of TeX. They are, to the casual reader,
pretty incomprehensible!
-<p/>Once an implementation of TeX has passed its <code>trip</code> test, or an
-implementation of Metafont has passed its <code>trap</code> test, then it may
-in principle be distributed as a working version. (In practice, any
-distributor would test new versions against &#8220;real&#8221; documents or
-fonts, too; <code>trip</code> and <code>trap</code> don&#8217;t actually test any
-for real world problems.
+<p/>Once an implementation of TeX has passed its <i>trip</i> test, or
+an implementation of Metafont has passed its <i>trap</i> test, then it
+may in principle be distributed as a working version. (In practice,
+any distributor would test new versions against &#8220;real&#8221; documents or
+fonts, too; while <i>trip</i> and <i>trap</i> test bits of
+pathways within the program, they don&#8217;t actually test for any real
+world problem.)
<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap</a>
</body>