biblatex 0.9d (4sep10)

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

1 files changed, 247 insertions, 1 deletions

diff --git a/Master/texmf-dist/doc/latex/biblatex/RELEASE b/Master/texmf-dist/doc/latex/biblatex/RELEASE
index 398f4911f33..3862ed4772a 100644
--- a/Master/texmf-dist/doc/latex/biblatex/RELEASE
+++ b/Master/texmf-dist/doc/latex/biblatex/RELEASE
@@ -1,4 +1,250 @@
-$Id: RELEASE,v 0.9a 2010/03/19 19:52:15 lehman beta $
+$Id: RELEASE,v 0.9d 2010/09/03 20:11:58 lehman beta $
+
+RELEASE NOTES FOR VERSION 0.9d
+
+*  Date formatting options
+
+   I've removed all '<date>=none' options as this feature seems to
+   be causing some confusion. Setting '<date>=none' was not
+   sufficient to suppress a certain date in all cases because date
+   specifications may also incorporate elements such as the 'issue'
+   field, be tied to the 'url' in a way that leads to erroneous
+   formatting if there is no date, etc. I'm afraid selectively
+   omitting dates really needs to be handled on the style level.
+
+   There's a new set of '<date>=iso8601' options which print
+   extended-format ISO-8601 dates. Not all of ISO-8601 is
+   implemented, only the core elements of the extended format which
+   are also used in .bib files, i.e., "yyyy-mm-dd" for individual
+   dates and "yyyy-mm-dd/yyyy-mm-dd" for ranges. Full-scale ISO-8601
+   date/time specs like "2005-08-09T18:31:42P3Y6M4DT12H30M17S"
+   wouldn't make much sense in a bibliography anyway. Note that
+   these options are language agnostic. They will override any
+   region-specific settings provided by .lbx files. That's the
+   whole point of ISO-8601, after all. 
+
+RELEASE NOTES FOR VERSION 0.9c
+
+*  Improved reencoding support
+
+   Biber 0.5.5 is capable of reencoding the data in bib files on the
+   fly. This solution is more robust than biblatex's macro-level
+   reencoding with inputenc. With 'backend=biber', biblatex will now
+   use Biber instead of inputenc. In addition to that, the biblatex
+   code which detects if the bib data needs to be reencoded to match
+   the encoding of the tex file is smarter now and should work
+   smoothly.
+
+   In practice, this simply means that you may always use the
+   'bibencoding' option to specify the encoding of your bib files
+   (there was some potential for spurious reencoding steps in
+   previous versions), with any backend. It is in fact highly
+   recommended to do so for two reasons: 1) the default value is
+   'ascii', and 2) biblatex will warn you if the bib encoding can't
+   be handled by the backend you selected.
+
+   You may put your platform default in biblatex.cfg; there is no
+   need to do that in each and every preamble (you may still
+   override all biblatex.cfg settings on a per-document basis in the
+   preamble, if required).
+
+*  UTF-8 encoded entry keys and bib filenames
+
+   Biber 0.5.5 supports UTF-8 encoded entry keys. Biblatex will work
+   with UTF-8 keys and filenames when running on an engine with
+   native UTF-8 support (i.e., XeTeX or LuaTeX). Macro-level UTF-8
+   support with inputenc/inputenx will not do.
+
+*  Improved arXiv support
+
+   I've added an additional eprint-related field plus two aliases to
+   better support arXiv references. The changelog includes pointers
+   to the relevant sections of the manual.
+
+RELEASE NOTES FOR VERSION 0.9b
+
+*  Extended Biber interface
+
+   If you're using Biber as backend, make sure you update Biber as
+   well (to version 0.5.4 or higher) because the Biblatex -> Biber
+   interface has been extended.
+   
+   The most obvious effect of this improvement is that Biber is now
+   capable of handling multiple refsections in a single pass. If you
+   have any 'refsection' environments in a document, you only need to
+   run Biber once.
+
+*  New dependency: logreq package
+
+   Starting with this release, biblatex will use the logreq package
+   to write machine-readable messages to an auxiliary log file. When
+   installing biblatex 0.9b, make sure to install the logreq package
+   as well. It is available from CTAN:
+   
+   http://www.ctan.org/tex-archive/macros/latex/contrib/logreq/
+   
+   A TDS archive is available as well:
+   
+   http://www.ctan.org/tex-archive/install/macros/latex/logreq.tds.zip
+
+*  Modified \defbibfilter syntax
+
+   I've modified \defbibfilter such that it uses \ifboolexpr (from
+   etoolbox.sty) instead of \ifthenelse (from ifthen.sty)
+   internally. \ifboolexpr uses a slightly different syntax.
+   For example, this definition:
+
+   \defbibfilter{example}{%
+     \( \type{book} \or \type{inbook} \)
+     \and \keyword{abc}
+     \and \not \keyword{x y z}
+   }
+
+   becomes:
+   
+   \defbibfilter{example}{%
+     ( type=book or type=inbook )
+     and keyword=abc
+     and not keyword={x y z}
+   }
+
+   There is no need to update existing files since the old
+   \ifthenelse syntax is still supported. \defbibfilter will
+   implicitly 'translate' at definition time, if required.
+
+*  Renamed option 'defernums' to 'defernumbers'
+
+   The package option 'defernums' has been renamed to
+   'defernumbers'.
+
+*  Prefixed numerical citations, improved 'numeric' styles
+
+   I've added three options to \printbibliography which are related
+   to numerical citation schemes. They are called 'prefixnumbers',
+   'resetnumbers', and 'omitnumbers'. Note that these options
+   require that 'defernumbers' be set globally since they assign the
+   numeric labels as the bibliography is generated (as opposed to at
+   the beginning of the document body, as the data is read in).
+
+   The new options enable the numeric styles to support prefixed
+   numerical citations. The following may be accomplished by setting
+   'prefixnumbers' for each prefixed subbibliography:
+
+   REFERENCES
+   Printed References
+   [A1] ...
+   [A2] ...
+   Online References
+   [B1] ...
+   [B2] ...
+
+   It is also possible to mix one non-prefixed subbibliography with
+   one or more prefixed ones (set 'prefixnumbers' for each prefixed
+   subbib and 'resetnumbers' for the non-prefixed one) or even to
+   mix numerical citations with author-year or author-title
+   citations (set 'omitnumbers' for all non-numerical subbibs).
+
+   See the files '16-numeric-prefixed-1', '17-numeric-prefixed-2',
+   and '18-numeric-hybrid' in the 'examples' subdirectory for
+   practical examples.
+   
+   Adding support for prefixed numerical citations to existing
+   numeric styles is trivial. The prefixes set in the argument to
+   \printbibliography are available in the 'prefixnumber' field. If
+   no prefix has been set, the field is undefined. Hence, in the cbx
+   file, simply replace:
+
+   \printfield{labelnumber}
+   
+   with:
+   
+   \printfield{prefixnumber}%
+   \printfield{labelnumber}
+   
+   In the bbx file, the prefix needs to be incorporated in the
+   definition of the bibliography environment. Replace:
+   
+   \defbibenvironment{bibliography}
+     {\list
+	{\printfield[labelnumberwidth]{labelnumber}}
+	{...}
+     {\endlist}
+     {\item}
+
+   with:
+   
+   \defbibenvironment{bibliography}
+     {\list
+	{\printtext[labelnumberwidth]{%
+	   \printfield{prefixnumber}%
+	   \printfield{labelnumber}}}
+	{...}
+     {\endlist}
+     {\item}
+
+   The numeric styles which ship with biblatex support prefixed
+   labels out of the box.
+
+*  New author-title style 
+
+   There's a new style which rounds off the selection of
+   author-title styles which ship with biblatex. It's called
+   'authortitle-ticomp' and, as you can tell by the name, it's a
+   variant of the 'authortitle-tcomp' style with an 'ibidem'
+   feature.
+
+*  Improved verbose styles, added 'citepages' option
+
+   By popular request, all verbose styles now offer a 'citepages'
+   option which deals with the 'pages' field in citations, in
+   particular in cases in which the postnote is numerical.
+
+   Note that style specific options are only mentioned briefly in
+   the manual. They are discussed in greater details in the example
+   file for the style (in the 'examples' subdirectory).
+
+*  Long + short bibliography strings available
+
+   Previous biblatex releases used to pick the long or the short
+   version of the strings in the lbx files at file load time,
+   depending on the setting of the global 'abbreviate' option.
+   Starting with this release, both versions are kept in memory.
+
+   In addition to \bibstring and friends, which print the long or
+   the short version of the string (depending on the 'abbreviate'
+   option), there are now commands like \biblstring and \bibsstring,
+   which force the long or the short version, respectively.
+
+   Note that the auxiliary macro \lbx@fromlang, which is used in lbx
+   files, has been split up into \lbx@lfromlang and \lbx@sfromlang.
+
+*  Automatically omit redundant language specifications
+
+   Some style guides require that authors indicate the language of all
+   foreign-language items in the bibliography. Biblatex's 'language'
+   field (which is in fact a list) helps to deal with this
+   requirement. If you are writing in more than one language and
+   reuse the same set of bib files in different contexts, it is
+   convenient to include this information whenever you add a new
+   entry to a bib file. However, this leads to redundant
+   information. It is rather odd to indicate "English" in the
+   reference to an English book cited in an English article.
+
+   The 'clearlang' option and \DeclareRedundantLanguages avoid such
+   redundant language specifications. \DeclareRedundantLanguages
+   maps languages as indicated in the 'language' field to the
+   language identifiers of the babel package. Given this
+   information, biblatex can omit the language if it matches the
+   language of the document. Technically, this means that the
+   'language' field will appear as undefined to styles, so it is
+   safe to simply use '\printlist{language}' in styles and let
+   biblatex sort out the rest.
+
+   The 'clearlang' option controls this feature globally.
+   \DeclareRedundantLanguages mappings are typically included in lbx
+   files (but may also be given on a per-document basis in the
+   preamble). All standard lbx files which ship with biblatex now
+   include such mappings and 'clearlang' is enabled by default.
 
 RELEASE NOTES FOR VERSION 0.9a