<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">% \iffalse meta-comment
%
%% File: ltmeta.dtx
%% Copyright (C) 2021-2025
%% Frank Mittelbach, The LaTeX Project
%
% It may be distributed and/or modified under the conditions of the
% LaTeX Project Public License (LPPL), either version 1.3c of this
% license or (at your option) any later version.  The latest version
% of this license is in the file
%
%    https://www.latex-project.org/lppl.txt
%
%
%%% From File: ltmeta.dtx
%&lt;*driver&gt;
% \fi
\ProvidesFile{ltmeta.dtx}
             [2025/03/01 v1.0d LaTeX Kernel (Document Metadata)]
% \iffalse
%
\documentclass{l3doc}
\GetFileInfo{ltmeta.dtx}

\EnableCrossrefs
\CodelineIndex
\begin{document}
  \DocInput{ltmeta.dtx}
\end{document}
%&lt;/driver&gt;
%
% \fi
%
% \providecommand\hook[1]{\texttt{#1}}
% \providecommand\env[1]{\texttt{#1}}
%
%
%
% \title{The \texttt{ltmeta.dtx} code\thanks{This file has version
%    \fileversion\ dated \filedate, \copyright\ \LaTeX\
%    Project.}}
% \author{Frank Mittelbach}
%
% \maketitle
%
%
% \begin{abstract}
%    This code defines the \cs{DocumentMetadata} interface.
% \end{abstract}
%
% \tableofcontents
%
%
% \section{Introduction}
%
%
%    In the past there was no dedicated location to declare settings
%    concerning a document as a whole. Settings are placed somewhere
%    in the preamble or with the class options or even with some
%    package options.  For some settings this can be too late, for
%    example the pdf version can no longer be changed if a package has
%    used code which already opened the PDF.
%
%    \cs{DocumentMetadata} as a new command unifies such settings in
%    one place.  It must be used before \cs{documentclass} but can be
%    issued more than once there.
%
%    At the moment most of the code run by \cs{DocumentMetadata} is
%    external to the format and subject to change. This includes the
%    supported key/values.
%
%    For that reason all that happens right now in the format is to
%    look for suitable support files and if found, to redirect the
%    processing to them.
%
% \subsection{\cs{DocumentMetadata}}
%
% \begin{function}{\DocumentMetadata}
% \begin{syntax}
%  \cs{DocumentMetadata}\Arg{key-value list}
% \end{syntax}
% \end{function}
%
%
%
%    The keys defined for \cs{DocumentMetadata}
%    currently allow to set the PDF version, to set the PDF \texttt{/Lang},
%    to uncompress a PDF, to set the language and to declare a few PDF standards
%    and some color profiles.
%
%    \cs{DocumentMetadata} is also used to
%    activate the new PDF management code and it loads
%    a number of required files for the PDF management code.
%    As this forces the loading of the backend files, a backend
%    which can't be detected automatically like |dvipdfmx|,
%    must be set in the first \cs{DocumentMetadata} call (if there is more than one).
%
%    The full set of keys currently supported is documented in \texttt{documentmetadata-support.pdf}
%    for now.
%
%
% \StopEventually{\setlength\IndexMin{200pt}  \PrintIndex  }
%
%
% \section{The Implementation}
%
%
%
%    \begin{macrocode}
%&lt;*2ekernel|latexrelease&gt;
%    \end{macrocode}
%    Not needed yet but \ldots
%    \begin{macrocode}
%\ExplSyntaxOn
%    \end{macrocode}
%
%    \begin{macrocode}
%&lt;latexrelease&gt;\NewModuleRelease{2022/06/01}{ltmeta}
%&lt;latexrelease&gt;                 {Document Metadata handling}
%    \end{macrocode}
%    We start by making the conditionals testing for the use of
%    \cs{DocumentMetadata} execute the the false branch. Then, inside
%    \cs{DocumentMetadata}, we change them to select the true branch.  
% \changes{v1.0d}{2025/03/01}{Provide T F variants of
%                             \cs{IfDocumentMetadataTF} (gh/1522)}
%    \begin{macrocode}
\let \IfDocumentMetadataTF \@secondoftwo
\let \IfDocumentMetadataT \@gobble
\let \IfDocumentMetadataF \@firstofone
\protected\def\DocumentMetadata{%
  \InputIfFileExists{documentmetadata-support.ltx}%
     {%
%    \end{macrocode}
%    Support for \cs{DocumentMetadata} is available, so change the conditionals.
%    \begin{macrocode}
       \let \IfDocumentMetadataTF \@firstoftwo
       \let \IfDocumentMetadataT  \@firstofone
       \let \IfDocumentMetadataF  \@gobble
     }%
%    \end{macrocode}
%    The above file is changing \cs{DocumentMetadata} to a suitable
%    definition (or so we hope) so that it can be safely used several times
%    in the premable.
%
%    If the file can't be found we say so and carry on without it.
%    \begin{macrocode}
     {%
       \@latex@error{No support files for
                    \noexpand\DocumentMetadata found}
         {Is the 'LaTeX-lab' bundle installed?%
         \MessageBreak
         Without it, the declaration is ignored.}%
%    \end{macrocode}
%    No point in trying this more than once if there are several calls
%    in the document.
%    \begin{macrocode}
      \let\DocumentMetadata\@gobble
     }%
  \DocumentMetadata
}
%    \end{macrocode}
%
%   To allow package and class author to support for document links
%   we provide also the new interface commands of the hyperref package
%   for the creation of targets.
% \changes{v1.0b}{2022/05/17}{Default definition for targets added}
% \changes{v1.0c}{2024/09/21}{Added tagging support}
%  \begin{macro}{\MakeLinkTarget}
%  \begin{macro}{\LinkTargetOn}
%  \begin{macro}{\LinkTargetOff}
%  \begin{macro}{\NextLinkTarget}
%    \begin{macrocode}
%&lt;latexrelease&gt;\IncludeInRelease{2024/11/01}%
%&lt;latexrelease&gt;                 {\MakeLinkTarget}{Record target name for tagging support}%
\ExplSyntaxOn
\int_new:N\g__kernel_target_int
\NewDocumentCommand\MakeLinkTarget{sO{}m}{%
  \ifvmode
    \special{}%
  \else
    \@savsf\spacefactor
    \smash{}%
    \spacefactor\@savsf
  \fi
  \IfBooleanTF {#1}
   {
     \tl_gset:Ne \@currentHref {#3}
   }
   {
     \int_gincr:N\g__kernel_target_int
     \tl_gset:Ne \@currentHref {target*.\int_use:N\g__kernel_target_int}
   }
  \UseTaggingSocket{recordtarget} 
   }
\ExplSyntaxOff   
%&lt;latexrelease&gt;\EndIncludeInRelease
%&lt;latexrelease&gt;\IncludeInRelease{2022/06/01}%
%&lt;latexrelease&gt;                 {\MakeLinkTarget}{Record target name for tagging support}%
%&lt;latexrelease&gt;\NewDocumentCommand\MakeLinkTarget{sO{}m}{%
%&lt;latexrelease&gt;  \ifvmode
%&lt;latexrelease&gt;    \special{}%
%&lt;latexrelease&gt;  \else
%&lt;latexrelease&gt;    \@savsf\spacefactor
%&lt;latexrelease&gt;    \smash{}%
%&lt;latexrelease&gt;    \spacefactor\@savsf
%&lt;latexrelease&gt;  \fi}
%&lt;latexrelease&gt;\EndIncludeInRelease
\NewDocumentCommand\LinkTargetOn{}{}
\NewDocumentCommand\LinkTargetOff{}{}
\NewDocumentCommand\NextLinkTarget{m}{}
%    \end{macrocode}
%  \end{macro}
%  \end{macro}
%  \end{macro}
%  \end{macro}
%
%
%    We do not undo \cs{MakeLinkTarget} and friends if we roll back, in
%    case they are used in packages that themselves do not offer
%    rollback. This way a roll forward adds them, but the dummies remain
%    if you roll back and you don't get missing csname errors if they
%    are used.
%    \begin{macrocode}
%&lt;latexrelease&gt;\IncludeInRelease{0000/00/00}{ltmeta}%
%&lt;latexrelease&gt;                 {Undo Document Metadata handling}
%&lt;latexrelease&gt;
%&lt;latexrelease&gt;\let\DocumentMetadata\@undefined
%&lt;latexrelease&gt;
%&lt;latexrelease&gt;\EndModuleRelease
%    \end{macrocode}
%    Again for the future \ldots
%    \begin{macrocode}
%\ExplSyntaxOff
%    \end{macrocode}
%    \begin{macrocode}
%&lt;/2ekernel|latexrelease&gt;
%    \end{macrocode}
%
%    Restore module prefix (if any):
%    \begin{macrocode}
%&lt;@@=&gt;
%    \end{macrocode}
%
%
%
%
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\endinput
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
</pre></body></html>