biblatex 1.0 (20nov10)

git-svn-id: svn://tug.org/texlive/trunk@20519 c570f23f-e606-0410-a88d-b1316a301751

1 files changed, 84 insertions, 58 deletions

diff --git a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
index bdc2dad4fe6..ef6c7e178c7 100644
--- a/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
+++ b/Master/texmf-dist/doc/latex/biblatex/biblatex.tex
@@ -1,5 +1,5 @@
-% $Id: biblatex.tex,v 0.9e 2010/10/09 16:39:36 lehman beta $
-\documentclass{ltxdockit}[2010/09/26]
+% $Id: biblatex.tex,v 1.0 2010/11/19 16:16:35 lehman stable $
+\documentclass{ltxdockit}[2010/11/19]
 \usepackage{btxdockit}
 \usepackage[latin9]{inputenc}
 \usepackage[american]{babel}
@@ -11,10 +11,10 @@
 \MakeAutoQuote*{<}{>}
 \MakeShortVerb{\|}
 
-\rcsid{$Id: biblatex.tex,v 0.9e 2010/10/09 16:39:36 lehman beta $}
+\rcsid{$Id: biblatex.tex,v 1.0 2010/11/19 16:16:35 lehman stable $}
 
 \newcommand*{\BiblatexHome}{http://sourceforge.net/projects/biblatex/}
-\newcommand*{\BiblatexOnCTAN}{http://www.ctan.org/tex-archive/macros/latex/exptl/biblatex/}
+\newcommand*{\BiblatexOnCTAN}{http://www.ctan.org/tex-archive/macros/latex/contrib/biblatex/}
 
 \titlepage{%
   title={The \sty{biblatex} Package},
@@ -56,7 +56,10 @@
 
 \setcounter{secnumdepth}{4}
 
-% hyphenation
+\newrobustcmd*{\BiberOnly}{%
+  \textcolor{spot}{Biber only}}
+\newrobustcmd*{\BiberOnlyMark}{%
+  \leavevmode\marginpar{\BiberOnly}}
 
 \hyphenation{%
   star-red
@@ -100,8 +103,9 @@ Alexander van Loon (Dutch),
 Apostolos Syropoulos (Greek),
 Hannu Väisänen (Finnish),
 Prokopis (Greek),
-Mateus Araújo (Brazilian).
-
+Mateus Araújo (Brazilian),
+Andrea Marchitelli (Italian).
+ 
 \subsection{Prerequisites}
 \label{int:pre}
 
@@ -131,7 +135,7 @@ This \latex package, which is also loaded automatically, provides a frontend for
 
 \end{marglist}
 
-Apart from the above resources, \sty{biblatex} also requires the standard \latex packages \sty{keyval} and \sty{ifthen} as well as the \sty{url} package. These package are included in all common \tex distributions and will be loaded automatically. If the \opt{bibencoding} package option is enabled, the \sty{inputenc} package is required in addition to that. Note that \sty{inputenc} is not loaded automatically.
+Apart from the above resources, \sty{biblatex} also requires the standard \latex packages \sty{keyval} and \sty{ifthen} as well as the \sty{url} package. These package are included in all common \tex distributions and will be loaded automatically.
 
 \subsubsection{Recommended Packages}
 \label{int:pre:rec}
@@ -229,7 +233,7 @@ The \sty{natbib} package supports numeric and author"=year citation schemes, inc
 The \sty{splitbib} package provides support for bibliographies subdivided by topic. See \sty{bibtopic}.
 
 \item[ucs]
-The \sty{ucs} package provides support for \acr{UTF-8} encoded input. Either use \sty{inputenc}'s standard \file{utf8} module or a Unicode enabled engine such as \xelatex instead.
+The \sty{ucs} package provides support for \acr{UTF-8} encoded input. Either use \sty{inputenc}'s standard \file{utf8} module or a Unicode enabled engine such as \xetex or \luatex instead.
 
 \end{marglist}
 
@@ -1507,7 +1511,7 @@ 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>. For example, a name like <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},
@@ -1520,15 +1524,15 @@ author     = {Ba<<ß>>mann, Paul},
 sortname   = {Ba<<sszz>>mann, Paul},
 \end{lstlisting}
 %
-Not only \bibtex, \tex needs to know about the encoding as well. When using non"=Ascii characters in a \file{bib} file, load the \sty{inputenc} package and specify the encoding as usual. The \sty{biblatex} package is also capable of handling conflicting encodings in \file{tex} and \file{bib} files, provided that you specify the encoding of the \file{bib} file with the \opt{bibencoding} package option. See \secref{bib:cav:enc:enc} for details.
+Not only \bibtex, \latex needs to know about the encoding as well. See \secref{bib:cav:enc:enc} on how to specify encodings.
 
 \paragraph{Biber}
-Biber can handle Ascii notation, 8-bit encodings such as Latin\,1, and \acr{UTF-8}. 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 in the process of being added.\fnurl{http://cldr.unicode.org/} The bottom line is that Biber will deliver sorting results 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} in a contemporary text processing environment is of a very general nature and not limited to the lack of \utf support.\fnurl{http://unicode.org/reports/tr10/#Common_Misperceptions}
+Biber handles Ascii, 8-bit encodings such as Latin\,1, and \acr{UTF-8}. 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 in the process of being added.\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}
 
-Implementing Unicode includes much more than handling \utf input. Unicode is a very complex standard covering more than its most well known part, the Unicode character encoding and transport encodings such as \utf. It also covers aspects such as string collation which are 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_DE]{biblatex}
+\usepackage[backend=biber,sortlocale=de]{biblatex}
 \end{lstlisting}
 %
 If the language of the document corresponds to the main locale of the operating system, \opt{sortlocale} is
@@ -1536,41 +1540,46 @@ omissible as Biber will detect the locale settings of the environment automatica
 
 \paragraph{Specifying Encodings}
 \label{bib:cav:enc:enc}
-When using a non-Ascii encoding in the \file{bib} file, it is important to understand what \sty{biblatex} can do for you and what may require manual intervention. The package takes care of the \latex side, \ie it ensures that the data imported from the \file{bbl} file is interpreted correctly, provided that the \opt{bibencoding} package option is set properly. Depending on the backend, the \bibtex side may demand attention, too. When using \bin{bibtex8}, you need to supply \bin{bibtex8} with a matching \file{csf} file as it needs to know about the encoding of the \file{bib} file to be able to alphabetize the entries correctly. Unfortunately, there is no way for \sty{biblatex} to pass this information to \bin{bibtex8} automatically. The only way is setting the |--csfile| switch on the command line when executing \bin{bibtex8}. When using Biber, this happends automatically and no further steps, apart from setting the \opt{bibencoding} option, are required.
-
-Here are a few typical usage scenarios along with the relevant lines from the document preamble:
+When using a non-Ascii encoding in the \file{bib} file, it is important to understand what \sty{biblatex} can do for you and what may require manual intervention. The package takes care of the \latex side, \ie it ensures that the data imported from the \file{bbl} file is interpreted correctly, provided that the \opt{bibencoding} package option is set properly. Depending on the backend, the \bibtex side may demand attention, too. When using \bin{bibtex8}, you need to supply \bin{bibtex8} with a matching \file{csf} file as it needs to know about the encoding of the \file{bib} file to be able to alphabetize the entries correctly. Unfortunately, there is no way for \sty{biblatex} to pass this information to \bin{bibtex8} automatically. The only way is setting its |--csfile| option on the command line when running \bin{bibtex8}. When using Biber, all of this is handled automatically and no further steps, apart from setting the \opt{bibencoding} option in certain cases, are required. Here are a few typical usage scenarios along with the relevant lines from the document preamble:
 
 \begin{itemize}
 \setlength{\itemsep}{0pt}
 
-\item Ascii notation in both the \file{tex} and the \file{bib} file (this will work with \bibtex, \file{bibtex8}, and Biber):
+\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]{}
 \usepackage{biblatex}
 \end{lstlisting}
 
-\item Latin\,1 encoding (\acr{ISO}-8859-1) in the \file{tex} file, Ascii notation in the \file{bib} file (\bibtex, \file{bibtex8}, Biber):
+\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]{}
 \usepackage[latin1]{inputenc}
-\usepackage{biblatex}
+\usepackage[bibencoding=ascii]{biblatex}
 \end{lstlisting}
 
-\item Latin\,9 encoding (\acr{ISO}-8859-15) in both the \file{tex} and the \file{bib} file (\file{bibtex8}, Biber):
+\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]{}
 \usepackage[latin9]{inputenc}
-\usepackage[bibencoding=inputenc]{biblatex}
+\usepackage[bibencoding=auto]{biblatex}
+\end{lstlisting}
+%
+Since \kvopt{bibencoding}{auto} is the default setting, the option is omissible. The following setup will have the same effect:
+
+\begin{lstlisting}[style=latex]{}
+\usepackage[latin9]{inputenc}
+\usepackage{biblatex}
 \end{lstlisting}
 
-\item \acr{UTF-8} encoding in the \file{tex} file, Latin\,1 (\acr{ISO}-8859-1) in the \file{bib} file (\file{bibtex8}, Biber):
+\item \acr{UTF-8} 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]{}
 \usepackage[utf8]{inputenc}
 \usepackage[bibencoding=latin1]{biblatex}
 \end{lstlisting}
 
-\item Same scenario with Xe\tex or Lua\tex in native \acr{UTF-8} mode:
+The same scenario with \xetex or \luatex in native \acr{UTF-8} mode:
 
 \begin{lstlisting}[style=latex]{}
 \usepackage[bibencoding=latin1]{biblatex}
@@ -1580,35 +1589,42 @@ Here are a few typical usage scenarios along with the relevant lines from the do
 
 \begin{lstlisting}[style=latex]{}
 \usepackage[utf8]{inputenc}
-\usepackage{biblatex}
+\usepackage[bibencoding=ascii]{biblatex}
 \end{lstlisting}
 
-\item Same scenario with Xe\tex or Lua\tex in native \acr{UTF-8} mode:
+The same scenario with \xetex or \luatex in native \acr{UTF-8} mode:
 
 \begin{lstlisting}[style=latex]{}
-\usepackage{biblatex}
+\usepackage[bibencoding=ascii]{biblatex}
 \end{lstlisting}
 
 \end{itemize}
 
-Biber can handle Ascii notation, 8-bit encodings such as Latin\,1, and \acr{UTF-8}. It is also capable of reencoding the \file{bib} data on the fly (replacing the somewhat less robust macro-level reencoding routine of \sty{biblatex}). This will happen automatically if required, provided that you specify the encoding of the \file{bib} files properly. In addition to the scenarios discussed above, Biber can also handle the following cases:
+Biber can handle Ascii notation, 8-bit encodings such as Latin\,1, and \acr{UTF-8}. It is also capable of reencoding the \file{bib} data on the fly (replacing the limited macro-level reencoding feature of \sty{biblatex}). This will happen automatically if required, provided that you specify the encoding of the \file{bib} files properly. In addition to the scenarios discussed above, Biber can also handle the following cases:
 
 \begin{itemize}
 
-\item Transparent \acr{UTF-8} workflow, \ie \acr{UTF-8} encoding in both the \file{tex} and the \file{bib} file:
+\item Transparent \acr{UTF-8} workflow, \ie \acr{UTF-8} encoding in both the \file{tex} and the \file{bib} file with \pdftex or traditional \tex:
 
 \begin{lstlisting}[style=latex]{}
 \usepackage[utf8]{inputenc}
-\usepackage[bibencoding=inputenc]{biblatex}
+\usepackage[bibencoding=auto]{biblatex}
 \end{lstlisting}
+%
+Since \kvopt{bibencoding}{auto} is the default setting, the option is omissible:
 
-\item Same scenario with Xe\tex or Lua\tex in native \acr{UTF-8} mode:
+\begin{lstlisting}[style=latex]{}
+\usepackage[utf8]{inputenc}
+\usepackage{biblatex}
+\end{lstlisting}
+
+The same scenario with \xetex or \luatex in native \acr{UTF-8} mode:
 
 \begin{lstlisting}[style=latex]{}
-\usepackage[bibencoding=inputenc]{biblatex}
+\usepackage{biblatex}
 \end{lstlisting}
 
-\item It is even possible to combine an 8-bit-encoded \file{tex} file with \acr{UTF-8} encoding in the \file{bib} file, provided that all characters in the \file{bib} file are also available in the selected 8-bit encoding:
+\item It is even possible to combine an 8-bit encoded \file{tex} file with \acr{UTF-8} 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]{}
 \usepackage[latin1]{inputenc}
@@ -1689,14 +1705,13 @@ Please refer to \secref{use:srt} for an in"=depth explanation of the above sorti
 
 Whether to sort the bibliography and the list of shorthands in a case"=sensitive way. Note that case"=sensitive sorting is only supported by the \bin{bibtex8} and Biber backends. Sorting is always case"=insensitive with legacy \bibtex. See the \opt{backend} option for details.
 
-\boolitem[true]{sortupper}
+\boolitem[true]{sortupper}[\BiberOnly]
 
-This option is specific to Biber and corresponds to Biber's |--sortupper| command-line option. It has no effect with any other backend. If enabled, the bibliography is sorted in <uppercase before lowercase> order. Disabling this option means <lowercase before uppercase> order.
+This option corresponds to Biber's |--sortupper| command-line option. It has no effect with any other backend. If enabled, the bibliography is sorted in <uppercase before lowercase> order. Disabling this option means <lowercase before uppercase> order.
 
-\optitem{sortlocale}{\prm{locale}}
+\optitem{sortlocale}{\prm{locale}}[\BiberOnly]
 
-This option is specific to Biber and corresponds to Biber's |--sortlocale| command-line option.
-It has no effect with any other backend. If set, it specifies the locale to be used for sorting. Note that, while \sty{biblatex} provides no default value for this option, Biber will inherit the locale settings from the environment if no locale has been specified explicitly.
+This option corresponds to Biber's |--sortlocale| command-line option. It has no effect with any other backend. If set, it specifies the locale to be used for sorting. While \sty{biblatex} provides no default value for this option, Biber will inherit the locale settings from the environment if no locale has been specified explicitly.
 
 \optitem[los]{sortlos}{\opt{bib}, \opt{los}}
 
@@ -1863,6 +1878,7 @@ All styles support both Arabic and Roman numerals. In order to avoid potentially
 This option controls how back references to \bibtype{set} entires and their members are handled. The following options are available:
 
 \begin{valuelist}
+
 \item[setonly] All back references are added to the \bibtype{set} entry. The \bibfield{pageref} lists of set members remain blank.
 
 \item[memonly] References to set members are added to the respective member. References to the \bibtype{set} entry are added to all members. The \bibfield{pageref} list of the \bibtype{set} entry remains blank.
@@ -1997,45 +2013,45 @@ Path selector for arXiv links. If hyperlink support is enabled, this option cont
 
 See \secref{use:use:epr} for details on support for arXiv and electronic publishing information.
 
-\optitem[bibtex]{backend}{\opt{bibtex}, \opt{bibtex8}, \opt{biber}}
+\optitem[bibtex]{backend}{\opt{bibtex}, \opt{bibtex8}, \opt{bibtexu}, \opt{biber}}
 
 Specifies the database backend. The following backends are supported:
 
 \begin{valuelist}
 
-\item[bibtex] Legacy \bibtex. Traditional \bibtex supports Ascii encoding only. Sorting is always case"=insensitive, regardless of the \opt{sortcase} option.
+\item[bibtex] Legacy \bibtex. Traditional \bibtex supports Ascii encoding only. Sorting is always case"=insensitive.
+
+\item[bibtex8] \bin{bibtex8}, the 8-bit implementation of \bibtex, supports Ascii and 8-bit encodings such as Latin~1. Depending on the \file{csf} file, case"=sensitive sorting may be supported.
 
-\item[bibtex8] \bin{bibtex8}, the 8-bit implementation of \bibtex, supports Ascii and 8-bit encodings, such as Latin~1. Depending on the \opt{sortcase} option, case"=sensitive sorting is supported.
+\item[bibtexu] \bin{bibtexu} is a Unicode-enabled implementation of \bibtex which supports \utf. Note that \bin{bibtexu} is not actively supported by \sty{biblatex} and has not been tested as backend in any way. Biber is the recommended backend.
 
-\item[biber] Biber, the next"=generation database backend of \sty{biblatex}, supports Ascii, 8-bit encodings, and \utf. Depending on the \opt{sortcase} option, case"=sensitive sorting is supported.
+\item[biber] Biber, the next"=generation backend of \sty{biblatex}, supports Ascii, 8-bit encodings, \utf, on-the-fly reencoding, locale"=specific sorting, and many other features. Locale"=specific sorting, case"=sensitive sorting, and upper\slash lowercase precedence are controlled by the options \opt{sortlocale}, \opt{sortcase}, and \opt{sortupper}, respectively.
 
 \end{valuelist}
 
 This option will typically be set permanently in the configuration file, see \secref{use:cfg} for details. Also see \secref{bib:cav:enc} for further instructions concerning the encoding of \file{bib} files.
 
-\boolitem[true]{bibwarn}
+\optitem[auto]{bibencoding}{\opt{auto}, \prm{encoding}}
 
-By default, \sty{biblatex} will report warnings issued by the backend concerning the data in the \file{bib} file as \latex warnings. Use this option to suppress such warnings.
+Specifies the encoding of the \file{bib} files. The following choices are available:
 
-\intitem[2]{mincrossrefs}
-
-Sets the minimum number of cross references to \prm{integer} when requesting a \bibtex run.\footnote{If an entry which is cross-referenced by other entries in the \file{bib} file hits this threshold, it is included in the bibliography even if it has not been cited explicitly. This is a standard feature of \bibtex and not specific to \sty{biblatex}. See the description of the \bibfield{crossref} field in \secref{bib:fld:spc} for further information.} Note that this package option merely affects the format of certain requests written to the transcript file. It will not have any effect if the editor or compiler script launching \bibtex does not include dedicated \sty{biblatex} support or if \bibtex is manually launched from the command"=line.\footnote{As of this writing, no \latex editors or compiler scripts with dedicated \sty{biblatex} support are known, but this will hopefully change in the future.} See \secref{bib:cav:ide} for details. This option also affects the handling of the \bibfield{xref} field. See the field description in \secref{bib:fld:spc} as well as \secref{bib:cav:ref} for details.
+\begin{valuelist}
 
-\optitem[ascii]{bibencoding}{\opt{ascii}, \opt{inputenc}, \prm{encoding}}
+\item[auto] Use this option if the workflow is transparent, \ie if the encoding of the \file{bib} file is identical to the encoding of the \file{tex} file. The \sty{biblatex} package will try to auto-detect the encoding of the \file{tex} file. If the \sty{inputenc}\slash\sty{inputenx}\slash\sty{luainputenc} package is available, \sty{biblatex} will get the main encoding from that package. If not, it assumes \texttt{utf8} if \xetex or \luatex has been detected, and \texttt{ascii} otherwise.
 
-If the \file{bib} file is not an Ascii file, use this option to specify its encoding. The following choices are available:
+\item[\prm{encoding}] If the encoding of the \file{bib} file is different from the one of the \file{tex} file, you need to specify it explicitly. When using the \sty{inputenc}\slash\sty{inputenx}\slash\sty{luainputenc} package, the \prm{encoding} must be an encoding name known to that package.
 
-\begin{valuelist}
+\end{valuelist}
 
-\item[ascii] Assume Ascii encoding. This option disables the encoding feature.
+By default, \sty{biblatex} assumes that the \file{tex} file and the \file{bib} file use the same encoding. Note that some backends only support a limited number of encodings. See \secref{bib:cav:enc} for further instructions.
 
-\item[inputenc] Get the encoding from the \sty{inputenc} package. Use this option if the encoding of the \file{bib} file is identical to the one of the \latex file.
+\boolitem[true]{bibwarn}
 
-\item[\prm{encoding}] If the encoding of the \file{bib} file is different from the one of the \latex file, you need to specify it explicitly. The \prm{encoding} must be an encoding name known to the \sty{inputenc} package, \ie there must be a matching \path{encoding.def} file. If this option is used, all macros used in the \file{bib} file must be robust or explicitly prefixed with \cmd{protect}.\footnote{In order to support different encodings in \file{tex} and \file{bib} files, this package will preprocess all data in the \file{bib} file with the equivalent of a \cmd{protected@edef}. This step is required to convert all 8-bit characters into encoding agnostic \latex internal character representations (\acr{LICR}s).}
+By default, \sty{biblatex} will report warnings issued by the backend concerning the data in the \file{bib} file as \latex warnings. Use this option to suppress such warnings.
 
-\end{valuelist}
+\intitem[2]{mincrossrefs}
 
-Note that \kvopt{bibencoding}{inputenc} and \kvopt{bibencoding}{\prm{encoding}} will implicitly set \kvopt{backend}{bibtex8} and report the encoding to external tools (see \secref{bib:cav:ide}). When using theses options, you should provide a matching \path{encoding.csf} file for \sty{bibtex8}. See \secref{bib:cav:enc} for further instructions.
+Sets the minimum number of cross references to \prm{integer} when requesting a \bibtex run.\footnote{If an entry which is cross-referenced by other entries in the \file{bib} file hits this threshold, it is included in the bibliography even if it has not been cited explicitly. This is a standard feature of \bibtex and not specific to \sty{biblatex}. See the description of the \bibfield{crossref} field in \secref{bib:fld:spc} for further information.} Note that this package option merely affects the format of certain requests written to the transcript file. It will not have any effect if the editor or compiler script launching \bibtex does not include dedicated \sty{biblatex} support or if \bibtex is manually launched from the command"=line.\footnote{As of this writing, no \latex editors or compiler scripts with dedicated \sty{biblatex} support are known, but this will hopefully change in the future.} See \secref{bib:cav:ide} for details. This option also affects the handling of the \bibfield{xref} field. See the field description in \secref{bib:fld:spc} as well as \secref{bib:cav:ref} for details.
 
 \end{optionlist}
 
@@ -7411,7 +7427,7 @@ Note that \cmd{DeclareLanguageMapping} is not intended to handle language varian
 \subsubsection{Grouping}
 \label{aut:cav:grp}
 
-When developing a citation or bibliography style, you may need to set switches or store certain values for later use. In this case, it is crucial to understand the basic grouping structure imposed by this package. As a rule of thumb, you are working in a large group whenever author commands such a those discussed in \secref{aut:aux} are available because the author interface of this package is only enabled locally. If any bibliographic data is available, there is at least one additional group. Here are some general rules:
+In a citation or bibliography style, you may need to set flags or store certain values for later use. In this case, it is crucial to understand the basic grouping structure imposed by this package. As a rule of thumb, you are working in a large group whenever author commands such a those discussed in \secref{aut:aux} are available because the author interface of this package is only enabled locally. If any bibliographic data is available, there is at least one additional group. Here are some general rules:
 
 \begin{itemize}
 
@@ -7434,7 +7450,7 @@ Note that using \cmd{aftergroup} in citation and bibliography styles is unreliab
 \subsubsection{Namespaces}
 \label{aut:cav:nam}
 
-In order to reduce the risk of name clashes, \latex packages typically prefix the names of internal macros with a short string specific to the package. For example, if the \sty{foobar} package requires a macro for internal use, it would typically be called \cmd{FB@macro} or \cmd{foo@macro} rather than \cmd{macro} or \cmd{@macro}. Here is a list of the prefixes used or recommended by \sty{biblatex}:
+In order to minimize the risk of name clashes, \latex packages typically prefix the names of internal macros with a short string specific to the package. For example, if the \sty{foobar} package requires a macro for internal use, it would typically be called \cmd{FB@macro} or \cmd{foo@macro} rather than \cmd{macro} or \cmd{@macro}. Here is a list of the prefixes used or recommended by \sty{biblatex}:
 
 \begin{marglist}
 
@@ -7457,6 +7473,16 @@ This revision history is a list of changes relevant to users of this package. Ch
 
 \begin{changelog}
 
+\begin{release}{1.0}{2010-11-19}
+\item First officially stable release
+\item Renamed option \kvopt{bibencoding}{inputenc} to \kvopt{bibencoding}{auto}\see{use:opt:pre}
+\item Made \kvopt{bibencoding}{auto} the package default\see{use:opt:pre}
+\item Added option \kvopt{backend}{bibtexu}\see{use:opt:pre}
+\item Slightly updated documentation\see{bib:cav:enc}
+\item Updated support for Dutch (Alexander van Loon)\see{use:opt:pre}
+\item Updated support for Italian (Andrea Marchitelli)\see{use:opt:pre}
+\end{release}
+
 \begin{release}{0.9e}{2010-10-09}
 \item Updated and expanded manual\see{bib:cav:enc}
 \item Added option \opt{sortupper}\see{use:opt:pre}
@@ -7491,7 +7517,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}
-\item Updated support for Brazilian (translations by Mateus Araújo)\see{use:opt:pre}
+\item Updated support for Brazilian (Mateus Araújo)\see{use:opt:pre}
 \item Fixed some bugs
 \end{release}