summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2022-05-31 19:43:45 +0000
committerKarl Berry <karl@freefriends.org>2022-05-31 19:43:45 +0000
commit0b490f871a5cea8ad4f6c5e52a6374b96ec76fad (patch)
tree4c1505240bcda5a9d86a71ad79c38d67b14dcf36
parent7632b2ad78b2932f3d6e1bad03376a4364941e43 (diff)
multifootnote (31may22)
git-svn-id: svn://tug.org/texlive/trunk@63456 c570f23f-e606-0410-a88d-b1316a301751
-rw-r--r--Master/texmf-dist/doc/latex/multifootnote/LICENSE416
-rw-r--r--Master/texmf-dist/doc/latex/multifootnote/README.md11
-rw-r--r--Master/texmf-dist/doc/latex/multifootnote/multifootnote-doc.pdfbin0 -> 94268 bytes
-rw-r--r--Master/texmf-dist/doc/latex/multifootnote/multifootnote-doc.tex256
-rw-r--r--Master/texmf-dist/tex/latex/multifootnote/multifootnote.sty185
-rwxr-xr-xMaster/tlpkg/bin/tlpkg-ctan-check2
-rw-r--r--Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc1
-rw-r--r--Master/tlpkg/tlpsrc/multifootnote.tlpsrc0
8 files changed, 870 insertions, 1 deletions
diff --git a/Master/texmf-dist/doc/latex/multifootnote/LICENSE b/Master/texmf-dist/doc/latex/multifootnote/LICENSE
new file mode 100644
index 00000000000..22443139013
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/multifootnote/LICENSE
@@ -0,0 +1,416 @@
+The LaTeX Project Public License
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+
+LPPL Version 1.3c 2008-05-04
+
+Copyright 1999 2002-2008 LaTeX3 Project
+ Everyone is allowed to distribute verbatim copies of this
+ license document, but modification of it is not allowed.
+
+
+PREAMBLE
+========
+
+The LaTeX Project Public License (LPPL) is the primary license under
+which the LaTeX kernel and the base LaTeX packages are distributed.
+
+You may use this license for any work of which you hold the copyright
+and which you wish to distribute. This license may be particularly
+suitable if your work is TeX-related (such as a LaTeX package), but
+it is written in such a way that you can use it even if your work is
+unrelated to TeX.
+
+The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+below, gives instructions, examples, and recommendations for authors
+who are considering distributing their works under this license.
+
+This license gives conditions under which a work may be distributed
+and modified, as well as conditions under which modified versions of
+that work may be distributed.
+
+We, the LaTeX3 Project, believe that the conditions below give you
+the freedom to make and distribute modified versions of your work
+that conform with whatever technical specifications you wish while
+maintaining the availability, integrity, and reliability of
+that work. If you do not see how to achieve your goal while
+meeting these conditions, then read the document `cfgguide.tex'
+and `modguide.tex' in the base LaTeX distribution for suggestions.
+
+
+DEFINITIONS
+===========
+
+In this license document the following terms are used:
+
+ `Work'
+ Any work being distributed under this License.
+
+ `Derived Work'
+ Any work that under any applicable law is derived from the Work.
+
+ `Modification'
+ Any procedure that produces a Derived Work under any applicable
+ law -- for example, the production of a file containing an
+ original file associated with the Work or a significant portion of
+ such a file, either verbatim or with modifications and/or
+ translated into another language.
+
+ `Modify'
+ To apply any procedure that produces a Derived Work under any
+ applicable law.
+
+ `Distribution'
+ Making copies of the Work available from one person to another, in
+ whole or in part. Distribution includes (but is not limited to)
+ making any electronic components of the Work accessible by
+ file transfer protocols such as FTP or HTTP or by shared file
+ systems such as Sun's Network File System (NFS).
+
+ `Compiled Work'
+ A version of the Work that has been processed into a form where it
+ is directly usable on a computer system. This processing may
+ include using installation facilities provided by the Work,
+ transformations of the Work, copying of components of the Work, or
+ other activities. Note that modification of any installation
+ facilities provided by the Work constitutes modification of the Work.
+
+ `Current Maintainer'
+ A person or persons nominated as such within the Work. If there is
+ no such explicit nomination then it is the `Copyright Holder' under
+ any applicable law.
+
+ `Base Interpreter'
+ A program or process that is normally needed for running or
+ interpreting a part or the whole of the Work.
+
+ A Base Interpreter may depend on external components but these
+ are not considered part of the Base Interpreter provided that each
+ external component clearly identifies itself whenever it is used
+ interactively. Unless explicitly specified when applying the
+ license to the Work, the only applicable Base Interpreter is a
+ `LaTeX-Format' or in the case of files belonging to the
+ `LaTeX-format' a program implementing the `TeX language'.
+
+
+
+CONDITIONS ON DISTRIBUTION AND MODIFICATION
+===========================================
+
+1. Activities other than distribution and/or modification of the Work
+are not covered by this license; they are outside its scope. In
+particular, the act of running the Work is not restricted and no
+requirements are made concerning any offers of support for the Work.
+
+2. You may distribute a complete, unmodified copy of the Work as you
+received it. Distribution of only part of the Work is considered
+modification of the Work, and no right to distribute such a Derived
+Work may be assumed under the terms of this clause.
+
+3. You may distribute a Compiled Work that has been generated from a
+complete, unmodified copy of the Work as distributed under Clause 2
+above, as long as that Compiled Work is distributed in such a way that
+the recipients may install the Compiled Work on their system exactly
+as it would have been installed if they generated a Compiled Work
+directly from the Work.
+
+4. If you are the Current Maintainer of the Work, you may, without
+restriction, modify the Work, thus creating a Derived Work. You may
+also distribute the Derived Work without restriction, including
+Compiled Works generated from the Derived Work. Derived Works
+distributed in this manner by the Current Maintainer are considered to
+be updated versions of the Work.
+
+5. If you are not the Current Maintainer of the Work, you may modify
+your copy of the Work, thus creating a Derived Work based on the Work,
+and compile this Derived Work, thus creating a Compiled Work based on
+the Derived Work.
+
+6. If you are not the Current Maintainer of the Work, you may
+distribute a Derived Work provided the following conditions are met
+for every component of the Work unless that component clearly states
+in the copyright notice that it is exempt from that condition. Only
+the Current Maintainer is allowed to add such statements of exemption
+to a component of the Work.
+
+ a. If a component of this Derived Work can be a direct replacement
+ for a component of the Work when that component is used with the
+ Base Interpreter, then, wherever this component of the Work
+ identifies itself to the user when used interactively with that
+ Base Interpreter, the replacement component of this Derived Work
+ clearly and unambiguously identifies itself as a modified version
+ of this component to the user when used interactively with that
+ Base Interpreter.
+
+ b. Every component of the Derived Work contains prominent notices
+ detailing the nature of the changes to that component, or a
+ prominent reference to another file that is distributed as part
+ of the Derived Work and that contains a complete and accurate log
+ of the changes.
+
+ c. No information in the Derived Work implies that any persons,
+ including (but not limited to) the authors of the original version
+ of the Work, provide any support, including (but not limited to)
+ the reporting and handling of errors, to recipients of the
+ Derived Work unless those persons have stated explicitly that
+ they do provide such support for the Derived Work.
+
+ d. You distribute at least one of the following with the Derived Work:
+
+ 1. A complete, unmodified copy of the Work;
+ if your distribution of a modified component is made by
+ offering access to copy the modified component from a
+ designated place, then offering equivalent access to copy
+ the Work from the same or some similar place meets this
+ condition, even though third parties are not compelled to
+ copy the Work along with the modified component;
+
+ 2. Information that is sufficient to obtain a complete,
+ unmodified copy of the Work.
+
+7. If you are not the Current Maintainer of the Work, you may
+distribute a Compiled Work generated from a Derived Work, as long as
+the Derived Work is distributed to all recipients of the Compiled
+Work, and as long as the conditions of Clause 6, above, are met with
+regard to the Derived Work.
+
+8. The conditions above are not intended to prohibit, and hence do not
+apply to, the modification, by any method, of any component so that it
+becomes identical to an updated version of that component of the Work as
+it is distributed by the Current Maintainer under Clause 4, above.
+
+9. Distribution of the Work or any Derived Work in an alternative
+format, where the Work or that Derived Work (in whole or in part) is
+then produced by applying some process to that format, does not relax or
+nullify any sections of this license as they pertain to the results of
+applying that process.
+
+10. a. A Derived Work may be distributed under a different license
+ provided that license itself honors the conditions listed in
+ Clause 6 above, in regard to the Work, though it does not have
+ to honor the rest of the conditions in this license.
+
+ b. If a Derived Work is distributed under a different license, that
+ Derived Work must provide sufficient documentation as part of
+ itself to allow each recipient of that Derived Work to honor the
+ restrictions in Clause 6 above, concerning changes from the Work.
+
+11. This license places no restrictions on works that are unrelated to
+the Work, nor does this license place any restrictions on aggregating
+such works with the Work by any means.
+
+12. Nothing in this license is intended to, or may be used to, prevent
+complete compliance by all parties with all applicable laws.
+
+
+NO WARRANTY
+===========
+
+There is no warranty for the Work. Except when otherwise stated in
+writing, the Copyright Holder provides the Work `as is', without
+warranty of any kind, either expressed or implied, including, but not
+limited to, the implied warranties of merchantability and fitness for a
+particular purpose. The entire risk as to the quality and performance
+of the Work is with you. Should the Work prove defective, you assume
+the cost of all necessary servicing, repair, or correction.
+
+In no event unless required by applicable law or agreed to in writing
+will The Copyright Holder, or any author named in the components of the
+Work, or any other party who may distribute and/or modify the Work as
+permitted above, be liable to you for damages, including any general,
+special, incidental or consequential damages arising out of any use of
+the Work or out of inability to use the Work (including, but not limited
+to, loss of data, data being rendered inaccurate, or losses sustained by
+anyone as a result of any failure of the Work to operate with any other
+programs), even if the Copyright Holder or said author or said other
+party has been advised of the possibility of such damages.
+
+
+MAINTENANCE OF THE WORK
+=======================
+
+The Work has the status `author-maintained' if the Copyright Holder
+explicitly and prominently states near the primary copyright notice in
+the Work that the Work can only be maintained by the Copyright Holder
+or simply that it is `author-maintained'.
+
+The Work has the status `maintained' if there is a Current Maintainer
+who has indicated in the Work that they are willing to receive error
+reports for the Work (for example, by supplying a valid e-mail
+address). It is not required for the Current Maintainer to acknowledge
+or act upon these error reports.
+
+The Work changes from status `maintained' to `unmaintained' if there
+is no Current Maintainer, or the person stated to be Current
+Maintainer of the work cannot be reached through the indicated means
+of communication for a period of six months, and there are no other
+significant signs of active maintenance.
+
+You can become the Current Maintainer of the Work by agreement with
+any existing Current Maintainer to take over this role.
+
+If the Work is unmaintained, you can become the Current Maintainer of
+the Work through the following steps:
+
+ 1. Make a reasonable attempt to trace the Current Maintainer (and
+ the Copyright Holder, if the two differ) through the means of
+ an Internet or similar search.
+
+ 2. If this search is successful, then enquire whether the Work
+ is still maintained.
+
+ a. If it is being maintained, then ask the Current Maintainer
+ to update their communication data within one month.
+
+ b. If the search is unsuccessful or no action to resume active
+ maintenance is taken by the Current Maintainer, then announce
+ within the pertinent community your intention to take over
+ maintenance. (If the Work is a LaTeX work, this could be
+ done, for example, by posting to comp.text.tex.)
+
+ 3a. If the Current Maintainer is reachable and agrees to pass
+ maintenance of the Work to you, then this takes effect
+ immediately upon announcement.
+
+ b. If the Current Maintainer is not reachable and the Copyright
+ Holder agrees that maintenance of the Work be passed to you,
+ then this takes effect immediately upon announcement.
+
+ 4. If you make an `intention announcement' as described in 2b. above
+ and after three months your intention is challenged neither by
+ the Current Maintainer nor by the Copyright Holder nor by other
+ people, then you may arrange for the Work to be changed so as
+ to name you as the (new) Current Maintainer.
+
+ 5. If the previously unreachable Current Maintainer becomes
+ reachable once more within three months of a change completed
+ under the terms of 3b) or 4), then that Current Maintainer must
+ become or remain the Current Maintainer upon request provided
+ they then update their communication data within one month.
+
+A change in the Current Maintainer does not, of itself, alter the fact
+that the Work is distributed under the LPPL license.
+
+If you become the Current Maintainer of the Work, you should
+immediately provide, within the Work, a prominent and unambiguous
+statement of your status as Current Maintainer. You should also
+announce your new status to the same pertinent community as
+in 2b) above.
+
+
+WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+======================================================
+
+This section contains important instructions, examples, and
+recommendations for authors who are considering distributing their
+works under this license. These authors are addressed as `you' in
+this section.
+
+Choosing This License or Another License
+----------------------------------------
+
+If for any part of your work you want or need to use *distribution*
+conditions that differ significantly from those in this license, then
+do not refer to this license anywhere in your work but, instead,
+distribute your work under a different license. You may use the text
+of this license as a model for your own license, but your license
+should not refer to the LPPL or otherwise give the impression that
+your work is distributed under the LPPL.
+
+The document `modguide.tex' in the base LaTeX distribution explains
+the motivation behind the conditions of this license. It explains,
+for example, why distributing LaTeX under the GNU General Public
+License (GPL) was considered inappropriate. Even if your work is
+unrelated to LaTeX, the discussion in `modguide.tex' may still be
+relevant, and authors intending to distribute their works under any
+license are encouraged to read it.
+
+A Recommendation on Modification Without Distribution
+-----------------------------------------------------
+
+It is wise never to modify a component of the Work, even for your own
+personal use, without also meeting the above conditions for
+distributing the modified component. While you might intend that such
+modifications will never be distributed, often this will happen by
+accident -- you may forget that you have modified that component; or
+it may not occur to you when allowing others to access the modified
+version that you are thus distributing it and violating the conditions
+of this license in ways that could have legal implications and, worse,
+cause problems for the community. It is therefore usually in your
+best interest to keep your copy of the Work identical with the public
+one. Many works provide ways to control the behavior of that work
+without altering any of its licensed components.
+
+How to Use This License
+-----------------------
+
+To use this license, place in each of the components of your work both
+an explicit copyright notice including your name and the year the work
+was authored and/or last substantially modified. Include also a
+statement that the distribution and/or modification of that
+component is constrained by the conditions in this license.
+
+Here is an example of such a notice and statement:
+
+ %% pig.dtx
+ %% Copyright 2005 M. Y. Name
+ %
+ % 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.
+ %
+ % This work has the LPPL maintenance status `maintained'.
+ %
+ % The Current Maintainer of this work is M. Y. Name.
+ %
+ % This work consists of the files pig.dtx and pig.ins
+ % and the derived file pig.sty.
+
+Given such a notice and statement in a file, the conditions
+given in this license document would apply, with the `Work' referring
+to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+referring to any `LaTeX-Format', and both `Copyright Holder' and
+`Current Maintainer' referring to the person `M. Y. Name'.
+
+If you do not want the Maintenance section of LPPL to apply to your
+Work, change `maintained' above into `author-maintained'.
+However, we recommend that you use `maintained', as the Maintenance
+section was added in order to ensure that your Work remains useful to
+the community even when you can no longer maintain and support it
+yourself.
+
+Derived Works That Are Not Replacements
+---------------------------------------
+
+Several clauses of the LPPL specify means to provide reliability and
+stability for the user community. They therefore concern themselves
+with the case that a Derived Work is intended to be used as a
+(compatible or incompatible) replacement of the original Work. If
+this is not the case (e.g., if a few lines of code are reused for a
+completely different task), then clauses 6b and 6d shall not apply.
+
+
+Important Recommendations
+-------------------------
+
+ Defining What Constitutes the Work
+
+ The LPPL requires that distributions of the Work contain all the
+ files of the Work. It is therefore important that you provide a
+ way for the licensee to determine which files constitute the Work.
+ This could, for example, be achieved by explicitly listing all the
+ files of the Work near the copyright notice of each file or by
+ using a line such as:
+
+ % This work consists of all files listed in manifest.txt.
+
+ in that place. In the absence of an unequivocal list it might be
+ impossible for the licensee to determine what is considered by you
+ to comprise the Work and, in such a case, the licensee would be
+ entitled to make reasonable conjectures as to which files comprise
+ the Work.
+
diff --git a/Master/texmf-dist/doc/latex/multifootnote/README.md b/Master/texmf-dist/doc/latex/multifootnote/README.md
new file mode 100644
index 00000000000..bab1f56b21e
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/multifootnote/README.md
@@ -0,0 +1,11 @@
+<!-- Copyright (C) 2022 by Jinwen XU -->
+
+# `multifootnote` - Multiple numbers for the same footnote
+
+The package `multifootnote` provides several commands for generating footnotes with multiple numbers (or marks, if you prefer).
+
+*For more information, please refer to its documentation.*
+
+# License
+
+This work is released under the LaTeX Project Public License, v1.3c or later.
diff --git a/Master/texmf-dist/doc/latex/multifootnote/multifootnote-doc.pdf b/Master/texmf-dist/doc/latex/multifootnote/multifootnote-doc.pdf
new file mode 100644
index 00000000000..0a6410382f9
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/multifootnote/multifootnote-doc.pdf
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/multifootnote/multifootnote-doc.tex b/Master/texmf-dist/doc/latex/multifootnote/multifootnote-doc.tex
new file mode 100644
index 00000000000..c1c6516a953
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/multifootnote/multifootnote-doc.tex
@@ -0,0 +1,256 @@
+\documentclass[classical]{einfart}
+
+\usepackage{ProjLib}
+
+\usepackage[left indent]{multifootnote}
+
+%%================================
+%% For typesetting code
+%%================================
+\usepackage{listings}
+\usepackage{xcolor}
+\usepackage{setspace}
+\definecolor{code-main}{RGB}{70,130,180}
+\definecolor{code-expl3}{RGB}{240,50,60}
+\definecolor{code-option}{RGB}{40,110,20}
+\definecolor{code-keys}{RGB}{100,130,150}
+\definecolor{code-comment}{RGB}{20,120,80}
+\definecolor{code-background}{gray}{0.99}
+\lstset{
+ language = [LaTeX]TeX,
+ basicstyle = \ttfamily,
+ keywordstyle = \color{code-main},
+ commentstyle = \color{code-comment},
+ showstringspaces = false,
+ breaklines = true,
+ frame = lines,
+ backgroundcolor = \color{code-background},
+ flexiblecolumns = true,
+ escapeinside = {(*}{*)},
+ alsoletter = {_,:},
+ % numbers = left,
+ % firstnumber = last,
+ numberstyle = \scriptsize\ttfamily,
+ stepnumber = 1,
+ numbersep = 5pt,
+}
+\newcommand{\meta}[1]{$\langle${\normalfont\itshape#1}$\rangle$}
+\lstset{% LaTeX2 commands
+ classoffset = 0,
+ texcsstyle =* \color{code-main},
+ moretexcs =
+ {
+ multifootnotetext,
+ multifootnotemark,
+ multifootnotetag,
+ multifootnotetagtext,
+ multifootnote,
+ footnotenumber,
+ footnotetag,
+ }
+}
+\lstset{% LaTeX3 commands
+ classoffset = 1,
+ texcsstyle =* \color{code-expl3},
+ moretexcs =
+ {
+ }
+}
+\lstnewenvironment{code}{\setstretch{1.05}\LocallyStopLineNumbers}{\ResumeLineNumbers\vspace{-.3\baselineskip}\vspace{-.5\parskip}}
+\lstnewenvironment{code*}{\setstretch{1.05}\lstset{numbers=left}\LocallyStopLineNumbers}{\ResumeLineNumbers\vspace{-.3\baselineskip}\vspace{-.5\parskip}}
+
+\newcommand{\packageoption}[1]{\texttt{\textcolor{code-option}{#1}}}
+\newcommand{\commandoption}[1]{\texttt{\textcolor{code-keys}{#1}}}
+
+%%================================
+%% tip
+%%================================
+\usepackage[many]{tcolorbox}
+\newenvironment{tip}[1][Tip]
+ {%
+ \LocallyStopLineNumbers%
+ \begin{tcolorbox}[breakable,
+ enhanced,
+ width = \textwidth,
+ colback = paper, colbacktitle = paper,
+ colframe = gray!50, boxrule=0.2mm,
+ coltitle = black,
+ fonttitle = \sffamily,
+ attach boxed title to top left = {yshift=-\tcboxedtitleheight/2, xshift=.5cm},
+ boxed title style = {boxrule=0pt, colframe=paper},
+ before skip = 3mm,
+ after skip = 3mm,
+ top = 2.5mm,
+ bottom = 1.5mm,
+ title={\scshape\sffamily #1}]%
+ }
+ {%
+ \end{tcolorbox}%
+ \ResumeLineNumbers%
+ }
+
+
+\newcommand{\multifootnotepackage}{{\normalfont\textsf{multifootnote}}}
+
+\begin{document}
+
+\def\PackageVersion{2022/05/31}
+
+\title{\multifootnotepackage{}\\\smallskip\itshape Multiple numbers for the same footnote}
+\author{Jinwen XU}
+\thanks{Corresponding to: \texttt{\multifootnotepackage{} \PackageVersion}}
+\date{\TheDate{\PackageVersion}[only-year-month], in Paris}
+
+\maketitle
+
+\begin{abstract}
+ \raggedleft
+ The package \multifootnotepackage{} provides two groups of commands for \\generating footnotes with multiple numbers (or marks, if you prefer).
+\end{abstract}
+
+
+\vspace*{-.5\baselineskip}
+
+\section{How to load it}
+
+You can simply load the current package with:
+
+\begin{code}
+\usepackage[(*\meta{options}*)]{multifootnote}
+\end{code}
+
+\medskip
+It has the following options:
+\begin{itemize}[label=,leftmargin=1.25em,itemindent=-1.25em]
+ \item \packageoption{left align}
+ \begin{itemize}
+ \item Align the footnotes to the left.
+ \item Alternative names: \packageoption{left-align} \,$|$\, \packageoption{leftalign}
+ \end{itemize}
+ \item \packageoption{left indent} or \packageoption{left indent} \lstinline|=| \meta{length}
+ \begin{itemize}
+ \item Similar to \packageoption{left align}, but with an indentation \meta{length}, default to be \texttt{1.5em}.
+ \item Alternative names: \packageoption{left-indent} \,$|$\, \packageoption{leftindent}
+ \end{itemize}
+\end{itemize}
+
+\section{How to use it}
+
+Here are two approaches for producing a footnote with multiple numbers, and in either of them, there are two commands involved.
+
+\subsection{First approach}
+
+This approach is more or less traditional, with one command to produce the footnote mark and another the text.
+\begin{itemize}
+ \item \lstinline|\multifootnotemark[|\meta{label}\lstinline|]|
+ \begin{itemize}
+ \item This command is for producing the footnote marks.
+ \item \meta{label} cannot contain commas. However, colon \textquote{\texttt{:}} and semicolon \textquote{\texttt{;}} are allowed.
+ \item Alternative name: \lstinline|\footnotenumber[|\meta{label}\lstinline|]|.
+ \end{itemize}
+ \item \lstinline|\multifootnotetext[|\meta{list of labels}\lstinline|]{|\meta{footnote text}\lstinline|}|
+ \begin{itemize}
+ \item This command is for producing the footnote text.
+ \item \meta{list of labels} is a list of labels that you specified with \lstinline|\multifootnotemark[|\meta{label}\lstinline|]|, separated with commas, like this: \commandoption{fn1,fn2,fn3}.
+ \item It should not be too far away from the corresponding marks.
+ \item Alternative name: \lstinline|\multifootnote[|\meta{list of labels}\lstinline|]{|\meta{footnote text}\lstinline|}|.
+ \end{itemize}
+\end{itemize}
+
+\subsection{Second approach}
+
+This approach is considered more convenient, with one command to specify the \meta{tag} while printing the footnote mark, and another to print the footnote text for this group.
+\begin{itemize}
+ \item \lstinline|\multifootnotetag{|\meta{tag}\lstinline|}| or \lstinline|\multifootnotetag{|\meta{list of tags}\lstinline|}|
+ \begin{itemize}
+ \item This command is for producing the footnote marks.
+ \item \meta{tag} cannot contain commas. However, colon \textquote{\texttt{:}} and semicolon \textquote{\texttt{;}} are allowed.
+ \item \meta{list of tags} is a list of tags, separated with commas, like this: \commandoption{fntag1,fntag2,fntag3}.
+ \item Alternative name: \lstinline|\footnotetag{|\meta{tag}\lstinline|}| or \lstinline|\footnotetag{|\meta{list of tags}\lstinline|}|.
+ \end{itemize}
+ \item \lstinline|\multifootnotetagtext[|\meta{tag}\lstinline|]{|\meta{footnote text}\lstinline|}|
+ \begin{itemize}
+ \item This command is for producing the footnote text.
+ \item It should not be too far away from the corresponding marks.
+ \item Alternative name: \lstinline|\multifootnote[|\meta{tag}\lstinline|]{|\meta{footnote text}\lstinline|}|.
+ \end{itemize}
+\end{itemize}
+
+\begin{tip}
+ \lstinline|\multifootnote| appears in both approaches for producing footnote text: it shall be interpreted as \lstinline|\multifootnotetext| if the optional argument is a comma-separated list, and as \lstinline|\multifootnotetagtext| if not. See the examples below.
+\end{tip}
+
+\bigskip
+\begin{center}
+ \itshape
+ If you're feeling confused, don't worry. Let's now take a look at some examples.
+\end{center}
+
+
+\section{Examples}
+
+Here are two examples of usage, with the package option \textquote{\packageoption{left indent}} enabled.
+
+\subsection{The first approach}
+
+\medskip
+\begin{code}
+Lorem ipsum\footnotenumber[(*\commandoption{fn1}*)] dolor\footnotenumber[(*\commandoption{fn2}*)] sit amet\footnotenumber[(*\commandoption{fn3}*)], consectetur\footnotenumber[(*\commandoption{fn4}*)] adipiscing elit\footnotenumber[(*\commandoption{fn5}*)].
+\multifootnote[(*\commandoption{fn1,fn2,fn5}*)]{This is a footnote for demonstration.}
+\multifootnote[(*\commandoption{fn1,fn3,fn4}*)]{This is another footnote for demonstration.}
+\end{code}
+
+Result:
+
+\fbox{Lorem ipsum\footnotenumber[fn1] dolor\footnotenumber[fn2] sit amet\footnotenumber[fn3], consectetur\footnotenumber[fn4] adipiscing elit\footnotenumber[fn5].}
+\multifootnote[fn1,fn2,fn5]{This is a footnote for demonstration.}
+\multifootnote[fn1,fn3,fn4]{This is another footnote for demonstration.}
+
+\subsection{The second approach}
+
+\medskip
+\begin{code}
+Lorem ipsum\footnotetag{(*\commandoption{fntag1,fntag2}*)} dolor\footnotetag{(*\commandoption{fntag1}*)} sit amet\footnotetag{(*\commandoption{fntag2}*)}, consectetur\footnotetag{(*\commandoption{fntag2}*)} adipiscing elit\footnotetag{(*\commandoption{fntag1}*)}.
+\multifootnote[(*\commandoption{fntag1}*)]{This is a footnote for demonstration.}
+\multifootnote[(*\commandoption{fntag2}*)]{This is another footnote for demonstration.}
+\end{code}
+
+Result:
+
+\fbox{Lorem ipsum\footnotetag{fntag1,fntag2} dolor\footnotetag{fntag1} sit amet\footnotetag{fntag2}, consectetur\footnotetag{fntag2} adipiscing elit\footnotetag{fntag1}.}
+\multifootnote[fntag1]{This is a footnote for demonstration.}
+\multifootnote[fntag2]{This is another footnote for demonstration.}
+
+\begin{tip}
+ The second approach is more recommended, as it involves fewer labels, and you shall not need to worry about the order of footnote marks in \lstinline|\multifootnote|.
+\end{tip}
+
+\begin{tip}[Attention]
+ Notice that in the first approach, \meta{label} appears as an optional argument of \lstinline|\footnotenumber[|\meta{label}\lstinline|]| (thus square brackets); while in the second approach, \meta{tag} is a mandatory argument of \lstinline|\footnotetag{|\meta{tag}\lstinline|}| (thus curly brackets).
+\end{tip}
+
+
+\bigskip
+\section{Acknowledgement}
+
+This package arises from a question (\href{https://tex.stackexchange.com/q/645330}{\texttt{645330}}) on \texttt{TeX.StackExchange}. The author thanks user \href{https://tex.stackexchange.com/users/270985}{\textsf{@Bolzano}} for bringing up the question of producing such footnotes.
+
+The author thanks \href{https://tex.stackexchange.com/users/2388}{\textsf{Ulrike Fischer}} for the code for fixing the broken hyperlinks generated by the first approach, and user \href{https://tex.stackexchange.com/users/73317}{\textsf{@frougon}} for his kind and helpful suggestions and comments.
+
+The author also wishes to thank user \href{https://tex.stackexchange.com/users/213149}{\textsf{@antshar}} for proposing the second approach. The code is surprisingly simple but works just as fine as that of the first approach.
+
+\section{Known issues}
+
+\begin{itemize}
+ % \item When package \textsf{hyperref} is loaded, hyperlinks to those footnotes generated by the commands here cannot point to the correct place.
+ \item \multifootnotepackage{} is not compatible with the package \textsf{footnotebackref}.
+\end{itemize}
+
+\medskip
+If you run into any issue or have ideas for improvement, feel free to discuss on:
+\begin{center}
+ \url{https://github.com/Jinwen-XU/multifootnote/issues}
+\end{center}
+or email me via \href{mailto:ProjLib@outlook.com}{\texttt{ProjLib@outlook.com}}.
+
+\end{document}
diff --git a/Master/texmf-dist/tex/latex/multifootnote/multifootnote.sty b/Master/texmf-dist/tex/latex/multifootnote/multifootnote.sty
new file mode 100644
index 00000000000..2c8d5e45ae1
--- /dev/null
+++ b/Master/texmf-dist/tex/latex/multifootnote/multifootnote.sty
@@ -0,0 +1,185 @@
+%%
+%% Copyright (C) 2022 by Jinwen XU
+%% ------------------------------------
+%%
+%% This file may be distributed and/or modified under the conditions of
+%% the LaTeX Project Public License, either version 1.3c 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
+%%
+\NeedsTeXFormat{LaTeX2e}[2020-10-01]
+\RequirePackage{l3keys2e}
+\ProvidesExplPackage
+ {multifootnote}
+ {2022/05/31} {}
+ {Multiple numbers for the same footnote}
+
+\msg_new:nnn { multifootnote }
+ { non-compatible-package }
+ { "multifootnote" ~ is ~ not ~ compatible ~ with ~ the ~ package ~ "#1". }
+
+\hook_gput_code:nnn { begindocument/before } { multifootnote }
+ {
+ \@ifpackageloaded { footnotebackref }
+ {
+ \msg_warning:nnn { multifootnote } { non-compatible-package } { footnotebackref }
+ } {}
+ }
+
+\dim_new:N \l_multifootnote_space_after_comma_dim
+\dim_set:Nn \l_multifootnote_space_after_comma_dim { 0.2ex }
+
+\bool_new:N \l__multifootnote_left_indent_bool
+\bool_set_false:N \l__multifootnote_left_indent_bool
+\dim_new:N \l__multifootnote_left_indent_dim
+
+\keys_define:nn { multifootnote }
+ {
+ , left-align .bool_set:N = \l__multifootnote_left_align_bool
+ , left-align .initial:n = { false }
+ , left~align .bool_set:N = \l__multifootnote_left_align_bool
+ , left align .bool_set:N = \l__multifootnote_left_align_bool
+ , left-indent .code:n = {
+ \bool_set_true:N \l__multifootnote_left_indent_bool
+ \dim_set:Nn \l__multifootnote_left_indent_dim { #1 }
+ }
+ , left-indent .default:n = { 1.5em }
+ , left~indent .code:n = {
+ \bool_set_true:N \l__multifootnote_left_indent_bool
+ \dim_set:Nn \l__multifootnote_left_indent_dim { #1 }
+ }
+ , left~indent .default:n = { 1.5em }
+ , left indent .code:n = {
+ \bool_set_true:N \l__multifootnote_left_indent_bool
+ \dim_set:Nn \l__multifootnote_left_indent_dim { #1 }
+ }
+ , left indent .default:n = { 1.5em }
+ , unknown .code:n = {}
+ }
+\ProcessKeysOptions { multifootnote }
+
+\cs_new_protected:Nn \multifootnote_make_footnote_left_align:n
+ {
+ \renewcommand { \@makefntext } [1]
+ {
+ \skip_horizontal:n { #1 }
+ \tl_if_blank:eF { \text_expand:n { \@thefnmark } }
+ {
+ \@makefnmark
+ \nobreakspace
+ }
+ ##1
+ }
+ }
+
+\bool_if:NT \l__multifootnote_left_align_bool
+ {
+ \multifootnote_make_footnote_left_align:n { 0pt }
+ }
+\bool_if:NT \l__multifootnote_left_indent_bool
+ {
+ \multifootnote_make_footnote_left_align:n { \l__multifootnote_left_indent_dim }
+ }
+
+% First approach
+\NewDocumentCommand \multifootnotemark { O{} }
+ {
+ \footnotemark
+ \group_begin:
+ \tl_if_blank:nF { #1 }
+ {
+ \addtocounter { footnote } { -1 }
+ \refstepcounter { footnote }
+ \@ifpackageloaded { hyperref }
+ {
+ \cs_gset_eq:NN \@currentHref \Hy@footnote@currentHref
+ } {}
+ \label { #1 }
+ }
+ \group_end:
+ }
+\NewCommandCopy \footnotenumber \multifootnotemark
+
+\NewDocumentCommand \multifootnotetext { O{} m }
+ {
+ \group_begin:
+ \clist_clear:N \l_tmpa_clist
+ \clist_clear:N \l_tmpb_clist
+ \tl_if_blank:nF { #1 }
+ {
+ \clist_map_inline:nn { #1 }
+ {
+ \@ifpackageloaded { hyperref }
+ {
+ \clist_put_right:Nn \l_tmpa_clist
+ { \ref*{ ##1 } }
+ \clist_put_right:Nn \l_tmpb_clist
+ { \Hy@raisedlink { \hypertarget { \getrefbykeydefault{##1}{anchor}{Doc-Start} } {} } }
+ }
+ {
+ \clist_put_right:Nn \l_tmpa_clist
+ { \ref { ##1 } }
+ }
+ }
+ \def \thefootnote { \clist_use:Nn \l_tmpa_clist { , \skip_horizontal:n { \l_multifootnote_space_after_comma_dim } } }
+ }
+ \@ifpackageloaded { hyperref }
+ {
+ \xdef \Hy@footnote@currentHref { x\Hy@footnote@currentHref }
+ } {}
+ \footnotetext { \clist_use:Nn \l_tmpb_clist {} \ignorespaces #2 }
+ \group_end:
+ }
+
+% Second approach
+\NewDocumentCommand \multifootnotetag { m }
+ {
+ \footnotemark
+ \group_begin:
+ \def \thefootnote {}
+ \footnotetext { \vspace { -\baselineskip } }
+ \group_end:
+ \clist_map_inline:nn { #1 }
+ {
+ \cs_if_exist:cTF { multifootnote-tag- ##1 }
+ {
+ \tl_gput_right:cx { multifootnote-tag- ##1 } { , \skip_horizontal:n { \l_multifootnote_space_after_comma_dim } \thefootnote }
+ }
+ {
+ \cs_gset:cpx { multifootnote-tag- ##1 } { \thefootnote }
+ }
+ }
+ }
+\NewCommandCopy \footnotetag \multifootnotetag
+
+\NewDocumentCommand \multifootnotetagtext { O{} m }
+ {
+ \group_begin:
+ \tl_if_blank:nTF { #1 }
+ {
+ \def \thefootnote { }
+ }
+ {
+ \def \thefootnote { \use:c { multifootnote-tag- #1 } }
+ }
+ \footnotetext { #2 }
+ \group_end:
+ }
+
+% The combined interface for producing footnote text
+\NewDocumentCommand \multifootnote { O{} m }
+ {
+ \str_if_in:nnTF { #1 } { , }
+ {
+ \multifootnotetext [ #1 ] { #2 }
+ }
+ {
+ \multifootnotetagtext [ #1 ] { #2 }
+ }
+ }
+
+\endinput
+%%
+%% End of file `multifootnote.sty'.
diff --git a/Master/tlpkg/bin/tlpkg-ctan-check b/Master/tlpkg/bin/tlpkg-ctan-check
index 2a2314781d6..ebab654b2e7 100755
--- a/Master/tlpkg/bin/tlpkg-ctan-check
+++ b/Master/tlpkg/bin/tlpkg-ctan-check
@@ -552,7 +552,7 @@ my @TLP_working = qw(
mucproc mugsthesis muling multenum
multiaudience multibbl multibib multibibliography
multicap multicolrule multidef multido multienv multiexpand
- multilang multiobjective multirow munich
+ multifootnote multilang multiobjective multirow munich
musical musicography musikui musixguit
musixtex musixtex-fonts musixtnt musuos muthesis
mversion mwcls mwe mweights mxedruli
diff --git a/Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc b/Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc
index be4a47979cd..c13376688e8 100644
--- a/Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc
+++ b/Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc
@@ -884,6 +884,7 @@ depend multicolrule
depend multidef
depend multienv
depend multiexpand
+depend multifootnote
depend multilang
depend multirow
depend mversion
diff --git a/Master/tlpkg/tlpsrc/multifootnote.tlpsrc b/Master/tlpkg/tlpsrc/multifootnote.tlpsrc
new file mode 100644
index 00000000000..e69de29bb2d
--- /dev/null
+++ b/Master/tlpkg/tlpsrc/multifootnote.tlpsrc