latexmk (3jul13)

git-svn-id: svn://tug.org/texlive/trunk@31087 c570f23f-e606-0410-a88d-b1316a301751

2 files changed, 211 insertions, 61 deletions

diff --git a/Master/texmf-dist/doc/man/man1/latexmk.1 b/Master/texmf-dist/doc/man/man1/latexmk.1
index 64567ed25f4..0a64141cebd 100644
--- a/Master/texmf-dist/doc/man/man1/latexmk.1
+++ b/Master/texmf-dist/doc/man/man1/latexmk.1
@@ -1,4 +1,4 @@
-.TH LATEXMK 1L "11 November 2012" ""
+.TH LATEXMK 1L "2 July 2013" ""
 .SH NAME
 latexmk \- generate LaTeX document
 .SH SYNOPSIS
@@ -18,27 +18,29 @@ By default \fIlatexmk\fR will run the commands necessary to generate
 a .dvi file.
 .PP
 \fILatexmk\fR can also be set to run continuously with a suitable
-previewer.  In that case the LaTeX program, etc, are rerun whenever
+previewer.  In that case the \fIlatex\fR program (or one of its
+relatives), etc, are rerun whenever
 one of the source files is modified, and the previewer automatically
 updates the on-screen view of the compiled document.
 .PP
 \fILatexmk\fR determines which are the source files by examining the
 log file.  (Optionally, it also examines the list of input and output
 files generated by the \fB-recorder\fR option of modern versions of
-\fIlatex\fR and \fIpdflatex\fR.  See the documentation for the
-\fB-recorder\fR option of \fIlatexmk\fR below.)
-When \fIlatexmk\fR is run, it examines properties of the
+\fIlatex\fR (and \fIpdflatex\fR, \fIxelatex\fR, \fIlualatex\fR, etc).
+See the documentation for the \fB-recorder\fR option of \fIlatexmk\fR
+below.)  When \fIlatexmk\fR is run, it examines properties of the
 source files, and if any have been changed since the last document
 generation, \fIlatexmk\fR will run the various LaTeX processing
-programs as necessary.  In particular, it will repeat the run of LaTeX
-(or pdflatex) often enough to resolve all cross references; depending
-on the macro packages used.  With some macro packages and document
-classes, four, or even more, runs may be needed. If necessary,
-\fIlatexmk\fR will also run bibtex, biber, and/or makeindex.  In addition,
-\fIlatexmk\fR can be configured to generate other necessary files.
-For example, from an updated figure file it can automatically generate
-a file in encapsulated postscript or another suitable format for
-reading by LaTeX.
+programs as necessary.  In particular, it will repeat the run of
+\fIlatex\fR (or a related program)) often enough to resolve all cross
+references; depending on the macro packages used.  With some macro
+packages and document classes, four, or even more, runs may be
+needed. If necessary, \fIlatexmk\fR will also run \fIbibtex\fR,
+\fIbiber\fR, and/or \fImakeindex\fR.  In addition, \fIlatexmk\fR can
+be configured to generate other necessary files.  For example, from an
+updated figure file it can automatically generate a file in
+encapsulated postscript or another suitable format for reading by
+LaTeX.
 .PP
 \fILatexmk\fR has two different previewing options.  In the simple
 \fB-pv\fR option, a dvi, postscript or pdf previewer is automatically
@@ -58,8 +60,8 @@ updating the .dvi (and possibly the .ps and .pdf) file, and refreshing
 the previewer's display.  It's not quite WYSIWYG, but usefully close.
 .PP
 For other previewers, the user may have to manually make the previewer
-update its display, which can be (some versions of xdvi and gsview) as
-simple as forcing a redraw of its display.
+update its display, which can be (some versions of \fIxdvi\fR and
+\fIgsview\fR) as simple as forcing a redraw of its display.
 .PP
 \fILatexmk\fR has the ability to print a banner in gray diagonally
 across each page when making the postscript file.  It can also, if
@@ -81,7 +83,7 @@ according to the operating system, so \fIlatexmk\fR often works
 without special configuration on MS-Windows, cygwin, Linux, OS-X, and
 other UNIX systems (notably Solaris).
 .PP
-A very annoying complication handled very reliably by \fILatexmk\fR,
+A very annoying complication handled very reliably by \fIlatexmk\fR,
 is that LaTeX is a multiple pass system.  On each run, LaTeX reads in
 information generated on a previous run, for things like cross
 referencing and indexing.  In the simplest cases, a second run of
@@ -104,18 +106,37 @@ In general the command line to invoke \fIlatexmk\fR has the form
 All options can be introduced by single or double "-" characters,
 e.g., "latexmk -help" or "latexmk --help".
 
-\fBNote\fR: In addition to the options in the list below,
+\fBNote 1\fR: In addition to the options in the list below,
 \fIlatexmk\fR recognizes almost all the options recognized by the
-\fIlatex\fR and \fIpdflatex\fR programs in one of both of their
+\fIlatex\fR, \fIpdflatex\fR programs (and their relatives) in their 
 current TeXLive and MiKTeX implementations.  Some of the options for
 these programs also trigger special action or behavior by
-\fIlatexmk\fR, in which case they are in this list.  Otherwise, they
+\fIlatexmk\fR, in which case they have specific explanations in this
+document.  Otherwise, they 
 are just passed through to a called \fIlatex\fR or \fIpdflatex\fR
 program. Run \fIlatexmk\fR with the \fB-showextraoptions\fR to get a
 list of the options that \fIlatexmk\fR accepts and that are simply
-passed through to \fIlatex\fR or \fIpdflatex\fR.  See also the
+passed through to \fIlatex\fR or \fIpdflatex\fR (etc).  See also the
 explanation of the \fB-showextraoptions\fR option for more
-information. 
+information.
+
+\fBNote 2\fR: In this documentation, the program \fIpdflatex\fR is often
+referred to.  Users of programs like \fIlualatex\fR and \fIxelatex\fR
+should know that from \fIlatexmk\fR's point of view, these other
+programs behave like \fIpdflatex\fR, i.e., they make a pdf file from a
+tex file, etc.  So whenever \fIpdflatex\fR is mentioned without
+mention of the other programs, the statements apply equally to
+\fIlualatex\fR, \fIxelatex\fR, and any other similar programs.
+\fILatexmk\fR can be easily configured to use whichever of these
+programs is needed.  See the documentation for the following options:
+\fB-pdflatex="COMMAND"\fR,
+\fB-lualatex\fR, and
+\fB-xelatex\fR,
+and also see the documentation for the 
+\fI$pdflatex\fR configuration variable.
+At present \fIlatexmk\fR cannot do automatic detection of which
+program is to be used.
+ 
 
 \fBDefinitions of options and arguments\fR
 
@@ -221,7 +242,7 @@ combination of log files, aux files, \fIlatexmk\fR's database file of
 source file information, 
 and those with extensions
 specified in the \fI@generated_exts\fR configuration variable.  In addition,
-files with extensions by the \fI$clean_ext\fR configuration variable are
+files specified by the \fI$clean_ext\fR configuration variable are
 removed.  
 
 This cleanup is instead of a regular make.  See the \fB-gg\fR option
@@ -237,7 +258,7 @@ dependencies and are also deleted.  Otherwise these files are not deleted.
 .B -C
 Clean up (remove) all regeneratable files generated by \fIlatex\fR and
 \fIbibtex\fR or \fIbiber\fR.  This is the same as the \fB-c\fR option with the
-addition of dvi, postscript and pdf files, and those with extensions
+addition of dvi, postscript and pdf files, and those specified
 in the \fI$clean_full_ext\fR configuration variable.
 
 This cleanup is instead of a regular make.  See the \fB-gg\fR option
@@ -254,6 +275,26 @@ dependencies and are also deleted.  Otherwise these files are not deleted.
 (Obsolete).  Now equivalent to the \fB-C\fR option.  See that option
 for details. 
 .TP 
+.B -cd
+Change to the directory containing the main source file before processing
+it.  Then all the generated files (aux, log, dvi, pdf, etc) will be
+relative to the source file.  
+
+This option is particularly useful when \fIlatexmk\fR is invoked from
+a GUI configured to invoke \fIlatexmk\fR with a full pathname for the
+source file.
+.TP 
+.B -cd-
+Do NOT change to the directory containing the main source file before processing
+it.  Then all the generated files (aux, log, dvi, pdf, etc) will be
+relative to the current directory rather than the source file.  
+
+This is the default behavior and corresponds to the behavior of the
+\fIlatex\fR and \fIpdflatex\fR programs.  However, it is not desirable
+behavior when \fIlatexmk\fR is invoked by a GUI configured to invoke
+\fIlatexmk\fR with a full pathname for the source file.  See the
+\fB-cd\fR option.
+.TP 
 .B -CF
 Remove the file containing the database of source file information,
 before doing the other actions requested.
@@ -380,6 +421,14 @@ Force \fIlatexmk\fR to continue document processing despite errors.
 Normally, when \fIlatexmk\fR detects that LaTeX or another program has
 found an error which will not be resolved by further processing, no
 further processing is carried out.
+
+Note: "Further processing" means the running of other programs or the
+rerunning of \fIlatex\fR (etc) that would be done if no errors had
+occurred.  If instead, or additionally, you want the \fIlatex\fR (etc)
+program not to pause for user input after an error, you should arrange
+this by an option that is passed to the program, e.g., by
+\fIlatexmk\fR's option \fB-interaction=nonstopmode\fR.
+
 .TP
 .B -f-
 Turn off the forced processing-past-errors such as is set by the
@@ -408,7 +457,7 @@ Set the basename of output files(s) to STRING, instead of the default,
 which is the basename of the specified TeX file.
 
 This is like the same option for current implementations of the
-\fIlatex\fR and \fIpdflatex\fR, and the passing of this option to
+\fIlatex\fR, \fIpdflatex\fR, etc, and the passing of this option to
 these programs is part of \fIlatexmk\fR's implementation of
 \fB-jobname\fR.
 
@@ -427,7 +476,7 @@ This sets the string specifying the command to run latex, and is
 typically used to add desired options.  Since the string normally
 contains spaces, it should be quoted, e.g.,
 
-     latex -latex="latex --shell-escape %O %S"  foo.tex
+     latexmk -latex="latex --shell-escape %O %S"  foo.tex
 
 The specification of the contents of the string are the same as for
 the \fI$latex\fR configuration variable.  Depending on your
@@ -442,6 +491,14 @@ Note that the effect of this option can also be achieved by using
 the \fB-e\fR option with a suitable line of Perl code to set the
 \fI$latex\fR variable.  See the explanation of the \fB-e\fR option.
 .TP
+.B -lualatex
+Use lualatex.  That is, use lualatex to process the source file(s) to
+pdf (in place of pdflatex).  This option is exactly equivalent to
+specifying the following sequence of options: 
+
+     -pdflatex="lualatex %O %S" -pdf -dvi- -ps-
+
+.TP
 .B -M
 Show list of dependent files after processing.  This is equivalent to
 the \fB-deps\fR option.
@@ -524,10 +581,14 @@ to see how to set the commands for printing.
 This option is incompatible with the \fB-pv\fR and \fB-pvc\fR options,
 so it turns them off. 
 .TP
+
 .B -pdf
-Generate pdf version of document using pdflatex.  (See the
-\fB-xelatex\fR if you wish to use \fIxelatex\fR to make your pdf
-file(s).) 
+Generate pdf version of document using \fIpdflatex\fR.  (If you wish
+to use \fIlualatex\fR or \fIxelatex\fR, you can use whichever of the
+options \fB-lualatex\fR or \fB-xelatex\fR applies.)  To configure
+\fIlatexmk\fR to have such behavior by default, see the section on 
+"Configuration/initialization (rc) files".
+
 .TP
 .B -pdfdvi
 Generate pdf version of document from the dvi file, by default using dvipdf.
@@ -547,7 +608,7 @@ This sets the string specifying the command to run pdflatex, and is
 typically used to add desired options.  Since the string normally
 contains spaces, it should be quoted, e.g.,
 
-     latex -pdf -pdflatex="pdflatex --shell-escape %O %S"  foo.tex
+     latexmk -pdf -pdflatex="pdflatex --shell-escape %O %S"  foo.tex
 
 The specification of the contents of the string are the same as for
 the \fI$pdflatex\fR configuration variable.  Depending on your
@@ -555,8 +616,19 @@ operating system and the command-line shell you are using, you may
 need to change the single quotes to double quotes (or something
 else). 
 
-To set the command for running latex (rather than the command for
-pdflatex) see the \fB-latex\fR option.
+This option can also be used to set a program to be used instead of
+the standard \fIpdflatex\fR program, e.g., 
+
+     latexmk -pdf -pdflatex="lualatex %O %S"  foo.tex
+
+to use \fIlualatex\fR or
+
+     latexmk -pdf -pdflatex="xelatex %O %S"  foo.tex
+
+to use \fIxelatex\fR.
+
+To set the command for running \fIlatex\fR (rather than the command
+for \fIpdflatex\fR) see the \fB-latex\fR option.
 
 Note that the effect of this option can also be achieved by using
 the \fB-e\fR option with a suitable line of Perl code to set the
@@ -776,14 +848,17 @@ Set the kind of file used when previewing is requested (e.g., by the
 \fB-pv\fR or \fB-pvc\fR switches).  The default is to view the "highest"
 kind of requested file (in the order dvi, ps, pdf).  
 .TP
+
 .B -xelatex
 Use xelatex.  That is, use xelatex to process the source file(s) to
 pdf (in place of pdflatex).  This option is exactly equivalent to
 specifying the following sequence of options: 
 
-     -pdflatex="xelatex %O %S" -pdf -dvi- -ps
+     -pdflatex="xelatex %O %S" -pdf -dvi- -ps-
 
 .PP
+\fBCompatibility between options\fR
+
 The preview-continuous option \fB-pvc\fR can only work with one file.
 So in this case you will normally only specify one filename on
 the command line.  
@@ -813,6 +888,62 @@ each of these options turns the others off.
 					.pdf, .ps & .bbl files\fR
 
 
+.SH HOW TO CHANGE THE WAY LATEXMK BEHAVES, DEALING WITH PROBLEMS, ETC
+
+Some possibilities:
+
+a. If you get a strange error, do look carefully at the output that is
+on the screen and in log files.  While there is much that is
+notoriously verbose in the output of \fIlatex\fR (and that is added to
+by \fIlatexmk\fR), the verbosity is there for a reason: to enable the
+user to diagnose problems.  \fILatexmk\fR does repeat some messages at
+the end of a run that it thinks would otherwise be easy to miss in the
+middle of other output. 
+
+b. If \fIlatexmk\fR doesn't do things the way you would like, the
+first step in finding out what to do is to look in this documentation
+at the list of command line options and then at the sections on
+configuration/initialization files.  A lot of \fIlatexmk\fR's behavior
+is configurable to deal with particular situations.  (But there is a
+lot of reading.)
+
+c. Further tricks can involve replacing the standard commands that
+\fIlatexmk\fR by other commands or scripts.
+
+d. For possible examples of code for use in an RC file, see the
+directory example_rcfiles in the distribution of \fIlatexmk\fR (e.g.,
+at http://www.ctan.org/tex-archive/support/latexmk/example_rcfiles).
+Even if these examples don't do what you want, they may provide
+suitable inspiration.
+
+e. There's a useful trick that can be used when you are \fIlualatex\fR
+instead of \fIpdflatex\fR (and in some related situations).  The
+problem is that \fIlatexmk\fR won't notice a dependency on a file,
+bar.baz say, that is input by the lua code in your document instead of
+by the LaTeX part.  (Thus if you change bar.baz and rerun
+\fIlatexmk\fR, then \fIlatexmk\fR will think no files have changed and
+not rerun \fIlualatex\fR, whereas if you had '\\input{bar.baz}' in the
+LaTeX part of the document, \fIlatexmk\fR would notice the change.)
+One solution is just to put the following somewhere in the LaTeX part
+of the document:
+
+              \\typeout{(bar.baz)}
+
+This puts a line in the log file that \fIlatexmk\fR will treat as
+implying that the file bar.baz was read.  (At present I don't know a
+way of doing this automatically.)  Of course, if the file has a
+different name, change bar.baz to the name of your file.
+
+f. Look on tex.stackexchange, i.e., at
+http://tex.stackexchange.com/questions/tagged/latexmk  Someone may
+have already solved your problem.
+
+g. Ask a question at tex.stackexchange.com.
+
+h. Or ask me (the author of \fIlatexmk\fR).  My e-mail is at the end
+of this documentation.
+
+
 .SH CONFIGURATION/INITIALIZATION (RC) FILES
 .PP
 \fILatexmk\fR can be customized using initialization files, which are
@@ -825,7 +956,7 @@ system RC file, in the following order, and reads the first it finds:
    "/usr/local/share/latexmk/LatexMk",
    "/usr/local/lib/latexmk/LatexMk".
    On a MS-WINDOWS system it looks for "C:\\latexmk\\LatexMk".
-   On a cygwin system (i.e., a MS-Windows system in which perl is
+   On a cygwin system (i.e., a MS-Windows system in which Perl is
 that of cygwin), \fIlatexmk\fR reads for the first it finds of
    "/cygdrive/c/latexmk/LatexMk",
    "/opt/local/share/latexmk/LatexMk",
@@ -864,7 +995,7 @@ overridden by later options on the command line.  There is also the
 \fI
 For possible examples of code for in an RC file, see the directory
 example_rcfiles in the distribution of latexmk (e.g., at
-http://ctan.tug.org/tex-archive/support/latexmk/example_rcfiles).
+http://www.ctan.org/tex-archive/support/latexmk/example_rcfiles).
 \fR
 
 .SH HOW TO SET VARIABLES IN INITIALIZATION FILES
@@ -1042,7 +1173,7 @@ about the rules for dealing with forward slashes in strings in the
 Perl language.)
 
 \fBCommand names under Cygwin\fR: If latexmk is executed by Cygwin's
-perl, \fI be particularly certain that pathnames in commands have
+Perl, \fI be particularly certain that pathnames in commands have
 \fBforward\fI slashes\fR not the usual backslashes for the separator
 of pathname components.  See the above examples.  Backslashes often
 get misinterpreted by the Unix shell used by Cygwin's Perl to execute
@@ -1284,14 +1415,15 @@ The value of this variable is a string containing the extensions
 separated by spaces.
 
 It is also possible to specify a more general pattern of file to be
-deleted, by using the place holder %R, as in commands.  Thus setting
+deleted, by using the place holder %R, as in commands, and it is also
+possible to use wildcards.  Thus setting
 
-   $clean_ext = "out %R-blx.bib";
+   $clean_ext = "out %R-blx.bib %R-figures*.log";
 
 in an initialization file will imply that when a clean-up operation is
 specified, not only is the standard set of files deleted, but also
-files of the form FOO.out and FOO-blx.bib, where FOO stands for the
-basename of the file being processed (as in FOO.tex).
+files of the form FOO.out, FOO-blx.bib, and %R-figures*.log, where FOO
+stands for the basename of the file being processed (as in FOO.tex).
 
 .TP
 .B $clean_full_ext [""]
@@ -1380,6 +1512,13 @@ match.
 .B $dependents_list [0]
 Whether to display a list(s) of dependencies at the end of a run.
 .TP
+.B $do_cd [0]
+Whether to change working directory to the directory specified for the
+main source file before processing it.  The default behavior is not to
+do this, which is the same as the behavior of \fIlatex\fR and
+\fIpdflatex\fR programs.  This variable is set by the \fB-cd\fR and
+\fB-cd-\fR options on \fIlatexmk\fR's command line.
+.TP
 .B $dvi_filter [empty]
 The dvi file filter to be run on the newly produced dvi file before
 other processing.  Equivalent to specifying the \fB-dF\fR option.
@@ -1540,7 +1679,7 @@ postscript file (an "eps" file) to be made that is to be read in on
 the next run.  The file contains a comment line giving its creation
 date and time.  On the next run the time changes, \fIlatex\fR sees
 that the eps file has changed, and therefore reruns latex.  This
-causes an infinite loop, that is only terminated becaues \fIlatexmk\fR
+causes an infinite loop, that is only terminated because \fIlatexmk\fR
 has a limit 
 on the number of runs to guard against pathological situations.
 
@@ -1573,7 +1712,7 @@ to be ignored.
 
 It may happen that a pattern to be ignored is specified in, for
 example, in a system or user initialization file, and you wish to
-remove this in a file read later.  To do this, you use perl's delete
+remove this in a file read later.  To do this, you use Perl's delete
 function, e.g.,
 
     delete $hash_calc_ignore_pattern{'eps'};
@@ -1767,26 +1906,37 @@ Equivalent to the \fB-pdf-\fR, \fB-pdf\fR, \fB-pdfdvi\fR,
 .TP
 
 .B $pdflatex ["pdflatex %O %S"]
-The LaTeX processing program in the version that makes a pdf file instead
+The LaTeX processing program in a version that makes a pdf file instead
 of a dvi file.
 
-An example of the use of this variable is to arrange for \fIxelatex\fR
-to be used instead of \fIpdflatex\fR, when you could set
+An example of the use of this variable is to arrange for 
+\fIlualatex\fR, \fIxelatex\fR or some similar program
+to be used instead of \fIpdflatex\fR.  
+Note that \fIlualatex\fR and \fIxelatex\fR only produce .pdf files
+(and not .dvi), so to use them you will also need to turn on
+production of .pdf files, and to turn off the production of .dvi
+(and .ps) files, either by command line options or by suitable
+settings in a configuration file. Thus to use \fIlualatex\fR, the
+following settings are appropriate:
+
+     $pdflatex = "lualatex %O %S";
+     $pdf_mode = 1; $postscript_mode = $dvi_mode = 0;
+
+To use \fIxelatex\fR, the corresponding settings are:
 
      $pdflatex = "xelatex %O %S";
+     $pdf_mode = 1; $postscript_mode = $dvi_mode = 0;
 
-Note that \fIxelatex\fR only produces .pdf files (and not .dvi), so to
-use it you will also need to turn on production of .pdf files, and to
-turn off the production of .dvi (and .ps) files, either by command
-line options or by the following settings in an initialization file
+Another use of the same variable is to add certain options to the
+command line for the program, e.g.,
 
-    $pdf_mode = 1; $postscript_mode = $dvi_mode = 0;
+     $pdflatex = "pdflatex --shell-escape %O %S";
 
 
 .TP
 .B %pdflatex_input_extensions
 This variable specifies the extensions tried by latexmk when it finds
-that a pdfLaTeX run resulted in an error that a file has not been found,
+that a pdflatex run resulted in an error that a file has not been found,
 and the file is given without an extension.  This typically happens when
 LaTeX commands of the form \\input{file} or \\includegraphics{figure},
 when the relevant source file does not exist.
@@ -1967,7 +2117,7 @@ with .ps files.)
 Note that gv could be used with the -watch option updates its display
 whenever the postscript file changes, whereas ghostview does not.
 However, different versions of gv have slightly different ways of
-writing this option.  You can configure this variable apppropriately.
+writing this option.  You can configure this variable appropriately.
 
 \fBWARNING\fR: Linux systems may have installed one (or more) versions
 of gv under different names, e.g., ggv, kghostview, etc, but perhaps
@@ -2185,7 +2335,7 @@ external program; this can be done by following the templates below,
 even by those without knowledge of the \fIPerl\fR programming language.  Of
 course, experts could do something much more elaborate.
 
-One other item in each custom-dependency rule labelled "must" above
+One other item in each custom-dependency rule labeled "must" above
 specifies how the rule should be applied when the source file fails to
 exist.
 
@@ -2193,7 +2343,7 @@ A simple and typical example of code in an initialization rcfile is
 
     add_cus_dep( 'fig', 'eps', 0, 'fig2eps' );
     sub fig2eps {
-        system( "fig2dev -Leps \"$_[0].fig\" \"$_[0].eps\"" ); 
+        system( "fig2dev -Leps \\"$_[0].fig\\" \\"$_[0].eps\\"" ); 
     }
 
 The first line adds a custom dependency that converts a file with
@@ -2227,12 +2377,12 @@ replace the above code in an initialization file by
 
     add_cus_dep( 'fig', 'pdf, 0, 'fig2pdf' );
     sub fig2pdf {
-        system( "fig2dev -Lpdf \"$_[0].fig\" \"$_[0].pdf\"" ); 
+        system( "fig2dev -Lpdf \\"$_[0].fig\\" \\"$_[0].pdf\\"" ); 
     }
 
 \fBNote 1:\fR In the command lines given in the system commands in the
 above examples, double quotes have been inserted around the file names
-(implemented by '\"' in the Perl language).  They immunize the running
+(implemented by '\\"' in the Perl language).  They immunize the running
 of the program against special characters in filenames.  Very often
 these quotes are not necessary, i.e., they can be omitted.  But it is
 normally safer to keep them in.  Even though the rules for quoting
@@ -2280,7 +2430,7 @@ happen:
 
     add_cus_dep('ndx', 'nnd', 0, 'makendx2nnd');
     sub makendx2nnd {
-        system( "makeindex -o \"$_[0].nnd\" \"$_[0].ndx"\" );
+        system( "makeindex -o \\"$_[0].nnd\\" \\"$_[0].ndx\\"" );
     }
 
 (You will need to modify this code if you use filenames
@@ -2318,7 +2468,7 @@ of \fI.fig\fR files to \fI.eps\fR files:
 
     push @cus_dep_list, "fig eps 0 fig2eps";
     sub fig2eps {
-        system( "fig2dev -Lps \"$_[0].fig\" \"$_[0].eps\"" );
+        system( "fig2dev -Lps \\"$_[0].fig\\" \\"$_[0].eps\\"" );
     }
 
 This method still works, and is equivalent to the earlier code using
@@ -2343,7 +2493,7 @@ the standard \fImake\fR program.  Second is that in a large document
 the set of source files can change quite frequently, particularly with
 included graphics files; in this situation keeping a Makefile manually
 updated is inappropriate and error-prone, especially when the
-depedencies can be determined automatically.  \fILatexmk\fR solves
+dependencies can be determined automatically.  \fILatexmk\fR solves
 both of these problems robustly.
 
 Thus for many standard LaTeX documents \fIlatexmk\fR can be used by
@@ -2491,10 +2641,10 @@ e-mail addresses are not written in their standard form to avoid being
 harvested by worms and viruses.)
 .SH AUTHOR
 Current version, by John Collins (username collins at node phys.psu.edu).
-(Version 4.35).
+(Version 4.37).
 
 Released version can be obtained from CTAN:
-<http://www.tug.org/tex-archive/support/latexmk/>, and from the
+<http://www.ctan.org/tex-archive/support/latexmk/>, and from the
 author's website <http://www.phys.psu.edu/~collins/software/latexmk/>.
 .br
 Modifications and enhancements by Evan McLean (Version 2.0)
diff --git a/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf b/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf
index ef8865a68b3..5b68a02a09e 100644
--- a/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf
+++ b/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf