summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inclplain.html
blob: edf5f310b5ca43a104d6df5f1e96c3798c787c82 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
<head>
<title>UK TeX FAQ -- question label inclplain</title>
</head><body>
<h3>Including Plain TeX files in LaTeX</h3>
<p/>LaTeX, though originally <a href="FAQ-LaTeXandPlain.html">based on Plain TeX</a>, does not
contain all of Plain TeX&rsquo;s commands.  Worse, some Plain TeX
command names appear in LaTeX, with different semantics.  As a
result, special measures need to be taken to allow general Plain TeX
documents (or parts of documents) to be typeset within LaTeX.
<p/>The truly reliable way is to translate the Plain TeX commands, to
produce an equivalent of the original&rsquo;s semantics.  However, this is
not practical in many circumstances, and for those occasions, the
<i>plain</i> package will often come to your aid.  The package
defines a <code>plain</code> environment, in which a Plain TeX
document may be processed:
<blockquote>
<pre>
\begin{plain}
  \input{plain-doc}
\end{plain}
</pre>
</blockquote><p>
The package is known to fail, for example, with documents that use
AMSTeX; no doubt it would also fail if asked to load Eplain.
All these things can be overcome (although it&rsquo;s not often easy), but
the environment saves a lot of work on many occasions.
<dl>
<dt><tt><i>plain.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse the directory</a>)
</dl>
<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain</a>
</body>