From c48ccf7d508e674e10d9771d333993da3a957589 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Mon, 7 Mar 2016 23:27:17 +0000 Subject: biblatex 3.3 (7mar16) git-svn-id: svn://tug.org/texlive/trunk@39966 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/latex/biblatex/RELEASE | 93 + Master/texmf-dist/doc/latex/biblatex/biblatex.pdf | Bin 1165440 -> 1284812 bytes Master/texmf-dist/doc/latex/biblatex/biblatex.tex | 1737 +++++++----- .../latex/biblatex/examples/01-introduction.tex | 1 + .../doc/latex/biblatex/examples/02-annotations.tex | 1 + .../biblatex/examples/03-localization-keys.tex | 1 + .../examples/10-references-per-section.tex | 1 + .../biblatex/examples/11-references-by-section.tex | 1 + .../biblatex/examples/12-references-by-segment.tex | 1 + .../biblatex/examples/13-references-by-keyword.tex | 1 + .../examples/14-references-by-category.tex | 1 + .../biblatex/examples/15-references-by-type.tex | 1 + .../biblatex/examples/16-numeric-prefixed-1.tex | 1 + .../biblatex/examples/17-numeric-prefixed-2.tex | 1 + .../latex/biblatex/examples/18-numeric-hybrid.tex | 1 + .../biblatex/examples/19-alphabetic-prefixed.tex | 1 + .../latex/biblatex/examples/20-indexing-single.tex | 1 + .../biblatex/examples/21-indexing-multiple.tex | 16 +- .../biblatex/examples/22-indexing-subentry.tex | 25 +- .../latex/biblatex/examples/30-style-numeric.tex | 1 + .../biblatex/examples/31-style-numeric-comp.tex | 1 + .../biblatex/examples/32-style-numeric-verb.tex | 1 + .../biblatex/examples/40-style-alphabetic.tex | 1 + .../biblatex/examples/41-style-alphabetic-verb.tex | 1 + .../examples/42-style-alphabetic-template.tex | 1 + .../biblatex/examples/50-style-authoryear.tex | 1 + .../biblatex/examples/51-style-authoryear-ibid.tex | 1 + .../biblatex/examples/52-style-authoryear-comp.tex | 1 + .../examples/53-style-authoryear-icomp.tex | 1 + .../biblatex/examples/60-style-authortitle.tex | 1 + .../examples/61-style-authortitle-ibid.tex | 1 + .../examples/62-style-authortitle-comp.tex | 1 + .../examples/63-style-authortitle-icomp.tex | 1 + .../examples/64-style-authortitle-terse.tex | 1 + .../examples/65-style-authortitle-tcomp.tex | 1 + .../examples/66-style-authortitle-ticomp.tex | 1 + .../latex/biblatex/examples/70-style-verbose.tex | 1 + .../biblatex/examples/71-style-verbose-ibid.tex | 1 + .../biblatex/examples/72-style-verbose-note.tex | 1 + .../biblatex/examples/73-style-verbose-inote.tex | 1 + .../biblatex/examples/74-style-verbose-trad1.tex | 1 + .../biblatex/examples/75-style-verbose-trad2.tex | 1 + .../biblatex/examples/76-style-verbose-trad3.tex | 1 + .../latex/biblatex/examples/80-style-reading.tex | 1 + .../doc/latex/biblatex/examples/81-style-draft.tex | 1 + .../doc/latex/biblatex/examples/82-style-debug.tex | 1 + .../latex/biblatex/examples/90-related-entries.tex | 5 +- .../latex/biblatex/examples/91-sorting-schemes.tex | 5 +- .../biblatex/examples/92-bibliographylists.tex | 9 +- .../doc/latex/biblatex/examples/93-nameparts.dbx | 1 + .../doc/latex/biblatex/examples/93-nameparts.tex | 66 + .../biblatex/examples/biblatex-examples.bltxml | 2851 ++++++++++++++++++++ 52 files changed, 4107 insertions(+), 742 deletions(-) create mode 100644 Master/texmf-dist/doc/latex/biblatex/examples/93-nameparts.dbx create mode 100644 Master/texmf-dist/doc/latex/biblatex/examples/93-nameparts.tex create mode 100644 Master/texmf-dist/doc/latex/biblatex/examples/biblatex-examples.bltxml (limited to 'Master/texmf-dist/doc/latex/biblatex') diff --git a/Master/texmf-dist/doc/latex/biblatex/RELEASE b/Master/texmf-dist/doc/latex/biblatex/RELEASE index f77b69cc67d..4bb203b278d 100644 --- a/Master/texmf-dist/doc/latex/biblatex/RELEASE +++ b/Master/texmf-dist/doc/latex/biblatex/RELEASE @@ -1,3 +1,96 @@ +RELEASE NOTES FOR VERSION 3.3 + +* Biber version 2.4 is required for biblatex 3.3 +* The \Declare*Option commands have a new optional argument when using + biber which declares the datatype of the option. It defaults to + "boolean" if not specified. If you define any custom options in your + style, you may want to specify the correct datatype (see docs). However, + it is unlikely that this will impact anything at the moment as this option + only used internally by biber for some checks. +* INCOMPATIBLE CHANGE - There have been major changes to the handling of + name lists in order to generalise name handling beyond the narrow + confines of the legacy bibtex name parts of "last, first, prefix, + suffix". These changes only apply when using biber as the backend and + mainly affect style authors. + * In general in macro names, "first" is now "given" and "last" is now "family": + + The option "firstinits" has been renamed to "giveninits" and the option "sortfirstinits" + to "sortgiveninits". The old names are available as legacy aliases. + Style authors using the internal toggles associated with these options will + need to change "first" to "given" in their names. + + Name formats and the \mkbibname* macros have been internally renamed by + replacing "first" with "given" and "last" with "family". There are aliases in place for the + older names. Please use the new names in any custom styles. + + * The most significant change concerns the definition of name formats. + Style authors will need to update any styles which use + \DeclareNameFormat or \DeclareIndexNameFormat which no longer accept + 8 arguments which are hard coded to the nameparts which bibtex + understands. These macros now take one argument which is a + comma-separated list which must be parsed with: + + \nameparts{#1}% + + All name formats should include this line, usually as the first line in + the format. Valid nameparts are now defined by the datamodel and the + default is compatible with standard bibtex with "last" renamed to + "family" and "first" renamed to "given". The default datamodel + declaration is: + + \DeclareDatamodelConstant[type=list]{nameparts}{prefix,family,suffix,given} + + This declaration automatically creates the \mkbibname macros and the + internal machinery for the \nameparts macro. After using the \nameparts macro + as described above, each namepart will be available in two macros with + the following name structure: + + \namepart + \nameparti + + The macro ending in "i" is the macro contain the namepart initials. + So, use of \nameparts{#1} in the default datamodel will result in these + macros being defined for use: + + \namepartprefix + \namepartprefixi + \namepartfamily + \namepartfamilyi + \namepartsuffix + \namepartsuffixi + \namepartgiven + \namepartgiveni + + As a further example, the name format: + + \DeclareNameFormat{first-last}{% + \iffirstinits + {\usebibmacro{name:first-last}{#1}{#4}{#5}{#7}} + {\usebibmacro{name:first-last}{#1}{#3}{#5}{#7}}% + \usebibmacro{name:andothers}} + + is now: + + \DeclareNameAlias{first-last}{given-family}% legacy alias + \DeclareNameFormat{given-family}{% + \nameparts{#1}% + \ifgiveninits + {\usebibmacro{name:given-family} + {\namepartfamily} + {\namepartgiveni} + {\namepartprefix} + {\namepartsuffix}} + {\usebibmacro{name:given-family} + {\namepartfamily} + {\namepartgiven} + {\namepartprefix} + {\namepartsuffix}}% + \usebibmacro{name:andothers}} + + See the example 93-nameparts.tex example file for an example of + defining and using a custom namepart, which is now possible due to + these changes. + RELEASE NOTES FOR VERSION 3.2 * Biber version 2.3 is required for biblatex 3.2 diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf b/Master/texmf-dist/doc/latex/biblatex/biblatex.pdf index 1dbd731c296..a4762be524d 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 2fdbbe39971..6ed0af92e75 100644 --- a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex +++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex @@ -1,7 +1,7 @@ \documentclass{ltxdockit}[2011/03/25] \usepackage{btxdockit} \usepackage{fontspec} -\setmonofont[Ligatures=TeX]{Courier New} +\setmonofont{Courier New} \setmainfont[Ligatures=TeX]{Linux Libertine O} \setsansfont[Ligatures=TeX]{Linux Biolinum O} \usepackage[american]{babel} @@ -13,8 +13,16 @@ \usepackage{pifont} \usepackage{microtype} \usepackage{typearea} +\usepackage{mdframed} \areaset[current]{370pt}{700pt} -\lstset{basicstyle=\ttfamily,keepspaces=true} +\lstset{ + basicstyle=\ttfamily, + keepspaces=true, + upquote=true, + frame=single, + breaklines=true, + postbreak=\raisebox{0ex}[0ex][0ex]{\ensuremath{\color{red}\hookrightarrow\space}} +} \KOMAoptions{numbers=noenddot} \addtokomafont{title}{\sffamily} \addtokomafont{paragraph}{\spotcolor} @@ -38,7 +46,9 @@ \MakeShortVerb{\|} \newcommand*{\biber}{Biber\xspace} -\newcommand*{\biblatex}{Biblatex\xspace} +\newcommand*{\biblatex}{BibLaTeX\xspace} +\newcommand*{\biblatexml}{BibLaTeXML\xspace} +\newcommand*{\ris}{RIS\xspace} \newcommand*{\biblatexhome}{http://sourceforge.net/projects/biblatex/} \newcommand*{\biblatexctan}{% http://www.ctan.org/tex-archive/macros/latex/contrib/biblatex/} @@ -49,8 +59,8 @@ url={\biblatexhome}, author={Philipp Lehman \\(with Philip Kime, Audrey Boruvka and Joseph Wright)}, email={}, - revision={3.2}, - date={27/12/2015}} + revision={3.4}, + date={//2016}} \hypersetup{% pdftitle={The \biblatex Package}, @@ -677,9 +687,18 @@ In datasources such as a \file{bib} file, all bibliographic data is specified in \begin{description} -\item[Name lists] are parsed and split up into the individual items at the \texttt{and} delimiter. Each item in the list is then dissected into four name components: the first name, the name prefix (von, van, of, da, de, della, \dots), the last name, and the name suffix (junior, senior, \dots). Name lists may be truncated in the \file{bib} file with the keyword <\texttt{and others}>. Typical examples of name lists are \bibfield{author} and \bibfield{editor}. +\item[Name lists] are parsed and split up into the individual items at the \texttt{and} delimiter. Each item in the list is then dissected into four name components: the given name, the name prefix (von, van, of, da, de, della, \dots), the family name, and the name suffix (junior, senior, \dots). Name lists may be truncated in the \file{bib} file with the keyword <\texttt{and others}>. Typical examples of name lists are \bibfield{author} and \bibfield{editor}. + +\BiberOnlyMark With \biber, name list fields automatically have an \cmd{ifuse*} test created as per the name lists in the default data model (see \secref{aut:aux:tst}). They are also automatically have a \opt{ifuse*} option created which controls labelling and sorting behaviour with the name (see \secref{use:opt:bib:hyb}). \biber supports a customisable list of name parts but current this is defined to be the same set of parts as supported by \bibtex: + +\begin{itemize} +\item Family name (also known as part) +\item Given name (also known as part) +\item Name prefix (also known as part) +\item Name suffix (also known as part) +\end{itemize} -\BiberOnlyMark With \biber, name list fields automatically have an \cmd{ifuse*} test created as per the name lists in the default data model (see \secref{aut:aux:tst}). They are also automatically have a \opt{ifuse*} option created which controls labelling and sorting behaviour with the name (see \secref{use:opt:bib:hyb}). +The supported list of name parts is defined as a constant list in the default data model using the \cmd{DeclareDatamodelConstant} command (see \ref{aut:ctm:dm}). However, it is not enough to simply add to this list in order to add support for another name part as name parts typically have to be hard coded into bibliography drivers and the backend processing. This constant is used as much as possible and is intended as a basis for future generalisation and extension. \item[Literal lists] are parsed and split up into the individual items at the \texttt{and} delimiter but not dissected further. Literal lists may be truncated in the \file{bib} file with the keyword <\texttt{and others}>. There are two subtypes: @@ -1192,11 +1211,11 @@ langidopts = {variant=british}, % would wrap the bibliography entry in: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \english[variant=british] ... \endenglish -\end{lstlisting} +\end{ltxexample} % \fielditem{ids}{separated list of entrykeys\BiberOnlyMark} @@ -1831,15 +1850,15 @@ Not only \bibtex, \latex needs to know about the encoding as well. See \secref{b 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]{} +\begin{ltxexample} \usepackage[backend=biber,sortlocale=de]{biblatex} -\end{lstlisting} +\end{ltxexample} % or if you are using german as the main document language via Babel or Polyglossia: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[backend=biber,sortlocale=auto]{biblatex} -\end{lstlisting} +\end{ltxexample} % This will make \biblatex pass the Babel/Polyglossia main document language as the locale which \biber will map into a suitable default locale. \biber @@ -1861,56 +1880,56 @@ When using a non-Ascii encoding in the \file{bib} file, it is important to under \item Ascii notation in both the \file{tex} and the \file{bib} file with \pdftex or traditional \tex (this will work with \bibtex, \file{bibtex8}, and \biber): -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage{biblatex} -\end{lstlisting} +\end{ltxexample} \item Latin\,1 encoding (\acr{ISO}-8859-1) in the \file{tex} file, Ascii notation in the \file{bib} file with \pdftex or traditional \tex (\bibtex, \file{bibtex8}, \biber): -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[latin1]{inputenc} \usepackage[bibencoding=ascii]{biblatex} -\end{lstlisting} +\end{ltxexample} \item Latin\,9 encoding (\acr{ISO}-8859-15) in both the \file{tex} and the \file{bib} file with \pdftex or traditional \tex (\file{bibtex8}, \biber): -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[latin9]{inputenc} \usepackage[bibencoding=auto]{biblatex} -\end{lstlisting} +\end{ltxexample} % Since \kvopt{bibencoding}{auto} is the default setting, the option is omissible. The following setup will have the same effect: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[latin9]{inputenc} \usepackage{biblatex} -\end{lstlisting} +\end{ltxexample} \item \utf encoding in the \file{tex} file, Latin\,1 (\acr{ISO}-8859-1) in the \file{bib} file with \pdftex or traditional \tex (\file{bibtex8}, \biber): -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[utf8]{inputenc} \usepackage[bibencoding=latin1]{biblatex} -\end{lstlisting} +\end{ltxexample} The same scenario with \xetex or \luatex in native \utf mode: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[bibencoding=latin1]{biblatex} -\end{lstlisting} +\end{ltxexample} \item Using \utf encoding in both the \file{tex} and the \file{bib} file is not possible with traditional \bibtex or \bin{bibtex8} since neither of them is capable of handling \utf. Unless you switch to \biber, you need to use an 8-bit encoding such as Latin\,1 (see above) or resort to Ascii notation in this case: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[utf8]{inputenc} \usepackage[bibencoding=ascii]{biblatex} -\end{lstlisting} +\end{ltxexample} The same scenario with \xetex or \luatex in native \utf mode: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[bibencoding=ascii]{biblatex} -\end{lstlisting} +\end{ltxexample} \end{itemize} @@ -1920,30 +1939,30 @@ The same scenario with \xetex or \luatex in native \utf mode: \item Transparent \utf workflow, \ie \utf encoding in both the \file{tex} and the \file{bib} file with \pdftex or traditional \tex: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[utf8]{inputenc} \usepackage[bibencoding=auto]{biblatex} -\end{lstlisting} +\end{ltxexample} % Since \kvopt{bibencoding}{auto} is the default setting, the option is omissible: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[utf8]{inputenc} \usepackage{biblatex} -\end{lstlisting} +\end{ltxexample} The same scenario with \xetex or \luatex in native \utf mode: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage{biblatex} -\end{lstlisting} +\end{ltxexample} \item It is even possible to combine an 8-bit encoded \file{tex} file with \utf encoding in the \file{bib} file, provided that all characters in the \file{bib} file are also covered by the selected 8-bit encoding: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[latin1]{inputenc} \usepackage[bibencoding=utf8]{biblatex} -\end{lstlisting} +\end{ltxexample} \end{itemize} @@ -1953,10 +1972,10 @@ Some workarounds may be required when using traditional \tex or \pdftex with \ut \item If you are affected by this problem, try setting the \opt{safeinputenc} option: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \usepackage[utf8]{inputenc} \usepackage[safeinputenc]{biblatex} -\end{lstlisting} +\end{ltxexample} % If this option is enabled, \biblatex will ignore \sty{inputenc}'s \opt{utf8} option and use Ascii. \biber will then try to convert the \file{bib} data to Ascii notation. For example, it will convert \texttt{\k{S}} to |\k{S}|. This option is similar to setting \kvopt{texencoding}{ascii} but will only take effect in this specific scenario (\sty{inputenc}\slash \sty{inputenx} with \utf). This workaround takes advantage of the fact that both Unicode and the \utf transport encoding are backwards compatible with Ascii. @@ -2452,7 +2471,7 @@ This option controls whether \bibfield{eprint} information is printed. \paragraph{Internal} \label{use:opt:pre:int} -The default settings of the following preamble options are controlled by bibliography and citation styles. Apart from the \opt{pagetracker} and \opt{firstinits} options, which you may want to adapt, there is normally no need to set them explicitly. +The default settings of the following preamble options are controlled by bibliography and citation styles. Apart from the \opt{pagetracker} and \opt{giveninits} options, which you may want to adapt, there is normally no need to set them explicitly. \begin{optionlist} @@ -2557,13 +2576,13 @@ This option controls the parenthesis tracker which keeps track of nested parenth The maximum permitted nesting level of parentheses and brackets. If parentheses and brackets are nested deeper than this value, \biblatex will issue errors. -\boolitem[false]{firstinits} +\boolitem[false]{giveninits} -When enabled, all first and middle names will be rendered as initials. The option will affect the \cmd{iffirstinits} test from \secref{aut:aux:tst}. +When enabled, all first and middle names will be rendered as initials. The option will affect the \cmd{ifgiveninits} test from \secref{aut:aux:tst}. -\boolitem[false]{sortfirstinits} +\boolitem[false]{sortgiveninits} -When enabled, sorting names will only use their initials. \BiberOnlyMark This is separate from \opt{firstinits} in case users want to show only inits but sort on full names, for example. +When enabled, sorting names will only use their initials. \BiberOnlyMark This is separate from \opt{giveninits} in case users want to show only inits but sort on full names, for example. \boolitem[false]{terseinits} @@ -2698,10 +2717,11 @@ With the standard styles, the \bibfield{translator} is printed after the title b As per \opt{useauthor}, \opt{useeditor} and \opt{usetranslator}, all name lists defined in the data model have an option controlling their behaviour in sorting and labelling automatically defined. Global, per-type and per-entry options called $>are automatically created. + \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, \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. +\BiberOnlyMark With \biber, this option is also settable on a per-type scope. With \biblatexml datasources, this is settable on per-namelist and per-name scopes. \optitem{indexing}{\opt{true}, \opt{false}, \opt{cite}, \opt{bib}} @@ -2727,8 +2747,7 @@ If this option is enabled, the entry is excluded from the list of shorthands. It \boolitem[false]{skipbiblist}[\BiberOnly] -This is the same as the \opt{skiplos} option when using the \bibtex backend. It is renamed for \biber to be consistent with the more generalised bibliography list functionality See \secref{use:bib:biblist}. -If this option is enabled, the entry is excluded from the list of shorthands. It is still included in the bibliography and it may also be cited by shorthand. +This is the same as the \opt{skiplos} option when using the \bibtex backend. It is renamed for \biber to be consistent with the more generalised bibliography list functionality, see \secref{use:bib:biblist}. If this option is enabled, the entry is excluded from and bibliography lists. It is still included in the bibliography and it may also be cited by shorthand etc. This option is also settable on a per-type basis. \boolitem[false]{skiplab} @@ -3022,12 +3041,12 @@ Using special fields such as \bibfield{sortkey}, \bibfield{sortname}, or \bibfie Adds a \prm{resource}, such as a \file{.bib} file, to the default resource list. This command is only available in the preamble. It replaces the \cmd{bibliography} legacy command. Note that files must be specified with their full name, including the extension. Do not omit the \file{.bib} extension from the filename. Also note that the \prm{resource} is a single resource. Invoke \cmd{addbibresource} multiple times to add more resources, for example: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \addbibresource{bibfile1.bib} \addbibresource{bibfile2.bib} \addbibresource[location=remote]{http://www.citeulike.org/bibtex/group/9517} \addbibresource[location=remote,label=lan]{ftp://192.168.1.57/~user/file.bib} -\end{lstlisting} +\end{ltxexample} % Since the \prm{resource} string is read in a verbatim-like mode, it may contain arbitrary characters. The only restriction is that any curly braces must be balanced. The following \prm{options} are available: @@ -3049,15 +3068,13 @@ The type of resource. Currently, the only supported type is \texttt{file}. The data type (format) of the resource. The following formats are currently supported: -\begin{valuelist}[zoterordfxml] +\begin{valuelist} \item[bibtex] \bibtex format. -\item[ris]\BiberOnlyMark Research Information Systems (\acr{RIS}) format.\fnurl{http://en.wikipedia.org/wiki/RIS_(file_format)} Note that an \texttt{ID} tag is required in all \acr{RIS} records. The \texttt{ID} value corresponds to the entry key. Support for this format is experimental. - -\item[zoterordfxml]\BiberOnlyMark Zotero \acr{RDF}/\acr{XML} format. Support for this format is experimental. Refer to the \biber manual for details. +\item[biblatexml]\BiberOnlyMark Experimental XML format for \biblatex. See \secref{apx:biblatexml}. -\item[endnotexml]\BiberOnlyMark EndNote \acr{XML} format. Support for this format is experimental. Refer to the \biber manual for details. +\item[ris]\BiberOnlyMark Research Information Systems (\acr{RIS}) format.\fnurl{http://en.wikipedia.org/wiki/RIS_(file_format)} Note that an \texttt{ID} tag is required in all \acr{RIS} records. The \texttt{ID} value corresponds to the entry key. Support for this format is experimental. \end{valuelist} @@ -3235,9 +3252,9 @@ In terms of sorting the list, the default is to sort use the sorting scheme name The most common bibliography list is a list of shorthand abbreviations for certain entries and so this has a convenience alias \cmd{printshorthands[\dots]} for backwards compatibility which is defined as: -\begin{lstlisting}[style=latex]{} +\begin{ltxexample} \printbiblist[...]{shorthand} -\end{lstlisting} +\end{ltxexample} \biblatex provides automatic support for data source fields in the default data model marked as