From 5f46fd638f10294ee1db2535603713f85b373080 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Fri, 3 Aug 2012 00:12:07 +0000 Subject: biblatex (1aug12) git-svn-id: svn://tug.org/texlive/trunk@27290 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/bibtex/bst/biblatex/biblatex.bst | 6 +- Master/texmf-dist/doc/latex/biblatex/RELEASE | 9 + Master/texmf-dist/doc/latex/biblatex/biblatex.pdf | Bin 1371252 -> 1384035 bytes Master/texmf-dist/doc/latex/biblatex/biblatex.tex | 94 ++-- .../biblatex/bibtex/bib/biblatex-examples.bib | 1 + .../latex/biblatex/examples/90-related-entries.pdf | Bin 109819 -> 109816 bytes .../latex/biblatex/examples/biblatex-examples.bib | 1 + Master/texmf-dist/tex/latex/biblatex/biblatex.def | 12 +- Master/texmf-dist/tex/latex/biblatex/biblatex.sty | 13 +- Master/texmf-dist/tex/latex/biblatex/biblatex2.sty | 97 ++-- .../tex/latex/biblatex/lbx/norwegian.lbx | 603 ++++++++++++--------- .../texmf-dist/tex/latex/biblatex/lbx/nynorsk.lbx | 276 ++++++++++ Master/tlpkg/libexec/ctan2tds | 5 +- 13 files changed, 758 insertions(+), 359 deletions(-) (limited to 'Master') diff --git a/Master/texmf-dist/bibtex/bst/biblatex/biblatex.bst b/Master/texmf-dist/bibtex/bst/biblatex/biblatex.bst index ed1a98d21cf..4cfb357ddeb 100644 --- a/Master/texmf-dist/bibtex/bst/biblatex/biblatex.bst +++ b/Master/texmf-dist/bibtex/bst/biblatex/biblatex.bst @@ -173,7 +173,7 @@ STRINGS { ctrl.alphaothers templist tempstrga tempstrgb resvstrga last.name last.hash last.year last.extra } FUNCTION {initialize} { - "$Revision: 2.0 $" + "$Revision: 2.1 $" #12 entry.max$ substring$ #-3 entry.max$ substring$ "Biblatex version: " swap$ * top$ @@ -1760,7 +1760,7 @@ FUNCTION {input:control:options} { FUNCTION {input:control:version} { input:control:parse - "$Revision: 2.0 $" + "$Revision: 2.1 $" #12 entry.max$ substring$ #-3 entry.max$ substring$ 'tempstrga := @@ -2583,7 +2583,7 @@ SORT FUNCTION {output:main:begin} { "% $ biblatex auxiliary file $" write$ newline$ - "% $ biblatex version " "$Revision: 2.0 $" + "% $ biblatex version " "$Revision: 2.1 $" #12 entry.max$ substring$ #-3 entry.max$ substring$ * " $" * write$ newline$ "% Do not modify the above lines!" write$ newline$ "%" write$ newline$ diff --git a/Master/texmf-dist/doc/latex/biblatex/RELEASE b/Master/texmf-dist/doc/latex/biblatex/RELEASE index edf961626e5..a14d8242505 100644 --- a/Master/texmf-dist/doc/latex/biblatex/RELEASE +++ b/Master/texmf-dist/doc/latex/biblatex/RELEASE @@ -1,3 +1,12 @@ +RELEASE NOTES FOR VERSION 2.1 + +* Biber version 1.1 is required for biblatex 2.1 + +* Custom data models is now looked for in more places. See PDF + documentation. Custom data model conflicts are now better processed by + biber. +* Some improved localisation (Norwegian) and doc fixes. + RELEASE NOTES FOR VERSION 2.0 * Biber is now the default backend. Biblatex 2.0 requires biber diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf b/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf index faf1c40c0c5..074f1392cfc 100644 Binary files a/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf and b/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf differ diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex index 6516124f689..babaded2a03 100644 --- a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex +++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex @@ -42,7 +42,7 @@ url={\biblatexhome}, author={Philipp Lehman (with Audrey Boruvka, Philip Kime and Joseph Wright)}, email={}, - revision={2.0}, + revision={2.1}, date={07/2012}} \hypersetup{% @@ -154,7 +154,7 @@ Please use the \sty{biblatex} project page on GitHub to report bugs and submit f 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 (Danish\slash Norwegian), +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), @@ -304,7 +304,7 @@ The \sty{ucs} package provides support for \utf encoded input. Either use \sty{i It is important to distinguish between \bibtex the program and \bibtex the file format. \sty{biblatex} can be used with or without \bibtex the program since its default backend \biber uses fully supports the \bibtex file format (\file{bib}) and users should be able to move to \sty{biblatex} will little or no changes to their \bibtex data files when using \biber as a backend. If using \bibtex as the data backend, note that you cannot use arbitrary \file{bst} files because the package depends on a special \bibtex interface. When using \bibtex as a backend, \sty{biblatex} uses its own special \file{bst} file only. The entry guide below is backend agnostic unless otherwise stated. -This section describes the default data model defined in the \file{blx-dm.def} file which is part of \path{biblatex}. The data model is defined using the macros documented in \secref{aut:ctm:dm}. It is possible to redefine the data model which both \sty{biblatex} and \biber use so that datasources can contain new entrytypes and fields (which of course will need style support). The data model specfication also allows for constraints to be defined so that data sources can be validated against the data model (using \biber's \path{--validate_datamodel} option). Users who want to customise the data model need to look at the \file{blx-dm.def} file and to read \secref{aut:ctm:dm}. +This section describes the default data model defined in the \file{blx-dm.def} file which is part of \path{biblatex}. The data model is defined using the macros documented in \secref{aut:ctm:dm}. It is possible to redefine the data model which both \sty{biblatex} and \biber use so that datasources can contain new entrytypes and fields (which of course will need style support). The data model specification also allows for constraints to be defined so that data sources can be validated against the data model (using \biber's \path{--validate_datamodel} option). Users who want to customise the data model need to look at the \file{blx-dm.def} file and to read \secref{aut:ctm:dm}. \subsection{Entry Types} \label{bib:typ} @@ -402,7 +402,7 @@ A fallback type for entries which do not fit into any other category. Use the fi \typeitem{online} -An online resource. \bibfield{author}, \bibfield{editor}, and \bibfield{year} are omissible in terms of \secref{bib:use:key}. This entry type is intended for sources such as web sites which are intrinsicly online resources. Note that all entry types support the \bibfield{url} field. For example, when adding an article from an online journal, it may be preferable to use the \bibtype{article} type and its \bibfield{url} field. +An online resource. \bibfield{author}, \bibfield{editor}, and \bibfield{year} are omissible in terms of \secref{bib:use:key}. This entry type is intended for sources such as web sites which are intrinsically online resources. Note that all entry types support the \bibfield{url} field. For example, when adding an article from an online journal, it may be preferable to use the \bibtype{article} type and its \bibfield{url} field. \reqitem{author/editor, title, year/date, url} \optitem{subtitle, titleaddon, language, version, note, organization, date, month, year, addendum, pubstate, urldate} @@ -529,7 +529,7 @@ Works of the visual arts such as paintings, sculpture, and installations. \typeitem{audio} -Audio recordings, typically on audio \acr{CD}, \acr{DVD}, audio casette, or similar media. See also \bibtype{music}. +Audio recordings, typically on audio \acr{CD}, \acr{DVD}, audio cassette, or similar media. See also \bibtype{music}. \typeitem{bibnote} @@ -585,7 +585,7 @@ National and international standards issued by a standards body such as the Inte \typeitem{video} -Audiovisual recordings, typically on \acr{DVD}, \acr{VHS} casette, or similar media. See also \bibtype{movie}. +Audiovisual recordings, typically on \acr{DVD}, \acr{VHS} cassette, or similar media. See also \bibtype{movie}. \end{typelist} @@ -718,19 +718,19 @@ The edition of a printed publication. This must be an integer, not an ordinal. D \listitem{editor}{name} -The editor(s) of the \bibfield{title}, \bibfield{booktitle}, or \bibfield{maintitle}, depending on the entry type. Use the \bibfield{editortype} field to specifiy the role if it is different from <\texttt{editor}>. See \secref{bib:use:edr} for further hints. +The editor(s) of the \bibfield{title}, \bibfield{booktitle}, or \bibfield{maintitle}, depending on the entry type. Use the \bibfield{editortype} field to specify the role if it is different from <\texttt{editor}>. See \secref{bib:use:edr} for further hints. \listitem{editora}{name} -A secondary editor performing a different editorial role, such as compiling, redacting, etc. Use the \bibfield{editoratype} field to specifiy the role. See \secref{bib:use:edr} for further hints. +A secondary editor performing a different editorial role, such as compiling, redacting, etc. Use the \bibfield{editoratype} field to specify the role. See \secref{bib:use:edr} for further hints. \listitem{editorb}{name} -Another secondary editor performing a different role. Use the \bibfield{editorbtype} field to specifiy the role. See \secref{bib:use:edr} for further hints. +Another secondary editor performing a different role. Use the \bibfield{editorbtype} field to specify the role. See \secref{bib:use:edr} for further hints. \listitem{editorc}{name} -Another secondary editor performing a different role. Use the \bibfield{editorctype} field to specifiy the role. See \secref{bib:use:edr} for further hints. +Another secondary editor performing a different role. Use the \bibfield{editorctype} field to specify the role. See \secref{bib:use:edr} for further hints. \fielditem{editortype}{key} @@ -1498,7 +1498,7 @@ This entry will be printed as \label{bib:use:tab1} \end{table} -The date fields \bibfield{date}, \bibfield{origdate}, \bibfield{eventdate}, and \bibfield{urldate} require a date specification in \texttt{yyyy-mm-dd} format. Date ranges are given as \texttt{yyyy-mm-dd\slash yyyy-mm-dd}. Partial dates are valid provided that date components are omitted at the end only. You may 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 date autmatically generated by \sty{biblatex}. The formatted date is language specific and will be adapted automatically. If there is no \bibfield{date} field in an entry, \sty{biblatex} will also consider the fields \bibfield{year} and \bibfield{month} for backwards compatibility with traditional \bibtex. Style author 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 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. +The date fields \bibfield{date}, \bibfield{origdate}, \bibfield{eventdate}, and \bibfield{urldate} require a date specification in \texttt{yyyy-mm-dd} format. Date ranges are given as \texttt{yyyy-mm-dd\slash yyyy-mm-dd}. Partial dates are valid provided that date components are omitted at the end only. You may 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 date automatically generated by \sty{biblatex}. The formatted date is language specific and will be adapted automatically. If there is no \bibfield{date} field in an entry, \sty{biblatex} will also consider the fields \bibfield{year} and \bibfield{month} for backwards compatibility with traditional \bibtex. Style author 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 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. \subsubsection{Months and Journal Issues} \label{bib:use:iss} @@ -2093,7 +2093,7 @@ This option controls how sequences of consecutive pages in the list of back refe \item[two] Compress any sequence of two or more consecutive pages to a range, \eg the above list is compressed to <1--2, 11--13, 21--24>. -\item[two+] Similar in concept to \opt{two} but a sequence of exactely two consecutive pages is printed using the starting page and the localization string \texttt{sequens}, \eg the above list is compressed to <1\,sq., 11--13, 21--24>. +\item[two+] Similar in concept to \opt{two} but a sequence of exactly two consecutive pages is printed using the starting page and the localization string \texttt{sequens}, \eg the above list is compressed to <1\,sq., 11--13, 21--24>. \item[three+] Similar in concept to \opt{two+} but a sequence of exactly three consecutive pages is printed using the starting page and the localization string \texttt{sequentes}, \eg the above list is compressed to <1\,sq., 11\,sqq., 21--24>. @@ -2105,7 +2105,7 @@ All styles support both Arabic and Roman numerals. In order to avoid potentially \optitem[setonly]{backrefsetstyle}{\opt{setonly}, \opt{memonly}, \opt{setormem}, \opt{setandmem}, \opt{memandset}, \opt{setplusmem}} -This option controls how back references to \bibtype{set} entires and their members are handled. The following options are available: +This option controls how back references to \bibtype{set} entries and their members are handled. The following options are available: \begin{valuelist} @@ -2267,7 +2267,7 @@ See \secref{bib:cav:enc} for further instructions concerning the encoding of \fi \optitem[auto]{texencoding}{\opt{auto}, \prm{encoding}} -Specifies the encoding of the \file{tex} file. This option affects the data transfered from the backend to \sty{biblatex}. When using \biber, this corresponds to \biber's |--bblencoding| option. The following choices are available: +Specifies the encoding of the \file{tex} file. This option affects the data transferred from the backend to \sty{biblatex}. When using \biber, this corresponds to \biber's |--bblencoding| option. The following choices are available: \begin{valuelist} @@ -2450,7 +2450,7 @@ When enabled, sorting names will only use their initials. \BiberOnlyMark This is \boolitem[false]{terseinits} -This option controls the format of initials generated by \sty{biblatex}. If enabled, initals are rendered using a terse format without dots and spaces. For example, the initials of Donald Ervin Knuth would be rendered as by default, and as if this option is enabled. \BiberOnlyMark With \biber, the option works by redefining some macros which control the format of initials. See \secref{use:cav:nam} for details. +This option controls the format of initials generated by \sty{biblatex}. If enabled, initials are rendered using a terse format without dots and spaces. For example, the initials of Donald Ervin Knuth would be rendered as by default, and as if this option is enabled. \BiberOnlyMark With \biber, the option works by redefining some macros which control the format of initials. See \secref{use:cav:nam} for details. \boolitem[false]{labelalpha} @@ -2751,7 +2751,7 @@ This style prints the entry key rather than some kind of label. It is intended f \subsubsection{Bibliography Styles} \label{use:xbx:bbx} -All bibliography styles which come with this package use the same basic format for the individual bibliography entries. They only differ in the kind of label printed in the bibliography and the overall formatting of the list of references. There is a matching bibliography style for every citation style. Note that some bibliography styles are not mentioned below because they simply load a more generic style. For example, the bibligraphy style \texttt{authortitle-comp} will load the \texttt{authortitle} style. +All bibliography styles which come with this package use the same basic format for the individual bibliography entries. They only differ in the kind of label printed in the bibliography and the overall formatting of the list of references. There is a matching bibliography style for every citation style. Note that some bibliography styles are not mentioned below because they simply load a more generic style. For example, the bibliography style \texttt{authortitle-comp} will load the \texttt{authortitle} style. \begin{marglist} @@ -2780,7 +2780,7 @@ The following bibliography styles are special purpose styles. They are not inten \begin{marglist} \item[draft] -This draft style includes the entry keys in the bibliography. The bibligraphy will be sorted by entry key. The style will set the following package options at load time: \kvopt{sorting}{debug}. +This draft style includes the entry keys in the bibliography. The bibliography will be sorted by entry key. The style will set the following package options at load time: \kvopt{sorting}{debug}. \item[debug] This style prints all bibliographic data in tabular format. It is intended for debugging only and will set the following package options at load time: \kvopt{sorting}{debug}. @@ -2790,7 +2790,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 itseld independently). 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). 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, @@ -2947,7 +2947,7 @@ This command prints the bibliography. It takes one optional argument, which is a \valitem[bibliography/shorthands]{env}{name} -The layout of the bibliography and the list of shorthands is controlled by enviroments defined with \cmd{defbibenvironment}. This option selects an environment. The \prm{name} corresponds to the identifier used when defining the environment with \cmd{defbibenvironment}. By default, the \cmd{printbibliography} command uses the identifier \texttt{bibliography}; \cmd{printshorthands} uses \texttt{shorthands}. See also \secref{use:bib:los,use:bib:hdg}. +The layout of the bibliography and the list of shorthands is controlled by environments defined with \cmd{defbibenvironment}. This option selects an environment. The \prm{name} corresponds to the identifier used when defining the environment with \cmd{defbibenvironment}. By default, the \cmd{printbibliography} command uses the identifier \texttt{bibliography}; \cmd{printshorthands} uses \texttt{shorthands}. See also \secref{use:bib:los,use:bib:hdg}. \valitem[bibliography/shorthands]{heading}{name} @@ -3293,7 +3293,7 @@ See the author guide, in particular \secref{aut:aux:tst,aut:aux:ife}, for furthe \subsubsection{Dynamic Entry Sets} \label{use:bib:set} -In addition to the \bibtype{set} entry type, \sty{biblatex} also supports dynamic entry sets defined on a per-document\slash per-refsection basis. The following command, which may be used in the dcument preamble or the document body, defines the set \prm{key}: +In addition to the \bibtype{set} entry type, \sty{biblatex} also supports dynamic entry sets defined on a per-document\slash per-refsection basis. The following command, which may be used in the document preamble or the document body, defines the set \prm{key}: \begin{ltxsyntax} @@ -4304,7 +4304,7 @@ Whenever a reference to a work which has not been cited before is added, this pr \paragraph{\biber} -The \sty{biblatex} package uses one auxilliary \file{bcf} file only. Even if there are citation commands in a file included via \cmd{include}, you only need to run \biber on the main \file{bcf} file. All information \biber needs is in the \file{bcf} file, including information about all refsections if using mutiple \env{refsection} environments (see \secref{use:use:mlt}). +The \sty{biblatex} package uses one auxiliary \file{bcf} file only. Even if there are citation commands in a file included via \cmd{include}, you only need to run \biber on the main \file{bcf} file. All information \biber needs is in the \file{bcf} file, including information about all refsections if using multiple \env{refsection} environments (see \secref{use:use:mlt}). \paragraph{\bibtex} @@ -4761,7 +4761,7 @@ Expands to \prm{true} if the class would add the bibliography to the table of co \subsubsection{Usage with the Memoir Class} \label{use:cav:mem} -When using \sty{biblatex} with the \sty{memoir} class, most class facilites for adapting the bibliography have no effect. Use the corresponding facilities of this package instead (\secref{use:bib:bib, use:bib:hdg, use:bib:nts}). Instead of redefining \sty{memoir}'s \cmd{bibsection}, use the \opt{heading} option of \cmd{printbibliography} and \cmd{defbibheading} (\secref{use:bib:bib, use:bib:hdg}). Instead of \cmd{prebibhook} and \cmd{postbibhook}, use the \opt{prenote} and \opt{postnote} options of \cmd{printbibliography} and \cmd{defbibnote} (\secref{use:bib:bib, use:bib:nts}). All default headings are adapted at load-time such that they blend well with the default layout of this class. The default headings \texttt{bibliography} and \texttt{shorthands} (\secref{use:bib:hdg}) are also responsive to \sty{memoir}'s \cmd{bibintoc} and \cmd{nobibintoc} switches. The length register \len{bibitemsep} is used by \sty{biblatex} in a way similar to \sty{memoir} (\secref{use:fmt:len}). This section also introduces some additional length registers which correspond to \sty{memoir}'s \cmd{biblistextra}. Lastly, \cmd{setbiblabel} does not map to a single facility of the \sty{biblatex} package since the style of all labels in the bibliography is controlled by the bibliography style. See \secref{aut:bbx:env} in the author section of this manual for details. If the \sty{memoir} class is detected, \sty{biblatex} will also provide the following additional test which may be useful in custom heading definitions: +When using \sty{biblatex} with the \sty{memoir} class, most class facilities for adapting the bibliography have no effect. Use the corresponding facilities of this package instead (\secref{use:bib:bib, use:bib:hdg, use:bib:nts}). Instead of redefining \sty{memoir}'s \cmd{bibsection}, use the \opt{heading} option of \cmd{printbibliography} and \cmd{defbibheading} (\secref{use:bib:bib, use:bib:hdg}). Instead of \cmd{prebibhook} and \cmd{postbibhook}, use the \opt{prenote} and \opt{postnote} options of \cmd{printbibliography} and \cmd{defbibnote} (\secref{use:bib:bib, use:bib:nts}). All default headings are adapted at load-time such that they blend well with the default layout of this class. The default headings \texttt{bibliography} and \texttt{shorthands} (\secref{use:bib:hdg}) are also responsive to \sty{memoir}'s \cmd{bibintoc} and \cmd{nobibintoc} switches. The length register \len{bibitemsep} is used by \sty{biblatex} in a way similar to \sty{memoir} (\secref{use:fmt:len}). This section also introduces some additional length registers which correspond to \sty{memoir}'s \cmd{biblistextra}. Lastly, \cmd{setbiblabel} does not map to a single facility of the \sty{biblatex} package since the style of all labels in the bibliography is controlled by the bibliography style. See \secref{aut:bbx:env} in the author section of this manual for details. If the \sty{memoir} class is detected, \sty{biblatex} will also provide the following additional test which may be useful in custom heading definitions: \begin{ltxsyntax} @@ -4888,7 +4888,7 @@ The delimiters: 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 initals is also handled by the backend and may be customized by redefining the following three macros: +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: \begin{namedelims} a & \cmd{bibinitperiod} & Inserted by the backend after initials.\\ @@ -4935,7 +4935,7 @@ This part of the manual documents the author interface of the \sty{biblatex} pac \subsection{Overview} \label{aut:int} -Before we get to the commands and facilities provided by \sty{biblatex}, we will have a look at some of its fundamental concepts. The \sty{biblatex} package uses auxilliary files in a specia way. Most notably, the \file{bbl} file is used differently and when using \bibtex as the backend, there is only one \file{bst} file which implements a structured data interface rather than exporting printable data. With \latex's standard bibliographic facilities, a document includes any number of citation commands in the document body plus \cmd{bibliographystyle} and \cmd{bibliography}, usually towards the end of the document. The location of the former is arbitrary, the latter marks the spot where the list of references is to be printed: +Before we get to the commands and facilities provided by \sty{biblatex}, we will have a look at some of its fundamental concepts. The \sty{biblatex} package uses auxiliary files in a special way. Most notably, the \file{bbl} file is used differently and when using \bibtex as the backend, there is only one \file{bst} file which implements a structured data interface rather than exporting printable data. With \latex's standard bibliographic facilities, a document includes any number of citation commands in the document body plus \cmd{bibliographystyle} and \cmd{bibliography}, usually towards the end of the document. The location of the former is arbitrary, the latter marks the spot where the list of references is to be printed: \begin{ltxexample} \documentclass{...} @@ -5028,9 +5028,9 @@ In order to streamline the whole procedure, \sty{biblatex} essentially employs t \item Run \bin{latex}: The first step is similar to the traditional procedure described above: \cmd{bibstyle} and \cmd{bibdata} commands are written to the \file{aux} file (\bibtex backend) or \file{bcf} file (\biber backend), along with \cmd{citation} commands for all citations. We then wait for the backend to supply the required data. With \bibtex as a backend, since \sty{biblatex} uses a special \file{bst} file which implements its data interface on the \bibtex end, the \cmd{bibstyle} command is always |\bibstyle{biblatex}|. -\item Run \bin{biber} or \bin{bibtex}: The backend supplies those entries from the \file{bib} file which were requested by the \cmd{citation} commands in the auxilliary file. However, it does not write a printable bibliography to the \file{bbl} file, but rather a structured representation of the bibliographic data. Just like an \file{aux} file, this \file{bbl} file does not print anything when read in. It merely puts data in memory. +\item Run \bin{biber} or \bin{bibtex}: The backend supplies those entries from the \file{bib} file which were requested by the \cmd{citation} commands in the auxiliary file. However, it does not write a printable bibliography to the \file{bbl} file, but rather a structured representation of the bibliographic data. Just like an \file{aux} file, this \file{bbl} file does not print anything when read in. It merely puts data in memory. -\item Run \bin{latex}: Starting with the second run, the \file{bbl} file is processed right at the beginning of the document body, just like an \file{aux} file. From this point on, all bibliographic data is available in memory so that all citations can be printed right away.\footnote{If the \opt{defernumbers} package option is enabled \sty{biblatex} uses an alogrithm similar to the traditional procedure to generate numeric lables. In this case, the numbers are assigned as the bibliography is printed and then cycled through the backend auzilliary file. It will take an additional \latex run for them to be picked up in citations.} The citation commands have access to the complete bibliographic data, not only to a predefined label. The bibliography is generated from memory using the same data and may be filtered or split as required. +\item Run \bin{latex}: Starting with the second run, the \file{bbl} file is processed right at the beginning of the document body, just like an \file{aux} file. From this point on, all bibliographic data is available in memory so that all citations can be printed right away.\footnote{If the \opt{defernumbers} package option is enabled \sty{biblatex} uses an algorithm similar to the traditional procedure to generate numeric labels. In this case, the numbers are assigned as the bibliography is printed and then cycled through the backend auxiliary file. It will take an additional \latex run for them to be picked up in citations.} The citation commands have access to the complete bibliographic data, not only to a predefined label. The bibliography is generated from memory using the same data and may be filtered or split as required. \end{enumerate} @@ -5217,7 +5217,7 @@ At this point, there is still one piece missing: the formatting directives used \DeclareFieldFormat{title}{\emph{#1}} \end{lstlisting} % -List formats are slightly more complex. After splitting up the list into individual items, \sty{biblatex} will execute the formatting directive once for every item in the list. The item is passed to the directive as an argument. The separator to be inserted between the indivdual items in the list is also handled by the corresponding directive, hence we have to check whether we are in the middle of the list or at the end when inserting it. +List formats are slightly more complex. After splitting up the list into individual items, \sty{biblatex} will execute the formatting directive once for every item in the list. The item is passed to the directive as an argument. The separator to be inserted between the individual items in the list is also handled by the corresponding directive, hence we have to check whether we are in the middle of the list or at the end when inserting it. \begin{lstlisting}[style=latex]{} \DeclareListFormat{location}{% @@ -5241,7 +5241,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 indivdual 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} @@ -5279,7 +5279,7 @@ This field is special in that it is only available locally in name formatting di \fielditem{namehash}{string} -A hash string which uniquely identifies the \bibfield{labelname} list. This is useful for recurrence checks. For example, a citation style wich replaces recurrent authors or editors with a string like could save the \bibfield{namehash} field with \cmd{savefield} and use it in a comparison with \cmd{iffieldequals} later (see \secref{aut:aux:dat, aut:aux:tst}). The \bibfield{namehash} is derived from the truncated \bibfield{labelname} list, \ie it is responsive to \opt{maxnames} and \opt{minnames}. See also \bibfield{hash} and \bibfield{fullhash}. +A hash string which uniquely identifies the \bibfield{labelname} list. This is useful for recurrence checks. For example, a citation style which replaces recurrent authors or editors with a string like could save the \bibfield{namehash} field with \cmd{savefield} and use it in a comparison with \cmd{iffieldequals} later (see \secref{aut:aux:dat, aut:aux:tst}). The \bibfield{namehash} is derived from the truncated \bibfield{labelname} list, \ie it is responsive to \opt{maxnames} and \opt{minnames}. See also \bibfield{hash} and \bibfield{fullhash}. \fielditem{fullhash}{string} @@ -5725,7 +5725,7 @@ Note that name affixes are referred to as the of the name in the \ \item[\#8] The name affixes, given as initials. \end{argumentlist} % -If a certain part of a name is not available, the corresponding argument will be empty, hence you may use \cmd{ifblank} tests to check for the inidividual parts of a name. The name of the name list currently being processed is available to the \prm{code} as \cmd{currentname}. Note that the formatting directive also handles the punctuation to be inserted between separate names and between the individual parts of a name. You need to check whether you are in the middle of or at the end of the list, \ie whether \cnt{listcount} is smaller than or equal to \cnt{liststop}. See also \secref{use:cav:nam}. The starred variant of this command is similar to the regular version, except that all type-specific formats are cleared. +If a certain part of a name is not available, the corresponding argument will be empty, hence you may use \cmd{ifblank} tests to check for the individual parts of a name. The name of the name list currently being processed is available to the \prm{code} as \cmd{currentname}. Note that the formatting directive also handles the punctuation to be inserted between separate names and between the individual parts of a name. You need to check whether you are in the middle of or at the end of the list, \ie whether \cnt{listcount} is smaller than or equal to \cnt{liststop}. See also \secref{use:cav:nam}. The starred variant of this command is similar to the regular version, except that all type-specific formats are cleared. \cmditem{DeclareIndexFieldFormat}[entrytype, \dots]{format}{code} \cmditem*{DeclareIndexFieldFormat}*{format}{code} @@ -6129,12 +6129,14 @@ Validation against the data model means that after mapping your data sources int \item Whether the fields obey various constraints on their format which you specify \end{itemize} % -Redefining the data model can be done in several places. Style authors can create a \file{.dbx} file which contains the data model macros required and this will be loaded automatically when using the \sty{biblatex} package \opt{style} option by looking for a file named afer the style with a \file{.dbx} (just like the \file{.cbx} and \file{.bbx} files for a style). Alternatively, the name of the data model file can be different from the style name by specifying the name (without \file{.dbx} extension) to the package \opt{datamodel} option. After loading the style data model file, \sty{biblatex} then loads, if present, a users \file{biblatex-dm.cfg} which should be put somewhere \sty{biblatex} can find it, just like the main configuration file \sty{biblatex.cfg}. To summarise, the data model is determined by adding to the data model from each of these locations, in order:\\ +Redefining the data model can be done in several places. Style authors can create a \file{.dbx} file which contains the data model macros required and this will be loaded automatically when using the \sty{biblatex} package \opt{style} option by looking for a file named after the style with a \file{.dbx} extension (just like the \file{.cbx} and \file{.bbx} files for a style). If the \opt{style} option is not used but rather the \opt{citestyle} and \opt{bibstyle} options, then the package will try to load \file{.dbx} files called \file{.dbx} and \file{.dbx}. +Alternatively, the name of the data model file can be different from any of the style option names by specifying the name (without \file{.dbx} extension) to the package \opt{datamodel} option. After loading the style data model file, \sty{biblatex} then loads, if present, a users \file{biblatex-dm.cfg} which should be put somewhere \sty{biblatex} can find it, just like the main configuration file \sty{biblatex.cfg}. To summarise, the data model is determined by adding to the data model from each of these locations, in order:\\ \noindent\file{blx-dm.def}$\rightarrow$\\ \hspace*{1em}\file{.dbx} $\rightarrow$\\ \hspace*{2em}\file{