diff options
Diffstat (limited to 'Master/texmf-dist/doc/latex/biblatex/biblatex.tex')
| -rw-r--r-- | Master/texmf-dist/doc/latex/biblatex/biblatex.tex | 396 |
1 files changed, 270 insertions, 126 deletions
diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex index 0f68a5cd523..e7c01bb5d98 100644 --- a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex +++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex @@ -1,6 +1,9 @@ \documentclass{ltxdockit}[2011/03/25] \usepackage{btxdockit} -\usepackage[latin9]{inputenc} +\usepackage{fontspec} +\setmainfont[Ligatures=TeX]{TeXGyrePagella} +\setsansfont[Ligatures=TeX]{TexGyreHeros} +\setmonofont[Ligatures=NoCommon]{TeXGyreCursor} \usepackage[american]{babel} \usepackage[strict]{csquotes} \usepackage{tabularx} @@ -8,9 +11,9 @@ \usepackage{booktabs} \usepackage{shortvrb} \usepackage{pifont} -\usepackage{libertine} -\usepackage[scaled=0.8]{beramono} \usepackage{microtype} +\usepackage{typearea} +\areaset[current]{370pt}{700pt} \lstset{basicstyle=\ttfamily,keepspaces=true} \KOMAoptions{numbers=noenddot} \addtokomafont{paragraph}{\spotcolor} @@ -27,14 +30,15 @@ \patchcmd{\paragraph}{-1em}{1.5ex \@plus .2ex}{}{} \makeatother -\MakeAutoQuote{«}{»} +\MakeAutoQuote{«}{»} \MakeAutoQuote*{<}{>} \MakeShortVerb{\|} \newcommand*{\biber}{Biber\xspace} \newcommand*{\biblatex}{Biblatex\xspace} \newcommand*{\biblatexhome}{http://sourceforge.net/projects/biblatex/} -\newcommand*{\biblatexctan}{http://www.ctan.org/tex-archive/macros/latex/contrib/biblatex/} +\newcommand*{\biblatexctan}{% + http://www.ctan.org/tex-archive/macros/latex/contrib/biblatex/} \titlepage{% title={The \sty{biblatex} Package}, @@ -42,8 +46,8 @@ url={\biblatexhome}, author={Philipp Lehman (with Audrey Boruvka, Philip Kime and Joseph Wright)}, email={}, - revision={2.5}, - date={10/01/2013}} + revision={2.6}, + date={30/04/2013}} \hypersetup{% pdftitle={The \biblatex Package}, @@ -151,22 +155,23 @@ Please use the \sty{biblatex} project page on GitHub to report bugs and submit f \subsection{Acknowledgments} -The language modules of this package include contributions by the following contributors (in the order of submission): -Ignacio Fernández Galván (Spanish), -Enrico Gregorio (Italian), -Johannes Wilm, Håkon Malmedal (Danish\slash Norwegian), -Per Starbäck, Carl-Gustav Werner, Filip Åsblom (Swedish), -Augusto Ritter Stoffel (Brazilian), -Alexander van Loon (Dutch), -Apostolos Syropoulos (Greek), -Hannu Väisänen (Finnish), -Prokopis (Greek), -Mateus Araújo (Brazilian), -Andrea Marchitelli (Italian), -José Carlos Santos (Portuguese), -Oleg Domanov (Russian), -Pieter Belmans (Dutch), -Baldur Kristinsson (Icelandic). +The language modules of this package are made possible thanks to the following contributors: +Augusto Ritter Stoffel, Mateus Araújo (Brazilian); +Sebastià Vila-Marta (Catalan); +Ivo Pletikosić (Croatian); +Michal Hoftich (Czech); +Johannes Wilm (Danish\slash Norwegian); +Alexander van Loon, Pieter Belmans (Dutch); +Hannu Väisänen, Janne Kujanpää (Finnish); +Denis Bitouzé (French); +Apostolos Syropoulos, Prokopis (Greek); +Baldur Kristinsson (Icelandic); +Enrico Gregorio, Andrea Marchitelli (Italian); +HÃ¥kon Malmedal (Norwegian); +José Carlos Santos (Portuguese); +Oleg Domanov (Russian); +Ignacio Fernández Galván (Spanish); +Per Starbäck, Carl-Gustav Werner, Filip Ã…sblom (Swedish). \subsection{Prerequisites} \label{int:pre} @@ -315,6 +320,7 @@ compatibility matrix for the recent versions. \toprule Biber version & \biblatex\ version\\ \midrule +1.6 & 2.6\\ 1.5 & 2.5\\ 1.4 & 2.4\\ 1.3 & 2.3\\ @@ -755,7 +761,7 @@ The Digital Object Identifier of the work. \fielditem{edition}{integer or literal} -The edition of a printed publication. This must be an integer, not an ordinal. Don't say |edition={First}| or |edition={1st}| but |edition={1}|. The bibliography style converts this to a language dependent ordinal. It is also possible to give the edition as a literal string, for example «Third, revised and expanded edition». +The edition of a printed publication. This must be an integer, not an ordinal. Don't say |edition={First}| or |edition={1st}| but |edition={1}|. The bibliography style converts this to a language dependent ordinal. It is also possible to give the edition as a literal string, for example «Third, revised and expanded edition». \listitem{editor}{name} @@ -815,7 +821,7 @@ The date of a conference, a symposium, or some other event in \bibtype{proceedin \fielditem{eventtitle}{literal} -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}. +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{file}{verbatim} @@ -835,7 +841,7 @@ A publication notice for unusual publications which do not fit into any of the c \fielditem{indextitle}{literal} -A title to use for indexing instead of the regular \bibfield{title} field. This field may be useful if you have an entry with a title like «An Introduction to \dots» and want that indexed as «Introduction to \dots, An». Style authors should note that \sty{biblatex} automatically copies the value of the \bibfield{title} field to \bibfield{indextitle} if the latter field is undefined. +A title to use for indexing instead of the regular \bibfield{title} field. This field may be useful if you have an entry with a title like «An Introduction to \dots» and want that indexed as «Introduction to \dots, An». Style authors should note that \sty{biblatex} automatically copies the value of the \bibfield{title} field to \bibfield{indextitle} if the latter field is undefined. \listitem{institution}{literal} @@ -927,7 +933,7 @@ An addon to be printed immediately after the author name in the bibliography. No \fielditem{note}{literal} -Miscellaneous bibliographic data which does not fit into any other field. The \bibfield{note} field may be used to record bibliographic data in a free format. Publication facts such as «Reprint of the edition London 1831» are typical candidates for the \bibfield{note} field. See also \bibfield{addendum}. +Miscellaneous bibliographic data which does not fit into any other field. The \bibfield{note} field may be used to record bibliographic data in a free format. Publication facts such as «Reprint of the edition London 1831» are typical candidates for the \bibfield{note} field. See also \bibfield{addendum}. \fielditem{number}{literal} @@ -987,7 +993,7 @@ The publication state of the work, \eg\ <in press>. See \secref{aut:lng:key:pst} \fielditem{series}{literal} -The name of a publication series, such as «Studies in \dots», or the number of a journal series. Books in a publication series are usually numbered. The number or volume of a book in a series is given in the \bibfield{number} field. Note that the \bibtype{article} entry type makes use of the \bibfield{series} field as well, but handles it in a special way. See \secref{bib:use:ser} for details. +The name of a publication series, such as «Studies in \dots», or the number of a journal series. Books in a publication series are usually numbered. The number or volume of a book in a series is given in the \bibfield{number} field. Note that the \bibtype{article} entry type makes use of the \bibfield{series} field as well, but handles it in a special way. See \secref{bib:use:ser} for details. \listitem{shortauthor}{name} @@ -1003,7 +1009,7 @@ A special designation to be used by the citation style instead of the usual labe \fielditem{shorthandintro}{literal} -The verbose citation styles which comes with this package use a phrase like «henceforth cited as [shorthand]» to introduce shorthands on the first citation. If the \bibfield{shorthandintro} field is defined, it overrides the standard phrase. Note that the alternative phrase must include the shorthand. +The verbose citation styles which comes with this package use a phrase like «henceforth cited as [shorthand]» to introduce shorthands on the first citation. If the \bibfield{shorthandintro} field is defined, it overrides the standard phrase. Note that the alternative phrase must include the shorthand. \fielditem{shortjournal}{literal} @@ -1092,13 +1098,13 @@ 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{100pt}@{}X@{}} +\begin{tabularx}{\textwidth}{@{}p{100pt}@{}p{150pt}@{}X@{}} \toprule \multicolumn{1}{@{}H}{Language} & \multicolumn{1}{@{}H}{Region/Dialect} & \multicolumn{1}{@{}H}{Babel Identifiers} \\ \cmidrule(r){1-1}\cmidrule(r){2-2}\cmidrule{3-3} -Catalan & Andorra, Balearic islands, Catalonia, Valencia, Roussillon & \opt{catalan} \\ +Catalan & Spain, France, Andorra, Italy & \opt{catalan} \\ Czech & Czech Republic & \opt{czech} \\ Danish & Denmark & \opt{danish} \\ Dutch & Netherlands & \opt{dutch} \\ @@ -1157,7 +1163,7 @@ A comma"=separated list of entry options in \keyval notation. This field is used A special field used to modify the sorting order of the bibliography. This field is the first item the sorting routine considers when sorting the bibliography, hence it may be used to arrange the entries in groups. This may be useful when creating subdivided bibliographies with the bibliography filters. Please refer to \secref{use:srt} for further details. Also see \secref{aut:ctm:srt}. This field is consumed by the backend processing and does not appear in the \path{.bbl}. -\fielditem{related}{comma"=separated values} +\fielditem{related}{comma"=separated values\BiberOnlyMark} Citation keys of other entries which have a relationship to this entry. The relationship is specified by the \bibfield{relatedtype} field. Please refer to \secref{use:rel} for further details. @@ -1175,7 +1181,7 @@ formatting directives and bibliography macros for the related entries. Please re A field used to override the bibliography string specified by \bibfield{relatedtype}. Please refer to \secref{use:rel} for further details. -\fielditem{sortkey}{literal\BiberOnlyMark} +\fielditem{sortkey}{literal} A field used to modify the sorting order of the bibliography. Think of this field as the master sort key. If present, \sty{biblatex} uses this field during sorting and ignores everything else, except for the \bibfield{presort} 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}. @@ -1189,7 +1195,7 @@ Similar to \bibfield{sortkey} but used in the list of shorthands. If present, \s \fielditem{sorttitle}{literal} -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 <I> rather than <A>. 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}. +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 <I> rather than <A>. 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} @@ -1505,7 +1511,7 @@ The \bibtype{article} entry type makes use of the \bibfield{series} field as wel ... \end{lstlisting} % -This entry will be printed as «\emph{Journal Name}. 3rd ser. 15.7 (1995)». Some journals use designations such as «old series» and «new series» instead of a number. Such designations may be given in the \bibfield{series} field as well, either as a literal string or as a localization key. Consider the following example which makes use of the localization key \texttt{newseries}: +This entry will be printed as «\emph{Journal Name}. 3rd ser. 15.7 (1995)». Some journals use designations such as «old series» and «new series» instead of a number. Such designations may be given in the \bibfield{series} field as well, either as a literal string or as a localization key. Consider the following example which makes use of the localization key \texttt{newseries}: \begin{lstlisting}[style=bibtex]{} @Article{..., @@ -1516,7 +1522,7 @@ This entry will be printed as «\emph{Journal Name}. 3rd ser. 15.7 (1995)». Some ... \end{lstlisting} % -This entry will be printed as «\emph{Journal Name}. New ser. 9 (1998)». See \secref{aut:lng:key} for a list of localization keys defined by default. +This entry will be printed as «\emph{Journal Name}. New ser. 9 (1998)». See \secref{aut:lng:key} for a list of localization keys defined by default. \subsubsection{Date Specifications} \label{bib:use:dat} @@ -1701,7 +1707,7 @@ hash\_size & & 5000 & 10000 & 19000 & 35000 \\ Sorry---you've exceeded BibTeX's total number of fields 17250 \end{lstlisting} % -\Tabref{bib:cav:tab2} gives an overview of the various capacity parameters of \file{bibtex8} and the command"=line switches used to increase their default values. There are two ways to increase the capacity on the command"=line. You may use a high"=level switch like |--huge| to select a different set of defaults or low"=level switches such as |--mfields| to modify a single parameter. The first thing you should always do is run \file{bibtex8} with the |--wolfgang| switch. Don't even bother trying anything else. With a very large database, however, even that capacity may be too small. In this case, you need to resort to the low"=level switches. Here is an example of a set of switches which should cope with a \file{bib} file containing about 1000 entries: +\Tabref{bib:cav:tab2} gives an overview of the various capacity parameters of \file{bibtex8} and the command"=line switches used to increase their default values. There are two ways to increase the capacity on the command"=line. You may use a high"=level switch like |--huge| to select a different set of defaults or low"=level switches such as |--mfields| to modify a single parameter. The first thing you should always do is run \file{bibtex8} with the |--wolfgang| switch. Don't even bother trying anything else. With a very large database, however, even that capacity may be too small. In this case, you need to resort to the low"=level switches. Here is an example of a set of switches which should cope with a \file{bib} file containing about 1000 entries: \begin{lstlisting}[style=plain]{} bibtex8 --wolfgang --mcites 30000 --mentints 30000 --mentstrs 40000 @@ -1719,7 +1725,7 @@ When taking a closer look at \tabref{bib:cav:tab2}, you will notice that there a \paragraph{\bibtex} \label{bib:cav:enc:btx} -Traditional \bibtex can only alphabetize Ascii characters correctly. If the bibliographic data includes non"=Ascii characters, they have to be given in Ascii notation. For example, instead of typing a letter like <ä> directly, you need to input it as |\"a|, using an accent command and the Ascii letter. This Ascii notation needs to be wrapped in a pair of curly braces. Traditional \bibtex will then ignore the accent and use the Ascii letter for sorting. Here are a few examples: +Traditional \bibtex can only alphabetize Ascii characters correctly. If the bibliographic data includes non"=Ascii characters, they have to be given in Ascii notation. For example, instead of typing a letter like <ä> directly, you need to input it as |\"a|, using an accent command and the Ascii letter. This Ascii notation needs to be wrapped in a pair of curly braces. Traditional \bibtex will then ignore the accent and use the Ascii letter for sorting. Here are a few examples: \begin{lstlisting}[style=bibtex,upquote]{} author = {S<<{\'a}>>nchez, Jos<<{\'e}>>}, @@ -1728,20 +1734,20 @@ translator = {Ferdi<<{\`e}>>re, Fr<<{\c{c}}>>ois}, title = {<<{\OE}>>uvres compl<<{\`e}>>tes}, \end{lstlisting} % -Apart from it being inconvenient, there are two major issues with this convention. One subtle problem is that the extra set of braces suppresses the kerning on both sides of all non"=Ascii letters. But first and foremost, simply ignoring all accents may not be the correct way to handle them. For example, in Danish, the letter <å> is the very last letter of the alphabet, so it should be alphabetized after <z>. \bibtex will sort it like an <a>. The <æ> ligature and the letter <ø> are also sorted after <z> in this language. There are similar cases in Norwegian. In Swedish, the letter <ö> is the very last letter of the alphabet and the letters <å> and <ä> are also alphabetized after <z>, rather than like an <a>. What's more, even the sorting of Ascii characters is done in a rather peculiar way by traditional \bibtex because the sorting algorithm uses Ascii codepage order (\texttt{0-9,A-Z,a-z}). This implies that the lowercase letter <a> would end up after the uppercase <Z>, which is not even acceptable in the language \bibtex was originally designed for. The traditional \file{bst} files work around this problem by converting all strings used for sorting to lowercase, \ie sorting is effectively case"=insensitive. See also \secref{bib:cav:enc:enc}. +Apart from it being inconvenient, there are two major issues with this convention. One subtle problem is that the extra set of braces suppresses the kerning on both sides of all non"=Ascii letters. But first and foremost, simply ignoring all accents may not be the correct way to handle them. For example, in Danish, the letter <Ã¥> is the very last letter of the alphabet, so it should be alphabetized after <z>. \bibtex will sort it like an <a>. The <æ> ligature and the letter <ø> are also sorted after <z> in this language. There are similar cases in Norwegian. In Swedish, the letter <ö> is the very last letter of the alphabet and the letters <Ã¥> and <ä> are also alphabetized after <z>, rather than like an <a>. What's more, even the sorting of Ascii characters is done in a rather peculiar way by traditional \bibtex because the sorting algorithm uses Ascii codepage order (\texttt{0-9,A-Z,a-z}). This implies that the lowercase letter <a> would end up after the uppercase <Z>, which is not even acceptable in the language \bibtex was originally designed for. The traditional \file{bst} files work around this problem by converting all strings used for sorting to lowercase, \ie sorting is effectively case"=insensitive. See also \secref{bib:cav:enc:enc}. \paragraph{\file{bibtex8}} \label{bib:cav:enc:bt8} Switching to \file{bibtex8} will help in such cases. \file{bibtex8} can sort case"=sensitively and it can handle 8-bit characters properly, provided that you supply it with a suitable \file{csf} file and give the |--csfile| switch on the command line. This also implies that it is possible to apply language specific sorting rules to the bibliography. The \sty{biblatex} package comes with \file{csf} files for some common Western European encodings. \bin{bibtex8} also ships with a few \file{csf} files. Note that \file{biblatex.bst} can not detect if it is running under traditional \bibtex or \file{bibtex8}, hence the \opt{bibtex8} package option. By default, sorting is case-insensitive since this is required for traditional \bibtex. If the \opt{bibtex8} package option is enabled, sorting is case-sensitive. -Since \file{bibtex8} is backwards compatible with traditional \bibtex, it is possible to mix 8-bit input and Ascii notation. This is useful if the encoding used in the \file{bib} file does not cover all required characters. There are also a few marginal cases in which the Ascii notation scheme would yield better sorting results. A typical example is the ligature <½>. \file{bibtex8} will handle this ligature like a single character. Depending on the sorting scheme defined in the \file{csf} file, it could be treated like an <o> or alphabetized after the letter <o> but it can not be sorted as <oe>. The Ascii notation (|\oe|) is equivalent to <oe> during sorting: +Since \file{bibtex8} is backwards compatible with traditional \bibtex, it is possible to mix 8-bit input and Ascii notation. This is useful if the encoding used in the \file{bib} file does not cover all required characters. There are also a few marginal cases in which the Ascii notation scheme would yield better sorting results. A typical example is the ligature <Å“>. \file{bibtex8} will handle this ligature like a single character. Depending on the sorting scheme defined in the \file{csf} file, it could be treated like an <o> or alphabetized after the letter <o> but it can not be sorted as <oe>. The Ascii notation (|\oe|) is equivalent to <oe> during sorting: \begin{lstlisting}[style=bibtex,upquote]{} -title = {<<¼>>uvres compl<<è>>tes}, -title = {<<{\OE}>>uvres compl<<è>>tes}, +title = {<<Å’>>uvres compl<<è>>tes}, +title = {<<{\OE}>>uvres compl<<è>>tes}, \end{lstlisting} % -Sometimes even that is not sufficient and further tricks are required. For example, the letter <ß> in German is particularly tricky. This letter is essentially alphabetized as <ss> but after <ss>. The name <Baßmann> would be alphabetized as follows: Basmann\slash Bassmann\slash Baßmann\slash Bastmann. In this case, the Ascii notation (|\ss|) would yield slightly better sorting results than <ß> in conjunction with a \file{csf} file which treats <ß> like <s>: +Sometimes even that is not sufficient and further tricks are required. For example, the letter <ß> in German is particularly tricky. This letter is essentially alphabetized as <ss> but after <ss>. The name <Baßmann> would be alphabetized as follows: Basmann\slash Bassmann\slash Baßmann\slash Bastmann. In this case, the Ascii notation (|\ss|) would yield slightly better sorting results than <ß> in conjunction with a \file{csf} file which treats <ß> like <s>: \begin{lstlisting}[style=bibtex,upquote]{} author = {Ba<<{\ss}>>mann, Paul}, @@ -1750,7 +1756,7 @@ author = {Ba<<{\ss}>>mann, Paul}, To get it absolutely right, however, you need to resort to the \bibfield{sortname} field: \begin{lstlisting}[style=bibtex,upquote]{} -author = {Ba<<ß>>mann, Paul}, +author = {Ba<<ß>>mann, Paul}, sortname = {Ba<<sszz>>mann, Paul}, \end{lstlisting} % @@ -1759,7 +1765,7 @@ Not only \bibtex, \latex needs to know about the encoding as well. See \secref{b \paragraph{\biber} \biber handles Ascii, 8-bit encodings such as Latin\,1, and \utf. It features true Unicode support and is capable of reencoding the \file{bib} data on the fly in a robust way. For sorting, \biber uses a Perl implementation of the Unicode Collation Algorithm (\acr{UCA}), as outlined in Unicode Technical Standard \#10.\fnurl{http://unicode.org/reports/tr10/} Collation tailoring based on the Unicode Common Locale Data Repository (\acr{CLDR}) is also supported.\fnurl{http://cldr.unicode.org/} The bottom line is that \biber will deliver sorting results far superior to both \bibtex and \file{bibtex8} in many cases. If you are interested in the technical details, section 1.8 of Unicode Technical Standard \#10 will provide you with a very concise summary of why the inadequateness of traditional \bibtex and even \bin{bibtex8} is of a very general nature and not limited to the lack of \utf support.\fnurl{http://unicode.org/reports/tr10/#Common_Misperceptions} -Supporting Unicode implies much more than handling \utf input. Unicode is a complex standard covering more than its most well-known parts, the Unicode character encoding and transport encodings such as \utf. It also standardizes aspects such as string collation, which is required for language-sensitive sorting. For example, by using the Unicode Collation Algorithm, \biber can handle the character <ß> mentioned as an example in \secref{bib:cav:enc:bt8} without any manual intervention. All you need to do to get localized sorting is specify the locale: +Supporting Unicode implies much more than handling \utf input. Unicode is a complex standard covering more than its most well-known parts, the Unicode character encoding and transport encodings such as \utf. It also standardizes aspects such as string collation, which is required for language-sensitive sorting. For example, by using the Unicode Collation Algorithm, \biber can handle the character <ß> mentioned as an example in \secref{bib:cav:enc:bt8} without any manual intervention. All you need to do to get localized sorting is specify the locale: \begin{lstlisting}[style=latex]{} \usepackage[backend=biber,sortlocale=de]{biblatex} @@ -1880,6 +1886,18 @@ If this option is enabled, \sty{biblatex} will ignore \sty{inputenc}'s \opt{utf8 This solution may be acceptable as a workaround if the data in the \file{bib} file is mostly Ascii anyway, with only a few strings, such as some authors' names, causing problems. However, keep in mind that it will not magically make traditional \tex or \pdftex support Unicode. It may help if the occasional odd character is not supported by \sty{inputenc}, but may still be processed by \tex when using an accent command (\eg |\d{S}| instead of \texttt{\d{S}}). If you need full Unicode support, however, switch to \xetex or \luatex. +Typical errors when \sty{inputenc} cannot handle a certain UTF-8 character are: + +\begin{verbatim} +Package inputenc Error: Unicode char \u8: not set up for use with LaTeX +\end{verbatim} +% +but also less obvious things like: + +\begin{verbatim} +! Argument of \UTFviii@three@octets has an extra }. +\end{verbatim} + \subsubsection{Editors and Compiler Scripts} \label{bib:cav:ide} @@ -1996,7 +2014,7 @@ The sorting order of the list of shorthands. The following choices are available The sorting order of shorthands with \biber is more flexible and is set with the \opt{sorting} option to the \cmd{printshorthands} command. -\boolitem[true]{related} +\boolitem[true]{related}[\BiberOnly] Whether or not to use information from related entries or not. See \secref{use:rel}. @@ -2050,13 +2068,13 @@ This option controls multilingual support. When set to \opt{auto}, \sty{biblatex \begin{table} \tablesetup -\begin{tabularx}{\textwidth}{@{}p{100pt}@{}p{100pt}@{}>{\ttfamily}X@{}} +\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 & Andorra, Balearic islands, Catalonia, Valencia, Roussillon & catalan \\ +Catalan & Spain, France, Andorra, Italy & catalan \\ Czech & Czech Republic & czech \\ Danish & Denmark & danish \\ Dutch & Netherlands & dutch \\ @@ -2269,6 +2287,10 @@ January 21--30, 2010\par % As seen in the above examples, the actual date format is language specific. Note that the month name in all long formats is responsive to the \opt{abbreviate} package option. The leading zeros in all short formats may be controlled separately with the \opt{datezeros} package option. +\optitem[comp]{datelabel}{\opt{short}, \opt{long}, \opt{terse}, \opt{comp}, \opt{iso8601}} + +Similar to the \opt{date} option but controls the format of the date field selected with \cmd{DeclareLabeldate}. + \optitem[comp]{origdate}{\opt{short}, \opt{long}, \opt{terse}, \opt{comp}, \opt{iso8601}} Similar to the \opt{date} option but controls the format of the \bibfield{origdate}. @@ -2295,7 +2317,7 @@ This option controls whether \texttt{long} and \texttt{comp} dates are printed w \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. 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} @@ -2433,7 +2455,7 @@ This option controls the <ibidem> tracker which is required by the \cmd{ifciteib \item[true] Enable the tracker in global mode. \item[false] Disable the tracker. \item[context] Enable the tracker in context"=sensitive mode. In this mode, citations in footnotes and in the body text are tracked separately. -\item[strict] Enable the tracker in strict mode. In this mode, potentially ambiguous references are suppressed. A reference is considered ambiguous if either the current citation (the one including the <ibidem>) or the previous citation (the one the <ibidem> refers to) consists of a list of references.\footnote{For example, suppose the initial citation is «Jones, \emph{Title}; Williams, \emph{Title}» and the following one «ibidem». From a technical point of view, it is fairly clear that the <ibidem> refers to <Williams> because this is the last reference processed by the previous citation command. To a human reader, however, this may not be obvious because the <ibidem> may also refer to both titles. The strict mode avoids such ambiguous references.} +\item[strict] Enable the tracker in strict mode. In this mode, potentially ambiguous references are suppressed. A reference is considered ambiguous if either the current citation (the one including the <ibidem>) or the previous citation (the one the <ibidem> refers to) consists of a list of references.\footnote{For example, suppose the initial citation is «Jones, \emph{Title}; Williams, \emph{Title}» and the following one «ibidem». From a technical point of view, it is fairly clear that the <ibidem> refers to <Williams> because this is the last reference processed by the previous citation command. To a human reader, however, this may not be obvious because the <ibidem> may also refer to both titles. The strict mode avoids such ambiguous references.} \item[constrict] This mode combines the features of \opt{context} and \opt{strict}. It also keeps track of footnote numbers and detects potentially ambiguous references in footnotes in a stricter way than the \opt{strict} option. In addition to the conditions imposed by the \opt{strict} option, a reference in a footnote will only be considered as unambiguous if the current citation and the previous citation are given in the same footnote or in immediately consecutive footnotes. \end{valuelist} @@ -2527,9 +2549,9 @@ Whether or not to provide the special field \bibfield{extratitle}, see \secref{a 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. -\boolitem[false]{labelyear} +\boolitem[false]{labeldate} -Whether or not to provide the special fields \bibfield{labelyear} and \bibfield{extrayear}, see \secref{aut:bbx:fld} for details. +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. \boolitem[false]{singletitle} @@ -2562,7 +2584,7 @@ Whether or not to update the \cnt{uniquelist} counter, see \secref{aut:aux:tst} \begin{valuelist} \item[true] Disambiguate the \bibfield{labelname} list. \item[false] Disable this feature. -\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{labelyear}{true}. +\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{labeldate}{true}. \end{valuelist} % 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. See \secref{aut:cav:amb} for further details and practical examples. @@ -2580,7 +2602,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\\ -labelyear & labelyear & extrayear & labelname+labelyear\\ +labeldate & labelyear & extrayear & labelname+labelyear\\ labeltitle & --- & extratitle & labelname+labeltitle\\ labeltitleyear & --- & extratitleyear & labeltitle+labelyear\\ \bottomrule @@ -2628,7 +2650,7 @@ With the standard styles, the \bibfield{translator} is printed after the title b \boolitem[false]{useprefix} -Whether the name prefix (von, van, of, da, de, della, etc.) is considered when printing the last name in citations. This also affects the sorting and formatting of the bibliography as well as the generation of certain types of labels. If this option is enabled, \sty{biblatex} always precedes the last name with the prefix. For example, Ludwig van Beethoven would be cited as «Beethoven» and alphabetized as «Beethoven, Ludwig van» by default. If this option is enabled, he is cited as «van Beethoven» and alphabetized as «Van Beethoven, Ludwig» instead. +Whether the name prefix (von, van, of, da, de, della, etc.) is considered when printing the last name in citations. This also affects the sorting and formatting of the bibliography as well as the generation of certain types of labels. If this option is enabled, \sty{biblatex} always precedes the last name with the prefix. For example, Ludwig van Beethoven would be cited as «Beethoven» and alphabetized as «Beethoven, Ludwig van» by default. If this option is enabled, he is cited as «van Beethoven» and alphabetized as «Van Beethoven, Ludwig» instead. \BiberOnlyMark With \biber, this option is also settable on a per-type basis. \optitem{indexing}{\opt{true}, \opt{false}, \opt{cite}, \opt{bib}} @@ -2736,37 +2758,37 @@ The citation styles which come with this package implement several common citati \begin{marglist} \item[numeric] -This style implements a numeric citation scheme similar to the standard bibliographic facilities of \latex. It should be employed in conjunction with a numeric 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{labelnumber}{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 «[5c]» which point to a subentry in a set (the third one in this example). See the style example for details. +This style implements a numeric citation scheme similar to the standard bibliographic facilities of \latex. It should be employed in conjunction with a numeric 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{labelnumber}{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 «[5c]» which point to a subentry in a set (the third one in this example). See the style example for details. \item[numeric-comp] -A compact variant of the \texttt{numeric} style which prints a list of more than two consecutive numbers as a range. This style is similar to the \sty{cite} package and the \opt{sort\&compress} option of the \sty{natbib} package in numerical mode. For example, instead of «[8, 3, 1, 7, 2]» this style would print «[1--3, 7, 8]». It is intended for in-text citations. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{sortcites}{true}, \kvopt{labelnumber}{true}. It also provides the \opt{subentry} option. +A compact variant of the \texttt{numeric} style which prints a list of more than two consecutive numbers as a range. This style is similar to the \sty{cite} package and the \opt{sort\&compress} option of the \sty{natbib} package in numerical mode. For example, instead of «[8, 3, 1, 7, 2]» this style would print «[1--3, 7, 8]». It is intended for in-text citations. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{sortcites}{true}, \kvopt{labelnumber}{true}. It also provides the \opt{subentry} option. \item[numeric-verb] -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. +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 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}. +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{labelyear}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}. +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{labeldate}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}. \item[authoryear-comp] -A compact variant of the \texttt{authoryear} style which prints the author only once if subsequent references passed to a single citation command share the same author. If they share the same year as well, the year is also printed only once. For example, instead of «Doe 1995b; Doe 1992; Jones 1998; Doe 1995a» this style would print «Doe 1992, 1995a,b; Jones 1998». 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{sortcites}{true}, \kvopt{labelyear}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}. +A compact variant of the \texttt{authoryear} style which prints the author only once if subsequent references passed to a single citation command share the same author. If they share the same year as well, the year is also printed only once. For example, instead of «Doe 1995b; Doe 1992; Jones 1998; Doe 1995a» this style would print «Doe 1992, 1995a,b; Jones 1998». 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{sortcites}{true}, \kvopt{labeldate}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}. \item[authoryear-ibid] -A variant of the \texttt{authoryear} style which replaces repeated citations by the abbreviation \emph{ibidem} unless the citation is the first one on the current page or double-page spread, or the \emph{ibidem} would be ambiguous in the sense of the package option \kvopt{ibidtracker}{constrict}. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labelyear}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}, \kvopt{ibidtracker}{constrict}, \kvopt{pagetracker}{true}. This style also provides an additional preamble option called \opt{ibidpage}. See the style example for details. +A variant of the \texttt{authoryear} style which replaces repeated citations by the abbreviation \emph{ibidem} unless the citation is the first one on the current page or double-page spread, or the \emph{ibidem} would be ambiguous in the sense of the package option \kvopt{ibidtracker}{constrict}. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labeldate}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}, \kvopt{ibidtracker}{constrict}, \kvopt{pagetracker}{true}. This style also provides an additional preamble option called \opt{ibidpage}. See the style example for details. \item[authoryear-icomp] -A style combining \texttt{authoryear-comp} and \texttt{authoryear-ibid}. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labelyear}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}, \kvopt{ibidtracker}{constrict}, \kvopt{pagetracker}{true}, \kvopt{sortcites}{true}. This style also provides an additional preamble option called \opt{ibidpage}. See the style example for details. +A style combining \texttt{authoryear-comp} and \texttt{authoryear-ibid}. The style will set the following package options at load time: \kvopt{autocite}{inline}, \kvopt{labeldate}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}, \kvopt{ibidtracker}{constrict}, \kvopt{pagetracker}{true}, \kvopt{sortcites}{true}. This style also provides an additional preamble option called \opt{ibidpage}. See the style example for details. \item[authortitle] This style implements a simple author"=title citation scheme. It will make use of the \bibfield{shorttitle} field, if available. It is intended for citations given in footnotes. The style will set the following package options at load time: \kvopt{autocite}{footnote}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}. \item[authortitle-comp] -A compact variant of the \texttt{authortitle} style which prints the author only once if subsequent references passed to a single citation command share the same author. For example, instead of «Doe, \emph{First title}; Doe, \emph{Second title}» this style would print «Doe, \emph{First title}, \emph{Second title}». It is intended for citations given in footnotes. The style will set the following package options at load time: \kvopt{autocite}{footnote}, \kvopt{sortcites}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}. +A compact variant of the \texttt{authortitle} style which prints the author only once if subsequent references passed to a single citation command share the same author. For example, instead of «Doe, \emph{First title}; Doe, \emph{Second title}» this style would print «Doe, \emph{First title}, \emph{Second title}». It is intended for citations given in footnotes. The style will set the following package options at load time: \kvopt{autocite}{footnote}, \kvopt{sortcites}{true}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}. \item[authortitle-ibid] A variant of the \texttt{authortitle} style which replaces repeated citations by the abbreviation \emph{ibidem} unless the citation is the first one on the current page or double-page spread, or the \emph{ibidem} would be ambiguous in the sense of the package option \kvopt{ibidtracker}{constrict}. It is intended for citations given in footnotes. The style will set the following package options at load time: \kvopt{autocite}{footnote}, \kvopt{uniquename}{full}, \kvopt{uniquelist}{true}, \kvopt{ibidtracker}{constrict}, \kvopt{pagetracker}{true}. This style also provides an additional preamble option called \opt{ibidpage}. See the style example for details. @@ -2835,7 +2857,7 @@ This style prints a numeric label similar to the standard bibliographic faciliti This style prints an alphabetic label similar to the \path{alpha.bst} style of traditional \bibtex. It is intended for use in conjunction with an alphabetic citation style. Note that the \bibfield{shorthand} field overrides the default label. The style will set the following package options at load time: \kvopt{labelalpha}{true}, \kvopt{sorting}{anyt}. \item[authoryear] -This style differs from the other styles in that the publication date is not printed towards the end of the entry but rather after the author\slash editor. It is intended for use in conjunction with an author"=year citation style. Recurring author and editor names are replaced by a dash unless the entry is the first one on the current page or double-page spread. This style provides an additional preamble option called \opt{dashed} which controls this feature. It also provided a preamble option called \opt{mergedate}. See the style example for details. The style will set the following package options at load time: \kvopt{labelyear}{true}, \kvopt{sorting}{nyt}, \kvopt{pagetracker}{true}, \kvopt{mergedate}{true}. +This style differs from the other styles in that the publication date is not printed towards the end of the entry but rather after the author\slash editor. It is intended for use in conjunction with an author"=year citation style. Recurring author and editor names are replaced by a dash unless the entry is the first one on the current page or double-page spread. This style provides an additional preamble option called \opt{dashed} which controls this feature. It also provided a preamble option called \opt{mergedate}. See the style example for details. The style will set the following package options at load time: \kvopt{labeldate}{true}, \kvopt{sorting}{nyt}, \kvopt{pagetracker}{true}, \kvopt{mergedate}{true}. \item[authortitle] This style does not print any label at all. It is intended for use in conjunction with an author"=title citation style. Recurring author and editor names are replaced by a dash unless the entry is the first one on the current page or double-page spread. This style also provides an additional preamble option called \opt{dashed} which controls this feature. See the style example for details. The style will set the following package options at load time: \kvopt{pagetracker}{true}. @@ -2863,7 +2885,7 @@ This style prints all bibliographic data in tabular format. It is intended for d \subsection{Related Entries} \label{use:rel} -Almost all bibliography styles require authors to specify certain types of relationship between entries such as «Reprint of», «Reprinted in» etc. It is impossible to provide data fields to cover all of these relationships and so \sty{biblatex} provides a general mechanism for this using the entry fields \bibfield{related}, \bibfield{relatedtype} and \bibfield{relatedstring}. A related entry does not need to be cited and does not appear in the bibliography itself (unless of course it is also cited itself independently) as a clone is taken of the related entry to be used as a data source. The \bibfield{relatedtype} field should specify a localization string which will be printed before the information from the related entries is printed, for example «Orig. Pub. as». The \bibfield{relatedstring} field can be used to override the string determined via \bibfield{relatedtype}. Some examples: +Almost all bibliography styles require authors to specify certain types of relationship between entries such as «Reprint of», «Reprinted in» etc. It is impossible to provide data fields to cover all of these relationships and so \sty{biblatex} provides a general mechanism for this using the entry fields \bibfield{related}, \bibfield{relatedtype} and \bibfield{relatedstring}. A related entry does not need to be cited and does not appear in the bibliography itself (unless of course it is also cited itself independently) as a clone is taken of the related entry to be used as a data source. The \bibfield{relatedtype} field should specify a localization string which will be printed before the information from the related entries is printed, for example «Orig. Pub. as». The \bibfield{relatedstring} field can be used to override the string determined via \bibfield{relatedtype}. Some examples: \begin{lstlisting}[style=bibtex]{} @Book{key1, @@ -2881,7 +2903,7 @@ Almost all bibliography styles require authors to specify certain types of relat Here we specify that entry \texttt{key1} is a reprint of entry \texttt{key2}. In the bibliography driver for \texttt{Book} entries, when \cmd{usebibmacro\{related\}} is called for entry \texttt{key1}: \begin{itemize} -\item If the localization string «\texttt{reprintof}» is defined, it is printed, then +\item If the localization string «\texttt{reprintof}» is defined, it is printed in the \texttt{relatedstring:reprintof} format. If this formatting directive is undefined, the string is printed in the \texttt{relatedstring:default} format. \item If the \texttt{related:reprintof} macro is defined, it is used to format the information contained in entry \texttt{key2}, otherwise the \texttt{related:default} macro is used \item If the \texttt{related:reprintof} format is defined, it is used to format both the localization string and data. If this format is not defined, then the \texttt{related} format is used instead. \end{itemize} @@ -3543,10 +3565,12 @@ The following commands are provided by the core of \sty{biblatex}. They are inte \begin{ltxsyntax} \cmditem{citeauthor}[prenote][postnote]{key} +\cmditem*{citeauthor*}[prenote][postnote]{key} \cmditem{Citeauthor}[prenote][postnote]{key} +\cmditem*{Citeauthor*}[prenote][postnote]{key} These commands print the authors. Strictly speaking, it prints the \bibfield{labelname} list, which may be the -\bibfield{author}, the \bibfield{editor}, or the \bibfield{translator}. \cmd{Citeauthor} is similar to \cmd{citeauthor} 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. +\bibfield{author}, the \bibfield{editor}, or the \bibfield{translator}. \cmd{Citeauthor} is similar to \cmd{citeauthor} 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. The starred variants effectively force maxcitenames to 1 for just this command on so only print the first name in the labelname list (potentially followed by the «et al» string if there are more names). This allows more natural textual flow when refering to a paper in the singular when otherwise \cmd{citeauthor} would generate a (naturally plural) list of names. \cmditem{citetitle}[prenote][postnote]{key} \cmditem*{citetitle*}[prenote][postnote]{key} @@ -3884,6 +3908,9 @@ The separator inserted between <units> in the sense explained in \secref{aut:pct \csitem{finentrypunct} The punctuation printed at the very end of every bibliography entry, usually a period. The default definition is a period. +\csitem{entrysetpunct}\BiberOnlyMark +The punctuation printed between bibliography subentries of an entry set. The default definition is a semicolon and a space. + \csitem{bibnamedelima}\BiberOnlyMark This delimiter controls the spacing between the elements which make up a name part. It is inserted automatically after the first name element if the element is less than three characters long and before the last element. The default definition is an interword space penalized by the value of the \cnt{highnamepenalty} counter (\secref{use:fmt:len}). Please refer to \secref{use:cav:nam} for further details. @@ -3951,7 +3978,7 @@ The separator printed after the name used for alphabetizing in the bibliography The separator printed between the fields \bibfield{title} and \bibfield{subtitle}, \bibfield{booktitle} and \bibfield{booksubtitle}, as well as \bibfield{maintitle} and \bibfield{mainsubtitle}. With the default styles, this separator replaces \cmd{newunitpunct} at this location. The default definition is \cmd{newunitpunct}, \ie it is not handled differently from regular unit punctuation. \csitem{intitlepunct} -The separator between the word «in» and the following title in entry types such as \bibtype{article}, \bibtype{inbook}, \bibtype{incollection}, etc. The default definition is a colon plus an interword space (\eg «Article, in: \emph{Journal}» or «Title, in: \emph{Book}»). Note that this is the separator string, not only the punctuation mark. If you don't want a colon after «in», \cmd{intitlepunct} should still insert a space. +The separator between the word «in» and the following title in entry types such as \bibtype{article}, \bibtype{inbook}, \bibtype{incollection}, etc. The default definition is a colon plus an interword space (\eg «Article, in: \emph{Journal}» or «Title, in: \emph{Book}»). Note that this is the separator string, not only the punctuation mark. If you don't want a colon after «in», \cmd{intitlepunct} should still insert a space. \csitem{bibpagespunct} The separator printed before the \bibfield{pages} field. The default is a comma plus an interword space. @@ -4141,15 +4168,15 @@ The horizontal space between entries and their corresponding labels in the bibli \lenitem{bibitemsep} -The vertical space between the individual entries in the bibliography. This length is initialized to \cmd{itemsep} at load-time. Note that \len{bibitemsep}, \len{bibnamesep}, and \len{bibinitsep} are cumulative. When they coincide, the largest value will be applied. +The vertical space between the individual entries in the bibliography. This length is initialized to \cmd{itemsep} at load-time. Note that \len{bibitemsep}, \len{bibnamesep}, and \len{bibinitsep} obey the rules for \cmd{addvspace}, that is, when vertical space introduced by any of these commands immediately follows on from space introduced by another of them, the resulting total space is equal to the largest of them. \lenitem{bibnamesep} -Vertical space to be inserted between two entries in the bibliography whenever an entry starts with a name which is different from the initial name of the previous entry. The default value is zero. Setting this length to a positive value greater than \len{bibitemsep} will group the bibliography by author\slash editor name. Note that \len{bibitemsep}, \len{bibnamesep}, and \len{bibinitsep} are cumulative. When they coincide, the largest value will be applied. +Vertical space to be inserted between two entries in the bibliography whenever an entry starts with a name which is different from the initial name of the previous entry. The default value is zero. Setting this length to a positive value greater than \len{bibitemsep} will group the bibliography by author\slash editor name. Note that \len{bibitemsep}, \len{bibnamesep}, and \len{bibinitsep} obey the rules for \cmd{addvspace}, that is, when vertical space introduced by any of these commands immediately follows on from space introduced by another of them, the resulting total space is equal to the largest of them. \lenitem{bibinitsep} -Vertical space to be inserted between two entries in the bibliography whenever an entry starts with a letter which is different from the initial letter of the previous entry. The default value is zero. Setting this length to a positive value greater than \len{bibitemsep} will group the bibliography alphabetically. Note that \len{bibitemsep}, \len{bibnamesep}, and \len{bibinitsep} are cumulative. When they coincide, the largest value will be applied. +Vertical space to be inserted between two entries in the bibliography whenever an entry starts with a letter which is different from the initial letter of the previous entry. The default value is zero. Setting this length to a positive value greater than \len{bibitemsep} will group the bibliography alphabetically. Note that \len{bibitemsep}, \len{bibnamesep}, and \len{bibinitsep} obey the rules for \cmd{addvspace}, that is, when vertical space introduced by any of these commands immediately follows on from space introduced by another of them, the resulting total space is equal to the largest of them. \lenitem{bibparsep} @@ -4157,7 +4184,7 @@ The vertical space between paragraphs within an entry in the bibliography. The d \cntitem{abbrvpenalty} -This counter, which is used by the localization modules, holds the penalty used in short or abbreviated localization strings. For example, a linebreak in expressions such as «et al.» or «ed. by» is unfortunate, but should still be possible to prevent overfull boxes. This counter is initialized to \cmd{hyphenpenalty} at load-time. The idea is making \tex treat the whole expression as if it were a single, hyphenatable word as far as line"=breaking is concerned. If you dislike such linebreaks, use a higher value. If you do not mind them at all, set this counter to zero. If you want to suppress them unconditionally, set it to <infinite> (10\,000 or higher).\footnote{The default values assigned to \cnt{abbrvpenalty}, \cnt{lownamepenalty}, and \cnt{highnamepenalty} are deliberately very low to prevent overfull boxes. This implies that you will hardly notice any effect on line-breaking if the text is set justified. If you set these counters to 10\,000 to suppress the respective breakpoints, you will notice their effect but you may also be confronted with overfull boxes. Keep in mind that line-breaking in the bibliography is often more difficult than in the body text and that you can not resort to rephrasing a sentence. In some cases it may be preferable to set the entire bibliography \cmd{raggedright} to prevent suboptimal linebreaks. In this case, even the fairly low default penalties will make a visible difference.} +This counter, which is used by the localization modules, holds the penalty used in short or abbreviated localization strings. For example, a linebreak in expressions such as «et al.» or «ed. by» is unfortunate, but should still be possible to prevent overfull boxes. This counter is initialized to \cmd{hyphenpenalty} at load-time. The idea is making \tex treat the whole expression as if it were a single, hyphenatable word as far as line"=breaking is concerned. If you dislike such linebreaks, use a higher value. If you do not mind them at all, set this counter to zero. If you want to suppress them unconditionally, set it to <infinite> (10\,000 or higher).\footnote{The default values assigned to \cnt{abbrvpenalty}, \cnt{lownamepenalty}, and \cnt{highnamepenalty} are deliberately very low to prevent overfull boxes. This implies that you will hardly notice any effect on line-breaking if the text is set justified. If you set these counters to 10\,000 to suppress the respective breakpoints, you will notice their effect but you may also be confronted with overfull boxes. Keep in mind that line-breaking in the bibliography is often more difficult than in the body text and that you can not resort to rephrasing a sentence. In some cases it may be preferable to set the entire bibliography \cmd{raggedright} to prevent suboptimal linebreaks. In this case, even the fairly low default penalties will make a visible difference.} \cntitem{highnamepenalty} @@ -4226,13 +4253,13 @@ will yield <Special issue> or <special issue>, as appropriate. If the string to \autocap{\'e}dition sp\'eciale \end{lstlisting} % -This will yield <Édition spéciale> or <édition spéciale>. If the string to be capitalized starts with a command which prints a character, such as \cmd{ae} or \cmd{oe}, simply put the command in the \prm{character} argument: +This will yield <Édition spéciale> or <édition spéciale>. If the string to be capitalized starts with a command which prints a character, such as \cmd{ae} or \cmd{oe}, simply put the command in the \prm{character} argument: \begin{lstlisting}[style=latex]{} \autocap{\oe}uvres \end{lstlisting} % -This will yield <¼uvres> or <½uvres>. +This will yield <Å’uvres> or <Å“uvres>. \end{ltxsyntax} @@ -4339,7 +4366,7 @@ With traditional \bibtex, the \cmd{bibliography} command serves two purposes. It Whenever a reference to a work which has not been cited before is added, this procedure must be repeated. This is also the case if the last reference to a work which has been cited before is removed because some citation labels may change in this case. In contrast to traditional \bibtex, there is normally no need to run \bin{latex} twice after running the backend as far as the handling of bibliographic data is concerned.\footnote{That is, unless the \opt{defernumbers} package option is enabled. See \secref{aut:int}} -\BibTeXOnlyMark Note that when using \bibtex as the backend this only applies to the most basic case. Using the \bibfield{xref} field or the \bibfield{entryset} field may require an additional \latex/\bibtex/\latex cycle. Some other facilities provided by \sty{biblatex} may also require an additional \bin{latex} run to get certain references and the page tracking right. In this case, the usual warning messages such as «There were undefined references» and «Label(s) may have changed. Rerun to get cross-references right» will be printed. +\BibTeXOnlyMark Note that when using \bibtex as the backend this only applies to the most basic case. Using the \bibfield{xref} field or the \bibfield{entryset} field may require an additional \latex/\bibtex/\latex cycle. Some other facilities provided by \sty{biblatex} may also require an additional \bin{latex} run to get certain references and the page tracking right. In this case, the usual warning messages such as «There were undefined references» and «Label(s) may have changed. Rerun to get cross-references right» will be printed. \subsubsection{Auxiliary Files} \label{use:use:aux} @@ -4420,7 +4447,7 @@ If \cmd{printbibliography} is used inside a \env{refsection} environment, it aut \end{document} \end{ltxexample} % -Note the definition of the bibliography heading in the above example. This is the definition taking care of the subheadings in the bibliography. The main heading is generated with a plain \cmd{chapter} command in this case. The \sty{biblatex} package automatically sets a label at the beginning of every \env{refsection} environment, using the standard \cmd{label} command. The identifier used is the string \texttt{refsection:} followed by the number of the respective \env{refsection} environment. The number of the current section is accessible via the \cnt{refsection} counter. When using the \opt{section} option of \cmd{printbibliography}, this counter is also set locally. This means that you may use the counter in heading definitions to print subheadings like «References for Chapter 3», as shown above. You could also use the title of the respective chapter as a subheading by loading the \sty{nameref} package and using \cmd{nameref} instead of \cmd{ref}: +Note the definition of the bibliography heading in the above example. This is the definition taking care of the subheadings in the bibliography. The main heading is generated with a plain \cmd{chapter} command in this case. The \sty{biblatex} package automatically sets a label at the beginning of every \env{refsection} environment, using the standard \cmd{label} command. The identifier used is the string \texttt{refsection:} followed by the number of the respective \env{refsection} environment. The number of the current section is accessible via the \cnt{refsection} counter. When using the \opt{section} option of \cmd{printbibliography}, this counter is also set locally. This means that you may use the counter in heading definitions to print subheadings like «References for Chapter 3», as shown above. You could also use the title of the respective chapter as a subheading by loading the \sty{nameref} package and using \cmd{nameref} instead of \cmd{ref}: \begin{lstlisting}[style=latex] \usepackage{<<nameref>>} @@ -4583,7 +4610,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 \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 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} @@ -4679,7 +4706,7 @@ See also \secref{bib:typ:blx,bib:fld:spc}. \subsubsection{Electronic Publishing Information} \label{use:use:epr} -The \sty{biblatex} package provides three fields for electronic publishing information: \bibfield{eprint}, \bibfield{eprinttype}, and \bibfield{eprintclass}. The \bibfield{eprint} field is a verbatim field similar to \bibfield{doi} which holds the identifier of the item. The \bibfield{eprinttype} field holds the resource name, \ie the name of the site or electronic archive. The optional \bibfield{eprintclass} field is intended for additional information specific to the resource indicated by the \bibfield{eprinttype} field. This could be a section, a path, classification information, etc. If the \bibfield{eprinttype} field is available, the standard styles will use it as a literal label. In the following example, they would print «Resource: identifier» rather than the generic «eprint: identifier»: +The \sty{biblatex} package provides three fields for electronic publishing information: \bibfield{eprint}, \bibfield{eprinttype}, and \bibfield{eprintclass}. The \bibfield{eprint} field is a verbatim field similar to \bibfield{doi} which holds the identifier of the item. The \bibfield{eprinttype} field holds the resource name, \ie the name of the site or electronic archive. The optional \bibfield{eprintclass} field is intended for additional information specific to the resource indicated by the \bibfield{eprinttype} field. This could be a section, a path, classification information, etc. If the \bibfield{eprinttype} field is available, the standard styles will use it as a literal label. In the following example, they would print «Resource: identifier» rather than the generic «eprint: identifier»: \begin{lstlisting}[style=bibtex]{} <<eprint>> = {<<identifier>>}, @@ -4716,7 +4743,7 @@ When using \acr{JSTOR}'s export feature to export citations in \bibtex format, \ url = {http://www.jstor.org/stable/<<number>>}, \end{lstlisting} % -While this will work as expected, full \acr{URL}s tend to clutter the bibliography. With the \bibfield{eprint} fields, the standard styles will use the more readable «\acr{JSTOR}: \prm{number}» format which also supports hyperlinks. The \prm{number} becomes a clickable link if \sty{hyperref} support is enabled. +While this will work as expected, full \acr{URL}s tend to clutter the bibliography. With the \bibfield{eprint} fields, the standard styles will use the more readable «\acr{JSTOR}: \prm{number}» format which also supports hyperlinks. The \prm{number} becomes a clickable link if \sty{hyperref} support is enabled. For PubMed references, put the stable PubMed identifier in the \bibfield{eprint} field and the string \texttt{pubmed} in the \bibfield{eprinttype} field. This means that: @@ -4731,7 +4758,7 @@ becomes: <<eprinttype>> = {<<pubmed>>}, \end{lstlisting} % -and the standard styles will print «\acr{PMID}: \prm{pmid}» instead of the lengthy \acr{URL}. If hyperref support is enabled, the \prm{pmid} will be a clickable link to PubMed. +and the standard styles will print «\acr{PMID}: \prm{pmid}» instead of the lengthy \acr{URL}. If hyperref support is enabled, the \prm{pmid} will be a clickable link to PubMed. For handles (\acr{HDL}s), put the handle in the \bibfield{eprint} field and the string \texttt{hdl} in the \bibfield{eprinttype} field: @@ -4753,7 +4780,7 @@ would become: <<eprinttype>> = {<<googlebooks>>}, \end{lstlisting} % -and the standard styles would print «Google Books: |XXu4AkRVBBoC|» instead of the full \acr{URL}. If hyperref support is enabled, the identifier will be a clickable link to Google Books.\footnote{Note that the Google Books \acr{id} seems to be a bit of an <internal> value. As of this writing, there does not seem to be any way to search for an \acr{id} on Google Books. You may prefer to use the \bibfield{url} in this case.} +and the standard styles would print «Google Books: |XXu4AkRVBBoC|» instead of the full \acr{URL}. If hyperref support is enabled, the identifier will be a clickable link to Google Books.\footnote{Note that the Google Books \acr{id} seems to be a bit of an <internal> value. As of this writing, there does not seem to be any way to search for an \acr{id} on Google Books. You may prefer to use the \bibfield{url} in this case.} Note that \bibfield{eprint} is a verbatim field. Always give the identifier in its unmodified form. For example, there is no need to replace |_| with |\_|. Also see \secref{aut:cav:epr} on how to add dedicated support for other eprint resources. @@ -4915,21 +4942,21 @@ Initials in the \file{bib} file get a special delimiter: \item J.\delim{~}{i}Edward\delim{ }{d}Doe \end{namesample} % -Let's consider a more complex name: \enquote{Charles-Jean Étienne Gustave Nicolas de La Vallée Poussin}. This name is composed of the following parts: +Let's consider a more complex name: \enquote{Charles-Jean Étienne Gustave Nicolas de La Vallée Poussin}. This name is composed of the following parts: \begin{nameparts} -First & Charles-Jean Étienne Gustave Nicolas \\ +First & Charles-Jean Étienne Gustave Nicolas \\ Prefix & de \\ -Last & La Vallée Poussin \\ +Last & La Vallée Poussin \\ Suffix & --- \\ \end{nameparts} % The delimiters: \begin{namesample} -\item Charles-Jean\delim{~}{b}Étienne\delim{~}{b}Gustave\delim{~}{a}Nicolas\delim{ }{d}% +\item Charles-Jean\delim{~}{b}Étienne\delim{~}{b}Gustave\delim{~}{a}Nicolas\delim{ }{d}% de\delim{ }{c}% - La\delim{~}{a}Vallée\delim{~}{a}Poussin + La\delim{~}{a}Vallée\delim{~}{a}Poussin \end{namesample} % Note that \cmd{bibnamedelima/b/i} are inserted by the backend. The backend processes the name parts and takes care of the delimiters between the elements that make up a name part, processing each part individually. In contrast to that, the delimiters between the parts of the complete name (\cmd{bibnamedelimc/d}) are added by name formatting directives at a later point in the processing chain. The spacing and punctuation of initials is also handled by the backend and may be customized by redefining the following three macros: @@ -5285,7 +5312,7 @@ Formatting directives for names are similar to those for literal lists, but the {}} \end{lstlisting} % -The above directive reverses the name of the first author («Last, First») and prints the remaining names in their regular sequence («First Last»). Note that the only component which is guaranteed to be available is the last name, hence we have to check which parts of the name are actually present. If a certain component of a name is not available, the corresponding argument will be blank. As with directives for literal lists, the separator to be inserted between the individual items in the list is also handled by the formatting directive, hence we have to check whether we are in the middle of the list or at the end when inserting it. This is what the second \cmd{ifthenelse} test does. +The above directive reverses the name of the first author («Last, First») and prints the remaining names in their regular sequence («First Last»). Note that the only component which is guaranteed to be available is the last name, hence we have to check which parts of the name are actually present. If a certain component of a name is not available, the corresponding argument will be blank. As with directives for literal lists, the separator to be inserted between the individual items in the list is also handled by the formatting directive, hence we have to check whether we are in the middle of the list or at the end when inserting it. This is what the second \cmd{ifthenelse} test does. \subsubsection{Special Fields} \label{aut:bbx:fld} @@ -5337,6 +5364,11 @@ If the \opt{backref} package option is enabled, this list holds the page numbers This field holds the initial letter of the string used during sorting. This is useful when subdividing the bibliography alphabetically. +\fielditem{clonesourcekey}{string\BiberOnlyMark} + +This field holds the entry key of the entry from which an entry was cloned. Clones are created for +entries which are mentioned in \bibfield{related} fields as part of related entry processing, for example. + \end{fieldlist} \paragraph{Fields for Use in Citation Labels} @@ -5379,12 +5411,22 @@ It is sometimes useful, for example in author"=title citation schemes, to be abl \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{labelyear}, see \secref{use:opt:pre:int} for details. See also \bibfield{extrayear}. -\BiberOnlyMark With \biber, this field may be customized. See \secref{aut:ctm:fld} for details. +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} + +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} + +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{labelyear}, 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:tab2} summarises the various \opt{extra*} disambiguation counters and what they track. \end{fieldlist} @@ -5700,6 +5742,14 @@ This command prints the date of the entry, as specified in the fields \bibfield{ Similar to \cmd{printdate} but incorporates the \bibfield{extrayear} field in the date specification. This is useful for bibliography styles designed for author-year citations. +\csitem{printdatelabel}|\BiberOnlyMark| + +Similar to \cmd{printdate} but prints the date field determined by \cmd{DeclareLabeldate}. The date format is controlled by the package option \opt{datelabel} from \secref{use:opt:pre:gen}. Additional formatting may be applied by adjusting the field format \texttt{urldate} (\secref{aut:fmt:ich}). + +\csitem{printdateextralabel}|\BiberOnlyMark| + +Similar to \cmd{printdatelabel} but incorporates the \bibfield{extrayear} field in the date specification. This is useful for bibliography styles designed for author-year citations. + \csitem{printurldate} Similar to \cmd{printdate} but prints the \bibfield{urldate} of the entry. The date format is controlled by the package option \opt{urldate} from \secref{use:opt:pre:gen}. Additional formatting may be applied by adjusting the field format \texttt{urldate} (\secref{aut:fmt:ich}). @@ -5784,7 +5834,7 @@ Defines the name list format \prm{format}. This formatting directive is arbitrar \item[\#4] The first names, given as initials. \item[\#5] The name prefixes, for example von, van, of, da, de, del, della, etc. Note that name prefixes are referred to as the <von part> of the name in the \bibtex file format documentation. \item[\#6] The name prefixes, given as initials. -\item[\#7] The name affixes, for example <junior>, <senior>, <der Jüngere>, <der Ältere>, etc. +\item[\#7] The name affixes, for example <junior>, <senior>, <der Jüngere>, <der Ältere>, etc. Note that name affixes are referred to as the <junior part> of the name in the \bibtex file format documentation. \item[\#8] The name affixes, given as initials. \end{argumentlist} @@ -5860,7 +5910,7 @@ The related entry feature is enabled by default by the package option \opt{relat Bibliographic data sources which are automatically generated or which you have no control over can be a problem if you need to edit them in some way. For this reason, \biber has the ability to modify data as it is read so that you can apply modifications to the source data stream without actually changing it. The modification can be defined in \biber's config file (see \biber docs), or via \sty{biblatex} macros in which case you can apply the modification only for specific documents, styles or globally. -Source mappings can be defined at different «levels» which are applied +Source mappings can be defined at different «levels» which are applied in a defined order. See the \biblatex\ manual regarding these macros:\\[2ex] \noindent \texttt{user}-level maps defined with \cmd{DeclareSourcemap}$\rightarrow$\\ @@ -6413,7 +6463,7 @@ For constraints of \prm{type} <conditional>, specifies a quantified set of \cmd{ \choitem{quantifier}{all, one, none} -Specifies how many of the \cmd{constrainfield}'s inside the \cmd{consequent} have to be present to satisfy the consequent of the conditional constraint. +Specifies how many of the \cmd{constraintfield}'s inside the \cmd{consequent} have to be present to satisfy the consequent of the conditional constraint. \end{optionlist*} @@ -6537,6 +6587,14 @@ The number of characters of the \prm{field} to use. For name list fields, if \kv The side of the string from which to take the \texttt{strwidth} number of characters. +\choitem[right]{padside}{left, right} + +Side to pad the label part when using the \texttt{padchar} option. Only for use with fixed-width label strings (\texttt{strwidth}). + +\valitem{padchar}{character} + +If present, pads the label part on the \texttt{padside} side with the specified character to the length of \texttt{strwidth}. Only for use with fixed-width label strings (\texttt{strwidth}). + \boolitem[false]{uppercase} Forces the label part derived from the field to uppercase. By default, the case is taken from the field source and not modified. @@ -6753,6 +6811,41 @@ Agassi, Courier, Laver [ACouL-002] Borg, Connors, Edberg [BCEd-003] Borg, Connors, Emerson [BCEm-004] \end{lstlisting} +% +Here is another rather contrived example showing that you don't need to specially quote \latex special characters (apart from <\%>, obviously) when specifying padding characters and literals: + +\begin{lstlisting}[style=latex]{} +\DeclareLabelalphaTemplate{ + \labelelement{ + \literal{>} + } + \labelelement{ + \literal{\%} + } + \labelelement{ + \field[strwidth=4, padchar=_]{<<labelname>>} + } + \labelelement{ + \field[strwidth=3, padchar=&, padside=left]{title} + } + \labelelement{ + \field[strwidth=2,strside=right]{<<year>>} + } +} +\end{lstlisting} +% +which given: +\begin{lstlisting}[style=bibtex]{} +@Book{test, + author = {XXX YY}, + title = {T}, + year = {2007}, +} +\end{lstlisting} +would resulting a label looking like this: +\begin{verbatim} +[>%YY__&&T07] +\end{verbatim} \subsubsection{Sorting} \label{aut:ctm:srt} @@ -6843,7 +6936,7 @@ The \cmd{citeorder} element has a special meaning. It requests a sort based on t \cite{one,two} \end{lstlisting} % -there is a distinction between the lexical order and the semantic order. Here «one» and «two» have the same semantic order but a unique lexical order. The semantic order only matters if you specify further sorting to disambiguate entries with the same semantic order. For example, this is the definition of the \opt{none} sorting scheme: +there is a distinction between the lexical order and the semantic order. Here «one» and «two» have the same semantic order but a unique lexical order. The semantic order only matters if you specify further sorting to disambiguate entries with the same semantic order. For example, this is the definition of the \opt{none} sorting scheme: \begin{lstlisting}[style=latex]{} \DeclareSortingScheme{none}{ @@ -6851,7 +6944,7 @@ there is a distinction between the lexical order and the semantic order. Here «o } \end{lstlisting} % -This sorts the bibliography purely lexically by the order of the keys in the citation commands. In the example above, it sorts «one» before «two». However, suppose that you consider «one» and «two» to have the same order (semantic order) since they are cited at the same time and want to further sort these by year. Suppose «two» has an earlier \bibfield{year} than «one»: +This sorts the bibliography purely lexically by the order of the keys in the citation commands. In the example above, it sorts «one» before «two». However, suppose that you consider «one» and «two» to have the same order (semantic order) since they are cited at the same time and want to further sort these by year. Suppose «two» has an earlier \bibfield{year} than «one»: \begin{lstlisting}[style=latex]{} \DeclareSortingScheme{noneyear}{ @@ -6860,7 +6953,7 @@ This sorts the bibliography purely lexically by the order of the keys in the cit } \end{lstlisting} % -This sorts «two» before «one», even though lexically, «one» would sort before «two». This is possible because the semantic order can be disambiguated by the further sorting on year. With the standard \opt{none} sorting scheme, the lexical order and semantic order are identical because there is nothing further to disambiguate them. This means that you can use \cmd{citeorder} just like any other sorting specification element, choosing how to further sort entries cited at the same time (in the same citation command). +This sorts «two» before «one», even though lexically, «one» would sort before «two». This is possible because the semantic order can be disambiguated by the further sorting on year. With the standard \opt{none} sorting scheme, the lexical order and semantic order are identical because there is nothing further to disambiguate them. This means that you can use \cmd{citeorder} just like any other sorting specification element, choosing how to further sort entries cited at the same time (in the same citation command). \end{ltxsyntax} @@ -6938,7 +7031,7 @@ Specifies a string to be used to automatically populate the \bibfield{presort} f \subsubsection{Controlling Name Initials Generation} \label{aut:ctm:noinit} -Generating initials for name parts from a given name involves some difficulties when you have names with prefixes, diacritics, hyphens etc. Often, you want to ignore things like prefixes when generating initials so that the initials for «al-Hasan» is just «H» instead of «a-H». This is tricky when you also have names like «Ho-Pun» where you want the initials to be «H-P», for example. +Generating initials for name parts from a given name involves some difficulties when you have names with prefixes, diacritics, hyphens etc. Often, you want to ignore things like prefixes when generating initials so that the initials for «al-Hasan» is just «H» instead of «a-H». This is tricky when you also have names like «Ho-Pun» where you want the initials to be «H-P», for example. \begin{ltxsyntax} @@ -6993,7 +7086,7 @@ If there is no \cmd{DeclareNosort} specification, \biber will default to: } \end{lstlisting} % -This \biber default strips diacritics and prefixes from names when sorting. Suppose you wanted to ignore «The» at the beginning of a \bibfield{title} field when sorting: +This \biber default strips diacritics and prefixes from names when sorting. Suppose you wanted to ignore «The» at the beginning of a \bibfield{title} field when sorting: \begin{lstlisting}[style=latex]{} \DeclareNosort{ @@ -7001,7 +7094,7 @@ This \biber default strips diacritics and prefixes from names when sorting. Supp } \end{lstlisting} % -Or if you wanted to ignore «The» at the beginning of any title field: +Or if you wanted to ignore «The» at the beginning of any title field: \begin{lstlisting}[style=latex]{} \DeclareNosort{ @@ -7093,20 +7186,22 @@ For example, the following specification for selecting \bibfield{labelname} firs % See \secref{use:opt:bib:ded} for options to override this on a per-entry basis. -\cmditem{DeclareLabelyear}[entrytype, \dots]{specification}|\BiberOnlyMark| +\cmditem{DeclareLabeldate}[entrytype, \dots]{specification}|\BiberOnlyMark| -Defines the date components to consider when generating the \bibfield{labelyear} field (see \secref{aut:bbx:fld:lab}). The \prm{specification} is an ordered list of \cmd{field} commands. The items are checked in the order listed and the first item which is available will be used as \bibfield{labelyear}. Note that the items are date components, not date fields. 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 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: \begin{lstlisting}[style=latex]{} -\DeclareLabelyear{% - \field{year} - \field{eventyear} - \field{origyear} - \field{urlyear} +\DeclareLabeldate{% + \field{date} + \field{eventdate} + \field{origdate} + \field{urldate} + \literal{nodate} } \end{lstlisting} % -The \bibfield{labelyear} 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. See also \secref{aut:bbx:fld:dat}. +Note that the \bibfield{date} field is split by the backend into \bibfield{year}, \bibfield{month} which are also valid fields in the default data model. In order to support legacy data which directly sets \bibfield{year} and/or \bibfield{month}, the specification <\bibfield{date}> in \cmd{DeclareLabeldate} will also match \bibfield{year} and \bibfield{month} fields, if present. +The \bibfield{labelyear}, \bibfield{labelmonth} and \bibfield{labelday} fields may be customized globally or on a per-type basis. If the optional \prm{entrytype} argument is given, the specification applies to the respective entry type. If not, it is applied globally. The \prm{entrytype} argument may be a comma"=separated list of values. This command may only be used in the preamble. See also \secref{aut:bbx:fld:dat}. \cmditem{DeclareLabeltitle}[entrytype, \dots]{specification}|\BiberOnlyMark| @@ -7447,7 +7542,7 @@ Expands to \prm{true} if the \prm{list} is defined and has been truncated in the \cmditem{ifmorenames}{true}{false} -Expands to \prm{true} if the current name list has been or will be truncated, and to \prm{false} otherwise. This command is intended for use in formatting directives for name lists. It will always expand to \prm{false} when used elsewhere. This command performs the equivalent of an \cmd{ifandothers} test for the current list. If this test is negative, it also checks if the \cnt{listtotal} counter is larger than \cnt{liststop}. This command may be used in a formatting directive to decide if a note such as «and others» or «et al.» is to be printed at the end of the list. Note that you still need to check whether you are in the middle or at the end of the list, \ie whether \cnt{listcount} is smaller than or equal to \cnt{liststop}, see \secref{aut:bib:dat} for details. +Expands to \prm{true} if the current name list has been or will be truncated, and to \prm{false} otherwise. This command is intended for use in formatting directives for name lists. It will always expand to \prm{false} when used elsewhere. This command performs the equivalent of an \cmd{ifandothers} test for the current list. If this test is negative, it also checks if the \cnt{listtotal} counter is larger than \cnt{liststop}. This command may be used in a formatting directive to decide if a note such as «and others» or «et al.» is to be printed at the end of the list. Note that you still need to check whether you are in the middle or at the end of the list, \ie whether \cnt{listcount} is smaller than or equal to \cnt{liststop}, see \secref{aut:bib:dat} for details. \cmditem{ifmoreitems}{true}{false} @@ -7535,7 +7630,7 @@ Executes \prm{true} if the \prm{string} is an Arabic or Roman numeral, and \prm{ \cmditem{ifnumerals}{string}{true}{false} -Executes \prm{true} if the \prm{string} is a range or a list of Arabic or Roman numerals, and \prm{false} otherwise. This command is robust. In contrast to \cmd{ifnumeral}, it will also execute \prm{true} with arguments like «52--58», «14/15», «1,~3,~5», and so on. See also \cmd{DeclareNumChars}, \cmd{DeclareRangeChars}, \cmd{DeclareRangeCommands}, and \cmd{NumCheckSetup} in \secref{aut:aux:msc}. +Executes \prm{true} if the \prm{string} is a range or a list of Arabic or Roman numerals, and \prm{false} otherwise. This command is robust. In contrast to \cmd{ifnumeral}, it will also execute \prm{true} with arguments like «52--58», «14/15», «1,~3,~5», and so on. See also \cmd{DeclareNumChars}, \cmd{DeclareRangeChars}, \cmd{DeclareRangeCommands}, and \cmd{NumCheckSetup} in \secref{aut:aux:msc}. \cmditem{ifpages}{string}{true}{false} @@ -7794,7 +7889,7 @@ The optional argument \bibfield{pagination} in the first example is omissible. \cmditem{mkpagetotal}[pagination][postpro]{text} -This command is similar to \cmd{mkpageprefix} except that it is intended for the \bibfield{pagetotal} field of bibliography entries, \ie it will print «123 pages» rather than «page 123». The optional \prm{pagination} argument defaults to \bibfield{bookpagination}. The spacing inserted between the pagination suffix and the \prm{text} may be modified by redefining the macro \cmd{ppspace}. The optional \prm{postpro} argument specifies a macro to be used for post-processing the \prm{text}. If only one optional argument is given, it is taken as \prm{pagination}. Here is a typical example: +This command is similar to \cmd{mkpageprefix} except that it is intended for the \bibfield{pagetotal} field of bibliography entries, \ie it will print «123 pages» rather than «page 123». The optional \prm{pagination} argument defaults to \bibfield{bookpagination}. The spacing inserted between the pagination suffix and the \prm{text} may be modified by redefining the macro \cmd{ppspace}. The optional \prm{postpro} argument specifies a macro to be used for post-processing the \prm{text}. If only one optional argument is given, it is taken as \prm{pagination}. Here is a typical example: \begin{lstlisting}[style=latex]{} \DeclareFieldFormat{pagetotal}{<<\mkpagetotal[bookpagination]{#1}>>} @@ -7841,7 +7936,7 @@ The optional argument \bibfield{bookpagination} is omissible in this case. \cmditem{mkcomprange}[postpro]{text} \cmditem*{mkcomprange*}[postpro]{text} -This command, which is intended for use in field formatting directives, will parse its \prm{text} argument for page ranges and compress them. For example, «125--129» may be formatted as «125--9». You may configure the behavior of \cmd{mkcomprange} by adjusting the \latex counters \cnt{mincomprange}, \cnt{maxcomprange}, and \cnt{mincompwidth}, as illustrated in \tabref{aut:aux:tab1}. The default settings are \texttt{10}, \texttt{100000}, and \texttt{1}, respectively. This means that the command tries to compress as much as possible by default. Use \cmd{setcounter} to adjust the parameters. The scanner recognizes \cmd{bibrangedash} and hyphens as range dashes. It will normalize the dash by replacing any number of consecutive hyphens with \cmd{bibrangedash}. Lists of ranges delimited with \cmd{bibrangessep} (\biber\footnote{\biber will always convert commas/semicolon multi-range separators into \cmd{bibrangessep} so that it can be controlled in the style.}) or commas/semicolons (BibTeX) are also supported. If you want to hide a character from the list/range scanner for some reason, wrap the character or the entire string in curly braces. The optional \prm{postpro} argument specifies a macro to be used for post-processing the \prm{text}. This is important if you want to combine \cmd{mkcomprange} with other formatting macros which also need to parse their \prm{text} argument, such as \cmd{mkpageprefix}. Simply nesting these commands will not work as expected. Use the \prm{postpro} argument to set up the processing chain as follows: +This command, which is intended for use in field formatting directives, will parse its \prm{text} argument for page ranges and compress them. For example, «125--129» may be formatted as «125--9». You may configure the behavior of \cmd{mkcomprange} by adjusting the \latex counters \cnt{mincomprange}, \cnt{maxcomprange}, and \cnt{mincompwidth}, as illustrated in \tabref{aut:aux:tab1}. The default settings are \texttt{10}, \texttt{100000}, and \texttt{1}, respectively. This means that the command tries to compress as much as possible by default. Use \cmd{setcounter} to adjust the parameters. The scanner recognizes \cmd{bibrangedash} and hyphens as range dashes. It will normalize the dash by replacing any number of consecutive hyphens with \cmd{bibrangedash}. Lists of ranges delimited with \cmd{bibrangessep} (\biber\footnote{\biber will always convert commas/semicolon multi-range separators into \cmd{bibrangessep} so that it can be controlled in the style.}) or commas/semicolons (BibTeX) are also supported. If you want to hide a character from the list/range scanner for some reason, wrap the character or the entire string in curly braces. The optional \prm{postpro} argument specifies a macro to be used for post-processing the \prm{text}. This is important if you want to combine \cmd{mkcomprange} with other formatting macros which also need to parse their \prm{text} argument, such as \cmd{mkpageprefix}. Simply nesting these commands will not work as expected. Use the \prm{postpro} argument to set up the processing chain as follows: \begin{lstlisting}[style=latex]{} \DeclareFieldFormat{postnote}{\mkcomprange[<<{>>\mkpageprefix[pagination]<<}>>]{#1}} @@ -7878,6 +7973,22 @@ pp. 5, 123, 423 p. 5, p. 123, p. 423 \end{lstlisting} +\cmditem{rangelen}{text} + +This command will parse its argument as a range and return the length of the range. It will return 0 for open-ended ranges. + +\begin{lstlisting}[style=latex]{} +\rangelen{5-10} returns '5' +\rangelen{-10} returns '0' +\rangelen{5-} returns '0' +\rangelen{5} returns '1' +\end{lstlisting} +% +This can be used as part of tests in styles which require, for example, <f> as a suffix for ranges of only two pages, for example, when a page range <36-37> should be printed as <36f>. This could be done using \cmd{ifnumcomp}: + +\begin{lstlisting}[style=latex]{} +\ifnumcomp{\rangelen{\thefield{pages}}}{=}{1}{add 'f'}{do nothing} +\end{lstlisting} \cmditem{DeclareNumChars}{characters} \cmditem*{DeclareNumChars*}{characters} @@ -7989,6 +8100,11 @@ Inserts \cmd{finentrypunct}. This command should be used at the very end of ever The \cmd{setunit} command is similar to \cmd{newunit} except that it uses \prm{punctuation} instead of \cmd{newunitpunct}. The starred variant differs from the regular version in that it checks if the last \cmd{printtext}, \cmd{printfield}, \cmd{printlist}, \cmd{printnames}, or \cmd{bibstring} command did actually print anything. If not, it does nothing. +\cmditem{printunit}{punctuation} +\cmditem*{printunit*}{punctuation} + +The \cmd{printunit} command is similar to \cmd{setunit} except that \prm{punctuation} persists in the buffer until the next \cmd{printtext}, \cmd{printfield}, \cmd{printlist}, \cmd{printnames}, or \cmd{bibstring} command. + \cmditem{setpunctfont}{command} This command, which is intended for use in field formatting directives, provides an alternative way of dealing with unit punctuation after a field printed in a different font (for example, a title printed in italics). The standard \latex way of dealing with this is adding a small amount of space, the so-called italic correction. This command allows adapting the punctuation to the font of the preceding field. The \prm{command} should be a text font command which takes one argument, such as \cmd{emph} or \cmd{textbf}. This command will only affect punctuation marks inserted by one of the commands from \secref{aut:pct:pct}. The font adaption is applied to the next punctuation mark only and will be reset automatically thereafter. If you want to reset it manually before it takes effect, issue \cmd{resetpunctfont}. If the \opt{punctfont} package option is disabled, this command does nothing. Note that the \cmd{mkbibemph} and \cmd{mkbibbold} wrappers from \secref{aut:fmt:ich} incorporate this feature by default. @@ -8199,7 +8315,7 @@ Undoes the settings applied by \cmd{uspunctuation}, restoring standard punctuati \subsubsection{Correcting Punctuation Tracking} \label{aut:pct:ctr} -The facilities for punctuation tracking and automatic capitalization are very reliable under normal circumstances, but there are always marginal cases which may require manual intervention. Typical cases are localization strings printed as the first word in a footnote (which is usually treated as the beginning of a paragraph as far as capitalization is concerned, but \tex is not in vertical mode at this point) or punctuation after periods which are not really end"=of"=sentence periods (for example, after an ellipsis like «[\dots\unkern]» a command such as \cmd{addperiod} would do nothing since parentheses and brackets are transparent to the punctuation tracker). In such cases, use the following commands in bibliography and citation styles to mark the beginning or middle of a sentence if and where required: +The facilities for punctuation tracking and automatic capitalization are very reliable under normal circumstances, but there are always marginal cases which may require manual intervention. Typical cases are localization strings printed as the first word in a footnote (which is usually treated as the beginning of a paragraph as far as capitalization is concerned, but \tex is not in vertical mode at this point) or punctuation after periods which are not really end"=of"=sentence periods (for example, after an ellipsis like «[\dots\unkern]» a command such as \cmd{addperiod} would do nothing since parentheses and brackets are transparent to the punctuation tracker). In such cases, use the following commands in bibliography and citation styles to mark the beginning or middle of a sentence if and where required: \begin{ltxsyntax} @@ -8286,6 +8402,10 @@ Similar to \cmd{bibxstring} but always uses the long string, ignoring the \opt{a Similar to \cmd{bibxstring} but always uses the short string, ignoring the \opt{abbreviate} option. +\cmditem{mainlang} + +Switches from the current language to the main document language. This can be used the \prm{wrapper} argument in the localization string commands above. + \end{ltxsyntax} \subsection{Localization Modules} @@ -8557,7 +8677,7 @@ The following keys refer to roles which are expressed as an action (<edited by>, \item[byreviser] The expression <revised by \prm{name}>. \item[byreviewer] The expression <reviewed by \prm{name}>. \item[bycollaborator] An expression like <in collaboration with \prm{name}> or <in cooperation with \prm{name}>. -\item[bytranslator] The expression <translated by \prm{name}> or <translated from \prm{language} by \prm{name}>. +\item[bytranslator] The expression <translated by \prm{name}> or <translated from \prm{language} by \prm{name}>. \item[bycommentator] The expression <commented by \prm{name}>. \item[byannotator] The expression <annotated by \prm{name}>. \end{keymarglist} @@ -8755,6 +8875,7 @@ The following keys are typically used in the \bibfield{type} field of \bibtype{t \label{aut:lng:key:msc} \begin{keymarglist} +\item[nodate] The term to use in place of a date when there is no date for an entry \eg\ <n.d.> \item[and] The term <and>, as used in a list of authors or editors, for example. \item[andothers] The expression <and others> or <et alii>, used to mark the truncation of a name list. \item[andmore] Like \texttt{andothers} but used to mark the truncation of a literal list. @@ -8767,6 +8888,7 @@ The following strings are intended for use as labels, \eg\ <Address: \prm{url}> \begin{keymarglist} \item[url] The term <address> in the sense of an internet address. +\item[urlfrom] An expression like <available from \prm{url}> or <available at \prm{url}>. \item[urlseen] An expression like <accessed on \prm{date}>, <retrieved on \prm{date}>, <visited on \prm{date}>, referring to the access date of an online resource. \item[file] The term <file>. \item[library] The term <library>. @@ -8989,7 +9111,7 @@ The separator to be printed after the name used for alphabetizing in the bibliog The separator to be printed between the fields \bibfield{title} and \bibfield{subtitle}, \bibfield{booktitle} and \bibfield{booksubtitle}, as well as \bibfield{maintitle} and \bibfield{mainsubtitle}. Use this separator instead of \cmd{newunitpunct} at this location. The default is \cmd{newunitpunct}, \ie it is not handled differently from regular unit punctuation but permits convenient reconfiguration. \csitem{intitlepunct} -The separator to be printed between the word «in» and the following title in entry types such as \bibtype{article}, \bibtype{inbook}, \bibtype{incollection}, etc. Use this separator instead of \cmd{newunitpunct} at this location. The default definition is a colon plus an interword space. +The separator to be printed between the word «in» and the following title in entry types such as \bibtype{article}, \bibtype{inbook}, \bibtype{incollection}, etc. Use this separator instead of \cmd{newunitpunct} at this location. The default definition is a colon plus an interword space. \csitem{bibpagespunct} The separator to be printed before the \bibfield{pages} field. Use this separator instead of \cmd{newunitpunct} at this location. The default is a comma plus an interword space. @@ -9287,6 +9409,10 @@ A special formatting directive which controls the format of the volume portion i A special formatting directive which controls the format of \cmd{printdate} (\secref{aut:bib:dat}). Note that the date format (long/short etc.) is controlled by the package option \opt{date} from \secref{use:opt:pre:gen}. This formatting directive only controls additional formatting such as fonts etc. +\optitem{datelabel} + +Similar to \texttt{date} but controls the format of \cmd{printdatelabel}. + \optitem{urldate} Similar to \texttt{date} but controls the format of \cmd{printurldate}. @@ -9375,7 +9501,7 @@ This counter is similar to \cnt{citecount} but only available in multicite comma \cntitem{listtotal} -This counter holds the total number of items in the current list. It is intended for use in list formatting directives and does not hold a meaningful value when used anywhere else. As an exception, it may also be used in the second optional argument to \cmd{printnames} and \cmd{printlist}, see \secref{aut:bib:dat} for details. For every list, there is also a counter by the same name which holds the total number of items in the corresponding list. For example, the \cnt{author} counter holds the total number of items in the \bibfield{author} list. This applies to both name lists and literal lists. These counters are similar to \cnt{listtotal} except that they may also be used independently of list formatting directives. For example, a bibliography style might check the \cnt{editor} counter to decide Whether or not to print the term «editor» or rather its plural form «editors» after the list of editors. +This counter holds the total number of items in the current list. It is intended for use in list formatting directives and does not hold a meaningful value when used anywhere else. As an exception, it may also be used in the second optional argument to \cmd{printnames} and \cmd{printlist}, see \secref{aut:bib:dat} for details. For every list, there is also a counter by the same name which holds the total number of items in the corresponding list. For example, the \cnt{author} counter holds the total number of items in the \bibfield{author} list. This applies to both name lists and literal lists. These counters are similar to \cnt{listtotal} except that they may also be used independently of list formatting directives. For example, a bibliography style might check the \cnt{editor} counter to decide Whether or not to print the term «editor» or rather its plural form «editors» after the list of editors. \cntitem{listcount} @@ -9424,6 +9550,10 @@ Appends the \prm{code} to an internal hook executed at the beginning of every it Appends the \prm{code} to an internal hook executed at the beginning of every item in the list of shorthands. The \prm{code} is executed immediately after the \prm{item code} of \cmd{defbibenvironment}. The bibliographic data of the respective entry is available at this point. This command may only be used in the preamble. +\cmditem{AtNextBibliography}{code} + +Similar to \cmd{AtBeginBibliography} but only affecting the next \cmd{printbibliography}. The internal hook is cleared after being executed once. This command may be used in the document body. + \cmditem{AtEveryCite}{code} Appends the \prm{code} to an internal hook executed at the beginning of every citation command. The \prm{code} is executed immediately before the \prm{precode} of the command (see \secref{aut:cbx:cbx}). No bibliographic data is available at this point. This command may only be used in the preamble. @@ -10355,7 +10485,7 @@ The \opt{ris} driver reflects the fact that \opt{ris} itself is a very simple an \subsection{\opt{zoterordfxml}} -The \opt{zoterordfxml} driver reads the Zotero\footnote{\url{www.zotero.org}} XML representation of its RDF format. From the \biblatex point of view, it suffers from a lack of the notion of a citation key and so is of limited use. The format may include a citation key in the future at which point the \biber driver and these default mappings will be updated. As with \opt{endnotexml}, the format is somewhat messy with, in particular, a very limited way of dealing with related entries which makes the driver setup rather ugly. As can be seen below, it is possible to map into a field prefixed with «BIBERCUSTOM» which is not a real field in the data model but can be detected in the \biber driver itself and used to process a source field which does not map naturally to any \biblatex data model field as it needs special treatment. This is messy but is due largely due to messy source data models. +The \opt{zoterordfxml} driver reads the Zotero\footnote{\url{www.zotero.org}} XML representation of its RDF format. From the \biblatex point of view, it suffers from a lack of the notion of a citation key and so is of limited use. The format may include a citation key in the future at which point the \biber driver and these default mappings will be updated. As with \opt{endnotexml}, the format is somewhat messy with, in particular, a very limited way of dealing with related entries which makes the driver setup rather ugly. As can be seen below, it is possible to map into a field prefixed with «BIBERCUSTOM» which is not a real field in the data model but can be detected in the \biber driver itself and used to process a source field which does not map naturally to any \biblatex data model field as it needs special treatment. This is messy but is due largely due to messy source data models. \begin{lstlisting}[style=latex]{} \DeclareDriverSourcemap[datatype=zoterordfxml]{ @@ -10742,7 +10872,7 @@ labeltitlefield &\_&\_&\_&\+\\ labeltitleform &\_&\_&\_&\+\\ labeltitlelang &\_&\_&\_&\+\\ labeltitleyear &\+&\+&\+&\_\\ -labelyear &\+&\+&\+&\_\\ +labeldate &\+&\+&\+&\_\\ language &\+&\+&\_&\_\\ loadfiles &\+&\+&\_&\_\\ loccittracker &\+&\+&\_&\_\\ @@ -10802,6 +10932,20 @@ This revision history is a list of changes relevant to users of this package. Ch \begin{changelog} +\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 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 \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 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 Changed some \biber\ option names to cohere with \biber\ 1.5. @@ -11095,7 +11239,7 @@ This revision history is a list of changes relevant to users of this package. Ch \item Added option \opt{check} to \cmd{printbibliography}\see{use:bib:bib} \item Added option \opt{check} to \cmd{printshorthands}\see{use:bib:los} \item Added \cmd{defbibcheck}\see{use:bib:flt} -\item Updated support for Portuguese (José Carlos Santos) +\item Updated support for Portuguese (José Carlos Santos) \item Fixed conflict with \sty{titletoc} \item Fixed some bugs \end{release} @@ -11144,7 +11288,7 @@ This revision history is a list of changes relevant to users of this package. Ch %\item Added field alias \bibfield{primaryclass}\see{bib:fld:als} %\item Updated documentation\see{use:use:epr} %\item Tweaked package option \kvopt{babel}{other*}\see{use:opt:pre:gen} -%\item Updated support for Brazilian (Mateus Araújo) +%\item Updated support for Brazilian (Mateus Araújo) %\item Fixed some bugs %\end{release} % @@ -11240,7 +11384,7 @@ This revision history is a list of changes relevant to users of this package. Ch %\item Added localization key \texttt{backrefpages}\see{aut:lng:key} %\item Slightly expanded documentation\see{bib:use:dat} %\item Slightly expanded documentation\see{aut:bbx:fld:dat} -%\item Added support for Finnish (translations by Hannu Väisänen) +%\item Added support for Finnish (translations by Hannu Väisänen) %\item Updated support for Greek (translations by Prokopis) % %\end{release} @@ -11422,7 +11566,7 @@ This revision history is a list of changes relevant to users of this package. Ch %\item Updated and clarified documentation\see{aut:lng:key} %\item Added support for Brazilian Portuguese (by Augusto Ritter Stoffel) %\item Added preliminary support for Portuguese/Portugal\see{use:opt:pre:gen} -%\item Added revised Swedish translations (by Per Starbäck)\see{use:opt:pre:gen} +%\item Added revised Swedish translations (by Per Starbäck)\see{use:opt:pre:gen} %\item Expanded documentation\see{aut:cav:nam} %\item Improved concatenation of editorial and other roles %\item Fixed some bugs @@ -11595,7 +11739,7 @@ This revision history is a list of changes relevant to users of this package. Ch %\item Added \cmd{DeclareNumChars}\see{aut:aux:msc} %\item Added \cmd{DeclareRangeChars}\see{aut:aux:msc} %\item Added \cmd{DeclareRangeCommands}\see{aut:aux:msc} -%\item Added support for Swedish (translations by Per Starbäck and others) +%\item Added support for Swedish (translations by Per Starbäck and others) %\item Updated various localization files %\item Various minor improvements throughout %\item Fixed some bugs @@ -12048,7 +12192,7 @@ This revision history is a list of changes relevant to users of this package. Ch %\item Updated documentation\see{aut:fmt:fmt} %\item Updated and completed documentation\see{use:fmt:lng} %\item Updated and completed documentation\see{aut:fmt:lng} -%\item Added support for Spanish (translations by Ignacio Fernández Galván) +%\item Added support for Spanish (translations by Ignacio Fernández Galván) %\item Various memory-related optimizations in \path{biblatex.bst} % %\end{release} @@ -12231,7 +12375,7 @@ This revision history is a list of changes relevant to users of this package. Ch \end{document} %%% Local Variables: -%%% TeX-command-default: "PDFLaTeX" +%%% coding: utf-8 %%% eval: (auto-fill-mode -1) %%% eval: (visual-line-mode) %%% End: |