summaryrefslogtreecommitdiff
path: root/macros/latex
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2023-11-20 03:04:02 +0000
committerNorbert Preining <norbert@preining.info>2023-11-20 03:04:02 +0000
commit682900f29e7ea9d31046e9541be14fd749b2eb17 (patch)
tree34d06fa9d427e231373629b5cc44517c583c84de /macros/latex
parentaa94b613f51dfa2b65c607585727b66875e765d8 (diff)
CTAN sync 202311200304
Diffstat (limited to 'macros/latex')
-rw-r--r--macros/latex/contrib/fvextra/fvextra.dtx902
-rw-r--r--macros/latex/contrib/fvextra/fvextra.pdfbin867095 -> 905184 bytes
-rw-r--r--macros/latex/contrib/proflycee/doc/ProfLycee-doc.pdfbin1413877 -> 1425491 bytes
-rw-r--r--macros/latex/contrib/proflycee/doc/ProfLycee-doc.tex4
-rw-r--r--macros/latex/contrib/proflycee/tex/ProfLycee.sty3
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-aleatoire.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-analyse.tex93
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-arithm.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-ecritures.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-geom.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-graphiques.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-listings.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-minted.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-piton.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-probas.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-pythontex.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-recreat.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-stats.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-suites.tex8
-rw-r--r--macros/latex/contrib/proflycee/tex/proflycee-tools-trigo.tex8
-rw-r--r--macros/latex/contrib/q-and-a/Q-and-A.cls198
-rw-r--r--macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple-content.tex2
-rw-r--r--macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple.pdfbin29394 -> 29542 bytes
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-content.tex81
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-dark.pdfbin0 -> 45378 bytes
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-light.pdfbin0 -> 45343 bytes
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical.tex51
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/code/Q-and-A-demo-ChatGPT-classical-code-1.py (renamed from macros/latex/contrib/q-and-a/demo/theme-ChatGPT/code/Q-and-A-example-code-1.py)0
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/images/Q-and-A-demo-ChatGPT-classical-logo-ChatGPT.pdf (renamed from macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-logo-ChatGPT.pdf)bin2703 -> 2703 bytes
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/images/Q-and-A-demo-ChatGPT-classical-logo-User.pdf (renamed from macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-logo-User.pdf)bin1444 -> 1444 bytes
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-content.tex6
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-dark.pdfbin45683 -> 111664 bytes
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-light.pdfbin45654 -> 111646 bytes
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT.tex42
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT/code/Q-and-A-demo-ChatGPT-code-1.py25
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-ChatGPT-logo-ChatGPT.pdfbin0 -> 2703 bytes
-rw-r--r--macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-ChatGPT-logo-User.pdfbin0 -> 1444 bytes
-rw-r--r--macros/latex/contrib/q-and-a/doc/Q-and-A-doc.pdfbin108248 -> 110412 bytes
-rw-r--r--macros/latex/contrib/q-and-a/doc/Q-and-A-doc.tex34
-rw-r--r--macros/latex/contrib/starray/README.md5
-rw-r--r--macros/latex/contrib/starray/doc/starray.pdfbin266418 -> 268851 bytes
-rw-r--r--macros/latex/contrib/starray/doc/starray.tex29
-rw-r--r--macros/latex/contrib/starray/latex/starray.sty126
-rw-r--r--macros/latex/contrib/tagpdf/README.md4
-rw-r--r--macros/latex/contrib/tagpdf/ex-AF-file.pdf106
-rw-r--r--macros/latex/contrib/tagpdf/ex-alt-actualtext.pdfbin34295 -> 42249 bytes
-rw-r--r--macros/latex/contrib/tagpdf/ex-attribute.pdf80
-rw-r--r--macros/latex/contrib/tagpdf/ex-formula-problem.pdf68
-rw-r--r--macros/latex/contrib/tagpdf/ex-list.pdf152
-rw-r--r--macros/latex/contrib/tagpdf/ex-mc-manual-para-split-obsolete.pdf46
-rw-r--r--macros/latex/contrib/tagpdf/ex-softhyphen.pdf68
-rw-r--r--macros/latex/contrib/tagpdf/ex-spaceglyph-listings.pdf60
-rw-r--r--macros/latex/contrib/tagpdf/ex-structure-obsolete.pdf94
-rw-r--r--macros/latex/contrib/tagpdf/ex-tagpdf-template.pdf90
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-backend.dtx8
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-checks.dtx4
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-code.pdfbin1650343 -> 1639998 bytes
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-data.dtx18
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-mc-generic.dtx6
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-mc-luacode.dtx6
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-mc-shared.dtx4
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-roles.dtx4
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-space.dtx4
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-struct.dtx6
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-tree.dtx4
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf-user.dtx4
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf.dtx118
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf.pdfbin1097084 -> 1094883 bytes
-rw-r--r--macros/latex/contrib/tagpdf/tagpdf.tex1221
-rw-r--r--macros/latex/contrib/tagpdf/tagpdfdocu-patches.sty21
70 files changed, 2387 insertions, 1522 deletions
diff --git a/macros/latex/contrib/fvextra/fvextra.dtx b/macros/latex/contrib/fvextra/fvextra.dtx
index 612c885839..edd5d3599e 100644
--- a/macros/latex/contrib/fvextra/fvextra.dtx
+++ b/macros/latex/contrib/fvextra/fvextra.dtx
@@ -1,6 +1,6 @@
% \iffalse meta-comment
%
-% Copyright (C) 2016-2022 by Geoffrey M. Poore <gpoore@gmail.com>
+% Copyright (C) 2016-2023 by Geoffrey M. Poore <gpoore@gmail.com>
% ---------------------------------------------------------------------------
% This work may be distributed and/or modified under the
% conditions of the LaTeX Project Public License, either version 1.3
@@ -26,7 +26,7 @@
%<package>\NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<package>\ProvidesPackage{fvextra}
%<*package>
- [2022/11/30 v1.5 fvextra - extensions and patches for fancyvrb]
+ [2023/11/19 v1.6 fvextra - extensions and patches for fancyvrb]
%</package>
%
%<*driver>
@@ -64,6 +64,27 @@
\usepackage{environ}
+\usepackage{tcolorbox}
+\tcbuselibrary{listings}
+% strip leading percent symbols
+\def\tcbverbatimwrite#1{%
+ \@bsphack
+ \tcb@set@verbatim@finish%
+ \tcb@allocate@tcb@out%
+ \immediate\openout\tcb@out #1
+ \tcb@verbatim@begin@hook%
+ \let\do\@makeother\dospecials
+ \tcb@verbatim@change@percent\catcode`\^^M\active \catcode`\^^I=12
+ \def\verbatim@processline{%
+ \immediate\write\tcb@out
+ {\expandafter\@gobble\the\verbatim@line}}%
+ \verbatim@start}%
+
+% fix redefinition by tcolorbox
+\def\verbatim@processline{%
+ \expandafter\check@percent\the\verbatim@line\par}
+
+
\usepackage{hyperref}
\hypersetup{
pdftitle=The fvextra package: extensions and patches for fancyvrb,
@@ -209,9 +230,10 @@
\g@addto@macro\changestext{\end{itemize}}%
}
\newcommand{\PrintChangelog}{%
- \addcontentsline{toc}{section}{Version History}
- \section*{Version History}%
- \label{sec:version-history}
+ %\addcontentsline{toc}{section}{Changelog}
+ %\section*{Changelog}%
+ \section{Changelog}%
+ \label{sec:changelog}
\begin{description}%
\changestext
\end{description}%
@@ -230,23 +252,21 @@
%</driver>
% \fi
%
-% \CheckSum{5254}
-%
-% \CharacterTable
-% {Upper-case \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z
-% Lower-case \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z
-% Digits \0\1\2\3\4\5\6\7\8\9
-% Exclamation \! Double quote \" Hash (number) \#
-% Dollar \$ Percent \% Ampersand \&
-% Acute accent \' Left paren \( Right paren \)
-% Asterisk \* Plus \+ Comma \,
-% Minus \- Point \. Solidus \/
-% Colon \: Semicolon \; Less than \<
-% Equals \= Greater than \> Question mark \?
-% Commercial at \@ Left bracket \[ Backslash \\
-% Right bracket \] Circumflex \^ Underscore \_
-% Grave accent \` Left brace \{ Vertical bar \|
-% Right brace \} Tilde \~}
+%
+% \begin{changelog}{v1.6}{2023/11/19}
+% \item Added new environment \Verb{VerbatimWrite}. This is similar to \Verb{fancyvrb}'s \Verb{VerbatimOut}, except that it allows for writing to a file multiple times and guarantees truly verbatim output via \Verb{\detokenize}.
+% \item Added new environment \Verb{VerbatimBuffer}. This stores the contents of an environment verbatim in a ``buffer,'' a sequence of numbered macros each of which contains one line of the environment. The ``buffered'' lines can then be looped over for further processing or later use.
+% \item Added new command \Verb{\VerbatimInsertBuffer}. This inserts an existing buffer created by \Verb{VerbatimBuffer} as a \Verb{Verbatim} environment.
+% \item Redefined visible space \Verb{\FancyVerbSpace} so that it now has the correct width. It had previously been redefined as \Verb{\textvisiblespace}, but that was slightly too narrrow.
+% \item Added option \Verb{spacebreak}. This determines the line break that is inserted around spaces when \Verb{showspaces=true} or \Verb{breakcollapsespaces=false}, by defining the new macro \Verb{\FancyVerbSpaceBreak}.
+% \item \Verb{breakbefore}, \Verb{breakafter}, and \Verb{breakanywhere} now produce plain breaks around spaces when \Verb{showspaces=true}, instead of breaks with a break symbol at the end of wrapped lines. \Verb{\FancyVerbBreakAnywhereBreak}, \Verb{\FancyVerbBreakBeforeBreak}, and \Verb{\FancyVerbBreakAfterBreak} are no longer inserted next to spaces. Instead, \Verb{\FancyVerbSpaceBreak} is inserted or (depending on options) \Verb{\FV@Space} is defined to include \Verb{\FancyVerbSpaceBreak}.
+% \item Added option \Verb{breakcollapsespaces}. When \Verb{true} (default), a line break within a run of regular spaces (\Verb{showspaces=false}) replaces all spaces with a single break, and the wrapped line after the break starts with a non-space character. When \Verb{false}, a line break within a run of regular spaces preserves all spaces, and the wrapped line after the break may start with one or more spaces. This causes regular spaces to behave exactly like the visible spaces produced with \Verb{showspaces}; both give identical line breaks, with the only difference being the appearance of spaces.
+% \item \Verb{breaklines} now automatically enables breaks after space characters when \Verb{showspaces=true}.
+% \item Reimplemented definition of \Verb{\FV@Space} to work with new space options.
+% \item Added documentation about how reimplemented commands handle the \Verb{codes} option differently compared to \fancyvrb\ (\#17).
+% \item Starred commands such as \Verb{\Verb*} now use both visible spaces and visible tabs instead of just visible spaces. This is more similar to the current behavior of \Verb{\verb*}, except that \Verb{\verb*} converts tabs into visible spaces (\#19).
+% \item The \Verb{mathescape} option now resets the ampersand \Verb{&} catcode (\#18).
+% \end{changelog}
%
%
% \begin{changelog}{v1.5}{2022/11/30}
@@ -355,7 +375,7 @@
%
% Additional verbatim features would be nice, but since \fancyvrb\ has remained almost unchanged for so long, a major upgrade could be problematic. There are likely many existing documents that tweak or patch \fancyvrb\ internals in a way that relies on the existing implementation. At the same time, creating a completely new verbatim package would require a major time investment and duplicate much of \fancyvrb\ that remains perfectly functional. Perhaps someday there will be an amazing new verbatim package. Until then, we have \fvextra.
%
-% \fvextra\ is an add-on package that gives \fancyvrb\ several additional features, including automatic line breaking. Because \fvextra\ patches and overwrites some of the \fancyvrb\ internals, it may not be suitable for documents that rely on the details of the original \fancyvrb\ implementation. \fvextra\ tries to maintain the default \fancyvrb\ behavior in most cases. All reimplementations (\cref{sec:reimplemented-cmd-env}), patches (\cref{sec:patch}), and modifications to \fancyvrb\ defaults (\cref{sec:modifications}) are documented. In most cases, there are options to switch back to original implementations or original default behavior.
+% \fvextra\ is an add-on package that gives \fancyvrb\ several additional features, including automatic line breaking. Because \fvextra\ patches and overwrites some of the \fancyvrb\ internals, it may not be suitable for documents that rely on the details of the original \fancyvrb\ implementation. \fvextra\ tries to maintain the default \fancyvrb\ behavior in most cases. All reimplementations (\cref{sec:reimplemented-cmd}), patches (\cref{sec:patch}), and modifications to \fancyvrb\ defaults (\cref{sec:modifications}) are documented. In most cases, there are options to switch back to original implementations or original default behavior.
%
% Some features of \fvextra\ were originally created as part of the \pkg{pythontex} and \pkg{minted} packages. \fancyvrb-related patches and extensions that currently exist in those packages will gradually be migrated into \fvextra.
%
@@ -372,7 +392,7 @@
%
%
% \subsection{Pandoc compatibility}
-%
+%
% \pkg{fvextra} supports line breaking in \href{https://pandoc.org/}{Pandoc} \LaTeX\ output that includes highlighted source code. Enabling basic line breaking at spaces is as simple as adding |\usepackage{fvextra}| and |\fvset{breaklines}| to the Pandoc Markdown |header-includes|.
%
% By default, more advanced line breaking features such as |breakanywhere|, |breakbefore|, and |breakafter| will not work with Pandoc highlighted output, due to the presence of the syntax highlighting macros. This can be fixed by using |breaknonspaceingroup|, which enables all line breaking features within macros. For example, the following YAML metadata in a Markdown document would redefine the Pandoc |Highlighting| environment to enable line breaking anywhere.
@@ -480,9 +500,13 @@
%
%
% \item[mathescape (boolean) (false)]
-% This causes everything between dollar signs |$...$| to be typeset as math. The caret |^| and underscore |_| have their normal math meanings.
+% This causes everything between dollar signs |$...$| to be typeset as math. The ampersand |&|, caret |^|, and underscore |_| have their normal math meanings.
%
-% This is equivalent to |codes={\catcode`$=3\catcode`^=7\catcode`_=8}|. |mathescape| is always applied \emph{before} |codes|, so that |codes| can be used to override some of these definitions.
+% This is equivalent to
+% \begin{Verbatim}[gobble=2]
+% codes={\catcode`\$=3\catcode`\&=4\catcode`\^=7\catcode`\_=8}
+% \end{Verbatim}
+% |mathescape| is always applied \emph{before} |codes|, so that |codes| can be used to override some of these definitions.
%
% Note that \fvextra\ provides several patches that make math mode within verbatim as close to normal math mode as possible (\cref{sec:patch:math}).
%
@@ -526,10 +550,14 @@
% This only applies to the reimplemented \cmd{\UseVerb}, when paired with the reimplemented \cmd{\SaveVerb}. It may be extended to environments (\cmd{\UseVerbatim}, etc.\@) in the future, if the relevant commands and environments are reimplemented.
%
%
-% \item[space (macro) (\string\textvisiblespace, \textvisiblespace)]
+% \item[space (macro) ({\ttfamily\FancyVerbSpace})]
% Redefine the visible space character. Note that this is only used if |showspaces=true|. The color of the character may be set with |spacecolor|.
%
%
+% \item[spacebreak (macro) (\Verb{\discretionary{}{}{}})]
+% This determines the break that is inserted around spaces when |breaklines=true| and one or more of the following conditions applies: |breakcollapsespaces=false|, |showspaces=true|, or the space is affected by |breakbefore| or |breakafter|. If it is redefined, it should typically be similar to |\FancyVerbBreakAnywhereBreak|, |\FancyVerbBreakBeforeBreak|, and |\FancyVerbBreakAfterBreak| to obtain consistent breaks.
+%
+%
% \item[spacecolor (string) (none)]
% Set the color of visible spaces. By default (|none|), they take the color of their surroundings.
%
@@ -617,13 +645,13 @@
%
% This is like \cmd{\fvset}, except that options only apply to commands that typeset inline verbatim, like \cmd{\Verb} and \cmd{\EscVerb}. Settings from \cmd{\fvinlineset} override those from \cmd{\fvset}.
%
-% Note that \cmd{\fvinlineset} only works with commands that are reimplemented, patched, or defined by \fvextra; it is not compatible with the original \fancyvrb\ definitions.
+% Note that \cmd{\fvinlineset} only works with commands that are reimplemented, patched, or defined by \fvextra; it is not compatible with the original \fancyvrb\ definitions.
%
%
% \subsection{Custom formatting for inline commands like \cmd{\Verb} with \cmd{\FancyVerbFormatInline}}
%
% \DescribeMacro{\FancyVerbFormatInline}
-%
+%
% This can be used to apply custom formatting to inline verbatim text created with commands like \cmd{\Verb}. It only works with commands that are reimplemented, patched, or defined by \fvextra; it is not compatible with the original \fancyvrb\ definitions. The default definition does nothing; it is equivalent to |\newcommand{\FancyVerbFormatInline}[1]{#1}|.
%
% This is the inline equivalent of \cmd{\FancyVerbFormatLine} and \cmd{\FancyVerbFormatText}. In the inline context, there is no need to distinguish between entire line formatting and only text formatting, so only \cmd{\FancyVerbFormatInline} exists.
@@ -656,19 +684,22 @@
%
%
%
-% \section{Reimplemented commands and environments}
-% \label{sec:reimplemented-cmd-env}
+% \section{Reimplemented commands}
+% \label{sec:reimplemented-cmd}
%
% \fvextra\ reimplements parts of \fancyvrb. These new implementations stay close to the original definitions while allowing for new features that otherwise would not be possible. Reimplemented versions are used by default. The original implementations may be used via |\fvset{extra=false}| or by using |extra=false| in the optional arguments to a command or environment.
%
+% Reimplemented commands restrict the scope of catcode-related options compared to the original \fancyvrb\ versions. This prevents catcode-related options from interfering with new features such as |\FancyVerbFormatInline|. With \fvextra, the |codes| option should only be used for catcode modifications. Including non-catcode commands in |codes| will typically have no effect, unlike with \fancyvrb. If you want to customize verbatim content using general commands, consider |formatcom|.
+%
% \subsection{\cmd{\Verb}}
% \DescribeMacro{\Verb*\oarg{options}\meta{delim~char~or~\{}\meta{text}\meta{delim~char~or~\}}}
%
% The new \cmd{\Verb} works as expected (with a few limitations) inside other commands. It even works in movable arguments (for example, in \cmd{\section}), and is compatible with \pkg{hyperref} for generating PDF strings (for example, PDF bookmarks). The \fancyvrb\ definition did work inside some other commands, but essentially functioned as \cmd{\texttt} in that context.
%
-% \cmd{\Verb} is compatible with |breaklines| and the relevant line-breaking options.
+% \cmd{\Verb} is compatible with |breaklines| and the relevant line-breaking options.
+%
+% Like the original \fancyvrb\ implementation, the new \cmd{\Verb} can be starred (|\Verb*|) and accepts optional arguments. While \fancyvrb's starred command |\Verb*| is a shortcut for |showspaces|, \fvextra's |\Verb*| is a shortcut for both |showspaces| and |showtabs|. This is more similar to the current behavior of \LaTeX's \Verb{\verb*}, except that \Verb{\verb*} converts tabs into visible spaces instead of displaying them as visible tabs.
%
-% Like the original \fancyvrb\ implementation, the new \cmd{\Verb} can be starred (|*|) as a shortcut for |showspaces|, and accepts optional arguments.
% \begin{description}
% \item[Delimiters] A repeated character like normal \cmd{\verb}, or a pair of curly braces |{...}|. If curly braces are used, then \meta{text} cannot contain unpaired curly braces. Note that curly braces should be preferred when using \cmd{\Verb} inside other commands, and curly braces are \emph{required} when \cmd{\Verb} is in a movable argument, such as in a \cmd{\section}. Non-ASCII characters now work as delimiters under pdfTeX with \pkg{inputenc} using UTF-8.\footnote{Under pdfTeX, non-ASCII code points are processed at the byte rather than code point level, so \cmd{\Verb} must treat a sequence of multiple bytes as the delimiter.} For example, \Verb{\VerbĀ§verbĀ§} now works as expected.
% \item[Limitations inside other commands] While the new \cmd{\Verb} does work inside arbitrary other commands, there are a few limitations.
@@ -710,7 +741,7 @@
% \item |\UseVerb[retokenize, commandchars=\\\{\}]{save}| $\Rightarrow$ \UseVerb[retokenize, commandchars=\\\{\}]{save}
% \end{itemize}
%
-%
+%
%
%
%
@@ -752,6 +783,156 @@
% AFTER
% \end{example}
%
+% \cmd{VerbEnv} is not implemented using the typical \fancyvrb\ environment implementation style, so it is not compatible with |\RecustomVerbatimEnvironment|.
+%
+%
+% \subsection{\cmd{VerbatimWrite}}
+% \DescribeMacro{\begin\{VerbatimWrite\}\oarg{opt}\\$\langle$\textit{lines}$\rangle$\\\cmd{\end{VerbatimWrite}}}
+%
+% This writes environment contents verbatim to an external file. It is similar to \fancyvrb's |VerbatimOut|, except that (1) it allows writing to a file multiple times (multiple environments can write to the same file) and (2) by default it uses |\detokenize| to guarantee truly verbatim output.
+%
+% By default, all \fancyvrb\ options except for |VerbatimWrite|-specific options are ignored. This can be customized on a per-environment basis via environment optional arguments.
+%
+% ~
+%
+% \noindent Options defined specifically for \cmd{VerbatimWrite}:
+%
+% \begin{optionlist}
+% \item[writefilehandle (file handle) (\meta{none})]
+% File handle for writing. For example,
+% \begin{Verbatim}[gobble=2]
+% \newwrite\myfile
+% \immediate\openout\myfile=myfile.txt\relax
+%
+% \begin{VerbatimWrite}[writefilehandle=\myfile]
+% ...
+% \end{VerbatimWrite}
+%
+% \immediate\closeout\myfile
+% \end{Verbatim}
+%
+% \item[writer (macro) (\cmd{\FancyVerbDefaultWriter})]
+% This is the macro that processes each line of text in the environment and then writes it to file. This is the default implementation:
+% \begin{Verbatim}[gobble=2]
+% \def\FancyVerbDefaultWriter#1{%
+% \immediate\write\FancyVerbWriteFileHandle{\detokenize{#1}}}
+% \end{Verbatim}
+% \end{optionlist}
+%
+%
+% \subsection{\cmd{VerbatimBuffer}}
+% \DescribeMacro{\begin\{VerbatimBuffer\}\oarg{opt}\\$\langle$\textit{lines}$\rangle$\\\cmd{\end{VerbatimBuffer}}}
+%
+% This environment stores its contents verbatim in a ``buffer,'' a sequence of numbered macros each of which contains one line of the environment. The ``buffered'' lines can then be looped over for further processing or later use. This is similar to \fancyvrb's |SaveVerbatim|, which saves an environment for later use. |VerbatimBuffer| offers additional flexibility by capturing truly verbatim environment contents using |\detokenize| and saving environment contents in a format designed for further processing.
+%
+% By default, all \fancyvrb\ options except for |VerbatimBuffer|-specific options are ignored. This can be customized on a per-environment basis via environment optional arguments.
+%
+% Below is an extended example that demonstrates what is possible with |VerbatimBuffer| combined with |\VerbatimInsertBuffer|. This uses |\ifdefstring| from the \pkg{etoolbox} package.
+% \begin{itemize}
+% \item |\setformatter| defines an empty |\formatter| macro. Then it loops over the lines in a buffer looking for a line containing only the text ``red''. If this is found, it redefines |\formatter| to |\color{red}|. |FancyVerbBufferIndex| is a counter that is always available for buffer looping. |FancyVerbBufferLength| is the default counter containing the buffer length (number of lines). |\FancyVerbBufferLineName| contains the base name for buffer line macros (default |FancyVerbBufferLine|).
+% \item |afterbuffer| involves two steps: (1) |\setformatter| loops through the buffer and defines |\formatter| based on the buffer contents, and (2) |\VerbatimInsertBuffer| typesets the buffer, using |formatcom=\formatter| to format the text based on whether any line contains only the text ``red''.
+% \end{itemize}
+%
+%\begin{tcblisting}{oversize=5em}
+%\def\setformatter{%
+% \def\formatter{}%
+% \setcounter{FancyVerbBufferIndex}{1}%
+% \loop\unless\ifnum\value{FancyVerbBufferIndex}>\value{FancyVerbBufferLength}\relax
+% \expandafter\let\expandafter\bufferline
+% \csname\FancyVerbBufferLineName\arabic{FancyVerbBufferIndex}\endcsname
+% \ifdefstring{\bufferline}{red}{\def\formatter{\color{red}}}{}%
+% \stepcounter{FancyVerbBufferIndex}%
+% \repeat}
+%
+%\begin{VerbatimBuffer}[
+% afterbuffer={\setformatter\VerbatimInsertBuffer[formatcom=\formatter]}
+%]
+%first
+%second
+%red
+%\end{VerbatimBuffer}
+%\end{tcblisting}
+%
+% Here is the same example, but rewritten to use a global buffer with custom buffer names instead.
+%
+%\begin{tcblisting}{oversize=5em}
+%\begin{VerbatimBuffer}[globalbuffer, bufferlinename=exbuff, bufferlengthname=exbuff]
+%first
+%second
+%red
+%\end{VerbatimBuffer}
+%
+%\def\formatter{}
+%\setcounter{FancyVerbBufferIndex}{1}
+%\loop\unless\ifnum\value{FancyVerbBufferIndex}>\value{exbuff}\relax
+% \expandafter\let\expandafter\bufferline
+% \csname exbuff\arabic{FancyVerbBufferIndex}\endcsname
+% \ifdefstring{\bufferline}{red}{\def\formatter{\color{red}}}{}
+% \stepcounter{FancyVerbBufferIndex}
+%\repeat
+%
+%\VerbatimInsertBuffer[
+% formatcom=\formatter,
+% bufferlinename=exbuff,
+% bufferlengthname=exbuff
+%]
+%\end{tcblisting}
+%
+% ~
+%
+% \noindent Options defined specifically for \cmd{VerbatimBuffer}:
+%
+% \begin{optionlist}
+% \item[afterbuffer (macro) (\meta{none})]
+% Macro or macros invoked at the end of the environment, after all lines of the environment have been buffered. This is outside the |\begingroup...\endgroup| that wraps verbatim processing, so \fancyvrb\ settings are no longer active. However, the buffer line macros and the buffer length counter are still accessible.
+%
+% \item[bufferer (macro) (\Verb{\FancyVerbDefaultBufferer})]
+% This is the macro that adds lines to the buffer. The default is designed to create a truly verbatim buffer via |\detokenize|. This can be customized if you wish to use \fancyvrb\ options related to catcodes to create a buffer that is only partially verbatim (that contains macros).
+% \begin{Verbatim}[gobble=2, fontsize=\small]
+% \def\FancyVerbDefaultBufferer#1{%
+% \expandafter\xdef\csname\FancyVerbBufferLineName\arabic{FancyVerbBufferIndex}\endcsname{%
+% \detokenize{#1}}}
+% \end{Verbatim}
+% A custom |bufferer| must take a single argument |#1| (a line of the environment text) and ultimately store the processed line in a macro called
+% \begin{Verbatim}[gobble=2]
+% \csname\FancyVerbBufferLineName\arabic{FancyVerbBufferIndex}\endcsname
+% \end{Verbatim}
+% This macro must be defined globally, so |\xdef| or |\gdef| is necessary (this does not interfere with scoping from |globalbuffer|). Otherwise, there are no restrictions. The |\xdef| and |\detokenize| in the default definition guarantee that the buffer consists only of the literal text from the environment, but this is not required for a custom |bufferer|.
+%
+% \item[bufferlengthname (string) (FancyVerbBufferLength)]
+% Name of the counter (|\newcounter|) storing the length of the buffer. This is the number of lines stored.
+%
+% \item[bufferlinename (string) (FancyVerbBufferLine)]
+% The base name of the buffer line macros. The default is |FancyVerbBufferLine|, which will result in buffer macros |\FancyVerbBufferLine<n>| with integer |n| greater than or equal to one and less than or equal to the number of lines (one-based indexing). Since buffer macro names contain a number, they must be accessed differently than typical macros:
+% \begin{Verbatim}[gobble=2]
+% \csname FancyVerbBufferLine<n>\endcsname
+% \@nameuse{FancyVerbBufferLine<n>}
+% \end{Verbatim}
+% Typically the buffer macros will be looped over with a counter that is incremented, in which case |<n>| should be the counter value |\arabic{<counter>}|.
+%
+% \item[buffername (string) (\meta{none})]
+% Shortcut for setting |bufferlengthname| and |bufferlinename| simultaneously, using the same root name. This sets |bufferlengthname| to |<buffername>length| and |bufferlinename| to |<buffername>line|.
+%
+% \item[globalbuffer (bool) (false)]
+% This determines whether buffer line macros are defined globally, that is, whether they are accessible after the end of the |VerbatimBuffer| environment. It does not affect any |afterbuffer| macro, since that is invoked inside the environment. |globalbuffer| also determines whether the buffer length counter contains the buffer length or is reset to zero after the end of the |VerbatimBuffer| environment.
+%
+% When buffered lines are used immediately, consider using |afterbuffer| instead of |globalbuffer|. When buffered lines must be used later in a document, consider using |globalbuffer| with custom (and perhaps unique) |bufferlinename| and |bufferlengthname|.
+%
+% When |globalbuffer=false|, at the end of the environment all buffer line macros based on the current |bufferlinename| are ``deleted'' (|\let| to an undefined macro), and the buffer length counter from |bufferlengthname| is set to zero. This means that a |VerbatimBuffer| environment with |globalbuffer=false| will clear the buffer created by any previous |VerbatimBuffer| that had |globalbuffer=true| and shared the same |bufferlinename|.
+% \end{optionlist}
+%
+%
+% \subsection{\cmd{\VerbatimInsertBuffer}}
+% \DescribeMacro{\VerbatimInsertBuffer\oarg{options}}
+%
+% This inserts an existing buffer created by |VerbatimBuffer| as a |Verbatim| environment. It customizes |Verbatim| internals to function with a buffer in a command context. See the |VerbatimBuffer| documentation for an example of usage.
+%
+% Options related to catcodes cause the buffer to be retokenized during typesetting. That is, the \fancyvrb\ options used for |\VerbatimInsertBuffer| are not restricted by those that were in effect when |VerbatimBuffer| originally created the buffer, so long as the buffer contains a complete representation of the original |VerbatimBuffer| environment contents.
+%
+% |\VerbatimInsertBuffer| is not implemented using the typical \fancyvrb\ command and environment implementation styles, so it is not compatible with |\RecustomVerbatimCommand| or |\RecustomVerbatimEnvironment|.
+%
+%
+%
%
% \section{Line breaking}
% \label{sec:breaklines}
@@ -772,7 +953,7 @@
%
% For an alternative, see |breakbefore|. When |breakbefore| and |breakafter| are used for the same character, |breakbeforeinrun| and |breakafterinrun| must both have the same setting.
%
-% Note that when |commandchars| or |codes| are used to include macros within verbatim content, breaks will not occur within mandatory macro arguments by default. Depending on settings, macros that take optional arguments may not work unless the entire macro including arguments is wrapped in a group (curly braces |{}|, or other characters specified with |commandchars|). See \cref{sec:breaklines:advanced} for details.
+% Note that when |commandchars| or |codes| are used to include macros within verbatim content, breaks will not occur within mandatory macro arguments by default. Depending on settings, macros that take optional arguments may not work unless the entire macro including arguments is wrapped in a group (curly braces |{}|, or other characters specified with |commandchars|). See \cref{sec:breaklines:advanced} for details, and consider |breaknonspaceingroup| as a solution in simple cases.
%
% \begin{longexample}
% \begin{Verbatim}[breaklines, breakafter=d]
@@ -786,17 +967,17 @@
%
%
% \item[breakaftersymbolpre (string) (\string\,\string\footnotesize\string\ensuremath\{\_\string\rfloor\}, \,\footnotesize\ensuremath{_\rfloor})]
-% The symbol inserted pre-break for breaks inserted by |breakafter|.
+% The symbol inserted pre-break for breaks inserted by |breakafter|. This does not apply to breaks inserted next to spaces; see |spacebreak|.
%
%
% \item[breakaftersymbolpost (string) (\meta{none})]
-% The symbol inserted post-break for breaks inserted by |breakafter|.
+% The symbol inserted post-break for breaks inserted by |breakafter|. This does not apply to breaks inserted next to spaces; see |spacebreak|.
%
%
% \item[breakanywhere (boolean) (false)]
% Break lines anywhere, not just at spaces, when |breaklines=true|.
%
-% Note that when |commandchars| or |codes| are used to include macros within verbatim content, breaks will not occur within mandatory macro arguments by default. Depending on settings, macros that take optional arguments may not work unless the entire macro including arguments is wrapped in a group (curly braces |{}|, or other characters specified with |commandchars|). See \cref{sec:breaklines:advanced} for details.
+% Note that when |commandchars| or |codes| are used to include macros within verbatim content, breaks will not occur within mandatory macro arguments by default. Depending on settings, macros that take optional arguments may not work unless the entire macro including arguments is wrapped in a group (curly braces |{}|, or other characters specified with |commandchars|). See \cref{sec:breaklines:advanced} for details, and consider |breaknonspaceingroup| as a solution in simple cases.
%
% \begin{longexample}
% \begin{Verbatim}[breaklines, breakanywhere]
@@ -806,11 +987,11 @@
%
%
% \item[breakanywheresymbolpre (string) (\string\,\string\footnotesize\string\ensuremath\{\_\string\rfloor\}, \,\footnotesize\ensuremath{_\rfloor})]
-% The symbol inserted pre-break for breaks inserted by |breakanywhere|.
+% The symbol inserted pre-break for breaks inserted by |breakanywhere|. This does not apply to breaks inserted next to spaces; see |spacebreak|.
%
%
% \item[breakanywheresymbolpost (string) (\meta{none})]
-% The symbol inserted post-break for breaks inserted by |breakanywhere|.
+% The symbol inserted post-break for breaks inserted by |breakanywhere|. This does not apply to breaks inserted next to spaces; see |spacebreak|.
%
%
% \item[breakautoindent (boolean) (true)]
@@ -822,7 +1003,7 @@
%
% For an alternative, see |breakafter|. When |breakbefore| and |breakafter| are used for the same character, |breakbeforeinrun| and |breakafterinrun| must both have the same setting.
%
-% Note that when |commandchars| or |codes| are used to include macros within verbatim content, breaks will not occur within mandatory macro arguments by default. Depending on settings, macros that take optional arguments may not work unless the entire macro including arguments is wrapped in a group (curly braces |{}|, or other characters specified with |commandchars|). See \cref{sec:breaklines:advanced} for details.
+% Note that when |commandchars| or |codes| are used to include macros within verbatim content, breaks will not occur within mandatory macro arguments by default. Depending on settings, macros that take optional arguments may not work unless the entire macro including arguments is wrapped in a group (curly braces |{}|, or other characters specified with |commandchars|). See \cref{sec:breaklines:advanced} for details, and consider |breaknonspaceingroup| as a solution in simple cases.
%
% \begin{longexample}
% \begin{Verbatim}[breaklines, breakbefore=A]
@@ -836,11 +1017,15 @@
%
%
% \item[breakbeforesymbolpre (string) (\string\,\string\footnotesize\string\ensuremath\{\_\string\rfloor\}, \,\footnotesize\ensuremath{_\rfloor})]
-% The symbol inserted pre-break for breaks inserted by |breakbefore|.
+% The symbol inserted pre-break for breaks inserted by |breakbefore|. This does not apply to breaks inserted next to spaces; see |spacebreak|.
%
%
% \item[breakbeforesymbolpost (string) (\meta{none})]
-% The symbol inserted post-break for breaks inserted by |breakbefore|.
+% The symbol inserted post-break for breaks inserted by |breakbefore|. This does not apply to breaks inserted next to spaces; see |spacebreak|.
+%
+%
+% \item[breakcollapsespaces (bool) (true)]
+% When \Verb{true} (default), a line break within a run of regular spaces (\Verb{showspaces=false}) replaces all spaces with a single break, and the wrapped line after the break starts with a non-space character. When \Verb{false}, a line break within a run of regular spaces preserves all spaces, and the wrapped line after the break may start with one or more spaces. This causes regular spaces to behave exactly like the visible spaces produced with \Verb{showspaces}; both give identical line breaks, with the only difference being the appearance of spaces.
%
%
% \item[breakindent (dimension) (\meta{breakindentnchars})]
@@ -853,7 +1038,7 @@
% \item[breaklines (boolean) (false)]
% Automatically break long lines. When a line is broken, the result must fit on a single page. There is no support for breaking a line across multiple pages.\footnote{Following the implementation in \pkg{fancyvrb}, each line is typeset within an |\hbox|, so page breaks are not possible.}
%
-% By default, automatic breaks occur at spaces. Use |breakanywhere| to enable breaking anywhere; use |breakbefore| and |breakafter| for more fine-tuned breaking.
+% By default, automatic breaks occur at spaces (even when |showspaces=true|). Use |breakanywhere| to enable breaking anywhere; use |breakbefore| and |breakafter| for more fine-tuned breaking.
%
% \begin{example}
% ...text.
@@ -885,17 +1070,17 @@
% \end{longexample}
% \endgroup
%
-% Automatic line breaks will not work with |showspaces=true| unless you use |breakanywhere|, or use |breakbefore| or |breakafter| with |\space|. For example,
+% Beginning in version 1.6, automatic line breaks work with |showspaces=true| by default. Defining |breakbefore| or |breakafter| for |\space| is no longer necessary. For example,
%
% \begin{longexample}
-% \begin{Verbatim}[breaklines, showspaces, breakafter=\space]
+% \begin{Verbatim}[breaklines, showspaces]
% some_string = 'Some Text That Goes On And On For So Long That It Could Never Fit'
% \end{Verbatim}
% \end{longexample}
%
%
% \item[breaknonspaceingroup (boolean) (false)]
-% By using |commandchars|, it is possible to include \LaTeX\ commands within otherwise verbatim text. In these cases, there can be groups (typically |{...}| but depends on |commandchars|) within verbatim. Spaces within groups are treated as potential line break locations when |breaklines=true|, but by default no other break locations are inserted (|breakbefore|, |breakafter|, |breakanywhere|). This is because inserting non-space break locations can interfere with command functionality. For example, in |\textcolor{red}{text}|, breaks shouldn't be inserted within |red|.
+% By using |commandchars|, it is possible to include \LaTeX\ commands within otherwise verbatim text. In these cases, there can be groups (typically |{...}| but depends on |commandchars|) within verbatim. Spaces within groups are treated as potential line break locations when |breaklines=true|, but by default no other break locations are inserted (|breakbefore|, |breakafter|, |breakanywhere|). This is because inserting non-space break locations can interfere with command functionality. For example, in |\textcolor{red}{text}|, breaks shouldn't be inserted within |red|.
%
% |breaknonspaceingroup| allows non-space breaks to be inserted within groups. This option should only be used when |commandchars| is including \LaTeX\ commands that do not take optional arguments and only take mandatory arguments that are typeset. Something like |\textit{text}| is fine, but |\textcolor{red}{text}| is not because one of the mandatory arguments is not typeset but rather provides a setting. For more complex commands, it is typically better to redefine them to insert breaks in appropriate locations using |\FancyVerbBreakStart...\FancyVerbBreakStop|.
%
@@ -953,6 +1138,11 @@
% \item[breaksymbolseprightnchars (integer) (2)]
% Allows |breaksymbolsepright| to be specified as an integer number of characters rather than as a dimension (assumes a fixed-width font).
%
+%
+% \item[spacebreak (macro) (\Verb{\discretionary{}{}{}})]
+% This determines the break that is inserted around spaces when |breaklines=true| and one or more of the following conditions applies: |breakcollapsespaces=false|, |showspaces=true|, or the space is affected by |breakbefore| or |breakafter|. If it is redefined, it should typically be similar to |\FancyVerbBreakAnywhereBreak|, |\FancyVerbBreakBeforeBreak|, and |\FancyVerbBreakAfterBreak| to obtain consistent breaks.
+%
+%
% \end{optionlist}
%
%
@@ -1073,7 +1263,7 @@
% \DescribeMacro{\FancyVerbBreakBeforeBreak}
% \DescribeMacro{\FancyVerbBreakAfterBreak}
%
-% These macros govern the behavior of breaks introduced by |breakanywhere|, |breakbefore|, and |breakafter|. Breaks introduced by the default |breaklines| when |showspaces=false| are standard breaks following spaces. No special commands are provided for working with them; the normal \LaTeX\ commands for breaking should suffice.
+% These macros govern the behavior of breaks introduced by |breakanywhere|, |breakbefore|, and |breakafter|. These do not apply to breaks inserted next to spaces; see |spacebreak|.
%
% By default, these macros use |\discretionary|. |\discretionary| takes three arguments: commands to insert before the break, commands to insert after the break, and commands to insert if there is no break. For example, the default definition of |\FancyVerbBreakAnywhereBreak|:
%
@@ -1138,7 +1328,7 @@
% \subsection{Visible spaces}
% \label{sec:patch:visible-space}
%
-% The command |\FancyVerbSpace| defines the visible space when |showspaces=true|. The default \fancyvrb\ definition allows a font command to escape under some circumstances, so that all following text is forced to be teletype font. The command is redefined to use |\textvisiblespace|.
+% The command |\FancyVerbSpace| defines the visible space when |showspaces=true|. The default \fancyvrb\ definition allows a font command to escape under some circumstances, so that all following text is forced to be teletype font. The command is redefined following \url{https://tex.stackexchange.com/a/120231/10742}.
%
%
% \subsection{\texttt{obeytabs} with visible tabs and with tabs inside macro arguments}
@@ -1241,7 +1431,7 @@
%
%
% \subsection{Command lookahead tokenization}
-%
+%
% \cmd{\FV@Command} is used internally by commands like \cmd{\Verb} to read stars (|*|) and optional arguments (|[...]|) before invoking the core of the command. This is redefined so that lookahead tokenizes under a verbatim catcode regime. The original definition could prevent commands like \cmd{\Verb} from using characters like |%| as delimiters, because the lookahead for a star and optional argument could read the |%| and give it its normal meaning of comment character. The new definition fixes this, so that commands like \cmd{\Verb} behave as closely to \cmd{\verb} as possible.
%
%
@@ -1305,7 +1495,7 @@
%
% \DescribeMacro{\FancyVerbSpace}
%
-% This defines the visible space character (\texttt{\FancyVerbSpace}) that is used when |showspaces=true|. The default definition (as patched by \fvextra, \cref{sec:patch:visible-space}) is |\textvisiblespace|. While this may be redefined directly, \fvextra\ also defines a new option |space|.
+% This defines the visible space character (\texttt{\FancyVerbSpace}) that is used when |showspaces=true|. The default definition (as patched by \fvextra, \cref{sec:patch:visible-space}) follows \url{https://tex.stackexchange.com/a/120231/10742}. While this may be redefined directly, \fvextra\ also defines a new option |space|.
%
%
%
@@ -1346,8 +1536,26 @@
%
% \subsubsection{\fancyvrb\ space and tab tokens}
%
+% \begin{macro}{\FV@ActiveSpaceToken}
+% Active space for |\ifx| token comparisons.
+% \begin{macrocode}
+\begingroup
+\catcode`\ =\active%
+\gdef\FV@ActiveSpaceToken{ }%
+\endgroup%
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\FV@SpaceCatTen}
+% Space with catcode 10. Used instead of \Verb[showspaces]{\ } and |\space| in some contexts to avoid issues in the event that these are redefined.
+% \begin{macrocode}
+\edef\FV@SpaceCatTen{\detokenize{ }}
+% \end{macrocode}
+% \end{macro}
+%
+%
% \begin{macro}{\FV@FVSpaceToken}
-% Macro with the same definition as \fancyvrb's active space. Useful for |\ifx| comparisons with |\@ifnextchar| lookaheads.
+% Macro with the same definition as \fancyvrb's active space. Useful for |\ifx| comparisons, such as |\@ifnextchar| lookaheads.
% \begin{macrocode}
\def\FV@FVSpaceToken{\FV@Space}
% \end{macrocode}
@@ -1355,13 +1563,14 @@
%
%
% \begin{macro}{\FV@FVTabToken}
-% Macro with the same definition as \fancyvrb's active tab. Useful for |\ifx| comparisons with |\@ifnextchar| lookaheads.
+% Macro with the same definition as \fancyvrb's active tab. Useful for |\ifx| comparisons, such as |\@ifnextchar| lookaheads.
% \begin{macrocode}
\def\FV@FVTabToken{\FV@Tab}
% \end{macrocode}
% \end{macro}
%
%
+%
% \subsubsection{ASCII processing}
%
% \begin{macro}{\FVExtraDoSpecials}
@@ -2153,7 +2362,7 @@
% \begin{itemize}
% \item \cmd{\FV@VDetok@Scan} searches for spaces to replace. After any spaces in \meta{tokens} have been handled, the space in \Verb*|^^C \FV@<Sentinel>| triggers space processing. When \cmd{\FV@VDetok@Scan} detects the sentinel macro \cmd{\FV@<Sentinel>}, scanning stops.
% \item The |{}| protects the beginning of \meta{tokens}, so that if \meta{tokens} is a group, its braces won't be gobbled. Later, the inserted |{}| must be stripped so that it does not become part the processed \meta{tokens}.
-% \item |^^C| is a convenient separator between \meta{tokens} and the rest of the sentinel sequence.
+% \item |^^C| is a convenient separator between \meta{tokens} and the rest of the sentinel sequence.
% \begin{itemize}
% \item Since \cmd{\FV@VDetok@Scan} has delimited arguments, a leading catcode 10 space in \meta{tokens} will be preserved automatically. Preserving a trailing catcode 10 space is much easier if it is immediately adjacent to a non-space character in the sentinel sequence; two adjacent catcode 10 spaces would be difficult to handle with macro pattern matching. However, the sentinel sequence must contain a catcode 10 space, so the sentinel sequence must contain at least 3 tokens.
% \item Since |^^C| is not a control word, it does not gobble following spaces. That makes it much easier to assemble macro arguments that contain a catcode 10 space. This is useful because the sentinel sequence \Verb*|^^C \FV@<Sentinel>| may have to be inserted into processing multiple times (for example, in recursive handling of groups).
@@ -2287,7 +2496,7 @@
{\expandafter\FV@VDetok@ScanToken@i\detokenize{#1}^^C \FV@<Sentinel>}}
% \end{macrocode}
% \end{macro}
-%
+%
% \begin{macro}{\FV@VDetok@ScanToken@i}
% If |#2| is empty, then there are no spaces in the detokenized token, so it is either an \cmd{\active} character other than the space, or a two-character sequence of the form |<backslash><symbol>| where the second character is not a space. Thus, |#1| contains \meta{detokenized}|^^C|. Otherwise, |#1| contains \meta{detokenized\_without\_space}, and |#2| may be discarded since it contains \Verb*|^^C \FV@<Sentinel>|. (If the detokenized token contains a space, it is always at the end.)
% \begin{macrocode}
@@ -2489,7 +2698,7 @@
{\expandafter\FV@PDFStrVDetok@ScanToken@i\detokenize{#1}^^C \FV@<Sentinel>}}
% \end{macrocode}
% \end{macro}
-%
+%
% \begin{macro}{\FV@PDFStrVDetok@ScanToken@i}
% \begin{macrocode}
\gdef\FV@PDFStrVDetok@ScanToken@i#1 #2\FV@<Sentinel>{%
@@ -2586,7 +2795,7 @@
% \begin{macro}{\FVExtraEscapedVerbatimDetokenize}
% This is a variant of \cmd{\FVExtraVerbatimDetokenize} that treats character sequences of the form |\<char>| as escapes for |<char>|. It is primarily intended for making |\<symbol>| escapes for |<symbol>|, but allowing arbitrary escapes simplifies the default behavior and implementation. This is useful in constructing nearly verbatim commands that can be used inside other commands, because the backslash escapes allow for characters like |#| and |%|, as well as making possible multiple adjacent spaces via \Verb*|\ |. It should be applied to arguments that are read verbatim insofar as is possible, except that the backslash |\| should have its normal meaning (catcode 0). Most of the implementation is identical to that for \cmd{\FVExtraVerbatimDetokenize}. Only the token processing requires modification to handle backslash escapes.
%
-% It is possible to restrict escapes to ASCII symbols and punctuation. See \cmd{\FVExtraDetokenizeREscVArg}. The disadvantage of restricting escapes is that it prevents functioning in an expansion-only context (unless you want to use undefined macros as a means of raising errors). The advantage is that it eliminates ambiguity introduced by allowing arbitrary escapes. Backslash escapes of characters with catcode 11 (ASCII letters, |[A-Za-z]|) are typically not necessary, and introduce ambiguity because something like |\x| will gobble following spaces since it will be tokenized originally as a control word.
+% It is possible to restrict escapes to ASCII symbols and punctuation. See \cmd{\FVExtraDetokenizeREscVArg}. The disadvantage of restricting escapes is that it prevents functioning in an expansion-only context (unless you want to use undefined macros as a means of raising errors). The advantage is that it eliminates ambiguity introduced by allowing arbitrary escapes. Backslash escapes of characters with catcode 11 (ASCII letters, |[A-Za-z]|) are typically not necessary, and introduce ambiguity because something like |\x| will gobble following spaces since it will be tokenized originally as a control word.
% \begin{macrocode}
\gdef\FVExtraEscapedVerbatimDetokenize#1{%
\FV@EscVDetok@Scan{}#1^^C \FV@<Sentinel>}
@@ -2697,7 +2906,7 @@
{\expandafter\FV@EscVDetok@ScanToken@i\detokenize{#1}^^C \FV@<Sentinel>}}
% \end{macrocode}
% \end{macro}
-%
+%
% \begin{macro}{\FV@EscVDetok@ScanToken@i}
% \begin{macrocode}
\gdef\FV@EscVDetok@ScanToken@i#1 #2\FV@<Sentinel>{%
@@ -2937,7 +3146,7 @@
{\expandafter\FV@PDFStrEscVDetok@ScanToken@i\detokenize{#1}^^C \FV@<Sentinel>}}
% \end{macrocode}
% \end{macro}
-%
+%
% \begin{macro}{\FV@PDFStrEscVDetok@ScanToken@i}
% \begin{macrocode}
\gdef\FV@PDFStrEscVDetok@ScanToken@i#1 #2\FV@<Sentinel>{%
@@ -3321,7 +3530,7 @@
{\FVC@Verb@Extra@i}}
% \end{macrocode}
% \end{macro}
-%
+%
% \begin{macro}{\FVC@Verb@Extra@i}
% \begin{macrocode}
\def\FVC@Verb@Extra@i{%
@@ -3458,7 +3667,7 @@
\fi}
% \end{macrocode}
% \end{macro}
-%
+%
%
% \begin{macro}{\FVC@UseVerb@Extra}
% \begin{macrocode}
@@ -3537,7 +3746,7 @@
% \end{macro}
%
% \begin{macro}{\FVC@EscVerb@i}
-% \begin{macrocode}
+% \begin{macrocode}
\def\FVC@EscVerb@i#1{%
\begingroup
\FV@UseInlineKeyValues\FV@UseKeyValues\FV@FormattingPrep
@@ -3671,6 +3880,276 @@
%
%
%
+% \subsubsection{\cmd{VerbatimWrite}}
+%
+% This environment writes its contents to a file verbatim. Differences from \fancyvrb's |VerbatimOut|:
+% \begin{itemize}
+% \item Multiple |VerbatimWrite| environments can write to the same file. The file is set via the |writefilehandle| option. This does mean that the user is responsible for creating a new file handle via |\newwrite| and then ideally invoking |\closeout| at the appropriate time.
+% \item By default, text is really written verbatim. This is accomplished by a combination of setting catcodes to 12 (other) and |\detokenize|. This can be customized using the new |writer| option, which defines a macro that performs any processing on each line before writing it to file. By default, all \fancyvrb\ options except for |VerbatimWrite|-specific options are ignored. This can be customized on a per-environment basis via environment optional arguments.
+% \end{itemize}
+%
+% \begin{macro}{writefilehandle, \FancyVerbWriteFileHandle}
+% Set file handle for |VerbatimWrite|.
+% \begin{macrocode}
+\define@key{FV}{writefilehandle}{%
+ \FV@SetWrite#1\FV@Sentinel}
+\def\FV@SetWrite#1#2\FV@Sentinel{%
+ \let\FancyVerbWriteFileHandle\relax
+ \if\relax\detokenize{#2}\relax
+ \let\FancyVerbWriteFileHandle#1\relax
+ \fi
+ \ifx\FancyVerbWriteFileHandle\relax
+ \PackageError{fvextra}%
+ {Missing or invalid file handle for write}%
+ {Need file handle from \string\newwrite}%
+ \fi}
+\let\FancyVerbWriteFileHandle\relax
+% \end{macrocode}
+% \end{macro}
+%
+%
+% \begin{macro}{writer, \FV@Writer}
+% Define writer macro that processes each line before writing.
+% \begin{macrocode}
+\define@key{FV}{writer}{%
+ \let\FV@Writer#1\relax}
+\def\FancyVerbDefaultWriter#1{%
+ \immediate\write\FancyVerbWriteFileHandle{\detokenize{#1}}}
+\fvset{writer=\FancyVerbDefaultWriter}
+% \end{macrocode}
+% \end{macro}
+%
+%
+% \begin{macro}{VerbatimWrite}
+% The environment implementation follows standard \fancyvrb\ environment style.
+%
+% A special write counter is used to track line numbers while avoiding incrementing the regular counter that is used for typeset code. Some macros do nothing with the default |writer|, but are needed to enable \fancyvrb\ options when a custom |writer| is used in conjuction with optional environment arguments. These include |\FancyVerbDefineActive|, |\FancyVerbFormatCom|, and |\FV@DefineTabOut|.
+% \begin{macrocode}
+\newcounter{FancyVerbWriteLine}
+\def\VerbatimWrite{%
+ \FV@Environment
+ {codes=,commandchars=none,commentchar=none,defineactive,%
+ gobble=0,formatcom=,firstline,lastline}%
+ {VerbatimWrite}}
+\def\FVB@VerbatimWrite{%
+ \@bsphack
+ \begingroup
+ \setcounter{FancyVerbWriteLine}{0}%
+ \let\c@FancyVerbLine\c@FancyVerbWriteLine
+ \FV@UseKeyValues
+ \FV@DefineWhiteSpace
+ \def\FV@Space{\space}%
+ \FV@DefineTabOut
+ \let\FV@ProcessLine\FV@Writer
+ \let\FV@FontScanPrep\relax
+ \let\@noligs\relax
+ \FancyVerbDefineActive
+ \FancyVerbFormatCom
+ \FV@Scan}
+\def\FVE@VerbatimWrite{%
+ \endgroup
+ \@esphack}
+\def\endVerbatimWrite{\FVE@VerbatimWrite}
+% \end{macrocode}
+% \end{macro}
+%
+%
+%
+% \subsubsection{\cmd{VerbatimBuffer}}
+%
+% This environment stores its contents verbatim in a ``buffer,'' a sequence of numbered macros each of which contains one line of the environment. The ``buffered'' lines can then be looped over for further processing or later use.
+%
+% By default, all \fancyvrb\ options except for |VerbatimBuffer|-specific options are ignored. This can be customized on a per-environment basis via environment optional arguments.
+%
+% \begin{macro}{afterbuffer, \FV@afterbuffer}
+% Macro that is inserted after the last line of the environment is buffered, immediately before the environment ends.
+% \begin{macrocode}
+\define@key{FV}{afterbuffer}{%
+ \def\FV@afterbuffer{#1}}
+\fvset{afterbuffer=}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{FancyVerbBufferIndex}
+% Current index in buffer during buffering. This is given a |\FancyVerb*| macro name since it may be accessed by the user in defining custom |bufferer|.
+% \begin{macrocode}
+\newcounter{FancyVerbBufferIndex}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{bufferer, \FV@Bufferer, \FancyVerbDefaultBufferer}
+% This is the macro that adds lines to the buffer. The default is designed to create a truly verbatim buffer via |\detokenize|.
+% \begin{macrocode}
+\define@key{FV}{bufferer}{%
+ \let\FV@Bufferer=#1\relax}
+\def\FancyVerbDefaultBufferer#1{%
+ \expandafter\xdef\csname\FancyVerbBufferLineName\arabic{FancyVerbBufferIndex}\endcsname{%
+ \detokenize{#1}}}
+\fvset{bufferer=\FancyVerbDefaultBufferer}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{bufferlengthname, \FV@bufferlengthname}
+% Name of counter storing the length of the buffer.
+% \begin{macrocode}
+\define@key{FV}{bufferlengthname}{%
+ \ifcsname c@#1\endcsname
+ \else
+ \newcounter{#1}%
+ \fi
+ \def\FV@bufferlengthname{#1}}
+\fvset{bufferlengthname=FancyVerbBufferLength}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{bufferlinename, \FancyVerbBufferLineName}
+% Base name of buffer line macros. This is given a |\FancyVerb*| macro name since it may be accessed by the user in defining custom |bufferer|.
+% \begin{macrocode}
+\define@key{FV}{bufferlinename}{%
+ \def\FancyVerbBufferLineName{#1}}
+\fvset{bufferlinename=FancyVerbBufferLine}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{buffername}
+% Shortcut for setting |bufferlengthname| and |bufferlinename|.
+% \begin{macrocode}
+\define@key{FV}{buffername}{%
+ \fvset{bufferlengthname=#1length,bufferlinename=#1line}}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{globalbuffer, FV@globalbuffer}
+% Whether buffer macros and the buffer length counter are defined globally.
+% \begin{macrocode}
+\newbool{FV@globalbuffer}
+\define@booleankey{FV}{globalbuffer}%
+ {\booltrue{FV@globalbuffer}}%
+ {\boolfalse{FV@globalbuffer}}
+\fvset{globalbuffer=false}
+% \end{macrocode}
+% \end{macro}
+%
+%
+% \begin{macro}{VerbatimBuffer}
+% The environment implementation follows standard \fancyvrb\ environment style.
+%
+% A special buffer counter is used to track line numbers while avoiding incrementing the regular counter that is used for typeset code. Some macros do nothing with the default |bufferer|, but are needed to enable \fancyvrb\ options when a custom |bufferer| is used in conjuction with optional environment arguments. These include |\FancyVerbDefineActive| and |\FancyVerbFormatCom|. Since counters are global, the location of |\setcounter| at the end of the environment relative to |\begingroup...\endgroup| is not important.
+% \begin{macrocode}
+\newcounter{FancyVerbBufferLine}
+\newcounter{FV@oldbufferlength}
+\newbool{FV@globalbuffer@tmp}
+\let\FV@bufferlengthname@tmp\relax
+\let\FancyVerbBufferLineName@tmp\relax
+\let\FV@afterbuffer@tmp\relax
+\def\VerbatimBuffer{%
+ \FV@Environment
+ {codes=,commandchars=none,commentchar=none,defineactive,%
+ gobble=0,formatcom=,firstline,lastline}%
+ {VerbatimBuffer}}
+\def\FVB@VerbatimBuffer{%
+ \@bsphack
+ \begingroup
+ \setcounter{FancyVerbBufferLine}{0}%
+ \let\c@FancyVerbLine\c@FancyVerbBufferLine
+ \setcounter{FancyVerbBufferIndex}{0}%
+ \setcounter{FV@oldbufferlength}{\expandafter\value\expandafter{\FV@bufferlengthname}}%
+ \expandafter\setcounter\expandafter{\FV@bufferlengthname}{0}%
+ \FV@UseKeyValues
+ \ifbool{FV@globalbuffer}%
+ {\global\booltrue{FV@globalbuffer@tmp}}%
+ {\global\boolfalse{FV@globalbuffer@tmp}}%
+ \global\let\FV@bufferlengthname@tmp\FV@bufferlengthname
+ \global\let\FancyVerbBufferLineName@tmp\FancyVerbBufferLineName
+ \global\let\FV@afterbuffer@tmp\FV@afterbuffer
+ \FV@DefineWhiteSpace
+ \def\FV@ProcessLine{\stepcounter{FancyVerbBufferIndex}\FV@Bufferer}%
+ \let\FV@FontScanPrep\relax
+ \let\@noligs\relax
+ \FancyVerbDefineActive
+ \FancyVerbFormatCom
+ \FV@Scan}
+\def\FVE@VerbatimBuffer{%
+ \endgroup
+ \@esphack
+ \expandafter\setcounter\expandafter{\FV@bufferlengthname@tmp}%
+ {\value{FancyVerbBufferIndex}}%
+ \setcounter{FancyVerbBufferIndex}{0}%
+ \begingroup
+ \FV@afterbuffer@tmp
+ \endgroup
+ \ifbool{FV@globalbuffer@tmp}%
+ {}%
+ {\ifnum\value{FV@oldbufferlength}>%
+ \expandafter\value\expandafter{\FV@bufferlengthname@tmp}\relax
+ \expandafter\setcounter\expandafter{\FV@bufferlengthname@tmp}%
+ {\value{FV@oldbufferlength}}%
+ \fi
+ \loop\unless\ifnum\expandafter\value\expandafter{\FV@bufferlengthname@tmp}=0\relax
+ \expandafter\global\expandafter\let\csname
+ \FancyVerbBufferLineName@tmp
+ \expandafter\arabic\expandafter{\FV@bufferlengthname@tmp}%
+ \endcsname\FV@Undefined
+ \expandafter\addtocounter\expandafter{\FV@bufferlengthname@tmp}{-1}%
+ \repeat}}
+\def\endVerbatimBuffer{\FVE@VerbatimBuffer}
+% \end{macrocode}
+% \end{macro}
+%
+%
+%
+% \subsubsection{\cmd{\VerbatimInsertBuffer}}
+% \begin{macro}{\VerbatimInsertBuffer}
+% This inserts an existing buffer created by |VerbatimBuffer| as a |Verbatim| environment. It customizes |Verbatim| internals to function with a buffer in a command context.
+% \begin{macrocode}
+\newcommand{\VerbatimInsertBuffer}[1][]{%
+ \begingroup
+ \def\FV@KeyValues{#1}%
+ \def\FV@Scan{%
+ \FV@CatCodes
+ \xdef\FV@EnvironName{Verbatim}%
+ \ifnum\expandafter\value\expandafter{\FV@bufferlengthname}=\z@\relax
+ \PackageError{fvextra}%
+ {Buffer length counter \FV@bufferlengthname\space is invalid or zero}%
+ {}%
+ \let\FV@GetLine\relax
+ \fi
+ \FV@GetLine}%
+ \let\FV@CheckScan\relax
+ \setcounter{FancyVerbBufferIndex}{1}%
+ \def\VerbatimInsertBuffer@def@FV@Line##1{%
+ \FVExtraRetokenizeVArg{\def\FV@Line}{}{##1}}
+ \def\FancyVerbGetLine{%
+ \ifnum\value{FancyVerbBufferIndex}>%
+ \expandafter\value\expandafter{\FV@bufferlengthname}\relax
+ \global\let\FV@EnvironName\relax
+ \let\next\relax
+ \else
+ \ifcsname \FancyVerbBufferLineName\arabic{FancyVerbBufferIndex}\endcsname
+ \expandafter\let\expandafter\FV@Line@Buffer
+ \csname\FancyVerbBufferLineName\arabic{FancyVerbBufferIndex}\endcsname
+ \expandafter\VerbatimInsertBuffer@def@FV@Line\expandafter{\FV@Line@Buffer}%
+ \def\next{\FV@PreProcessLine\FV@GetLine}%
+ \stepcounter{FancyVerbBufferIndex}%
+ \else
+ \def\next{%
+ \PackageError{fvextra}%
+ {Buffer with line macro named
+ "\FancyVerbBufferLineName\arabic{FancyVerbBufferIndex}" does not exist}%
+ {Check bufferlinename, bufferlengthname, and globalbuffer settings}%
+ }%
+ \fi
+ \fi
+ \next}%
+ \FVB@Verbatim
+ \FVE@Verbatim
+ \setcounter{FancyVerbBufferIndex}{0}%
+ \endgroup}
+% \end{macrocode}
+% \end{macro}
+%
+%
+%
%
% \subsection{Patches}
% \label{sec:impl:patches}
@@ -3695,7 +4174,7 @@
% \begin{macrocode}
\def\FV@Command#1#2{%
\FVExtra@ifstarVArg
- {\def\FV@KeyValues{#1,showspaces}\FV@@Command{#2}}%
+ {\def\FV@KeyValues{#1,showspaces,showtabs}\FV@@Command{#2}}%
{\def\FV@KeyValues{#1}\FV@@Command{#2}}}
% \end{macrocode}
% \end{macro}
@@ -3745,9 +4224,15 @@
%\begin{verbatim}
%{\catcode`\ =12 \gdef\FancyVerbSpace{\tt }}
%\end{verbatim}
-% The command is redefined in more robust and standard \LaTeX\ form.
+% |\textvisiblespace| is not an alternative because it does not have the correct width. The redefinition follows \url{https://tex.stackexchange.com/a/120231/10742}.
% \begin{macrocode}
-\def\FancyVerbSpace{\textvisiblespace}
+\def\FancyVerbSpace{%
+ \makebox[0.5em]{%
+ \kern.07em
+ \vrule height.3ex
+ \hrulefill
+ \vrule height.3ex
+ \kern.07em}}
% \end{macrocode}
% \end{macro}
%
@@ -4128,8 +4613,20 @@
% \end{macro}
%
%
+% \begin{macro}{showspaces, FV@showspaces}
+% Reimplement |showspaces| with a bool to work with new space options.
+% \begin{macrocode}
+\newbool{FV@showspaces}
+\define@booleankey{FV}{showspaces}%
+ {\booltrue{FV@showspaces}}%
+ {\boolfalse{FV@showspaces}}
+\fvset{showspaces=false}
+% \end{macrocode}
+% \end{macro}
+%
+%
% \begin{macro}{space}
-% Redefine |\FancyVerbSpace|.
+% Redefine |\FancyVerbSpace|, which is the visible space.
% \begin{macrocode}
\define@key{FV}{space}{\def\FancyVerbSpace{#1}}
% \end{macrocode}
@@ -4145,21 +4642,73 @@
{\ifstrequal{#1}{none}%
{\let\FV@SpaceColor\relax}%
{\def\FV@SpaceColor{\textcolor{#1}}}}}
-\define@booleankey{FV}{showspaces}%
- {\def\FV@Space{\FV@SpaceColor{\FancyVerbSpace}}}%
- {\def\FV@Space{\ }}
-\fvset{spacecolor=none, showspaces=false}
+\fvset{spacecolor=none}
+% \end{macrocode}
+% \end{macro}
+%
+%
+% \begin{macro}{spacebreak, \FancyVerbSpaceBreak}
+% Line break for spaces that is inserted when spaces are visible (|showspaces=true|) or when breaks around spaces are handled specially (|breakcollapsespaces=false|). Not used for regular spaces under default conditions.
+% \begin{macrocode}
+\define@key{FV}{spacebreak}{%
+ \def\FancyVerbSpaceBreak{#1}}
+\fvset{spacebreak=\discretionary{}{}{}}
+% \end{macrocode}
+% \end{macro}
+%
+%
+% \begin{macro}{breakcollapsespaces, FV@breakcollapsespaces}
+% When a line break occurs within a sequence of regular space characters (|showspaces=false|), collapse the spaces into a single space and then replace it with the break. When this is |true|, a sequence of spaces will cause at most a single line break, and the first character on the wrapped line after the break will be a non-space character. When this is |false|, a sequence of spaces may result in multiple line breaks. Each wrapped line besides the last will contain only spaces. The final wrapped line may contain leading spaces before any non-space character(s).
+% \begin{macrocode}
+\newbool{FV@breakcollapsespaces}
+\define@booleankey{FV}{breakcollapsespaces}%
+ {\booltrue{FV@breakcollapsespaces}}%
+ {\boolfalse{FV@breakcollapsespaces}}%
+\fvset{breakcollapsespaces=true}
+% \end{macrocode}
+% \end{macro}
+%
+%
+% \begin{macro}{\FV@DefFVSpace}
+% Redefine |\FV@Space| based on \pkg{fvextra} options that affect spaces.
+%
+% This must be added to |\FV@FormattingPrep@PreHook|, but only after |breakbefore| and |breakafter| macros are defined. Hence the |\AtEndOfPackage|.
+% \begin{macrocode}
+\def\FV@DefFVSpace{%
+ \ifbool{FV@showspaces}%
+ {\ifbool{FV@breaklines}%
+ {\ifcsname FV@BreakBefore@Token\FV@SpaceCatTen\endcsname
+ \def\FV@Space{\FV@SpaceColor{\FancyVerbSpace}}%
+ \else\ifcsname FV@BreakAfter@Token\FV@SpaceCatTen\endcsname
+ \def\FV@Space{\FV@SpaceColor{\FancyVerbSpace}}%
+ \else
+ \def\FV@Space{\FV@SpaceColor{\FancyVerbSpace}\FancyVerbSpaceBreak}%
+ \fi\fi}%
+ {\def\FV@Space{\FV@SpaceColor{\FancyVerbSpace}}}}%
+ {\ifbool{FV@breaklines}%
+ {\ifcsname FV@BreakBefore@Token\FV@SpaceCatTen\endcsname
+ \def\FV@Space{\mbox{\FV@SpaceCatTen}}%
+ \else\ifcsname FV@BreakAfter@Token\FV@SpaceCatTen\endcsname
+ \def\FV@Space{\mbox{\FV@SpaceCatTen}}%
+ \else
+ \ifbool{FV@breakcollapsespaces}%
+ {\def\FV@Space{\FV@SpaceCatTen}}%
+ {\def\FV@Space{\mbox{\FV@SpaceCatTen}\FancyVerbSpaceBreak}}%
+ \fi\fi}%
+ {\def\FV@Space{\FV@SpaceCatTen}}}}%
+\AtEndOfPackage{%
+ \g@addto@macro\FV@FormattingPrep@PreHook{\FV@DefFVSpace}}
% \end{macrocode}
% \end{macro}
%
%
% \begin{macro}{mathescape}
-% Give |$|, |^|, and |_| their normal catcodes to allow normal typeset math.
+% Give |$|, |&|, |^|, and |_| their normal catcodes to allow normal typeset math.
% \begin{macrocode}
\define@booleankey{FV}{mathescape}%
{\let\FancyVerbMathEscape\FV@MathEscape}%
{\let\FancyVerbMathEscape\relax}
-\def\FV@MathEscape{\catcode`\$=3\catcode`\^=7\catcode`\_=8\relax}
+\def\FV@MathEscape{\catcode`\$=3\catcode`\&=4\catcode`\^=7\catcode`\_=8\relax}
\FV@AddToHook\FV@CatCodesHook\FancyVerbMathEscape
\fvset{mathescape=false}
% \end{macrocode}
@@ -4728,7 +5277,7 @@
\ifx\directlua\relax
\else
\FV@AddToHook\FV@FormattingPrep@PreHook\FV@BreakLinesLuaTeXHook
- \fi
+ \fi
\fi
% \end{macrocode}
% \end{macro}
@@ -4932,8 +5481,9 @@
% \end{macrocode}
% \end{macro}
%
+%
% \begin{macro}{FV@breakanywhere}
-% Allow line breaking (almost) anywhere. Set |\FV@Break| and |\FV@EndBreak| to be used, and |\let| |\FV@Break@Token| to the appropriate macro.
+% Allow line breaking (almost) anywhere. Set |\FV@Break| and |\FV@EndBreak| to be used, and |\let| |\FV@Break@DefaultToken| to the appropriate macro.
% \begin{macrocode}
\newbool{FV@breakanywhere}
\define@booleankey{FV}{breakanywhere}%
@@ -5352,7 +5902,7 @@
%
% For \pkg{fvextra}'s standard scanning: If this is the main buffer (depth 0), stop scanning---which ultimately allows |\FV@BreakBuffer| to be handled by |\FV@InsertBreaks|. For user macros: Insert |\FV@BreakBuffer| at buffer depth 0. Otherwise for both cases: Append the current buffer to the previous buffer, and continue scanning.
%
-% An intermediate |\FV@BreakBufferStop@i| is used to optimize |\ifx| comparisons for |\FV@BreakBufferStop| during scanning.
+% An intermediate |\FV@BreakBufferStop@i| is used to optimize |\ifx| comparisons for |\FV@BreakBufferStop| during scanning.
% \begin{macrocode}
\def\FV@BreakBufferStop{%
\FV@BreakBufferStop@i}
@@ -5509,7 +6059,7 @@
% \begin{macrocode}
\def\FV@Break@NBToken#1{%
\FV@BreakBuffer@Append{#1}%
- \let\FV@Break@LastToken=\FV@Undefined
+ \let\FV@LastToken=\FV@Undefined
\FV@Break@Scan}
% \end{macrocode}
% \end{macro}
@@ -5537,8 +6087,21 @@
%
% \begin{macrocode}
\def\FV@Break@AnyToken#1{%
- \FV@BreakBuffer@Append{\FancyVerbBreakAnywhereBreak#1}%
- \FV@Break@Scan}
+ \ifx\FV@FVSpaceToken#1\relax
+ \expandafter\@firstoftwo
+ \else
+ \expandafter\@secondoftwo
+ \fi
+ {\let\FV@LastToken=#1\FV@BreakBuffer@Append{#1}\FV@Break@Scan}%
+ {\ifx\FV@LastToken\FV@FVSpaceToken
+ \expandafter\@firstoftwo
+ \else
+ \expandafter\@secondoftwo
+ \fi
+ {\let\FV@LastToken=#1%
+ \FV@BreakBuffer@Append{#1}\FV@Break@Scan}%
+ {\let\FV@LastToken=#1%
+ \FV@BreakBuffer@Append{\FancyVerbBreakAnywhereBreak#1}\FV@Break@Scan}}}
% \end{macrocode}
% \end{macro}
%
@@ -5568,11 +6131,19 @@
\def\FV@Break@BeforeTokenBreak#1{%
\ifbool{FV@breakbeforeinrun}%
{\ifcsname FV@BreakAfter@Token\detokenize{#1}\endcsname
- \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak}%
+ \ifx#1\FV@FVSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak}%
+ \fi
\let\FV@Break@Next\FV@Break@BeforeTokenBreak@AfterRescan
\def\FV@RescanToken{#1}%
\else
- \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak#1}%
+ \ifx#1\FV@FVSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak#1}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak#1}%
+ \fi
\let\FV@Break@Next\FV@Break@Scan
\let\FV@LastToken=#1%
\fi}%
@@ -5587,11 +6158,19 @@
\fi
\else
\ifcsname FV@BreakAfter@Token\detokenize{#1}\endcsname
- \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak}%
+ \ifx#1\FV@FVSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak}%
+ \fi
\let\FV@Break@Next\FV@Break@BeforeTokenBreak@AfterRescan
\def\FV@RescanToken{#1}%
\else
- \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak#1}%
+ \ifx#1\FV@FVSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak#1}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak#1}%
+ \fi
\let\FV@Break@Next\FV@Break@Scan
\let\FV@LastToken=#1%
\fi
@@ -5602,32 +6181,58 @@
\def\FV@Break@AfterTokenBreak#1{%
\let\FV@LastToken=#1%
\@ifnextchar\FV@FVSpaceToken%
- {\FV@BreakBuffer@Append{#1}\FV@Break@Scan}%
- {\ifbool{FV@breakafterinrun}%
- {\FV@BreakBuffer@Append{#1\FancyVerbBreakAfterBreak}%
- \let\FV@Break@Next\FV@Break@Scan}%
- {\ifx\@let@token#1\relax
+ {\ifx#1\FV@FVSpaceToken
+ \expandafter\@firstoftwo
+ \else
+ \expandafter\@secondoftwo
+ \fi
+ {\FV@Break@AfterTokenBreak@i{#1}}%
+ {\FV@BreakBuffer@Append{#1}%
+ \FV@Break@Scan}}%
+ {\FV@Break@AfterTokenBreak@i{#1}}}
+\def\FV@Break@AfterTokenBreak@i#1{%
+ \ifbool{FV@breakafterinrun}%
+ {\ifx#1\FV@FVSpaceToken
+ \FV@BreakBuffer@Append{#1\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{#1\FancyVerbBreakAfterBreak}%
+ \fi
+ \let\FV@Break@Next\FV@Break@Scan}%
+ {\ifx\@let@token#1\relax
+ \FV@BreakBuffer@Append{#1}%
+ \let\FV@Break@Next\FV@Break@Scan
+ \else
+ \expandafter\ifx\csname @let@token\endcsname\bgroup\relax
\FV@BreakBuffer@Append{#1}%
- \let\FV@Break@Next\FV@Break@Scan
+ \let\FV@Break@Next\FV@Break@AfterTokenBreak@Group
\else
- \expandafter\ifx\csname @let@token\endcsname\bgroup\relax
- \FV@BreakBuffer@Append{#1}%
- \let\FV@Break@Next\FV@Break@AfterTokenBreak@Group
+ \ifx#1\FV@FVSpaceToken
+ \FV@BreakBuffer@Append{#1\FancyVerbSpaceBreak}%
\else
\FV@BreakBuffer@Append{#1\FancyVerbBreakAfterBreak}%
- \let\FV@Break@Next\FV@Break@Scan
\fi
- \fi}%
- \FV@Break@Next}%
+ \let\FV@Break@Next\FV@Break@Scan
+ \fi
+ \fi}%
+ \FV@Break@Next
}
\def\FV@Break@AfterTokenBreak@Group#1{%
\ifstrempty{#1}%
{\FV@BreakBuffer@Append{{}}%
\@ifnextchar\FV@LastToken%
{\FV@Break@Scan}%
- {\FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ {\ifx\FV@LastToken\FV@FVSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ \fi
\FV@Break@Scan}}%
- {\FV@Break@Group{#1}}}
+ {\ifx\FV@LastToken\FV@FVSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ \fi
+ \FV@Break@Group{#1}}}
% \end{macrocode}
% \end{macro}
%
@@ -5744,8 +6349,23 @@
\FV@Break@Next{#1}%
}
\def\FV@Break@AnyToken@UTF@i#1{%
- \FV@BreakBuffer@Append{\FancyVerbBreakAnywhereBreak#1}%
- \FV@Break@Scan}
+ \def\FV@CurrentToken{#1}%
+ \ifx\FV@CurrentToken\FV@ActiveSpaceToken\relax
+ \expandafter\@firstoftwo
+ \else
+ \expandafter\@secondoftwo
+ \fi
+ {\let\FV@LastToken\FV@CurrentToken
+ \FV@BreakBuffer@Append{#1}\FV@Break@Scan}%
+ {\ifx\FV@LastToken\FV@ActiveSpaceToken
+ \expandafter\@firstoftwo
+ \else
+ \expandafter\@secondoftwo
+ \fi
+ {\let\FV@LastToken\FV@CurrentToken
+ \FV@BreakBuffer@Append{#1}\FV@Break@Scan}%
+ {\let\FV@LastToken\FV@CurrentToken
+ \FV@BreakBuffer@Append{\FancyVerbBreakAnywhereBreak#1}\FV@Break@Scan}}}
% \end{macrocode}
% \end{macro}
%
@@ -5783,11 +6403,19 @@
\def\FV@CurrentToken{#1}%
\ifbool{FV@breakbeforeinrun}%
{\ifcsname FV@BreakAfter@Token\detokenize{#1}\endcsname
- \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak}%
+ \ifx\FV@CurrentToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak}%
+ \fi
\let\FV@Break@Next\FV@Break@BeforeTokenBreak@AfterRescan@UTF
\def\FV@RescanToken{#1}%
\else
- \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak#1}%
+ \ifx\FV@CurrentToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak#1}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak#1}%
+ \fi
\let\FV@Break@Next\FV@Break@Scan
\def\FV@LastToken{#1}%
\fi}%
@@ -5802,11 +6430,19 @@
\fi
\else
\ifcsname FV@BreakAfter@Token\detokenize{#1}\endcsname
- \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak}%
+ \ifx\FV@CurrentToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak}%
+ \fi
\let\FV@Break@Next\FV@Break@BeforeTokenBreak@AfterRescan@UTF
\def\FV@RescanToken{#1}%
\else
- \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak#1}%
+ \ifx\FV@CurrentToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak#1}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakBeforeBreak#1}%
+ \fi
\let\FV@Break@Next\FV@Break@Scan
\def\FV@LastToken{#1}%
\fi
@@ -5817,27 +6453,43 @@
\def\FV@Break@AfterTokenBreak@UTF#1{%
\def\FV@LastToken{#1}%
\@ifnextchar\FV@FVSpaceToken%
- {\FV@BreakBuffer@Append{#1}\FV@Break@Scan}%
- {\ifbool{FV@breakafterinrun}%
- {\FV@BreakBuffer@Append{#1\FancyVerbBreakAfterBreak}%
- \let\FV@Break@Next\FV@Break@Scan}%
+ {\ifx\FV@LastToken\FV@ActiveSpaceToken
+ \expandafter\@firstoftwo
+ \else
+ \expandafter\@secondoftwo
+ \fi
+ {\FV@Break@AfterTokenBreak@UTF@i{#1}}%
{\FV@BreakBuffer@Append{#1}%
- \ifx\@let@token\bgroup\relax
- \let\FV@Break@Next\FV@Break@AfterTokenBreak@Group@UTF
- \else
- \let\FV@Break@Next\FV@Break@AfterTokenBreak@UTF@i
- \fi}%
- \FV@Break@Next}%
-}
+ \FV@Break@Scan}}%
+ {\FV@Break@AfterTokenBreak@UTF@i{#1}}}
\def\FV@Break@AfterTokenBreak@UTF@i#1{%
+ \ifbool{FV@breakafterinrun}%
+ {\ifx\FV@LastToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{#1\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{#1\FancyVerbBreakAfterBreak}%
+ \fi
+ \let\FV@Break@Next\FV@Break@Scan}%
+ {\FV@BreakBuffer@Append{#1}%
+ \expandafter\ifx\csname @let@token\endcsname\bgroup\relax
+ \let\FV@Break@Next\FV@Break@AfterTokenBreak@Group@UTF
+ \else
+ \let\FV@Break@Next\FV@Break@AfterTokenBreak@UTF@ii
+ \fi}%
+ \FV@Break@Next}
+\def\FV@Break@AfterTokenBreak@UTF@ii#1{%
\ifcsname FV@U8:\detokenize{#1}\endcsname
\expandafter\let\expandafter\FV@Break@Next\csname FV@U8:\detokenize{#1}\endcsname
- \let\FV@UTF@octets@after\FV@Break@AfterTokenBreak@UTF@i
+ \let\FV@UTF@octets@after\FV@Break@AfterTokenBreak@UTF@ii
\else
\def\FV@NextToken{#1}%
\ifx\FV@LastToken\FV@NextToken
\else
- \FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ \ifx\FV@LastToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ \fi
\fi
\let\FV@Break@Next\FV@Break@Scan
\fi
@@ -5846,9 +6498,19 @@
\ifstrempty{#1}%
{\FV@BreakBuffer@Append{{}}%
\@ifnextchar\bgroup
- {\FV@Break@Group}%
+ {\ifx\FV@LastToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ \fi
+ \FV@Break@Group}%
{\FV@Break@AfterTokenBreak@Group@UTF@i}}%
- {\FV@Break@Group{#1}}}
+ {\ifx\FV@LastToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ \fi
+ \FV@Break@Group{#1}}}
\def\FV@Break@AfterTokenBreak@Group@UTF@i#1{%
\ifcsname FV@U8:\detokenize{#1}\endcsname
\expandafter\let\expandafter\FV@Break@Next\csname FV@U8:\detokenize{#1}\endcsname
@@ -5857,7 +6519,11 @@
\def\FV@NextToken{#1}%
\ifx\FV@LastToken\FV@NextToken
\else
- \FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ \ifx\FV@LastToken\FV@ActiveSpaceToken
+ \FV@BreakBuffer@Append{\FancyVerbSpaceBreak}%
+ \else
+ \FV@BreakBuffer@Append{\FancyVerbBreakAfterBreak}%
+ \fi
\fi
\let\FV@Break@Next\FV@Break@Scan
\fi
diff --git a/macros/latex/contrib/fvextra/fvextra.pdf b/macros/latex/contrib/fvextra/fvextra.pdf
index d66fe66d14..54b8e27fdd 100644
--- a/macros/latex/contrib/fvextra/fvextra.pdf
+++ b/macros/latex/contrib/fvextra/fvextra.pdf
Binary files differ
diff --git a/macros/latex/contrib/proflycee/doc/ProfLycee-doc.pdf b/macros/latex/contrib/proflycee/doc/ProfLycee-doc.pdf
index 511b284af0..8f6e135b5b 100644
--- a/macros/latex/contrib/proflycee/doc/ProfLycee-doc.pdf
+++ b/macros/latex/contrib/proflycee/doc/ProfLycee-doc.pdf
Binary files differ
diff --git a/macros/latex/contrib/proflycee/doc/ProfLycee-doc.tex b/macros/latex/contrib/proflycee/doc/ProfLycee-doc.tex
index 44ae53a48c..32cea1a647 100644
--- a/macros/latex/contrib/proflycee/doc/ProfLycee-doc.tex
+++ b/macros/latex/contrib/proflycee/doc/ProfLycee-doc.tex
@@ -5,8 +5,8 @@
% arara: lualatex: {shell: yes, synctex: no, interaction: batchmode} if found('log', '(undefined references|Please rerun|Rerun to get)')
\documentclass[a4paper,french,11pt]{article}
-\def\PLversion{3.00e}
-\def\PLdate{10 novembre 2023}
+\def\PLversion{3.00f}
+\def\PLdate{18 novembre 2023}
\usepackage{amsfonts}
\usepackage{ProfLycee}
\useproflyclib{piton,minted,pythontex,ecritures}
diff --git a/macros/latex/contrib/proflycee/tex/ProfLycee.sty b/macros/latex/contrib/proflycee/tex/ProfLycee.sty
index 555bc5c125..cd11a8d3d5 100644
--- a/macros/latex/contrib/proflycee/tex/ProfLycee.sty
+++ b/macros/latex/contrib/proflycee/tex/ProfLycee.sty
@@ -3,7 +3,8 @@
% or later, see http://www.latex-project.org/lppl.txtf
\NeedsTeXFormat{LaTeX2e}
-\ProvidesPackage{ProfLycee}[2023/11/10 3.00e Aide pour l'utilisation de LaTeX en lycee]
+\ProvidesPackage{ProfLycee}[2023/11/18 3.00f Aide pour l'utilisation de LaTeX en lycee]
+% 3.00f Conversion d'une Ʃcriture dƩcimale pƩriodique en fraction (avec rƩdaction Ʃventuelle)
% 3.00e Ajout des 'machines Ć  transformer' + Correction d'un nom de commande (cc ProfCollege ^^)
% 3.00d Ajout de commandes pour des chateaux de cartes et des allumettes
% 3.00c Ajout de chiffrements (CĆ©sar + Affine + Hill)
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-aleatoire.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-aleatoire.tex
index c1d167f058..ab5fa85c51 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-aleatoire.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-aleatoire.tex
@@ -1,12 +1,6 @@
% proflycee-tools-aleatoire.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%%------EnsembleList
\defKV[kvensemble]{%
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-analyse.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-analyse.tex
index 4057fe37dd..00f6f0206a 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-analyse.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-analyse.tex
@@ -1,12 +1,6 @@
% proflycee-tools-analyse.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%%------SimplFrac nouvelle version
\NewDocumentCommand\ConversionFraction{ s O{} m }{%
@@ -629,4 +623,89 @@
{}%
}
+%====FRACTION PƉRIODIQUE
+\defKV[FracPeriod]{Inconnue=\def\FracPerVar{#1}}
+\setKVdefault[FracPeriod]{Enonce=true,d=true,Inconnue=x,Solution=false,Brut=true,Simple=false}
+
+\NewDocumentCommand\FractionPeriode{ O{} m m }{%on verra pour la mise en forme aprĆØs...
+ %clƩs
+ \restoreKV[FracPeriod]% revenir au valeurs par dƩfaut
+ \setKV[FracPeriod]{#1}% lit les arguments optionnels
+ %les variables utiles
+ \IfEndWith{#2}{.}%
+ {%
+ \StrBefore{#2}{.}[\tmp@avt]%
+ \xdef\tmp@apr{0}%
+ \xdef\tmp@len@apr{0}%
+ }%
+ {%
+ \StrCut{#2}{.}{\tmp@avt}{\tmp@apr}%
+ \StrLen{\tmp@apr}[\tmp@len@apr]%
+ }%
+ \StrLen{#3}[\tmp@len@per]%
+ %raccourcis
+ \IfEndWith{#2}{.}%
+ {%
+ \xdef\tmp@enonce{\num{\tmp@avt}{,}\overline{#3}}%
+ }%
+ {%
+ \xdef\tmp@enonce{\num{#2}\overline{#3}}%
+ }%
+ %calculs
+ \xdef\tmp@num@brut{\xintieval{10**(\tmp@len@per+\tmp@len@apr)*\tmp@avt+10**(\tmp@len@per)*\tmp@apr-10**(\tmp@len@apr)*\tmp@avt+(#3)-\tmp@apr}}%
+ \xdef\tmp@denom@brut{\xintieval{10**(\tmp@len@per+\tmp@len@apr)-10**(\tmp@len@apr)}}%
+ \xdef\tmp@pgcd{\xinteval{gcd(\tmp@num@brut,\tmp@denom@brut)}}%
+ %rƩsolution OK
+ \ifboolKV[FracPeriod]{Solution}%
+ {%
+ %phrase d'accroche
+ \xintifboolexpr{\tmp@len@apr == 0}%
+ {%
+ \noindent On note $\FracPerVar=\tmp@enonce$.\par
+ \noindent La premiĆØre Ć©galitĆ© est donc \[\boxed{\FracPerVar=\tmp@enonce} \quad (1)\]
+ }%
+ {%
+ \noindent On note $\FracPerVar=\tmp@enonce$.\par
+ }%
+ \xintifboolexpr{\tmp@len@apr == 0}%
+ {}%
+ {%
+ \noindent On \textit{ramĆØne} la pĆ©riode prĆØs de la virgule en multipliant par $10^{\tmp@len@apr}$ : \[\boxed{10^{\tmp@len@apr}\times\FracPerVar=\num{\xinteval{\tmp@avt*10**(\tmp@len@apr)+\tmp@apr}}{,}\overline{#3}} \quad (1)\]
+ }%
+ \noindent On \textit{dƩcale} la pƩriode avant la virgule, en multipliant l'ƩgalitƩ (1) par $10^{\tmp@len@per}$ : \[10^{\tmp@len@per}\xintifboolexpr{\tmp@len@apr == 0}{}{\times10^{\tmp@len@apr}}\times\FracPerVar=10^{\tmp@len@per}\times\num{\xinteval{\tmp@avt*10**(\tmp@len@apr)+\tmp@apr}}{,}\overline{#3} \Rightarrow \boxed{10^{\xinteval{\tmp@len@per+\tmp@len@apr}}\times\FracPerVar = \num{\xintieval{10**(\tmp@len@per)*(\tmp@avt*10**(\tmp@len@apr)+\tmp@apr)+#3}}{,}\overline{#3}} \quad (2)\]
+ %soustraction
+ On soustrait les deux ƩgalitƩs, $(2)-(1)$, ce qui permet d'\textit{enlever} la partie dƩcimale :
+ \begin{align*}
+ 10^{\xinteval{\tmp@len@per+\tmp@len@apr}}\times\FracPerVar-\xintifboolexpr{\tmp@len@apr == 0}{}{10^{\tmp@len@apr}\times}\FracPerVar = \num{\xintieval{10**(\tmp@len@per)*(\tmp@avt*10**(\tmp@len@apr)+\tmp@apr)+#3}}{,}\overline{#3} -\num{\xinteval{\tmp@avt*10**(\tmp@len@apr)+\tmp@apr}}{,}\overline{#3} &\Rightarrow \big(10^{\xinteval{\tmp@len@per+\tmp@len@apr}}-\xintifboolexpr{\tmp@len@apr == 0}{1}{10^{\tmp@len@apr}}\big)\times\FracPerVar = \num{\xintieval{10**(\tmp@len@per)*(\tmp@avt*10**(\tmp@len@apr)+\tmp@apr)+#3}} - \num{\xintieval{\tmp@avt*10**(\tmp@len@apr)+\tmp@apr}} \\
+ \phantom{10^{\xinteval{\tmp@len@per+\tmp@len@apr}}\times\FracPerVar-10^{\tmp@len@apr}\times\FracPerVar = \num{\xintieval{10**(\tmp@len@per)*(\tmp@avt*10**(\tmp@len@apr)+\tmp@apr)+#3}}{,}\overline{#3} -\num{\xinteval{\tmp@avt*10**(\tmp@len@apr)+\tmp@apr}}{,}\overline{#3}} &\Rightarrow \num{\xinteval{10**(\tmp@len@per+\tmp@len@apr)-10**(\tmp@len@apr)}}\times\FracPerVar=\num{\xintieval{10**(\tmp@len@per)*(\tmp@avt*10**(\tmp@len@apr)+\tmp@apr)+#3- (\tmp@avt*10**(\tmp@len@apr)+\tmp@apr)}} \\
+ &\Rightarrow\FracPerVar = \ifboolKV[FracPeriod]{d}{\displaystyle}{}\frac{\num{\tmp@num@brut}}{\num{\tmp@denom@brut}}
+ \end{align*}
+ %affichage(s) OK
+ \noindent Ainsi on a \ensuremath{\tmp@enonce = \ifboolKV[FracPeriod]{d}{\displaystyle}{}\frac{\num{\tmp@num@brut}}{\num{\tmp@denom@brut}} \xintifboolexpr{\tmp@pgcd == 1}{}{=\ifboolKV[FracPeriod]{d}{\displaystyle}{}\frac{\num{\xintieval{\tmp@num@brut/\tmp@pgcd}}}{\num{\xintieval{\tmp@denom@brut/\tmp@pgcd}}}}%
+ }.\par%
+ }%
+ {}%
+ \ifboolKV[FracPeriod]{Brut}%
+ {%
+ \xdef\FracPerNum{\tmp@num@brut}%
+ \xdef\FracPerDenom{\tmp@denom@brut}%
+ \xdef\FracPerNumSimpl{\xintieval{(\tmp@num@brut)/gcd(\tmp@num@brut,\tmp@denom@brut)}}%
+ \xdef\FracPerDenomSimpl{\xintieval{(\tmp@denom@brut)/gcd(\tmp@num@brut,\tmp@denom@brut)}}%
+ }%
+ {}%
+ \ifboolKV[FracPeriod]{Simple}%
+ {%
+ %affichage(s) OK
+ \noindent\ensuremath{%
+ \ifboolKV[FracPeriod]{Enonce}%
+ {%
+ \tmp@enonce =
+ }%
+ {}%
+ \ifboolKV[FracPeriod]{d}{\displaystyle}{}\frac{\num{\tmp@num@brut}}{\num{\tmp@denom@brut}} \xintifboolexpr{\tmp@pgcd == 1}{}{=\ifboolKV[FracPeriod]{d}{\displaystyle}{}\frac{\num{\xintieval{\tmp@num@brut/\tmp@pgcd}}}{\num{\xintieval{\tmp@denom@brut/\tmp@pgcd}}}}%
+ }\par%
+ }%
+ {}%
+}
+
\endinput \ No newline at end of file
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-arithm.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-arithm.tex
index fcff96116f..cabba276fb 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-arithm.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-arithm.tex
@@ -1,12 +1,6 @@
% proflycee-tools-arithm.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
\RequirePackage{ifthen}
\RequirePackage{modulus}
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-ecritures.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-ecritures.tex
index 2db6379ed6..ec26d66da2 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-ecritures.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-ecritures.tex
@@ -1,12 +1,6 @@
% proflycee-tools-ecritures.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%===PACKAGE
\RequirePackage{interval}
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-geom.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-geom.tex
index b49e23440d..eb898aa85a 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-geom.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-geom.tex
@@ -1,12 +1,6 @@
% proflycee-tools-geom.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%%------PaveDroitTikZ
\defKV[paramspave]{%
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-graphiques.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-graphiques.tex
index 25c206b76f..f6695cacd2 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-graphiques.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-graphiques.tex
@@ -1,12 +1,6 @@
% proflycee-tools-graphiques.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%%------SPLINES
%commande utile pour extraire des infos d'une liste
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-listings.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-listings.tex
index adcc03f028..c6be201f71 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-listings.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-listings.tex
@@ -1,12 +1,6 @@
% proflycee-tools-listings.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%2.7.5 Ajout de clƩs pour PythonLst + Couleurs optionnelles pour PseudoCode
%2.7.3 Correction de la couleur des bordures
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-minted.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-minted.tex
index 49407898c4..87c152c191 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-minted.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-minted.tex
@@ -1,12 +1,6 @@
% proflycee-tools-minted.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
% 2.7.5 Argument optionnel pour les numƩros de lignes + changement dƩclaration environnements
%2.7.3 Correction de la couleur des bordures
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-piton.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-piton.tex
index 5c48f5e69a..ca63b2db89 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-piton.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-piton.tex
@@ -1,12 +1,6 @@
% proflycee-tools-piton.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%2.7.6 Correction du comportement de la console, avec une meilleure gestion de la largeur ^^ (merci Ć  ablasz ;-))
%2.7.5 Ajout d'un argument optionnel pour commencer les codes python Ơ un numƩro de ligne diffƩrent de 1
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-probas.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-probas.tex
index 37cd0a4793..963ac25f7a 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-probas.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-probas.tex
@@ -1,12 +1,6 @@
% proflycee-tools-probas.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%%------LOISPROBAS
%calculs "simples"
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-pythontex.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-pythontex.tex
index ea2dbf6066..ba19e70223 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-pythontex.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-pythontex.tex
@@ -1,12 +1,6 @@
% proflycee-tools-pythontex.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%2.7.5 Argument optionnel pour commencer la numƩrotation Ơ une autre ligne que 1
%2.7.3 Correction de la couleur des bordures
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-recreat.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-recreat.tex
index 880ac4cbb3..b80cc6fef6 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-recreat.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-recreat.tex
@@ -1,12 +1,6 @@
% proflycee-tools-recreat.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%%------FENƊTRE CALCUL FORMEL
\newcommand\CFchap{\textasciicircum}
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-stats.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-stats.tex
index 26c12c2c13..eafa4c5909 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-stats.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-stats.tex
@@ -1,12 +1,6 @@
% proflycee-tools-stats.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%2.6.8 Grille histogrammes non rƩguliers
%2.6.7 Histogrammes
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-suites.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-suites.tex
index 5cdd3234e3..f83f215d01 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-suites.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-suites.tex
@@ -1,12 +1,6 @@
% proflycee-tools-suites.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%%------CabWeb
\defKV[webrecurr]{%
diff --git a/macros/latex/contrib/proflycee/tex/proflycee-tools-trigo.tex b/macros/latex/contrib/proflycee/tex/proflycee-tools-trigo.tex
index cd85a0ed44..24ec136ca5 100644
--- a/macros/latex/contrib/proflycee/tex/proflycee-tools-trigo.tex
+++ b/macros/latex/contrib/proflycee/tex/proflycee-tools-trigo.tex
@@ -1,12 +1,6 @@
% proflycee-tools-trigo.tex
% Copyright 2023 CĆ©dric Pierquet
-% This work may be distributed and/or modified under the
-% conditions of the LaTeX Project Public License, either version 1.3
-% of this license or (at your option) any later version.
-% The latest version of this license is in
-% http://www.latex-project.org/lppl.txt
-% and version 1.3 or later is part of all distributions of LaTeX
-% version 2005/12/01 or later.
+% Released under the LaTeX Project Public License v1.3c or later, see http://www.latex-project.org/lppl.txt
%%------CercleTrigo
\defKV[cercletrigo]{%
diff --git a/macros/latex/contrib/q-and-a/Q-and-A.cls b/macros/latex/contrib/q-and-a/Q-and-A.cls
index c865647b68..ee0edba93b 100644
--- a/macros/latex/contrib/q-and-a/Q-and-A.cls
+++ b/macros/latex/contrib/q-and-a/Q-and-A.cls
@@ -12,7 +12,7 @@
\NeedsTeXFormat{LaTeX2e}[2022-06-01]
\ProvidesExplClass
{Q-and-A}
- {2023/11/17a} {}
+ {2023/11/19} {}
{Document class for typesetting Q&A conversation}
\keys_define:nn { Q-and-A }
@@ -40,6 +40,15 @@
, ChatGPT-dark .meta:n = { theme = ChatGPT-dark }
, ChatGPT~dark .meta:n = { theme = ChatGPT-dark }
, ChatGPT dark .meta:n = { theme = ChatGPT-dark }
+ , ChatGPT-classical .meta:n = { theme = ChatGPT-classical-light }
+ , ChatGPT-classical-light .meta:n = { theme = ChatGPT-classical-light }
+ , ChatGPT-classical~light .meta:n = { theme = ChatGPT-classical-light }
+ , ChatGPT~classical~light .meta:n = { theme = ChatGPT-classical-light }
+ , ChatGPT classical light .meta:n = { theme = ChatGPT-classical-light }
+ , ChatGPT-classical-dark .meta:n = { theme = ChatGPT-classical-dark }
+ , ChatGPT-classical~dark .meta:n = { theme = ChatGPT-classical-dark }
+ , ChatGPT~classical~dark .meta:n = { theme = ChatGPT-classical-dark }
+ , ChatGPT classical dark .meta:n = { theme = ChatGPT-classical-dark }
, numbered-question .bool_set:N = \l__QA_numbered_question_bool
, numbered-question .initial:n = { false }
@@ -132,6 +141,36 @@
\definecolor{QA-Q-back}{RGB}{ 52, 53, 65}
\definecolor{QA-Q-text}{RGB}{236,236,241}
\definecolor{QA-Q-emph}{RGB}{255,255,255}
+ \colorlet{QA-A-back}{QA-Q-back}
+ \colorlet{QA-A-text}{QA-Q-text}
+ \colorlet{QA-A-emph}{QA-Q-emph}
+ \colorlet{QA-N-back}{QA-Q-back}
+ \colorlet{QA-N-text}{QA-Q-text}
+ \colorlet{paper}{QA-Q-back}
+ \colorlet{main-text}{QA-Q-text}
+ \colorlet{emph-text}{QA-Q-text}
+ }
+
+\str_if_eq:onT { \l__QA_theme_str } { ChatGPT-light }
+ {
+ \definecolor{QA-Q-back}{RGB}{255,255,255}
+ \definecolor{QA-Q-text}{RGB}{ 52, 53, 65}
+ \definecolor{QA-Q-emph}{RGB}{ 0, 0, 0}
+ \colorlet{QA-A-back}{QA-Q-back}
+ \colorlet{QA-A-text}{QA-Q-text}
+ \colorlet{QA-A-emph}{QA-Q-emph}
+ \colorlet{QA-N-back}{QA-Q-back}
+ \colorlet{QA-N-text}{QA-Q-text}
+ \colorlet{paper}{QA-Q-back}
+ \colorlet{main-text}{QA-Q-text}
+ \colorlet{emph-text}{QA-Q-text}
+ }
+
+\str_if_eq:onT { \l__QA_theme_str } { ChatGPT-classical-dark }
+ {
+ \definecolor{QA-Q-back}{RGB}{ 52, 53, 65}
+ \definecolor{QA-Q-text}{RGB}{236,236,241}
+ \definecolor{QA-Q-emph}{RGB}{255,255,255}
\definecolor{QA-A-back}{RGB}{ 68, 70, 84}
\definecolor{QA-A-text}{RGB}{209,213,219}
\definecolor{QA-A-emph}{RGB}{255,255,255}
@@ -142,7 +181,7 @@
\colorlet{emph-text}{QA-Q-text}
}
-\str_if_eq:onT { \l__QA_theme_str } { ChatGPT-light }
+\str_if_eq:onT { \l__QA_theme_str } { ChatGPT-classical-light }
{
\definecolor{QA-Q-back}{RGB}{255,255,255}
\definecolor{QA-Q-text}{RGB}{ 52, 53, 65}
@@ -184,7 +223,7 @@
\dim_new:N \l_QA_list_labelsep_dim
\dim_set:Nn \l_QA_list_labelsep_dim { 1em }
-\exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+\str_if_in:NnT \l__QA_theme_str { ChatGPT }
{
\dim_set:Nn \l_QA_item_indentation_dim { .33em }
\dim_set:Nn \l_QA_list_indentation_dim { 4.5em + \l__QA_extra_left_margin_dim }
@@ -290,7 +329,17 @@
\tcbset{QA-additional/.style={}}
% ChatGPT style
-\exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+\str_if_in:NnT \l__QA_theme_str { ChatGPT }
+ {
+ \tcbset{QA-additional/.style={
+ fontupper=\sffamily,
+ code={\onehalfspacing},
+ top=1.5em,
+ bottom=1.5em,
+ }
+ }
+ }
+\str_if_in:NnT \l__QA_theme_str { ChatGPT-classical }
{
\tcbset{QA-additional/.style={
fontupper=\sffamily,
@@ -533,6 +582,25 @@
\dim_gset:Nn \labelsep { \l_tmpa_dim }
}
+\NewDocumentCommand \QASection { m }
+ {
+ \par\medskip\smallskip
+ \textbf{\larger[1.5]#1}
+ \par\smallskip
+ }
+\NewDocumentCommand \QASubSection { m }
+ {
+ \par\medskip
+ \textbf{\larger#1}
+ \par\smallskip
+ }
+\NewDocumentCommand \QASubSubSection { m }
+ {
+ \par\smallskip
+ \textbf{#1}
+ \par\smallskip
+ }
+
\newenvironment{QACompactCenter}
{\parskip=0pt\par\nopagebreak\centering}
{\par\noindent\ignorespacesafterend}
@@ -625,7 +693,7 @@
% \textcolor{emph-text}{\texttt{#1}}
\QACodebox{\vphantom{Ƅpgjy}#1}
}
-\exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+\str_if_in:NnT \l__QA_theme_str { ChatGPT }
{
\RenewDocumentCommand \QACode { m }
{
@@ -652,8 +720,14 @@
}
\NewDocumentEnvironment { QA_void } { } { } { }
+
+\str_new:N \g__QA_Q_name_str
\NewDocumentEnvironment { QA_Q } { D<>{} }
{
+ \str_if_empty:nF { #1 }
+ {
+ \str_gset:Nn \g__QA_Q_name_str { #1 }
+ }
\colorlet{paper}{QA-Q-back}
\colorlet{main-text}{QA-Q-text}
\colorlet{emph-text}{QA-Q-emph}
@@ -665,21 +739,38 @@
colback={QA-Q-back},
colupper={QA-Q-text},
]
- \exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
{ \vspace{-.5\parskip} }
\vspace{-.5\parskip} % due to "parbox=false"
\vspace{-\parskip}
\begin{QA-entry}
- \exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
{ \parskip=2\parskip }
\item[\hfill\color{QA-Q-text!33!QA-Q-back}\l_QA_logo_code_Q_tl]
+ \str_case:NnT \l__QA_theme_str
+ {
+ { ChatGPT-dark } {}
+ { ChatGPT-light } {}
+ }
+ {
+ \str_if_empty:NF \g__QA_Q_name_str
+ {
+ \textbf{ \g__QA_Q_name_str }\\
+ }
+ }
}
{
\end{QA-entry}
\end{tcolorbox}
}
+
+\str_new:N \g__QA_A_name_str
\NewDocumentEnvironment { QA_A } { D<>{} }
{
+ \str_if_empty:nF { #1 }
+ {
+ \str_gset:Nn \g__QA_A_name_str { #1 }
+ }
\colorlet{paper}{QA-A-back}
\colorlet{main-text}{QA-A-text}
\colorlet{emph-text}{QA-A-emph}
@@ -691,14 +782,25 @@
colback={QA-A-back},
colupper={QA-A-text},
]
- \exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
{ \vspace{-.5\parskip} }
\vspace{-.5\parskip} % due to "parbox=false"
\vspace{-\parskip}
\begin{QA-entry}
- \exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
{ \parskip=2\parskip }
\item[\hfill\color{QA-A-text!33!QA-A-back}\l_QA_logo_code_A_tl]
+ \str_case:NnT \l__QA_theme_str
+ {
+ { ChatGPT-dark } {}
+ { ChatGPT-light } {}
+ }
+ {
+ \str_if_empty:NF \g__QA_A_name_str
+ {
+ \textbf{ \g__QA_A_name_str }\\
+ }
+ }
}
{
\end{QA-entry}
@@ -709,7 +811,7 @@
\colorlet{paper}{QA-N-back}
\colorlet{main-text}{QA-N-text}
\colorlet{emph-text}{QA-N-emph}
- \exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
{
\colorlet{QA-code-title-back}{QA-A-back}
\colorlet{QA-code-title-text}{QA-A-text}
@@ -742,26 +844,46 @@
\RenewDocumentEnvironment { QA_A } { D<>{} }
{
+ \str_if_empty:nF { #1 }
+ {
+ \str_gset:Nn \g__QA_A_name_str { #1 }
+ }
\color{QA-A-text}
\vspace{1em}
- \exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
+ { \vspace{.5em} }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT-classical }
+ { \vspace{.5em} }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
{
- \vspace{1em}
\sffamily
\onehalfspacing
\vspace{-.5\parskip}
}
\vspace{-.5\parskip}
\begin{QA-entry}[leftmargin=.5mm, itemindent=0pt, labelsep=\l_QA_list_labelsep_dim, labelwidth=3em]
- \exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
{ \parskip=2\parskip }
\item[\hfill\color{QA-A-text!33!QA-A-back}\l_QA_logo_code_A_tl]
+ \str_case:NnT \l__QA_theme_str
+ {
+ { ChatGPT-dark } {}
+ { ChatGPT-light } {}
+ }
+ {
+ \str_if_empty:NF \g__QA_A_name_str
+ {
+ \textbf{ \g__QA_A_name_str }\\
+ }
+ }
}
{
\end{QA-entry}
\vspace{1em}
- \exp_args:No \str_if_in:nnT { \l__QA_theme_str } { ChatGPT }
- { \vspace{1em} }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT }
+ { \vspace{.5em} }
+ \str_if_in:NnT \l__QA_theme_str { ChatGPT-classical }
+ { \vspace{.5em} }
}
}
@@ -818,6 +940,10 @@
\bool_gset_false:N \g__QA_Q_multiple_counter_already_enabled_bool
\NewDocumentCommand \EnableMultipleQuestion { }
{
+ \hook_gput_next_code:nn { env/QA_Q/before } { \__QA_Q_multiple_enable_core: }
+ }
+\cs_new:Nn \__QA_Q_multiple_enable_core:
+ {
\bool_if:NF \g__QA_Q_multiple_counter_already_enabled_bool
{
\setcounter{QA_Q_aux}{\value{QA_Q}} % set the outer counter
@@ -841,6 +967,10 @@
}
\NewDocumentCommand \DisableMultipleQuestion { }
{
+ \hook_gput_next_code:nn { env/QA_Q/before } { \__QA_Q_multiple_disable_core: }
+ }
+\cs_new:Nn \__QA_Q_multiple_disable_core:
+ {
\bool_if:NT \g__QA_Q_multiple_counter_already_enabled_bool
{
\counterwithout{QA_Q}{QA_Q_aux}
@@ -857,10 +987,14 @@
\bool_gset_false:N \g__QA_A_multiple_counter_already_enabled_bool
\NewDocumentCommand \EnableMultipleAnswer { }
{
+ \hook_gput_next_code:nn { env/QA_A/before } { \__QA_A_multiple_enable_core: }
+ }
+\cs_new:Nn \__QA_A_multiple_enable_core:
+ {
\bool_if:NF \g__QA_A_multiple_counter_already_enabled_bool
{
\setcounter{QA_A_aux}{\value{QA_A}} % set the outer counter
- % \addtocounter{QA_A_aux}{1}
+ \addtocounter{QA_A_aux}{1}
\setcounter{QA_A}{0} % reset the inner counter
\counterwithin{QA_A}{QA_A_aux}
\hook_gput_code:nnn { env/QA_A/begin } { Q-and-A-multi-A }
@@ -880,11 +1014,15 @@
}
\NewDocumentCommand \DisableMultipleAnswer { }
{
+ \hook_gput_next_code:nn { env/QA_A/before } { \__QA_A_multiple_disable_core: }
+ }
+\cs_new:Nn \__QA_A_multiple_disable_core:
+ {
\bool_if:NT \g__QA_A_multiple_counter_already_enabled_bool
{
\counterwithout{QA_A}{QA_A_aux}
\setcounter{QA_A}{\value{QA_A_aux}} % set the outer counter
- % \addtocounter{QA_A}{-1}
+ \addtocounter{QA_A}{-1}
\hook_gremove_code:nn { env/QA_A/begin } { Q-and-A-multi-A }
\hook_gremove_code:nn { env/QA_Q/begin } { Q-and-A-multi-A }
}
@@ -1118,17 +1256,29 @@
{ āš› \c{section} }
\l_QA_tmp_tl
\regex_replace_all:nnN
- { \#\#\#\# }
+ { \#\#\#\#\- }
{ āš› \c{subsubsection}\* }
\l_QA_tmp_tl
\regex_replace_all:nnN
- { \#\#\# }
+ { \#\#\#\- }
{ āš› \c{subsection}\* }
\l_QA_tmp_tl
\regex_replace_all:nnN
- { \#\# }
+ { \#\#\- }
{ āš› \c{section}\* }
\l_QA_tmp_tl
+ \regex_replace_all:nnN
+ { \#\#\#\# }
+ { \c{QASubSubSection} }
+ \l_QA_tmp_tl
+ \regex_replace_all:nnN
+ { \#\#\# }
+ { \c{QASubSection} }
+ \l_QA_tmp_tl
+ \regex_replace_all:nnN
+ { \#\# }
+ { \c{QASection} }
+ \l_QA_tmp_tl
\regex_replace_all:nnN
{ \`\` }
@@ -1358,6 +1508,14 @@
{
\end { Q-and-A }
\vspace{-1mm}
+ \str_case:NnT \l__QA_theme_str
+ {
+ { ChatGPT-dark } {}
+ { ChatGPT-light } {}
+ }
+ {
+ \vspace{1em}
+ }
\egroup
\dimen0=\dp0
\pdfpageheight=\dimexpr\ht0\relax
diff --git a/macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple-content.tex b/macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple-content.tex
index a7ee5787ed..9dabdc5dc7 100644
--- a/macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple-content.tex
+++ b/macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple-content.tex
@@ -28,7 +28,7 @@
Answer.
"
- Now stop the **multiple question** mode, and start the **multiple answer** mode.
+ Now stop the multiple question mode, and start the **multiple answer** mode.
\DisableMultipleQuestion
diff --git a/macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple.pdf b/macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple.pdf
index 8c7b209882..620746bd50 100644
--- a/macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple.pdf
+++ b/macros/latex/contrib/q-and-a/demo/mode-multiple/Q-and-A-demo-multiple.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-content.tex b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-content.tex
new file mode 100644
index 0000000000..68e24d871e
--- /dev/null
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-content.tex
@@ -0,0 +1,81 @@
+"
+ The following conversation is generated by ChatGPT (with GPT-3.5) on \TheDate{2023-11-01}.
+
+? <You>
+ What is artificial intelligence (AI)?
+
+: <ChatGPT>
+ Artificial intelligence, or AI, refers to the development of computer systems that can perform tasks that typically require human intelligence, such as learning, reasoning, problem-solving, and decision-making. AI technologies aim to simulate human cognitive functions in machines, enabling them to understand and respond to data, make predictions, and adapt to changing circumstances.
+
+?
+ What are some common applications of AI?
+
+:
+ AI has a wide range of applications, including:
+
+ [Natural Language Processing (NLP)]
+ [*] Chatbots
+ [*] Language translation
+ [*] Sentiment analysis
+
+ [Computer Vision]
+ [*] Image and video analysis
+ [*] Facial recognition
+ [*] Autonomous vehicles
+
+ [Machine Learning]
+ [*] Predictive analytics
+ [*] Recommendation systems
+ [*] Fraud detection
+
+ [Robotics]
+ [*] Automation in manufacturing
+ [*] Healthcare assistance
+ [*] Service industries
+
+ [Healthcare]
+ [*] Disease diagnosis
+ [*] Drug discovery
+ [*] Personalized treatment plans
+
+ [Finance]
+ [*] Algorithmic trading
+ [*] Risk assessment
+ [*] Customer support
+
+?
+ How does machine learning relate to AI?
+
+:
+ Machine learning is a subfield of AI that focuses on developing algorithms and models that allow computers to learn from and make predictions or decisions based on data. It's a crucial component of AI because it enables systems to improve their performance over time by learning from past experiences.
+
+?
+ Are there different types of machine learning?
+
+:
+ Yes, there are three main types of machine learning:
+
+ [Supervised Learning]
+ In this type, the model is trained on labeled data, making predictions based on known examples.
+
+ [Unsupervised Learning]
+ Unsupervised learning involves finding patterns or structures in unlabeled data without specific guidance.
+
+ [Reinforcement Learning]
+ Reinforcement learning is about training agents to make sequences of decisions to maximize a reward in an environment.
+
+?
+ Can you provide an example of Python code for a simple machine learning model?
+
+:
+ Certainly! Here's a basic Python code example for training a linear regression model using the popular scikit-learn library:
+
+ == [python] {code/Q-and-A-demo-ChatGPT-classical-code-1.py}
+
+ This code demonstrates a simple linear regression model for predicting housing prices. You can use scikit-learn to create and evaluate various machine learning models in Python.
+
+?
+ What are some ethical considerations in AI and machine learning?
+
+:
+ Ethical concerns in AI and machine learning include issues like bias in algorithms, data privacy, job displacement due to automation, and the responsible use of AI in areas like healthcare and law enforcement. It's important to address these concerns to ensure that AI benefits society as a whole.
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-dark.pdf b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-dark.pdf
new file mode 100644
index 0000000000..f01abba240
--- /dev/null
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-dark.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-light.pdf b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-light.pdf
new file mode 100644
index 0000000000..049998b187
--- /dev/null
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical-light.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical.tex b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical.tex
new file mode 100644
index 0000000000..2b93876f38
--- /dev/null
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/Q-and-A-demo-ChatGPT-classical.tex
@@ -0,0 +1,51 @@
+\documentclass[%11pt,
+ use theme = ChatGPT-classical-light,
+ % use theme = ChatGPT-classical-dark,
+ scroll,
+]{Q-and-A}
+
+% The User Logo
+\SetLogoCode[Q]{%
+ \smash{\raisebox{-.65\baselineskip}{%
+ \begin{tikzpicture}
+ \node [inner sep=0pt] at (0,0) {\includegraphics[height=1.5\baselineskip]{Q-and-A-demo-ChatGPT-classical-logo-User}};
+ \draw [QA-Q-back, rounded corners=.15\baselineskip, line width=.2\baselineskip]
+ (current bounding box.north west) --
+ (current bounding box.north east) --
+ (current bounding box.south east) --
+ (current bounding box.south west) -- cycle;
+ \end{tikzpicture}%
+ }\hspace{-.25em}%
+ }}
+% The ChatGPT Logo
+\SetLogoCode[A]{%
+ \smash{\raisebox{-.65\baselineskip}{%
+ \begin{tikzpicture}
+ \node [inner sep=0pt] at (0,0) {\includegraphics[height=1.5\baselineskip]{Q-and-A-demo-ChatGPT-classical-logo-ChatGPT}};
+ \draw [QA-A-back, rounded corners=.15\baselineskip, line width=.2\baselineskip]
+ (current bounding box.north west) --
+ (current bounding box.north east) --
+ (current bounding box.south east) --
+ (current bounding box.south west) -- cycle;
+ \end{tikzpicture}%
+ }\hspace{-.25em}%
+ }}
+
+
+\begin{document}
+
+
+:: {Q-and-A-demo-ChatGPT-classical-content}
+
+"
+ Below is the code of this conversation.
+
+ == {Q-and-A-demo-ChatGPT-classical-content}
+
+"
+ Below is the code of the main document.
+
+ == [latex] {\jobname}
+
+
+\end{document}
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/code/Q-and-A-example-code-1.py b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/code/Q-and-A-demo-ChatGPT-classical-code-1.py
index ac8e3e09c0..ac8e3e09c0 100644
--- a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/code/Q-and-A-example-code-1.py
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/code/Q-and-A-demo-ChatGPT-classical-code-1.py
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-logo-ChatGPT.pdf b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/images/Q-and-A-demo-ChatGPT-classical-logo-ChatGPT.pdf
index bd89da4131..bd89da4131 100644
--- a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-logo-ChatGPT.pdf
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/images/Q-and-A-demo-ChatGPT-classical-logo-ChatGPT.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-logo-User.pdf b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/images/Q-and-A-demo-ChatGPT-classical-logo-User.pdf
index fc3a741085..fc3a741085 100644
--- a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-logo-User.pdf
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT-classical/images/Q-and-A-demo-ChatGPT-classical-logo-User.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-content.tex b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-content.tex
index 8db7a03a33..1d6d4cc0ab 100644
--- a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-content.tex
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-content.tex
@@ -1,10 +1,10 @@
"
The following conversation is generated by ChatGPT (with GPT-3.5) on \TheDate{2023-11-01}.
-?
+? <You>
What is artificial intelligence (AI)?
-:
+: <ChatGPT>
Artificial intelligence, or AI, refers to the development of computer systems that can perform tasks that typically require human intelligence, such as learning, reasoning, problem-solving, and decision-making. AI technologies aim to simulate human cognitive functions in machines, enabling them to understand and respond to data, make predictions, and adapt to changing circumstances.
?
@@ -70,7 +70,7 @@
:
Certainly! Here's a basic Python code example for training a linear regression model using the popular scikit-learn library:
- == [python] {code/Q-and-A-example-code-1.py}
+ == [python] {code/Q-and-A-demo-ChatGPT-code-1.py}
This code demonstrates a simple linear regression model for predicting housing prices. You can use scikit-learn to create and evaluate various machine learning models in Python.
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-dark.pdf b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-dark.pdf
index 9ccbae5242..6f06282c23 100644
--- a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-dark.pdf
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-dark.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-light.pdf b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-light.pdf
index 82349a5414..d0929037aa 100644
--- a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-light.pdf
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT-light.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT.tex b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT.tex
index fb5be3e4ce..bcbbdc5496 100644
--- a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT.tex
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/Q-and-A-demo-ChatGPT.tex
@@ -6,37 +6,29 @@
% The User Logo
\SetLogoCode[Q]{%
- \smash{\raisebox{-.65\baselineskip}{%
+ \smash{\raisebox{-.35\baselineskip}{%
\begin{tikzpicture}
- \node [inner sep=0pt] at (0,0) {\includegraphics[height=1.5\baselineskip]{Q-and-A-demo-logo-User}};
- \draw [QA-Q-back, rounded corners=.15\baselineskip, line width=.2\baselineskip]
- (current bounding box.north west) --
- (current bounding box.north east) --
- (current bounding box.south east) --
- (current bounding box.south west) -- cycle;
- \clip (current bounding box.north west) --
- (current bounding box.north east) --
- (current bounding box.south east) --
- (current bounding box.south west) -- cycle;
+ \clip (0,0) circle (.54\baselineskip);
+ \draw [QA-A-emph, line width=.04\baselineskip]
+ (0,0) circle (.52\baselineskip);
+ \node [inner sep=0pt, opacity=.7] at (0,0) {\includegraphics[height=1.2\baselineskip]{Q-and-A-demo-ChatGPT-logo-User}};
+ \clip (0,0) circle (.5\baselineskip);
+ \node [inner sep=0pt] at (0,0) {\includegraphics[height=1.2\baselineskip]{Q-and-A-demo-ChatGPT-logo-User}};
\end{tikzpicture}%
- }\hspace{-.25em}%
+ }\hspace{-.75em}%
}}
% The ChatGPT Logo
\SetLogoCode[A]{%
- \smash{\raisebox{-.65\baselineskip}{%
+ \smash{\raisebox{-.35\baselineskip}{%
\begin{tikzpicture}
- \node [inner sep=0pt] at (0,0) {\includegraphics[height=1.5\baselineskip]{Q-and-A-demo-logo-ChatGPT}};
- \draw [QA-A-back, rounded corners=.15\baselineskip, line width=.2\baselineskip]
- (current bounding box.north west) --
- (current bounding box.north east) --
- (current bounding box.south east) --
- (current bounding box.south west) -- cycle;
- \clip (current bounding box.north west) --
- (current bounding box.north east) --
- (current bounding box.south east) --
- (current bounding box.south west) -- cycle;
+ \clip (0,0) circle (.54\baselineskip);
+ \draw [QA-A-emph, line width=.04\baselineskip]
+ (0,0) circle (.52\baselineskip);
+ \node [inner sep=0pt, opacity=.7] at (0,0) {\includegraphics[height=1.2\baselineskip]{Q-and-A-demo-ChatGPT-logo-ChatGPT}};
+ \clip (0,0) circle (.5\baselineskip);
+ \node [inner sep=0pt] at (0,0) {\includegraphics[height=1.2\baselineskip]{Q-and-A-demo-ChatGPT-logo-ChatGPT}};
\end{tikzpicture}%
- }\hspace{-.25em}%
+ }\hspace{-.75em}%
}}
@@ -45,6 +37,8 @@
:: {Q-and-A-demo-ChatGPT-content}
+---
+
"
Below is the code of this conversation.
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/code/Q-and-A-demo-ChatGPT-code-1.py b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/code/Q-and-A-demo-ChatGPT-code-1.py
new file mode 100644
index 0000000000..ac8e3e09c0
--- /dev/null
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/code/Q-and-A-demo-ChatGPT-code-1.py
@@ -0,0 +1,25 @@
+# Import the necessary libraries
+from sklearn import datasets
+from sklearn.model_selection import train_test_split
+from sklearn.linear_model import LinearRegression
+from sklearn.metrics import mean_squared_error
+
+# Load a sample dataset (e.g., the Boston Housing dataset)
+data = datasets.load_boston()
+X, y = data.data, data.target
+
+# Split the dataset into training and testing sets
+X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.2, random_state=42)
+
+# Create a linear regression model
+model = LinearRegression()
+
+# Train the model on the training data
+model.fit(X_train, y_train)
+
+# Make predictions on the test data
+y_pred = model.predict(X_test)
+
+# Calculate the mean squared error to evaluate the model
+mse = mean_squared_error(y_test, y_pred)
+print(f"Mean Squared Error: {mse}") \ No newline at end of file
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-ChatGPT-logo-ChatGPT.pdf b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-ChatGPT-logo-ChatGPT.pdf
new file mode 100644
index 0000000000..bd89da4131
--- /dev/null
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-ChatGPT-logo-ChatGPT.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-ChatGPT-logo-User.pdf b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-ChatGPT-logo-User.pdf
new file mode 100644
index 0000000000..fc3a741085
--- /dev/null
+++ b/macros/latex/contrib/q-and-a/demo/theme-ChatGPT/images/Q-and-A-demo-ChatGPT-logo-User.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/doc/Q-and-A-doc.pdf b/macros/latex/contrib/q-and-a/doc/Q-and-A-doc.pdf
index f810f598d1..aaf9b6c812 100644
--- a/macros/latex/contrib/q-and-a/doc/Q-and-A-doc.pdf
+++ b/macros/latex/contrib/q-and-a/doc/Q-and-A-doc.pdf
Binary files differ
diff --git a/macros/latex/contrib/q-and-a/doc/Q-and-A-doc.tex b/macros/latex/contrib/q-and-a/doc/Q-and-A-doc.tex
index 369b6efd90..ef442a2259 100644
--- a/macros/latex/contrib/q-and-a/doc/Q-and-A-doc.tex
+++ b/macros/latex/contrib/q-and-a/doc/Q-and-A-doc.tex
@@ -5,8 +5,8 @@
scroll,
]{Q-and-A}
-\def\PackageVersion{2023/11/17}
-\def\PackageSubVersion{a}
+\def\PackageVersion{2023/11/19}
+\def\PackageSubVersion{}
\newcommand{\QApackage}{{\normalfont\textsf{Q-and-A}}}
@@ -72,10 +72,19 @@
\begin{itemize}
\item Font size options such as `11pt`, `12pt`.
\item `scroll`: turn the scroll mode on, which generates a single-page pdf similar to a long screenshot. It is recommended to use this option if your document contains some large piece of code.
- \item `use theme = \meta{theme}`: use the selected theme, available choices include: `default` (like the current document), `ChatGPT-light` and `ChatGPT-dark` (see the demo documents).
+ \item `use theme = \meta{theme}`: use the selected theme, available choices include:
+ \begin{itemize}
+ \item `default` (like the current document);
+ \item `ChatGPT-light` and `ChatGPT-dark` (see the demo documents);
+ \item `ChatGPT-classical-light` and `ChatGPT-classical-dark` (see the demo documents).
+ \end{itemize}
\item `numbered question`, or `question number`: enable the numbering of questions.
\item `numbered answer`, or `answer number`: enable the numbering of answers.
- \item `multiple question` and `multiple answer`: enable subcounter for questions and answers. This can also be enabled/disabled manually in the middle of the document, via `\textbackslash EnableMultipleQuestion` / `\textbackslash DisableMultipleQuestion` and `\textbackslash EnableMultipleAnswer` / `\textbackslash DisableMultipleAnswer`.
+ \item `multiple question` and `multiple answer`: enable subcounter for questions and answers. This can also be enabled/disabled manually in the middle of the document, via:
+ \begin{itemize}
+ \item `\textbackslash EnableMultipleQuestion` / `\textbackslash DisableMultipleQuestion` and
+ \item `\textbackslash EnableMultipleAnswer` / `\textbackslash DisableMultipleAnswer`.
+ \end{itemize}
\item `smaller subcounter`: when `multiple question` (and/or `multiple answer`) is enabled, use this option to show the subcounter in a smaller size.
\item `enlarge left margin by = \meta{length}`, or `increase left margin by = \meta{length}`: enlarge the left margin by the amount of `\meta{length}`. This would be useful if there are so many questions/answers that the numbering becomes too long to fit in the margin.
\QANote{Here `\meta{length}` should be specified with absolute unit like `pt`, `cm`, `mm`, `in`, etc., but not with unit like `ex` or `em`.}
@@ -94,7 +103,7 @@
\item An answer begins with the prefix `A:` or `:`.
\item A narration begins with the prefix `N:` or `"`.
\end{itemize}
- >>> Note that this depends on the current language. The prefixes `?`, `:` and `"` being universal, yet~ā€”
+ \QANote{Note that this depends on the current language. The prefixes `?`, `:` and `"` being universal, yet~ā€”
\begin{itemize}
\item for French, it is Q\&R\&N, thus the alphabetical prefixes become `Q:`, `R:` and `N:`;
\item for German, it is F\&A\&E, thus the alphabetical prefixes become `F:`, `A:` and `E:`;
@@ -104,7 +113,9 @@
\item for Spanish, it is P\&R\&N, thus the alphabetical prefixes become `P:`, `R:` and `N:`;
\item for simplified Chinese, it is also possible to use the prefix `问ļ¼š` for questions, `ē­”ļ¼š` for answers, and `ę³Øļ¼š` for narrations; similarly for traditional Chinese;
\item for Chinese or Japanese, it is also possible to use the prefix `ļ¼Ÿ` for questions, `ļ¼š` for answers, and `ā€œ`, `ā€` or `怌` for narrations.
- \end{itemize}
+ \end{itemize}}
+ You may specify the identity of the current speaker by placing `<\meta{name}>` after the prefix (there could be some spaces in between). For example, `? <You>` would set the questioner's name to `You`. How this name is disposed of depends on your current selected theme.
+ \QANote{The identity for the current type would be recorded, so unless you wish to change it, you only need to write it once.}
[Emphasize and Bold]
\begin{itemize}
@@ -151,14 +162,19 @@
[Sections]
\begin{itemize}
- \item You may start a new (*unnumbered*) ---
+ \item Inside questions/answers, you may start a new (*unnumbered*) ---
\begin{itemize}
\item section, via `\textsharp\textsharp{} \{\meta{section title}\}`;
\item subsection, via `\textsharp\textsharp\textsharp{} \{\meta{subsection title}\}`;
\item subsubsection, via `\textsharp\textsharp\textsharp\textsharp{} \{\meta{subsubsection title}\}`;
\end{itemize}
- \item If you wish to use the *numbered* version, write `\textsharp\textsharp+`, `\textsharp\textsharp\textsharp+` and `\textsharp\textsharp\textsharp\textsharp+` instead.
+ \item To start a section outside questions/answers:
+ \begin{itemize}
+ \item For the *unnumbered* version, write `\textsharp\textsharp-`, `\textsharp\textsharp\textsharp-` and `\textsharp\textsharp\textsharp\textsharp-` instead.
+ \item For the *numbered* version, write `\textsharp\textsharp+`, `\textsharp\textsharp\textsharp+` and `\textsharp\textsharp\textsharp\textsharp+` instead.
+ \end{itemize}
\end{itemize}
+ \QANote{Note that, *numbered* sections inside questions/answers are not provided, since they do not seem to be quite useful (for example, Markdown doesn't provide numbered sections) and, on the other hand, one could simply use emphasized enumerate.}
[Input/Include Files]
\begin{itemize}
@@ -273,6 +289,8 @@
%% 2023-11-05, solved with the new option "answer outside the box".
\item Due to the current implementation, though it is already possible to automatically adopt the identifiers and labels for supported languages, you still need to use the identifiers `Q`, `A` and `N` when setting them.
\item Currently, for typesetting questions and answers, the text is in fact being put into some sort of `description` list (upon reflection, why did I do this? I could have simply put the label into margin...). As a result, the level of lists might be slightly messed up, which could sometimes lead to issues with the list labels.
+ \item Some vertical and horizontal spacing still needs to be fine-tuned.
+ \item The code for all those themes is currently mixed up, which poses difficulties for maintenance and expandability.
\end{itemize}
diff --git a/macros/latex/contrib/starray/README.md b/macros/latex/contrib/starray/README.md
index e00db9e4a1..5079dcbc3a 100644
--- a/macros/latex/contrib/starray/README.md
+++ b/macros/latex/contrib/starray/README.md
@@ -73,7 +73,10 @@ The Current Maintainer of this work is Alceu Frigeri
## Changelog
-* Version 1.3 (this)
+* Version 1.4 (this)
+ - added a few functions _set_iter_from_hash:nn and _iterate_over:n.
+
+* Version 1.3
- Fixed issue #4, where (in some instances) _set_from_keyval could render a quark loop.
* Version 1.2
diff --git a/macros/latex/contrib/starray/doc/starray.pdf b/macros/latex/contrib/starray/doc/starray.pdf
index 9523653f0a..b030731578 100644
--- a/macros/latex/contrib/starray/doc/starray.pdf
+++ b/macros/latex/contrib/starray/doc/starray.pdf
Binary files differ
diff --git a/macros/latex/contrib/starray/doc/starray.tex b/macros/latex/contrib/starray/doc/starray.tex
index 5837d2308f..615d8fe92a 100644
--- a/macros/latex/contrib/starray/doc/starray.tex
+++ b/macros/latex/contrib/starray/doc/starray.tex
@@ -15,7 +15,7 @@
%%
%% The Current Maintainer of this work is Alceu Frigeri
%%
-%% This is version 1.3 (2023/06/04)
+%% This is version 1.4 (2023/11/18)
%%
%% The list of files that compose this work can be found in the README.md file at
%% https://ctan.org/pkg/starray
@@ -450,6 +450,18 @@ Before the reset \tsobj[marg]{st-root.subY.subYYY} was equivalent to \tsobj[marg
+\begin{codedescribe}[code,new=2023/11/04]{\starray_set_iter_from_hash:nn,\starray_set_iter_from_hash:nnTF}
+\begin{codesyntax}%
+\tsmacro{\starray_set_iter_from_hash:nn}{starray-ref,hash}
+\tsmacro{\starray_set_iter_from_hash:nnTF}{starray-ref,hash,if-true,if-false}
+\end{codesyntax}
+\end{codedescribe}
+\tsmacro{\starray_set_iter_from_hash:nn}{starray-ref,hash} will set iter based on the \tsobj[meta]{hash} used when instantiating a term (see \ref{pack:instantiate} ).
+\begin{tsremark}
+A warning is raised (see \ref{pack:options}) in case of a \tsobj[marg]{starray-ref} syntax error or invalid \tsobj[meta]{hash}. The branching version doesn't raise any warning.
+\end{tsremark}
+
+
\begin{codedescribe}{\starray_get_iter:n,\starray_get_iter:nN,\starray_get_iter:nNTF}
\begin{codesyntax}%
\tsmacro{\starray_get_iter:n}{starray-ref}
@@ -495,6 +507,21 @@ A warning is raised (see \ref{pack:options}) in case of a \tsobj[marg]{starray-r
This can be used after any command which 'parses a term', for instance \tsobj{\starray_term_syntax:n}, see section \ref{conditionals:terms}, but it only makes sense (and returns a reliable/meaningful result) IF the last parser operation was successfully executed.
\end{tsremark}
+\begin{codedescribe}[code,new=2023/11/04]{\starray_iterate_over:nn,\starray_iterate_over:nnTF}
+\begin{codesyntax}%
+\tsmacro{\starray_iterate_over:nn}{starray-ref,code}
+\tsmacro{\starray_iterate_over:nnTF}{starray-ref,code,if-true,if-false}
+\end{codesyntax}
+\tsobj{\starray_iterate_over:nn} will reset the \tsobj[marg]{starray-ref} iterator, and then execute \tsobj[marg]{code} for each valid value of \tsobj{iter}. At the loop's end, the \tsobj[marg]{starray-ref} iterator will point to the last element of it. The \tsobj[marg]{if-true} is executed, at the loop's end if there is no syntax error. Similarly \tsobj[marg]{if-false} is only execute if a syntax error is detected.
+\end{codedescribe}
+\begin{tsremark}
+\tsobj{\starray_iterate_over:nn} Creates a local group, so that one can recurse over sub-structures. Be aware, then, that \tsobj[marg]{code} is executed in said local group.
+\end{tsremark}
+\begin{tsremark}
+A warning is raised (see \ref{pack:options}) in case of a \tsobj[marg]{starray-ref} syntax error. The branching version doesn't raise any warning.
+\end{tsremark}
+
+
\section{Changing and recovering starray properties}\label{pack:get/set}
diff --git a/macros/latex/contrib/starray/latex/starray.sty b/macros/latex/contrib/starray/latex/starray.sty
index 0bfe015ab2..fbbb668458 100644
--- a/macros/latex/contrib/starray/latex/starray.sty
+++ b/macros/latex/contrib/starray/latex/starray.sty
@@ -12,7 +12,7 @@
%%
%% The Current Maintainer of this work is Alceu Frigeri
%%
-%% This is version 1.3 (2023/06/04)
+%% This is version 1.4 (2023/11/18)
%%
%% The list of files that compose this work can be found in the README.md file at
%% https://ctan.org/pkg/starray
@@ -24,8 +24,8 @@
\ProvidesExplPackage
{starray}
- {2023/06/04}
- {1.3}
+ {2023/11/18}
+ {1.4}
{A structured array/hash of properties}
%%%%%%%
@@ -38,8 +38,8 @@
{
name .code:n = starray ,
prefix .code:n = starray ,
- date .code:n = 2023/06/04,
- version .code:n = 1.3 ,
+ date .code:n = 2023/11/18,
+ version .code:n = 1.4 ,
description .code:n = A~structured~array/hash~of~properties
}
\cs_if_exist:NF \__codedesc_pkg_info:nn
@@ -145,6 +145,7 @@
\cs_generate_variant:Nn \seq_gput_right:Nn {ce}
\cs_generate_variant:Nn \int_to_Alph:n {e}
+\cs_generate_variant:Nn \int_gset:Nn {Ne}
\cs_generate_variant:Nn \prop_put:Nnn {Nee , cee}
\cs_generate_variant:Nn \prop_gput:Nnn {Nee , cee}
@@ -1088,6 +1089,63 @@
%%%% \starray_set_iter
%%%%
%%%%%%%%%%%%%%%
+\prg_new_protected_conditional:Npnn \__starray_set_iter_from_hash:nn #1#2 {T , F, TF}
+ {
+ \prop_get:cnN {\l__starray_prefix_tl #1 _base_prop} {iter_hash} \l_tmpa_prop
+ \prop_get:NnNTF \l_tmpa_prop {#2} \l_tmpa_tl
+ {
+ \int_gset:Nn
+ { \prop_item:cn {\l__starray_prefix_tl #1 _base_prop} {iter} }
+ { \l_tmpa_tl }
+ \prg_return_true:
+ }
+ {
+ \prg_return_false:
+ }
+ }
+
+
+\cs_new_protected:Npn \starray_set_iter_from_hash:nn #1#2
+ {
+ \__starray_parser:nnTF {\c__starray_no_idx_ending_bool}{#1}
+ {
+ \__starray_set_iter_from_hash:nnTF {\l__starray_parsed_ref_tl}{#2}
+ {
+ \__starray_set_sub_iter:nnn {}{\l__starray_parsed_ref_tl}{}
+ }
+ {
+ \msg_warning:nnnn {starray} {reference / iter} {iterhash:1} {#1}{#2}
+ }
+ }
+ {
+ \__starray_msg_dispatch:
+ \msg_warning:nnnn {starray} {syntax / iter} {iter:1} {#1}
+ } % returns nothing by default
+ }
+
+\prg_new_protected_conditional:Npnn \starray_set_iter_from_hash:nn #1#2 {T, F, TF}
+ {
+ \bool_set_true:N \l__starray_rtn_bool
+
+ \__starray_parser:nnTF {\c__starray_no_idx_ending_bool}{#1}
+ {
+ \__starray_set_iter_from_hash:nnTF {\l__starray_parsed_ref_tl}{#2}
+ {
+ \__starray_set_sub_iter:nnn {}{\l__starray_parsed_ref_tl}{}
+ \prg_return_true:
+ }
+ {
+ \bool_set_false:N \l__starray_rtn_bool
+ \prg_return_false:
+ }
+ }
+ {
+ \bool_set_false:N \l__starray_rtn_bool
+ \seq_clear:N \l__starray_msg_seq
+ \prg_return_false:
+ } % returns nothing by default
+ }
+
\cs_new_protected:Npn \starray_set_iter:nn #1#2
{
@@ -1226,6 +1284,62 @@
}
}
+
+%%%%%%%%%%%%%%%
+%%%%
+%%%% \starray_iterate_over
+%%%%
+%%%%%%%%%%%%%%%
+\bool_new:N \l__starray_iterate_bool
+
+\cs_new_protected:Npn \starray_iterate_over:nn #1#2
+ {
+
+ \bool_if_exist:cF {l__starray_iterate_ #1 _bool}
+ { \bool_new:c {l__starray_iterate_ #1 _bool} }
+ \starray_reset_iter:nTF {#1}
+ {
+ \bool_gset_true:c {l__starray_iterate_ #1 _bool}
+ \bool_do_while:cn {l__starray_iterate_ #1 _bool}
+ {
+
+ #2
+
+ \starray_next_iter:nTF {#1}
+ { \bool_gset_true:c {l__starray_iterate_ #1 _bool} }
+ { \bool_gset_false:c {l__starray_iterate_ #1 _bool} }
+ }
+ }
+ {
+ \bool_set_false:N \l__starray_rtn_bool
+ \msg_warning:nnnn {starray} {syntax / iter} {iter:6} {#1}
+ }
+
+ }
+
+\prg_new_protected_conditional:Npnn \starray_iterate_over:nn #1#2 {T, F, TF}
+ {
+ \bool_if_exist:cF {l__starray_iterate_#1_bool}{\bool_new:c {l__starray_iterate_#1_bool}}
+ \starray_reset_iter:nTF {#1}
+ {
+ \bool_gset_true:c {l__starray_iterate_#1_bool}
+ \bool_do_while:cn {l__starray_iterate_#1_bool}
+ {
+ #2
+ \starray_next_iter:nF {#1}
+ %{\bool_gset_true:c {l__starray_iterate_#1_bool}}
+ {\bool_gset_false:c {l__starray_iterate_#1_bool}}
+ }
+ \prg_return_true:
+ }
+ {
+ \seq_clear:N \l__starray_msg_seq
+ \prg_return_false:
+ }
+ }
+
+
+
%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%
%%%%
@@ -1265,7 +1379,7 @@
%%%%%%%%%%%%%%%%
%%%
-%%% WARNING: This is uses the 'last parsed term'.
+%%% WARNING: This uses the 'last parsed term'.
%%%
%%%%%%%%%%%%%%%%
\cs_new:Npn \starray_parsed_get_prop:n #1
diff --git a/macros/latex/contrib/tagpdf/README.md b/macros/latex/contrib/tagpdf/README.md
index 4af8236a53..989f3e4c0a 100644
--- a/macros/latex/contrib/tagpdf/README.md
+++ b/macros/latex/contrib/tagpdf/README.md
@@ -1,6 +1,6 @@
#tagpdf ā€” A package to create tagged pdf
-Packageversion: 0.98p
-Packagedate: 2023/11/17
+Packageversion: 0.98q
+Packagedate: 2023/11/19
Author: Ulrike Fischer
## License
diff --git a/macros/latex/contrib/tagpdf/ex-AF-file.pdf b/macros/latex/contrib/tagpdf/ex-AF-file.pdf
index 0a23364e22..7a3510dce2 100644
--- a/macros/latex/contrib/tagpdf/ex-AF-file.pdf
+++ b/macros/latex/contrib/tagpdf/ex-AF-file.pdf
@@ -1,11 +1,11 @@
%PDF-2.0
%ĢÕĮŌÅŲŠÄĘ
23 0 obj
-<< /Subtype /application#2Fx-tex/Type /EmbeddedFile /Params<</ModDate (D:20231118102457+01'00') /Size 151 /CheckSum (75055DA17B75996F290B2BB310067A84) >> /Length 151 >>
+<< /Subtype /application#2Fx-tex/Type /EmbeddedFile /Params<</ModDate (D:20231119133347Z) /Size 151 /CheckSum (45E3979306E2D6608CA47CED1BB11C85) >> /Length 151 >>
stream
%% LaTeX2e file `example-input-file.tex'
%% generated by the `filecontents' environment
-%% from source `ex-AF-file' on 2023/11/18.
+%% from source `ex-AF-file' on 2023/11/19.
%%
Additional info!
@@ -15,7 +15,7 @@ endobj
<< /Type /Filespec /AFRelationship /Unspecified /F <FEFF006500780061006D0070006C0065002D0069006E007000750074002D00660069006C0065002E007400650078> /UF <FEFF006500780061006D0070006C0065002D0069006E007000750074002D00660069006C0065002E007400650078> /EF<</F 23 0 R/UF 23 0 R>> >>
endobj
26 0 obj
-<< /Subtype /text#2Fplain/Type /EmbeddedFile /Params<</ModDate (D:20231118) >> /Length 19 >>
+<< /Subtype /text#2Fplain/Type /EmbeddedFile /Params<</ModDate (D:20231119) >> /Length 19 >>
stream
BƤr with teh shirt
endstream
@@ -24,7 +24,7 @@ endobj
<< /Type /Filespec /AFRelationship /Supplement /F <FEFF007400610067002D0041004600660069006C00650031002E007400780074> /UF <FEFF007400610067002D0041004600660069006C00650031002E007400780074> /EF<</F 26 0 R/UF 26 0 R>> >>
endobj
29 0 obj
-<< /Subtype /text#2Fplain/Type /EmbeddedFile /Params<</ModDate (D:20231118) >> /Length 4 >>
+<< /Subtype /text#2Fplain/Type /EmbeddedFile /Params<</ModDate (D:20231119) >> /Length 4 >>
stream
Duck
endstream
@@ -33,7 +33,7 @@ endobj
<< /Type /Filespec /AFRelationship /Supplement /F <FEFF007400610067002D0041004600660069006C00650032002E007400780074> /UF <FEFF007400610067002D0041004600660069006C00650032002E007400780074> /EF<</F 29 0 R/UF 29 0 R>> >>
endobj
32 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11382 >>
+<< /Type /Metadata /Subtype /XML /Length 11362 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -242,17 +242,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:25:12+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:34:46Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-AF-file.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:25:12+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:25:12+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:25:12+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:34:46Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:34:46Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:34:46Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:38d5a844-2217-4081-87cc-b2129dc357a6</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:6226cf57-f7d6-4d14-8031-6bb55b06ef0a</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:093e8ef6-098e-4201-8f10-5dbf8a2fe8b2</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>1</prism:pageCount>
</rdf:Description>
@@ -350,7 +350,7 @@ endobj
<< /Type /Namespace /NS (https://www.latex-project.org/ns/inline/2022) /RoleMapNS 19 0 R >>
endobj
20 0 obj
-<< /Type /Namespace /NS (data:,227BA38F-DA17-3158-71DD-E8AF0A331658) >>
+<< /Type /Namespace /NS (data:,D85A321F-C9AB-5DDD-AE5F-6AFFFA790903) >>
endobj
7 0 obj
[ 8 0 R 10 0 R 12 0 R 14 0 R 16 0 R 18 0 R 20 0 R ]
@@ -452,60 +452,60 @@ endobj
<< /Type /Catalog /Pages 37 0 R /MarkInfo 38 0 R/Lang (de-DE)/Metadata 32 0 R/StructTreeRoot 5 0 R >>
endobj
47 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231118102512+01'00')/ModDate (D:20231118102512+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231119133446Z)/ModDate (D:20231119133446Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 48
0000000002 65535 f
-0000013712 00000 n
+0000013686 00000 n
0000000003 00000 f
0000000004 00000 f
0000000009 00000 f
-0000016268 00000 n
-0000013795 00000 n
-0000015691 00000 n
-0000014006 00000 n
+0000016242 00000 n
+0000013769 00000 n
+0000015665 00000 n
+0000013980 00000 n
0000000011 00000 f
-0000014074 00000 n
+0000014048 00000 n
0000000013 00000 f
-0000014144 00000 n
+0000014118 00000 n
0000000021 00000 f
-0000014907 00000 n
-0000014225 00000 n
-0000015185 00000 n
-0000015014 00000 n
-0000015493 00000 n
-0000015292 00000 n
-0000015602 00000 n
+0000014881 00000 n
+0000014199 00000 n
+0000015159 00000 n
+0000014988 00000 n
+0000015467 00000 n
+0000015266 00000 n
+0000015576 00000 n
0000000000 00000 f
-0000015759 00000 n
+0000015733 00000 n
0000000020 00000 n
-0000000382 00000 n
-0000015872 00000 n
-0000000673 00000 n
-0000000828 00000 n
-0000016004 00000 n
-0000001062 00000 n
-0000001202 00000 n
-0000016136 00000 n
-0000001436 00000 n
-0000013649 00000 n
-0000013514 00000 n
-0000012908 00000 n
-0000020006 00000 n
-0000020360 00000 n
-0000013759 00000 n
-0000013852 00000 n
-0000013969 00000 n
-0000016373 00000 n
-0000018822 00000 n
-0000016559 00000 n
-0000019043 00000 n
-0000020160 00000 n
-0000020422 00000 n
-0000020540 00000 n
+0000000376 00000 n
+0000015846 00000 n
+0000000667 00000 n
+0000000822 00000 n
+0000015978 00000 n
+0000001056 00000 n
+0000001196 00000 n
+0000016110 00000 n
+0000001430 00000 n
+0000013623 00000 n
+0000013488 00000 n
+0000012882 00000 n
+0000019980 00000 n
+0000020334 00000 n
+0000013733 00000 n
+0000013826 00000 n
+0000013943 00000 n
+0000016347 00000 n
+0000018796 00000 n
+0000016533 00000 n
+0000019017 00000 n
+0000020134 00000 n
+0000020396 00000 n
+0000020514 00000 n
trailer
-<< /Size 48 /Root 46 0 R /Info 47 0 R /ID [ <1B455F20A800F11F790A1B24D5E6CC15> <1B455F20A800F11F790A1B24D5E6CC15> ] >>
+<< /Size 48 /Root 46 0 R /Info 47 0 R /ID [ <3C4C2E49156D77AD5FF589962A81127A> <3C4C2E49156D77AD5FF589962A81127A> ] >>
startxref
-20763
+20725
%%EOF
diff --git a/macros/latex/contrib/tagpdf/ex-alt-actualtext.pdf b/macros/latex/contrib/tagpdf/ex-alt-actualtext.pdf
index d6161d6060..6989f675ac 100644
--- a/macros/latex/contrib/tagpdf/ex-alt-actualtext.pdf
+++ b/macros/latex/contrib/tagpdf/ex-alt-actualtext.pdf
Binary files differ
diff --git a/macros/latex/contrib/tagpdf/ex-attribute.pdf b/macros/latex/contrib/tagpdf/ex-attribute.pdf
index 0c20b33f6c..5e4f359b39 100644
--- a/macros/latex/contrib/tagpdf/ex-attribute.pdf
+++ b/macros/latex/contrib/tagpdf/ex-attribute.pdf
@@ -7,7 +7,7 @@ endobj
<< <</O /Layout /Borderstyle /Dotted >> >>
endobj
21 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11384 >>
+<< /Type /Metadata /Subtype /XML /Length 11364 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -216,17 +216,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:25:54+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:37:28Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-attribute.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:25:54+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:25:54+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:25:54+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:37:28Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:37:28Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:37:28Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:7a9cf910-1c19-429a-8f24-339c62d8a57f</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:96f4cc40-9bfa-4460-84a7-43bde95afbca</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:f082e4cc-de88-4d9c-84ff-78390061b22e</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>1</prism:pageCount>
</rdf:Description>
@@ -449,51 +449,51 @@ endobj
<< /Type /Catalog /Pages 26 0 R /MarkInfo 27 0 R/Lang (de_DE)/Metadata 21 0 R/StructTreeRoot 5 0 R >>
endobj
38 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/Title (Title)/CreationDate (D:20231118102554+01'00')/ModDate (D:20231118102554+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/Title (Title)/CreationDate (D:20231119133728Z)/ModDate (D:20231119133728Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 39
0000000002 65535 f
-0000012845 00000 n
+0000012825 00000 n
0000000003 00000 f
0000000004 00000 f
0000000008 00000 f
-0000014964 00000 n
-0000012928 00000 n
-0000013247 00000 n
+0000014944 00000 n
+0000012908 00000 n
+0000013227 00000 n
0000000000 00000 f
-0000013952 00000 n
-0000014037 00000 n
-0000014129 00000 n
-0000014213 00000 n
-0000014303 00000 n
+0000013932 00000 n
+0000014017 00000 n
+0000014109 00000 n
+0000014193 00000 n
+0000014283 00000 n
0000000020 00000 n
0000000071 00000 n
-0000014432 00000 n
-0000014572 00000 n
-0000014656 00000 n
-0000014746 00000 n
-0000014855 00000 n
+0000014412 00000 n
+0000014552 00000 n
+0000014636 00000 n
+0000014726 00000 n
+0000014835 00000 n
0000000132 00000 n
-0000012758 00000 n
-0000012616 00000 n
-0000011606 00000 n
-0000017304 00000 n
-0000017658 00000 n
-0000012892 00000 n
-0000012992 00000 n
-0000013210 00000 n
-0000013826 00000 n
-0000015082 00000 n
-0000016260 00000 n
-0000015159 00000 n
-0000015233 00000 n
-0000016496 00000 n
-0000017458 00000 n
-0000017720 00000 n
-0000017838 00000 n
+0000012738 00000 n
+0000012596 00000 n
+0000011586 00000 n
+0000017284 00000 n
+0000017638 00000 n
+0000012872 00000 n
+0000012972 00000 n
+0000013190 00000 n
+0000013806 00000 n
+0000015062 00000 n
+0000016240 00000 n
+0000015139 00000 n
+0000015213 00000 n
+0000016476 00000 n
+0000017438 00000 n
+0000017700 00000 n
+0000017818 00000 n
trailer
-<< /Size 39 /Root 37 0 R /Info 38 0 R /ID [ <2E1559CE1A4788646EA32B510E42AB1F> <2E1559CE1A4788646EA32B510E42AB1F> ] >>
+<< /Size 39 /Root 37 0 R /Info 38 0 R /ID [ <75FAFAFFF317C04961B178649521EB4A> <75FAFAFFF317C04961B178649521EB4A> ] >>
startxref
-18075
+18043
%%EOF
diff --git a/macros/latex/contrib/tagpdf/ex-formula-problem.pdf b/macros/latex/contrib/tagpdf/ex-formula-problem.pdf
index 7387044824..b135d8e44f 100644
--- a/macros/latex/contrib/tagpdf/ex-formula-problem.pdf
+++ b/macros/latex/contrib/tagpdf/ex-formula-problem.pdf
@@ -30,7 +30,7 @@ endobj
<< /ExtGState 1 0 R /Font << /F15 15 0 R >> /ProcSet [ /PDF /Text ] >>
endobj
19 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11390 >>
+<< /Type /Metadata /Subtype /XML /Length 11370 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -239,17 +239,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:26:15+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:38:51Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-formula-problem.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:26:15+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:26:15+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:26:15+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:38:51Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:38:51Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:38:51Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:8eb2ce1d-b2ec-440a-8bc2-73733eb3eeb0</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:e4e16a3c-c617-4fb0-8850-a955397a8c93</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:6f499452-8e28-414b-8dc5-c9e0e9473e77</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>2</prism:pageCount>
</rdf:Description>
@@ -425,46 +425,46 @@ endobj
<< /Type /Catalog /Pages 16 0 R /MarkInfo 23 0 R/Lang (de-DE)/Metadata 19 0 R/StructTreeRoot 5 0 R >>
endobj
33 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231118102615+01'00')/ModDate (D:20231118102615+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231119133851Z)/ModDate (D:20231119133851Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 34
0000000002 65535 f
-0000012816 00000 n
+0000012796 00000 n
0000000003 00000 f
0000000004 00000 f
0000000008 00000 f
-0000014379 00000 n
-0000012899 00000 n
-0000013137 00000 n
+0000014359 00000 n
+0000012879 00000 n
+0000013117 00000 n
0000000000 00000 f
-0000013716 00000 n
-0000013823 00000 n
-0000013929 00000 n
+0000013696 00000 n
+0000013803 00000 n
+0000013909 00000 n
0000000637 00000 n
0000000502 00000 n
0000000020 00000 n
-0000018463 00000 n
-0000018817 00000 n
-0000014041 00000 n
-0000014147 00000 n
+0000018443 00000 n
+0000018797 00000 n
+0000014021 00000 n
+0000014127 00000 n
0000000724 00000 n
-0000012729 00000 n
-0000012594 00000 n
-0000012204 00000 n
-0000012863 00000 n
-0000012969 00000 n
-0000013100 00000 n
-0000014480 00000 n
-0000017236 00000 n
-0000014681 00000 n
-0000014757 00000 n
-0000017472 00000 n
-0000018617 00000 n
-0000018886 00000 n
-0000019004 00000 n
+0000012709 00000 n
+0000012574 00000 n
+0000012184 00000 n
+0000012843 00000 n
+0000012949 00000 n
+0000013080 00000 n
+0000014460 00000 n
+0000017216 00000 n
+0000014661 00000 n
+0000014737 00000 n
+0000017452 00000 n
+0000018597 00000 n
+0000018866 00000 n
+0000018984 00000 n
trailer
-<< /Size 34 /Root 32 0 R /Info 33 0 R /ID [ <08F9DB569804A35867852F35B6E4F1DB> <08F9DB569804A35867852F35B6E4F1DB> ] >>
+<< /Size 34 /Root 32 0 R /Info 33 0 R /ID [ <C8449D2A8DF9E8F15C6E4A9A73EF1D4E> <C8449D2A8DF9E8F15C6E4A9A73EF1D4E> ] >>
startxref
-19227
+19195
%%EOF
diff --git a/macros/latex/contrib/tagpdf/ex-list.pdf b/macros/latex/contrib/tagpdf/ex-list.pdf
index dd7c93abf1..fb26522f3b 100644
--- a/macros/latex/contrib/tagpdf/ex-list.pdf
+++ b/macros/latex/contrib/tagpdf/ex-list.pdf
@@ -1,7 +1,7 @@
%PDF-1.7
%ĢÕĮŌÅŲŠÄĘ
48 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11379 >>
+<< /Type /Metadata /Subtype /XML /Length 11359 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -210,17 +210,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:26:38+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:40:08Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-list.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:26:38+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:26:38+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:26:38+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:40:08Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:40:08Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:40:08Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:4c749825-1de7-414c-879f-29e4d0bef66e</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:98a4c726-f369-408b-8dfd-e2574cdeb9f2</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:19435395-436e-4e73-8ea2-775846824f23</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>1</prism:pageCount>
</rdf:Description>
@@ -653,85 +653,85 @@ endobj
<< /Type /Catalog /Pages 54 0 R /MarkInfo 55 0 R/Lang (en-US)/Metadata 48 0 R/StructTreeRoot 5 0 R >>
endobj
72 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231118102638+01'00')/ModDate (D:20231118102638+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231119134008Z)/ModDate (D:20231119134008Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 73
0000000002 65535 f
-0000013512 00000 n
+0000013492 00000 n
0000000003 00000 f
0000000004 00000 f
0000000008 00000 f
-0000019049 00000 n
-0000013595 00000 n
-0000014434 00000 n
+0000019029 00000 n
+0000013575 00000 n
+0000014414 00000 n
0000000000 00000 f
-0000015230 00000 n
-0000015331 00000 n
-0000015407 00000 n
-0000015483 00000 n
-0000015570 00000 n
-0000015677 00000 n
-0000015767 00000 n
-0000015877 00000 n
-0000015961 00000 n
-0000016049 00000 n
-0000016172 00000 n
-0000016262 00000 n
-0000016372 00000 n
-0000016456 00000 n
-0000016544 00000 n
-0000016667 00000 n
-0000016754 00000 n
-0000016865 00000 n
-0000016955 00000 n
-0000017065 00000 n
-0000017149 00000 n
-0000017237 00000 n
-0000017360 00000 n
-0000017450 00000 n
-0000017560 00000 n
-0000017644 00000 n
-0000017732 00000 n
-0000017855 00000 n
-0000017942 00000 n
-0000018057 00000 n
-0000018147 00000 n
-0000018257 00000 n
-0000018341 00000 n
-0000018429 00000 n
-0000018552 00000 n
-0000018642 00000 n
-0000018753 00000 n
-0000018837 00000 n
-0000018925 00000 n
+0000015210 00000 n
+0000015311 00000 n
+0000015387 00000 n
+0000015463 00000 n
+0000015550 00000 n
+0000015657 00000 n
+0000015747 00000 n
+0000015857 00000 n
+0000015941 00000 n
+0000016029 00000 n
+0000016152 00000 n
+0000016242 00000 n
+0000016352 00000 n
+0000016436 00000 n
+0000016524 00000 n
+0000016647 00000 n
+0000016734 00000 n
+0000016845 00000 n
+0000016935 00000 n
+0000017045 00000 n
+0000017129 00000 n
+0000017217 00000 n
+0000017340 00000 n
+0000017430 00000 n
+0000017540 00000 n
+0000017624 00000 n
+0000017712 00000 n
+0000017835 00000 n
+0000017922 00000 n
+0000018037 00000 n
+0000018127 00000 n
+0000018237 00000 n
+0000018321 00000 n
+0000018409 00000 n
+0000018532 00000 n
+0000018622 00000 n
+0000018733 00000 n
+0000018817 00000 n
+0000018905 00000 n
0000000020 00000 n
-0000013413 00000 n
-0000013271 00000 n
-0000011489 00000 n
-0000029176 00000 n
-0000022224 00000 n
-0000029530 00000 n
-0000013559 00000 n
-0000013715 00000 n
-0000014397 00000 n
-0000015026 00000 n
-0000019167 00000 n
-0000021126 00000 n
-0000019299 00000 n
-0000019373 00000 n
-0000021360 00000 n
-0000022375 00000 n
-0000022572 00000 n
-0000027711 00000 n
-0000022908 00000 n
-0000023031 00000 n
-0000027947 00000 n
-0000029330 00000 n
-0000029592 00000 n
-0000029710 00000 n
+0000013393 00000 n
+0000013251 00000 n
+0000011469 00000 n
+0000029156 00000 n
+0000022204 00000 n
+0000029510 00000 n
+0000013539 00000 n
+0000013695 00000 n
+0000014377 00000 n
+0000015006 00000 n
+0000019147 00000 n
+0000021106 00000 n
+0000019279 00000 n
+0000019353 00000 n
+0000021340 00000 n
+0000022355 00000 n
+0000022552 00000 n
+0000027691 00000 n
+0000022888 00000 n
+0000023011 00000 n
+0000027927 00000 n
+0000029310 00000 n
+0000029572 00000 n
+0000029690 00000 n
trailer
-<< /Size 73 /Root 71 0 R /Info 72 0 R /ID [ <47FD9894AF86ED0B47FDCBD52537905C> <47FD9894AF86ED0B47FDCBD52537905C> ] >>
+<< /Size 73 /Root 71 0 R /Info 72 0 R /ID [ <F1BDDA4E8C7F976DD737665B4BE7A55C> <F1BDDA4E8C7F976DD737665B4BE7A55C> ] >>
startxref
-29933
+29901
%%EOF
diff --git a/macros/latex/contrib/tagpdf/ex-mc-manual-para-split-obsolete.pdf b/macros/latex/contrib/tagpdf/ex-mc-manual-para-split-obsolete.pdf
index 6127da53ad..22cba55cba 100644
--- a/macros/latex/contrib/tagpdf/ex-mc-manual-para-split-obsolete.pdf
+++ b/macros/latex/contrib/tagpdf/ex-mc-manual-para-split-obsolete.pdf
@@ -34,7 +34,7 @@ endobj
<< /ExtGState 1 0 R /Font << /F15 13 0 R >> /ProcSet [ /PDF /Text ] >>
endobj
15 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11404 >>
+<< /Type /Metadata /Subtype /XML /Length 11384 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -243,17 +243,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:26:57+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:41:18Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-mc-manual-para-split-obsolete.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:26:57+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:26:57+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:26:57+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:41:18Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:41:18Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:41:18Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:c33d64b4-96ec-4e48-8f27-0b3edc831547</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:bf18d3e4-e954-4360-8578-d842d8baf104</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:2f590883-d839-4051-8d17-22e16f4ed267</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>2</prism:pageCount>
</rdf:Description>
@@ -413,12 +413,12 @@ endobj
<< /Type /Catalog /Pages 14 0 R /Lang (en-US)/Metadata 15 0 R >>
endobj
25 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231118102657+01'00')/ModDate (D:20231118102657+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231119134118Z)/ModDate (D:20231119134118Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 26
0000000002 65535 f
-0000016854 00000 n
+0000016834 00000 n
0000000003 00000 f
0000000004 00000 f
0000000005 00000 f
@@ -427,24 +427,24 @@ xref
0000000008 00000 f
0000000000 00000 f
0000002976 00000 n
-0000016648 00000 n
+0000016628 00000 n
0000003094 00000 n
0000000020 00000 n
-0000023475 00000 n
-0000023829 00000 n
+0000023455 00000 n
+0000023809 00000 n
0000003181 00000 n
-0000016767 00000 n
-0000014675 00000 n
-0000016901 00000 n
-0000022024 00000 n
-0000017208 00000 n
-0000017283 00000 n
-0000022260 00000 n
-0000023629 00000 n
-0000023897 00000 n
-0000023978 00000 n
+0000016747 00000 n
+0000014655 00000 n
+0000016881 00000 n
+0000022004 00000 n
+0000017188 00000 n
+0000017263 00000 n
+0000022240 00000 n
+0000023609 00000 n
+0000023877 00000 n
+0000023958 00000 n
trailer
-<< /Size 26 /Root 24 0 R /Info 25 0 R /ID [ <F21B3032E6485F236901364889B0F4CB> <F21B3032E6485F236901364889B0F4CB> ] >>
+<< /Size 26 /Root 24 0 R /Info 25 0 R /ID [ <DA491642949C7CF65190DA24A01CA523> <DA491642949C7CF65190DA24A01CA523> ] >>
startxref
-24201
+24169
%%EOF
diff --git a/macros/latex/contrib/tagpdf/ex-softhyphen.pdf b/macros/latex/contrib/tagpdf/ex-softhyphen.pdf
index 2fc23aac31..0e83e98465 100644
--- a/macros/latex/contrib/tagpdf/ex-softhyphen.pdf
+++ b/macros/latex/contrib/tagpdf/ex-softhyphen.pdf
@@ -1,7 +1,7 @@
%PDF-1.7
%ĢÕĮŌÅŲŠÄĘ
14 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11385 >>
+<< /Type /Metadata /Subtype /XML /Length 11365 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -210,17 +210,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:27:16+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:42:28Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-softhyphen.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:27:16+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:27:16+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:27:16+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:42:28Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:42:28Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:42:28Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:aa82e685-4098-469d-861c-3c45dfc700c7</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:a27dc837-bdd5-4721-8673-990033345cee</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:85ed99f7-c19c-476d-812a-bd2591f00049</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>1</prism:pageCount>
</rdf:Description>
@@ -393,43 +393,43 @@ endobj
<< /Type /Catalog /Pages 19 0 R /MarkInfo 20 0 R/Lang (en-US)/Metadata 14 0 R/StructTreeRoot 5 0 R >>
endobj
30 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231118102716+01'00')/ModDate (D:20231118102716+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231119134228Z)/ModDate (D:20231119134228Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 31
0000000002 65535 f
-0000012363 00000 n
+0000012343 00000 n
0000000003 00000 f
0000000004 00000 f
0000000008 00000 f
-0000013741 00000 n
-0000012446 00000 n
-0000012664 00000 n
+0000013721 00000 n
+0000012426 00000 n
+0000012644 00000 n
0000000000 00000 f
-0000013256 00000 n
-0000013349 00000 n
-0000013435 00000 n
-0000013545 00000 n
-0000013631 00000 n
+0000013236 00000 n
+0000013329 00000 n
+0000013415 00000 n
+0000013525 00000 n
+0000013611 00000 n
0000000020 00000 n
-0000012276 00000 n
-0000012141 00000 n
-0000011495 00000 n
-0000017690 00000 n
-0000018054 00000 n
-0000012410 00000 n
-0000012496 00000 n
-0000012627 00000 n
-0000013842 00000 n
-0000016490 00000 n
-0000013996 00000 n
-0000014170 00000 n
-0000016730 00000 n
-0000017849 00000 n
-0000018116 00000 n
-0000018234 00000 n
+0000012256 00000 n
+0000012121 00000 n
+0000011475 00000 n
+0000017670 00000 n
+0000018034 00000 n
+0000012390 00000 n
+0000012476 00000 n
+0000012607 00000 n
+0000013822 00000 n
+0000016470 00000 n
+0000013976 00000 n
+0000014150 00000 n
+0000016710 00000 n
+0000017829 00000 n
+0000018096 00000 n
+0000018214 00000 n
trailer
-<< /Size 31 /Root 29 0 R /Info 30 0 R /ID [ <248591E017E3308CA6FE6136963724C1> <248591E017E3308CA6FE6136963724C1> ] >>
+<< /Size 31 /Root 29 0 R /Info 30 0 R /ID [ <D3BABA5B4BFA89297AB18B331256197C> <D3BABA5B4BFA89297AB18B331256197C> ] >>
startxref
-18457
+18425
%%EOF
diff --git a/macros/latex/contrib/tagpdf/ex-spaceglyph-listings.pdf b/macros/latex/contrib/tagpdf/ex-spaceglyph-listings.pdf
index a72bc48688..2f48f2d9c9 100644
--- a/macros/latex/contrib/tagpdf/ex-spaceglyph-listings.pdf
+++ b/macros/latex/contrib/tagpdf/ex-spaceglyph-listings.pdf
@@ -1,7 +1,7 @@
%PDF-1.5
%ĢÕĮŌÅŲŠÄĘ
10 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11394 >>
+<< /Type /Metadata /Subtype /XML /Length 11374 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -210,17 +210,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:27:34+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:43:31Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-spaceglyph-listings.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:27:34+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:27:34+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:27:34+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:43:31Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:43:31Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:43:31Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:acdc2435-bf29-4e54-8d09-1c9b6dc32038</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:268bb461-46b6-42b8-8a2e-164a0163e29d</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:8582b1db-9189-4c8e-8ae1-f5cb4bfcb2e8</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>1</prism:pageCount>
</rdf:Description>
@@ -354,39 +354,39 @@ endobj
<< /Type /Catalog /Pages 15 0 R /MarkInfo 16 0 R/Lang (en-US)/Metadata 10 0 R/StructTreeRoot 5 0 R >>
endobj
26 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231118102734+01'00')/ModDate (D:20231118102734+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231119134331Z)/ModDate (D:20231119134331Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 27
0000000002 65535 f
-0000012010 00000 n
+0000011990 00000 n
0000000003 00000 f
0000000004 00000 f
0000000008 00000 f
-0000012885 00000 n
-0000012093 00000 n
-0000012232 00000 n
+0000012865 00000 n
+0000012073 00000 n
+0000012212 00000 n
0000000000 00000 f
-0000012811 00000 n
+0000012791 00000 n
0000000020 00000 n
-0000011923 00000 n
-0000011788 00000 n
-0000011504 00000 n
-0000015068 00000 n
-0000015422 00000 n
-0000012057 00000 n
-0000012124 00000 n
-0000012195 00000 n
-0000012986 00000 n
-0000014052 00000 n
-0000013041 00000 n
-0000013116 00000 n
-0000014288 00000 n
-0000015222 00000 n
-0000015484 00000 n
-0000015602 00000 n
+0000011903 00000 n
+0000011768 00000 n
+0000011484 00000 n
+0000015048 00000 n
+0000015402 00000 n
+0000012037 00000 n
+0000012104 00000 n
+0000012175 00000 n
+0000012966 00000 n
+0000014032 00000 n
+0000013021 00000 n
+0000013096 00000 n
+0000014268 00000 n
+0000015202 00000 n
+0000015464 00000 n
+0000015582 00000 n
trailer
-<< /Size 27 /Root 25 0 R /Info 26 0 R /ID [ <11DC8607645D63824703EB8FBB080D53> <11DC8607645D63824703EB8FBB080D53> ] >>
+<< /Size 27 /Root 25 0 R /Info 26 0 R /ID [ <535CC97264842307626DA15720B24663> <535CC97264842307626DA15720B24663> ] >>
startxref
-15825
+15793
%%EOF
diff --git a/macros/latex/contrib/tagpdf/ex-structure-obsolete.pdf b/macros/latex/contrib/tagpdf/ex-structure-obsolete.pdf
index 684b9e6e25..8df7f2b594 100644
--- a/macros/latex/contrib/tagpdf/ex-structure-obsolete.pdf
+++ b/macros/latex/contrib/tagpdf/ex-structure-obsolete.pdf
@@ -1,7 +1,7 @@
%PDF-1.7
%ĢÕĮŌÅŲŠÄĘ
20 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11393 >>
+<< /Type /Metadata /Subtype /XML /Length 11373 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -210,17 +210,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:27:52+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:44:38Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-structure-obsolete.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:27:52+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:27:52+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:27:52+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:44:38Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:44:38Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:44:38Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:bf5e4a2b-cfa9-4fc5-878c-8f9d2ee95445</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:985c35d3-f65d-446f-8866-76eb02dca137</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:abdf394d-d275-41e8-891c-758451157aaf</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>1</prism:pageCount>
</rdf:Description>
@@ -526,56 +526,56 @@ endobj
<< /Type /Catalog /Pages 26 0 R /MarkInfo 27 0 R/Lang (en-US)/Metadata 20 0 R/StructTreeRoot 5 0 R >>
endobj
43 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231118102752+01'00')/ModDate (D:20231118102752+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231119134438Z)/ModDate (D:20231119134438Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 44
0000000002 65535 f
-0000012797 00000 n
+0000012777 00000 n
0000000003 00000 f
0000000004 00000 f
0000000008 00000 f
-0000014933 00000 n
-0000012880 00000 n
-0000013229 00000 n
+0000014913 00000 n
+0000012860 00000 n
+0000013209 00000 n
0000000000 00000 f
-0000013821 00000 n
-0000013906 00000 n
-0000014004 00000 n
-0000014112 00000 n
-0000014220 00000 n
-0000014309 00000 n
-0000014399 00000 n
-0000014509 00000 n
-0000014621 00000 n
-0000014711 00000 n
-0000014821 00000 n
+0000013801 00000 n
+0000013886 00000 n
+0000013984 00000 n
+0000014092 00000 n
+0000014200 00000 n
+0000014289 00000 n
+0000014379 00000 n
+0000014489 00000 n
+0000014601 00000 n
+0000014691 00000 n
+0000014801 00000 n
0000000020 00000 n
-0000012698 00000 n
-0000012563 00000 n
-0000011503 00000 n
-0000023016 00000 n
-0000019782 00000 n
-0000023364 00000 n
-0000012844 00000 n
-0000012958 00000 n
-0000013192 00000 n
-0000015034 00000 n
-0000018513 00000 n
-0000015283 00000 n
-0000015358 00000 n
-0000018749 00000 n
-0000019936 00000 n
-0000020136 00000 n
-0000021904 00000 n
-0000020273 00000 n
-0000020349 00000 n
-0000022138 00000 n
-0000023167 00000 n
-0000023426 00000 n
-0000023544 00000 n
+0000012678 00000 n
+0000012543 00000 n
+0000011483 00000 n
+0000022996 00000 n
+0000019762 00000 n
+0000023344 00000 n
+0000012824 00000 n
+0000012938 00000 n
+0000013172 00000 n
+0000015014 00000 n
+0000018493 00000 n
+0000015263 00000 n
+0000015338 00000 n
+0000018729 00000 n
+0000019916 00000 n
+0000020116 00000 n
+0000021884 00000 n
+0000020253 00000 n
+0000020329 00000 n
+0000022118 00000 n
+0000023147 00000 n
+0000023406 00000 n
+0000023524 00000 n
trailer
-<< /Size 44 /Root 42 0 R /Info 43 0 R /ID [ <CD162660C7B5DBC963DE658C99B3EB8E> <CD162660C7B5DBC963DE658C99B3EB8E> ] >>
+<< /Size 44 /Root 42 0 R /Info 43 0 R /ID [ <B5110F0AAF2E81EBF9F9713BBB5D01A2> <B5110F0AAF2E81EBF9F9713BBB5D01A2> ] >>
startxref
-23767
+23735
%%EOF
diff --git a/macros/latex/contrib/tagpdf/ex-tagpdf-template.pdf b/macros/latex/contrib/tagpdf/ex-tagpdf-template.pdf
index 4132331078..49a61608f7 100644
--- a/macros/latex/contrib/tagpdf/ex-tagpdf-template.pdf
+++ b/macros/latex/contrib/tagpdf/ex-tagpdf-template.pdf
@@ -1,7 +1,7 @@
%PDF-2.0
%ĢÕĮŌÅŲŠÄĘ
27 0 obj
-<< /Type /Metadata /Subtype /XML /Length 11390 >>
+<< /Type /Metadata /Subtype /XML /Length 11370 >>
stream
<?xpacket begin="ļ»æ" id="W5M0MpCehiHzreSzNTczkc9d"?>
@@ -210,17 +210,17 @@ stream
</dc:language>
<dc:date>
<rdf:Seq>
- <rdf:li>2023-11-18T10:28:13+01:00</rdf:li>
+ <rdf:li>2023-11-19T13:45:45Z</rdf:li>
</rdf:Seq>
</dc:date>
<dc:format>application/pdf</dc:format>
<dc:source>ex-tagpdf-template.tex</dc:source>
<xmp:CreatorTool>LaTeX</xmp:CreatorTool>
- <xmp:CreateDate>2023-11-18T10:28:13+01:00</xmp:CreateDate>
- <xmp:ModifyDate>2023-11-18T10:28:13+01:00</xmp:ModifyDate>
- <xmp:MetadataDate>2023-11-18T10:28:13+01:00</xmp:MetadataDate>
+ <xmp:CreateDate>2023-11-19T13:45:45Z</xmp:CreateDate>
+ <xmp:ModifyDate>2023-11-19T13:45:45Z</xmp:ModifyDate>
+ <xmp:MetadataDate>2023-11-19T13:45:45Z</xmp:MetadataDate>
<xmpMM:DocumentID>uuid:f320abfc-f6ab-4d12-8719-d176f4d947cf</xmpMM:DocumentID>
- <xmpMM:InstanceID>uuid:c66e9f64-1d51-4aed-88b9-1ba692096422</xmpMM:InstanceID>
+ <xmpMM:InstanceID>uuid:554307d8-161f-4125-8cf2-e74ed08aeef3</xmpMM:InstanceID>
<prism:complianceProfile>three</prism:complianceProfile>
<prism:pageCount>1</prism:pageCount>
</rdf:Description>
@@ -309,7 +309,7 @@ endobj
<< /Type /Namespace /NS (https://www.latex-project.org/ns/inline/2022) /RoleMapNS 19 0 R >>
endobj
20 0 obj
-<< /Type /Namespace /NS (data:,BB9EB9D0-CF0-4B6E-1119-6F03DB993EFE) >>
+<< /Type /Namespace /NS (data:,28278A81-B193-36BC-AB45-5B2A3A37DCBF) >>
endobj
7 0 obj
[ 8 0 R 10 0 R 12 0 R 14 0 R 16 0 R 18 0 R 20 0 R ]
@@ -401,56 +401,56 @@ endobj
<< /Type /Catalog /Pages 32 0 R /MarkInfo 33 0 R/Lang (en-US)/Metadata 27 0 R/StructTreeRoot 5 0 R >>
endobj
43 0 obj
-<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231118102813+01'00')/ModDate (D:20231118102813+01'00') /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
+<< /Producer (luahbtex-1.17.0)/Creator (LaTeX)/CreationDate (D:20231119134545Z)/ModDate (D:20231119134545Z) /Trapped /False /PTEX.FullBanner (This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)) >>
endobj
xref
0 44
0000000002 65535 f
-0000011932 00000 n
+0000011912 00000 n
0000000003 00000 f
0000000004 00000 f
0000000009 00000 f
-0000014544 00000 n
-0000012015 00000 n
-0000013972 00000 n
-0000012288 00000 n
+0000014525 00000 n
+0000011995 00000 n
+0000013953 00000 n
+0000012268 00000 n
0000000011 00000 f
-0000012356 00000 n
+0000012336 00000 n
0000000013 00000 f
-0000012426 00000 n
+0000012406 00000 n
0000000021 00000 f
-0000013189 00000 n
-0000012507 00000 n
-0000013467 00000 n
-0000013296 00000 n
-0000013775 00000 n
-0000013574 00000 n
-0000013884 00000 n
+0000013169 00000 n
+0000012487 00000 n
+0000013447 00000 n
+0000013276 00000 n
+0000013755 00000 n
+0000013554 00000 n
+0000013864 00000 n
0000000000 00000 f
-0000014040 00000 n
-0000014137 00000 n
-0000014224 00000 n
-0000014311 00000 n
-0000014410 00000 n
+0000014021 00000 n
+0000014118 00000 n
+0000014205 00000 n
+0000014292 00000 n
+0000014391 00000 n
0000000020 00000 n
-0000011869 00000 n
-0000011734 00000 n
-0000011500 00000 n
-0000017150 00000 n
-0000017504 00000 n
-0000011979 00000 n
-0000012056 00000 n
-0000012188 00000 n
-0000012225 00000 n
-0000014666 00000 n
-0000016107 00000 n
-0000014753 00000 n
-0000016328 00000 n
-0000017304 00000 n
-0000017566 00000 n
-0000017684 00000 n
+0000011849 00000 n
+0000011714 00000 n
+0000011480 00000 n
+0000017131 00000 n
+0000017485 00000 n
+0000011959 00000 n
+0000012036 00000 n
+0000012168 00000 n
+0000012205 00000 n
+0000014647 00000 n
+0000016088 00000 n
+0000014734 00000 n
+0000016309 00000 n
+0000017285 00000 n
+0000017547 00000 n
+0000017665 00000 n
trailer
-<< /Size 44 /Root 42 0 R /Info 43 0 R /ID [ <4AEDDBD711E0DB4C3594C354006BEAFD> <4AEDDBD711E0DB4C3594C354006BEAFD> ] >>
+<< /Size 44 /Root 42 0 R /Info 43 0 R /ID [ <AF44F9C7C6A6589FC30798F138DF5EB8> <AF44F9C7C6A6589FC30798F138DF5EB8> ] >>
startxref
-17907
+17876
%%EOF
diff --git a/macros/latex/contrib/tagpdf/tagpdf-backend.dtx b/macros/latex/contrib/tagpdf/tagpdf-backend.dtx
index b189742c5d..d02333ad24 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-backend.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-backend.dtx
@@ -47,13 +47,13 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{implementation}
% \begin{macrocode}
%<@@=tag>
%<*luatex>
-\ProvidesExplFile {tagpdf-luatex.def} {2023-11-17} {0.98p}
+\ProvidesExplFile {tagpdf-luatex.def} {2023-11-19} {0.98q}
{tagpdf~driver~for~luatex}
% \end{macrocode}
% \section{Loading the lua}
@@ -158,8 +158,8 @@
local ProvidesLuaModule = {
name = "tagpdf",
- version = "0.98p", --TAGVERSION
- date = "2023-11-17", --TAGDATE
+ version = "0.98q", --TAGVERSION
+ date = "2023-11-19", --TAGDATE
description = "tagpdf lua code",
license = "The LATEX Project Public License 1.3c"
}
diff --git a/macros/latex/contrib/tagpdf/tagpdf-checks.dtx b/macros/latex/contrib/tagpdf/tagpdf-checks.dtx
index 8a281250df..9b4de607d4 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-checks.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-checks.dtx
@@ -48,7 +48,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{documentation}
% \section{Commands}
@@ -313,7 +313,7 @@
% \begin{macrocode}
%<@@=tag>
%<*header>
-\ProvidesExplPackage {tagpdf-checks-code} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-checks-code} {2023-11-19} {0.98q}
{part of tagpdf - code related to checks, conditionals, debugging and messages}
%</header>
% \end{macrocode}
diff --git a/macros/latex/contrib/tagpdf/tagpdf-code.pdf b/macros/latex/contrib/tagpdf/tagpdf-code.pdf
index acf2d1db01..04c8e495d1 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-code.pdf
+++ b/macros/latex/contrib/tagpdf/tagpdf-code.pdf
Binary files differ
diff --git a/macros/latex/contrib/tagpdf/tagpdf-data.dtx b/macros/latex/contrib/tagpdf/tagpdf-data.dtx
index b866058c83..6803d0c280 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-data.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-data.dtx
@@ -47,7 +47,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{documentation}
% This files contains a various data files which are read in
@@ -60,7 +60,7 @@
% It lists the new tag, the rolemap and the namespace of the rolemap.
% \begin{macrocode}
%<*ns-latex>
-%% \ProvidesExplFile {tagpdf-ns-latex.def} {2023-11-17} {0.98p}
+%% \ProvidesExplFile {tagpdf-ns-latex.def} {2023-11-19} {0.98q}
%% {latex} {https://www.latex-project.org/ns/dflt/2022}{}
title, Title, pdf2,
part, Title, pdf2,
@@ -92,7 +92,7 @@ text, P, pdf2,
% It is bound to change
% \begin{macrocode}
%<*ns-latex-book>
-%% \ProvidesExplFile {tagpdf-ns-latex-book.def} {2023-11-17} {0.98p}
+%% \ProvidesExplFile {tagpdf-ns-latex-book.def} {2023-11-19} {0.98q}
%% {latex-book} {https://www.latex-project.org/ns/book/2022}{}
chapter, H1,pdf2,
section, H2,pdf2,
@@ -108,7 +108,7 @@ subparagraph, H6,pdf2,
% loaded.
% \begin{macrocode}
%<*ns-latex-inline>
-%% \ProvidesExplFile {tagpdf-ns-latex-inline.def} {2023-11-17} {0.98p}
+%% \ProvidesExplFile {tagpdf-ns-latex-inline.def} {2023-11-19} {0.98q}
%% {latex-inline} {https://www.latex-project.org/ns/inline/2022}{}
chapter, Span, pdf2,
section, Span, pdf2,
@@ -122,7 +122,7 @@ P, Span, pdf2,
% \section{The pdf namespace data}
% \begin{macrocode}
%<*ns-pdf>
-%% \ProvidesExplFile {tagpdf-ns-pdf.def} {2023-11-17} {0.98p}
+%% \ProvidesExplFile {tagpdf-ns-pdf.def} {2023-11-19} {0.98q}
%% {pdf} {http://iso.org/pdf/ssn}{}
StructTreeRoot,StructTreeRoot,pdf,D,
Document,Document,pdf,D,
@@ -190,7 +190,7 @@ Strong,Span,pdf,I,
% \section{The pdf 2.0 namespace data}
% \begin{macrocode}
%<*ns-pdf2>
-%% \ProvidesExplFile {tagpdf-ns-pdf2.def} {2023-11-17} {0.98p}
+%% \ProvidesExplFile {tagpdf-ns-pdf2.def} {2023-11-19} {0.98q}
%% {pdf2} {http://iso.org/pdf2/ssn}{}
Document,Document,pdf2,D,
Part,Part,pdf2,G,
@@ -246,7 +246,7 @@ Strong,Strong,pdf2,I,
% \section{The mathml namespace data}
% \begin{macrocode}
%<*ns-mathml>
-%% \ProvidesExplFile {tagpdf-ns-mathml.def} {2023-11-17} {0.98p}
+%% \ProvidesExplFile {tagpdf-ns-mathml.def} {2023-11-19} {0.98q}
% {mathml}{http://www.w3.org/1998/Math/MathML}{}
abs,abs,mathml,
and,and,mathml,
@@ -481,7 +481,7 @@ xor,xor,mathml,
% This will perhaps change in future.
% \begin{macrocode}
%<*parent-child>
-%% \ProvidesExplFile {tagpdf-parent-child.csv} {2023-11-17} {0.98p}
+%% \ProvidesExplFile {tagpdf-parent-child.csv} {2023-11-19} {0.98q}
,,,StructTreeRoot,Document,Art,Part,Div,Sect,BlockQuote,NonStruct,TOC,TOCI,Index,Private,Quote,Note,Reference,BibEntry,P,Hn,H,Lbl,Code,Span,Link,Annot,Form,Ruby,RB,RT,RP,Warichu,WT,WP,L,LI,LBody,Table,TR,TH,TD,THead,TBody,TFoot,Caption,Figure,Formula,MC
Document,both,document level,1,0..n,āˆ…,ā€”,ā€”,āˆ…,0..n,ā€”,āˆ…,āˆ…,āˆ…,0..n,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…
Art,1.7,grouping,āˆ…,0..n,āˆ…,ā€”,ā€”,0..n,0..n,ā€”,āˆ…,āˆ…,āˆ…,0..n,āˆ…,0..n,āˆ…,āˆ…,āˆ…,0..1,0..1,āˆ…,āˆ…,āˆ…,0..n,0..n,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,0..n,āˆ…,āˆ…,0..n,0..n,āˆ…,āˆ…,āˆ…,0..n,0..n,āˆ…,āˆ…
@@ -536,7 +536,7 @@ MC,both,---,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,0..n,ā€”,āˆ…,āˆ…,āˆ…,0..n,0..n,0..n,0..n,0..
% This will perhaps change in future.
% \begin{macrocode}
%<*parent-child-2>
-%% \ProvidesExplFile {tagpdf-parent-child-2.csv} {2023-11-17} {0.98p}
+%% \ProvidesExplFile {tagpdf-parent-child-2.csv} {2023-11-19} {0.98q}
,,,StructTreeRoot,Document,DocumentFragment,Art,Part,Div,Sect,Aside,BlockQuote,NonStruct,TOC,TOCI,Index,Private,Title,Sub,Quote,Note,Reference,BibEntry,P,Hn,H,Lbl,Code,Em,Strong,Span,Link,Annot,Form,Ruby,RB,RT,RP,Warichu,WT,WP,FENote,L,LI,LBody,Table,TR,TH,TD,THead,TBody,TFoot,Caption,Figure,Formula,math,mathml,Artifact,MC
Document,both,document level,1,0..n,0..n,āˆ…,ā€”,ā€”,āˆ…,0..n,0..n,ā€”,āˆ…,āˆ…,āˆ…,0..n,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,0..n,āˆ…
DocumentFragment,2.0,document level,āˆ…,0..n,0..n,0..n,ā€”,ā€”,0..n,0..n,0..n,ā€”,āˆ…,āˆ…,āˆ…,0..n,āˆ…,āˆ…,āˆ…,āˆ…*,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…*,āˆ…,āˆ…,āˆ…,āˆ…*,āˆ…*,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…*,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…,āˆ…*,āˆ…,āˆ…,āˆ…,āˆ…,0..n,āˆ…
diff --git a/macros/latex/contrib/tagpdf/tagpdf-mc-generic.dtx b/macros/latex/contrib/tagpdf/tagpdf-mc-generic.dtx
index be9830837a..ff030a6c6e 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-mc-generic.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-mc-generic.dtx
@@ -46,7 +46,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{documentation}
% \end{documentation}
@@ -55,11 +55,11 @@
% \begin{macrocode}
%<@@=tag>
%<*generic>
-\ProvidesExplPackage {tagpdf-mc-code-generic} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-mc-code-generic} {2023-11-19} {0.98q}
{part of tagpdf - code related to marking chunks - generic mode}
%</generic>
%<*debug>
-\ProvidesExplPackage {tagpdf-debug-generic} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-debug-generic} {2023-11-19} {0.98q}
{part of tagpdf - debugging code related to marking chunks - generic mode}
%</debug>
% \end{macrocode}
diff --git a/macros/latex/contrib/tagpdf/tagpdf-mc-luacode.dtx b/macros/latex/contrib/tagpdf/tagpdf-mc-luacode.dtx
index 5d4930fcc3..c3454bb45d 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-mc-luacode.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-mc-luacode.dtx
@@ -46,7 +46,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{implementation}
% The code is splitted into three parts: code shared by all engines,
@@ -86,11 +86,11 @@
% \begin{macrocode}
%<@@=tag>
%<*luamode>
-\ProvidesExplPackage {tagpdf-mc-code-lua} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-mc-code-lua} {2023-11-19} {0.98q}
{tagpdf - mc code only for the luamode }
%</luamode>
%<*debug>
-\ProvidesExplPackage {tagpdf-debug-lua} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-debug-lua} {2023-11-19} {0.98q}
{part of tagpdf - debugging code related to marking chunks - lua mode}
%</debug>
% \end{macrocode}
diff --git a/macros/latex/contrib/tagpdf/tagpdf-mc-shared.dtx b/macros/latex/contrib/tagpdf/tagpdf-mc-shared.dtx
index de0facacc4..169b9f900c 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-mc-shared.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-mc-shared.dtx
@@ -46,7 +46,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{documentation}
% \section{Public Commands}
@@ -181,7 +181,7 @@
% \begin{macrocode}
%<@@=tag>
%<*header>
-\ProvidesExplPackage {tagpdf-mc-code-shared} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-mc-code-shared} {2023-11-19} {0.98q}
{part of tagpdf - code related to marking chunks -
code shared by generic and luamode }
%</header>
diff --git a/macros/latex/contrib/tagpdf/tagpdf-roles.dtx b/macros/latex/contrib/tagpdf/tagpdf-roles.dtx
index de76d3a1d1..bd97e8d7d4 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-roles.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-roles.dtx
@@ -46,7 +46,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{documentation}
% \begin{function}
@@ -98,7 +98,7 @@
% \begin{macrocode}
%<@@=tag>
%<*header>
-\ProvidesExplPackage {tagpdf-roles-code} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-roles-code} {2023-11-19} {0.98q}
{part of tagpdf - code related to roles and structure names}
%</header>
% \end{macrocode}
diff --git a/macros/latex/contrib/tagpdf/tagpdf-space.dtx b/macros/latex/contrib/tagpdf/tagpdf-space.dtx
index 16b5ec5e55..f4bfab5418 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-space.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-space.dtx
@@ -46,7 +46,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{documentation}
% \begin{function}{interwordspace (setup-key)}
@@ -64,7 +64,7 @@
% \begin{macrocode}
%<@@=tag>
%<*header>
-\ProvidesExplPackage {tagpdf-space-code} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-space-code} {2023-11-19} {0.98q}
{part of tagpdf - code related to real space chars}
%</header>
% \end{macrocode}
diff --git a/macros/latex/contrib/tagpdf/tagpdf-struct.dtx b/macros/latex/contrib/tagpdf/tagpdf-struct.dtx
index 76b23e8e4c..9f839f8bc0 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-struct.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-struct.dtx
@@ -46,7 +46,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{documentation}
% \section{Public Commands}
@@ -264,7 +264,7 @@
% \begin{macrocode}
%<@@=tag>
%<*header>
-\ProvidesExplPackage {tagpdf-struct-code} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-struct-code} {2023-11-19} {0.98q}
{part of tagpdf - code related to storing structure}
%</header>
% \end{macrocode}
@@ -1850,7 +1850,7 @@
% \section{Attributes and attribute classes}
% \begin{macrocode}
%<*header>
-\ProvidesExplPackage {tagpdf-attr-code} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-attr-code} {2023-11-19} {0.98q}
{part of tagpdf - code related to attributes and attribute classes}
%</header>
% \end{macrocode}
diff --git a/macros/latex/contrib/tagpdf/tagpdf-tree.dtx b/macros/latex/contrib/tagpdf/tagpdf-tree.dtx
index d244a8dc4c..37fc53b644 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-tree.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-tree.dtx
@@ -47,13 +47,13 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{implementation}
% \begin{macrocode}
%<@@=tag>
%<*header>
-\ProvidesExplPackage {tagpdf-tree-code} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-tree-code} {2023-11-19} {0.98q}
{part of tagpdf - code related to writing trees and dictionaries to the pdf}
%</header>
% \end{macrocode}
diff --git a/macros/latex/contrib/tagpdf/tagpdf-user.dtx b/macros/latex/contrib/tagpdf/tagpdf-user.dtx
index 4724b322dc..704a2f769d 100644
--- a/macros/latex/contrib/tagpdf/tagpdf-user.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf-user.dtx
@@ -46,7 +46,7 @@
% }^^A
% }
%
-% \date{Version 0.98p, released 2023-11-17}
+% \date{Version 0.98q, released 2023-11-19}
% \maketitle
% \begin{documentation}
% \section{Setup commands}
@@ -250,7 +250,7 @@
% \begin{macrocode}
%<@@=tag>
%<*header>
-\ProvidesExplPackage {tagpdf-user} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-user} {2023-11-19} {0.98q}
{tagpdf - user commands}
%</header>
% \end{macrocode}
diff --git a/macros/latex/contrib/tagpdf/tagpdf.dtx b/macros/latex/contrib/tagpdf/tagpdf.dtx
index cfe2ff9df8..907f466a43 100644
--- a/macros/latex/contrib/tagpdf/tagpdf.dtx
+++ b/macros/latex/contrib/tagpdf/tagpdf.dtx
@@ -93,7 +93,7 @@
% \begin{macrocode}
%<@@=tag>
%<*package>
-\ProvidesExplPackage {tagpdf} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf} {2023-11-19} {0.98q}
{ A package to experiment with pdf tagging }
\bool_if:nF
@@ -119,7 +119,7 @@
% \end{macrocode}
%<*debug>
% \begin{macrocode}
-\ProvidesExplPackage {tagpdf-debug} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-debug} {2023-11-19} {0.98q}
{ debug code for tagpdf }
\@ifpackageloaded{tagpdf}{}{\PackageWarning{tagpdf-debug}{tagpdf~not~loaded,~quitting}\endinput}
% \end{macrocode}
@@ -142,7 +142,7 @@
% we define a base package with dummy functions
% \begin{macrocode}
%<*base>
-\ProvidesExplPackage {tagpdf-base} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdf-base} {2023-11-19} {0.98q}
{part of tagpdf - provide base, no-op versions of the user commands }
%</base>
% \end{macrocode}
@@ -168,10 +168,6 @@
\ProcessOptions
% \end{macrocode}
% \section{Packages}
-% We need the temporary version of l3ref until this is in the kernel.
-% \begin{macrocode}
-\RequirePackage{l3ref-tmp}
-% \end{macrocode}
% To be on the safe side for now, load also the base definitions
% \begin{macrocode}
\RequirePackage{tagpdf-base}
@@ -200,43 +196,23 @@
% \begin{macro}{\@@_lastpagelabel:}
% \begin{macrocode}
%<*package>
-\cs_if_exist:NTF \property_new:nnnn
- {
- \cs_new_protected:Npn \@@_lastpagelabel:
- {
- \legacy_if:nT { @filesw }
- {
- \exp_args:NNne \exp_args:NNe\iow_now:Nn \@auxout
- {
- \token_to_str:N \new@label@record
- {@tag@LastPage}
- {
- {abspage} { \int_use:N \g_shipout_readonly_int}
- {tagmcabs}{ \int_use:N \c@g_@@_MCID_abs_int }
- {tagstruct}{\int_use:N \c@g_@@_struct_abs_int }
- }
- }
- }
- }
- }
+\cs_new_protected:Npn \@@_lastpagelabel:
{
- \cs_new_protected:Npn \@@_lastpagelabel:
- {
- \legacy_if:nT { @filesw }
- {
- \exp_args:NNne \exp_args:NNe\iow_now:Nn \@auxout
- {
- \token_to_str:N \newlabeldata
- {@tag@LastPage}
- {
- {abspage} { \int_use:N \g_shipout_readonly_int}
- {tagmcabs}{ \int_use:N \c@g_@@_MCID_abs_int }
- {tagstruct}{\int_use:N \c@g_@@_struct_abs_int }
- }
- }
- }
- }
- }
+ \legacy_if:nT { @filesw }
+ {
+ \exp_args:NNne \exp_args:NNe\iow_now:Nn \@auxout
+ {
+ \token_to_str:N \new@label@record
+ {@tag@LastPage}
+ {
+ {abspage} { \int_use:N \g_shipout_readonly_int}
+ {tagmcabs}{ \int_use:N \c@g_@@_MCID_abs_int }
+ {tagstruct}{\int_use:N \c@g_@@_struct_abs_int }
+ }
+ }
+ }
+ }
+
\AddToHook{enddocument/afterlastpage}
{\@@_lastpagelabel:}
% \end{macrocode}
@@ -372,10 +348,6 @@
% To ease transition to properties we setup internal definition. They can be replaced
% by the property definitions once that is released.
% \begin{macro}{\@@_property_new:nnnn,\@@_property_gset:nnnn,\@@_property_ref:nnn}
-% \begin{macrocode}
-\cs_if_exist:NTF \property_new:nnnn
- {
-% \end{macrocode}
% At first a command to define new properties
% \begin{macrocode}
\cs_new_eq:NN \@@_property_new:nnnn \property_new:nnnn
@@ -397,45 +369,7 @@
\property_record:nn{#1}{#2}
\@esphack
}
- }
-% \end{macrocode}
-% now the same with l3ref-tmp
-% \begin{macrocode}
- {
- \cs_new_protected:Npn \@@_property_new:nnnn #1 #2 #3 #4
- {
- \ref_attribute_gset:nnnn {#1}{#3}{#2}{#4}
- }
- \cs_new_protected:Npn \@@_property_gset:nnnn #1 #2 #3 #4
- {
- \ref_attribute_gset:nnnn {#1}{#3}{#2}{#4}
- }
- \cs_new:Npn \@@_property_ref:nnn #1#2#3
- {
- \exp_args:Nee
- \__ref_value:nnn
- { \tl_to_str:n {#1} } { \tl_to_str:n {#2} } {#3}
- }
- \cs_new:Npn \__ref_value:nnn #1#2#3
- {
- \tl_if_exist:cTF { g__ref_label_ #1 _ #2 _tl }
- { \tl_use:c { g__ref_label_ #1 _ #2 _tl } }
- {
- #3
- }
- }
- \cs_new_eq:NN \@@_property_ref:nn \ref_value:nn
- \cs_new_protected:Npn \@@_property_record:nn #1#2
- {
- \@bsphack
- \ref_label:nn {#1}{#2}
- \@esphack
- }
-% \end{macrocode}
-% to provide problems when switching between main and dev format:
-% \begin{macrocode}
- \providecommand\new@label@record[2]{}
- }
+
% \end{macrocode}
% And a few variants
% \begin{macrocode}
@@ -443,18 +377,6 @@
\cs_generate_variant:Nn \@@_property_ref:nn {en}
\cs_generate_variant:Nn \@@_property_record:nn {en,eV}
% \end{macrocode}
-% The graphic code in latex-lab uses an internal tagpdf command, so until the next
-% release we need to provide it
-% \begin{macrocode}
-\cs_new:Npn \@@_ref_value:enn #1#2#3
- {
- \tl_if_exist:cTF { g__ref_label_ #1 _ #2 _tl }
- { \tl_use:c { g__ref_label_ #1 _ #2 _tl } }
- {
- #3
- }
- }
-% \end{macrocode}
% \end{macro}
%
% \begin{macro}{\@@_property_ref_lastpage:nn}
diff --git a/macros/latex/contrib/tagpdf/tagpdf.pdf b/macros/latex/contrib/tagpdf/tagpdf.pdf
index 1cd330a0df..960f814e6b 100644
--- a/macros/latex/contrib/tagpdf/tagpdf.pdf
+++ b/macros/latex/contrib/tagpdf/tagpdf.pdf
Binary files differ
diff --git a/macros/latex/contrib/tagpdf/tagpdf.tex b/macros/latex/contrib/tagpdf/tagpdf.tex
index 16f1957d32..8f46499e71 100644
--- a/macros/latex/contrib/tagpdf/tagpdf.tex
+++ b/macros/latex/contrib/tagpdf/tagpdf.tex
@@ -16,8 +16,8 @@
}
\DebugBlocksOff
\makeatletter
-\def\UlrikeFischer@package@version{0.98p}
-\def\UlrikeFischer@package@date{2023-11-17}
+\def\UlrikeFischer@package@version{0.98q}
+\def\UlrikeFischer@package@date{2023-11-19}
\makeatother
\documentclass[bibliography=totoc,a4paper]{article}
@@ -34,9 +34,13 @@
\addbibresource{tagpdf.bib}
\usepackage[noparboxrestore]{marginnote}
+\makeatletter
+\renewcommand*{\mn@parboxrestore}{\tagpdfparaOff}%
+\makeatother
\reversemarginpar
\usepackage{tcolorbox}
+%think later ...
\usepackage{tikz}
\usetikzlibrary{positioning}
@@ -57,7 +61,11 @@
\makeatletter \def\lst@visiblespace{\lst@ttfamily{\char32}{\char32}}\makeatother
-\tagpdfsetup{tabsorder=structure}
+\tagpdfsetup{
+ tabsorder=structure,
+ %log=v
+ %show-spaces
+ }
\usepackage[pdfdisplaydoctitle=true]{hyperref}
@@ -73,8 +81,10 @@
\newcommand\PrintKeyName[1]{\textsf{#1}}
\newcommand\pkg[1]{\texttt{#1}}
\newcommand\DescribeKey[1]{\texttt{#1}}
+%\newcommand\cs[1]{\texttt{\textbackslash #1}}
+%\usepackage{ydoc-desc} %hm hyperref ist ein Problem ...
+
-%tagging patches:
\usepackage{tagpdfdocu-patches}
\newcommand\PDF{PDF}
@@ -88,25 +98,38 @@
\begin{document}
-\maketitle
+\tagstructbegin{tag=Title}
+\begin{center}%
+\let\thanks\footnote
+\makeatletter
+\huge \@title \par
+\vskip .5em
+\@author \par
+\vskip 1em%
+\@date \par
+\end{center}%
+\tagstructend
+
+
+
+
\tagstructbegin{tag=Div}
\begin{tcolorbox}[colframe=red,before upper=\tagpdfparaOn]
-This package is not meant for normal use in a document. It started in 2018 as
-a tool to \emph{research} tagging. It is now the base of the code developed
-in the \texttt{latex-lab} bundle for the Tagged PDF project
-\url{https://www.latex-project.org/publications/indexbytopic/pdf/}.
+This package is not meant for normal use in a document. It is on one mainly a tool to \emph{research}
+tagging. On the other side it is the base of the code developed in the \texttt{latex-lab} bundle for the
+Tagged PDF project \url{https://www.latex-project.org/publications/indexbytopic/pdf/}.
-The package is developed together with the code in the \texttt{latex-lab}
-bundle, in the \LaTeX{} format, in the \texttt{pdfmanagement-testphase}
-package (the \LaTeX{} PDF management bundle) and the L3 programming layer.
-That means you should ensure that all these components are up-to-date and in
-sync which each other.
+The package develops together with the code in the \texttt{latex-lab} bundle, in the
+\LaTeX{} format, in the \texttt{pdfmanagement-testphase} package (the \LaTeX{} PDF management bundle)
+and the L3 programming layer.
+That means you should ensure that all these components are up-to-date and in sync which each
+other.
-This package quite probably still contains bugs. It is in parts quite slow as
-the code currently prefers readability over speed. At some time the code will
-be integrated into the \LaTeX{} format and the package will disappear.
+This package quite probably contains bugs. It is in parts
+quite slow as the code currently prefers readability over speed.
+At some time it will disappear when the code has been integrated into the \LaTeX{} format.
This package can still change in an incompatible way.
@@ -134,106 +157,64 @@ Issues, comments, suggestions can be added as issues to these two github tracker
\section{Introduction}
-Since many years the creation of accessible, tagged \PDF{}-files with \LaTeX\
-which conform to the PDF/UA standard has been on the agenda of \TeX-meetings.
-Many people agree that this is important and Ross Moore has done quite some
-work on it. There is also a TUG-mailing list and a web page
-\parencite{tugaccess} dedicated to this topic.
-
-In my opinion missing were means to \emph{experiment} with tagging and
-accessibility. Means to try out, how difficult it is to tag some structures,
-means to try out, how much tagging is really needed (standards and validators
-don't need to be right \ldots), means to test what else is needed so that a
-\PDF{} works e.g. with a screen reader, means to try out how core \LaTeX\
-commands behave if tagging is used. Without such experiments it is in my
-opinion quite difficult to get a feeling about what has to be done, which
-kernel changes are needed, how packages should be adapted.
-
-This package was developed to close this gap by offering \emph{core} commands
-to tag a \PDF{}\footnote{In case you don't know what this means: there will
-be some explanations later on.}. My hope was that the knowledge gained by the
-use of this package would at the end allow to decide if and how code to do
-tagging should be part of the \LaTeX\ kernel.
-
-
-The code has been written so that it can be added as module to the \LaTeX{}
-kernel itself if it turns out to be usable. It therefore avoid to patch
-commands from other packages and wasn't also not an aim of the package to
-develop such patches. While at the end changes to various commands in many
-classes and packages will be needed to get tagged \PDF{} files these changes
-should be done by class, package and document writers themselves using a
-sensible API provided by the kernel and not by some external package that
-adds patches everywhere and would need constant maintenance -- one only need
-to look at packages like tex4ht or bidi or hyperref to see how difficult and
-sometimes fragile this is.
-
-The package is now a part of the Tagged PDF project and triggered already
-various changes in the LaTeX kernel and the engines: There is a new PDF
-management, the new para hooks allows to automatically tag paragraphs, after
-changes in the output routine page breaks and header and footer are handled
-correctly, the engines support now structure destinations. More changes are
-in the latex-lab bundle and can be loaded through testphase keys.
-
-I'm sure that tagpdf still has bugs. Bugs reports, suggestions and comments
-can be added to the issue tracker on github.
-\url{https://github.com/u-fischer/tagpdf} and
-\url{https://github.com/latex3/tagging-project}.
+Since many years the creation of accessible, tagged \PDF{}-files with \LaTeX\ which conform to the PDF/UA standard has been on the agenda of \TeX-meetings. Many people agree that this is important and Ross Moore has done quite some work on it. There is also a TUG-mailing list and a web page \parencite{tugaccess} dedicated to this theme.
+
+In my opinion missing were means to \emph{experiment} with tagging and accessibility. Means to try out, how difficult it is to tag some structures, means to try out, how much tagging is really needed (standards and validators don't need to be right \ldots), means to test what else is needed so that a \PDF{} works e.g. with a screen reader, means to try out how core \LaTeX\ commands behave if tagging is used. Without such experiments it is in my opinion
+quite difficult to get a feeling about what has to be done, which kernel changes are needed, how packages should be adapted.
+
+This package was developed to close this gap by offering \emph{core} commands to tag a \PDF{}%
+\footnote{In case you don't know what this means: there will be some explanations later on.}.
+My hope was that the knowledge gained by the use of this package will at the end
+allow to decide if and how code to do tagging should be part of the \LaTeX\ kernel.
+
+
+The code has been written so that it can be added as module to the \LaTeX{} kernel itself if it turns out to be usable.
+It therefore avoid to patch commands from other packages and is also not an aim of the package to develop such patches. While at the end changes to various commands in many classes and packages will be needed to get tagged \PDF{} files
+these changes should be done by the class, package and document writers themselves using a sensible API provided by the kernel and not by some external package that adds patches everywhere and would need constant maintenance -- one only need to look at packages like tex4ht or bidi or hyperref to see how difficult and sometimes fragile this is.
+
+The package is now a part of the Tagged PDF project and triggered already various changes in the LaTeX kernel and the engines: There is a new PDF management,
+the new para hooks allows to automatically tag paragraphs, after changes in the output routine
+page breaks and header and footer are handled correctly, the engines support
+now structure destinations. More changes are in the latex-lab bundle and can be loaded through testphase keys.
+
+I'm sure that tagpdf still has bugs. Bugs reports, suggestions and comments can be added to the issue tracker on github. \url{https://github.com/u-fischer/tagpdf}.
Please also check the github site and latex-lab for new examples and improvements.
\subsection{Tagging and accessibility}
-While the package is named \texttt{tagpdf} the goal is also \emph{accessible}
-\PDF{}-files. Tagging is \emph{one} (the most difficult) requirement for
-accessibility but there are others. I will mention some later on in this
-documentation, and -- if sensible -- I will also try to add code, keys or
-tips for them.
+While the package is named \texttt{tagpdf} the goal is also \emph{accessible} \PDF{}-files. Tagging is \emph{one} (the most difficult) requirement for accessibility but there are others. I will mention some later on in this documentation, and -- if sensible -- I will also try to add code, keys or tips for them.
-So the name of the package is a bit wrong. As excuse I can only say that it
-is short and easy to pronounce.
+So the name of the package is a bit wrong. As excuse I can only say that it is shorter and easier to pronounce.
\subsection{Engines and modes}
-The package works theoretically with all engines, but the xelatex and the
-latex-dvips-route are basically untested and they also don't support real
-space glyphs so I don't recommend them. lualatex is the most powerful and
-safe modus and should be used for new documents, it is slower than pdflatex
-but requires less compilations. pdflatex works ok and can be used for legacy
-documents; it needs more compilations to resolve all cross references needed
-for the tagging.
+The package works theoretically with all engines,
+but the xelatex and the latex-dvips-route are basically untested tested and they also don't support
+real space glyphs so I don't recommend them.
+lualatex is the most powerful and safe modus and should be used for new documents, it is slower than pdflatex but requires less compilations to get tagging. pdflatex works ok and can be used for legacy documents; it needs more compilations to resolve all cross references needed for the tagging.
The package has two modes: the \emph{generic mode} which should work in
theory with every engine and the \emph{lua mode} which works only with
lualatex and (since version 0.98k) with dvilualatex.
-I implemented the generic mode first. Mostly because my \TeX\ skills are much
-better than my lua skills and I wanted to get the \TeX\ side right before
-starting to fight with attributes and node traversing.
+I implemented the generic mode first. Mostly because my \TeX\ skills are much better than my lua skills and I wanted to get the \TeX\ side right before starting to fight with attributes and node traversing.
-While the generic mode is not bad and I spent quite some time to get it
-working I nevertheless think that the lua mode is the future and the only one
-that will be usable for larger documents. \PDF{} is a page orientated format
-and so the ability of luatex to manipulate pages and nodes after the
-\TeX-processing is really useful here. Also with luatex characters are
-normally already given as unicode.
+While the generic mode is not bad and I spent quite some time to get it working I nevertheless think that the lua mode is the future and the only one that will be usable for larger documents. \PDF{} is a page orientated format and so the ability of luatex to manipulate pages and nodes after the \TeX-processing is really useful here. Also with luatex characters are normally already given as unicode.
-The package uses quite a lot labels (in generic mode more than with luamode).
-It is now based on the property module of the \LaTeX{} kernel. This module
-provide expandable references but the drawback is that they don't always give
-yet good rerun messages if they have changed. I advise to use the
-\pkg{rerunfilecheck} package as a intermediate work-around and when using
-pdflatex compile at best at least once or twice more often then normal.
+The package uses quite a lot labels (in generic mode more than with luamode). At the begin it relied on the \pkg{zref} package, but switched now to a new experimental implementation for labels. The drawback of the new method is that they don't give yet good rerun messages if they have changed. I advise to use the \pkg{rerunfilecheck} package as a intermediate work-around and when using pdflatex compile
+at best at least once or twice more often then normal.
\subsection{References and target PDF version}
My main reference for the first versions of this package was the free
-reference for \PDF{} 1.7. \parencite{pdfreference} and so they implemented
-only support for \PDF{} 1.7.
+reference for \PDF{} 1.7. \parencite{pdfreference} and so the first versions
+of the package implemented only \PDF{} 1.7.
-In 2018 \PDF{} 2.0. has been released. The reference can now be bought at no
-cost through the PDF association.
+In 2018 \PDF{} 2.0. has been released. The reference can be bought at no cost
+through the PDF association.
\PDF{} 2.0 has a number of features that are really needed for good tagging:
it knows more structure types, it allows to add associated files to
@@ -241,16 +222,16 @@ structures---these are small, embedded files which can for example contain
the mathML or source code of an equation---, it knows structure destinations
which allows to link to a structure.
-\PDF{}~2.0 features are currently (end of 2023) not well supported by
+
+\PDF{}~2.0 features are currently (mid 2023) not well supported by
\PDF~consumer. No PDF viewer (including Acrobat) for example can handle name
-spaces and associated files. The PDF Accessibility Checker (PAC) even crashes
-if one tries to load a \PDF{} 2.0 file, and pdftk will create a \PDF{}~1.0
-from it.
+spaces and associated files. PAC~3 even crashes if one tries to load a \PDF{}
+2.0 file, and pdftk will create a \PDF{}~1.0 from it.
Nevertheless \LaTeX{} targets \PDF{} 2.0, tagpdf has added support for
-associated files, for name spaces and other \PDF{} 2.0 features. We recommend
-to use \PDF{} 2.0 if possible and then to complain to the PDF{} consumer if
-something doesn't work.
+associated files, for name spaces and other \PDF{} 2.0 features tagpdf and we
+recommend to use \PDF{} 2.0 if possible and then to complain to the PDF{}
+consumer if something doesn't work.
The package doesn't try to suppress all 2.0 features if an older \PDF{}
version is produced. It normally doesn't harm if a \PDF{} contains keys
@@ -272,23 +253,22 @@ incompabilities.
e.g. if a chunk is opened on one page but closed
on the next page or if the document isn't compiled often enough.
-\item One must check how good the PDF follows requirements of standards
- like PDF/UA \emph{formally}\footnote{The PDF/UA-2 standard for \PDF~2.0
- will hopefully be released begin of 2024.}.
+\item One must check how good the requirements of the PDF/UA standard are
+ followed \emph{formally}\footnote{The PDF/UA-2 standard for \PDF~2.0
+ will hopefully be released in 2023}.
\item
One must check how good the accessibility is \emph{practically}.
\end{itemize}
-Syntax validation and formal standard validation can be done for example with
-preflight of the (non-free) Adobe Acrobat. It can also be done also with the
-free \PDF{} Accessibility Checker (PAC~2021) \parencite{pac3}. There is also
-the validator veraPDF \parencite{verapdf}. A rather new and quite useful tool
-is \enquote{Next Generation PDF} \parencite{ngpdf}, a browser application
-which converts a tagged PDF to html, allows to inspect its structure and also
-to edit the structure. For PDF~2.0 files there is also a checker based on the
-arlington model from veraPDF.
+Syntax validation and formal standard validation can be done with preflight
+of the (non-free) adobe acrobat. It can also be done also with the free
+\PDF{} Accessibility Checker (PAC~2021) \parencite{pac3}. There is also the
+validator veraPDF \parencite{verapdf}. A rather new and quite useful tool is
+\enquote{Next Generation PDF} \parencite{ngpdf}, a browser application which
+converts a tagged PDF to html, allows to inspect its structure and also to
+edit the structure.
Practical validation is naturally the more complicated part.
It needs screen reader, users which actually knows how to handle them,
@@ -303,15 +283,18 @@ don't like the list structure \texttt{L}.
It is also possible that validators contradict: that the one says everything is okay,
while the other complains.
+
+
\subsection{Examples wanted!}
-To make the package usable examples are needed: examples that demonstrate how
-various structures can be tagged and which patches are needed, examples for
-the test suite, examples that demonstrates problems.
+
+To make the package usable examples are needed:
+examples that demonstrate how various structures can be tagged and which patches are needed,
+examples for the test suite, examples that demonstrates problems.
\begin{tcolorbox}
-Feedback, contributions and corrections are welcome!
+Feedback, contribuations and corrections are welcome!
\end{tcolorbox}
@@ -320,6 +303,248 @@ so that uncompressed \PDF{} are created and the internal objects and
structures can be inspected and be compared by the l3build checks.%
+\section{Changes}
+
+This section lists only important changes. More can be found in the \texttt{CHANGELOG.MD} and by checking the git commits.
+
+\subsection{Changes in 0.3}
+
+
+In this version I improved the handling of alternative and actual text. See section~\ref{sec:alt}. This change meant that the package relies on the module \texttt{l3str-convert}.
+
+I no longer try to (pdf-)escape the tag names: it is a bit unclear how to do it at best with luatex. This will perhaps later change again.
+
+
+\subsection{Changes in 0.5}
+
+
+I added code to handle attributes and attribute classes, see section~\ref{sec:attributes} and corrected a small number of code errors.
+
+I added code to add \enquote{real} space glyphs to the \PDF{}, see section \ref{sec:spacechars}.
+
+
+
+\subsection{Changes in 0.6}
+
+
+\textbf{Breaking change!} The attributes used in luamode to mark the MC-chunks are no longer set globally. I thought that global attributes would make it easier to tag, but it only leads to problem when e.g. header and footer are inserted. So from this version on the attributes are set locally and the effect of a \verb+\tagmcbegin+ ends with the current group. This means that in some cases more \verb+\tagmcbegin+ are needed and this affected some of the examples, e.g. the patching commands for sections with KOMA. On the other side it means that quite often one can omit the \verb+\tagmcend+ command.
+
+
+\subsection{Changes in version 0.61}
+
+\begin{itemize}
+\item internal code adaptions to expl3 changes.
+\item dropped the compresslevel key -- probably not needed.
+\end{itemize}
+
+
+\subsection{Changes in version 0.8}
+
+\begin{itemize}
+\item As a first step to include the code proper in the \LaTeX\ kernel the module name has changed from \texttt{uftag} to \texttt{tag}. The commands starting with |\uftag| will stay valid for some time but then be deprecated.
+
+\item \textbf{Breaking change!} The argument of \texttt{newattribute} option should no longer add the dictionary bracket \verb+<<..>>+, they are added by the code.
+
+
+\item \textbf{Breaking change!} The package now requires the new PDF management as provided for now by the package \pkg{pdfmanagement-testphase}. \pkg{pdfmanagement-testphase},
+prepares the ground for better support for tagged PDF in \LaTeX{}.
+It is part of a larger project to automatically generate tagged PDF \url{https://www.latex-project.org/news/2020/11/30/tagged-pdf-FS-study/}
+
+\item Support to add associated files to structures has been added with new keys \texttt{AF}, \texttt{AFinline} and \texttt{AFinline-o}.
+
+\item \textbf{Breaking change!} The support for other 8-bit input encodings has been removed.
+utf8 is now the required encoding.
+
+\item The keys |lang|, |ref| and |E| have been added for structures.
+
+\item The new hooks of LaTeX are used to tagged many paragraphs automatically. The small red numbers around paragraphs in the documentation show them in action. The main problem here is not to tag a paragraph, but to avoid to tag too many: paragraphs pop up in many places.
+\end{itemize}
+
+\subsection{Changes in version 0.81}
+
+\begin{itemize}
+\item Hook code to tag links (URI and GoTo type) have been added. So normally they should simply work if tagging
+is activated.
+
+\item Commands and keys to allow automatic paragraph tagging have been added. See section~\ref{sec:paratagging}.
+As can be seen in this documentation the code works quite good already, but one should be aware that \enquote{paragraphs} can appear in many places and sometimes there are even more paragraph begin than ends.
+
+\item A key to test if local or global setting of the mc-attributes in luamode is more sensible, see \ref{sec:global-local} for more details.
+
+\item New commands to store and reset mc-tags.
+
+\item PDF 2.0 namespaces are now supported.
+\end{itemize}
+
+\subsection{Changes in version 0.82}
+
+A command |\tag_if_active:TF| to test if tagging is active has been added. This allow external packages to write conditional code.
+
+The commands |\tag_struct_parent_int:| and |\tag_struct_insert_annot:nn| have been added. They allow to
+add annotations to the structure.
+
+
+\subsection{Changes in version 0.83}
+
+|\tag_finish_structure:| has been removed, it is no longer a public command.
+
+\subsection{Changes in version 0.90}
+
+\begin{itemize}
+\item Code has been cleaned up and better documented.
+
+\item \textbf{More engines supported} The generic mode of \pkg{tagpdf} now works
+(theoretically, it is not much tested) with all engines supported
+by the \PDF\ management.
+So compilations with Xe\LaTeX{} or with dvips should work. But it should be noted that
+these engines and backends don't support the |interspaceword| option. With Xe\LaTeX{} it is perhaps possible
+implement something with |\XeTeXinterchartoks|, but for the dvips route I don't see an option (apart from lots
+of manual macros everywhere).
+\item \textbf{MC-attributes are global again} In\sidenote{Breaking change!} version 0.6 the attributes used in
+luamode to mark the MC-chunks were no longer set globally. This avoided a number of problems with header and footer
+and background material, but further tests showed that it makes it difficult to correctly mark things like
+links which have to interrupt the current marking code---the attributes couldn't easily escape groups added by
+users. See section~\ref{sec:global-local} for more details.
+\item \textbf{key global-mc removed:} Due to the changes in the attribute keys this key is not longer needed.
+\item \textbf{key check-tags removed:} It doesn't fit. Checks are handled over the logging level.
+\item |\tagpdfget| has been removed, use the expl3 version if needed.
+\item The show commands |\showtagpdfmcdata|, |\showtagpdfattributes|, |\showtagstack| have been removed and replaced
+by a more flexible command |\ShowTagging|.
+\item The commands |\tagmcbegin| and |\tagmcend| no longer ignore following spaces or remove earlier one. While this
+is nice in some places, it also ate spaces in places where this wasn't expected. From now on both commands behave exactly
+like the expl3 versions.
+\item The lua-code to add real space glyphs has been separated from the tagging code. This means that |interwordspace| now
+works also if tagging is not active.
+\item The key |activate| has been added, it open the first structure, see below.
+\end{itemize}
+
+\subsection{Changes in version 0.92}
+
+\begin{itemize}
+\item support for page breaks in pdftex has been added, see section~\ref{sec:splitpara},
+
+
+\item header and footer are tagged as artifacts automatically, see section~\ref{sec:header-footer}.
+
+\item keys \texttt{alttext-o} and \texttt{actualtext-o} has been removed. \texttt{alttext} and \texttt{actualtext}
+will now expand once.
+
+\end{itemize}
+
+
+
+
+\subsection{Changes in version 0.93}
+
+\begin{itemize}
+\item Support for associated files in the root element (key \texttt{root-AF})
+has been added. This allow e.g. to add a css-file which is be used if the \PDF\ is converted to
+html.
+
+\item First steps have been done to adapt the package to planed changes in \LaTeX{}:
+The command \cs{DocumentMetadata} will be
+added to the format and will take over the role of \cs{DeclareDocumentMetadata}
+from \pkg{pdfmanagement-testphase} and additionally
+will also load the pdf management code. This will simplify the documents
+as it will no longer be needed to load the package.
+
+\item The package has now support for \enquote{structure destinations}.
+This is a new type of destinations in \PDF~2.0.
+For pdftex and luatex this requires new binaries. They will be included
+in texlive 2022, miktex already has the new pdftex, the new luatex will probably follow soon.
+
+\item The commands \cs{tagpdfifluatexT}, \cs{tagpdfifluatexTF} has been removed \cs{tagpdfifpdftexT},
+
+\end{itemize}
+
+\subsection{Changes in version 0.94}
+
+In this version a small package, \pkg{tagpdf-base} has been added. It provides
+no-op versions of the main expl3 user commands for packages that want to support
+tagging but can't be sure if the \pkg{tagpdf} package has been loaded.
+
+\subsection{Changes in version 0.95}
+
+Small bug fixes.
+
+\subsection{Changes in version 0.96}
+
+\begin{itemize}
+\item The \texttt{alttext} key has been renamed to \texttt{alt}, the other key name exists as alias.
+
+\item The new command |\tag_struct_object_ref:n| allows to
+ create the object reference of a structure.
+
+\item a new key \texttt{parent} has been added
+ to allow structures to choose their parent structure.
+
+\item a new option \texttt{paratag} allows to change the tag name used for the
+ automatically tagged paragraphs.
+
+\item the commands |\tag_start:|, |\tag_stop:|, |\tag_stop:n| and |\tag_start:n| allow
+ to stop and start tagging (for example in trial typesetting).
+
+\item Small bug fixes.
+\end{itemize}
+
+\subsection{Changes in version 0.98}
+
+\begin{itemize}
+\item The declarations of tag namespaces have been externalized and are now
+read from files when \pkg{tagpdf} is loaded.
+
+\item The \PDF{} format (and some of the standards) declare various parent-child rules for
+structure tags. A first step to implement this rules and check if they are fullfilled have
+been done. More information can be found in section~\ref{sec:parent-child}.
+
+\item As a side effect of the new rule checking, the requirements for new tags
+ have been tightened: Adding a new tag with add-new-tag now requires that the target role is
+ defined. Unknown roles error.
+
+\item |\tagmcbegin| no longer requires that a tag is set, instead if will pick up
+the tag name from the surrounding structure.
+
+\item Structure destination are now created also with \PDF \textless\,2.0. They shouldn't harm and
+can improve the html export.
+
+\end{itemize}
+
+\subsection{Changes in version 0.98a}
+Small bug fixes in code and documentation.
+
+\subsection{Changes in version 0.98b}
+The main change is from now on every structure has an ID and an IDtree is
+added. The ID of a structure can be retrieved with |\tag_get:n|
+see~\ref{sec:retrieve}.
+
+
+\subsection{Changes in version 0.98e}
+
+\begin{itemize}
+\item The main change is that the automatic paratagging uses now a two-level structure. This accompanies development
+in the LaTeX github inthe \texttt{latex-lab} package regarding the tagging of blocks like lists or verbatim.
+See~\ref{sec:paratagging} and also \texttt{latex-lab-block-tagging.dtx} for more background.
+
+\item The command |tag_struct_end:n| has been add to improve debugging.
+\end{itemize}
+
+\subsection{Changes in version 0.98k}
+
+The luamode has been adapted and now allows also the compilation with
+dvilualatex. By default it will insert specials for \texttt{dvips} into the
+dvi. But be aware that \texttt{dvips} can normally not be used as it can't
+handle open type fonts, and extended version would be needed which isn't in
+texlive yet. It is also possible to use \texttt{dvipdfmx} as backend (which
+already has support for open type fonts), for this you need to use
+\texttt{backend=dvipdfmx} in the \cs{DocumentMetadata} command. Real space
+chars will work, but are currently not taken from the current font. This will
+be improved in the next luaotfload version. The compilation with dvilualatex
+is not much tested yet.
+
+\subsection{Changes in version 0.98l}
+
+In 2023 the primitives to write literal code into the pdf have been extended in all engines
+and now allow to delay the expansion of their argument to the shipout. This made it possible to greatly simplify and speed up the code used in generic mode to number the MC-chunks. In most cases building the structure should now need only two or three compilations. The new code requires a current pdfmanagement-testphase and is then used automatically if the new engines are detected.
\subsection{Proof of concept: the tagging of the documentation itself}
@@ -329,30 +554,25 @@ complain, but PAC~3 wanted alternative text for all links (no idea why) and
so I put everywhere simple text like \enquote{link} and \enquote{ref}. The
links to footnotes gave warnings, so I disabled them. I used types from the
\PDF{} version 1.7, mostly as I had no idea what should be used for code in
-2.0. Margin notes were simply wrong and there were tagging commands
-everywhere \ldots
+2.0. Margin notes were simply wrong \ldots
The tagging has been improved and automated over time in sync with
-improvements and new features in the LaTeX kernel, the latex-lab bundle and
-the \PDF\ management code and is now much better. Only a few
-structures---mostly some from currenty unsupported packages--- still need
-manual tagging. But sadly the output of the validators don't quite reflect
-the improvements. The documentation uses now \PDF~2.0 and PAC~3 can't handle
-this, it claims that the file is damaged. The Adobe validator has a bug and
-doesn't like the (valid) use of the \texttt{Lbl} tag for the section numbers
-(see figure~\ref{fig:adobe}).
+improvements and new features in the LaTeX kernel and the \PDF\ management
+code and is now much better. Sadly the output of the validators don't quite
+reflect the improvements. The documentation uses now \PDF~2.0 and PAC~3
+can't handle this, it claims that the file is damaged. The Adobe validator
+has a bug and doesn't like the (valid) use of the \texttt{Lbl} tag for the
+section numbers (see figure~\ref{fig:adobe}).
-But even if the documentation passed the tests of the validators: as
-mentioned above passing a formal test doesn't mean that the content is really
-good and usable. The user commands used for the tagging and also some of the
-patches used are still rather crude. So there is lot space for improvement.
+
+But even if the documentation passed the tests of the validators: as mentioned above passing a formal test doesn't mean that the content is really good and usable. I have a lot doubts that the code parts are really readable. The bibliography and the references must be improved. The user commands used for the tagging and also some of the patches used are still rather crude. So there is lot space for improvement.
\begin{tcolorbox}[before upper=\tagpdfparaOn]
-Be aware that to create the tagged version a current lualatex-dev and a
-current version of the pdfmanagment-testphase package is needed.
+Be aware that to create the tagged version a current lualatex-dev and a current version of the pdfmanagment-testphase package is needed.
\end{tcolorbox}
+
\includegraphics[alt=PAC 3 report]{pac3}
@@ -829,13 +1049,12 @@ This sounds easy. But there are quite a number of traps, mostly with pdfLaTeX:
While in generic mode the commands insert the literals directly and so have
all the problems described above the lua mode works quite differently: The
-tagging commands don't insert literals but set some (global)
-\emph{attributes} which are attached to all the following nodes. When the
-page is shipped out some lua code is called which wanders through the shipout
-box and injects the literals at the places where the attributes changes.
+tagging commands don't insert literals but set some \emph{attributes} which
+are attached to all the following nodes. When the page is shipped out some
+lua code is called which wanders through the shipout box and injects the
+literals at the places where the attributes changes.
-This means that quite a number of problems mentioned above are not relevant
-for the lua mode:
+This means that quite a number of problems mentioned above are not relevant for the lua mode:
\begin{enumerate}
\item Pagebreaks between start and end of the marker are
@@ -873,9 +1092,6 @@ These commands insert the begin of the marked content code in the \PDF{}.
They don't start a paragraph. \emph{They don't start a group}. Such markers
should not be nested. The command will warn you if this happens.
-In the generic mode the commands insert literals. These are whatsits and so
-can affect spacing. In lua mode they set an attribute \emph{globally}.
-
The key-val list understands the following keys:
\begin{description}
@@ -1043,17 +1259,12 @@ This (expandable) command give back some variables. Currently the working key wo
\subsubsection{Luamode: global or not global -- that is the question}\label{sec:global-local}
-In\sidenote{Luamode mode only} luamode the mc-commands set and unset an
-attribute to mark the nodes. One can view such an attribute like a font
-change or a color: they affect all following chars and glue nodes until
-stopped.
+In\sidenote{Luamode mode only} luamode the mc-commands set and unset an attribute to mark the nodes. One can view such an attribute like a font change or a color: they affect all following chars and glue nodes until stopped.
-From version 0.6 to 0.82 the attributes were set locally. This had the
-advantage that the attributes didn't spill over in area where they are not
-wanted like the header and footer or the background pictures. But it had the
-disadvantage that it was difficult for an inner structure to correctly
-interrupt the outer mc-chunk if it can't control the group level. For example
-this didn't work due to the grouping inserted by the user:
+From version 0.6 to 0.82 the attributes were set locally.
+This had the advantage that the attributes didn't spill over in area where they are not wanted like the header and footer or the background pictures.
+But it had the disadvantage that it was difficult for an inner structure to correctly interrupt the outer
+mc-chunk if it can't control the group level. For example this didn't work due to the grouping inserted by the user:
\begin{taglstlisting}
\tagstructbegin{tag=P}
@@ -1295,26 +1506,25 @@ rerun.
\subsubsection{Automatic tagging of paragraphs}\label{sec:paratagging}
-Another feature that emerged from the \LaTeX{} tagged PDF project are hooks
-at the begin and end of paragraphs. \pkg{tagpdf} makes use of these hooks to
-tag paragraphs. In the first version it added only one structure, but this
-proved to be not adequate:
+Another feature that emerged from the \LaTeX{} tagged PDF project are hooks at the begin and end of paragraphs.
+\pkg{tagpdf} makes use of these hooks to tag paragraphs. In the first version it added only one structure, but this proved to be not adequate:
Paragraphs in \LaTeX{} can be nested, e.g., you can have a paragraph
containing a display quote, which in turn consists of more than one
(sub)paragraph, followed by some more text which all belongs to the
same outer paragraph.
-In the \PDF{} model and in the HTML model that is not supported: the rules in
-\PDF{} specification do not allow \texttt{P}-structures to be nested --- a
-limitation that conflicts with real live, given that such constructs are
-quite normal in spoken and written language.
+In the \PDF{} model and in the HTML model that is not supported: the rules
+in \PDF{} specification do not allow \texttt{P}-structures to be nested --- a
+limitation that conflicts with real live, given that such
+constructs are quite normal in spoken and written language.
-The approach we take (starting with march 2023, version 0.98e) to resolve
-this is to model such \enquote{big} paragraphs with a structure named
-\texttt{text-unit} and use \texttt{P} (under the name \texttt{text}) only for
-(portions of) the actual paragraph text in a way that the \texttt{P}s are not
-nested. As a result we have for a simple paragraph two structures:
+The approach we take (starting with march 2023, version 0.98e)
+to resolve this is to model such \enquote{big}
+paragraphs with a structure named \texttt{text-unit} and use \texttt{P} (under the name \texttt{text})
+only for (portions of) the actual paragraph text in a way that the
+\texttt{P}s are not nested. As a result we have for a simple
+paragraph two structures:
\begin{taglstlisting}
<text-unit>
@@ -1340,54 +1550,41 @@ nested. As a result we have for a simple paragraph two structures:
</text-unit>
\end{taglstlisting}
+In other words such a display block is always embedded in a
+|<text-unit>| structure, possibly preceded by a |<text>|\ldots|</text>| block
+and possibly followed by one, though both such blocks are optional.
+More information about this can be found in the documentation of \texttt{latex-lab-block-tagging}.
-In other words such a display block is always embedded in a |<text-unit>|
-structure, possibly preceded by a |<text>|\ldots|</text>| block and possibly
-followed by one, though both such blocks are optional. More information about
-this can be found in the documentation of \texttt{latex-lab-block-tagging}.
+As a consequence \pkg{tagpdf} now adds two structures if paratagging is activated. The new code
+to tag display blocks extends this code to handle the nesting of lists and other display structures.
-As a consequence \pkg{tagpdf} now adds two structures if paratagging is
-activated. The new code to tag display blocks extends this code to handle the
-nesting of lists and other display structures.
+The automatic tagging require that for every begin of a paragraph with the begin hook code
+there a corresponding end with the closing hook code. This can fail, e.g if a |vbox| doesn't correctly issue a |\par| at the end.
+If this happens the tagging structure can get very confused. At the end of the document \pkg{tagpdf} checks if
+the number of outer and inner start and end paragraph structures created with the automatic paratagging code
+are equal and it will error if not.
-The automatic tagging require that for every begin of a paragraph with the
-begin hook code there a corresponding end with the closing hook code. This
-can fail, e.g if a |vbox| doesn't correctly issue a |\par| at the end. If
-this happens the tagging structure can get very confused. At the end of the
-document \pkg{tagpdf} checks if the number of outer and inner start and end
-paragraph structures created with the automatic paratagging code are equal
-and it will error if not.
+The automatic tagging of paragraphs can be deactivated completely or only the outer level with the |\tagtool| keys
+|para| and |para-flattened| or with the (now deprecated) commands |\tagpdfparaOn| and |\tagpdfparaOff|.
-The automatic tagging of paragraphs can be deactivated completely or only the
-outer level with the |\tagtool| keys |para| and |para-flattened| or with the
-(now deprecated) commands |\tagpdfparaOn| and |\tagpdfparaOff|.
-Nesting the activation and deactivation of the tagging of paragraphs can be
-quite difficult. For example if it is unclear if the inner code issues a
-|\par| or not it is not trivial to exclude an end hook for every excluded
-begin hook. In such cases it can be easier to use the |paratag| key with the
-value |NonStruct| to convert some |P|-structures into |NonStruct|-structures
-without real meaning.
+Nesting the activation and deactivation of the tagging of paragraphs can be quite difficult. For example if it is unclear if the inner code issues a |\par| or not it is not trivial to exclude an end hook for every excluded begin hook.
+In such cases it can be easier to use the |paratag| key with the value |NonStruct| to convert some |P|-structures
+into |NonStruct|-structures without real meaning.
\subsection{Task 2: Marking the structure}
-The structure is represented in the \PDF{} with a number of objects of type
-\texttt{StructElem} which build a tree: each of this objects points back to
-its parent and normally has a number of kid elements, which are either again
-structure elements or -- as leafs of the tree -- the marked contents chunks
-marked up with the \verb+tagmc+-commands. The root of the tree is the
-\texttt{StructTreeRoot}.
+
+
+The structure is represented in the \PDF{} with a number of objects of type \texttt{StructElem} which build a tree: each of this objects points back to its parent and normally has a number of kid elements, which are either again structure elements or -- as leafs of the tree -- the marked contents chunks marked up with the \verb+tagmc+-commands. The root of the tree is the \texttt{StructTreeRoot}.
\subsubsection{Structure types}
-The tree should reflect the \emph{semantic} meaning of the text. That means
-that the text should be marked as section, list, table head, table cell and
-so on. A number of standard structure types is predefined, see section
-\ref{sec:new-tag} but it is allowed to create more. If you want to use types
-of your own you must declare them. E.g. this declares two new types
-\texttt{TAB} and {FIG} and bases them on \texttt{P}:
+
+
+The tree should reflect the \emph{semantic} meaning of the text. That means that the text should be marked as section, list, table head, table cell and so on. A number of standard structure types is predefined, see section \ref{sec:new-tag} but it is allowed to create more. If you want to use types of your own you must declare them. E.g. this declares two new types \texttt{TAB} and {FIG} and bases them on \texttt{P}:
\begin{taglstlisting}
@@ -1401,9 +1598,10 @@ of your own you must declare them. E.g. this declares two new types
\subsubsection{Sectioning}
-The sectioning units can be structured in two ways: a flat, html-like and a
-more (in pdf/UA2 basically deprecated) xml-like version. The flat version
-creates a structure like this:
+
+
+The sectioning units can be structured in two ways: a flat, html-like and a more (in pdf/UA2 basically deprecated) xml-like version.
+The flat version creates a structure like this:
\begin{taglstlisting}
@@ -1416,10 +1614,7 @@ creates a structure like this:
So here the headings are marked according their level with \texttt{H1}, \texttt{H2}, etc.
-
-In the xml-like tree the complete text of a sectioning unit is surrounded
-with the \texttt{Sect} tag, and all headers with the tag \texttt{H}. Here the
-nesting defines the level of a sectioning heading.
+In the xml-like tree the complete text of a sectioning unit is surrounded with the \texttt{Sect} tag, and all headers with the tag \texttt{H}. Here the nesting defines the level of a sectioning heading.
\begin{taglstlisting}
@@ -1434,12 +1629,7 @@ nesting defines the level of a sectioning heading.
\end{taglstlisting}
-
-The flat version is more \LaTeX-like and it is rather straightforward to
-patch \verb+\chapter+, \verb+\section+ and so on to insert the appropriates
-\texttt{H\ldots} start and end markers. The xml-like tree is more difficult
-to automate. If such a tree is wanted I would recommend to use -- like the
-context format -- explicit commands to start and end a sectioning unit.
+The flat version is more \LaTeX-like and it is rather straightforward to patch \verb+\chapter+, \verb+\section+ and so on to insert the appropriates \texttt{H\ldots} start and end markers. The xml-like tree is more difficult to automate. If such a tree is wanted I would recommend to use -- like the context format -- explicit commands to start and end a sectioning unit.
@@ -1473,13 +1663,13 @@ The key-val list understands the following keys:
the two attributes \texttt{tagstruct} (the structure number) and \texttt{tagstructobj} (the
object reference).
- \item[\PrintKeyName{parent}] With the parent key one can choose another
- parent. The value is a structure number which must refer to an
- already existing, previously created structure. Such a structure
- number can have been stored previously with \cs{tag\_get:n}, but one
- can also use a label on the parent structure and then use
- \cs{ref\_value:nn}\verb+{tagpdfstruct-label}{tagstruct}+ to retrieve
- it.
+ \item[\PrintKeyName{parent}]
+ % By default a structure is added as kid to the currently active structure.
+ With the parent key one can choose another parent. The value is a structure number which
+ must refer to an already existing, previously created structure. Such a structure
+ number can have been stored previously with \cs{tag\_get:n}, but one can also use
+ a label on the parent structure and then use
+ \cs{ref\_value:nn}\verb+{tagpdfstruct-label}{tagstruct}+ to retrieve it.
\item[\PrintKeyName{alt}] This key inserts an \texttt{/Alt} value in the
dictionary of structure object, see section~\ref{sec:alt}. The value
@@ -1611,52 +1801,44 @@ The key-val list understands the following keys:
\begin{docCommand}[nosep]{tagstructend}{}\end{docCommand}
\begin{docCommand}{tag_struct_end:}{}\end{docCommand}
-
-These commands end a structure. They don't end a group and it doesn't
-matter if they are in another group as the starting commands.
+These commands end a structure. They don't end a group and it doesn't matter if they are in another group as the starting commands.
\begin{docCommand}[nosep]{tagstructuse}{\marg{label}}\end{docCommand}
\begin{docCommand}{tag_struct_use:n}{\marg{label}}\end{docCommand}
-These commands insert a structure previously stashed away as kid into the
-currently active structure. A structure should be used only once, if the
-structure already has a parent you will get a warning.
+
+These commands insert a structure previously stashed away as kid into the currently active structure. A structure should be used only once, if the structure already has a parent you will get a warning.
+
\subsubsection{Root structure}
-A document should have at least one structure which contains the whole
-document. A suitable tag is \texttt{Document}. Such a root is now always
-added automatically. Its type can be changed with the key
-\texttt{activate}.
+
+
+A document should have at least one structure which contains the whole document. A suitable tag is \texttt{Document}.
+Such a root is now always added automatically. Its type can be changed with the key \texttt{activate}.
+
+
+
\subsubsection{Attributes and attribute classes}\label{sec:attributes}
-Structure Element can have so-called attributes. A single attribute is a
-dictionary (or a stream but this is currently not supported by the package
-as I don't know an use-case) with at least the required key \verb+/O+ (for
-\enquote{Owner} which describes the scope the attribute applies too. As an
-example here an attribute that can be attached to tabular header (type TH)
-and adds the info that the header is a column header:
+Structure Element can have so-called attributes. A single attribute is a dictionary%\footnote{
+(or a stream but this is currently not supported by the package as I don't know an use-case)
+with at least the required key \verb+/O+ (for \enquote{Owner} which describes the scope the attribute applies too.
+As an example here an attribute that can be attached to tabular header (type TH) and adds the info that the header is a column header:
\begin{taglstlisting}
<</O /Table /Scope /Column>>
\end{taglstlisting}
+One or more such attributes can be attached to a structure element. It is also possible to store such an attribute under a symbolic name in a so-called \enquote{ClassedMap} and then to attach references to such classes to a structure.
-One or more such attributes can be attached to a structure element. It is
-also possible to store such an attribute under a symbolic name in a
-so-called \enquote{ClassedMap} and then to attach references to such
-classes to a structure.
-
+To use such attributes you must at first declare it in \verb+\tagpdfsetup+ with the key \texttt{newattribute}. This key takes two argument, a name and the content of the attribute.
+The name should be a sensible key name, it is converted to a pdf name with
+\verb+\pdf_name_from_unicode_e:n+, so slashes and spaces are allow. The content should be a dictionary without the braket.
-To use such attributes you must at first declare it in \verb+\tagpdfsetup+
-with the key \texttt{newattribute}. This key takes two argument, a name and
-the content of the attribute. The name should be a sensible key name, it is
-converted to a pdf name with \verb+\pdf_name_from_unicode_e:n+, so slashes
-and spaces are allow. The content should be a dictionary without the
-bracket.
\begin{taglstlisting}
@@ -1670,17 +1852,17 @@ bracket.
\end{taglstlisting}
-Attributes are only written to the \PDF{} when used, so it is not a problem
-to predeclare a number of standard attributes.
+
+Attributes are only written to the \PDF{} when used, so it is not a problem to predeclare a number of standard attributes.
+
+
+It is your responsability that the content of the dictionary is valid \PDF{} and that the values are sensible!
-It is your responsability that the content of the dictionary is valid
-\PDF{} and that the values are sensible!
+Attributes can then be used with the key \PrintKeyName{attribute} or \PrintKeyName{attribute-class} which both take a comma list of attribute names as argument:
+%\footnote{That's not really a sensible example}:
-Attributes can then be used with the key \PrintKeyName{attribute} or
-\PrintKeyName{attribute-class} which both take a comma list of attribute
-names as argument:
\begin{taglstlisting}
@@ -1694,27 +1876,17 @@ names as argument:
\subsection{Task 3: tree Management}
-When all the document content has been correctly marked and the data for
-the trees has been collected they must be flushed to the \PDF{}. This is
-done automatically (if the package has been activated) with an internal
-command in an end document hook.
+When all the document content has been correctly marked and the data for the trees has been collected they must be flushed to the \PDF{}. This is done automatically (if the package has been activated) with an internal command in an end document hook.
\begin{docCommand}{__tag_finish_structure:}{}\end{docCommand}
-This will hopefully write all the needed objects and values to the \PDF{}.
-(Beside the already mentioned \texttt{StructTreeRoot} and
-\texttt{StructElem} objects, additionally a so-called \texttt{ParentTree}
-is needed which records the parents of all the marked contents bits, a
-\texttt{Rolemap}, perhaps a \texttt{ClassMap} and object for the
-attributes, and a few more values and dictionaries).
+This will hopefully write all the needed objects and values to the \PDF{}. (Beside the already mentioned \texttt{StructTreeRoot} and \texttt{StructElem} objects, additionally a so-called \texttt{ParentTree} is needed which records the parents of all the marked contents bits, a \texttt{Rolemap}, perhaps a \texttt{ClassMap} and object for the attributes, and a few more values and dictionaries).
\subsection{A fully marked up document body}
-The following shows the marking needed for a section, a sentence and a list
-with two items. It is obvious that one wouldn't like to have to do this for
-real documents. If tagging should be usable, the commands must be hidden as
-much as possible inside suitable \LaTeX\ commands and environments.
+
+The following shows the marking needed for a section, a sentence and a list with two items. It is obvious that one wouldn't like to have to do this for real documents. If tagging should be usable, the commands must be hidden as much as possible inside suitable \LaTeX\ commands and enviroments.
\begin{taglstlisting}
@@ -1769,12 +1941,10 @@ much as possible inside suitable \LaTeX\ commands and environments.
\subsection{Interrupting the tagging}
-
-Experience showed that it must be possible to interrupt tagging in some
-places. For example various packages do trial typesetting to measure text
-and this shouldn't create structures. There are therefore a number of
-commands for various use cases\footnote{it is quite possible that some of
-the commands will disappear again if we realize that they are not fitting!}
+Experience showed that it must be possible to interrupt tagging in some places.
+For example various packages do trial typesetting to measure text and this shouldn't create
+structures. There are therefore a number of commands for various use cases\footnote{it is
+quite possible that some of the commands will disappear again if we realize that they are not fitting!}
\begin{docCommand}[nosep]{tag_stop:}{}\end{docCommand}
@@ -1784,10 +1954,9 @@ the commands will disappear again if we realize that they are not fitting!}
\begin{docCommand}[nosep]{tag_stop_group_begin:}{}\end{docCommand}
\begin{docCommand}{tag_start_group_end:}{}\end{docCommand}
-This commands stop and start tagging in the current group by switching
-\emph{local} booleans. They also stop the increasing of the counters which
-keep track of paragraphs if the correct wrapper commands are used. The
-grouping commands also open and close a group.
+This commands stop and start tagging in the current group
+by switching \emph{local} booleans.
+The grouping commands also open and close a group.
Restarting tagging is normally only needed if groups can't be used and then
must be done with care: |\tagstart| should normally only restart tagging if
@@ -1986,9 +2155,8 @@ to be the first element in the parent structure, and elements like \texttt{Part}
inherit restrictions from parent structures.
External standards like \PDF/UA can add more rules.
-
-Altogether this doesn't make it easy to check if a structure tree is
-conformant or not without slowing down the compilation a lot.
+Altogether this doesn't make it easy to check if a structure tree is conformant or not without slowing down
+the compilation a lot.
With version 0.98 some first steps to do checks (and to react to the result of a change)
have been implemented. Some checks will led to warning directly, but the majority
@@ -2004,12 +2172,8 @@ Package tagpdf Info: The rule between parent 'H2 (from subsection/latex)'
(tagpdf) and child 'H1 (from section/latex)' is '-1 ($\emptyset$)'
\end{taglstlisting}
-
-The descriptions of the parent and childs are rather verbose as the checks
-have to take role mapping and name spaces into account. The result of a
-check is a number---negative if the relation is not allowed, positive if
-allowed. The text in the parentheses show the symbols used in the
-\PDF-matrix.
+The descriptions of the parent and childs are rather verbose as the checks have to take role mapping and name spaces into account. The result of a check is a number---negative if the relation is not allowed,
+positive if allowed. The text in the parentheses show the symbols used in the \PDF-matrix.
Be aware
\begin{itemize}
@@ -2019,54 +2183,35 @@ in \PDF~1.7 and then has different containment rules.
\item The special tag \texttt{MC} stands for mc-chunks, so \enquote{real content} (the matrix has containments rules for this too).
\item Currently there is as only negative number \texttt{\textminus1} but that is bound to change, depending on if (and how) it is possible to \enquote{repair} a disallowed parent-child relation.
\item Warnings can be wrong.
-\end{itemize}
+\end{itemize}
+
+
+
+
+
\section{\enquote{Real} space glyphs}\label{sec:spacechars}
-TeX uses only spaces (horizontal movements) to separate words. That means
-that a \PDF{} reader has to use some heuristic when copying text or
-reflowing the text to decide if a space is meant as a word boundary or e.g.
-as a kerning. Accessible document should use real space glyphs (U+0032)
-from a font in such places.
+
+TeX uses only spaces (horizontal movements) to separate words. That means that a \PDF{} reader has to use some heuristic when copying text or reflowing the text to decide if a space is meant as a word boundary or e.g. as a kerning. Accessible document should use real space glyphs (U+0032) from a font in such places.
With the key \PrintKeyName{interwordspace} you can activate such space glyphs.
-With pdftex this will simply call the primitive
-\verb+\pdfinterwordspaceon+. pdftex will then insert at various places a
-char from a font called dummy-space. Attention! This means that at every
-space there are additional font switches in the \PDF{}: from the current
-font to the dummy-space font and back again. This will make the \PDF{}
-larger. As \verb+\pdfinterwordspaceon+ is a primitive function it can't be
-fine tuned or adapted. You can only turn it on and off and insert manually
-such a space glyph with \verb+\pdffakespace+.
-
-With luatex (in luamode) |interwordspace| is implemented with a
-lua-function which is inserted in two callbacks and marks up the places
-where it seems sensible to inter a space glyph. Later in the process the
-space glyphs are injected -- the code will take the glyph from the current
-font if this has a space glyph or switch to the default latin modern font.
-The current code works reasonable well in normal text. |interwordspace| can
-be used without actually tagging a document.
-
-The key \PrintKeyName{show-spaces} will show lines at the places where in
-lua mode spaces are inserted and so can help you to find problematic
-places. For listings -- which have a quite specific handling of spaces --
-you can find a suggestion in the example \texttt{ex-space-glyph-listings}.
-
-\emph{Attention:} Even with real spaces copy\& pasting of code doesn't need
-to give the correct results: you get spaces but not necessarly the right
-number of spaces. The \PDF{} viewers I tried all copied four real space
-glyphs as one space. I only got the four spaces with the export to text or
-xml in the AdobePro.
+With pdftex this will simply call the primitive \verb+\pdfinterwordspaceon+. pdftex will then insert at various places a char from a font called dummy-space. Attention! This means that at every space there are additional font switches in the \PDF{}: from the current font to the dummy-space font and back again. This will make the \PDF{} larger. As \verb+\pdfinterwordspaceon+ is a primitive function it can't be fine tuned or adapted. You can only turn it on and off and insert manually such a space glyph with \verb+\pdffakespace+.
+
+With luatex (in luamode) |interwordspace| is implemented with a lua-function which is inserted in two callbacks and marks up the places where it seems sensible to inter a space glyph. Later in the process the space glyphs are injected -- the code will take the glyph from the current font if this has a space glyph or switch to the default latin modern font. The current code works reasonable well in normal text.
+|interwordspace| can be used without actually tagging a document.
+
+The key \PrintKeyName{show-spaces} will show lines at the places where in lua mode spaces are inserted and so can help you to find problematic places. For listings -- which have a quite specific handling of spaces -- you can find a suggestion in the example \texttt{ex-space-glyph-listings}.
+
+\emph{Attention:} Even with real spaces copy\& pasting of code doesn't need to give the correct results: you get spaces but not necessarly the right number of spaces. The \PDF{} viewers I tried all copied four real space glyphs as one space. I only got the four spaces with the export to text or xml in the AdobePro.
\begin{docCommand}{pdffakespace}{}\end{docCommand}
-This is in pdftex a primitive. It inserts the dummy space glyph.
-\pkg{tagpdf} defines this command also for luatex -- attention if can
-perhaps insert break points.
+This is in pdftex a primitive. It inserts the dummy space glyph. \pkg{tagpdf} defines this command also for luatex -- attention if can perhaps insert break points.
\section{Structure destinations}\label{sec:struct-dest}
@@ -2076,33 +2221,33 @@ perhaps insert break points.
of the viewer and so give the impression that a link jumped to the word in this place.
But in reality they are not connected to the content.
- Starting with pdf~2.0 destinations can in a tagged PDF also point to a
- structure (to a \texttt{/StructElem} object). GoTo links can then
- additionally to the \texttt{/D} key which points to a standard page
- destination also point to such a structure destination with an
- \texttt{/SD} key. Programs that e.g. convert such a PDF to html can then
- create better links. (According to the reference, PDF-viewer should prefer
- the structure destination over the page destination, but as far as it is
- known this isn't done yet.)
-
- At first structure destinations (and GoTo links making use of it) could
- natively only be created with the dvipdfmx backend. With pdftex and
- lualatex it was only possible to create a restricted type which used only
- the \enquote{Fit} mode. Starting with \TeX{}live 2022 (earlier in miktex)
- both engines knew new keywords which allowed to create structure
- destination easily and support has been already added to the \PDF\
- management and \pkg{tagpdf}. In most cases it should simply work, but one
- should be aware that as one now has a destination that is actually tied to
- the content it gets more important to actually consider the context and
- the place where such destinations are created. It now makes a difference
- if the destination is created before the structure is opened or after so
- in some cases code that place destinations should be changed to place them
- inside the structure they belong too. One also has to consider the pages
- connected to the destinations: The structure destination is bound to the
- page where the structure \emph{begins}, if this differ from the page of
- the page destination (e.g. if the destination is created by a
- \verb+\phantomsection+ in the middle of a longer paragraph) then it may
- be necessary to surround destinations with a dummy structure (a Span or an
+ Starting with pdf~2.0 destinations can in a tagged PDF also point
+ to a structure (to a \texttt{/StructElem} object).
+ GoTo links can then additionally to the \texttt{/D} key which points to a
+ standard page destination also point to such a structure destination with an \texttt{/SD} key.
+ Programs that e.g. convert such a PDF to html can then create better links.
+ (According to the reference, PDF-viewer should prefer the structure destination
+ over the page destination, but as far as it is known this isn't done yet.)
+
+ Currently structure destinations (and GoTo links making use of it) could natively only
+ be created with the dvipdfmx backend. With pdftex and lualatex it was only possible to create
+ a restricted type which used only the \enquote{Fit} mode. Starting with
+ \TeX{}live 2022 (earlier in miktex) both engines will knew new keywords which allow
+ to create structure destination easily.
+
+ Support for this has been already added to the \PDF\ management and
+ \pkg{tagpdf} will make use of it if possible. In most cases it should simply
+ work, but one should be aware that as one now has a destination that is
+ actually tied to the content it gets more important to actually consider the
+ context and the place where such destinations are created. It now makes a
+ difference if the destination is created before the structure is opened or
+ after so in some cases code that place destinations should be changed to
+ place them inside the structure they belong too. One also has to consider
+ the pages connected to the destinations: The structure destination is bound
+ to the page where the structure \emph{begins}, if this differ from the page
+ of the page destination (e.g. if the destination is created by a
+ \verb+\phantomsection+ in the middle of a longer paragraph) then may be
+ necessary to surround destinations with a dummy structure (a Span or an
Artifact) to get the right page number.
\section{Storing and reusing boxes}\label{sec:savebox}
@@ -2268,38 +2413,30 @@ tagging commands) the following strategy can be used:
\section{Accessibility is not only tagging}
-A tagged \PDF{} is needed for accessibility but this is not enough. As
-already mentioned there are more requirements:
+
+A tagged \PDF{} is needed for accessibility but this is not enough. As already mentioned there are more requirements:
\begin{itemize}
- \item The language must be declared by adding a \texttt{/Lang xx-XX} to
- the \PDF{} catalog or -- if the language changes for a part of the
- text to the structure or the marked content. Setting the document
- language can be done with the \texttt{lang} option of
- \cs{DocumentMetadata}. For settings in marked content and structure
- the \texttt{lang} key can be used too.
-
- \item All characters must have an unicode representation or a suitable
- alternative text. With lualatex and open type (unicode) fonts this
- is normally not a problem. With pdflatex it could need additional
- \verb+\pdfglyphtounicode+ commands.
-
+ \item The language must be declared by adding a \texttt{/Lang xx-XX} to the \PDF{} catalog or -- if the language changes for a part of the text to the structure or the marked content. Setting the document language can be rather easily done with existing packages. With the new \PDF{} resource management it should be done with \verb+\pdfmanagement_add:nnn{Catalog}{Lang}{(en-US)}+. For settings in marked content and structure I will have to add keys.
+ \item All characters must have an unicode representation or a suitable alternative text.
+ With lualatex and open type (unicode) fonts this is normally not a problem. With pdflatex it could need
+ \begin{taglstlisting}
+ \input{glyphtounicode}
+ \pdfgentounicode=1
+ \end{taglstlisting}
+
+ and perhaps some\verb+\pdfglyphtounicode+ commands.
\item Hard and soft hyphen must be distinct.
-
- \item Spaces between words should be space glyphs and not only a
- horizontal movement. See section~\ref{sec:spacechars}.
-
- \item Various small infos must be present in the catalog dictionary,
- info dictionary and the page dictionaries, e.g. metadata like title.
- This can be done with the options of \cs{DocumentMetadata}. See the
- documentation of \texttt{l3pdfmeta} for details.
+ \item Spaces between words should be space glyphs and not only a horizontal movement. See section~\ref{sec:spacechars}.
+ \item Various small infos must be present in the catalog dictionary, info dictionary and the page dictionaries, e.g. metadata like title.
\end{itemize}
+If suitable I will add code for this tasks to this packages. But some of them can also be done already with existing packages like hyperref, hyperxmp, pdfx.
\section{Debugging}
-While developing commands and tagging a document, it can be useful to get
-some info about the current structure. For this a show command is provided
+While developing commands and tagging a document, it can be useful to get some info about the current structure. For this
+a show command is provided
\begin{docCommand}{ShowTagging}{\marg{key-val}}\end{docCommand}
@@ -2337,6 +2474,7 @@ This command takes as argument a key-val list which implements a number of show
\section{To-do}
+
\begin{itemize}
\item Add commands and keys to enable/disable the checks.
\item Check/extend the code for language tags.
@@ -2359,304 +2497,10 @@ This command takes as argument a key-val list which implements a number of show
\item Find someone to check and improve the lua code
\item Move more things to lua in the luamode
\item Find someone to check and improve the rest of the code
-\item Check differences between \PDF{} versions 1.7 and 2.0. (progress:
- WIP, namespaces done)
+\item Check differences between \PDF{} versions 1.7 and 2.0. (progress: WIP, namespaces done)
\item bidi?
\end{itemize}
-\section{History}
-
-This section lists important changes during the development of the package.
-More can be found in the \texttt{CHANGELOG.MD} and by checking the git
-commits.
-
-\subsection{Changes in 0.3}
-
-In this version I improved the handling of alternative and actual text. See
-section~\ref{sec:alt}. This change meant that the package relies on the
-module \texttt{l3str-convert}.
-
-I no longer try to (pdf-)escape the tag names: it is a bit unclear how to
-do it at best with luatex. This will perhaps later change again.
-
-\subsection{Changes in 0.5}
-
-I added code to handle attributes and attribute classes, see
-section~\ref{sec:attributes} and corrected a small number of code errors.
-
-I added code to add \enquote{real} space glyphs to the \PDF{}, see section
-\ref{sec:spacechars}.
-
-\subsection{Changes in 0.6}
-
-\textbf{Breaking change!} The attributes used in luamode to mark the
-MC-chunks are no longer set globally. I thought that global attributes
-would make it easier to tag, but it only leads to problem when e.g. header
-and footer are inserted. So from this version on the attributes are set
-locally and the effect of a \verb+\tagmcbegin+ ends with the current group.
-This means that in some cases more \verb+\tagmcbegin+ are needed and this
-affected some of the examples, e.g. the patching commands for sections with
-KOMA. On the other side it means that quite often one can omit the
-\verb+\tagmcend+ command.
-
-
-\subsection{Changes in version 0.61}
-
-\begin{itemize}
-\item internal code adaptions to expl3 changes.
-\item dropped the compresslevel key -- probably not needed.
-\end{itemize}
-
-
-\subsection{Changes in version 0.8}
-
-\begin{itemize}
-\item As a first step to include the code proper in the \LaTeX\ kernel
- the module name has changed from \texttt{uftag} to \texttt{tag}. The
- commands starting with |\uftag| will stay valid for some time but
- then be deprecated.
-
-\item \textbf{Breaking change!} The argument of \texttt{newattribute}
- option should no longer add the dictionary bracket \verb+<<..>>+,
- they are added by the code.
-
-
-\item \textbf{Breaking change!} The package now requires the new PDF
- management as provided for now by the package
- \pkg{pdfmanagement-testphase}. \pkg{pdfmanagement-testphase},
- prepares the ground for better support for tagged PDF in \LaTeX{}. It
- is part of a larger project to automatically generate tagged PDF
- \url{https://www.latex-project.org/news/2020/11/30/tagged-pdf-FS-study/}
-
-\item Support to add associated files to structures has been added with
- new keys \texttt{AF}, \texttt{AFinline} and \texttt{AFinline-o}.
-
-\item \textbf{Breaking change!} The support for other 8-bit input
- encodings has been removed. utf8 is now the required encoding.
-
-\item The keys |lang|, |ref| and |E| have been added for structures.
-
-\item The new hooks of LaTeX are used to tagged many paragraphs
- automatically. The small red numbers around paragraphs in the
- documentation show them in action. The main problem here is not to
- tag a paragraph, but to avoid to tag too many: paragraphs pop up in
- many places.
-\end{itemize}
-
-\subsection{Changes in version 0.81}
-
-\begin{itemize}
-\item Hook code to tag links (URI and GoTo type) have been added. So
- normally they should simply work if tagging is activated.
-
-\item Commands and keys to allow automatic paragraph tagging have been
- added. See section~\ref{sec:paratagging}. As can be seen in this
- documentation the code works quite good already, but one should be
- aware that \enquote{paragraphs} can appear in many places and
- sometimes there are even more paragraph begin than ends.
-
-\item A key to test if local or global setting of the mc-attributes in
- luamode is more sensible, see \ref{sec:global-local} for more
- details.
-
-\item New commands to store and reset mc-tags.
-
-\item PDF 2.0 namespaces are now supported.
-\end{itemize}
-
-\subsection{Changes in version 0.82}
-
-A command |\tag_if_active:TF| to test if tagging is active has been added.
-This allow external packages to write conditional code.
-
-The commands |\tag_struct_parent_int:| and |\tag_struct_insert_annot:nn|
-have been added. They allow to add annotations to the structure.
-
-
-\subsection{Changes in version 0.83}
-
-|\tag_finish_structure:| has been removed, it is no longer a public
-command.
-
-\subsection{Changes in version 0.90}
-
-\begin{itemize}
-\item Code has been cleaned up and better documented.
-
-\item \textbf{More engines supported} The generic mode of \pkg{tagpdf}
- now works (theoretically, it is not much tested) with all engines
- supported by the \PDF\ management. So compilations with Xe\LaTeX{} or
- with dvips should work. But it should be noted that these engines and
- backends don't support the |interspaceword| option. With Xe\LaTeX{}
- it is perhaps possible implement something with
- |\XeTeXinterchartoks|, but for the dvips route I don't see an option
- (apart from lots of manual macros everywhere).
-\item \textbf{MC-attributes are global again} In\sidenote{Breaking
- change!} version 0.6 the attributes used in luamode to mark the
- MC-chunks were no longer set globally. This avoided a number of
- problems with header and footer and background material, but further
- tests showed that it makes it difficult to correctly mark things like
- links which have to interrupt the current marking code---the
- attributes couldn't easily escape groups added by users. See
- section~\ref{sec:global-local} for more details.
-\item \textbf{key global-mc removed:} Due to the changes in the attribute
- keys this key is not longer needed.
-\item \textbf{key check-tags removed:} It doesn't fit. Checks are handled
- over the logging level.
-\item |\tagpdfget| has been removed, use the expl3 version if needed.
-\item The show commands |\showtagpdfmcdata|, |\showtagpdfattributes|,
- |\showtagstack| have been removed and replaced by a more flexible
- command |\ShowTagging|.
-\item The commands |\tagmcbegin| and |\tagmcend| no longer ignore
- following spaces or remove earlier one. While this is nice in some
- places, it also ate spaces in places where this wasn't expected. From
- now on both commands behave exactly like the expl3 versions.
-\item The lua-code to add real space glyphs has been separated from the
- tagging code. This means that |interwordspace| now works also if
- tagging is not active.
-\item The key |activate| has been added, it open the first structure, see
- below.
-\end{itemize}
-
-\subsection{Changes in version 0.92}
-
-\begin{itemize}
-\item support for page breaks in pdftex has been added, see
- section~\ref{sec:splitpara},
-
-
-\item header and footer are tagged as artifacts automatically, see
- section~\ref{sec:header-footer}.
-
-\item keys \texttt{alttext-o} and \texttt{actualtext-o} has been removed.
- \texttt{alttext} and \texttt{actualtext} will now expand once.
-
-\end{itemize}
-
-\subsection{Changes in version 0.93}
-
-\begin{itemize}
-\item Support for associated files in the root element (key
- \texttt{root-AF}) has been added. This allow e.g. to add a css-file
- which is be used if the \PDF\ is converted to html.
-
-\item First steps have been done to adapt the package to planed changes
- in \LaTeX{}: The command \cs{DocumentMetadata} will be added to the
- format and will take over the role of \cs{DeclareDocumentMetadata}
- from \pkg{pdfmanagement-testphase} and additionally will also load
- the pdf management code. This will simplify the documents as it will
- no longer be needed to load the package.
-
-\item The package has now support for \enquote{structure destinations}.
- This is a new type of destinations in \PDF~2.0. For pdftex and luatex
- this requires new binaries. They will be included in texlive 2022,
- miktex already has the new pdftex, the new luatex will probably
- follow soon.
-
-\item The commands \cs{tagpdfifluatexT}, \cs{tagpdfifluatexTF} has been
- removed \cs{tagpdfifpdftexT},
-
-\end{itemize}
-
-\subsection{Changes in version 0.94}
-
-In this version a small package, \pkg{tagpdf-base} has been added. It
-provides no-op versions of the main expl3 user commands for packages that
-want to support tagging but can't be sure if the \pkg{tagpdf} package has
-been loaded.
-
-\subsection{Changes in version 0.95}
-
-Small bug fixes.
-
-\subsection{Changes in version 0.96}
-
-\begin{itemize}
-\item The \texttt{alttext} key has been renamed to \texttt{alt}, the
- other key name exists as alias.
-
-\item The new command |\tag_struct_object_ref:n| allows to create the
- object reference of a structure.
-
-\item a new key \texttt{parent} has been added to allow structures to
- choose their parent structure.
-
-\item a new option \texttt{paratag} allows to change the tag name used
- for the automatically tagged paragraphs.
-
-\item the commands |\tag_start:|, |\tag_stop:|, |\tag_stop:n| and
- |\tag_start:n| allow to stop and start tagging (for example in trial
- typesetting).
-
-\item Small bug fixes.
-\end{itemize}
-
-\subsection{Changes in version 0.98}
-
-\begin{itemize}
-\item The declarations of tag namespaces have been externalized and are
- now read from files when \pkg{tagpdf} is loaded.
-
-\item The \PDF{} format (and some of the standards) declare various
- parent-child rules for structure tags. A first step to implement this
- rules and check if they are fullfilled have been done. More
- information can be found in section~\ref{sec:parent-child}.
-
-\item As a side effect of the new rule checking, the requirements for new
- tags have been tightened: Adding a new tag with add-new-tag now
- requires that the target role is defined. Unknown roles error.
-
-\item |\tagmcbegin| no longer requires that a tag is set, instead if will
- pick up the tag name from the surrounding structure.
-
-\item Structure destination are now created also with \PDF
- \textless\,2.0. They shouldn't harm and can improve the html export.
-
-\end{itemize}
-
-\subsection{Changes in version 0.98a}
-Small bug fixes in code and documentation.
-
-\subsection{Changes in version 0.98b}
-The main change is from now on every structure has an ID and an IDtree is
-added. The ID of a structure can be retrieved with |\tag_get:n|
-see~\ref{sec:retrieve}.
-
-
-\subsection{Changes in version 0.98e}
-
-\begin{itemize}
-\item The main change is that the automatic paratagging uses now a
- two-level structure. This accompanies development in the LaTeX github
- inthe \texttt{latex-lab} package regarding the tagging of blocks like
- lists or verbatim. See~\ref{sec:paratagging} and also
- \texttt{latex-lab-block-tagging.dtx} for more background.
-
-\item The command |tag_struct_end:n| has been add to improve debugging.
-\end{itemize}
-
-\subsection{Changes in version 0.98k}
-
-The luamode has been adapted and now allows also the compilation with
-dvilualatex. By default it will insert specials for \texttt{dvips} into the
-dvi. But be aware that \texttt{dvips} can normally not be used as it can't
-handle open type fonts, and extended version would be needed which isn't in
-texlive yet. It is also possible to use \texttt{dvipdfmx} as backend (which
-already has support for open type fonts), for this you need to use
-\texttt{backend=dvipdfmx} in the \cs{DocumentMetadata} command. Real space
-chars will work, but are currently not taken from the current font. This
-will be improved in the next luaotfload version. The compilation with
-dvilualatex is not much tested yet.
-
-\subsection{Changes in version 0.98l}
-
-In 2023 the primitives to write literal code into the pdf have been
-extended in all engines and now allow to delay the expansion of their
-argument to the shipout. This made it possible to greatly simplify and
-speed up the code used in generic mode to number the MC-chunks. In most
-cases building the structure should now need only two or three
-compilations. The new code requires a current pdfmanagement-testphase and
-is then used automatically if the new engines are detected.
\printbibliography[heading=bibintoc]
@@ -2670,8 +2514,8 @@ is then used automatically if the new engines are detected.
\section{Some remarks about the \PDF{} syntax}
-This is not meant as a full reference only as a background to make the
-examples and remarks easier to understand.
+This is not meant as a full reference only as a background to make the examples and remarks easier to understand.
+
\begin{description}
@@ -2784,29 +2628,12 @@ Dictionaries are enclosed by double angle brackets. They contain key-value pairs
- \item[(indirect) objects] These are enclosed by the keywords
- \texttt{obj} (which has two numbers as prefix arguments) and
- \texttt{endobj}. The first argument is the object number, the second
- a generation number -- if a \PDF{} is edited objects with a larger
- generation number can be added. As with pdflatex/lualatex the \PDF{}
- is always new we can safely assume that the number is always 0.
- Objects can be referenced in other places with the \texttt{R}
- operator. The content of an object can be all sort of things.
+ \item[(indirect) objects] These are enclosed by the keywords \texttt{obj} (which has two numbers as prefix arguments) and \texttt{endobj}. The first argument is the object number, the second a generation number -- if a \PDF{} is edited objects with a larger generation number can be added. As with pdflatex/lualatex the \PDF{} is always new we can safely assume that the number is always 0. Objects can be referenced in other places with the \texttt{R} operator. The content of an object can be all sort of things.
- \item[streams] A stream is a sequence of bytes. It can be long and is
- used for the real content of \PDF{}: text, fonts, content of
- graphics. A stream starts with a dictionary which at least sets the
- \texttt{/Length} name to the length of the stream followed by the
- stream content enclosed by the keywords \texttt{stream} and
- \texttt{endstream}.
+ \item[streams] A stream is a sequence of bytes. It can be long and is used for the real content of \PDF{}: text, fonts, content of graphics.
+ A stream starts with a dictionary which at least sets the \texttt{/Length} name to the length of the stream followed by the stream content enclosed by the keywords \texttt{stream} and \texttt{endstream}.
- Here an example of a stream, an object definition and reference. In the
- object 2 (a page object) the \texttt{/Contents} key references the
- object 3 and this then contains the text of the page in a stream.
- \texttt{Tf}, \texttt{Tm} and \texttt{TJ} are (postfix) operators, the
- first chooses the font with the name \texttt{/F15} at the size 10.9,
- the second displaces the reference point on the page and the third
- inserts the text.
+ Here an example of a stream, an object definition and reference. In the object 2 (a page object) the \texttt{/Contents} key references the object 3 and this then contains the text of the page in a stream. \texttt{Tf}, \texttt{Tm} and \texttt{TJ} are (postfix) operators, the first chooses the font with the name \texttt{/F15} at the size 10.9, the second displaces the reference point on the page and the third inserts the text.
\begin{taglstlisting}
% a page object (shortened)
@@ -2830,12 +2657,9 @@ Dictionaries are enclosed by double angle brackets. They contain key-value pairs
endobj
\end{taglstlisting}
- In such a stream the \texttt{BT}--\texttt{ET} pair encloses texts while
- drawing and graphics are outside of such pairs.
+ In such a stream the \texttt{BT}--\texttt{ET} pair encloses texts while drawing and graphics are outside of such pairs.
-\item[Number tree] This is a more complex data structure that is meant to
- index objects by numbers. In the core is an array with number-value
- pairs. A simple version of number tree which has the keys 0 and 3 is
+\item[Number tree] This is a more complex data structure that is meant to index objects by numbers. In the core is an array with number-value pairs. A simple version of number tree which has the keys 0 and 3 is
\begin{taglstlisting}
6 0 obj
@@ -2848,11 +2672,10 @@ Dictionaries are enclosed by double angle brackets. They contain key-value pairs
endobj
\end{taglstlisting}
-This maps 0 to an array and 2 to the object reference \texttt{21 0 R}.
-Number trees can be split over various nodes -- root, intermediate and
-leaf nodes. We will need such a tree for the \emph{parent tree}.
+This maps 0 to an array and 2 to the object reference \texttt{21 0 R}. Number trees can be split over various nodes -- root, intermediate and leaf nodes. We will need such a tree for the \emph{parent tree}.
\end{description}
\end{document}
+%http://msf.mathmlcloud.org/file_formats/8 %sample \PDF{} for math
diff --git a/macros/latex/contrib/tagpdf/tagpdfdocu-patches.sty b/macros/latex/contrib/tagpdf/tagpdfdocu-patches.sty
index d0b90609a9..c9d62205f5 100644
--- a/macros/latex/contrib/tagpdf/tagpdfdocu-patches.sty
+++ b/macros/latex/contrib/tagpdf/tagpdfdocu-patches.sty
@@ -1,5 +1,5 @@
%\RequirePackage[enable-debug]{expl3}[2018/06/14]
-\ProvidesExplPackage {tagpdfdocu-patches} {2023-11-17} {0.98p}
+\ProvidesExplPackage {tagpdfdocu-patches} {2023-11-19} {0.98q}
{patches/commands for the tagpdf documentation}
\RequirePackage{etoolbox,xpatch}
@@ -68,11 +68,10 @@
\endblockenv
}
-% ======== marginnote ==========
+ % ======== marginnote ==========
% TODO marginnote has a bug (a \par is missing) so it messes up tagging.
% but currently unneeded as we marked them up as artifacts anyway as they don't contain
% meaningful contents
-\renewcommand*{\mn@parboxrestore}{\tagpdfparaOff}%
\NewDocumentCommand\sidenote{m}
{
@@ -146,20 +145,8 @@
{bbox}{/O /Layout /BBox [0 0 100 100]}
}
-% ======= maketitle
-
-\renewcommand\maketitle{%
- \tagstructbegin{tag=Title}
- \begin{center}%
- \let\thanks\footnote
- \makeatletter
- \huge \@title \par
- \vskip .5em
- \@author \par
- \vskip 1em%
- \@date \par
- \end{center}%
- \tagstructend}
+
+%====== floats ========
\endinput