summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html
index 701145fc5c9..90edef45b5b 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html
@@ -3,15 +3,15 @@
</head><body>
<h3>What is a DVI file?</h3>
<p>A DVI file (that is, a file with the type or extension <code>.dvi</code>) is
-TeX's main output file, using TeX in its broadest sense to
-include LaTeX, etc. 'DVI' is supposed to be an acronym for
+TeX&rsquo;s main output file, using TeX in its broadest sense to
+include LaTeX, etc. &lsquo;DVI&rsquo; is supposed to be an acronym for
DeVice-Independent, meaning that the file can be
printed on almost any
kind of typographic output device. The DVI file is designed to be
read by a driver (<a href="FAQ-driver.html">DVI drivers</a>) to produce
further output designed specifically for a particular printer (e.g., a
LaserJet) or to be used as input to a previewer for display on a
-computer screen. DVI files use TeX's internal coding; a TeX
+computer screen. DVI files use TeX&rsquo;s internal coding; a TeX
input file should produce the same DVI file regardless of which
implementation of TeX is used to produce it.
<p>A DVI file contains all the information that is needed for printing