summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/biblatex
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2013-07-11 23:36:27 +0000
committerKarl Berry <karl@freefriends.org>2013-07-11 23:36:27 +0000
commit275a02abde664ff395868e975c7c06d89276ac0b (patch)
treec315179a8d6f30c65f89152a70176afa828cc7e7 /Master/texmf-dist/doc/latex/biblatex
parent40e239851e66f62ec8d3092c746e61151b445b6f (diff)
biblatex (10jul13)
git-svn-id: svn://tug.org/texlive/trunk@31176 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/latex/biblatex')
-rw-r--r--Master/texmf-dist/doc/latex/biblatex/RELEASE9
-rw-r--r--Master/texmf-dist/doc/latex/biblatex/biblatex.pdfbin1089976 -> 1089795 bytes
-rw-r--r--Master/texmf-dist/doc/latex/biblatex/biblatex.tex520
-rw-r--r--Master/texmf-dist/doc/latex/biblatex/examples/03-localization-keys.tex2
4 files changed, 289 insertions, 242 deletions
diff --git a/Master/texmf-dist/doc/latex/biblatex/RELEASE b/Master/texmf-dist/doc/latex/biblatex/RELEASE
index 5c55e0ffaf5..755042a7db8 100644
--- a/Master/texmf-dist/doc/latex/biblatex/RELEASE
+++ b/Master/texmf-dist/doc/latex/biblatex/RELEASE
@@ -1,3 +1,12 @@
+RELEASE NOTES FOR VERSION 2.7
+
+* Biber version 1.7 is required for biblatex 2.7
+
+* New field EVENTTITLEADDON now part of default data model and default styles
+
+* Many citation command enhancements, better flow-of-text integration for
+ \textcite et al. See changelog in PDF doc for details.
+
RELEASE NOTES FOR VERSION 2.6
* Biber version 1.6 is required for biblatex 2.6
diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf b/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf
index 67ed6c091d0..03541be3961 100644
--- a/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf
+++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
index e7c01bb5d98..1371e490bba 100644
--- a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
+++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
@@ -1,9 +1,12 @@
\documentclass{ltxdockit}[2011/03/25]
\usepackage{btxdockit}
\usepackage{fontspec}
-\setmainfont[Ligatures=TeX]{TeXGyrePagella}
-\setsansfont[Ligatures=TeX]{TexGyreHeros}
-\setmonofont[Ligatures=NoCommon]{TeXGyreCursor}
+\usepackage[mono=false]{libertine}
+% http://www.ctan.org/pkg/dejavu
+\setmonofont[Scale=MatchLowercase]{DejaVu Sans Mono}
+%\setmainfont[Ligatures=TeX]{TeXGyrePagella}
+%\setsansfont[Ligatures=TeX]{TexGyreHeros}
+%\setmonofont[Ligatures=NoCommon]{TeXGyreCursor}
\usepackage[american]{babel}
\usepackage[strict]{csquotes}
\usepackage{tabularx}
@@ -16,11 +19,14 @@
\areaset[current]{370pt}{700pt}
\lstset{basicstyle=\ttfamily,keepspaces=true}
\KOMAoptions{numbers=noenddot}
+\addtokomafont{title}{\sffamily}
\addtokomafont{paragraph}{\spotcolor}
\addtokomafont{section}{\spotcolor}
\addtokomafont{subsection}{\spotcolor}
\addtokomafont{subsubsection}{\spotcolor}
\addtokomafont{descriptionlabel}{\spotcolor}
+\setkomafont{caption}{\bfseries\sffamily\spotcolor}
+\setkomafont{captionlabel}{\bfseries\sffamily\spotcolor}
\pretocmd{\cmd}{\sloppy}{}{}
\pretocmd{\bibfield}{\sloppy}{}{}
\pretocmd{\bibtype}{\sloppy}{}{}
@@ -44,10 +50,10 @@
title={The \sty{biblatex} Package},
subtitle={Programmable Bibliographies and Citations},
url={\biblatexhome},
- author={Philipp Lehman (with Audrey Boruvka, Philip Kime and Joseph Wright)},
+ author={Philipp Lehman \\(with Philip Kime, Audrey Boruvka and Joseph Wright)},
email={},
- revision={2.6},
- date={30/04/2013}}
+ revision={2.7},
+ date={07/07/2013}}
\hypersetup{%
pdftitle={The \biblatex Package},
@@ -146,7 +152,7 @@ This package provides advanced bibliographic facilities for use with \latex in c
\subsection{License}
-Copyright \textcopyright\ 2006--2012 Philipp Lehman. Permission is granted to copy, distribute and\slash or modify this software under the terms of the \lppl, version 1.3.\fnurl{http://www.ctan.org/tex-archive/macros/latex/base/lppl.txt}.
+Copyright \textcopyright\ 2006--2012 Philipp Lehman, 2012--2013 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.ctan.org/tex-archive/macros/latex/base/lppl.txt}
\subsection{Feedback}
\label{int:feb}
@@ -168,6 +174,7 @@ Apostolos Syropoulos, Prokopis (Greek);
Baldur Kristinsson (Icelandic);
Enrico Gregorio, Andrea Marchitelli (Italian);
Håkon Malmedal (Norwegian);
+Anastasia Kandulina, Yuriy Chernyshov (Polish);
José Carlos Santos (Portuguese);
Oleg Domanov (Russian);
Ignacio Fernández Galván (Spanish);
@@ -197,6 +204,9 @@ The \sty{biblatex} package can use legacy \bibtex as a data backend. While a leg
\item[etoolbox]
This \latex package, which is loaded automatically, provides generic programming facilities required by \sty{biblatex}. It is available from \acr{CTAN}.\fnurl{http://www.ctan.org/tex-archive/macros/latex/contrib/etoolbox/}
+\item[kvoptions]
+This \latex package, which is also loaded automatically, is used for internal option handling. It is available with the \sty{oberdiek} package bundle from \acr{CTAN}.\fnurl{http://www.ctan.org/pkg/kvoptions}
+
\item[logreq]
This \latex package, which is also loaded automatically, provides a frontend for writing machine-readable messages to an auxiliary log file. It is available from \acr{CTAN}.\fnurl{http://www.ctan.org/tex-archive/macros/latex/contrib/logreq/}
@@ -217,6 +227,9 @@ The \sty{babel} package provides the core architecture for multilingual typesett
\item[csquotes]
If this package is available, \sty{biblatex} will use its language sensitive quotation facilities to enclose certain titles in quotation marks. If not, \sty{biblatex} uses quotes suitable for American English as a fallback. When writing in any other language, loading \sty{csquotes} is strongly recommended.\fnurl{http://www.ctan.org/tex-archive/macros/latex/contrib/csquotes/}
+\item[xpatch]
+The \sty{xpatch} package extends the patching commands of \sty{etoolbox} to \sty{biblatex} bibliography macros, drivers and formatting directives.\fnurl{http://www.ctan.org/tex-archive/macros/latex/contrib/xpatch/}
+
\end{marglist}
\subsubsection{Compatible Classes and Packages}
@@ -299,6 +312,9 @@ The \sty{natbib} package supports numeric and author"=year citation schemes, inc
\item[splitbib]
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 \sty{biblatex} \texttt{refsection} and \texttt{refsegment} 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.
@@ -314,12 +330,13 @@ during processing if it encounters information which comes from a
compatibility matrix for the recent versions.
\begin{table}
-\begin{center}
-\small
-\begin{tabular}{lllll}
+\tablesetup\centering
+\begin{tabular}{cc}
\toprule
-Biber version & \biblatex\ version\\
+\sffamily\bfseries\spotcolor Biber version
+ & \sffamily\bfseries\spotcolor \biblatex\ version\\
\midrule
+1.7 & 2.7\\
1.6 & 2.6\\
1.5 & 2.5\\
1.4 & 2.4\\
@@ -339,7 +356,6 @@ Biber version & \biblatex\ version\\
0.9 & 1.4x\\
\bottomrule
\end{tabular}
-\end{center}
\caption{\biber/\biblatex\ compatibility matrix}
\label{tab:int:pre:bibercompat}
\end{table}
@@ -475,21 +491,21 @@ Supplemental material in a \bibtype{periodical}. This type is similar to \bibtyp
A single"=volume conference proceedings. This type is very similar to \bibtype{collection}. It supports an optional \bibfield{organization} field which holds the sponsoring institution. The \bibfield{editor} is omissible in terms of \secref{bib:use:key}.
\reqitem{editor, title, year/date}
-\optitem{subtitle, titleaddon, maintitle, mainsubtitle, maintitleaddon, eventtitle, eventdate, venue, language, volume, part, volumes, series, number, note, organization, publisher, location, month, isbn, chapter, pages, pagetotal, addendum, pubstate, doi, eprint, eprintclass, eprinttype, url, urldate}
+\optitem{subtitle, titleaddon, maintitle, mainsubtitle, maintitleaddon, eventtitle, eventtitleaddon, eventdate, venue, language, volume, part, volumes, series, number, note, organization, publisher, location, month, isbn, chapter, pages, pagetotal, addendum, pubstate, doi, eprint, eprintclass, eprinttype, url, urldate}
\typeitem{mvproceedings}
A multi"=volume \bibtype{proceedings} entry. For backwards compatibility, multi"=volume proceedings are also supported by the entry type \bibtype{proceedings}. However, it is advisable to make use of the dedicated entry type \bibtype{mvproceedings}
\reqitem{editor, title, year/date}
-\optitem{subtitle, titleaddon, eventtitle, eventdate, venue, language, volumes, series, number, note, organization, publisher, location, month, isbn, pagetotal, addendum, pubstate, doi, eprint, eprintclass, eprinttype, url, urldate}
+\optitem{subtitle, titleaddon, eventtitle, eventtitleaddon, eventdate, venue, language, volumes, series, number, note, organization, publisher, location, month, isbn, pagetotal, addendum, pubstate, doi, eprint, eprintclass, eprinttype, url, urldate}
\typeitem{inproceedings}
An article in a conference proceedings. This type is similar to \bibtype{incollection}. It supports an optional \bibfield{organization} field.
\reqitem{author, editor, title, booktitle, year/date}
-\optitem{subtitle, titleaddon, maintitle, mainsubtitle, maintitleaddon, booksubtitle, booktitleaddon, eventtitle, eventdate, venue, language, volume, part, volumes, series, number, note, organization, publisher, location, month, isbn, chapter, pages, addendum, pubstate, doi, eprint, eprintclass, eprinttype, url, urldate}
+\optitem{subtitle, titleaddon, maintitle, mainsubtitle, maintitleaddon, booksubtitle, booktitleaddon, eventtitle, eventtitleaddon, eventdate, venue, language, volume, part, volumes, series, number, note, organization, publisher, location, month, isbn, chapter, pages, addendum, pubstate, doi, eprint, eprintclass, eprinttype, url, urldate}
\typeitem{reference}
@@ -642,7 +658,7 @@ This section gives an overview of the fields supported by the \sty{biblatex} def
\subsubsection{Data Types}
\label{bib:fld:typ}
-In datasources such as a \file{bib} file, all bibliographic data is specified in fields. Some of those fields, for example \bibfield{author} and \bibfield{editor}, may contain a list of items. This list structure is implemented by the \bibtex file format via the keyword <|and|>, which is used to separate the individual items in the list. The \sty{biblatex} package implements three distinct data types to handle bibliographic data: name lists, literal lists, and fields. There are also several list and field subtypes. This section gives an overview of the data types supported by this package. See \secref{bib:fld:dat, bib:fld:spc} for information about the mapping of the \bibtex file format fields to \sty{biblatex}'s data types.
+In datasources such as a \file{bib} file, all bibliographic data is specified in fields. Some of those fields, for example \bibfield{author} and \bibfield{editor}, may contain a list of items. This list structure is implemented by the \bibtex file format via the keyword <|and|>, which is used to separate the individual items in the list. The \sty{biblatex} package implements three distinct data types to handle bibliographic data: name lists, literal lists, and fields. There are also several list and field subtypes and a content type which can be used to semantically distinguish fields which are otherwise not distinguishable on the basis of only their datatype (see \secref{aut:ctm:dm}). This section gives an overview of the data types supported by this package. See \secref{bib:fld:dat, bib:fld:spc} for information about the mapping of the \bibtex file format fields to \sty{biblatex}'s data types.
\begin{description}
@@ -669,7 +685,9 @@ In datasources such as a \file{bib} file, all bibliographic data is specified in
\item[Range fields] are literal fields with one special feature: all dashes are normalized and replaced by the command \cmd{bibrangedash}. 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 \BiberOnlyMark\cmd{bibrangessep} command which can be used to customise the separator between multiple ranges.
-\item[Integer fields] hold unformatted integers which may be converted to ordinals or strings as they are printed. A typical example is the \bibfield{month} field.
+\item[Integer fields] hold unformatted integers which may be converted to ordinals or strings as they are printed. A typical example is the \bibfield{extrayear} field.
+
+\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.
\item[Date fields] hold a date specification in \texttt{yyyy-mm-dd} format or a date range in \texttt{yyyy-mm-dd/yyyy-mm-dd} format. Date fields are special in that the date is parsed and split up into its components. See \secref{bib:use:dat} for details. A typical example is the \bibfield{date} field.
@@ -823,6 +841,10 @@ The date of a conference, a symposium, or some other event in \bibtype{proceedin
The title of a conference, a symposium, or some other event in \bibtype{proceedings} and \bibtype{inproceedings} entries. This field may also be useful for the custom types listed in \secref{bib:typ:ctm}. Note that this field holds the plain title of the event. Things like «Proceedings of the Fifth XYZ Conference» go into the \bibfield{titleaddon} or \bibfield{booktitleaddon} field, respectively. See also \bibfield{eventdate} and \bibfield{venue}.
+\fielditem{eventtitleaddon}{literal}
+
+An annex to the \bibfield{eventtitle} field. Can be used for known event acronyms, for example.
+
\fielditem{file}{verbatim}
A local link to a \acr{pdf} or other version of the work. Not used by the standard bibliography styles.
@@ -923,7 +945,7 @@ 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}{integer}
+\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. See also \bibfield{date} as well as \secref{bib:use:iss, bib:use:dat}.
@@ -1098,33 +1120,37 @@ The gender of the author or the gender of the editor, if there is no author. The
\begin{table}
\tablesetup
-\begin{tabularx}{\textwidth}{@{}p{100pt}@{}p{150pt}@{}X@{}}
+\begin{tabularx}{\textwidth}{@{}p{80pt}@{}p{170pt}@{}X@{}}
\toprule
\multicolumn{1}{@{}H}{Language} &
\multicolumn{1}{@{}H}{Region/Dialect} &
-\multicolumn{1}{@{}H}{Babel Identifiers} \\
+\multicolumn{1}{@{}H}{Identifiers} \\
\cmidrule(r){1-1}\cmidrule(r){2-2}\cmidrule{3-3}
-Catalan & Spain, France, Andorra, Italy & \opt{catalan} \\
-Czech & Czech Republic & \opt{czech} \\
-Danish & Denmark & \opt{danish} \\
-Dutch & Netherlands & \opt{dutch} \\
-English & USA & \opt{american}, \opt{USenglish}, \opt{english} \\
- & United Kingdom & \opt{british}, \opt{UKenglish} \\
- & Canada & \opt{canadian} \\
- & Australia & \opt{australian} \\
- & New Zealand & \opt{newzealand} \\
-Finnish & Finland & \opt{finnish} \\
-French & France, Canada & \opt{french}, \opt{francais}, \opt{canadien} \\
-German & Germany & \opt{german}, \opt{ngerman} \\
- & Austria & \opt{austrian}, \opt{naustrian} \\
-Greek & Greece & \opt{greek} \\
-Italian & Italy & \opt{italian} \\
-Norwegian & Norway & \opt{norsk}, \opt{nynorsk} \\
-Portuguese& Brazil & \opt{brazil} \\
- & Portugal & \opt{portuges} \\
-Russian & Russia & \opt{russian} \\
-Spanish & Spain & \opt{spanish} \\
-Swedish & Sweden & \opt{swedish} \\
+Catalan & Spain, France, Andorra, Italy & \opt{catalan} \\
+Croatian & Croatia, Bosnia and Herzegovina, Serbia & \opt{croatian} \\
+Czech & Czech Republic & \opt{czech} \\
+Danish & Denmark & \opt{danish} \\
+Dutch & Netherlands & \opt{dutch} \\
+English & USA & \opt{american}, \opt{USenglish}, \opt{english} \\
+ & United Kingdom & \opt{british}, \opt{UKenglish} \\
+ & Canada & \opt{canadian} \\
+ & Australia & \opt{australian} \\
+ & New Zealand & \opt{newzealand} \\
+Finnish & Finland & \opt{finnish} \\
+French & France, Canada & \opt{french} \\
+German & Germany & \opt{german} \\
+ & Austria & \opt{austrian} \\
+German (new) & Germany & \opt{ngerman} \\
+ & Austria & \opt{naustrian} \\
+Greek & Greece & \opt{greek} \\
+Italian & Italy & \opt{italian} \\
+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} \\
+Spanish & Spain & \opt{spanish} \\
+Swedish & Sweden & \opt{swedish} \\
\bottomrule
\end{tabularx}
\caption{Supported Languages}
@@ -1151,11 +1177,11 @@ indexsorttitle = {LATEX Companion},
%
Style authors should note that \sty{biblatex} automatically copies the value of either the \bibfield{indextitle} or the \bibfield{title} field to \bibfield{indexsorttitle} if the latter field is undefined.
-\fielditem{keywords}{comma-separated values}
+\fielditem{keywords}{comma"=separated values}
A comma"=separated list of keywords. These keywords are intended for the bibliography filters (see \secref{use:bib:bib, use:use:div}), they are usually not printed. Note that spaces after commas are ignored.
-\fielditem{options}{comma-separated \keyval options}
+\fielditem{options}{comma"=separated \keyval options}
A comma"=separated list of entry options in \keyval notation. This field is used to set options on a per"=entry basis. See \secref{use:opt:bib} for details. Note that citation and bibliography styles may define additional entry options.
@@ -1201,7 +1227,7 @@ A field used to modify the sorting order of the bibliography. If present, this f
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}{comma-separated list of entrykeys\BiberOnlyMark}
+\fielditem{xdata}{comma"=separated list of entrykeys\BiberOnlyMark}
This field inherits data from one or more \bibtype{xdata} entries. Conceptually, the \bibfield{xdata} field is related to \bibfield{crossref} and \bibfield{xref}: \bibfield{crossref} establishes a logical parent/child relation and inherits data; \bibfield{xref} establishes as logical parent/child relation without inheriting data; \bibfield{xdata} inherits data without establishing a relation. The value of the \bibfield{xdata} may be a single entry key or a comma"=separated list of keys. See \secref{use:use:xdat} for further details. This field is consumed by the backend processing and does not appear in the \path{.bbl}.
@@ -2064,45 +2090,7 @@ This option controls whether the citation commands scan ahead for punctuation ma
\optitem[auto]{language}{\opt{auto}, \prm{language}}
-This option controls multilingual support. When set to \opt{auto}, \sty{biblatex} will try to get the main document language from the \sty{babel} package (and fall back to English if \sty{babel} is not available). This is the default behavior. It is also possible to select the document language manually. In this case, the \opt{babel} option below will have no effect. Please refer to \tabref{use:opt:tab1} for a list of supported languages and the corresponding identifiers.
-
-\begin{table}
-\tablesetup
-\begin{tabularx}{\textwidth}{@{}p{100pt}@{}p{150pt}@{}>{\ttfamily}X@{}}
-\toprule
-\multicolumn{1}{@{}H}{Language} &
-\multicolumn{1}{@{}H}{Region/Dialect} &
-\multicolumn{1}{@{}H}{Identifier} \\
-\cmidrule(r){1-1}\cmidrule(r){2-2}\cmidrule{3-3}
-Catalan & Spain, France, Andorra, Italy & catalan \\
-Czech & Czech Republic & czech \\
-Danish & Denmark & danish \\
-Dutch & Netherlands & dutch \\
-English & USA & american \\
- & United Kingdom & british \\
- & Canada & canadian \\
- & Australia & australian \\
- & New Zealand & newzealand \\
-Finnish & Finland & finnish \\
-French & France, Canada & french \\
-German & Germany & german \\
- & Austria & austrian \\
-German (new)
- & Germany & ngerman \\
- & Austria & naustrian \\
-Greek & Greece & greek \\
-Italian & Italy & italian \\
-Norwegian & Norway & norwegian \\
-Portuguese& Brazil & brazilian \\
- & Portugal & portuguese \\
-Russian & Russia & russian \\
-Spanish & Spain & spanish \\
-Swedish & Sweden & swedish \\
-\bottomrule
-\end{tabularx}
-\caption{Supported Languages}
-\label{use:opt:tab1}
-\end{table}
+This option controls multilingual support. When set to \opt{auto}, \sty{biblatex} will try to get the main document language from the \sty{babel} package (and fall back to English if \sty{babel} is not available). This is the default behavior. It is also possible to select the document language manually. In this case, the \opt{babel} option below will have no effect. Please refer to \tabref{bib:fld:tab1} for a list of supported languages and the corresponding identifiers.
\boolitem[true]{clearlang}
@@ -2526,7 +2514,7 @@ This option controls the format of initials generated by \sty{biblatex}. If enab
\boolitem[false]{labelalpha}
Whether or not to provide the special fields \bibfield{labelalpha} and \bibfield{extraalpha}, see \secref{aut:bbx:fld} for details.
-\BiberOnlyMark With \biber, this option is also settable on a per-type basis. See also \opt{maxalphanames} and \opt{minalphanames}. Table \ref{use:opt:tab2} summarises the various \opt{extra*} disambiguation counters and what they track.
+\BiberOnlyMark With \biber, this option is also settable on a per-type basis. See also \opt{maxalphanames} and \opt{minalphanames}. Table \ref{use:opt:tab1} summarises the various \opt{extra*} disambiguation counters and what they track.
\intitem[3]{maxalphanames}[\BiberOnly]
@@ -2543,16 +2531,16 @@ This option is also settable on a per-type basis.
\boolitem[false]{labeltitle}[\BiberOnly]
-Whether or not to provide the special field \bibfield{extratitle}, see \secref{aut:bbx:fld} for details. Note that the special field \bibfield{labeltitle} is always provided and this option controls rather whether \bibfield{labeltitle} is used to generate \bibfield{extratitle} information. This option is also settable on a per-type basis. Table \ref{use:opt:tab2} summarises the various \opt{extra*} disambiguation counters and what they track.
+Whether or not to provide the special field \bibfield{extratitle}, see \secref{aut:bbx:fld} for details. Note that the special field \bibfield{labeltitle} is always provided and this option controls rather whether \bibfield{labeltitle} is used to generate \bibfield{extratitle} information. 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.
\boolitem[false]{labeltitleyear}[\BiberOnly]
-Whether or not to provide the special field \bibfield{extratitleyear}, see \secref{aut:bbx:fld} for details. Note that the special field \bibfield{labeltitle} is always provided and this option controls rather whether \bibfield{labeltitle} is used to generate \bibfield{extratitleyear} information. This option is also settable on a per-type basis. Table \ref{use:opt:tab2} summarises the various \opt{extra*} disambiguation counters and what they track.
+Whether or not to provide the special field \bibfield{extratitleyear}, see \secref{aut:bbx:fld} for details. Note that the special field \bibfield{labeltitle} is always provided and this option controls rather whether \bibfield{labeltitle} is used to generate \bibfield{extratitleyear} information. 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.
\boolitem[false]{labeldate}
Whether or not to provide the special fields \bibfield{labelyear}, \bibfield{labelmonth}, \bibfield{labelday} and \bibfield{extrayear}, see \secref{aut:bbx:fld} for details.
-\BiberOnlyMark With \biber, this option is also settable on a per-type basis. Table \ref{use:opt:tab2} summarises the various \opt{extra*} disambiguation counters and what they track.
+\BiberOnlyMark With \biber, 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.
\boolitem[false]{singletitle}
@@ -2608,7 +2596,7 @@ labeltitleyear & --- & extratitleyear & labeltitle+labelyear\\
\bottomrule
\end{tabularx}
\caption{Disambiguation counters}
-\label{use:opt:tab2}
+\label{use:opt:tab1}
\end{table}
\subsubsection{Entry Options}
@@ -2690,26 +2678,10 @@ Setting this option is equivalent to \kvopt{uniquename}{false}, \kvopt{uniquelis
Specifies the field to consider first when looking for a \bibfield{labelname} candidate. It is essentially prepended to the search list created by \cmd{DeclareLabelname} for just this entry.
-\choitem[original]{labelnameform}{original,translated,romanised,uniform}
-
-Specifies the script variant for the field specified with \opt{labelnamefield}, if the datasource you are using supports this.
-
-\choitem[none]{labelnamelang}{<language specifier>}
-
-Specifies the \sty{babel} language variant for the field specified with \opt{labelnamefield} if the datasource you are using supports this. The default, if no \prm{lang} option is set, this means to use the field variant in the datasource which has no explicit language defined.
-
\valitem{labeltitlefield}{fieldname}
Specifies the field to consider first when looking for a \bibfield{labeltitle} candidate. It is essentially prepended to the search list created by \cmd{DeclareLabeltitle} for just this entry.
-\choitem[original]{labeltitleform}{original,translated,romanised,uniform}
-
-Specifies the script variant for the field specified with \opt{labeltitlefield}, if the datasource you are using supports this.
-
-\choitem[none]{labeltitlelang}{<language specifier>}
-
-Specifies the \sty{babel} language variant for the field specified with \opt{labeltitlefield} if the datasource you are using supports this. The default, if no \prm{lang} option is set, this means to use the field variant in the datasource which has no explicit language defined.
-
\end{optionlist}
\subsubsection{Legacy Options}
@@ -3447,7 +3419,7 @@ The following additional citation commands are only provided by some of the cita
\cmditem{textcite}[prenote][postnote]{key}
\cmditem{Textcite}[prenote][postnote]{key}
-These citation commands are provided by all styles that ship with this package. They are intended for use in the flow of text, replacing the subject of a sentence. They print the authors or editors followed by a citation label which is enclosed in parentheses. Depending on the citation style, the label may be a number, the year of publication, an abridged version of the title, or something else. The numeric and alphabetic styles use square brackets instead of parentheses. \cmd{Textcite} is similar to \cmd{textcite} but capitalizes the name prefix of the first name in the citation if the \opt{useprefix} option is enabled, provided that there is a name prefix.
+These citation commands are provided by all styles that ship with this package. They are intended for use in the flow of text, replacing the subject of a sentence. They print the authors or editors followed by a citation label which is enclosed in parentheses. Depending on the citation style, the label may be a number, the year of publication, an abridged version of the title, or something else. The numeric and alphabetic styles use square brackets instead of parentheses. In the verbose styles, the label is provided in a footnote. Trailing punctuation is moved between the author or editor names and the footnote mark. \cmd{Textcite} is similar to \cmd{textcite} but capitalizes the name prefix of the first name in the citation if the \opt{useprefix} option is enabled, provided that there is a name prefix.
\cmditem{smartcite}[prenote][postnote]{key}
\cmditem{Smartcite}[prenote][postnote]{key}
@@ -3502,32 +3474,32 @@ By default, this package provides the following multicite commands which corresp
\begin{ltxsyntax}
-\cmditem{cites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
-\cmditem{Cites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
+\cmditem{cites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
+\cmditem{Cites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
The multicite version of \cmd{cite} and \cmd{Cite}, respectively.
-\cmditem{parencites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
-\cmditem{Parencites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
+\cmditem{parencites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
+\cmditem{Parencites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
The multicite version of \cmd{parencite} and \cmd{Parencite}, respectively.
-\cmditem{footcites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
-\cmditem{footcitetexts}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
+\cmditem{footcites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
+\cmditem{footcitetexts}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
The multicite version of \cmd{footcite} and \cmd{footcitetext}, respectively.
-\cmditem{smartcites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
-\cmditem{Smartcites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
+\cmditem{smartcites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
+\cmditem{Smartcites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
The multicite version of \cmd{smartcite} and \cmd{Smartcite}, respectively.
-\cmditem{textcites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
-\cmditem{Textcites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
+\cmditem{textcites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
+\cmditem{Textcites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
-The multicite version of \cmd{textcite} and \cmd{Textcite}, respectively. This command is only provided by non-verbose styles.
+The multicite version of \cmd{textcite} and \cmd{Textcite}, respectively.
-\cmditem{supercites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
+\cmditem{supercites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
The multicite version of \cmd{supercite}. This command is only provided by the numeric styles.
@@ -3550,8 +3522,8 @@ In contrast to other citation commands, the \cmd{autocite} command does not only
The starred variants of \cmd{autocite} do not behave differently from the regular ones. The asterisk is simply passed on to the backend command. For example, if \cmd{autocite} is configured to use \cmd{parencite}, then \cmd{autocite*} will execute \cmd{parencite*}.
-\cmditem{autocites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
-\cmditem{Autocites}(pre)(post)[pre][post]{key}|...|[pre][post]{key}
+\cmditem{autocites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
+\cmditem{Autocites}(multiprenote)(multipostnote)[prenote][postnote]{key}|...|[prenote][postnote]{key}
This is the multicite version of \cmd{autocite}. It also detects and moves punctuation if required. Note that there is no starred variant. \cmd{Autocites} is similar to \cmd{autocites} but capitalizes the name prefix of the first name in the citation if the \opt{useprefix} option is enabled, provided that there is a name prefix and the citation style prints any name at all.
@@ -3626,31 +3598,61 @@ Similar to \cmd{fullcite} but puts the entire citation in a footnote and adds a
These commands are similar to \cmd{cite} and \cmd{Cite} but intended for references to multi"=volume works which are cited by volume and page number. Instead of the \prm{postnote}, they take a mandatory \prm{volume} and an optional \prm{page} argument. Since they merely compose the postnote and pass it to the \cmd{cite} command provided by the citation style as a \prm{postnote} argument, these commands are style independent. The format of the volume portion is controlled by the field formatting directive \opt{volcitevolume}, the format of the page/text portion is controlled by the field formatting directive \opt{volcitepages} (\secref{aut:fmt:ich}). The delimiter printed between the volume portion and the page/text portion may be modified by redefining the macro \cmd{volcitedelim} (\secref{aut:fmt:fmt}).
+\cmditem{volcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+\cmditem{Volcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+
+The multicite version of \cmd{volcite} and \cmd{Volcite}, respectively.
+
\cmditem{pvolcite}[prenote]{volume}[page]{key}
\cmditem{Pvolcite}[prenote]{volume}[page]{key}
Similar to \cmd{volcite} but based on \cmd{parencite}.
+\cmditem{pvolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+\cmditem{Pvolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+
+The multicite version of \cmd{pvolcite} and \cmd{Pvolcite}, respectively.
+
\cmditem{fvolcite}[prenote]{volume}[page]{key}
\cmditem{ftvolcite}[prenote]{volume}[page]{key}
Similar to \cmd{volcite} but based on \cmd{footcite} and \cmd{footcitetext}, respectively.
+\cmditem{fvolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+\cmditem{Fvolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+
+The multicite version of \cmd{fvolcite} and \cmd{Fvolcite}, respectively.
+
\cmditem{svolcite}[prenote]{volume}[page]{key}
\cmditem{Svolcite}[prenote]{volume}[page]{key}
Similar to \cmd{volcite} but based on \cmd{smartcite}.
+\cmditem{svolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+\cmditem{Svolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+
+The multicite version of \cmd{svolcite} and \cmd{Svolcite}, respectively.
+
\cmditem{tvolcite}[prenote]{volume}[page]{key}
\cmditem{Tvolcite}[prenote]{volume}[page]{key}
Similar to \cmd{volcite} but based on \cmd{textcite}.
+\cmditem{tvolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+\cmditem{Tvolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+
+The multicite version of \cmd{tvolcite} and \cmd{Tvolcite}, respectively.
+
\cmditem{avolcite}[prenote]{volume}[page]{key}
\cmditem{Avolcite}[prenote]{volume}[page]{key}
Similar to \cmd{volcite} but based on \cmd{autocite}.
+\cmditem{avolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+\cmditem{Avolcites}(multiprenote)(multipostnote)[prenote]{volume}[page]{key}|\\...|[prenote]{volume}[page]{key}
+
+The multicite version of \cmd{avolcite} and \cmd{Avolcite}, respectively.
+
\cmditem{notecite}[prenote][postnote]{key}
\cmditem{Notecite}[prenote][postnote]{key}
@@ -4029,6 +4031,9 @@ Similar to \cmd{multicitedelim}, but used by the \cmd{supercite} command only. T
\csitem{compcitedelim}
Similar to \cmd{multicitedelim}, but used by certain citation styles when <compressing> multiple citations. The default definition is a comma plus an interword space.
+\csitem{textcitedelim}
+Similar to \cmd{multicitedelim}, but used by \cmd{textcite} and related commands (\secref{use:cit:cbx}). The default is a comma plus an interword space. The standard styles modify this provisional definition to ensure that the delimiter before the final citation is the localized term <and>, separated by interword spaces. See also \cmd{finalandcomma} and \cmd{finalandsemicolon} in \secref{use:fmt:lng}.
+
\csitem{nametitledelim}
The delimiter printed between the author\slash editor and the title by author-title and some verbose citation styles. The default definition is a comma plus an interword space.
@@ -4123,7 +4128,17 @@ Prints the comma to be inserted before the final <and> in a list, if applicable
Michel Goossens, Frank Mittelbach<<,>> and Alexander Samarin
\end{lstlisting}
%
-\cmd{finalandcomma} is the comma before the word <and>. See also \cmd{multinamedelim}, \cmd{finalnamedelim}, and \cmd{revsdnamedelim} in \secref{use:fmt:fmt}.
+\cmd{finalandcomma} is the comma before the word <and>. See also \cmd{multinamedelim}, \cmd{finalnamedelim}, \cmd{textcitedelim}, and \cmd{revsdnamedelim} in \secref{use:fmt:fmt}.
+
+\csitem{finalandsemicolon}
+
+Prints the semicolon to be inserted before the final <and> in a list of lists, if applicable in the respective language. Here is an example:
+
+\begin{lstlisting}[style=latex]{}
+Goossens, Mittelbach, and Samarin; Bertram and Wenworth<<;>> and Knuth
+\end{lstlisting}
+%
+\cmd{finalandsemicolon} is the semicolon before the word <and>. See also \cmd{textcitedelim} in \secref{use:fmt:fmt}.
\cmditem{mkbibordinal}{integer}
@@ -4610,7 +4625,7 @@ The handling of the headings is different from \cmd{bibbysection} and \cmd{bibby
\subsubsection{Entry Sets}
\label{use:use:set}
-An entry set is a group of entries which are cited as a single reference and listed as a single item in the bibliography. The individual entries in the set are separated by \cmd{entrysetpunct} (\secref{aut:fmt:fmt}). The individual entries in the set are separated by \cmd{entrysetpunct} (\secref{aut:fmt:fmt}). The \sty{biblatex} package supports two types of entry sets. Static entry sets are defined in the \file{bib} file like any other entry. Dynamic entry sets are defined with \cmd{defbibentryset} (\secref{use:bib:set}) on a per-document\slash per-refsection basis in the document preamble or the document body. This section deals with the definition of entry sets; style authors should also see \secref{aut:cav:set} for further information.
+An entry set is a group of entries which are cited as a single reference and listed as a single item in the bibliography. The individual entries in the set are separated by \cmd{entrysetpunct} (\secref{aut:fmt:fmt}). The \sty{biblatex} package supports two types of entry sets. Static entry sets are defined in the \file{bib} file like any other entry. Dynamic entry sets are defined with \cmd{defbibentryset} (\secref{use:bib:set}) on a per-document\slash per-refsection basis in the document preamble or the document body. This section deals with the definition of entry sets; style authors should also see \secref{aut:cav:set} for further information.
\paragraph{Static entry sets}
@@ -5382,7 +5397,7 @@ When using \bibtex as the backend, a label similar to the labels generated by th
\fielditem{extraalpha}{integer}
-The <alphabetic> citation scheme usually requires a letter to be appended to the label if the bibliography contains two or more works by the same author which were all published in the same year. In this case, the \bibfield{extraalpha} field holds an integer which may be converted to a letter with \cmd{mknumalph} or formatted in some other way. This field is similar to the role of \bibfield{extrayear} in the author"=year scheme. A complete <alphabetic> label consists of the fields \bibfield{labelalpha} plus \bibfield{extraalpha}. Note that the \bibfield{labelalpha} and \bibfield{extraalpha} fields need to be requested with the package option \opt{labelalpha}, see \secref{use:opt:pre:int} for details. See also \bibfield{labelalpha} as well as \cmd{labelalphaothers} in \secref{use:fmt:fmt}. Table \ref{use:opt:tab2} summarises the various \opt{extra*} disambiguation counters and what they track.
+The <alphabetic> citation scheme usually requires a letter to be appended to the label if the bibliography contains two or more works by the same author which were all published in the same year. In this case, the \bibfield{extraalpha} field holds an integer which may be converted to a letter with \cmd{mknumalph} or formatted in some other way. This field is similar to the role of \bibfield{extrayear} in the author"=year scheme. A complete <alphabetic> label consists of the fields \bibfield{labelalpha} plus \bibfield{extraalpha}. Note that the \bibfield{labelalpha} and \bibfield{extraalpha} fields need to be requested with the package option \opt{labelalpha}, see \secref{use:opt:pre:int} for details. See also \bibfield{labelalpha} as well as \cmd{labelalphaothers} in \secref{use:fmt:fmt}. Table \ref{use:opt:tab1} summarises the various \opt{extra*} disambiguation counters and what they track.
\listitem{labelname}{name}
@@ -5403,30 +5418,30 @@ The printable title of a work. In some circumstances, a style might need to choo
\fielditem{extratitle}{integer}
-It is sometimes useful, for example in author"=title citation schemes, to be able to disambiguate works with the same title. For works by the same \bibfield{labelname} with the same \bibfield{labeltitle}, the \bibfield{extratitle} field holds an integer which may be converted to a letter with \cmd{mknumalph} or formatted in some other way (or it can be merely used as a flag to say that some other field such as a date should be used in conjunction with the \bibfield{labeltitle} field). This field is undefined if there is only one work with the same \bibfield{labeltitle} by the same \bibfield{labelname} in the bibliography. Note that the \bibfield{extratitle} field needs to be requested with the package option \opt{labeltitle}, see \secref{use:opt:pre:int} for details. See also \bibfield{labeltitle}. Table \ref{use:opt:tab2} summarises the various \opt{extra*} disambiguation counters and what they track.
+It is sometimes useful, for example in author"=title citation schemes, to be able to disambiguate works with the same title. For works by the same \bibfield{labelname} with the same \bibfield{labeltitle}, the \bibfield{extratitle} field holds an integer which may be converted to a letter with \cmd{mknumalph} or formatted in some other way (or it can be merely used as a flag to say that some other field such as a date should be used in conjunction with the \bibfield{labeltitle} field). This field is undefined if there is only one work with the same \bibfield{labeltitle} by the same \bibfield{labelname} in the bibliography. Note that the \bibfield{extratitle} field needs to be requested with the package option \opt{labeltitle}, see \secref{use:opt:pre:int} for details. See also \bibfield{labeltitle}. Table \ref{use:opt:tab1} summarises the various \opt{extra*} disambiguation counters and what they track.
\fielditem{extratitleyear}{integer}
-It is sometimes useful, for example in author"=title citation schemes, to be able to disambiguate works with the same title in the same year but with no author. For works with the same \bibfield{labeltitle} and with the same \bibfield{labelyear}, the \bibfield{extratitleyear} field holds an integer which may be converted to a letter with \cmd{mknumalph} or formatted in some other way (or it can be merely used as a flag to say that some other field such as a publisher should be used in conjunction with the \bibfield{labelyear} field). This field is undefined if there is only one work with the same \bibfield{labeltitle} and \bibfield{labelyear} in the bibliography. Note that the \bibfield{extratitleyear} field needs to be requested with the package option \opt{labeltitleyear}, see \secref{use:opt:pre:int} for details. See also \bibfield{labeltitleyear}. Table \ref{use:opt:tab2} summarises the various \opt{extra*} disambiguation counters and what they track.
+It is sometimes useful, for example in author"=title citation schemes, to be able to disambiguate works with the same title in the same year but with no author. For works with the same \bibfield{labeltitle} and with the same \bibfield{labelyear}, the \bibfield{extratitleyear} field holds an integer which may be converted to a letter with \cmd{mknumalph} or formatted in some other way (or it can be merely used as a flag to say that some other field such as a publisher should be used in conjunction with the \bibfield{labelyear} field). This field is undefined if there is only one work with the same \bibfield{labeltitle} and \bibfield{labelyear} in the bibliography. Note that the \bibfield{extratitleyear} field needs to be requested with the package option \opt{labeltitleyear}, see \secref{use:opt:pre:int} for details. See also \bibfield{labeltitleyear}. Table \ref{use:opt:tab1} summarises the various \opt{extra*} disambiguation counters and what they track.
\fielditem{labelyear}{literal}
The publication year, as specified in the \bibfield{date} or the \bibfield{year} field, for use in author-year labels. A complete author-year label consists of the fields \bibfield{labelyear} plus \bibfield{extrayear}. Note that the \bibfield{labelyear} and \bibfield{extrayear} fields need to be requested with the package option \opt{labeldate}, see \secref{use:opt:pre:int} for details. See also \bibfield{extrayear}.
\BiberOnlyMark With \biber, the source date field for this may be customized. See \secref{aut:ctm:fld} for details.
-\fielditem{labelmonth}{integer}
+\fielditem{labelmonth}{datepart}
The publication month, as specified in the \bibfield{date} or the \bibfield{month} field, for use in author-year labels. Note that the \bibfield{labelmonth} field needs to be requested with the package option \opt{labeldate}, see \secref{use:opt:pre:int} for details.
\BiberOnlyMark With \biber, this source date field for this may be customized. See \secref{aut:ctm:fld} for details.
-\fielditem{labelday}{integer}
+\fielditem{labelday}{datepart}
The publication day, as specified in the \bibfield{date}, for use in author-year labels. Note that the \bibfield{labelday} field needs to be requested with the package option \opt{labeldate}, see \secref{use:opt:pre:int} for details.
\BiberOnlyMark With \biber, this source date field for this may be customized. See \secref{aut:ctm:fld} for details.
\fielditem{extrayear}{integer}
-The author"=year citation scheme usually requires a letter to be appended to the year if the bibliography contains two or more works by the same author which were all published in the same year. In this case, the \bibfield{extrayear} field holds an integer which may be converted to a letter with \cmd{mknumalph} or formatted in some other way. This field is undefined if there is only one work by the author in the bibliography or if all works by the author have different publication years. A complete author-year label consists of the fields \bibfield{labelyear} plus \bibfield{extrayear}. Note that the \bibfield{labelyear} and \bibfield{extrayear} fields need to be requested with the package option \opt{labeldate}, see \secref{use:opt:pre:int} for details. See also \bibfield{labelyear}. Table \ref{use:opt:tab2} summarises the various \opt{extra*} disambiguation counters and what they track.
+The author"=year citation scheme usually requires a letter to be appended to the year if the bibliography contains two or more works by the same author which were all published in the same year. In this case, the \bibfield{extrayear} field holds an integer which may be converted to a letter with \cmd{mknumalph} or formatted in some other way. This field is undefined if there is only one work by the author in the bibliography or if all works by the author have different publication years. A complete author-year label consists of the fields \bibfield{labelyear} plus \bibfield{extrayear}. Note that the \bibfield{labelyear} and \bibfield{extrayear} fields need to be requested with the package option \opt{labeldate}, see \secref{use:opt:pre:int} for details. See also \bibfield{labelyear}. Table \ref{use:opt:tab1} summarises the various \opt{extra*} disambiguation counters and what they track.
\end{fieldlist}
@@ -5503,99 +5518,99 @@ eventdate & 1995-01-31/1995-02-05 & eventday & 31 \\
\begin{fieldlist}
-\fielditem{day}{integer}
+\fielditem{day}{datepart}
This field holds the day component of the \bibfield{date} field. If the date is a range, it holds the day component of the start date.
-\fielditem{month}{integer}
+\fielditem{month}{datepart}
This field is the \bibfield{month} as given in the database file or it holds the month component of the \bibfield{date} field. If the date is a range, it holds the month component of the start date.
-\fielditem{year}{integer}
+\fielditem{year}{datepart}
This field is the \bibfield{year} as given in the database file or it holds the year component of the \bibfield{date} field. If the date is a range, it holds the year component of the start date.
-\fielditem{endday}{integer}
+\fielditem{endday}{datepart}
If the date specification in the \bibfield{date} field is a range, this field holds the day component of the end date.
-\fielditem{endmonth}{integer}
+\fielditem{endmonth}{datepart}
If the date specification in the \bibfield{date} field is a range, this field holds the month component of the end date.
-\fielditem{endyear}{integer}
+\fielditem{endyear}{datepart}
If the date specification in the \bibfield{date} field is a range, this field holds the year component of the end date. A blank (but defined) \bibfield{endyear} component indicates an open ended \bibfield{date} range.
-\fielditem{origday}{integer}
+\fielditem{origday}{datepart}
This field holds the day component of the \bibfield{origdate} field. If the date is a range, it holds the day component of the start date.
-\fielditem{origmonth}{integer}
+\fielditem{origmonth}{datepart}
This field holds the month component of the \bibfield{origdate} field. If the date is a range, it holds the month component of the start date.
-\fielditem{origyear}{integer}
+\fielditem{origyear}{datepart}
This field holds the year component of the \bibfield{origdate} field. If the date is a range, it holds the year component of the start date.
-\fielditem{origendday}{integer}
+\fielditem{origendday}{datepart}
If the date specification in the \bibfield{origdate} field is a range, this field holds the day component of the end date.
-\fielditem{origendmonth}{integer}
+\fielditem{origendmonth}{datepart}
If the date specification in the \bibfield{origdate} field is a range, this field holds the month component of the end date.
-\fielditem{origendyear}{integer}
+\fielditem{origendyear}{datepart}
If the date specification in the \bibfield{origdate} field is a range, this field holds the year component of the end date. A blank (but defined) \bibfield{origendyear} component indicates an open ended \bibfield{origdate} range.
-\fielditem{eventday}{integer}
+\fielditem{eventday}{datepart}
This field holds the day component of the \bibfield{eventdate} field. If the date is a range, it holds the day component of the start date.
-\fielditem{eventmonth}{integer}
+\fielditem{eventmonth}{datepart}
This field holds the month component of the \bibfield{eventdate} field. If the date is a range, it holds the month component of the start date.
-\fielditem{eventyear}{integer}
+\fielditem{eventyear}{datepart}
This field holds the year component of the \bibfield{eventdate} field. If the date is a range, it holds the year component of the start date.
-\fielditem{eventendday}{integer}
+\fielditem{eventendday}{datepart}
If the date specification in the \bibfield{eventdate} field is a range, this field holds the day component of the end date.
-\fielditem{eventendmonth}{integer}
+\fielditem{eventendmonth}{datepart}
If the date specification in the \bibfield{eventdate} field is a range, this field holds the month component of the end date.
-\fielditem{eventendyear}{integer}
+\fielditem{eventendyear}{datepart}
If the date specification in the \bibfield{eventdate} field is a range, this field holds the year component of the end date. A blank (but defined) \bibfield{eventendyear} component indicates an open ended \bibfield{eventdate} range.
-\fielditem{urlday}{integer}
+\fielditem{urlday}{datepart}
This field holds the day component of the \bibfield{urldate} field.
-\fielditem{urlmonth}{integer}
+\fielditem{urlmonth}{datepart}
This field holds the month component of the \bibfield{urldate} field.
-\fielditem{urlyear}{integer}
+\fielditem{urlyear}{datepart}
This field holds the year component of the \bibfield{urldate} field.
-\fielditem{urlendday}{integer}
+\fielditem{urlendday}{datepart}
If the date specification in the \bibfield{urldate} field is a range, this field holds the day component of the end date.
-\fielditem{urlendmonth}{integer}
+\fielditem{urlendmonth}{datepart}
If the date specification in the \bibfield{urldate} field is a range, this field holds the month component of the end date.
-\fielditem{urlendyear}{integer}
+\fielditem{urlendyear}{datepart}
If the date specification in the \bibfield{urldate} field is a range, this field holds the year component of the end date. A blank (but defined) \bibfield{urlendyear} component indicates an open ended \bibfield{urldate} range.
@@ -5680,6 +5695,18 @@ The \prm{prenote} argument passed to a citation command. This field is specific
The \prm{postnote} argument passed to a citation command. This field is specific to citations and not available in the bibliography. If the \prm{postnote} argument is missing or empty, this field is undefined.
+\fielditem{multiprenote}{literal}
+
+The \prm{multiprenote} argument passed to a multicite command. This field is specific to citations and not available in the bibliography. If the \prm{multiprenote} argument is missing or empty, this field is undefined.
+
+\fielditem{multipostnote}{literal}
+
+The \prm{multipostnote} argument passed to a multicite command. This field is specific to citations and not available in the bibliography. If the \prm{multipostnote} argument is missing or empty, this field is undefined.
+
+\fielditem{postpunct}{punctuation command}
+
+The trailing punctuation argument implicitly passed to a citation command. This field is specific to citations and not available in the bibliography. If the character following a given citation command is not specified in \cmd{DeclareAutoPunctuation} (\secref{aut:pct:cfg}), this field is undefined.
+
\end{fieldlist}
\subsection{Data Interface}
@@ -5986,6 +6013,7 @@ A mapping step. Each step is applied sequentially to every relevant entry where
\valitem{fieldsource}{entryfield}
\valitem{fieldtarget}{entryfield}
\valitem{match}{regexp}
+\valitem{notmatch}{regexp}
\valitem{replace}{regexp}
\valitem{fieldset}{entryfield}
\valitem{fieldvalue}{string}
@@ -6014,7 +6042,7 @@ For all boolean \cmd{step} options, the short form \opt{option} is equivalent to
\texttt{final} is \texttt{true} then if there is no \texttt{fieldsource} \prm{entryfield} in the entry, processing of the parent \cmd{map} immediately terminates.
\item If \texttt{match} is defined but
\texttt{replace} is not, only apply the step if the \texttt{fieldsource} \prm{entryfield} matches the
- \texttt{match} regular expression\footnote{Regular expressions are full Perl 5.14 regular expressions. This means you may need to deal with special characters, see examples.}. You may use capture parenthesis as usual and refer to these (\$1\ldots\$9) in later \texttt{fieldvalue} specifications. This allows you to pull out parts of some fields and put these parts in other fields.
+ \texttt{match} regular expression (logic is reversed if you use \texttt{notmatch} instead)\footnote{Regular expressions are full Perl 5.16 regular expressions. This means you may need to deal with special characters, see examples.}. You may use capture parenthesis as usual and refer to these (\$1\ldots\$9) in later \texttt{fieldvalue} specifications. This allows you to pull out parts of some fields and put these parts in other fields.
\item Perform a regular expression match and replace on the value of the \texttt{fieldsource} \prm{entryfield} if \texttt{match} and \texttt{replace} are defined.
\item If \texttt{fieldset} is defined, then its value is \prm{entryfield}
which will be set to a value specified by further options. If
@@ -6383,6 +6411,10 @@ Declares the comma"=separated list of \prm{fields} to be valid fields in the dat
Set the type of the field as described in \secref{bib:fld:typ}. Is typically <field> or <list>.
+\valitem{format}{field format}
+
+Any special format of the field. Normally unspecified but can take the value <csv>. Used internally by \biber for various things.
+
\valitem{datatype}{field datatype}
Set the datatype of the field as described in \secref{bib:fld:typ}. For example, <name> or <literal>.
@@ -6665,18 +6697,6 @@ Here are some examples. The default global \sty{biblatex} alphabetic label templ
}
\end{lstlisting}
%
-Here is an example using form and script variants. We use as the label the left three characters of the <romanised> form of the \bibfield{labelname} field as a preference. If this doesn't exist, we use the <translated> form in the <french> language. If this does not exist, we use the default \bibfield{labelname} from the datasource which has no form or lang specifications.
-
-\begin{lstlisting}[style=latex]{}
-\DeclareLabelalphaTemplate{
- \labelelement{
- \field[strwidth=3,strside=left,form=romanised]{<<labelname>>}
- \field[strwidth=3,strside=left,form=translated,lang=french]{<<labelname>>}
- \field[strwidth=3,strside=left]{<<labelname>>}
- }
-}
-\end{lstlisting}
-%
To get an idea of how the label automatic disambiguation works, consider the following author lists:
\begin{lstlisting}{}
@@ -6860,7 +6880,7 @@ Defines the sorting scheme \prm{name}. The \prm{name} is the identifier passed t
\cmditem{sort}{elements}
-Specifies the elements considered in the sorting process. The \prm{elements} are an undelimited list of \cmd{name}, \cmd{list}, \cmd{field}, \cmd{literal}, and \cmd{citeorder} commands which are evaluated in the order in which they are given. If an element is defined, it is added to the sort key and the sorting routine skips to the next \cmd{sort} directive. If it is undefined, the next element is evaluated. Since literal strings are always defined, any \cmd{literal} commands should be the sole or the last element in a \cmd{sort} directive. The \cmd{sort} command supports the following optional arguments:
+Specifies the elements considered in the sorting process. The \prm{elements} are an undelimited list of \cmd{field}, \cmd{literal}, and \cmd{citeorder} commands which are evaluated in the order in which they are given. If an element is defined, it is added to the sort key and the sorting routine skips to the next \cmd{sort} directive. If it is undefined, the next element is evaluated. Since literal strings are always defined, any \cmd{literal} commands should be the sole or the last element in a \cmd{sort} directive. The \cmd{sort} command supports the following optional arguments:
\begin{optionlist*}
@@ -6914,14 +6934,6 @@ Performs a substring match on the \texttt{left} or \texttt{right} side of the fi
The number of characters to match.
-\choitem[original]{form}{original,translated,romanised,uniform}
-
-Specifies the script variant of a field, if the datasource you are using supports this.
-
-\choitem[none]{lang}{<language specifier>}
-
-Specifies the \sty{babel} language variant of a field if the datasource you are using supports this. The default, if no \prm{lang} option is set, this means to use the field variant in the datasource which has no explicit language defined.
-
\end{optionlist*}
\cmditem{literal}{string}
@@ -6975,18 +6987,6 @@ Here are some examples of sorting schemes. In the first example, we define a sim
}
\end{lstlisting}
%
-Here is an example of specifying particular field scripts and language variants. Here we are sorting on variants of the \bibfield{author} field. First choice is the <translated> form in the <english> language. If this does not exist, then we look for a <romanised> form and if this does not exist, we use the default form.
-
-\begin{lstlisting}[style=latex]{}
-\DeclareSortingScheme{sample}{
- \sort{
- \field[form=translated, lang=english]{<<author>>}
- \field[form=romanised]{<<author>>}
- \field{<<author>>}
- }
-}
-\end{lstlisting}
-%
In the next example, we define the same scheme in a more elaborate way, considering special fields such as \bibfield{presort}, \bibfield{sortkey}, \bibfield{sortname}, etc. Since the \bibfield{sortkey} field specifies the master sort key, it needs to override all other elements except for \bibfield{presort}. This is indicated by the \opt{final} option. If the \bibfield{sortkey} field is available, processing will stop at this point. If not, the sorting routine continues with the next \cmd{sort} directive. This setup corresponds to the default definition of the \texttt{nty} scheme:
\begin{lstlisting}[style=latex]{}
@@ -7161,34 +7161,11 @@ Defines the fields to consider when generating the \bibfield{labelname} field (s
}
\end{lstlisting}
%
-The \bibfield{labelname} field may be customized globally or on a per-type basis. If the optional \prm{entrytype} argument is given, the specification applies to the respective entry type. If not, it is applied globally. The \prm{entrytype} argument may be a comma"=separated list of values. This command may only be used in the preamble. \cmd{field} may take the following options:
-
-\begin{optionlist*}
-
-\choitem[original]{form}{original,translated,romanised,uniform}
-
-Specifies the script variant of a field, if the datasource you are using supports this.
-
-\choitem[none]{lang}{<language specifier>}
-
-Specifies the \sty{babel} language variant of a field if the datasource you are using supports this. The default, if no \prm{lang} option is set, this means to use the field variant in the datasource which has no explicit language defined.
-
-\end{optionlist*}
-%
-For example, the following specification for selecting \bibfield{labelname} first looks for an english translation variant of the \bibfield{AUTHOR} field, then a romainsed variant and if neither of these can be found, the default field with no form or lang specifications.
-\begin{lstlisting}[style=latex]{}
-\DeclareLabelname{%
- \field[form=translated,lang=english]{author}
- \field[form=romanised]{author}
- \field{author}
-}
-\end{lstlisting}
-%
-See \secref{use:opt:bib:ded} for options to override this on a per-entry basis.
+The \bibfield{labelname} field may be customized globally or on a per-type basis. If the optional \prm{entrytype} argument is given, the specification applies to the respective entry type. If not, it is applied globally. The \prm{entrytype} argument may be a comma"=separated list of values. This command may only be used in the preamble.
\cmditem{DeclareLabeldate}[entrytype, \dots]{specification}|\BiberOnlyMark|
-Defines the date components to consider when generating \bibfield{labelyear}, \bibfield{labelmonth} and \bibfield{labelday} fields (see \secref{aut:bbx:fld:lab}). The \prm{specification} is an ordered list of \cmd{field} or \cmd{literal} commands. The items are checked in the order listed and the first item which is available will be used to popluate the \bibfield{labelyear}, \bibfield{labelmonth} and \bibfield{labelday} fields. Note that the \cmd{field} items do not have to be datetype <date> in the data model so that you can create pseudo-year labels by, for example, using a \bibfield{pubstate} field contents, if available, as the year label by defining \cmd{DeclareLabeldate} suitably. Note also that a \cmd{literal} command will always be used when found and so this should always be the last thing in the list. If the value of a \cmd{literal} command is a valid localisation string, then this will be resolved in the current language, otherwise the value is used as a literal string as-is. This is the default definition:
+Defines the date components to consider when generating \bibfield{labelyear}, \bibfield{labelmonth} and \bibfield{labelday} fields (see \secref{aut:bbx:fld:lab}). The \prm{specification} is an ordered list of \cmd{field} or \cmd{literal} commands. The items are checked in the order listed and the first item which is available will be used to popluate the \bibfield{labelyear}, \bibfield{labelmonth} and \bibfield{labelday} fields. Note that the \cmd{field} items do not have to be datetype <date> in the data model so that you can create pseudo-year labels by, for example, using a \bibfield{pubstate} field contents, if available, as the year label by defining \cmd{DeclareLabeldate} suitably. Note also that a \cmd{literal} command will always be used when found and so this should always be the last thing in the list. If the value of a \cmd{literal} command is a valid localization string, then this will be resolved in the current language, otherwise the value is used as a literal string as-is. This is the default definition:
\begin{lstlisting}[style=latex]{}
\DeclareLabeldate{%
@@ -7214,30 +7191,7 @@ Defines the fields to consider when generating the \bibfield{labeltitle} field (
}
\end{lstlisting}
%
-The \bibfield{labeltitle} field may be customized globally or on a per-type basis. If the optional \prm{entrytype} argument is given, the specification applies to the respective entry type. If not, it is applied globally. The \prm{entrytype} argument may be a comma"=separated list of values. This command may only be used in the preamble. \cmd{field} may take the following options:
-
-\begin{optionlist*}
-
-\choitem[original]{form}{original,translated,romanised,uniform}
-
-Specifies the script variant of a field, if the datasource you are using supports this.
-
-\choitem[none]{lang}{<language specifier>}
-
-Specifies the \sty{babel} language variant of a field if the datasource you are using supports this. The default, if no \prm{lang} option is set, this means to use the field variant in the datasource which has no explicit language defined.
-
-\end{optionlist*}
-%
-For example, the following specification for selecting \bibfield{labeltitle} first looks for an english translation variant of the \bibfield{TITLE} field, then a romainsed variant and if neither of these can be found, the default field with no form or lang specifications.
-\begin{lstlisting}[style=latex]{}
-\DeclareLabelname{%
- \field[form=translated,lang=english]{title}
- \field[form=romanised]{title}
- \field{title}
-}
-\end{lstlisting}
-%
-See \secref{use:opt:bib:ded} for options to override this on a per-entry basis.
+The \bibfield{labeltitle} field may be customized globally or on a per-type basis. If the optional \prm{entrytype} argument is given, the specification applies to the respective entry type. If not, it is applied globally. The \prm{entrytype} argument may be a comma"=separated list of values. This command may only be used in the preamble.
\end{ltxsyntax}
@@ -7590,6 +7544,18 @@ A variant of \cmd{ifciteseen} which takes an entry key as its first argument. Si
%
Apart from the additional argument, \cmd{ifentryseen} behaves like \cmd{ifciteseen}.
+\cmditem{ifentryinbib}{entrykey}{true}{false}
+
+Executes \prm{true} if the entry \prm{entrykey} appears in the current bibliography, and \prm{false} otherwise. This command is intended for use in bibliography styles.
+
+\cmditem{iffirstcitekey}{true}{false}
+
+Executes \prm{true} if the entry currently being processed is the first one in the citation list, and \prm{false} otherwise. This command relies on the \cnt{citecount}, \cnt{citetotal}, \cnt{multicitecount} and \cnt{multicitetotal} counters (\secref{aut:fmt:ilc}) and thus is intended for use only in the \prm{loopcode} of a citation command defined with \cmd{DeclareCiteCommand}.
+
+\cmditem{iflastcitekey}{true}{false}
+
+Similar \cmd{iffirstcitekey}, but executes \prm{true} if the entry currently being processed is the last one in the citation list, and \prm{false} otherwise.
+
\cmditem{ifciteibid}{true}{false}
Expands to \prm{true} if the entry currently being processed is the same as the last one, and to \prm{false} otherwise. This command is intended for use in citation styles. If there are any \env{refsection} environments in the document, the tracking is local to these environments. Note that the <ibidem> tracker needs to be enabled explicitly with the package option \opt{ibidtracker}. The behavior of this test depends on the mode the tracker is operating in, see \secref{use:opt:pre:int} for details. If the tracker is disabled, the test always yields \prm{false}. Also see the \cmd{citetrackertrue} and \cmd{citetrackerfalse} switches in \secref{aut:aux:msc}.
@@ -8969,6 +8935,7 @@ Other expressions frequently used in citations:
\item[langitalian] The language <Italian>.
\item[langlatin] The language <Latin>.
\item[langnorwegian] The language <Norwegian>.
+\item[langpolish] The language <Polish>.
\item[langportuguese] The language <Portuguese>.
\item[langrussian] The language <Russian>.
\item[langspanish] The language <Spanish>.
@@ -8993,6 +8960,7 @@ The following strings are intended for use in phrases like <translated from [the
\item[fromitalian] The expression <from [the] Italian>.
\item[fromlatin] The expression <from [the] Latin>.
\item[fromnorwegian] The expression <from [the] Norwegian>.
+\item[frompolish] The expression <from [the] Polish>.
\item[fromportuguese] The expression <from [the] Portuguese>.
\item[fromrussian] The expression <from [the] Russian>.
\item[fromspanish] The expression <from [the] Spanish>.
@@ -9147,7 +9115,10 @@ The delimiter printed between citations if multiple entry keys are passed to a s
Similar to \cmd{multinamedelim}, but intended for the \cmd{supercite} command only.
\csitem{compcitedelim}
-Similar to \cmd{multicitedelim}, but intended for citation styles which <compress> multiple citations, \ie print the author only once if subsequent citations share the same author etc.
+Similar to \cmd{multicitedelim}, but intended for citation styles that <compress> multiple citations, \ie print the author only once if subsequent citations share the same author etc.
+
+\csitem{textcitedelim}
+Similar to \cmd{multicitedelim}, but intended for \cmd{textcite} and related commands (\secref{use:cit:cbx}).
\csitem{nametitledelim}
The delimiter to be printed between the author\slash editor and the title. This command should be incorporated in the definition of all citation commands of author-title and some verbose citation styles.
@@ -9211,6 +9182,10 @@ Similar to \cmd{mkbibdatelong} but using the language specific short date format
Prints the comma to be inserted before the final <and> in an enumeration, if applicable in the respective language.
+\csitem{finalandsemicolon}
+
+Prints the semicolon to be inserted before the final <and> in an enumeration, if applicable in the respective language.
+
\cmditem{mkbibordinal}{integer}
Takes an integer argument and prints it as an ordinal number.
@@ -9562,6 +9537,10 @@ Appends the \prm{code} to an internal hook executed at the beginning of every ci
Appends the \prm{code} to an internal hook executed once for every entry key passed to a citation command. The \prm{code} is executed immediately before the \prm{loopcode} of the command (see \secref{aut:cbx:cbx}). The bibliographic data of the respective entry is available at this point. This command may only be used in the preamble.
+\cmditem{AtEveryMultiCite}{code}
+
+Appends the \prm{code} to an internal hook executed at the beginning of every multicite command. The \prm{code} is executed immediately before the \bibfield{multiprenote} field (\secref{aut:cbx:fld}) is printed. No bibliographic data is available at this point. This command may only be used in the preamble.
+
\cmditem{AtNextCite}{code}
Similar to \cmd{AtEveryCite} but only affecting the next citation command. The internal hook is cleared after being executed once. This command may be used in the document body.
@@ -9570,9 +9549,45 @@ Similar to \cmd{AtEveryCite} but only affecting the next citation command. The i
Similar to \cmd{AtEveryCitekey} but only affecting the next entry key. The internal hook is cleared after being executed once. This command may be used in the document body.
+\cmditem{AtNextMultiCite}{code}
+
+Similar to \cmd{AtEveryMultiCite} but only affecting the next multicite command. The internal hook is cleared after being executed once. This command may be used in the document body.
+
\cmditem{AtDataInput}[entrytype]{code}
-Appends the \prm{code} to an internal hook executed once for every entry as the bibliographic data is imported from the \file{bbl} file. The \prm{entrytype} is the entry type the \prm{code} applies to. If it applies to all entry types, omit the optional argument. The \prm{code} is executed immediately after the entry has been imported. This command may only be used in the preamble. Note that, if there are any \env{refsection} environments in the document and an entry is cited in more than one of them, the \prm{code} may be executed multiple times for an entry. The \cnt{refsection} counter holds the number of the respective reference section while the data is imported.
+Appends the \prm{code} to an internal hook executed once for every entry as the bibliographic data is imported from the \file{bbl} file. The \prm{entrytype} is the entry type the \prm{code} applies to. If it applies to all entry types, omit the optional argument. The \prm{code} is executed immediately after the entry has been imported. This command may only be used in the preamble. Note that \prm{code} may be executed multiple times for an entry. This occurs when the same entry is cited in different \env{refsection} environments or the \opt{sorting} option settings incorporate more than one sorting scheme. The \cnt{refsection} counter holds the number of the respective reference section while the data is imported.
+
+\cmditem{UseBibitemHook}
+
+Executes the internal hook corresponding to \cmd{AtEveryBibitem}.
+
+\cmditem{UseEveryCiteHook}
+
+Executes the internal hook corresponding to \cmd{AtEveryCite}.
+
+\cmditem{UseEveryCitekeyHook}
+
+Executes the internal hook corresponding to \cmd{AtEveryCitekey}.
+
+\cmditem{UseEveryMultiCiteHook}
+
+Executes the internal hook corresponding to \cmd{AtMultiEveryCite}.
+
+\cmditem{UseNextCiteHook}
+
+Executes and clears the internal hook corresponding to \cmd{AtNextCite}.
+
+\cmditem{UseNextCitekeyHook}
+
+Executes and clears the internal hook corresponding to \cmd{AtNextCitekey}.
+
+\cmditem{UseNextMultiCiteHook}
+
+Executes and clears the internal hook corresponding to \cmd{AtNextMultiCite}.
+
+\cmditem{DeferNextCitekeyHook}
+
+Locally un-defines the internal hook specified by \cmd{AtNextCitekey}. This essentially defers the hook to the next entry key in the citation list, when executed in the \prm{precode} argument of \cmd{DeclareCiteCommand} (\secref{aut:cbx:cbx}).
\end{ltxsyntax}
@@ -10619,6 +10634,7 @@ Please refer to \secref{bib:cav:ref, aut:ctm:ref} for explanation.
\bottomrule
\endfoot
\textasteriskcentered & \textasteriskcentered &
+ ids\par
crossref\par
xref\par
entryset\par
@@ -10932,32 +10948,51 @@ This revision history is a list of changes relevant to users of this package. Ch
\begin{changelog}
+\begin{release}{2.7}{2013-07-07}
+\item Added field \bibfield{eventtitleaddon} to default datamodel and styles\see{bib:fld:dat}
+\item Added \cmd{ifentryinbib}, \cmd{iffirstcitekey} and \cmd{iflastcitekey}\see{aut:aux:tst}
+\item Added \bibfield{postpunct} special field, documented \bibfield{multiprenote} and \bibfield{multipostnote} special fields\see{aut:cbx:fld}
+\item Added \cmd{UseBibitemHook}, \cmd{AtEveryMultiCite}, \cmd{AtNextMultiCite}, \cmd{UseEveryCiteHook}, \cmd{UseEveryCitekeyHook}, \cmd{UseEveryMultiCiteHook}, \cmd{UseNextCiteHook}, \cmd{UseNextCitekeyHook}, \cmd{UseNextMultiCiteHook}, \cmd{DeferNextCitekeyHook}\see{aut:fmt:hok}
+\item Fixed \cmd{textcite} and related commands in the numeric and verbose styles\see{use:cit:cbx}
+\item Added multicite variants of \cmd{volcite} and related commands\see{use:cit:spc}
+\item Added \cmd{finalandsemicolon}\see{use:fmt:lng}
+\item Added citation delimiter \cmd{textcitedelim} for \cmd{textcite} and related commands to styles\see{aut:fmt:fmt}
+\item Updated Russian localization (Oleg Domanov)
+\item Fixed Brazilian and Finnish localization
+\end{release}
+
\begin{release}{2.6}{2013-04-30}
-\item Added \cmd{printunit}see{aut:pct:new}
-\item Added field \bibfield{clonesourcekey}see{aut:bbx:fld:gen}
+\item Added \cmd{printunit}\see{aut:pct:new}
+\item Added field \bibfield{clonesourcekey}\see{aut:bbx:fld:gen}
\item New options for \cmd{DeclareLabelalphaTemplate}\see{aut:ctm:lab}
\item Added \cmd{DeclareLabeldate} and retired \cmd{DeclareLabelyear}\see{aut:ctm:fld}
-\item Added \texttt{nodate} localisation string\see{aut:lng:key:msc}
+\item Added \texttt{nodate} localization string\see{aut:lng:key:msc}
\item Added \cmd{rangelen}\see{aut:aux:msc}
\item Added starred variants of \cmd{citeauthor} and \cmd{Citeauthor}\see{use:cit:txt}
\item Restored original \texttt{url} format. Added \texttt{urlfrom} localization key\see{aut:lng:key:lab}
\item Added \cmd{AtNextBibliography}\see{aut:fmt:hok}
\item Fixed related entry processing to allow nested and cyclic related entries
+\item Added Croatian localization (Ivo Pletikosić)
+\item Added Polish localization (Anastasia Kandulina, Yuriy Chernyshov)
+\item Fixed Catalan localization
+\item Added smart ``of'' for titles to Catalan and French localization
\item Misc bug fixes
\end{release}
\begin{release}{2.5}{2013-01-10}
-\item Made \texttt{url} work as a localisation string, defaulting to previously hard-coded value <\textsc{URL}>.
+\item Made \texttt{url} work as a localization string, defaulting to previously hard-coded value <\textsc{URL}>.
\item Changed some \biber\ option names to cohere with \biber\ 1.5.
\item New sourcemap step for conditionally removing entire entries\see{aut:ctm:map}\BiberOnlyMark
+\item Updated Catalan localization (Sebastià Vila-Marta)
\end{release}
\begin{release}{2.4}{2012-11-28}
\item Added \bibfield{relatedoptions} field\see{aut:ctm:rel}\BiberOnlyMark
\item Added \cmd{DeclareStyleSourcemap}\see{aut:ctm:map}\BiberOnlyMark
\item Renamed \cmd{DeclareDefaultSourcemap} to \cmd{DeclareDriverSourcemap}\see{aut:ctm:map}\BiberOnlyMark
-\item Added Czech localisation
\item Documented \cmd{DeclareFieldInputHandler}, \cmd{DeclareListInputHandler} and \cmd{DeclareNameInputHandler}.
+\item Added Czech localization (Michal Hoftich)
+\item Updated Catalan localization (Sebastià Vila-Marta)
\end{release}
\begin{release}{2.3}{2012-11-01}
@@ -10969,6 +11004,7 @@ This revision history is a list of changes relevant to users of this package. Ch
\item Added starred variant of \cmd{usebibmacro}\see{aut:aux:msc}
\item Added \cmd{ifbibmacroundef}, \cmd{iffieldformatundef}, \cmd{iflistformatundef}
and \cmd{ifnameformatundef}\see{aut:aux:msc}
+\item Added Catalan localization (Sebastià Vila-Marta)
\item Misc bug fixes
\end{release}
@@ -10980,7 +11016,7 @@ This revision history is a list of changes relevant to users of this package. Ch
\begin{release}{2.1}{2012-08-01}
\item Misc bug fixes
-\item Added better Norwegian localization
+\item Updated Norwegian localization (Håkon Malmedal)
\item Increased data model auto-loading possibilities\see{aut:ctm:dm}\BiberOnlyMark
\end{release}
diff --git a/Master/texmf-dist/doc/latex/biblatex/examples/03-localization-keys.tex b/Master/texmf-dist/doc/latex/biblatex/examples/03-localization-keys.tex
index 2e031d9b3c4..c57d824b85b 100644
--- a/Master/texmf-dist/doc/latex/biblatex/examples/03-localization-keys.tex
+++ b/Master/texmf-dist/doc/latex/biblatex/examples/03-localization-keys.tex
@@ -554,6 +554,7 @@ Other expressions frequently used in citations:
\keyitem{langitalian} The language <Italian>.
\keyitem{langlatin} The language <Latin>.
\keyitem{langnorwegian} The language <Norwegian>.
+\keyitem{langpolish} The language <Polish>.
\keyitem{langportuguese} The language <Portuguese>.
\keyitem{langrussian} The language <Russian>.
\keyitem{langspanish} The language <Spanish>.
@@ -578,6 +579,7 @@ The following strings are intended for use in phrases like <translated from [the
\keyitem{fromitalian} The expression <from [the] Italian>.
\keyitem{fromlatin} The expression <from [the] Latin>.
\keyitem{fromnorwegian} The expression <from [the] Norwegian>.
+\keyitem{frompolish} The expression <from [the] Polish>.
\keyitem{fromportuguese} The expression <from [the] Portuguese>.
\keyitem{fromrussian} The expression <from [the] Russian>.
\keyitem{fromspanish} The expression <from [the] Spanish>.