summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/biblatex/CHANGES.org
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/biblatex/CHANGES.org')
-rw-r--r--Master/texmf-dist/doc/latex/biblatex/CHANGES.org157
1 files changed, 157 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/latex/biblatex/CHANGES.org b/Master/texmf-dist/doc/latex/biblatex/CHANGES.org
index 0ea70f42fee..31c4e2dbe59 100644
--- a/Master/texmf-dist/doc/latex/biblatex/CHANGES.org
+++ b/Master/texmf-dist/doc/latex/biblatex/CHANGES.org
@@ -1,3 +1,160 @@
+* RELEASE NOTES FOR VERSION 3.8a
+** Bug fix release
+- Documentation version fix and loop fix in certain styles
+* RELEASE NOTES FOR VERSION 3.8
+** Requirements
+Biber version 2.8 is required for biblatex 3.8
+
+** In order to standardise terminology, some commands and options have dropped the "scheme" naming convention and switched to "template"
+- ~\DeclareSortingScheme~ is now ~\DeclareSortingTemplate~
+- ~\DeclareSortingNamekeyScheme~ is now ~\DeclareSortingNamekeyTemplate~
+- The "sortingnamekeyscheme" option is now "sortingnamekeytemplate"
+
+** ~\DeclareLabelalphaNameTemplate~ no longer has entrytype scope
+- *INCOMPATIBLE CHANGE* The optional first argument to
+ ~\DeclareLabelalphaNameTemplate~ was previously an entrytype but is now an
+ arbitrary template name, as with ~\DeclareUniquenameTemplate~. This is to
+ allow multiple definitions which can be referred to at different scopes.
+ It is unlikely that anyone used this with entrytype scope anyway.
+
+** ~origlanguage~ is now a list instead of a field.
+- *INCOMPATIBLE CHANGE* Since this is mostly used to generate localisation strings like
+ 'Translated from the <language>' via the internal macros ~lbx@lfromlang~
+ and ~\lbx@sfromlang~, users and style authors should not see any
+ differences. However, if your style prints ~origlanguage~ directly using
+ ~\printfield~, this will need to be changed to ~\printlist~.
+
+** Name handling enhancements
+- Name handling is now fully generalised to cover arbitrary name parts.
+ The final few pieces have been completed to allow fully customisable
+ name handling, allowing for better internationalisation. The code for
+ name uniqueness calculation and label generation for names is now fully
+ abstracted: templates created with ~\DeclareUniquenameTemplate~ and
+ ~\DeclareLabelalphaNameTemplate~ may now be specified at per-refcontext,
+ per-entry, per-namelist and per-name scope, which allows complete
+ control over all aspects of name usage. See the comments in the enhanced
+ ~93-nameparts.tex~ example file.
+
+** ~extrayear~ is now ~extradate~ and the information used to track this can be customised
+- ~extrayear~ is called ~extradate~ now. Limited backwards compatibility is
+ in place to allow a smooth transition, but style developers should use the new name.
+- The new \DeclareExtradate command allows users to track authoryear
+ disambiguation in arbitrary ways now, for example allowing disambiguation
+ at month or day level instead of just year. See the PDF doc for details.
+- Some bibmacros from the ~authoryear~ style family were renamed,
+ ~cite:labelyear+extrayear~ becomes ~cite:labeldate+extradate~,
+ ~cite:extrayear~ is ~cite:extradate~ now, and ~date+extrayear~
+ is ~date+extradate~. Some backwards compatibility code is present,
+ but developers should make sure their code works as expected.
+
+** Date formatting
+- The ~mergedate~ output has been restored to its earlier form,
+ it has also been extended to cover all EDTF date parts.
+ In order to facilitate this, a few date-related tests were introduced
+ ~\iflabeldateisdate~, ~\ifdatehasyearonlyprecision~, ~\ifdatehastime~
+ and ~\ifdateshavedifferentprecision~.
+- The ~authoryear~ citation styles now use ~\printlabeldateextra~
+ instead of ~\printfield{labelyear}\printfield{extrayear}~.
+ This should have no consequences for end users (except that
+ dates in citations and bibliography don't differ any more -
+ previously there were subtle differences when many EDTF features
+ were used), but style developers should check if they assume
+ anything about the bibmacros that have now changed.
+ Style developers are invited to have a look at the changes and
+ to get inspired to offer full EDTF format for their styles as well.
+
+** Set handling
+- Static entry sets used to have the behaviour that when citing a member of
+ a set, the data for the citation came from the set parent which was in
+ turn taken from the first member of the set. In most use cases, the only
+ part of the set parent data that was actually used was the labels but in
+ certain edge cases, other data was used which results in confusing
+ citations for set members. This has been refactored so that when citing
+ set members, the member data is used along with some labelling data
+ injected from the set parent. This means that things like
+ ~\citeauthor{somesetmember}~ now give the expected results.
+ *PLEASE NOTE* that this means that citing sets directly in default styles *not*
+ based on labels (~authoryear~, ~authortitle~, ~verbose~ etc.) will result
+ in blank citations as it is not envisaged that sets are useful in such
+ styles.
+- The members of a set can now be sorted according to the active
+ sorting scheme, this is enabled via the ~sortsets~ option.
+ By default the option is set to false and set members appear
+ in the order given in the data source.
+- The ~alphabetic~ style family now also supports the ~subentry~
+ option.
+
+** Localisation and styles
+- Styles which supply their own location strings in .lbx files typically
+ use \DeclareLanguageMapping to map a document language to the supplied
+ language files. This is not ideal because the mapping has to be done by
+ the user depending on the specific language. For example, for the APA
+ style, in a document using American english, this line is necessary in
+ every document:
+
+ \DeclareLanguageMapping{american}{american-apa}
+
+ so that the style supplied america-apa.lbx file is loaded. In a document
+ using the german language, the user would have to use:
+
+ \DeclareLanguageMapping{german}{german-apa}
+
+ A new macro \DeclareLanguageMappingSuffix is now supplied which allows
+ styles to register a global localisation file suffix which is appended to
+ any document language automatically. This removes the need for
+ \DeclareLanguageMapping in user documents as it ensures that the correct
+ localisation file will be read nomatter what the document language. For
+ example, the APA style (from version v7.5) now has this in apa.bbx:
+
+ \DeclareLanguageMappingSuffix{-apa}
+
+ which means that for a given document language <lang>, the localisation file:
+
+ <lang>-apa.lbx
+
+ will be loaded. \DeclareLanguageMapping, if present, will override
+ \DeclareLanguageMappingSuffix.
+
+** Context-sensitive delimiters
+- Several delimiter macros now use the context-sensitive delimiter interface
+ introduced in version 3.4 (~\DeclareDelimFormat~). This change is fully
+ backwards compatible, but style developers should feel encouraged to use the
+ new commands ~\DeclareDelimFormat~ and ~\printdelim~.
+- Three new delimiters are introduced. ~authortypedelim~, ~editortypedelim~,
+ and ~translatortypedelim~ control the delimiter between the respective name
+ and the following ~<name>~ bibstring.
+ This together with ~\DeclareFieldFormat{<name>type}~ allows one to go from
+ 'E. Ditor, ed.' to 'E. Ditor (ed.)' more easily without the need
+ to redefine entire bibmacros.
+- ~\DeclareDelimAlias~ allows one to alias one delimiter to another.
+ E.g. ~\DeclareDelimAlias{finalnamedelim}{multinamedelim}~
+ will make ~finalnamedelim~ an alias for ~multinamedelim~.
+ The starred version ~\DeclareDelimAlias*~ is local to the
+ specified contexts.
+
+** Misc changes
+- The initialisation code for ~\usedriver~ can now be modified via
+ ~\AtUsedriver~, the code can be executed with ~\UseUsedriverHook~.
+ The default settings retain backwards compatibility with earlier
+ versions.
+- The field ~urlraw~ contains the unencoded, raw version of the URL.
+ If the URL includes Unicode characters, ~urlraw~ will show them
+ unencoded while the standard ~url~ field will contain them in
+ percent-encoded form.
+- ~\mkpagetotal~ now has its own bibstrings ~<pagination>total(s)~
+ Previously it relied on the ~<pagination>(s)~ bibstrings.
+- ~sortyear~ is now a literal field and not an integer.
+- The ~etextools~ package is now officially incompatible.
+- ~bidi~-support for footnotes was improved.
+- ~\ifentryseen~, ~\ifentryinbib~, ~\ifentrycategory~
+ and ~\ifentrykeyword~ can now be used outside of
+ ~biblatex~ macros directly in the document.
+- ~\letbibmacro~ can be used to create bibmacro aliases as if
+ using ~\let~.
+- ~\DeprecateFieldWithReplacement~, ~\DeprecateListWithReplacement~
+ and ~\DeprecateNameWithReplacement~ can be used to deprecate a field,
+ name or list and replace it with a new one.
+
* RELEASE NOTES FOR VERSION 3.7
** Requirements
Biber version 2.7 is required for biblatex 3.7