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/RELEASE93
1 files changed, 93 insertions, 0 deletions
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<namepart> 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<namepart>
+ \namepart<namepart>i
+
+ 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