summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/biblatex/biblatex.tex')
-rw-r--r--Master/texmf-dist/doc/latex/biblatex/biblatex.tex72
1 files changed, 52 insertions, 20 deletions
diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
index 3a39461266e..25adb732d7f 100644
--- a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
+++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
@@ -60,7 +60,7 @@
url={\biblatexhome},
author={Philipp Lehman \\(with Philip Kime, Audrey Boruvka and Joseph Wright)},
email={},
- revision={3.6},
+ revision={3.7},
date={\today}}
\hypersetup{%
@@ -1171,8 +1171,10 @@ Finnish & Finland & \opt{finnish} \\
French & France, Canada & \opt{french} \\
German & Germany & \opt{german} \\
& Austria & \opt{austrian} \\
+ & Switzerland & \opt{swissgerman} \\
German (new) & Germany & \opt{ngerman} \\
& Austria & \opt{naustrian} \\
+ & Switzerland & \opt{nswissgerman} \\
Greek & Greece & \opt{greek} \\
Italian & Italy & \opt{italian} \\
Norwegian & Norway & \opt{norwegian}, \opt{norsk}, \opt{nynorsk} \\
@@ -1617,8 +1619,13 @@ This entry will be printed as «\emph{Journal Name}. New ser. 9 (1998)». See \s
\cmidrule{1-1}\cmidrule(l){2-2}\cmidrule(l){3-3}
1850 & 1850 & 1850 \\
1997/ & 1997-- & 1997-- \\
+/1997 & --1997 & --1997 \\
1997/unknown & 1997-- & 1997-- \\
+1997/* & 1997-- & 1997-- \\
+unknown/1997 & --1997 & --1997 \\
+*/1997 & --1997 & --1997 \\
1997/open & 1997-- & 1997-- \\
+open/1997 & --1997 & --1997 \\
1967-02 & 02/1967 & February 1967 \\
2009-01-31 & 31/01/2009 & 31st January 2009 \\
1988/1992 & 1988--1992 & 1988--1992 \\
@@ -1631,13 +1638,13 @@ This entry will be printed as «\emph{Journal Name}. New ser. 9 (1998)». See \s
\label{bib:use:tab1}
\end{table}
-Date fields such as the default data model dates \bibfield{date}, \bibfield{origdate}, \bibfield{eventdate}, and \bibfield{urldate} adhere to \acr{EDTF}\footnote{\url{https://www.loc.gov/standards/datetime/pre-submission.html}} (Extended Date/Time Format) specification levels 0 and 1. \acr{EDTF} is a stricter subset of the somewhat messy formats allowed by \acr{ISO8601v2004} and is better suited to bibliographic data. In addition to the \acr{EDTF} empty date range markers, you may also specify an open ended date range by giving the range separator and omitting the end date (\eg \texttt{YYYY/}). See \tabref{bib:use:tab1} for some examples of valid date specifications and the formatted dates automatically generated by \biblatex. The formatted date is language specific and will be adapted automatically. If there is no \bibfield{date} field in an entry, \biblatex will also consider the fields \bibfield{year} and \bibfield{month} for backwards compatibility with traditional \bibtex but this is not encouraged as explicit \bibfield{year} and \bibfield{month} are not parsed for date meta-information markers or times and are used as-is. Style authors should note that date fields like \bibfield{date} or \bibfield{origdate} are only available in the \file{bib} file. All dates are parsed and dissected into their components as the \file{bib} file is processed. The date and time components are made available to styles by way of the special fields discussed in \secref{aut:bbx:fld:dat}. See this section and \tabref{aut:bbx:fld:tab1} on page~\pageref{aut:bbx:fld:tab1} for further information.
+Date fields such as the default data model dates \bibfield{date}, \bibfield{origdate}, \bibfield{eventdate}, and \bibfield{urldate} adhere to \acr{EDTF}\footnote{\url{https://www.loc.gov/standards/datetime/pre-submission.html}} (Extended Date/Time Format) specification levels 0 and 1. Also supported are the open-ended range specifications in section 4.5 of the current working draft of ISO8601-2\footnote{\url{http://www.loc.gov/standards/datetime/iso-tc154-wg5_n0039_iso_wd_8601-2_2016-02-16.pdf}}. \acr{EDTF} is a stricter subset of the somewhat messy formats allowed by \acr{ISO8601v2004} and is better suited to bibliographic data. In addition to the \acr{EDTF} empty date range markers, you may also specify an open ended/start date range by giving the range separator and omitting the end/start date (\eg \texttt{YYYY/}, \texttt{/YYYY}). See \tabref{bib:use:tab1} for some examples of valid date specifications and the formatted dates automatically generated by \biblatex. The formatted date is language specific and will be adapted automatically. If there is no \bibfield{date} field in an entry, \biblatex will also consider the fields \bibfield{year} and \bibfield{month} for backwards compatibility with traditional \bibtex but this is not encouraged as explicit \bibfield{year} and \bibfield{month} are not parsed for date meta-information markers or times and are used as-is. Style authors should note that date fields like \bibfield{date} or \bibfield{origdate} are only available in the \file{bib} file. All dates are parsed and dissected into their components as the \file{bib} file is processed. The date and time components are made available to styles by way of the special fields discussed in \secref{aut:bbx:fld:dat}. See this section and \tabref{aut:bbx:fld:tab1} on page~\pageref{aut:bbx:fld:tab1} for further information.
\acr{EDTF} dates are astronomical dates in which year <0> exists. When outputting dates in BCE or BC era (see the \opt{dateera} option below), note that they will typically be one year earlier since BCE/BC era do not have a year 0 (year 0 is 1 BCE/BC). This conversion is automatic. See examples in table \tabref{bib:use:tab2}.
Date field names \emph{must} end with the string <date>, as with the default date fields. Bear this in mind when adding new date fields to the datamodel (see \secref{aut:ctm:dm}). \biblatex will check all date fields after reading the date model and will exit with an error if it finds a date field which does not adhere to this naming convention.
-\acr{EDTF} supports dates before common era (BCE/BC) by way of a negative date format and supports <approximate> (circa) and uncertain dates. Such date formats set internal markers which can be tested for so that appropriate localised markers (such as \opt{circa} or \opt{beforecommonera}) can be inserted. Also supported are <uncertain> dates (\acr{EDTF} 5.2.2) which are automatically expanded into appropriate data ranges accompanied by a field \bibfield{$<$datetype$>$dateunspecified} which details the granularity of the unspecified data. Styles may use this information to format such dates appropriately but the standard styles do not do this. See \tabref{bib:use:tab3} on page~\pageref{bib:use:tab3} for the allowed \acr{EDTF} <unspecified> formats, their range expansions and \bibfield{$<$datetype$>$dateunspecified} values (see \secref{aut:bbx:fld:gen}).
+\acr{EDTF} supports dates before common era (BCE/BC) by way of a negative date format and supports <approximate> (circa) and uncertain dates. Such date formats set internal markers which can be tested for so that appropriate localised markers (such as \opt{circa} or \opt{beforecommonera}) can be inserted. Also supported are <unspecified> dates (\acr{EDTF} 5.2.2) which are automatically expanded into appropriate data ranges accompanied by a field \bibfield{$<$datetype$>$dateunspecified} which details the granularity of the unspecified data. Styles may use this information to format such dates appropriately but the standard styles do not do this. See \tabref{bib:use:tab3} on page~\pageref{bib:use:tab3} for the allowed \acr{EDTF} <unspecified> formats, their range expansions and \bibfield{$<$datetype$>$dateunspecified} values (see \secref{aut:bbx:fld:gen}).
\begin{table}
\tablesetup
@@ -1658,7 +1665,7 @@ Date field names \emph{must} end with the string <date>, as with the default dat
\label{bib:use:tab3}
\end{table}
-\tabref{bib:use:tab2} shows formats which use appropriate tests and formatting. See the date meta-information tests in \secref{aut:aux:tst} and the localisation strings in in \secref{aut:lng:key:dt}. See also the \file{96-dates.tex} example file for complete examples of the tests and localisation strings use.
+\tabref{bib:use:tab2} shows formats which use appropriate tests and formatting. See the date meta-information tests in \secref{aut:aux:tst} and the localisation strings in \secref{aut:lng:key:dt}. See also the \file{96-dates.tex} example file for complete examples of the tests and localisation strings use.
The output of <circa>, uncertainty and era information in standard styles (or custom styles not customising the internal \cmd{mkdaterange*} macros) is controlled by the package options \opt{datecirca}, \opt{dateuncertain}, \opt{dateera} and \opt{dateeraauto} (see \secref{use:opt:pre:gen}). See \tabref{bib:use:tab2} on page~\pageref{bib:use:tab2} for examples which assumes these options are all used.
@@ -3821,14 +3828,14 @@ At the beginning of the document, there is always a global context containing gl
% labelprefix=A
\end{refcontext}
-\newfcontext}[labelprefix=B]
+\newrefcontext}[labelprefix=B]
% reference context:
% sorting=nty
% sortingnamekeyscheme=global
% labelprefix=B
\endrefcontext
-\newfcontext}[sorting=ynt,labelprefix=C]{testrc}
+\newrefcontext}[sorting=ynt,labelprefix=C]{testrc}
% reference context:
% sorting=ynt
% sortingnamekeyscheme=global
@@ -3844,9 +3851,11 @@ At the beginning of the document, there is always a global context containing gl
\cmditem{assignrefcontextcats*}[key=value, \dots]{category1, category2, ...}
\cmditem{assignrefcontextentries}[key=value, \dots]{entrykey1, entrykey2, ...}
\cmditem{assignrefcontextentries*}[key=value, \dots]{entrykey1, entrykey2, ...}
+\cmditem{assignrefcontextentries}[key=value, \dots]{*}
+\cmditem{assignrefcontextentries*}[key=value, \dots]{*}
\end{ltxsyntax}
-These commands automate putting citations into refcontexts when the default behaviour is not sufficient. The default behaviour is that the data for a citation is drawn from the refcontext of the last bibliography in which it was printed. For citations that are used in some way but not printed in a bibliography or bibliography list, they default to drawing their data from the global refcontext established at the beginning of the document. To override this behaviour, instead of manually wrapping citation commands in \env{refcontext} environments, which might be error-prone and tedious, you can register a comma"=separated list of \prm{keywords}, \prm{categories} or \prm{entrykeys} which, respectively, make the entries with any of the specified keywords, entries in any of the specified categories (see \secref{use:use:div}) or entries with any of the specified citation keys draw their data from a particular refcontext specified by the \prm{refcontext key/values} which are parsed as the per the corresponding \env{refcontext} options. Such refcontext auto-assignments are specific to the current refsection. You may specify the same citation key in any of these commands but be aware that assignment is done in the order \prm{keywords}, \prm{categories}, \prm{entrykeys} with the later specifications overriding the earlier. An example:
+These commands automate putting citations into refcontexts when the default behaviour is not sufficient. The default behaviour is that the data for a citation is drawn from the refcontext of the last bibliography in which it was printed. For citations that are used in some way but not printed in a bibliography or bibliography list, they default to drawing their data from the global refcontext established at the beginning of the document. To override this behaviour, instead of manually wrapping citation commands in \env{refcontext} environments, which might be error-prone and tedious, you can register a comma"=separated list of \prm{keywords}, \prm{categories} or \prm{entrykeys} which, respectively, make the entries with any of the specified keywords, entries in any of the specified categories (see \secref{use:use:div}) or entries with any of the specified citation keys draw their data from a particular refcontext specified by the \prm{refcontext key/values} which are parsed as the per the corresponding \env{refcontext} options. Such refcontext auto-assignments are specific to the current refsection. You may specify the same citation key in any of these commands but be aware that assignment is done in the order \prm{keywords}, \prm{categories}, \prm{entrykeys} with the later specifications overriding the earlier. \cmd{assignrefcontextentries} accepts a single asterisk instead of a list of entrykeys which allows the assignment of all keys in a refsection to a refcontext with having to explicitly list them. An example:
\begin{ltxexample}[style=latex]{}
\assignrefcontextentries[labelprefix=A]{key2}
@@ -4636,7 +4645,7 @@ A. Smith. Title. 2000, (Orig. pub. as<<->>Origtitle)
\end{ltxexample}
\csitem{relateddelim}
-The separator between the data of multiple related entries. The default definition is an optional dot plus linebreak. Here is an example where volumes A-E are related entries of the 5 volume main work:
+The generic separator between the data of multiple related entries. The default definition is an optional dot plus linebreak. Here is an example where volumes A-E are related entries of the 5 volume main work:
\begin{ltxexample}
Donald E. Knuth. Computers & Typesetting. 5 vols. Reading, Mass.: Addison-
@@ -4648,8 +4657,10 @@ Vol. D: METAFONT: The Program. 1986.
Vol. E: Computer Modern Typefaces. 1986.
\end{ltxexample}
-\end{ltxsyntax}
+\csitem{relateddelim$<$relatedtype$>$}
+The separator between the data of multiple related entries inside related entries of type <relatedtype>. There is no default, if such a type-specific delimiter does not exist, \cmd{relateddelim} is used.
+\end{ltxsyntax}
\subsubsection{Context-sensitive Delimiters}
\label{use:fmt:csd}
@@ -4771,7 +4782,7 @@ The language specific marker to be used after uncertain dates when the global op
\csitem{bibdateeraprefix}
-The language specific marker which is printed as a prefix to beginning BCE/BC dates in a date range when the option \opt{dateera} is set to <astronomical>. Defaults to \cmd{textminus}.
+The language specific marker which is printed as a prefix to beginning BCE/BC dates in a date range when the option \opt{dateera} is set to <astronomical>. Defaults to \cmd{textminus}, if defined and \cmd{textendash} otherwise.
\csitem{bibdateeraendprefix}
@@ -7032,6 +7043,8 @@ This defines the macros \cmd{datafieldsetsetnames} and \cmd{datafieldsetsettitle
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 \biblatex macros in which case you can apply the modification only for specific documents, styles or globally.
+Source mapping happens during data parsing and therefore before any other operation such as inheritance and sorting.
+
Source mappings can be defined at different «levels» which are applied
in a defined order. See the \biblatex\ manual regarding these macros:\\[2ex]
@@ -7063,9 +7076,9 @@ Defines source data modification (mapping) rules which can be used to perform an
The \prm{specification} is an undelimited list of \cmd{maps} directives which specify containers for mappings rules applying to a particular data source type (\secref{use:bib:res}). Spaces, tabs, and line endings may be used freely to visually arrange the \prm{specification}. Blank lines are not permissible. This command may only be used in the preamble and may only be used once---subsequent uses will overwrite earlier definitions.
-\cmditem{maps}{elements}
+\cmditem{maps}[options]{elements}
-Contains an ordered set of \cmd{map} elements each of which is a logically related set of mapping steps to apply to the data source.
+Contains an ordered set of \cmd{map} elements each of which is a logically related set of mapping steps to apply to the data source. The \prm{options} are:
\begin{optionlist*}
@@ -7079,9 +7092,9 @@ Specify whether a mapping rule is allowed to overwrite already existing data in
\end{optionlist*}
-\cmditem{map}{restrictions,steps}
+\cmditem{map}[options]{restrictions,steps}
-A container for an ordered set of map \cmd{step}s, optionally restricted to particular entrytypes or data sources. This is a grouping element to allow a set of mapping steps to apply only to specific entrytypes or data sources. Mapping steps must always be contained within a \cmd{map} element.
+A container for an ordered set of map \cmd{step}s, optionally restricted to particular entrytypes or data sources. This is a grouping element to allow a set of mapping steps to apply only to specific entrytypes or data sources. Mapping steps must always be contained within a \cmd{map} element. The \prm{options} are:
\begin{optionlist*}
@@ -8479,7 +8492,16 @@ Finally, here is an example of a sorting scheme which overrides the global sorti
\cmditem{DeclareSortExclusion}{entrytype, \dots}{field, \dots}
-Specifies fields to be excluded from sorting on a per-type basis. The \prm{entrytype} argument and the \prm{field} argument may be a comma"=separated list of values. A blank \prm{field} argument will clear all exclusions for this \prm{entrytype}. This command may only be used in the preamble.
+Specifies fields to be excluded from sorting on a per-type basis. The \prm{entrytype} argument and the \prm{field} argument may be a comma"=separated list of values. A blank \prm{field} argument will clear all exclusions for this \prm{entrytype}. A value of <*> for \prm{entrytype} will exclude \prm{field,\dots} for every entrytype. This is equivalent to simply deleting the field from the sorting specification and is only normally used in combination with \cmd{DeclareSortInclusion} when one wishes to exclude a field for all but explicitly included entrytypes. See example in \cmd{DeclareSortInclusion} below. This command may only be used in the preamble.
+
+\cmditem{DeclareSortInclusion}{entrytype, \dots}{field, \dots}
+
+Only used along with \cmd{DeclareSortExclusion}. Specifies fields to be included in sorting on a per-type basis. This allows the user to exclude a field from sorting for all entrytypes and then to override this for certain entrytypes. This is easier sometimes than using \cmd{DeclareSortExclusion} to list exclusions for many entrytypes. The \prm{entrytype} argument and the \prm{field} argument may be a comma"=separated list of values. This command may only be used in the preamble. For example, this would use \bibfield{title} during sorting only for \bibtype{article}s:
+
+\begin{ltxexample}
+\DeclareSortExclusion{*}{title}
+\DeclareSortInclusion{article}{title}
+\end{ltxexample}
\cmditem{DeclarePresort}[entrytype, \dots]{string}
@@ -9528,7 +9550,7 @@ Similar to the \cmd{forcsvlist} command from the \sty{etoolbox} package, except
\cmditem{MakeCapital}{text}
-Similar to \cmd{MakeUppercase} but only coverts the first printable character in \prm{text} to uppercase. Note that the restrictions that apply to \cmd{MakeUppercase} also apply to this command. Namely, all commands in \prm{text} must either be robust or prefixed with \cmd{protect} since the \prm{text} is expanded during capitalization. Apart from Ascii characters and the standard accent commands, this command also handles the active characters of the \sty{inputenc} package as well as the shorthands of the \sty{babel} package. If the \prm{text} starts with a control sequence, nothing is capitalized. This command is robust.
+Similar to \cmd{MakeUppercase} but only converts the first printable character in \prm{text} to uppercase. Note that the restrictions that apply to \cmd{MakeUppercase} also apply to this command. Namely, all commands in \prm{text} must either be robust or prefixed with \cmd{protect} since the \prm{text} is expanded during capitalization. Apart from Ascii characters and the standard accent commands, this command also handles the active characters of the \sty{inputenc} package as well as the shorthands of the \sty{babel} package. If the \prm{text} starts with a control sequence, nothing is capitalized. This command is robust.
\cmditem{MakeSentenceCase}{text}
\cmditem*{MakeSentenceCase*}{text}
@@ -10183,7 +10205,8 @@ The \prm{language} is the string given in the \bibfield{language} field (without
\begin{ltxexample}
\DeclareRedundantLanguages{french}{french}
-\DeclareRedundantLanguages{german}{german,ngerman,austrian,naustrian}
+\DeclareRedundantLanguages{german}{german,ngerman,austrian,naustrian,
+ nswissgerman,swissgerman}
\DeclareRedundantLanguages{english,american}{english,american,british,
canadian,australian,newzealand,USenglish,UKenglish}
\end{ltxexample}
@@ -10940,6 +10963,9 @@ The separator between the relatedtype bibliography localisation string and the d
\csitem{relateddelim}
The separator between the data of multiple related entries. The default definition is a linebreak.
+\csitem{relateddelim$<$relatedtype$>$}
+The separator between the data of multiple related entries inside related entries of type <relatedtype>. There is no default, if such a type-specific delimiter does not exist, \cmd{relateddelim} is used.
+
\end{ltxsyntax}
\subsubsection{Language-specific Commands}
@@ -10984,7 +11010,7 @@ The language specific marker to be used after uncertain dates when the global op
\csitem{bibdateeraprefix}
-The language specific marker which is printed as a prefix to beginning BCE/BC dates in a date range when the option \opt{dateera} is set to <astronomical>. Defaults to \cmd{textminus}.
+The language specific marker which is printed as a prefix to beginning BCE/BC dates in a date range when the option \opt{dateera} is set to <astronomical>. Defaults to \cmd{textminus}, if defined and \cmd{textendash} otherwise.
\csitem{bibdateeraendprefix}
@@ -12142,7 +12168,7 @@ Since the alternative \file{lbx} file can inherit strings from the standard \pat
\endinput
\end{ltxexample}
%
-Alternative \file{lbx} files must ensure that the localisation module is complete. They will typically do so by inheriting data from the corresponding standard module. If the language \texttt{american} is mapped to \path{american-mla.lbx}, \biblatex will not load \path{american.lbx} unless this module is requested explicitly. In the above example, inheriting <strings> and <extras> will cause \biblatex to load \path{american.lbx} before applying the modifications in \path{american-mla.lbx}.
+Alternative \file{lbx} files must ensure that the localisation module is complete. They should do so by inheriting data from the corresponding standard module. If the language \texttt{american} is mapped to \path{american-mla.lbx}, \biblatex will not load \path{american.lbx} unless this module is requested explicitly. In the above example, inheriting <strings> and <extras> will cause \biblatex to load \path{american.lbx} before applying the modifications in \path{american-mla.lbx}.
Note that \cmd{DeclareLanguageMapping} is not intended to handle language variants (\eg American English vs. British English) or \sty{babel}/\sty{polyglossia} language aliases (\eg \texttt{USenglish} vs. \texttt{american}). For example, \sty{babel}/\sty{polyglossia} offers the \texttt{USenglish} option which is similar to \texttt{american}. Therefore, \biblatex ships with an \path{USenglish.lbx} file which simply inherits all data from \path{american.lbx} (which in turn gets the <strings> from \path{english.lbx}). In other words, the mapping of language variants and \sty{babel}/\sty{polyglossia} language aliases happens on the file level, the point being that \biblatex's language support can be extended simply by adding additional \file{lbx} files. There is no need for centralized mapping. If you need support for, say, Portuguese (babel/polyglossia: \file{portuges}), you create a file named \path{portuges.lbx}. If \sty{babel}/\sty{polyglossia} offered an alias named \texttt{brasil}, you would create \path{brasil.lbx} and inherit the data from \path{portuges.lbx}. In contrast to that, the point of \cmd{DeclareLanguageMapping} is handling \emph{stylistic} variants like <humanities vs. natural sciences> or <\acr{mla} vs. \acr{apa}> etc. which will typically be built on top of existing \file{lbx} files.
@@ -12801,7 +12827,13 @@ This revision history is a list of changes relevant to users of this package. Ch
\begin{changelog}
-\begin{release}{3.6}{2016-09-17}
+\begin{release}{3.7}{2016-12-08}
+\item Corrected default for \cmd{bibdateeraprefix}\see{aut:fmt:lng}
+\item Added \cmd{DeclareSortInclusion}\see{aut:ctm:srt}
+\item Added \cmd{relateddelim$<$relatedtype$>$}\see{use:fmt:fmt}
+\end{release}
+
+\begin{release}{3.6}{2016-09-15}
\item Corrected some documentation and fixed a bug with labeldate
localisation strings.
\end{release}