summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html18
1 files changed, 9 insertions, 9 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html
index a82c700079c..030afa9e158 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html
@@ -4,9 +4,9 @@
<h3>Makefiles for LaTeX documents</h3>
<p/>LaTeX is a tricky beast for running <i>make</i> on: the need to
instruct LaTeX to run several times for essentially different
-reasons (for example, &ldquo;get the table of contents stable&rdquo;, &ldquo;get the
-labels stable&rdquo;, &ldquo;add the bibliography&rdquo;, &ldquo;add the index&rdquo;) is
-actually rather difficult to express in the &lsquo;ordinary&rsquo; sort of
+reasons (for example, &#8220;get the table of contents stable&#8221;, &#8220;get the
+labels stable&#8221;, &#8220;add the bibliography&#8221;, &#8220;add the index&#8221;) is
+actually rather difficult to express in the &#8216;ordinary&#8217; sort of
dependency graph that one constructs for <i>make</i>.
<p/>The <i>latex-make</i> package offers help with this task (far more
sophisticated techniques than in the FAQ building script); it
@@ -15,35 +15,35 @@ looks good, but reports of its use (other than by its author) are scarce.
was <i>latexmk</i>, which is a <i>Perl</i>
script that analyses your LaTeX source for its dependencies, runs
BibTeX or <i>makeindex</i> as and when it notices that those
-programs&rsquo; input (parts of the <code>.aux</code> file, or the
+programs&#8217; input (parts of the <code>.aux</code> file, or the
<code>.idx</code> file, respectively) has changed, and so on.
<i>Latexmk</i> is a fine
solution (and was used in generating printable versions of these
FAQs for a long time); it has recently been upgraded and has
many bells and whistles that allow it to operate as if it were a poor
-man&rsquo;s WYSIWYG system.
+man&#8217;s WYSIWYG system.
<p/>Apparently along the same lines, is AutoLaTeX. The <i>README</i>
of the distribution is actual a Unix-type man-page output, and shows
great attention to the details of the document production process.
<p/>The <i>mk</i> (also, apparently, known as <i>latex_maker</i>)
is a Ruby script for the task in hand; it works well with another of
-the author&rsquo;s scripts script called <i>vpp</i> (View and Print
+the author&#8217;s scripts script called <i>vpp</i> (View and Print
PostScript/PDF).
-<p/>Windows users of the MiKTeX system may use that system&rsquo;s
+<p/>Windows users of the MiKTeX system may use that system&#8217;s
<i>texify</i> application. <i>Texify</i> deals with basic
LaTeX features, including generating a bibliography and an index;
it makes no claim to deal with other things (such as multiple
bibliographies or indexes, or lists of terminology, etc.), which
AutoLaTeX can be configured to process.
<p/>The <a href="FAQ-texinfo.html"><i>texinfo</i> system</a> comes with a similar
-utility called <i>texi2dvi</i>, which is capable of &ldquo;converting&rdquo;
+utility called <i>texi2dvi</i>, which is capable of &#8220;converting&#8221;
either LaTeX or <i>texinfo</i> files into DVI (or into
PDF, using PDFTeX).
<p/>A later contribution is the bundle <i>latexmake</i>, which
offers a set of <i>make</i> rules that invoke <i>texi2dvi</i>
as necessary.
<p/>The curious may examine the rules employed to run the present
-FAQ through LaTeX: we don&rsquo;t present them as a complete
+FAQ through LaTeX: we don&#8217;t present them as a complete
solution, but some of the tricks employed are surely re-usable.
<dl>
<dt><tt><i>AutoLaTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/autolatex.zip">support/autolatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/autolatex/">browse the directory</a>)