diff options
Diffstat (limited to 'Master/texmf-dist/doc/latex/biblatex/biblatex.tex')
-rw-r--r-- | Master/texmf-dist/doc/latex/biblatex/biblatex.tex | 206 |
1 files changed, 144 insertions, 62 deletions
diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex index fd1ddb81dd8..8d01c37d4ec 100644 --- a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex +++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex @@ -58,15 +58,15 @@ title={The \biblatex Package}, subtitle={Programmable Bibliographies and Citations}, url={\biblatexhome}, - author={Philipp Lehman \\(with Philip Kime, Audrey Boruvka and Joseph Wright)}, + author={Philipp Lehman \\(with Philip Kime, Moritz Wemheuer, Audrey Boruvka and Joseph Wright)}, email={}, - revision={3.10}, + revision={3.11}, date={\today}} \hypersetup{% pdftitle={The \biblatex Package}, pdfsubject={Programmable Bibliographies and Citations}, - pdfauthor={Philipp Lehman, Philip Kime}, + pdfauthor={Philipp Lehman, Philip Kime, Moritz Wemheuer}, pdfkeywords={tex, latex, bibtex, bibliography, references, citation}} % tables @@ -168,7 +168,7 @@ This package provides advanced bibliographic facilities for use with \latex. The \subsection{License} -Copyright \textcopyright\ 2006--2012 Philipp Lehman, 2012--2017 Philip Kime, Audrey Boruvka, Joseph Wright. Permission is granted to copy, distribute and\slash or modify this software under the terms of the \lppl, version 1.3.\fnurl{http://www.latex-project.org/lppl.txt} +Copyright \textcopyright\ 2006--2012 Philipp Lehman, 2012--2017 Philip Kime, Audrey Boruvka, Joseph Wright, 2018- Philip Kime and Moritz Wemheuer. Permission is granted to copy, distribute and\slash or modify this software under the terms of the \lppl, version 1.3.\fnurl{http://www.latex-project.org/lppl.txt} \subsection{Feedback} \label{int:feb} @@ -192,7 +192,8 @@ Denis Bitouzé (French); Apostolos Syropoulos, Prokopis (Greek); Baldur Kristinsson (Icelandic); Enrico Gregorio, Andrea Marchitelli (Italian); -Håkon Malmedal (Norwegian); +Rihards Skuja (Latvian); +Håkon Malmedal, Hans Fredrik Nordhaug (Norwegian); Anastasia Kandulina, Yuriy Chernyshov (Polish); José Carlos Santos (Portuguese); Oleg Domanov (Russian); @@ -200,8 +201,7 @@ Martin Vrábel, Dávid Lupták (Slovak); Tea Tušar and Bogdan Filipič (Slovene); Ignacio Fernández Galván (Spanish); Per Starbäck, Carl-Gustav Werner, Filip Åsblom (Swedish); -Sergiy M. Ponomarenko (Ukrainian); -Hans Fredrik Nordhaug (Norwegian) +Sergiy M. Ponomarenko (Ukrainian). \subsection{Prerequisites} \label{int:pre} @@ -326,7 +326,7 @@ The \sty{natbib} package supports numeric and author"=year citation schemes, inc The \sty{splitbib} package provides support for bibliographies subdivided by topic. See \sty{bibtopic}. \item[titlesec] -The \sty{titlesec} package redefines user-level document division commands such as \cmd{chapter} or \cmd{section}. This approach is not compatible with internal command changes applied by the \biblatex \texttt{refsection} and \texttt{refsegment} option settings described in \secref{use:opt:pre:gen}. +The \sty{titlesec} package redefines user-level document division commands such as \cmd{chapter} or \cmd{section}. This approach is not compatible with internal command changes applied by the \biblatex \opt{refsection}, \opt{refsegment} and \opt{citereset} option settings described in \secref{use:opt:pre:gen}. \item[ucs] The \sty{ucs} package provides support for \utf encoded input. Either use \sty{inputenc}'s standard \file{utf8} module or a Unicode enabled engine such as \xetex or \luatex instead. @@ -357,6 +357,7 @@ compatibility matrix for the recent versions. \sffamily\bfseries\spotcolor Biber version & \sffamily\bfseries\spotcolor \biblatex\ version\\ \midrule +2.11 & 3.11\\ 2.10 & 3.10\\ 2.9 & 3.9\\ 2.8 & 3.8\\ @@ -574,7 +575,7 @@ A thesis written for an educational institution to satisfy the requirements for A work with an author and a title which has not been formally published, such as a manuscript or the script of a talk. Use the fields \bibfield{howpublished} and \bibfield{note} to supply additional information in free format, if applicable. \reqitem{author, title, year/date} -\optitem{subtitle, titleaddon, language, howpublished, note, location, isbn, date, month, year, addendum, pubstate, url, urldate} +\optitem{subtitle, titleaddon, type, eventtitle, eventtitleaddon, eventdate, venue, language, howpublished, note, location, isbn, date, month, year, addendum, pubstate, url, urldate} \typeitem{xdata} @@ -1170,7 +1171,7 @@ The gender of the author or the gender of the editor, if there is no author. The \begin{table} \tablesetup -\begin{tabularx}{\textwidth}{@{}p{80pt}@{}p{170pt}@{}X@{}} +\begin{tabularx}{\textwidth}{@{}p{90pt}@{}p{160pt}@{}X@{}} \toprule \multicolumn{1}{@{}H}{Language} & \multicolumn{1}{@{}H}{Region/Dialect} & @@ -1197,8 +1198,11 @@ German (new) & Germany & \opt{ngerman} \\ & Austria & \opt{naustrian} \\ & Switzerland & \opt{nswissgerman} \\ Greek & Greece & \opt{greek} \\ +Icelandic & Iceland & \opt{icelandic} \\ Italian & Italy & \opt{italian} \\ -Norwegian & Norway & \opt{norsk}, \opt{nynorsk} \\ +Latvian & Latvia & \opt{latvian} \\ +Norwegian (Bokmål) & Norway & \opt{norsk} \\ +Norwegian (Nynorsk) & Norway & \opt{nynorsk} \\ Polish & Poland & \opt{polish} \\ Portuguese & Brazil & \opt{brazil} \\ & Portugal & \opt{portuguese}, \opt{portuges} \\ @@ -1708,7 +1712,7 @@ The output of <circa>, uncertainty and era information in standard styles (or cu 0343-02-03 & 343-02-02 CE & with \opt{dateeraauto=400} and \opt{julian} \\ 1723\textasciitilde & circa 1723 & using \cmd{ifdatecirca} test\\ 1723? & 1723? & using \cmd{ifdateuncertain} test\\ -1723?\textasciitilde & circa 1723? & using \cmd{ifdateuncertain} and \cmd{ifdatecirca} tests\\ +1723\% & circa 1723? & using \cmd{ifdateuncertain} and \cmd{ifdatecirca} tests\\ 2004-22 & 2004 & also, \bibfield{season} is set to the localisation string <summer>\\ 2004-24 & 2004 & also, \bibfield{season} is set to the localisation string <winter>\\ \bottomrule @@ -2021,7 +2025,7 @@ Whether or not to sort the bibliography and the list of shorthands case"=sensiti This option corresponds to \biber's \opt{--sortupper} command-line option. If enabled, the bibliography is sorted in <uppercase before lowercase> order. Disabling this option means <lowercase before uppercase> order. -\optitem{sortlocale}{\opt{auto}, \prm{locale}} +\optitem[auto]{sortlocale}{\opt{auto}, \prm{locale}} This option sets the global sorting locale. Every sorting template inherits this locale if none is specified using the \prm{locale} option to \cmd{printbibliography}. Setting this to \opt{auto} requests that it be set to the \sty{babel}/\sty{polyglossia} main document language identifier, if these packages are used and \texttt{en\_US} otherwise. \biber will map \sty{babel}/\sty{polyglossia} language identifiers into sensible locale identifiers (see the \biber documentation). You can therefore specify either a normal locale identifier like \texttt{de\_DE\_phonebook}, \texttt{es\_ES} or one of the supported \sty{babel}/\sty{polyglossia} language identifiers if the mapping \biber makes of this is fine for you. @@ -2128,6 +2132,10 @@ This option controls the extra spacing between blocks, \ie larger segments of a The \cmd{newblockpunct} command may also be redefined directly to achieve different results, see \secref{use:fmt:fmt}. Also see \secref{aut:pct:new} for additional information. +\boolitem[false]{locallabelwidth} + +This option controls whether \cmd{printbibliography} uses a locally calculated value for \cmd{labelnumberwidth} and \cmd{labelalphawidth} or the global value calculated from all entries. The local value is calculated separately for each bibliography and takes into account only the entries displayed in that bibliography. This option is useful if there are several bibliographies with wildly varying label lengths in the same document. + \optitem[foot+end]{notetype}{\opt{foot+end}, \opt{footonly}, \opt{endonly}} This option controls the behavior of \cmd{mkbibfootnote}, \cmd{mkbibendnote}, and similar wrappers from \secref{aut:fmt:ich}. The possible choices are: @@ -2420,7 +2428,7 @@ Note that setting \kvopt{texencoding}{\prm{encoding}} will also affect the \opt{ \optitem[auto]{bibencoding}{\opt{auto}, \prm{encoding}} -Specifies the encoding of the \file{bib} files. This corresponds to \biber's \opt{--input-encoding} option. The following choices are available: +Specifies the encoding of the \file{bib} files. This option corresponds to \biber's \opt{--input-encoding} option. The following choices are available: \begin{valuelist} @@ -2634,7 +2642,7 @@ This option is also settable on a per-type basis. Table \ref{use:opt:tab1} summa \cmidrule(r){1-1}\cmidrule(r){2-2}\cmidrule(r){3-3} singletitle & \cmd{ifsingletitle} & labelname\\ uniquetitle & \cmd{ifuniquetitle} & labeltitle\\ -uniquebaretitle & \cmd{ifuniquebaretitle} & labeltitle when labelname is null\\ +uniquebaretitle & \cmd{ifuniquebaretitle} & labeltitle {\rmfamily when} labelname {\rmfamily is null}\\ uniquework & \cmd{ifuniquework} & labelname+labeltitle\\ \bottomrule \end{tabularx} @@ -2726,8 +2734,8 @@ labeldateparts & labelyear & extradate & labelname+\\ & labelendseason & & \\ & labeltimezone & & \\ & labelendtimezone & & \\ -labeltitle & \rmfamily{---} & extratitle & labelname+labeltitle\\ -labeltitleyear & \rmfamily{---} & extratitleyear & labeltitle+labelyear\\ +labeltitle & {\rmfamily ---} & extratitle & labelname+labeltitle\\ +labeltitleyear & {\rmfamily ---} & extratitleyear & labeltitle+labelyear\\ \bottomrule \end{tabularx} \caption{Disambiguation counters} @@ -3174,21 +3182,27 @@ To access the annotation information when formatting bibliography data, three ma \begin{ltxsyntax} -\cmditem{iffieldannotation}{annotation}{true}{false} +\cmditem{iffieldannotation}[field]{annotation}{true}{false} + +Executes \prm{true} if the data field \prm{field} has an annotation \prm{annotation} and false otherwise. If \prm{field} is not given, the current data field as indicated by \cmd{currentfield}, \cmd{currentlist} or \cmd{currentname} (see \secref{aut:bib:fmt}) is assumed. Of course, this is only possible if these commands are defined, that is, inside formatting directives. + +\cmditem{ifitemannotation}[field][item]{annotation}{true}{false} + +Executes \prm{true} if the item \prm{item} in the data field \prm{field} has an annotation \prm{annotation} and false otherwise. The optional argument \prm{field} can be inferred if not provided as with \cmd{iffieldannotation}. If \prm{item} is not given, the number of the item currently being processed as given by \cnt{listcount} is used. -Executes \prm{true} if the current data field has an annotation \prm{annotation} and false otherwise. +\cmditem{ifpartannotation}[field][item]{part}{annotation}{true}{false} -\cmditem{ifitemannotation}{annotation}{true}{false} +Executes \prm{true} if the part named \prm{part} in item \prm{item} in the data field \prm{field} has an annotation \prm{annotation} and false otherwise. The two optional arguments \prm{field} and \prm{item} can be inferred as in \cmd{ifitemannotation}. The parameter \prm{part} can never be inferred and is therefore a mandatory argument. -Executes \prm{true} if the current item in the current data field has an annotation \prm{annotation} and false otherwise. +Date fields are special and handled in a context where \cmd{currentfield} is not accessible. Thus there is a fourth command to access annotations for dates. -\cmditem{ifpartannotation}{part}{annotation}{true}{false} +\cmditem{ifdateannotation}{datetype}{annotation}{true}{false} -Executes \prm{true} if the part named \prm{part} in current item in the current data field has an annotation \prm{annotation} and false otherwise. +Executes \prm{true} if the date field \prm{datetype} has an annotation \prm{annotation} and false otherwise. The \prm{datetype} argument is mandatory, because it can not be inferred in most contexts where \cmd{ifdateannotation} will be used. \end{ltxsyntax} % -These macros are available in the same places as \cmd{currentfield}, \cmd{currentlist} and \cmd{currentname} (see \secref{aut:bib:fmt}), that is, inside formatting directives. They automatically determine the name of the current data field being processed and also the current \opt{listcount} value which determines the current item in list fields. Parts such as name parts need to be named explicitly. As an example of how to use the annotation information to solve the problem originally presented in this section, this could be used in the name formatting directives to put an asterisk after all family names annotated as «student»: +As an example of how to use the annotation information to solve the problem originally presented in this section, this could be used in the name formatting directives to put an asterisk after all family names annotated as «student»: \begin{lstlisting}[style=latex]{} \ifpartannotation{family}{student} @@ -3358,6 +3372,10 @@ This option applies to numerical citation\slash bibliography styles only and req This option applies to numerical citation\slash bibliography styles only and requires that the \opt{defernumbers} option from \secref{use:opt:pre:gen} be enabled globally. If enabled, \biblatex will not assign a numerical label to the entries in the respective bibliography. This is useful when mixing a numerical subbibliography with one or more subbibliographies using a different scheme (\eg author-title or author-year). +\boolitem[false]{locallabelwidth} + +Calculate \cmd{labelnumberwidth}, \cmd{labelalphawidth} and similar lengths locally for the present bibliography and not globally for all entries. See also \opt{labelnumberwidth} in \secref{use:opt:pre:gen}. + \end{optionlist*} \begin{ltxsyntax} @@ -3391,20 +3409,34 @@ A bibliography list differs from a normal bibliography in that the same bibliogr \begin{ltxsyntax} -\cmditem{printbiblist}[key=value, \dots]{$<$biblistname$>$} +\cmditem{printbiblist}[key=value, \dots]{biblistname} + +This command prints a bibliography list. It takes an optional argument, which is a list of options given in \keyval notation. Valid options are all options supported by \cmd{printbibliography} (\secref{use:bib:bib}) except \opt{resetnumbers} and \opt{omitnumbers}. Additionaly, the two options \opt{driver} and \opt{biblistfilter} are available. If there are any \env{refsection} environments in the document, the bibliography list will be local to these environments; see \secref{use:bib:sec} for details. By default, this command uses the heading \texttt{biblist}. See \secref{use:bib:hdg} for details. -This command prints a bibliography list. It takes an optional argument, which is a list of options given in \keyval notation. Valid options are all options supported by \cmd{printbibliography} (\secref{use:bib:bib}) except \opt{resetnumbers} and \opt{omitnumbers}. If there are any \env{refsection} environments in the document, the bibliography list will be local to these environments; see \secref{use:bib:sec} for details. By default, this command uses the heading \texttt{biblist}. See \secref{use:bib:hdg} for details. The \prm{biblistname} is a mandatory argument which names the bibliography list. This name is used to identify: \begin{itemize} \item The default bibliography driver used to print the list entries -\item A default filter declared with \cmd{DeclareBiblistFilter} (see \secref{aut:ctm:bibfilt}) used to filter the entries returned from \biber +\item A default bibliography list filter declared with \cmd{DeclareBiblistFilter} (see \secref{aut:ctm:bibfilt}) used to filter the entries returned from \biber \item A default check declared with \cmd{defbibcheck} (see \secref{use:bib:flt}) used to post-process the list entries \item The default bib environment to use \item The default sorting template to use \end{itemize} -In terms of sorting the list, the default is to sort use the sorting template named after the bibliography list (if it exists) and only then to fall back to the current context sorting template is this is not defined (see \secref{use:bib:context}). +The two additional options can be used to change some of the defaults set by the mandatory argument. + +\begin{optionlist*} +\valitem[\prm{biblistname}]{driver}{driver} + +Change the bibliography driver used to print the list entries. +% \prm{driver} must be a valid driver declared with \cmd{DeclareBibliographyDriver} (see \secref{aut:bbx:bbx}). + +\valitem[\prm{biblistname}]{biblistfilter}{biblistfilter} + +Change the bibliography list filter used to filter the entries. \prm{biblistfilter} must be a valid bibliography list filter defined with \cmd{DeclareBiblistFilter} (see \secref{aut:ctm:bibfilt}). +\end{optionlist*} + +In terms of sorting the list, the default is to sort using the sorting template named after the bibliography list (if it exists) and only then to fall back to the current context sorting template if this is not defined (see \secref{use:bib:context}). The most common bibliography list is a list of shorthand abbreviations for certain entries and so this has a convenience alias \cmd{printshorthands[\dots]} for backwards compatibility which is defined as: @@ -3477,7 +3509,7 @@ The \env{refsection} environment is used in the document body to mark a referenc \envitem{refsection}[resource, \dots] -The optional argument is a comma"=separated list of resources specific to the reference section. If the argument is omitted, the reference section will use the default resource list, as specified with \cmd{addbibresource} in the preamble. If the argument is provided, it replaces the default resource list. Global resources specified with \cmd{addglobalbib} are always considered. \env{refsection} environments may not be nested, but you may use \env{refsegment} environments within a \env{refsection} to subdivide it into segments. Use the \opt{section} option of \cmd{printbibliography} to select a section when printing the bibliography, and the corresponding option of \cmd{printbiblist} when printing bibliography lists. Bibliography sections are numbered starting at~\texttt{1}. The number of the current section is also written to the transcript file. All citations given outside a \env{refsection} environment are assigned to section~0. If \cmd{printbibliography} is used within a \env{refsection}, it will automatically select the current section. The \opt{section} option is not required in this case. This also applies to \cmd{printbiblist}. +The optional argument is a comma"=separated list of resources specific to the reference section. If the argument is omitted, the reference section will use the default resource list, as specified with \cmd{addbibresource} in the preamble. If the argument is provided, it replaces the default resource list. Global resources specified with \cmd{addglobalbib} are always considered. \env{refsection} environments may not be nested, but you may use \env{refsegment} environments within a \env{refsection} to subdivide it into segments. Use the \opt{section} option of \cmd{printbibliography} to select a section when printing the bibliography, and the corresponding option of \cmd{printbiblist} when printing bibliography lists. Bibliography sections are numbered starting at~\texttt{1}. The number of the current section is also written to the transcript file. All citations given outside a \env{refsection} environment are assigned to section~0. If \cmd{printbibliography} is used within a \env{refsection}, it will automatically select the current section. The \opt{section} option is not required in this case. This also applies to \cmd{printbiblist}. Beginning a new reference section automatically ends the active reference context (see \secref{use:bib:context}). \cmditem{newrefsection}[resource, \dots] @@ -3644,7 +3676,7 @@ Matches all entries assigned to \prm{category} with \cmd{addtocategory}. Here is an example of a filter expression: -\begin{ltxexample}[style=latex,keywords={and,or,not,type,keyword}]{} +\begin{ltxexample}[style=latex,keywords={and,or,not,type,keyword}] \defbibfilter{example}{% ( type=book or type=inbook ) and keyword=abc @@ -3654,7 +3686,7 @@ Here is an example of a filter expression: % This filter will match all entries whose entry type is either \bibtype{book} or \bibtype{inbook} and whose \bibfield{keywords} field includes the keyword <\texttt{abc}> but not <\texttt{x y z}>. As seen in the above example, all elements are separated by whitespace (spaces, tabs, or line endings). There is no spacing around the equal sign. The logical operators are evaluated with the \cmd{ifboolexpr} command from the \sty{etoolbox} package. See the \sty{etoolbox} manual for details about the syntax. The syntax of the \cmd{ifthenelse} command from the \sty{ifthen} package, which has been employed in older versions of \biblatex, is still supported. This is the same test using \sty{ifthen}-like syntax: -\begin{ltxexample}[style=ifthen,morekeywords={\\type,\\keyword}]{} +\begin{ltxexample}[style=ifthen,morekeywords={\\type,\\keyword}] \defbibfilter{example}{% \( \type{book} \or \type{inbook} \) \and \keyword{abc} @@ -3756,7 +3788,7 @@ Reference contexts can be declared with \cmd{DeclareRefcontext} and referred to By default, data for a citation is drawn from the reference context of the last bibliography in which it was printed. For example: -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \DeclareRefcontext{ap}{labelprefix=A} \begin{document} @@ -3831,7 +3863,7 @@ This command is similar to the \env{refcontext} environment except that it is a % At the beginning of the document, there is always a global context containing global settings for each of the reference context options. Here is an example summarising the reference contexts with various settings: -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \usepackage[sorting=nty]{biblatex} \DeclareRefcontext{testrc}{sorting=nyt} @@ -3893,7 +3925,7 @@ At the beginning of the document, there is always a global context containing gl \end{ltxsyntax} These commands automate putting citations into refcontexts when the default behaviour is not sufficient. The \prm{key=value} options are as for \cmd{DeclareRefcontext}. The default behaviour is that the data for a citation is drawn from the refcontext of the last bibliography in which it was printed. For citations that are used in some way but not printed in a bibliography or bibliography list, they default to drawing their data from the global refcontext established at the beginning of the document. To override this behaviour, instead of manually wrapping citation commands in \env{refcontext} environments, which might be error-prone and tedious, you can register a comma"=separated list of \prm{keywords}, \prm{categories} or \prm{entrykeys} which, respectively, make the entries with any of the specified keywords, entries in any of the specified categories (see \secref{use:use:div}) or entries with any of the specified citation keys draw their data from a particular refcontext specified by the \prm{refcontext key/values} which are parsed as the per the corresponding \env{refcontext} options. Such refcontext auto-assignments are specific to the current refsection. You may specify the same citation key in any of these commands but be aware that assignment is done in the order \prm{keywords}, \prm{categories}, \prm{entrykeys} with the later specifications overriding the earlier. \cmd{assignrefcontextentries} accepts a single asterisk instead of a list of entrykeys which allows the assignment of all keys in a refsection to a refcontext with having to explicitly list them. An example: -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \assignrefcontextentries[labelprefix=A]{key2} \cite{key1} \begin{refcontext}[labelprefix=B] @@ -3904,7 +3936,7 @@ These commands automate putting citations into refcontexts when the default beha Here, the data for the citation of \bibfield{key2} will be drawn from refcontext \opt{labelprefix=A} and not \opt{labelprefix=B} (resulting in a label with prefix <A> and not <B>). The starred versions do not override a local refcontext and so with: -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \assignrefcontextentries*[labelprefix=A]{key2} \cite{key1} \begin{refcontext}[labelprefix=B] @@ -4020,7 +4052,7 @@ In addition to that, the entire citation list may also have a pre- and\slash or % Note that the multicite commands keep on scanning for arguments until they encounter a token that is not the start of an optional or mandatory argument. If a left brace or bracket follows a multicite command, you need to mask it by adding \cmd{relax} or a control space (a backslash followed by a space) after the last valid argument. This will cause the scanner to stop. -\begin{ltxexample}[style=latex,showspaces]{} +\begin{ltxexample}[style=latex,showspaces] \parencites[35]{key1}[78]{key2}<<\relax>>[...] \parencites[35]{key1}[78]{key2}<<\ >>{...} \end{ltxexample} @@ -4365,7 +4397,7 @@ consists of three entries and the entry key of the first one also serves as iden \mcite{<<set1>>,*glashow,*salam,*weinberg} \end{ltxexample} % -Once defined, an entry set is handled like any regular entry in a \file{bib} file. When using one of the \texttt{numeric} styles which come with \texttt{biblatex} and activating its \opt{subentry} option, it is even possible to refer to set members. See \tabref{use:cit:mct:tab2} for some examples. Restating the original definition of the set is redundant, but permissible. In contrast to \sty{mciteplus}, however, restating a part of the original definition is invalid. Use the entry key of the set instead. +Once defined, an entry set is handled like any regular entry in a \file{bib} file. When using one of the \texttt{numeric} styles which come with \biblatex and activating its \opt{subentry} option, it is even possible to refer to set members. See \tabref{use:cit:mct:tab2} for some examples. Restating the original definition of the set is redundant, but permissible. In contrast to \sty{mciteplus}, however, restating a part of the original definition is invalid. Use the entry key of the set instead. \begin{table} \tablesetup @@ -4704,8 +4736,7 @@ A. Smith. Title. 2000, (Orig. pub. as<<->>Origtitle) The generic separator between the data of multiple related entries. The default definition is an optional dot plus linebreak. Here is an example where volumes A-E are related entries of the 5 volume main work: \begin{ltxexample} -Donald E. Knuth. Computers & Typesetting. 5 vols. Reading, Mass.: Addison- -Wesley, 1984-1986. +Donald E. Knuth. Computers & Typesetting. 5 vols. Reading, Mass.: Addison-Wesley, 1984-1986. Vol. A: The TEXbook. 1984. Vol. B: TEX: The Program. 1986. Vol. C: The METAFONTbook. By. 1986. @@ -4716,6 +4747,12 @@ Vol. E: Computer Modern Typefaces. 1986. \csitem{relateddelim$<$relatedtype$>$} The separator between the data of multiple related entries inside related entries of type <relatedtype>. There is no default, if such a type-specific delimiter does not exist, \cmd{relateddelim} is used. +\csitem{begrelateddelim} +The generic separator before the block of related entries. The default definition is \cmd{newunitpunct}. + +\csitem{begrelateddelim$<$relatedtype$>$} +The separator between the block of related entries of type <relatedtype>. There is no default, if such a type-specific delimiter does not exist, \cmd{relateddelim} is used. + \end{ltxsyntax} \subsubsection{Context-sensitive Delimiters} @@ -4761,7 +4798,7 @@ therefore do not work. Therefore this command is provided for style authors which aliases the context \prm{alias} to the context \prm{name}. For example: -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \DeclareDelimcontextAlias{cbx@textcite}{textcite} \end{ltxexample} % @@ -4782,20 +4819,20 @@ as expected. For example, the defaults for \cmd{nametitledelim} are: -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \DeclareDelimFormat{nametitledelim}{\addcomma\space} \DeclareDelimFormat[textcite]{nametitledelim}{\addspace} \end{ltxexample} % This means that \cmd{nametitledelim} is defined globally as <\cmd{addcomma}\cmd{space}> as per the standard delimiter interface. However, in addition, the delimiter can be printed using \cmd{printdelim} which would print the same as \cmd{nametitledelim} apart from inside a \cmd{textcite}, in which it would print \cmd{addspace} which is more suitable for running text. If desired, a context can be forced with the optional argument to \cmd{printdelim}, so -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \printdelim[textcite]{nametitledelim} \end{ltxexample} % Would print \cmd{addspace} regardless of the surrounding context of the \cmd{printdelim}. Contexts are just arbitrary strings and so you can establish them at any time, using \cmd{delimcontext}. If \cmd{printdelim} finds no special value for the delimiter \prm{name} in the current context, it simply prints \cmd{name}. This means that style authors can use \cmd{printdelim} and users expecting to be able to use \cmd{renewcommand} to redefine delimiters can do so with one caveat---such a definition won't change any context-specific delimiters which are defined: -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \DeclareDelimFormat{delima}{X} \DeclareDelimFormat[textcite]{delima}{Y} \renewcommand*{\delima}{Z} @@ -6332,6 +6369,7 @@ will tell you if the corresponding date is defined and a (fully specified) range % will tell you if the corresponding date is defined and an open"=ended range. Open"=ended ranges are indicated by an empty \texttt{endyear} component (as opposed to an undefined \texttt{endyear} component). See \secref{bib:use:dat} and \tabref{bib:use:tab1} on page~\pageref{bib:use:tab1} for further examples. +\begingroup \tablesetup \begin{longtable}[l]{% @{}V{0.15\textwidth}% @@ -6480,6 +6518,7 @@ eventdate & 1995-01-31/1995-02-05 & eventday & 31 \\ \caption{Date Interface} \label{aut:bbx:fld:tab1} \end{longtable} +\endgroup \begin{fieldlist} @@ -6994,7 +7033,7 @@ contains the value of the name, \cmd{NewCount} contains the number of individual \subsubsection{Formatting Directives} \label{aut:bib:fmt} -This section introduces the commands used to define the formatting directives required by the data commands from \secref{aut:bib:dat}. Note that all standard formats are defined in \path{biblatex_.def}. +This section introduces the commands used to define the formatting directives required by the data commands from \secref{aut:bib:dat}. Note that all standard formats are defined in \path{biblatex.def}. \begin{ltxsyntax} @@ -7138,7 +7177,7 @@ For example, here are the default sets defined by \biblatex for name fields and \end{ltxsyntax} -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \DeclareDatafieldSet{setnames}{ \member[datatype=name, fieldtype=list] } @@ -7192,7 +7231,7 @@ Defines source data modification (mapping) rules which can be used to perform an reference section \end{itemize} -The \prm{specification} is an undelimited list of \cmd{maps} directives which specify containers for mappings rules applying to a particular data source type (\secref{use:bib:res}). Spaces, tabs, and line endings may be used freely to visually arrange the \prm{specification}. Blank lines are not permissible. This command may only be used in the preamble and may only be used once---subsequent uses will overwrite earlier definitions. +The \prm{specification} is an undelimited list of \cmd{maps} directives which specify containers for mappings rules applying to a particular data source type (\secref{use:bib:res}). Spaces, tabs, and line endings may be used freely to visually arrange the \prm{specification}. Blank lines are not permissible. This command may only be used in the preamble and can be used multiple times, the maps being run in order of definition. \cmditem{maps}[options]{elements} @@ -7226,7 +7265,7 @@ Loop over all \cmd{step}s in this \cmd{map}, setting the special variable |$MAPL to each of the comma-separated values contained in \prm{loopval}. \prm{loopval} can either be the name of a datafield set defined with \cmd{DeclareDatafieldSet} (see \secref{aut:ctm:dsets}), a datasource field which is fetched and parsed as a comma"=separated values list or an explicit comma"=separated values list. \prm{loopval} is determined in this order. This allows the user to repeat a group of \cmd{step}s for each value \prm{loopval}. Using regexp maps, it is possible to create a CSV field for use with this functionality. The special variable |$MAPUNIQ| %$ may also be used the \cmd{step}s to generate a random unique string. This can be useful when creating keys for new entries. An example: -\begin{ltxexample}[style=latex]{} +\begin{ltxexample}[style=latex] \DeclareSourcemap{ \maps[datatype=bibtex]{ \map[overwrite, foreach={author,editor, translator}]{ @@ -7275,6 +7314,7 @@ A mapping step. Each step is applied sequentially to every relevant entry where \valitem{entrynew}{entrynewkey} \valitem{entrynewtype}{string} \valitem{entrytarget}{string} +\boolitem[false]{entrynocite} \boolitem[false]{entrynull} \boolitem[false]{append} \boolitem[false]{final} @@ -7296,6 +7336,9 @@ For all boolean \cmd{step} options, the short form \opt{option} is equivalent to created by \texttt{entrynew}, the target for the field set will be the \texttt{entrytarget} entry rather than the entry being currently processed. This allows users to create new entries and set fields in them. +\item If \texttt{entrynocite} is used in a \texttt{entrynew} or + \texttt{entryclone} step, the new/clone entry will be included in the + \file{.bbl} as if the entry/clone had been \cmd{nocite}ed in the document. \item If \texttt{entrynull} is set, processing of the \cmd{map} immediately terminates and the current entry is not created. It is as if it did not exist in the datasource. Obviously, you should @@ -8664,8 +8707,8 @@ An example of transliterating titles so that they sort correctly in Sanskrit: & \sffamily\bfseries\spotcolor To & Description\\ \midrule -iast & devanagari & Sanskrit IAST\footnote{International Alphabet of Sanskrit Transliteration} to Devanāgarī\\ -russian & ala-lc & ALA-LC\footnote{American Library Association---Library of Congress} romanisation for Russian\\ +iast & devanagari & Sanskrit IAST to Devanāgarī\\ +russian & ala-lc & ALA-LC romanisation for Russian\\ russian & bgn/pcgn-standard & BGN/PCGN:1947 (Standard Variant), Cyrillic to Latin, Russian\\ \bottomrule \end{tabular} @@ -9326,6 +9369,18 @@ As \cmd{if$<$datetype$>$dateuncertain} but for use in \cmd{mkbibdate*} formattin As \cmd{ifend$<$datetype$>$dateuncertain} but for use in \cmd{mkbibdate*} formatting commands (\secref{aut:fmt:lng}) inside which the appropriate \cmd{ifend$<$datetype$>$dateuncertain} command is aliased to this command. +\cmditem{if$<$datetype$>$dateunknown}{true}{false} + +Expands to \prm{true} if the date <datetype>date (\opt{date}, \opt{urldate}, \opt{eventdate} etc.) is marked as unknown (as opposed to open) in the source and \prm{false} otherwise. See \secref{bib:use:dat}. + +\cmditem{ifdateunknown}{true}{false} + +As \cmd{if$<$datetype$>$dateunknown} but for use in \cmd{mkbibdate*} formatting commands (\secref{aut:fmt:lng}) inside which the appropriate \cmd{if$<$datetype$>$dateunknown} command is aliased to this command. + +\cmditem{ifenddateunknown}{true}{false} + +As \cmd{ifend$<$datetype$>$dateunknown} but for use in \cmd{mkbibdate*} formatting commands (\secref{aut:fmt:lng}) inside which the appropriate \cmd{ifend$<$datetype$>$dateunknown} command is aliased to this command. + \cmditem{iflabeldateisdate}{true}{false} Expands to \prm{true} if labeldate is defined and was obtained from date, and to \prm{false} otherwise. @@ -9854,11 +9909,10 @@ The problem with this convention is that the braces will suppress the kerning on This command is intended for use in field formatting directives which format the page numbers in the \prm{postnote} argument of citation commands and the \bibfield{pages} field of bibliography entries. It will parse its \prm{text} argument and prefix it with <p.> or <pp.> by default. The optional \prm{pagination} argument holds the name of a field indicating the pagination type. This may be either \bibfield{pagination} or \bibfield{bookpagination}, with \bibfield{pagination} being the default. The spacing between the prefix and the \prm{text} may be modified by redefining \cmd{ppspace}. The default is an unbreakable interword space. See \secref{bib:use:pag, use:cav:pag} for further details. See also \cmd{DeclareNumChars}, \cmd{DeclareRangeChars}, \cmd{DeclareRangeCommands}, and \cmd{NumCheckSetup}. The optional \prm{postpro} argument specifies a macro to be used for post-processing the \prm{text}. If only one optional argument is given, it is taken as \prm{pagination}. Here are two typical examples: \begin{ltxexample} -\DeclareFieldFormat{postnote}{<<\mkpageprefix[pagination]{#1}>>} +\DeclareFieldFormat{postnote}{<<\mkpageprefix[pagination][\mknormrange]{#1}>>} \DeclareFieldFormat{pages}{<<\mkpageprefix[bookpagination]{#1}>>} \end{ltxexample} % -The optional argument \bibfield{pagination} in the first example is omissible. \cmditem{mkpagetotal}[pagination][postpro]{text} @@ -9910,7 +9964,7 @@ The pagination strings are taken from \texttt{$<$pagination$>$total} and \texttt \cmditem{mkcomprange}[postpro]{text} \cmditem*{mkcomprange*}[postpro]{text} -This command, which is intended for use in field formatting directives, will parse its \prm{text} argument for page ranges and compress them. For example, «125--129» may be formatted as «125--9». You may configure the behavior of \cmd{mkcomprange} by adjusting the \latex counters \cnt{mincomprange}, \cnt{maxcomprange}, and \cnt{mincompwidth}, as illustrated in \tabref{aut:aux:tab1}. The default settings are \texttt{10}, \texttt{100000}, and \texttt{1}, respectively. This means that the command tries to compress as much as possible by default. Use \cmd{setcounter} to adjust the parameters. The scanner recognises \cmd{bibrangedash} and hyphens as range dashes. It will normalize the dash by replacing any number of consecutive hyphens with \cmd{bibrangedash}. Lists of ranges delimited with \cmd{bibrangessep} are also supported. The backend will normalise any comma or semi-colons surrounded by optional space by replacing them with \cmd{bibrangessep}. If you want to hide a character from the list/range scanner for some reason, wrap the character or the entire string in curly braces. The optional \prm{postpro} argument specifies a macro to be used for post-processing the \prm{text}. This is important if you want to combine \cmd{mkcomprange} with other formatting macros which also need to parse their \prm{text} argument, such as \cmd{mkpageprefix}. Simply nesting these commands will not work as expected. Use the \prm{postpro} argument to set up the processing chain as follows: +This command, which is intended for use in field formatting directives, will parse its \prm{text} argument for page ranges and compress them. For example, «125--129» may be formatted as «125--9». You may configure the behavior of \cmd{mkcomprange} by adjusting the \latex counters \cnt{mincomprange}, \cnt{maxcomprange}, and \cnt{mincompwidth}, as illustrated in \tabref{aut:aux:tab1}. The default settings are \texttt{10}, \texttt{100000}, and \texttt{1}, respectively. This means that the command tries to compress as much as possible by default. Use \cmd{setcounter} to adjust the parameters. The scanner recognises \cmd{bibrangedash} and hyphens as range dashes. It will normalize the dash by replacing any number of consecutive hyphens with \cmd{bibrangedash}. Lists of ranges delimited with \cmd{bibrangessep} are also supported. The scanner will normalise any comma or semi-colons surrounded by optional space by replacing them with \cmd{bibrangessep}. If you want to hide a character from the list/range scanner for some reason, wrap the character or the entire string in curly braces. The optional \prm{postpro} argument specifies a macro to be used for post-processing the \prm{text}. This is important if you want to combine \cmd{mkcomprange} with other formatting macros which also need to parse their \prm{text} argument, such as \cmd{mkpageprefix}. Simply nesting these commands will not work as expected. Use the \prm{postpro} argument to set up the processing chain as follows: \begin{ltxexample} \DeclareFieldFormat{postnote}{\mkcomprange[<<{>>\mkpageprefix[pagination]<<}>>]{#1}} @@ -9930,6 +9984,11 @@ pp. 5, 123-9, 423-39 p. 5, pp. 123-9, pp. 423-39 \end{ltxexample} +\cmditem{mknormrange}[postpro]{text} +\cmditem*{mknormrange*}[postpro]{text} + +This command, which is intended for use in field formatting directives, will parse its \prm{text} argument for page ranges and will normalise them. The command is similar to \cmd{mkcomprange} except that the page ranges will not be compressed. The scanner recognises \cmd{bibrangedash} and hyphens as range dashes. It will normalize the dash by replacing any number of consecutive hyphens with \cmd{bibrangedash}. Lists of ranges delimited with \cmd{bibrangessep} are also supported. The scanner will normalise any comma or semi-colons surrounded by optional space by replacing them with \cmd{bibrangessep}. If you want to hide a character from the list/range scanner for some reason, wrap the character or the entire string in curly braces. The optional \prm{postpro} argument specifies a macro to be used for post-processing the \prm{text}. See \cmd{mkcomprange} on how to use this argument. The starred version of this command differs from the regular one in the way the \prm{postpro} argument is applied to a list of values. + \cmditem{mkfirstpage}[postpro]{text} \cmditem*{mkfirstpage*}[postpro]{text} @@ -9999,9 +10058,9 @@ This command configures the \cmd{ifnumerals} and \cmd{ifpages} tests from \secre \DeclareRangeChars{~,;-+/} \end{ltxexample} -On engines that fully support Unicode the default is -\begin{ltxexample} -\DeclareRangeChars{~,;-–—+/} +For engines that fully support Unicode these defaults are extended with +\begin{ltxexample}[escapeinside={(*@}{@*)}] +\DeclareRangeChars*{(*@–—@*)} \end{ltxexample} % This means that strings like <3--5>, <35+>, <8/9> and so on will be considered as a range by \cmd{ifnumerals} and \cmd{ifpages}. Non-range characters in such strings are recognized as numbers. So strings like <3a--5a> and <35b+> are not deemed to be ranges by default. See also \secref{bib:use:pag, use:cav:pag} for further details. @@ -10047,14 +10106,17 @@ See the \sty{babel}/\sty{polyglossia} manuals and \tabref{bib:fld:tab1} for a li This command is similar to \cmd{PackageWarning} but prints the entry key of the entry currently being processed in addition to the input line number. It may be used in the bibliography as well as in citation commands. If the \prm{message} is fairly long, use \cmd{MessageBreak} to include line breaks. Note that the standard \cmd{PackageWarning} command does not provide a meaningful clue when used in the bibliography since the input line number is the line on which the \cmd{printbibliography} command was given. \boolitem{pagetracker} +\leavevmode\vspace{\numexpr2\baselineskip}% fix margin spilling into the text These commands activate or deactivate the citation tracker locally (this will affect the \cmd{iffirstonpage} and \cmd{ifsamepage} test from \secref{aut:aux:tst}). They are intended for use in the definition of citation commands or anywhere in the document body. If a citation command is to be excluded from page tracking, use \cmd{pagetrackerfalse} in the \prm{precode} argument of \cmd{DeclareCiteCommand}. See \secref{aut:cbx:cbx} for details. Note that these commands have no effect if page tracking has been disabled globally. \boolitem{citetracker} +\leavevmode\vspace{\numexpr2\baselineskip}% fix margin spilling into the text These commands activate or deactivate all citation trackers locally (this will affect the \cmd{ifciteseen}, \cmd{ifentryseen}, \cmd{ifciteibid}, and \cmd{ifciteidem} tests from \secref{aut:aux:tst}). They are intended for use in the definition of citation commands or anywhere in the document body. If a citation command is to be excluded from tracking, use \cmd{citetrackerfalse} in the \prm{precode} argument of \cmd{DeclareCiteCommand}. See \secref{aut:cbx:cbx} for details. Note that these commands have no effect if tracking has been disabled globally. \boolitem{backtracker} +\leavevmode\vspace{\numexpr2\baselineskip}% fix margin spilling into the text These commands activate or deactivate the \texttt{backref} tracker locally. They are intended for use in the definition of citation commands or anywhere in the document body. If a citation command is to be excluded from backtracking, use \cmd{backtrackerfalse} in the \prm{precode} argument of \cmd{DeclareCiteCommand}. Note that these commands have no effect if the \texttt{backref} option has been not been set globally. @@ -10246,16 +10308,15 @@ The following commands configure various features related to punctuation and aut \cmditem{DeclarePrefChars}{characters} \cmditem*{DeclarePrefChars*}{characters} -This command declares characters that are to be treated specially when testing to see if \cmd{bibnamedelimc} is to be inserted between a name prefix and a family name. If a character is in the list of \prm{characters}, \cmd{bibnamedelimc} is not inserted. It is used to allow abbreviated name prefices like <d'Argent> where no space should be inserted after the apostrophe. The starred version appends its argument to the list of prefix characters, the unstarred version replaces current setting. The default setting is: +This command declares characters that are to be treated specially when testing to see if \cmd{bibnamedelimc} is to be inserted between a name prefix and a family name. If a character is in the list of \prm{characters}, \cmd{bibnamedelimc} is not inserted. It is used to allow abbreviated name prefices like <d'Argent> where no space should be inserted after the apostrophe. The starred version appends its argument to the list of prefix characters, the unstarred version replaces the current setting. The default setting is: \begin{ltxexample} \DeclarePrefChars{'-} \end{ltxexample} -On engines that fully support Unicode the default is - -\begin{ltxexample} -\DeclarePrefChars{'’-} +For engines that fully support Unicode these defaults are extended with +\begin{ltxexample}[escapeinside={(*@}{@*)}] +\DeclarePrefChars*{(*@’@*)} \end{ltxexample} \cmditem{DeclareAutoPunctuation}{characters} @@ -10512,7 +10573,7 @@ This command defines a language file suffix which will be added when looking for % When the document language is <german>, \biblatex will look for the file \file{german-apa.lbx} which defines some APA specific strings and in turn loads \file{german.lbx}. If \cmd{DeclareLanguageMapping} is defined for a language, this overrides \cmd{DeclareLanguageMappingSuffix}. -Note that the suffix will not be applied to language files loaded recursively by the loading of a language file. For example, given the suffix defined above, when loading <ngerman>, \biblatex will look for the file \file{ngerman-apa.lbx} and if this recursively loads <german>, then biblatex will look for \file{german.lbx} and \emph{not} \file{german-apa.lbx}. +The suffix will be applied to other language files loaded recursively by the loading of a language file. For example, given the suffix defined above, when loading <ngerman>, \biblatex will look for the file \file{ngerman-apa.lbx} and if this recursively loads <german>, then biblatex will look for \file{german-apa.lbx}. Infinite recursion is of course avoided. \cmditem{NewBibliographyString}{key} @@ -11009,6 +11070,7 @@ Other expressions frequently used in citations: \item[langitalian] The language <Italian>. \item[langjapanese] The language <Japanese>. \item[langlatin] The language <Latin>. +\item[langlatvian] The language <Latvian>. \item[langnorwegian] The language <Norwegian>. \item[langpolish] The language <Polish>. \item[langportuguese] The language <Portuguese>. @@ -11040,6 +11102,7 @@ The following strings are intended for use in phrases like <translated from [the \item[fromitalian] The expression <from [the] Italian>. \item[fromjapanese] The expression <from [the] Japanese>. \item[fromlatin] The expression <from [the] Latin>. +\item[fromlatvian] The expression <from [the] Latvian>. \item[fromnorwegian] The expression <from [the] Norwegian>. \item[frompolish] The expression <from [the] Polish>. \item[fromportuguese] The expression <from [the] Portuguese>. @@ -11293,6 +11356,12 @@ The separator between the data of multiple related entries. The default definiti \csitem{relateddelim$<$relatedtype$>$} The separator between the data of multiple related entries inside related entries of type <relatedtype>. There is no default, if such a type-specific delimiter does not exist, \cmd{relateddelim} is used. +\csitem{begrelateddelim} +The generic separator before the block of related entries. The default definition is \cmd{newunitpunct}. + +\csitem{begrelateddelim$<$relatedtype$>$} +The separator between the block of related entries of type <relatedtype>. There is no default, if such a type-specific delimiter does not exist, \cmd{relateddelim} is used. + \end{ltxsyntax} \subsubsection{Language-specific Commands} @@ -12516,6 +12585,8 @@ If the document language is set to \texttt{french}, \path{french-humanities.lbx} \DeclareLanguageMapping{american}{american-mla} \end{ltxexample} % +Use \cmd{DeclareLanguageMappingSuffix} (see \secref{aut:lng:cmd}) to define such a mapping for all languages. + Since the alternative \file{lbx} file can inherit strings from the standard \path{american.lbx} module, \path{american-mla.lbx} may be as short as this: \begin{ltxexample} @@ -13222,9 +13293,20 @@ use$<$name$>$ &\+&\+&\_&\+&\+&\_&\_\\ \section{Revision History} \label{apx:log} -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.org} file. The numbers on the right indicate the relevant section of this manual. +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.11}{2018-02-20} +\item Added \opt{entrynocite} option to sourcemapping\see{aut:ctm:map} +\item Added \opt{driver} and \opt{biblistfilter} options to \cmd{printbiblist}\see{use:bib:biblist} +\item Added \cmd{mknormrange}\see{aut:aux:msc} +\item Added \cmd{ifdateannotation}\see{use:annote} +\item Extended \cmd{iffieldannotation} and friends\see{use:annote} +\item Changed \cmd{DeclareSourcemap} so that it can be used multiple times\see{aut:ctm:map} +\item Added Latvian localisation (Rihards Skuja) +\item Added \opt{locallabelwidth} option\see{use:opt:pre:gen} +\end{release} + \begin{release}{3.10}{2017-12-19} \item Changed \opt{edtf} to \opt{iso}\see{use:opt:pre:gen} \item Added \opt{noerroretextools} option\see{int:pre:inc} |