biblatex 1.2a (13feb11)

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

1 files changed, 93 insertions, 1 deletions

diff --git a/Master/texmf-dist/doc/latex/biblatex/RELEASE b/Master/texmf-dist/doc/latex/biblatex/RELEASE
index b442a3751f5..d46959aa328 100644
--- a/Master/texmf-dist/doc/latex/biblatex/RELEASE
+++ b/Master/texmf-dist/doc/latex/biblatex/RELEASE
@@ -1,5 +1,97 @@
-$Id: RELEASE,v 1.1b 2011/02/04 11:36:21 lehman stable $
+$Id: RELEASE,v 1.2a 2011/02/13 12:05:37 lehman stable $
 
+RELEASE NOTES FOR VERSION 1.2
+
+*  Remote resources, experimental RIS import [Biber only]
+
+   Biber 0.8 features support for remote .bib files (HTTP/FTP) and
+   experimental RIS file import. See the Biber manual and
+   \addbibresource in the biblatex manual for details.
+
+*  \bibliography superseded by \addbibresource
+
+   As Biber development opens new possibilities, I've refactored the
+   user interface for specifying bibliographic resources.
+   \bibliography is superseded by \addbibresource. There are two
+   differences when using \addbibresource:
+
+   1) Always give the full file name, do not omit the .bib extension.
+   2) No comma-separated lists, use one \addbibresource per bib file.
+   
+   For example, the old form:
+   
+   \bibliography{file1,file2}
+   
+   is superseded by:
+   
+   \addbibresource{file1.bib}
+   \addbibresource{file2.bib}
+
+   \addbibresource also supports options:
+
+   \addbibresource[location=local,type=file,datatype=bibtex]{file1.bib}
+
+   You only need to specify options which differ from the defaults
+   (local/file/bibtex), e.g.:
+
+   \addbibresource[datatype=ris]{file.ris}
+   \addbibresource[location=remote]{ftp://192.168.3.57/~fred/file1.bib}
+
+   The change is fully backwards compatible since \bibliography is
+   still available. There is no need to update existing files but
+   \addbibresource is the recommended way for new files.
+
+*  Smart/customizable 'crossref' data inheritance [Biber only]
+
+   Biber has been supporting 'crossref' customization for some time
+   but the biblatex user interface was still missing. This release
+   finally adds a user interface. This means that you may configure
+   how the data is inherited from the entry the 'crossref' field
+   refers to. The manual has all the details, including the default
+   settings.
+
+   If you're using the 'crossref' field, this change is a significant
+   one since the smart data inheritance is set up by default. By
+   'smart' I mean a sensible parent/child field mapping which
+   replaces BibTeX's symmetric mapping. There is no need any more to
+   duplicate fields.
+
+   BibTeX crossref:
+
+   book		->	inbook
+   -----------------------------------
+   title	->	title
+   booktitle	->	booktitle
+
+   Biber crossref:
+
+   book		->	inbook
+   -----------------------------------
+   title	->	booktitle
+
+*  New multi-volume entry types
+
+   There are four new entry types in this release: mvbook,
+   mvcollection, mvproceedings, mvreference. They are similar to the
+   established types without the 'mv' prefix but indicate a
+   multi-volume work explicitly.
+
+   This difference is crucial of you want to leverage Biber's
+   'crossref' support because titles are inherited differently in
+   this case:
+
+   book		->	inbook
+   -----------------------------------
+   title	->	booktitle
+   subtitle	->	booksubtitle
+   titleaddon	->	booktitleaddon
+
+   mvbook	->	inbook
+   -----------------------------------
+   title	->	maintitle
+   subtitle	->	mainsubtitle
+   titleaddon	->	maintitleaddon
+   
 RELEASE NOTES FOR VERSION 1.1
 
 Starting with this release, we'll leverage the possibilities of Biber