[latex3-commits] [git/LaTeX3-latex3-hyperref] develop, testthm: update documentation, changelog (a1fbd69)

Ulrike Fischer fischer at troubleshooting-tex.de
Wed Apr 19 16:36:57 CEST 2023


Repository : https://github.com/latex3/hyperref
On branches: develop,testthm
Link       : https://github.com/latex3/hyperref/commit/a1fbd6930eec08fe49819ddc6f9e0c2993cc6868

>---------------------------------------------------------------

commit a1fbd6930eec08fe49819ddc6f9e0c2993cc6868
Author: Ulrike Fischer <fischer at troubleshooting-tex.de>
Date:   Wed Apr 19 16:36:57 2023 +0200

    update documentation, changelog


>---------------------------------------------------------------

a1fbd6930eec08fe49819ddc6f9e0c2993cc6868
 ChangeLog.txt        |  3 +++
 doc/hyperref-doc.tex | 23 ++++++++++++++---------
 2 files changed, 17 insertions(+), 9 deletions(-)

diff --git a/ChangeLog.txt b/ChangeLog.txt
index d276e37..7eac953 100644
--- a/ChangeLog.txt
+++ b/ChangeLog.txt
@@ -1,3 +1,6 @@
+2023-04-19 Ulrike Fischer
+    * support hitex engine
+
 2023-02-19 Yukai Chou
     * remove dependency on etexcmds package
 
diff --git a/doc/hyperref-doc.tex b/doc/hyperref-doc.tex
index e9019cc..85eb163 100644
--- a/doc/hyperref-doc.tex
+++ b/doc/hyperref-doc.tex
@@ -265,28 +265,33 @@ of a URL (of the form \emph{URL\#name\_string}). Here
 
 However, the drivers intended to produce \emph{only} PDF use literal
 PostScript or PDF \verb|\special| commands. The commands are defined in
-configuration files for different drivers, selected by package options;
+configuration files for different drivers, selected by package options or for
+most current engines autodetected;
 at present, the following drivers are supported:
 
 \begin{description}
 \item[hypertex] DVI processors conforming to the Hyper\TeX\ guidelines (i.e.\ \textsf{xdvi}, \textsf{dvips} (with
 the \textsf{-z} option), \textsf{\hologo{OzTeX}}, and \textsf{Textures})
-\item[dvips] produces \verb|\special| commands tailored for \textsf{dvips}
+\item[dvips] produces \verb|\special| commands tailored for \textsf{dvips}. This is the default driver if dvi mode is
+detected.
 \item[dvipsone] produces \verb|\special| commands tailored for \textsf{dvipsone}
 \item[ps2pdf] a special case of output suitable for processing by earlier versions of Ghost\-script's
 PDF writer; this is basically the same as that for \textsf{dvips}, but a few variations remained before version 5.21
-\item[tex4ht] produces \verb|\special| commands for use with \textsf{\TeX4ht}
-\item[pdftex] pdf\TeX, \hologo{HanTheThanh}'s \TeX{} variant that writes PDF directly
-\item[luatex] lua\TeX, Unicode \TeX{} variant that writes PDF directly
+\item[tex4ht] produces \verb|\special| commands for use with \textsf{\TeX4ht}, autodetected.
+\item[pdftex] pdf\TeX, \hologo{HanTheThanh}'s \TeX{} variant that writes PDF directly, autodetected.
+\item[luatex] lua\TeX, Unicode \TeX{} variant that writes PDF directly, autodetected.
 \item[dvipdfm] produces \verb|\special| commands for Mark Wicks' DVI to PDF driver \textsf{dvipdfm}
 \item[dvipdfmx] produces \verb|\special| commands for driver
      \textsf{dvipdfmx}, a successor of \textsf{dvipdfm}
 \item[dviwindo] produces \verb|\special| commands that Y\&Y's Windows previewer interprets as hypertext jumps within the previewer
 \item[vtex] produces \verb|\special| commands that MicroPress' HTML and
      PDF-producing \TeX\ variants interpret as hypertext jumps within the
-     previewer
+     previewer, autodetected.
 \item[textures] produces \verb|\special| commands that \textsf{Textures} interprets as hypertext jumps within the previewer
-\item[xetex] produces \verb|\special| commands for Xe\TeX{}
+\item[xetex] produces \verb|\special| commands for Xe\TeX{}, autodetected.
+\item[hitex] (new 2023) for the hint format produces by the Hi\TeX{} engine, autodetected. This a quite experimental
+engine and the driver file is not part of the \xpackage{hyperref} bundle but is provided by
+the \xpackage{hitex} package. Problems should be reported to \url{https://github.com/ruckertm/HINT}. 
 \end{description}
 
 Output from \textsf{dvips} or \textsf{dvipsone} must be processed using
@@ -307,8 +312,8 @@ such as \textsf{xdvi}.
   \begin{quote}
     \texttt{driverfallback=dvipdfm}
   \end{quote}
-  Autodetected drivers (\textsf{pdftex}, \textsf{xetex}, \textsf{vtex},
-  \textsf{vtexpdfmark}) are recognized from within \TeX\ and
+  Autodetected drivers (\textsf{pdftex}, \textsf{luatex}, \textsf{xetex}, \textsf{vtex},
+  \textsf{vtexpdfmark}, \textsf{hitex}) are recognized from within \TeX\ and
   therefore cannot be given as value to option \textsf{driverfallback}.
   However a DVI driver program is run after the \TeX\ run is finished.
   Thus it cannot be detected at \TeX\ macro level. Then package





More information about the latex3-commits mailing list.