summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html21
1 files changed, 0 insertions, 21 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html
deleted file mode 100644
index ee2ed09f399..00000000000
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html
+++ /dev/null
@@ -1,21 +0,0 @@
-<head>
-<title>UK TeX FAQ -- question label plainvltx</title>
-</head><body>
-<h3>Should I use Plain TeX or LaTeX?</h3>
-<p/>There&rsquo;s no straightforward answer to this question. Many people swear
-by Plain TeX, and produce highly respectable documents using it
-(Knuth is an example of this, of course). But equally, many people
-are happy to let someone else take the design decisions for them,
-accepting a small loss of flexibility in exchange for a saving of
-brain power.
-<p/>The arguments around this topic can provoke huge amounts of noise and
-heat, without offering much by way of light; your best bet is to find
-out what those around you are using, and to go with the crowd. Later
-on, you can always switch your allegiance; don&rsquo;t bother about it.
-<p/>If you are preparing a manuscript for a publisher or journal, ask them
-what markup they want before you
-develop your own; many big publishers have developed their own
-(La)TeX styles for journals and books, and insist that authors stick
-closely to their markup.
-<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plainvltx">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plainvltx</a>
-</body>