Doc for #1383

doc/latex/biblatex/CHANGES.md

@@ -1,3 +1,5 @@
+# RELEASE NOTES FOR VERSION 3.21
+- \DeclareExtradate can now be specified per-entrytype
 # RELEASE NOTES FOR VERSION 3.20
 - Added new option settings `minyearinit` and `minyearfull` for
   `uniquename`

doc/latex/biblatex/biblatex.tex

@@ -10001,9 +10001,9 @@ \subsubsection{Special Fields}
 \end{ltxexample}
 %
 Note that the \bibfield{date} field is split by the backend into \bibfield{year}, \bibfield{month} which are also valid fields in the default data model. In order to support legacy data which directly sets \bibfield{year} and/or \bibfield{month}, the specification <\bibfield{date}> in \cmd{DeclareLabeldate} will also match \bibfield{year} and \bibfield{month} fields, if present.
-The \bibfield{label*} fields may be customized globally or on a per-type basis. If the optional \prm{entrytype} argument is given, the specification applies to the respective entry type. If not, it is applied globally. The \prm{entrytype} argument may be a comma"=separated list of values. This command may only be used in the preamble. See also \secref{aut:bbx:fld:dat}.
+The \bibfield{label*} fields may be customised globally or on a per-type basis. If the optional \prm{entrytype} argument is given, the specification applies to the respective entry type. If not, it is applied globally. The \prm{entrytype} argument may be a comma"=separated list of values. This command may only be used in the preamble. See also \secref{aut:bbx:fld:dat}.
 
-\cmditem{DeclareExtradate}{specification}
+\cmditem{DeclareExtradate}[[entrytype, \dots]{specification}
 
 Defines which date information is used to construct the \bibfield{extradate} field. With the default setting for \cmd{DeclareExtradateContext}, this field (see \secref{aut:bbx:fld:lab}) is printed to disambiguate works by the same \bibfield{labelname} (usually the author) or \bibfield{labeltitle} (usually the main title) which occur in the same date scope. By default, the date scope is the year and so two works by the same author/title within the same year will have different \bibfield{extradate} values which are used to disambiguate the works in the bibliography in the usual manner seen in many authoryear type styles. The \prm{specification} is one or more \cmd{scope} specifications which can contain one or more \cmd{field} specifications. Within a \cmd{scope}, the existence of each \cmd{field} will be checked and if found, the first \cmd{field} is used and the rest are ignored. This allows a fallback in case certain fields are not available in all entries. All \cmd{scope}s are used to track information and \cmd{scope}s should be specified in decreasing order of generality (e.g. year then month then day etc) The default definition is:
 
@@ -10116,7 +10116,7 @@ \subsubsection{Special Fields}
 Doe 2001b
 \end{lstlisting}
 %
-This command may only be used in the preamble.
+If the optional \prm{entrytype} argument is given, the specification applies to the respective entry types. If not, it is applied globally. The \prm{entrytype} argument may be a comma"=separated list of values. This command may only be used in the preamble.
 
 \cmditem{DeclareExtradateContext}[entrytype, \dots]{specification}
 
@@ -15032,6 +15032,9 @@ \section{Revision History}
 This revision history is a list of changes relevant to users of this package. Changes of a more technical nature which do not affect the user interface or the behavior of the package are not included in the list. More technical details are to be found in the \file{CHANGES.md} file. The numbers on the right indicate the relevant section of this manual.
 
 \begin{changelog}
+\begin{release}{3.21}{2024}
+\item \cmd{DeclareExtradate} can now be specified per-entrytype\see{aut:ctm:fld}
+\end{release}
 \begin{release}{3.20}{2024-03-22}
 \item Added new \opt{uniquename} options \see{use:opt:pre:int}
 \item Added default full date sorting templates\see{use:opt:pre}