From 24f27b13d3ff59a9fc025ce009af154a95fd9acf Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Sun, 5 Nov 2017 23:51:11 +0000 Subject: revert to biblatex 3.7, since 3.8 (and companion biber) was apparently not ready git-svn-id: svn://tug.org/texlive/trunk@45702 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/latex/biblatex/CHANGES.org | 154 --- Master/texmf-dist/doc/latex/biblatex/README | 10 +- Master/texmf-dist/doc/latex/biblatex/biblatex.pdf | Bin 1387130 -> 1346281 bytes Master/texmf-dist/doc/latex/biblatex/biblatex.tex | 1047 ++++++-------------- .../biblatex/examples/01-introduction-biber.pdf | Bin 167963 -> 167963 bytes .../biblatex/examples/01-introduction-bibtex.pdf | Bin 167963 -> 167963 bytes .../biblatex/examples/02-annotations-biber.pdf | Bin 208624 -> 208761 bytes .../biblatex/examples/02-annotations-bibtex.pdf | Bin 210549 -> 210545 bytes .../examples/03-localization-keys-biber.pdf | Bin 245681 -> 242952 bytes .../examples/03-localization-keys-bibtex.pdf | Bin 246046 -> 243270 bytes .../biblatex/examples/03-localization-keys.tex | 369 +++---- .../biblatex/examples/04-delimiters-biber.pdf | Bin 80153 -> 80158 bytes .../biblatex/examples/04-delimiters-bibtex.pdf | Bin 80153 -> 80153 bytes .../examples/10-references-per-section-biber.pdf | Bin 81709 -> 81709 bytes .../examples/10-references-per-section-bibtex.pdf | Bin 81709 -> 81709 bytes .../examples/11-references-by-section-biber.pdf | Bin 98397 -> 98404 bytes .../examples/11-references-by-section-bibtex.pdf | Bin 98397 -> 98397 bytes .../examples/12-references-by-segment-biber.pdf | Bin 98443 -> 98449 bytes .../examples/12-references-by-segment-bibtex.pdf | Bin 98443 -> 98443 bytes .../examples/13-references-by-keyword-biber.pdf | Bin 175146 -> 175146 bytes .../examples/13-references-by-keyword-bibtex.pdf | Bin 175146 -> 175146 bytes .../examples/14-references-by-category-biber.pdf | Bin 174652 -> 174652 bytes .../examples/14-references-by-category-bibtex.pdf | Bin 174652 -> 174652 bytes .../examples/15-references-by-type-biber.pdf | Bin 119275 -> 119006 bytes .../examples/15-references-by-type-bibtex.pdf | Bin 119275 -> 119006 bytes .../examples/16-numeric-prefixed-1-biber.pdf | Bin 156844 -> 156860 bytes .../examples/16-numeric-prefixed-1-bibtex.pdf | Bin 157852 -> 157850 bytes .../examples/17-numeric-prefixed-2-biber.pdf | Bin 156849 -> 156865 bytes .../examples/17-numeric-prefixed-2-bibtex.pdf | Bin 157850 -> 157857 bytes .../biblatex/examples/18-numeric-hybrid-biber.pdf | Bin 112922 -> 112693 bytes .../biblatex/examples/18-numeric-hybrid-bibtex.pdf | Bin 112922 -> 112693 bytes .../examples/19-alphabetic-prefixed-biber.pdf | Bin 158022 -> 158016 bytes .../examples/19-alphabetic-prefixed-bibtex.pdf | Bin 158600 -> 158608 bytes .../biblatex/examples/20-indexing-single-biber.pdf | Bin 170459 -> 170444 bytes .../examples/20-indexing-single-bibtex.pdf | Bin 171187 -> 171187 bytes .../examples/21-indexing-multiple-biber.pdf | Bin 171706 -> 171716 bytes .../examples/21-indexing-multiple-bibtex.pdf | Bin 172434 -> 172434 bytes .../examples/22-indexing-subentry-biber.pdf | Bin 88902 -> 88902 bytes .../examples/22-indexing-subentry-bibtex.pdf | Bin 88902 -> 88902 bytes .../biblatex/examples/30-style-numeric-biber.pdf | Bin 177237 -> 156345 bytes .../biblatex/examples/30-style-numeric-bibtex.pdf | Bin 178182 -> 157575 bytes .../latex/biblatex/examples/30-style-numeric.tex | 43 +- .../examples/31-style-numeric-comp-biber.pdf | Bin 179216 -> 158966 bytes .../examples/31-style-numeric-comp-bibtex.pdf | Bin 180475 -> 160235 bytes .../biblatex/examples/31-style-numeric-comp.tex | 16 - .../examples/32-style-numeric-verb-biber.pdf | Bin 181612 -> 161557 bytes .../examples/32-style-numeric-verb-bibtex.pdf | Bin 182615 -> 162407 bytes .../biblatex/examples/32-style-numeric-verb.tex | 14 - .../examples/40-style-alphabetic-biber.pdf | Bin 200072 -> 199924 bytes .../examples/40-style-alphabetic-bibtex.pdf | Bin 200754 -> 200749 bytes .../examples/41-style-alphabetic-verb-biber.pdf | Bin 111954 -> 111954 bytes .../examples/41-style-alphabetic-verb-bibtex.pdf | Bin 111954 -> 111954 bytes .../42-style-alphabetic-template-biber.pdf | Bin 101006 -> 101006 bytes .../42-style-alphabetic-template-bibtex.pdf | Bin 101006 -> 101006 bytes .../examples/50-style-authoryear-biber.pdf | Bin 280101 -> 279652 bytes .../examples/50-style-authoryear-bibtex.pdf | Bin 278983 -> 278901 bytes .../biblatex/examples/50-style-authoryear.tex | 41 +- .../examples/51-style-authoryear-ibid-biber.pdf | Bin 211744 -> 210650 bytes .../examples/51-style-authoryear-ibid-bibtex.pdf | Bin 211744 -> 210650 bytes .../biblatex/examples/51-style-authoryear-ibid.tex | 41 +- .../examples/52-style-authoryear-comp-biber.pdf | Bin 147309 -> 146378 bytes .../examples/52-style-authoryear-comp-bibtex.pdf | Bin 147309 -> 146378 bytes .../biblatex/examples/52-style-authoryear-comp.tex | 41 +- .../examples/53-style-authoryear-icomp-biber.pdf | Bin 223981 -> 223167 bytes .../examples/53-style-authoryear-icomp-bibtex.pdf | Bin 223981 -> 223167 bytes .../examples/53-style-authoryear-icomp.tex | 41 +- .../examples/60-style-authortitle-biber.pdf | Bin 277386 -> 277398 bytes .../examples/60-style-authortitle-bibtex.pdf | Bin 276660 -> 276663 bytes .../examples/61-style-authortitle-ibid-biber.pdf | Bin 200063 -> 200064 bytes .../examples/61-style-authortitle-ibid-bibtex.pdf | Bin 200063 -> 200064 bytes .../examples/62-style-authortitle-comp-biber.pdf | Bin 126056 -> 126056 bytes .../examples/62-style-authortitle-comp-bibtex.pdf | Bin 126056 -> 126056 bytes .../examples/63-style-authortitle-icomp-biber.pdf | Bin 220479 -> 220478 bytes .../examples/63-style-authortitle-icomp-bibtex.pdf | Bin 220479 -> 220478 bytes .../examples/64-style-authortitle-terse-biber.pdf | Bin 195329 -> 195328 bytes .../examples/64-style-authortitle-terse-bibtex.pdf | Bin 195329 -> 195328 bytes .../examples/65-style-authortitle-tcomp-biber.pdf | Bin 143184 -> 143184 bytes .../examples/65-style-authortitle-tcomp-bibtex.pdf | Bin 143184 -> 143184 bytes .../examples/66-style-authortitle-ticomp-biber.pdf | Bin 144581 -> 144581 bytes .../66-style-authortitle-ticomp-bibtex.pdf | Bin 144581 -> 144581 bytes .../biblatex/examples/70-style-verbose-biber.pdf | Bin 268072 -> 268087 bytes .../biblatex/examples/70-style-verbose-bibtex.pdf | Bin 266552 -> 266565 bytes .../examples/71-style-verbose-ibid-biber.pdf | Bin 271095 -> 271098 bytes .../examples/71-style-verbose-ibid-bibtex.pdf | Bin 269671 -> 269673 bytes .../examples/72-style-verbose-note-biber.pdf | Bin 270386 -> 270414 bytes .../examples/72-style-verbose-note-bibtex.pdf | Bin 268933 -> 268939 bytes .../examples/73-style-verbose-inote-biber.pdf | Bin 273262 -> 273275 bytes .../examples/73-style-verbose-inote-bibtex.pdf | Bin 271852 -> 271860 bytes .../examples/74-style-verbose-trad1-biber.pdf | Bin 327079 -> 327085 bytes .../examples/74-style-verbose-trad1-bibtex.pdf | Bin 325693 -> 325700 bytes .../examples/75-style-verbose-trad2-biber.pdf | Bin 272585 -> 272593 bytes .../examples/75-style-verbose-trad2-bibtex.pdf | Bin 271196 -> 271208 bytes .../examples/76-style-verbose-trad3-biber.pdf | Bin 270809 -> 270817 bytes .../examples/76-style-verbose-trad3-bibtex.pdf | Bin 269428 -> 269435 bytes .../biblatex/examples/80-style-reading-biber.pdf | Bin 244291 -> 244297 bytes .../biblatex/examples/80-style-reading-bibtex.pdf | Bin 244291 -> 244297 bytes .../biblatex/examples/81-style-draft-biber.pdf | Bin 149728 -> 149728 bytes .../biblatex/examples/81-style-draft-bibtex.pdf | Bin 149728 -> 149728 bytes .../biblatex/examples/82-style-debug-biber.pdf | Bin 149687 -> 149685 bytes .../biblatex/examples/82-style-debug-bibtex.pdf | Bin 148852 -> 148852 bytes .../biblatex/examples/90-related-entries-biber.pdf | Bin 31077 -> 31078 bytes .../biblatex/examples/91-sorting-schemes-biber.pdf | Bin 21549 -> 21532 bytes .../latex/biblatex/examples/91-sorting-schemes.tex | 6 - .../examples/92-bibliographylists-biber.pdf | Bin 61448 -> 61301 bytes .../biblatex/examples/92-bibliographylists.tex | 2 +- .../latex/biblatex/examples/93-nameparts-biber.pdf | Bin 37873 -> 50223 bytes .../doc/latex/biblatex/examples/93-nameparts.dbx | 2 +- .../doc/latex/biblatex/examples/93-nameparts.tex | 436 +------- .../biblatex/examples/94-labelprefix-biber.pdf | Bin 23852 -> 23852 bytes .../biblatex/examples/95-customlists-biber.pdf | Bin 12143 -> 12143 bytes .../doc/latex/biblatex/examples/95-customlists.tex | 2 +- .../doc/latex/biblatex/examples/96-dates-biber.pdf | Bin 25108 -> 24953 bytes .../doc/latex/biblatex/examples/96-dates.tex | 8 +- 113 files changed, 605 insertions(+), 1668 deletions(-) (limited to 'Master/texmf-dist/doc/latex/biblatex') diff --git a/Master/texmf-dist/doc/latex/biblatex/CHANGES.org b/Master/texmf-dist/doc/latex/biblatex/CHANGES.org index e573657f311..0ea70f42fee 100644 --- a/Master/texmf-dist/doc/latex/biblatex/CHANGES.org +++ b/Master/texmf-dist/doc/latex/biblatex/CHANGES.org @@ -1,157 +1,3 @@ -* RELEASE NOTES FOR VERSION 3.8 -** Requirements -Biber version 2.8 is required for biblatex 3.8 - -** In order to standardise terminology, some commands and options have dropped the "scheme" naming convention and switched to "template" -- ~\DeclareSortingScheme~ is now ~\DeclareSortingTemplate~ -- ~\DeclareSortingNamekeyScheme~ is now ~\DeclareSortingNamekeyTemplate~ -- The "sortingnamekeyscheme" option is now "sortingnamekeytemplate" - -** ~\DeclareLabelalphaNameTemplate~ no longer has entrytype scope -- *INCOMPATIBLE CHANGE* The optional first argument to - ~\DeclareLabelalphaNameTemplate~ was previously an entrytype but is now an - arbitrary template name, as with ~\DeclareUniquenameTemplate~. This is to - allow multiple definitions which can be referred to at different scopes. - It is unlikely that anyone used this with entrytype scope anyway. - -** ~origlanguage~ is now a list instead of a field. -- *INCOMPATIBLE CHANGE* Since this is mostly used to generate localisation strings like - 'Translated from the ' via the internal macros ~lbx@lfromlang~ - and ~\lbx@sfromlang~, users and style authors should not see any - differences. However, if your style prints ~origlanguage~ directly using - ~\printfield~, this will need to be changed to ~\printlist~. - -** Name handling enhancements -- Name handling is now fully generalised to cover arbitrary name parts. - The final few pieces have been completed to allow fully customisable - name handling, allowing for better internationalisation. The code for - name uniqueness calculation and label generation for names is now fully - abstracted: templates created with ~\DeclareUniquenameTemplate~ and - ~\DeclareLabelalphaNameTemplate~ may now be specified at per-refcontext, - per-entry, per-namelist and per-name scope, which allows complete - control over all aspects of name usage. See the comments in the enhanced - ~93-nameparts.tex~ example file. - -** ~extrayear~ is now ~extradate~ and the information used to track this can be customised -- ~extrayear~ is called ~extradate~ now. Limited backwards compatibility is - in place to allow a smooth transition, but style developers should use the new name. -- The new \DeclareExtradate command allows users to track authoryear - disambiguation in arbitrary ways now, for example allowing disambiguation - at month or day level instead of just year. See the PDF doc for details. -- Some bibmacros from the ~authoryear~ style family were renamed, - ~cite:labelyear+extrayear~ becomes ~cite:labeldate+extradate~, - ~cite:extrayear~ is ~cite:extradate~ now, and ~date+extrayear~ - is ~date+extradate~. Some backwards compatibility code is present, - but developers should make sure their code works as expected. - -** Date formatting -- The ~mergedate~ output has been restored to its earlier form, - it has also been extended to cover all EDTF date parts. - In order to facilitate this, a few date-related tests were introduced - ~\iflabeldateisdate~, ~\ifdatehasyearonlyprecision~, ~\ifdatehastime~ - and ~\ifdateshavedifferentprecision~. -- The ~authoryear~ citation styles now use ~\printlabeldateextra~ - instead of ~\printfield{labelyear}\printfield{extrayear}~. - This should have no consequences for end users (except that - dates in citations and bibliography don't differ any more - - previously there were subtle differences when many EDTF features - were used), but style developers should check if they assume - anything about the bibmacros that have now changed. - Style developers are invited to have a look at the changes and - to get inspired to offer full EDTF format for their styles as well. - -** Set handling -- Static entry sets used to have the behaviour that when citing a member of - a set, the data for the citation came from the set parent which was in - turn taken from the first member of the set. In most use cases, the only - part of the set parent data that was actually used was the labels but in - certain edge cases, other data was used which results in confusing - citations for set members. This has been refactored so that when citing - set members, the member data is used along with some labelling data - injected from the set parent. This means that things like - ~\citeauthor{somesetmember}~ now give the expected results. - *PLEASE NOTE* that this means that citing sets directly in default styles *not* - based on labels (~authoryear~, ~authortitle~, ~verbose~ etc.) will result - in blank citations as it is not envisaged that sets are useful in such - styles. -- The members of a set can now be sorted according to the active - sorting scheme, this is enabled via the ~sortsets~ option. - By default the option is set to false and set members appear - in the order given in the data source. -- The ~alphabetic~ style family now also supports the ~subentry~ - option. - -** Localisation and styles -- Styles which supply their own location strings in .lbx files typically - use \DeclareLanguageMapping to map a document language to the supplied - language files. This is not ideal because the mapping has to be done by - the user depending on the specific language. For example, for the APA - style, in a document using American english, this line is necessary in - every document: - - \DeclareLanguageMapping{american}{american-apa} - - so that the style supplied america-apa.lbx file is loaded. In a document - using the german language, the user would have to use: - - \DeclareLanguageMapping{german}{german-apa} - - A new macro \DeclareLanguageMappingSuffix is now supplied which allows - styles to register a global localisation file suffix which is appended to - any document language automatically. This removes the need for - \DeclareLanguageMapping in user documents as it ensures that the correct - localisation file will be read nomatter what the document language. For - example, the APA style (from version v7.5) now has this in apa.bbx: - - \DeclareLanguageMappingSuffix{-apa} - - which means that for a given document language , the localisation file: - - -apa.lbx - - will be loaded. \DeclareLanguageMapping, if present, will override - \DeclareLanguageMappingSuffix. - -** Context-sensitive delimiters -- Several delimiter macros now use the context-sensitive delimiter interface - introduced in version 3.4 (~\DeclareDelimFormat~). This change is fully - backwards compatible, but style developers should feel encouraged to use the - new commands ~\DeclareDelimFormat~ and ~\printdelim~. -- Three new delimiters are introduced. ~authortypedelim~, ~editortypedelim~, - and ~translatortypedelim~ control the delimiter between the respective name - and the following ~~ bibstring. - This together with ~\DeclareFieldFormat{type}~ allows one to go from - 'E. Ditor, ed.' to 'E. Ditor (ed.)' more easily without the need - to redefine entire bibmacros. -- ~\DeclareDelimAlias~ allows one to alias one delimiter to another. - E.g. ~\DeclareDelimAlias{finalnamedelim}{multinamedelim}~ - will make ~finalnamedelim~ an alias for ~multinamedelim~. - The starred version ~\DeclareDelimAlias*~ is local to the - specified contexts. - -** Misc changes -- The initialisation code for ~\usedriver~ can now be modified via - ~\AtUsedriver~, the code can be executed with ~\UseUsedriverHook~. - The default settings retain backwards compatibility with earlier - versions. -- The field ~urlraw~ contains the unencoded, raw version of the URL. - If the URL includes Unicode characters, ~urlraw~ will show them - unencoded while the standard ~url~ field will contain them in - percent-encoded form. -- ~\mkpagetotal~ now has its own bibstrings ~total(s)~ - Previously it relied on the ~(s)~ bibstrings. -- ~sortyear~ is now a literal field and not an integer. -- The ~etextools~ package is now officially incompatible. -- ~bidi~-support for footnotes was improved. -- ~\ifentryseen~, ~\ifentryinbib~, ~\ifentrycategory~ - and ~\ifentrykeyword~ can now be used outside of - ~biblatex~ macros directly in the document. -- ~\letbibmacro~ can be used to create bibmacro aliases as if - using ~\let~. -- ~\DeprecateFieldWithReplacement~, ~\DeprecateListWithReplacement~ - and ~\DeprecateNameWithReplacement~ can be used to deprecate a field, - name or list and replace it with a new one. - * RELEASE NOTES FOR VERSION 3.7 ** Requirements Biber version 2.7 is required for biblatex 3.7 diff --git a/Master/texmf-dist/doc/latex/biblatex/README b/Master/texmf-dist/doc/latex/biblatex/README index 0f98620216e..d5859160015 100644 --- a/Master/texmf-dist/doc/latex/biblatex/README +++ b/Master/texmf-dist/doc/latex/biblatex/README @@ -43,7 +43,7 @@ FEEDBACK Please use the biblatex project page on github to report bugs or submit feature requests: - https://github.com/plk/biblatex + http://github.com/plk/biblatex REQUIREMENTS @@ -65,7 +65,7 @@ Strongly recommended: Biber is available from CTAN, via TeXLive or from -https://sourceforge.net/projects/biblatex-biber/ +http://sourceforge.net/projects/biblatex-biber/ AUTOMATIC INSTALLATION @@ -81,7 +81,7 @@ SEMI-AUTOMATIC INSTALLATION 1. Get the file biblatex-.tds.zip from - https://sourceforge.net/projects/biblatex/files/ + http://sourceforge.net/projects/biblatex/files/ 2. Unpack the archive in the root directory of the local TeX installation tree, for example @@ -104,11 +104,11 @@ MANUAL INSTALLATION 1. Get the file biblatex-.tar.gz from - https://sourceforge.net/projects/biblatex/files/ + http://sourceforge.net/projects/biblatex/files/ or download the file - https://mirror.ctan.org/macros/latex/contrib/biblatex.zip + http://mirror.ctan.org/macros/latex/contrib/biblatex.zip 2. Unpack the archive in a temporary working directory. diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf b/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf index 25663c8cf7e..d694067ea94 100644 Binary files a/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf and b/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf differ diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex index ce8eb5e7e23..25adb732d7f 100644 --- a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex +++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex @@ -60,7 +60,7 @@ url={\biblatexhome}, author={Philipp Lehman \\(with Philip Kime, Audrey Boruvka and Joseph Wright)}, email={}, - revision={3.8}, + revision={3.7}, date={\today}} \hypersetup{% @@ -158,7 +158,7 @@ \section{Introduction} \label{int} -This document is a systematic reference manual for the \biblatex package. Look at the sample documents which come with \biblatex to get a first impression.\fnurl{\biblatexctan doc/examples} +This document is a systematic reference manual for the \biblatex package. Look at the sample documents which ship with \biblatex to get a first impression.\fnurl{\biblatexctan doc/examples} For a quick start guide, browse \secref{int:abt, bib:typ, bib:fld, bib:use, use:opt, use:xbx, use:bib, use:cit, use:use}. \subsection[About]{About \biblatex} @@ -178,15 +178,13 @@ Please use the \biblatex project page on GitHub to report bugs and submit featur \subsection{Acknowledgements} The language modules of this package are made possible thanks to the following contributors: -Augusto Ritter Stoffel, Mateus Araújo, Gustavo Barros (Brazilian); -Kaloyan Ganev (Bulgarian); +Augusto Ritter Stoffel, Mateus Araújo (Brazilian); Sebastià Vila-Marta (Catalan); Ivo Pletikosić (Croatian); Michal Hoftich (Czech); Jonas Nyrup (Danish); Johannes Wilm (Danish\slash Norwegian); Alexander van Loon, Pieter Belmans, Hendrik Maryns (Dutch); -Benson Muite (Estonian); Hannu Väisänen, Janne Kujanpää (Finnish); Denis Bitouzé (French); Apostolos Syropoulos, Prokopis (Greek); @@ -196,13 +194,12 @@ Håkon Malmedal (Norwegian); Anastasia Kandulina, Yuriy Chernyshov (Polish); José Carlos Santos (Portuguese); Oleg Domanov (Russian); -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) - +Martin Vrábel, Dávid Lupták (Slovak); +Benson Muite (Estonian); + \subsection{Prerequisites} \label{int:pre} @@ -216,7 +213,7 @@ The resources listed in this section are strictly required for \biblatex to func \begin{marglist} \item[\etex] -The \biblatex package requires \etex. \tex distributions have been providing \etex binaries for quite some time, the popular distributions use them by default these days. The \biblatex package checks if it is running under \etex. Simply try compiling your documents as you usually do, the chances are that it just works. If you get an error message, try compiling the document with \bin{elatex} instead of \bin{latex} or \bin{pdfelatex} instead of \bin{pdflatex}, respectively. +The \biblatex package requires \etex. \tex distributions have been shipping \etex binaries for quite some time, the popular distributions use them by default these days. The \biblatex package checks if it is running under \etex. Simply try compiling your documents as you usually do, the chances are that it just works. If you get an error message, try compiling the document with \bin{elatex} instead of \bin{latex} or \bin{pdfelatex} instead of \bin{pdflatex}, respectively. \item[\biber] \biber is the backend of \biblatex used to transfer data from source files to the \latex code. \biber comes with TeX Live and is also available from SourceForge.\fnurl{http://biblatex-biber.sourceforge.net/}. \biber uses the \texttt{btparse} C library for \bibtex format file parsing which aimed to be compatible with \bibtex's parsing rules but also aimed at correcting some of the common problems. For details, see the manual page for the Perl \texttt{Text::BibTeX} module\fnurl{http://search.cpan.org/~ambs/Text-BibTeX}. @@ -331,10 +328,6 @@ The \sty{titlesec} package redefines user-level document division commands such \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. -\item[etextools] -The \sty{etextools} package provides enhancements to list macros defined by \sty{etoolbox} and a few other tools for command definitions. -The package redefines list handling macros in a way incompatible with \biblatex. - \end{marglist} \subsubsection{Compatibility Matrix for \biber} @@ -353,8 +346,6 @@ compatibility matrix for the recent versions. \sffamily\bfseries\spotcolor Biber version & \sffamily\bfseries\spotcolor \biblatex\ version\\ \midrule -2.8 & 3.8\\ -2.7 & 3.7\\ 2.6 & 3.5, 3.6\\ 2.5 & 3.4\\ 2.4 & 3.3\\ @@ -401,7 +392,7 @@ This section gives an overview of the entry types supported by the default \bibl \subsubsection{Regular Types} \label{bib:typ:blx} -The lists below indicate the fields supported by each entry type. Note that the mapping of fields to an entry type is ultimately at the discretion of the bibliography style. The lists below therefore serve two purposes. They indicate the fields supported by the standard styles which come with this package and they also serve as a model for custom styles. Note that the fields are not strictly required in all cases, see \secref{bib:use:key} for details. The fields marked as are optional in a technical sense. Bibliographical formatting rules usually require more than just the fields. The default data model defined a few constraints for the format of date fields, ISBNs and some special fields like \bibfield{gender} but the constraints are only used if validating against the data model with \biber's \opt{--validate-datamodel} option. Generic fields like \bibfield{abstract} and \bibfield{annotation} or \bibfield{label} and \bibfield{shorthand} are not included in the lists below because they are independent of the entry type. The special fields discussed in \secref{bib:fld:spc}, which are also independent of the entry type, are not included in the lists either. See the default data model specification in the file \file{blx-dm.def} which comes with \biblatex for a complete specification. +The lists below indicate the fields supported by each entry type. Note that the mapping of fields to an entry type is ultimately at the discretion of the bibliography style. The lists below therefore serve two purposes. They indicate the fields supported by the standard styles which ship with this package and they also serve as a model for custom styles. Note that the fields are not strictly required in all cases, see \secref{bib:use:key} for details. The fields marked as are optional in a technical sense. Bibliographical formatting rules usually require more than just the fields. The default data model defined a few constraints for the format of date fields, ISBNs and some special fields like \bibfield{gender} but the constraints are only used if validating against the data model with \biber's \opt{--validate-datamodel} option. Generic fields like \bibfield{abstract} and \bibfield{annotation} or \bibfield{label} and \bibfield{shorthand} are not included in the lists below because they are independent of the entry type. The special fields discussed in \secref{bib:fld:spc}, which are also independent of the entry type, are not included in the lists either. See the default data model specification in the file \file{blx-dm.def} which comes with \biblatex for a complete specification. \begin{typelist} @@ -722,9 +713,9 @@ The supported list of name parts is defined as a constant list in the default da \item[Range fields] consist of one or more ranges where all dashes are normalized and replaced by the command \cmd{bibrangedash}. A range is something optionally followed by one or more dashes optionally followed by some non-dash (e.g. \texttt{5--7}). Any number of consecutive dashes will only yield a single range dash. A typical example of a range field is the \bibfield{pages} field. See also the \cmd{bibrangessep} command which can be used to customise the separator between multiple ranges. Range fields will be skipped and will generate a warning if they do not consist of one or more ranges. You can normalise messy range fields before they are parsed using \cmd{DeclareSourcemap} (see \secref{aut:ctm:map}). -\item[Integer fields] hold integers which may be converted to ordinals or strings as they are printed. A typical example is the \bibfield{extradate} or \bibfield{volume} field. Such fields are sorted as integers. \biber makes a (quite serious) effort to map non-arabic representations (roman numerals for example) to integers for sorting purposes. +\item[Integer fields] hold integers which may be converted to ordinals or strings as they are printed. A typical example is the \bibfield{extrayear} or \bibfield{volume} field. Such fields are sorted as integers. \biber makes a (quite serious) effort to map non-arabic representations (roman numerals for example) to integers for sorting purposes. -\item[Datepart fields] hold unformatted integers which may be converted to ordinals or strings as they are printed. A typical example is the \bibfield{month} field. For every field of datatype \bibfield{date} in the datamodel, datepart fields are automatically created with the following names: \bibfield{$<$datetype$>$year}, \bibfield{$<$datetype$>$endyear}, \bibfield{$<$datetype$>$month}, \bibfield{$<$datetype$>$endmonth}, \bibfield{$<$datetype$>$day}, \bibfield{$<$datetype$>$endday}, \bibfield{$<$datetype$>$hour}, \bibfield{$<$datetype$>$endhour}, \bibfield{$<$datetype$>$minute}, \bibfield{$<$datetype$>$endminute}, \bibfield{$<$datetype$>$second}, \bibfield{$<$datetype$>$endsecond}, \bibfield{$<$datetype$>$timezone}, \bibfield{$<$datetype$>$endtimezone}. $<$datetype$>$ is the string preceding for any datamodel field of \kvopt{datatype}{date}. For example, in the default datamodel, , , and the empty string <> for the date field \bibfield{date}. +\item[Datepart fields] hold unformatted integers which may be converted to ordinals or strings as they are printed. A typical example is the \bibfield{month} field. For every field X of datatype \bibfield{date} in the datamodel, datepart fields are automatically created with the following names: \bibfield{$<$datetype$>$year}, \bibfield{$<$datetype$>$endyear}, \bibfield{$<$datetype$>$month}, \bibfield{$<$datetype$>$endmonth}, \bibfield{$<$datetype$>$day}, \bibfield{$<$datetype$>$endday}, \bibfield{$<$datetype$>$hour}, \bibfield{$<$datetype$>$endhour}, \bibfield{$<$datetype$>$minute}, \bibfield{$<$datetype$>$endminute}, \bibfield{$<$datetype$>$second}, \bibfield{$<$datetype$>$endsecond}, \bibfield{$<$datetype$>$timezone}, \bibfield{$<$datetype$>$endtimezone}. $<$datetype$>$ is the string preceding for any datamodel field of \kvopt{datatype}{date}. For example, in the default datamodel, , , and the empty string <> for the date field \bibfield{date}. \item[Date fields] hold a date specification in \texttt{yyyy-mm-ddThh:nn[+|-][hh[:nn]|Z]} format or a date range in \texttt{yyyy-mm-ddThh:nn[+|-][hh[:nn]|Z]/yyyy-mm-ddThh:nn[+|-][hh[:nn]|Z]} format and other formats permitted by EDTF level 1, see \secref{bib:use:dat}. Date fields are special in that the date is parsed and split up into its datepart type components. The \bibfield{datepart} components (see above) are automatically defined and recognised when a field of datatype \bibfield{date} is defined in the datamodel. A typical example is the \bibfield{date} field. @@ -838,7 +829,7 @@ Another secondary editor performing a different role. Use the \bibfield{editorct \fielditem{editortype}{key} -The type of editorial role performed by the \bibfield{editor}. Roles supported by default are \texttt{editor}, \texttt{compiler}, \texttt{founder}, \texttt{continuator}, \texttt{redactor}, \texttt{reviser}, \texttt{collaborator}, \texttt{organizer}. The role <\texttt{editor}> is the default. In this case, the field is omissible. See \secref{bib:use:edr} for further hints. +The type of editorial role performed by the \bibfield{editor}. Roles supported by default are \texttt{editor}, \texttt{compiler}, \texttt{founder}, \texttt{continuator}, \texttt{redactor}, \texttt{reviser}, \texttt{collaborator}. The role <\texttt{editor}> is the default. In this case, the field is omissible. See \secref{bib:use:edr} for further hints. \fielditem{editoratype}{key} @@ -984,11 +975,9 @@ The main title of a multi"=volume book, such as \emph{Collected Works}. If the \ An annex to the \bibfield{maintitle}, to be printed in a different font. -\fielditem{month}{literal} +\fielditem{month}{datepart} -The publication month. This must be an integer, not an ordinal or a string. Don't say |month={January}| but |month={1}|. The bibliography style converts this to a language dependent string or ordinal where required. This field is a literal field only when given -explicitly in the data (for plain \bibtex compatibility for example). It is -however better to use the \bibfield{date} field as this supports many more features. See \secref{bib:use:dat}. +The publication month. This must be an integer, not an ordinal or a string. Don't say |month={January}| but |month={1}|. The bibliography style converts this to a language dependent string or ordinal where required. See also \bibfield{date} as well as \secref{bib:use:iss, bib:use:dat}. \fielditem{nameaddon}{literal} @@ -1010,9 +999,9 @@ The organization(s) that published a \bibtype{manual} or an \bibtype{online} res If the work is a translation, a reprint, or something similar, the publication date of the original edition. Not used by the standard bibliography styles. See also \bibfield{date}. -\listitem{origlanguage}{key} +\fielditem{origlanguage}{key} -If the work is a translation, the language(s) of the original work. See also \bibfield{language}. +If the work is a translation, the language of the original work. See also \bibfield{language}. \listitem{origlocation}{literal} @@ -1132,10 +1121,7 @@ The total number of volumes of a multi"=volume work. Depending on the entry type \fielditem{year}{literal} -The year of publication. This field is a literal field only when given -explicitly in the data (for plain \bibtex compatibility for example). It is -however better to use the \bibfield{date} field as this is compatible with -plain years too and supports many more features. See \secref{bib:use:dat}. +The year of publication. It is better to use the \bibfield{date} field as this is compatible with plain years too. See \secref{bib:use:dat}. \end{fieldlist} @@ -1170,7 +1156,6 @@ The gender of the author or the gender of the editor, if there is no author. The \multicolumn{1}{@{}H}{Region/Dialect} & \multicolumn{1}{@{}H}{Identifiers} \\ \cmidrule(r){1-1}\cmidrule(r){2-2}\cmidrule{3-3} -Bulgarian & Bulgaria & \opt{bulgarian} \\ Catalan & Spain, France, Andorra, Italy & \opt{catalan} \\ Croatian & Croatia, Bosnia and Herzegovina, Serbia & \opt{croatian} \\ Czech & Czech Republic & \opt{czech} \\ @@ -1192,16 +1177,15 @@ German (new) & Germany & \opt{ngerman} \\ & Switzerland & \opt{nswissgerman} \\ Greek & Greece & \opt{greek} \\ Italian & Italy & \opt{italian} \\ -Norwegian & Norway & \opt{norsk}, \opt{nynorsk} \\ +Norwegian & Norway & \opt{norwegian}, \opt{norsk}, \opt{nynorsk} \\ Polish & Poland & \opt{polish} \\ Portuguese & Brazil & \opt{brazil} \\ & Portugal & \opt{portuguese}, \opt{portuges} \\ Russian & Russia & \opt{russian} \\ Slovak & Slovakia & \opt{slovak} \\ -Slovene & Slovenia & \opt{slovene}, \opt{slovenian} \\ +Slovene & Slovenia & \opt{slovene} \\ Spanish & Spain & \opt{spanish} \\ Swedish & Sweden & \opt{swedish} \\ -Ukrainian & Ukraine & \opt{ukrainian} \\ \bottomrule \end{tabularx} \caption{Supported Languages} @@ -1292,9 +1276,9 @@ Similar to \bibfield{sortkey} but used in the list of shorthands. If present, \b A field used to modify the sorting order of the bibliography. If present, this field is used instead of the \bibfield{title} field when sorting the bibliography. The \bibfield{sorttitle} field may come in handy if you have an entry with a title like «An Introduction to\dots» and want that alphabetized under rather than . In this case, you could put «Introduction to\dots» in the \bibfield{sorttitle} field. Please refer to \secref{use:srt} for further details. This field is consumed by the backend processing and does not appear in the \path{.bbl}. -\fielditem{sortyear}{literal} +\fielditem{sortyear}{integer} -A field used to modify the sorting order of the bibliography. If present, this field is used instead of the \bibfield{year} field when sorting the bibliography. Please refer to \secref{use:srt} for further details. This field is consumed by the backend processing and does not appear in the \path{.bbl}. Note that this is not an integer but rather a literal field as sometimes things like «1984-1» are used to modify temporal sorting. +A field used to modify the sorting order of the bibliography. If present, this field is used instead of the \bibfield{year} field when sorting the bibliography. Please refer to \secref{use:srt} for further details. This field is consumed by the backend processing and does not appear in the \path{.bbl}. \fielditem{xdata}{separated list of entrykeys} @@ -1403,7 +1387,7 @@ Use the \bibtype{inbook} entry type for a self"=contained part of a book with it \subsubsection{Missing and Omissible Data} \label{bib:use:key} -The fields marked as in \secref{bib:typ:blx} are not strictly required in all cases. The bibliography styles which come with this package can get by with as little as a \bibfield{title} field for most entry types. A book published anonymously, a periodical without an explicit editor, or a software manual without an explicit author should pose no problem as far as the bibliography is concerned. Citation styles, however, may have different requirements. For example, an author"=year citation scheme obviously requires an \bibfield{author}\slash \bibfield{editor} and a \bibfield{year} field. +The fields marked as in \secref{bib:typ:blx} are not strictly required in all cases. The bibliography styles which ship with this package can get by with as little as a \bibfield{title} field for most entry types. A book published anonymously, a periodical without an explicit editor, or a software manual without an explicit author should pose no problem as far as the bibliography is concerned. Citation styles, however, may have different requirements. For example, an author"=year citation scheme obviously requires an \bibfield{author}\slash \bibfield{editor} and a \bibfield{year} field. You may generally use the \bibfield{label} field to provide a substitute for any missing data required for citations. How the \bibfield{label} field is employed depends on the citation style. The author"=year citation styles which come with this package use the \bibfield{label} field as a fallback if either the \bibfield{author}\slash \bibfield{editor} or the \bibfield{year} is missing. The numeric styles, on the other hand, do not use it at all since the numeric scheme is independent of the available data. The author"=title styles ignore it as well, because the bare \bibfield{title} is usually sufficient to form a unique citation and a title is expected to be available in any case. The \bibfield{label} field may also be used to override the non"=numeric portion of the automatically generated \bibfield{labelalpha} field used by alphabetic citation styles. See \secref{aut:bbx:fld} for details. @@ -1533,7 +1517,6 @@ The type of editorial role performed by an editor in one of the \bibfield{editor \item[redactor] A secondary editor whose task is redacting the work. \item[reviser] A secondary editor whose task is revising the work. \item[collaborator] A secondary editor or a consultant to the editor. -\item[organizer] Similar to \texttt{editor} but used if the task of the editor is mainly organizing. \end{marglist} % For example, if the task of the editor is compiling, you may indicate that in the corresponding \bibfield{editortype} field: @@ -1657,7 +1640,7 @@ open/1997 & --1997 & --1997 \\ Date fields such as the default data model dates \bibfield{date}, \bibfield{origdate}, \bibfield{eventdate}, and \bibfield{urldate} adhere to \acr{EDTF}\footnote{\url{https://www.loc.gov/standards/datetime/pre-submission.html}} (Extended Date/Time Format) specification levels 0 and 1. Also supported are the open-ended range specifications in section 4.5 of the current working draft of ISO8601-2\footnote{\url{http://www.loc.gov/standards/datetime/iso-tc154-wg5_n0039_iso_wd_8601-2_2016-02-16.pdf}}. \acr{EDTF} is a stricter subset of the somewhat messy formats allowed by \acr{ISO8601v2004} and is better suited to bibliographic data. In addition to the \acr{EDTF} empty date range markers, you may also specify an open ended/start date range by giving the range separator and omitting the end/start date (\eg \texttt{YYYY/}, \texttt{/YYYY}). See \tabref{bib:use:tab1} for some examples of valid date specifications and the formatted dates automatically generated by \biblatex. The formatted date is language specific and will be adapted automatically. If there is no \bibfield{date} field in an entry, \biblatex will also consider the fields \bibfield{year} and \bibfield{month} for backwards compatibility with traditional \bibtex but this is not encouraged as explicit \bibfield{year} and \bibfield{month} are not parsed for date meta-information markers or times and are used as-is. Style authors should note that date fields like \bibfield{date} or \bibfield{origdate} are only available in the \file{bib} file. All dates are parsed and dissected into their components as the \file{bib} file is processed. The date and time components are made available to styles by way of the special fields discussed in \secref{aut:bbx:fld:dat}. See this section and \tabref{aut:bbx:fld:tab1} on page~\pageref{aut:bbx:fld:tab1} for further information. -\acr{EDTF} dates are astronomical dates in which year <0> exists. When outputting dates in BCE or BC era (see the \opt{dateera} option below), note that they will typically be one year earlier since BCE/BC era do not have a year 0 (year 0 is 1 BCE/BC). This conversion is automatic. See examples in \tabref{bib:use:tab2}. +\acr{EDTF} dates are astronomical dates in which year <0> exists. When outputting dates in BCE or BC era (see the \opt{dateera} option below), note that they will typically be one year earlier since BCE/BC era do not have a year 0 (year 0 is 1 BCE/BC). This conversion is automatic. See examples in table \tabref{bib:use:tab2}. Date field names \emph{must} end with the string , as with the default date fields. Bear this in mind when adding new date fields to the datamodel (see \secref{aut:ctm:dm}). \biblatex will check all date fields after reading the date model and will exit with an error if it finds a date field which does not adhere to this naming convention. @@ -2006,10 +1989,10 @@ The sorting order of the bibliography. Unless stated otherwise, the entries are \item[ydnt] Sort by year (descending), name, title. \item[none] Do not sort at all. All entries are processed in citation order. \item[debug] Sort by entry key. This is intended for debugging only. -\item[\prm{name}] Use \prm{name}, as defined with \cmd{DeclareSortingTemplate} (\secref{aut:ctm:srt}) +\item[\prm{name}] Use \prm{name}, as defined with \cmd{DeclareSortingScheme} (\secref{aut:ctm:srt}) \end{valuelist} -Using any of the sorting templates only makes sense in conjunction with a bibliography style which prints the corresponding labels. Note that some bibliography styles initialize this package option to a value different from the package default (\opt{nty}). See \secref{use:xbx:bbx} for details. Please refer to \secref{use:srt} for an in"=depth explanation of the above sorting options as well as the fields considered in the sorting process. See also \secref{aut:ctm:srt} on how to adapt the predefined templates or define new ones. +Using any of the sorting schemes only makes sense in conjunction with a bibliography style which prints the corresponding labels. Note that some bibliography styles initialize this package option to a value different from the package default (\opt{nty}). See \secref{use:xbx:bbx} for details. Please refer to \secref{use:srt} for an in"=depth explanation of the above sorting options as well as the fields considered in the sorting process. See also \secref{aut:ctm:srt} on how to adapt the predefined schemes or define new ones. \boolitem[true]{sortcase} @@ -2021,7 +2004,7 @@ This option corresponds to \biber's \opt{--sortupper} command-line option. If en \optitem{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. +This option sets the global sorting locale. Every sorting scheme 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. \boolitem[true]{related} @@ -2029,11 +2012,7 @@ Whether or not to use information from related entries or not. See \secref{use:r \boolitem[false]{sortcites} -Whether or not to sort citations if multiple entry keys are passed to a citation command. If this option is enabled, citations are sorted according to the current bibliography context sorting template (see \secref{use:bib:context}). This feature works with all citation styles. - -\boolitem[false]{sortsets} - -Whether or not to sort set members according to the active reference context sorting scheme. By default this is false and set members appear in the order given in the data source. +Whether or not to sort citations if multiple entry keys are passed to a citation command. If this option is enabled, citations are sorted according to the current bibliography context sorting scheme (see \secref{use:bib:context}). This feature works with all citation styles. \intitem[3]{maxnames} @@ -2093,7 +2072,7 @@ This option controls which \sty{babel} language environment\footnote{\sty{polygl Disable this feature, \ie do not use any language environment at all. \item[hyphen] -Enclose the entry in a \env{hyphenrules} environment. This will load hyphenation patterns for the language specified in the \bibfield{langid} field of the entry, if available. +Enclose the entry in a \env{hyphenrules} environment. This will load hyphenation patterns for the language specified in the \env{hyphenation} field of the entry, if available. \item[other] Enclose the entry in an \env{otherlanguage} environment. This will load hyphenation patterns for the specified language, enable all extra definitions which \sty{babel}/\sty{polyglossia} and \biblatex provide for the respective language, and translate key terms such as and . The extra definitions include localisations of the date format, of ordinals, and similar things. @@ -2136,13 +2115,13 @@ This option controls the behavior of \cmd{mkbibfootnote}, \cmd{mkbibendnote}, an \item[endonly] Force endnotes, \ie make \cmd{mkbibfootnote} generate endnotes. \end{valuelist} -\optitem[auto]{hyperref}{\opt{true}, \opt{false}, \opt{auto}, \opt{manual}} +\optitem[auto]{hyperref}{\opt{true}, \opt{false}, \opt{auto}} -Whether or not to transform citations and back references into clickable hyperlinks. This feature requires the \sty{hyperref} package. It also requires support by the selected citation style. All standard styles which ship with this package support hyperlinks. \kvopt{hyperref}{auto} automatically detects if the \sty{hyperref} package has been loaded. This is the default setting. \kvopt{hyperref}{false} explicitly disables links even if \sty{hyperref} is loaded. \kvopt{hyperref}{true} enables links when \sty{hyperref} is loaded, it cannot explicitly enable links if \sty{hyperref} is not loaded, as such it works exactly like \kvopt{hyperref}{auto} except that it will issue a warning if \sty{hyperref} is not loaded. \kvopt{hyperref}{manual} gives full manual control over \sty{hyperref} interaction, it should only be needed by package authors in very special circumstances. With the \kvopt{hyperref}{manual} setting you are responsible to enable or disable \sty{hyperref} support manually with \cmd{BiblatexManualHyperrefOn} or \cmd{BiblatexManualHyperrefOff} yourself. One of the two commands must be called exactly once; \cmd{BiblatexManualHyperrefOn} can only be called after \sty{hyperref} is loaded. +Whether or not to transform citations and back references into clickable hyperlinks. This feature requires the \sty{hyperref} package. It also requires support by the selected citation style. All standard styles which ship with this package support hyperlinks. \kvopt{hyperref}{auto} automatically detects if the \sty{hyperref} package has been loaded. \boolitem[false]{backref} -Whether or not to print back references in the bibliography. The back references are a list of page numbers indicating the pages on which the respective bibliography entry is cited. If there are \env{refsection} environments in the document, the back references are local to the reference sections. Strictly speaking, this option only controls whether the \biblatex package collects the data required to print such references. This feature still has to be supported by the selected bibliography style. All standard styles which come with this package do so. +Whether or not to print back references in the bibliography. The back references are a list of page numbers indicating the pages on which the respective bibliography entry is cited. If there are \env{refsection} environments in the document, the back references are local to the reference sections. Strictly speaking, this option only controls whether the \biblatex package collects the data required to print such references. This feature still has to be supported by the selected bibliography style. All standard styles which ship with this package do so. \optitem[three]{backrefstyle}{\opt{none}, \opt{three}, \opt{two}, \opt{two+}, \opt{three+}, \opt{all+}} @@ -2197,7 +2176,7 @@ This option controls indexing in citations and in the bibliography. More precise \item[bib] Enable indexing in the bibliography only. \end{valuelist} -This feature requires support by the selected citation style. All standard styles which come with this package support indexing of both citations and entries in the bibliography. Note that you still need to enable indexing globally with \cmd{makeindex} to get an index. +This feature requires support by the selected citation style. All standard styles which ship with this package support indexing of both citations and entries in the bibliography. Note that you still need to enable indexing globally with \cmd{makeindex} to get an index. \boolitem[false]{loadfiles} @@ -2383,7 +2362,7 @@ Sets \opt{labeldateusetime} and the \opt{$<$datetype$>$dateusetime} option for a \boolitem[false]{defernumbers} -In contrast to standard \latex, the numeric labels generated by this package are normally assigned to the full list of references at the beginning of the document body. If this option is enabled, numeric labels (\ie the \bibfield{labelnumber} field discussed in \secref{aut:bbx:fld}) are assigned the first time an entry is printed in any bibliography. See \secref{use:cav:lab} for further explanation. This option requires two \latex runs after the data has been exported to the \file{bbl} file by the backend (in addition to any other runs required by page breaks changing etc.). An important thing to note is that if you are using this option, then changes to options, the \file{bib} file or certain commands like \cmd{printbibliography} will usually require that you delete your current \file{aux} file and re-run \latex to obtain the correct numbering. See \secref{aut:int}. +In contrast to standard \latex, the numeric labels generated by this package are normally assigned to the full list of references at the beginning of the document body. If this option is enabled, numeric labels (\ie the \bibfield{labelnumber} field discussed in \secref{aut:bbx:fld}) are assigned the first time an entry is printed in any bibliography. See \secref{use:cav:lab} for further explanation. This option requires two \latex runs after the data has been exported to the \file{bbl} file by the backend (in addition to any other runs required by page breaks changing etc.). An important thing to note is that if you change the value of this option in your document (or the value of options which depend on this like some of the options to the \cmd{printbibliography} macro, see \secref{use:bib:bib}), then it is likely that you will need to delete your current \file{aux} file and re-run \latex to obtain the correct numbering. See \secref{aut:int}. \boolitem[false]{punctfont} @@ -2617,7 +2596,7 @@ Whether or not to provide the special field \bibfield{extratitleyear}, see \secr \boolitem[false]{labeldateparts} -Whether or not to provide the special fields \bibfield{labelyear}, \bibfield{labelmonth}, \bibfield{labelday}, \bibfield{labelendyear}, \bibfield{labelendmonth}, \bibfield{labelendday}, \bibfield{labelhour}, \bibfield{labelendhour}, \bibfield{labelminute}, \bibfield{labelendminute}, \bibfield{labelsecond}, \bibfield{labelendsecond}, \bibfield{labelseason}, \bibfield{labelendseason}, \bibfield{labeltimezone}, \bibfield{labelendtimeone} and \bibfield{extradate}, see \secref{aut:bbx:fld} for details. +Whether or not to provide the special fields \bibfield{labelyear}, \bibfield{labelmonth}, \bibfield{labelday}, \bibfield{labelendyear}, \bibfield{labelendmonth}, \bibfield{labelendday}, \bibfield{labelhour}, \bibfield{labelendhour}, \bibfield{labelminute}, \bibfield{labelendminute}, \bibfield{labelsecond}, \bibfield{labelendsecond}, \bibfield{labelseason}, \bibfield{labelendseason}, \bibfield{labeltimezone}, \bibfield{labelendtimeone} and \bibfield{extrayear}, see \secref{aut:bbx:fld} for details. This option is also settable on a per-type basis. Table \ref{use:opt:tab1} summarises the various \opt{extra*} disambiguation counters and what they track. \begin{table} @@ -2676,11 +2655,11 @@ Whether or not to update the \cnt{uniquename} counter, see \secref{aut:aux:tst} \item[full] Disambiguate using initials or full names, as required. \item[allinit] Similar to \opt{init} but disambiguates all names in the \bibfield{labelname} list, beyond \opt{maxnames}\slash \opt{minnames}\slash \opt{uniquelist}. \item[allfull] Similar to \opt{full} but disambiguates all names in the \bibfield{labelname} list, beyond \opt{maxnames}\slash \opt{minnames}\slash \opt{uniquelist}. -\item[mininit] A variant of \texttt{init} which only disambiguates names in identical lists of base nameparts (by default, lists of family names). -\item[minfull] A variant of \texttt{full} which only disambiguates names in identical lists of base nameparts (by default, lists of family names). +\item[mininit] A variant of \texttt{init} which only disambiguates names in lists with identical last names. +\item[minfull] A variant of \texttt{full} which only disambiguates names in lists with identical last names. \end{valuelist} % -Note that the \opt{uniquename} option will also affect \opt{uniquelist}, the \cmd{ifsingletitle} test, and the \bibfield{extradate} field. See \secref{aut:cav:amb} for further details and practical examples. +Note that the \opt{uniquename} option will also affect \opt{uniquelist}, the \cmd{ifsingletitle} test, and the \bibfield{extrayear} field. See \secref{aut:cav:amb} for further details and practical examples. \optitem[false]{uniquelist}{\opt{true}, \opt{false}, \opt{minyear}} @@ -2692,7 +2671,7 @@ Whether or not to update the \cnt{uniquelist} counter, see \secref{aut:aux:tst} \item[minyear] Disambiguate the \bibfield{labelname} list only if the truncated list is identical to another one with the same \bibfield{labelyear}. This mode of operation is useful for author-year styles and requires \kvopt{labeldateparts}{true}. \end{valuelist} % -Note that the \opt{uniquelist} option will also affect the \cmd{ifsingletitle} test and the \bibfield{extradate} field. See \secref{aut:cav:amb} for further details and practical examples. +Note that the \opt{uniquelist} option will also affect the \cmd{ifsingletitle} test and the \bibfield{extrayear} field. See \secref{aut:cav:amb} for further details and practical examples. \end{optionlist} @@ -2708,7 +2687,7 @@ Note that the \opt{uniquelist} option will also affect the \cmd{ifsingletitle} t \multicolumn{1}{@{}H}{Counter tracks} \\ \cmidrule(r){1-1}\cmidrule(r){2-2}\cmidrule(r){3-3}\cmidrule{4-4} labelalpha & labelalpha & extraalpha & label\\ -labeldateparts & labelyear & extradate & labelname+\\ +labeldateparts & labelyear & extrayear & labelname+\\ & labelmonth & & labelyear\\ & labelday & & \\ & labelendyear & & \\ @@ -2779,14 +2758,14 @@ defined. Global, per-type and per-entry options called $>are automa Whether the default date model name part (von, van, of, da, de, della, etc.) is considered when: \begin{itemize} -\item Printing the family name in citations +\item Printing the last name in citations \item Sorting \item Generation of certain types of labels \item Generating name uniqueness information \item Formatting aspects of the bibliography \end{itemize} % -For example, if this option is enabled, \biblatex precedes the family name with the prefix---Ludwig van Beethoven would be cited as «van Beethoven» and alphabetized as «Van Beethoven, Ludwig». If this option is disabled (the default), he is cited as «Beethoven» and alphabetized as «Beethoven, Ludwig van» instead. +For example, if this option is enabled, \biblatex precedes the last name with the prefix---Ludwig van Beethoven would be cited as «van Beethoven» and alphabetized as «Van Beethoven, Ludwig». If this option is disabled (the default), he is cited as «Beethoven» and alphabetized as «Beethoven, Ludwig van» instead. This option is also settable on a per-type scope. With \biblatexml datasources and the \bibtex extended name format supported by \biber, this is also settable on per-namelist and per-name scopes. \optitem{indexing}{\opt{true}, \opt{false}, \opt{cite}, \opt{bib}} @@ -2850,7 +2829,7 @@ The following legacy option may be used globally in the optional argument to \cm \subsection{Global Customization} \label{use:cfg} -Apart from writing new citation and bibliography styles, there are numerous ways to customize the styles which come with this package. Customization will usually take place in the preamble, but there is also a configuration file for permanent adaptions. The configuration file may also be used to initialize the package options to a value different from the package default. +Apart from writing new citation and bibliography styles, there are numerous ways to customize the styles which ship with this package. Customization will usually take place in the preamble, but there is also a configuration file for permanent adaptions. The configuration file may also be used to initialize the package options to a value different from the package default. \subsubsection{Configuration File} \label{use:cfg:cfg} @@ -2873,7 +2852,7 @@ This command may also be used in the configuration file to modify the default se \subsection{Standard Styles} \label{use:xbx} -This section provides a short description of all bibliography and citation styles which come with the \biblatex package. If you want to write your own styles, see \secref{aut}. +This section provides a short description of all bibliography and citation styles which ship with the \biblatex package. If you want to write your own styles, see \secref{aut}. \subsubsection{Citation Styles} \label{use:xbx:cbx} @@ -2892,10 +2871,10 @@ A compact variant of the \texttt{numeric} style which prints a list of more than A verbose variant of the \texttt{numeric} style. The difference affects the handling of a list of citations and is only apparent when multiple entry keys are passed to a single citation command. For example, instead of «[2, 5, 6]» this style would print «[2]; [5]; [6]». It is intended for in-text citations. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labelnumber}{true}. It also provides the \opt{subentry} option. \item[alphabetic] -This style implements an alphabetic citation scheme similar to the \path{alpha.bst} style of traditional \bibtex. The alphabetic labels resemble a compact author"=year style to some extent, but the way they are employed is similar to a numeric citation scheme. For example, instead of «Jones 1995» this style would use the label «[Jon95]». «Jones and Williams 1986» would be rendered as «[JW86]». This style should be employed in conjunction with an alphabetic bibliography style which prints the corresponding labels in the bibliography. It is intended for in-text citations. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labelalpha}{true}. This style also provides an additional preamble option called \opt{subentry} which affects the handling of entry sets. If this option is disabled, citations referring to a member of a set will point to the entire set. If it is enabled, the style supports citations like «[SGW(c)]» which point to a subentry in a set (the third one in this example). See the style example for details. +This style implements an alphabetic citation scheme similar to the \path{alpha.bst} style of traditional \bibtex. The alphabetic labels resemble a compact author"=year style to some extent, but the way they are employed is similar to a numeric citation scheme. For example, instead of «Jones 1995» this style would use the label «[Jon95]». «Jones and Williams 1986» would be rendered as «[JW86]». This style should be employed in conjunction with an alphabetic bibliography style which prints the corresponding labels in the bibliography. It is intended for in-text citations. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labelalpha}{true}. \item[alphabetic-verb] -A verbose variant of the \texttt{alphabetic} style. The difference affects the handling of a list of citations and is only apparent when multiple entry keys are passed to a single citation command. For example, instead of «[Doe92; Doe95; Jon98]» this style would print «[Doe92]; [Doe95]; [Jon98]». It is intended for in-text citations. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labelalpha}{true}. It also provides the subentry option. +A verbose variant of the \texttt{alphabetic} style. The difference affects the handling of a list of citations and is only apparent when multiple entry keys are passed to a single citation command. For example, instead of «[Doe92; Doe95; Jon98]» this style would print «[Doe92]; [Doe95]; [Jon98]». It is intended for in-text citations. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labelalpha}{true}. \item[authoryear] This style implements an author"=year citation scheme. If the bibliography contains two or more works by the same author which were all published in the same year, a letter is appended to the year. For example, this style would print citations such as «Doe 1995a; Doe 1995b; Jones 1998». This style should be employed in conjunction with an author"=year bibliography style which prints the corresponding labels in the bibliography. It is primarily intended for in-text citations, but it could also be used with citations given in footnotes. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labeldateparts}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}. @@ -3083,11 +3062,11 @@ You can use the \bibfield{relatedoptions} to set options on the related entry da \subsection{Sorting Options} \label{use:srt} -This package supports fully customisable sorting templates for the bibliography. The default global sorting template is selected with the \opt{sorting} package option from \secref{use:opt:pre:gen}. Apart from the regular data fields there are also some special fields which may be used to optimize the sorting of the bibliography. \Apxref{apx:srt:a1, apx:srt:a2} give an outline of the default alphabetic sorting templates supported by \biblatex. Chronological sorting templates are listed in \apxref{apx:srt:chr}. A few explanations concerning the default templates are in order. +This package supports various sorting schemes for the bibliography. The sorting scheme is selected with the \opt{sorting} package option from \secref{use:opt:pre:gen}. Apart from the regular data fields there are also some special fields which may be used to optimize the sorting of the bibliography. \Apxref{apx:srt:a1, apx:srt:a2} give an outline of the alphabetic sorting schemes supported by \biblatex. Chronological sorting schemes are listed in \apxref{apx:srt:chr}. A few explanations concerning these schemes are in order. -The first item considered in the sorting process is always the \bibfield{presort} field of the entry. If this field is undefined, \biblatex will use the default value <\texttt{mm}> as a presort string. The next item considered is the \bibfield{sortkey} field. If this field is defined, it serves as the master sort key. Apart from the \bibfield{presort} field, no further data is considered in this case. If the \bibfield{sortkey} field is undefined, sorting continues with the name. The package will try using the \bibfield{sortname}, \bibfield{author}, \bibfield{editor}, and \bibfield{translator} fields, in this order. Which fields are considered also depends on the setting of the \opt{use$<$name$>$} options. If all such options are disabled, the \bibfield{sortname} field is ignored as well. Note that all name fields are responsive to \opt{maxnames} and \opt{minnames}. If no name field is available, either because all of them are undefined or because all \opt{use$<$name$>$} options are disabled, \biblatex will fall back to the \bibfield{sorttitle} and \bibfield{title} fields as a last resort. The remaining items are, in various order: the \bibfield{sortyear} field, if defined, or the first four digits of the \bibfield{year} field otherwise; the \bibfield{sorttitle} field, if defined, or the \bibfield{title} field otherwise; the \bibfield{volume} field. Note that the sorting templates shown in \apxref{apx:srt:a2} include an additional item: \bibfield{labelalpha} is the label used by bibliography styles. Strictly speaking, the string used for sorting is \bibfield{labelalpha}~+ \bibfield{extraalpha}. The sorting templates in \apxref{apx:srt:a2} are intended to be used in conjunction with alphabetic styles only. +The first item considered in the sorting process is always the \bibfield{presort} field of the entry. If this field is undefined, \biblatex will use the default value <\texttt{mm}> as a presort string. The next item considered is the \bibfield{sortkey} field. If this field is defined, it serves as the master sort key. Apart from the \bibfield{presort} field, no further data is considered in this case. If the \bibfield{sortkey} field is undefined, sorting continues with the name. The package will try using the \bibfield{sortname}, \bibfield{author}, \bibfield{editor}, and \bibfield{translator} fields, in this order. Which fields are considered also depends on the setting of the \opt{use$<$name$>$} options. If all such options are disabled, the \bibfield{sortname} field is ignored as well. Note that all name fields are responsive to \opt{maxnames} and \opt{minnames}. If no name field is available, either because all of them are undefined or because all \opt{use$<$name$>$} options are disabled, \biblatex will fall back to the \bibfield{sorttitle} and \bibfield{title} fields as a last resort. The remaining items are, in various order: the \bibfield{sortyear} field, if defined, or the first four digits of the \bibfield{year} field otherwise; the \bibfield{sorttitle} field, if defined, or the \bibfield{title} field otherwise; the \bibfield{volume} field. Note that the sorting schemes shown in \apxref{apx:srt:a2} include an additional item: \bibfield{labelalpha} is the label used by bibliography styles. Strictly speaking, the string used for sorting is \bibfield{labelalpha}~+ \bibfield{extraalpha}. The sorting schemes in \apxref{apx:srt:a2} are intended to be used in conjunction with alphabetic styles only. -The chronological sorting templates presented in \apxref{apx:srt:chr} also make use of the \bibfield{presort} and \bibfield{sortkey} fields, if defined. The next item considered is the \bibfield{sortyear} or the \bibfield{year} field, depending on availability. The \opt{ynt} template extracts the first four Arabic figures from the field. If both fields are undefined, the string \texttt{9999} is used as a fallback value. This means that all entries without a year will be moved to the end of the list. The \opt{ydnt} template is similar in concept but sorts the year in descending order. As with the \opt{ynt} template, the string \texttt{9999} is used as a fallback value. The remaining items are similar to the alphabetic sorting templates discussed above. Note that the \opt{ydnt} sorting template will only sort the date in descending order. All other items are sorted in ascending order as usual. +The chronological sorting schemes presented in \apxref{apx:srt:chr} also make use of the \bibfield{presort} and \bibfield{sortkey} fields, if defined. The next item considered is the \bibfield{sortyear} or the \bibfield{year} field, depending on availability. The \opt{ynt} scheme extracts the first four Arabic figures from the field. If both fields are undefined, the string \texttt{9999} is used as a fallback value. This means that all entries without a year will be moved to the end of the list. The \opt{ydnt} scheme is similar in concept but sorts the year in descending order. As with the \opt{ynt} scheme, the string \texttt{9999} is used as a fallback value. The remaining items are similar to the alphabetic sorting schemes discussed above. Note that the \opt{ydnt} sorting scheme will only sort the date in descending order. All other items are sorted in ascending order as usual. Using special fields such as \bibfield{sortkey}, \bibfield{sortname}, or \bibfield{sorttitle} is usually not required. The \biblatex package is quite capable of working out the desired sorting order by using the data found in the regular fields of an entry. You will only need them if you want to manually modify the sorting order of the bibliography or if any data required for sorting is missing. Please refer to the field descriptions in \secref{bib:fld:spc} for details on possible uses of the special fields. @@ -3218,7 +3197,7 @@ To put the given and family names of name list items annotated as «correspondin \cmditem{addbibresource}[options]{resource} -Adds a \prm{resource}, such as a \file{.bib} file, to the default resource list. This command is only available in the preamble. It replaces the \cmd{bibliography} legacy command. Note that files must be specified with their full name, including the extension. Do not omit the \file{.bib} extension from the filename. Also note that the \prm{resource} is a single resource. If the resources contain duplicate entries (that is, duplicate \bibfield{entrykey}s), it is backend dependent what then happens. For example, by default \biber will ignore further occurrence of \bibfield{entrykey}s unless its \opt{--noskipduplicates} options is used. Invoke \cmd{addbibresource} multiple times to add more resources, for example: +Adds a \prm{resource}, such as a \file{.bib} file, to the default resource list. This command is only available in the preamble. It replaces the \cmd{bibliography} legacy command. Note that files must be specified with their full name, including the extension. Do not omit the \file{.bib} extension from the filename. Also note that the \prm{resource} is a single resource. Invoke \cmd{addbibresource} multiple times to add more resources, for example: \begin{ltxexample} \addbibresource{bibfile1.bib} @@ -3265,7 +3244,7 @@ This command differs from \cmd{addbibresource} in that the \prm{resource} is add This command differs from \cmd{addbibresource} in that the resource \prm{options} are registered but the \prm{resource} not added to any resource list. This is only required for resources which 1) are given exclusively in the optional argument of \env{refsection} (\secref{use:bib:sec}) and 2) require options different from the default settings. In this case, \cmd{addsectionbib} is employed to qualify the \prm{resource} prior to using it by setting the appropriate \prm{options} in the preamble. The \opt{label} option may be useful to assign a short name to the resource. -\cmditem{bibliography}{bibfile, \dots}\DeprecatedMark +\cmditem{bibliography}{bibfile, \dots}|\DeprecatedMark| The legacy command for adding bibliographic resources, supported for backwards compatibility. Like \cmd{addbibresource}, this command is only available in the preamble and adds resources to the default resource list. Its argument is a comma"=separated list of \file{bib} files. The \file{.bib} extension may be omitted from the filename. Invoking this command multiple times to add more files is permissible. This command is deprecated. Please consider using \cmd{addbibresource} instead. @@ -3362,15 +3341,15 @@ This option applies to numerical citation\slash bibliography styles only and req \cmditem{bibbysection}[key=value, \dots] -This command automatically loops over all reference sections. This is equivalent to giving one \cmd{printbibliography} command for every section but has the additional benefit of automatically skipping sections without references. Note that \cmd{bibbysection} starts looking for references in section \texttt{1}. It will ignore references given outside of \env{refsection} environments since they are assigned to section~0. See \secref{use:use:mlt} for usage examples. The options are a subset of those supported by \cmd{printbibliography}. Valid options are \opt{env}, \opt{heading}, \opt{prenote}, \opt{postnote}. The current bibliography context sorting template is used for all sections (see \secref{use:bib:context}). +This command automatically loops over all reference sections. This is equivalent to giving one \cmd{printbibliography} command for every section but has the additional benefit of automatically skipping sections without references. Note that \cmd{bibbysection} starts looking for references in section \texttt{1}. It will ignore references given outside of \env{refsection} environments since they are assigned to section~0. See \secref{use:use:mlt} for usage examples. The options are a subset of those supported by \cmd{printbibliography}. Valid options are \opt{env}, \opt{heading}, \opt{prenote}, \opt{postnote}. The current bibliography context sorting scheme is used for all sections (see \secref{use:bib:context}). \cmditem{bibbysegment}[key=value, \dots] -This command automatically loops over all reference segments. This is equivalent to giving one \cmd{printbibliography} command for every segment in the current \env{refsection} but has the additional benefit of automatically skipping segments without references. Note that \cmd{bibbysegment} starts looking for references in segment \texttt{1}. It will ignore references given outside of \env{refsegment} environments since they are assigned to segment~0. See \secref{use:use:mlt} for usage examples. The options are a subset of those supported by \cmd{printbibliography}. Valid options are \opt{env}, \opt{heading}, \opt{prenote}, \opt{postnote}. The current bibliography context sorting template is used for all segments (see \secref{use:bib:context}). +This command automatically loops over all reference segments. This is equivalent to giving one \cmd{printbibliography} command for every segment in the current \env{refsection} but has the additional benefit of automatically skipping segments without references. Note that \cmd{bibbysegment} starts looking for references in segment \texttt{1}. It will ignore references given outside of \env{refsegment} environments since they are assigned to segment~0. See \secref{use:use:mlt} for usage examples. The options are a subset of those supported by \cmd{printbibliography}. Valid options are \opt{env}, \opt{heading}, \opt{prenote}, \opt{postnote}. The current bibliography context sorting scheme is used for all segments (see \secref{use:bib:context}). \cmditem{bibbycategory}[key=value, \dots] -This command loops over all bibliography categories. This is equivalent to giving one \cmd{printbibliography} command for every category but has the additional benefit of automatically skipping empty categories. The categories are processed in the order in which they were declared. See \secref{use:use:mlt} for usage examples. The options are a subset of those supported by \cmd{printbibliography}. Valid options are \opt{env}, \opt{prenote}, \opt{postnote}, \opt{section}. Note that \opt{heading} is not available with this command. The name of the current category is automatically used as the heading name. This is equivalent to passing \texttt{heading=\prm{category}} to \cmd{printbibliography} and implies that there must be a matching heading definition for every category. The current bibliography context sorting template is used for all categories (see \secref{use:bib:context}). +This command loops over all bibliography categories. This is equivalent to giving one \cmd{printbibliography} command for every category but has the additional benefit of automatically skipping empty categories. The categories are processed in the order in which they were declared. See \secref{use:use:mlt} for usage examples. The options are a subset of those supported by \cmd{printbibliography}. Valid options are \opt{env}, \opt{prenote}, \opt{postnote}, \opt{section}. Note that \opt{heading} is not available with this command. The name of the current category is automatically used as the heading name. This is equivalent to passing \texttt{heading=\prm{category}} to \cmd{printbibliography} and implies that there must be a matching heading definition for every category. The current bibliography context sorting scheme is used for all categories (see \secref{use:bib:context}). \cmditem{printbibheading}[key=value, \dots] @@ -3378,7 +3357,7 @@ This command prints a bibliography heading defined with \cmd{defbibheading}. It \end{ltxsyntax} % -To print a bibliography with a different sorting template than the global sorting template, use the bibliography context switching commands from \secref{use:bib:context}. +To print a bibliography with a different sorting scheme than the global sorting scheme, use the bibliography context switching commands from \secref{use:bib:context}. \subsubsection{Bibliography Lists} \label{use:bib:biblist} @@ -3399,10 +3378,10 @@ The \prm{biblistname} is a mandatory argument which names the bibliography list. \item A default 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 +\item The default sorting scheme name 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}). +In terms of sorting the list, the default is to sort use the sorting scheme named after the bibliography list (if it exists) and only then to fall back to the current context sorting scheme is 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: @@ -3437,13 +3416,13 @@ Since \bibfield{shortjournal} is defined in the default data model as a