summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/biblatex/RELEASE
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/biblatex/RELEASE')
-rw-r--r--Master/texmf-dist/doc/latex/biblatex/RELEASE57
1 files changed, 57 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/latex/biblatex/RELEASE b/Master/texmf-dist/doc/latex/biblatex/RELEASE
index 405e74a34b5..c9117079c0b 100644
--- a/Master/texmf-dist/doc/latex/biblatex/RELEASE
+++ b/Master/texmf-dist/doc/latex/biblatex/RELEASE
@@ -1,3 +1,60 @@
+RELEASE NOTES FOR VERSION 3.0
+
+* Biber version 2.0 is required for biblatex 3.0
+* A new reference context mechanism to allow for future extensions has been
+ introduced. Effectively, this means the following. The 'sorting' option to
+ \printbibliography and \printbiblist is deprecated. You should use the
+ 'sorting' option to \newrefcontext or the
+ \begin{refcontext}\end{refcontext} environment. This allows the sorting
+ list context wider scope over citations etc. too. For example, some
+ information in citations like extrayear depends on the sort list order
+ but until this version, citation sorting was always determined by the global sort
+ list. Therefore it was not too difficult to get into a situation where
+ citations were incorrect for a bibliography list with a defined sorting scheme:
+
+ \usepackage[sorting=nty]{biblatex}
+ \cite{test1}
+ \cite{test2}
+ \printbibliography[sorting=nyt]
+
+ In this case, the citation labels may not match the bibliography
+ because the data used to generate the citations are drawn from a
+ different sort list. This was a general issue that entry data was
+ assumed to be the same over all bibliography lists. Only the order of
+ entries was assumed to be different, which is incorrect. The order of
+ items in a bibliography list can impact the actual data contents of
+ items in the case of things like the extra* fields. Now, the above can
+ be solved using the new refcontext mechanism which exposes the sorting
+ context to biblatex:
+
+ \usepackage[sorting=nty]{biblatex}
+ \newrefcontext[sorting=nyt]
+ \cite{test1}
+ \cite{test2}
+ \printbibliography
+
+ In this case, the \cite commands pull their data from the "nyt" sorting
+ list data which is also used by the following \printbibliography
+ This is all for biber only.
+* labelname and labeltitle are now instantiated by biblatex dynamically at
+ output time. Prior to this release, labelname and labeltitle were
+ statically instantiated by biber and put into the .bbl. This does not allow
+ for context-sensitive labelname/labeltitle determination which is
+ foreseen in future extensions.
+* New "pernottype" and "entryclone" sourcemapping verbs allow for negated
+ matches on entry types and the cloning of entries respectively. Requires
+ biber.
+* Biber now calculates the length of ranges (like page ranges) so that the
+ various range-length tests are far more accurate. See the "frangelen"
+ field documentation. This is very robust and can deal with roman numerals
+ in just about all of their Unicode and ASCII forms.
+* When a bibliography field is declared as a "name" field in the data
+ model, all options and counters to decide whether to use it or not are
+ automatically created. This effectively extends the existing "useauthor"
+ and "useeditor" options to all data mode name fields automatically. These
+ options are now just special cases of the general data model name
+ handling mechanism.
+
RELEASE NOTES FOR VERSION 2.9a
* Biber version 1.9 is required for biblatex 2.9a