From: Karl Berry Date: Sat, 13 Sep 2025 16:02:51 +0000 (-0700) Subject: autoupdate X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b4855f4ae38143cb5e4b8c32df5f610d70471248;p=thirdparty%2Fgnulib.git autoupdate --- diff --git a/doc/maintain.texi b/doc/maintain.texi index a1cedb713b..893ddb7309 100644 --- a/doc/maintain.texi +++ b/doc/maintain.texi @@ -995,7 +995,7 @@ section which explains the importance of free documentation. Write to When you distribute several manuals together in one software package, their on-line forms can share a single copy of the GFDL (see -section@tie{}6). However, the printed (@samp{.dvi}, @samp{.pdf}, +section@tie{}6). However, the printed (@samp{.pdf}, @dots{}) forms should each contain a copy of the GFDL, unless they are set up to be printed and published only together. Therefore, it is usually simplest to include the GFDL in each manual. @@ -1713,7 +1713,7 @@ installing the diffs). The purpose of having diffs is that they are small. To keep them small, exclude files that the user can easily update. For example, -exclude info files, DVI files, tags tables, output files of Bison or +exclude info files, PDF files, tags tables, output files of Bison or Flex. In Emacs diffs, we exclude compiled Lisp files, leaving it up to the installer to recompile the patched sources. @@ -2597,7 +2597,7 @@ The template files will automatically produce entries for additional HTML output generated by @command{texi2html} (i.e., split by sections and chapters). -You can set the environment variables @env{MAKEINFO}, @env{TEXI2DVI}, +You can set the environment variables @env{MAKEINFO}, @env{TEXI2PDF}, etc., to control the programs that get executed, and @env{GENDOCS_TEMPLATE_DIR} to control where the @file{gendocs_template} file is found.