summaryrefslogtreecommitdiff
path: root/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2021-03-28 03:00:55 +0000
committerNorbert Preining <norbert@preining.info>2021-03-28 03:00:55 +0000
commitddd501183c3e68b7a98bdeb023d0b98ef84dae22 (patch)
treec36e981b83bb2591db85285af29b4d468ac671cb /macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
parent178fc96a7be703f91ea55832bd42b07eaf9f1ac5 (diff)
CTAN sync 202103280300
Diffstat (limited to 'macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE')
-rw-r--r--macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE115
1 files changed, 115 insertions, 0 deletions
diff --git a/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE b/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
index 428571c0fb..5d022e740f 100644
--- a/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
+++ b/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
@@ -1,3 +1,118 @@
+Release notes for version 2.1 [2021-03-27]:
+
+This release contains several new features, some modifications for
+compatibility with the latest biblatex, and many bug fixes. All
+styles require the latest biblatex (3.16) and biber (2.16).
+
+ - Patrick Danilevici has very generously provided a Romanian
+ localization for biblatex-chicago (cms-romanian.lbx) to go with the
+ romanian.lbx he wrote for biblatex itself. The only hitch is that
+ the latter file won't be in the standard biblatex package until the
+ next release, so you'll have to grab it from GitHub
+ https://github.com/plk/biblatex/tree/dev/tex/latex/biblatex/lbx
+ until then.
+
+ - Moritz Wemheuer recommended that I include the standard biblatex
+ macro "begentry" at the start of all drivers in both Chicago
+ styles, with an empty definition by default. This allows users to
+ redefine it in their preambles and thereby inject their code into
+ the driver before anything is printed.
+
+ - Moritz also drew my attention to a question on StackExchange which
+ suggested that I should expand the applicability of the
+ "annotation" field, so I've modified the "annotation" option in all
+ styles to allow the field to appear both in bibliography (reference
+ list) and in long notes, and also added two new options in all
+ styles, "bibannotesep" and "citeannotesep," which allow you to
+ define how the "annotation" field will relate to the main entry.
+ The options have different defaults, and although they have the
+ same pre-defined keys those keys may have slightly different
+ meanings depending on whether the "annotation" is to appear in
+ notes or bibliography. Please see the docs of field and options in
+ sections 4.2, 4.4.2, 4.4.3, 5.2, 5.4.2, and 5.4.3 of
+ biblatex-chicago.pdf.
+
+ - On a related subject, I have included two new options in all styles
+ -- "formatbib" and "entrybreak" -- which provide fine-grained control
+ of page breaking in bibliographies and reference lists. Some of
+ the values of these options are designed to be used with specific
+ values of the "bibannotesep" option, so please see the
+ documentation in sections 4.4.3 and 5.4.3.
+
+ - In the notes & bibliography style Fr. Norbert Keliher requested a
+ way to turn off the printing, in the first citation of a work, of
+ the introduction -- (hereafter cited as ...) -- of a "shorthand"
+ that will appear in subsequent citations. The "shorthandintro"
+ option is now available globally, per type, and per entry to allow
+ you to control the (non)appearance of this clarifying notification.
+ By default, the first citation of a work will continue to present
+ the "shorthand" as it always has. Please see section 4.4.3 for the
+ details.
+
+ - Philipp Immel requested a feature involving the "nameaddon" field,
+ and pointed to a discussion on StackExchange which suggested that
+ others were also unsatisfied with that field's functionality, so in
+ this release I've provided three new package options to allow users
+ to mould it to their needs. The options are called "nameaddon,"
+ "nameaddonformat," and "nameaddonsep," and you can find all the
+ details in the "nameaddon" docs in sections 4.2. and 5.2. Cf.
+ also the discussions of the options in sections 4.4.2, 4.4.3,
+ 5.4.2, and 5.4.3. Allow me to emphasize that the package defaults
+ remain exactly the same as before, so that if you don't set any of
+ the new options no changes to your documents or .bib databases are
+ necessary.
+
+ - Philipp Immel also requested a way to use the standard biblatex
+ option "datamodel" even when loading the Chicago styles with
+ \usepackage{biblatex-chicago}. Implementing this allowed me to
+ regularize how the standard "mcite" and "natbib" options were
+ passed through to biblatex, and also to support the new biblatex
+ "casechanger" option, which can help solve a bug reported by Peter
+ Mukunda Pasedach. See sections 4.4.3 and 5.4.3.
+
+ - The new "relatedtype" "short" is available in all styles to allow
+ the presentation of short references rather than full ones when
+ using the "related" mechanism. See sections 4.2.1 and 5.2.1.
+
+ - In a similar vein, I have provided new \citeincite and
+ \fullciteincite commands to allow you, in some contexts, to cite a
+ related work inside the fields of another entry, something which,
+ although not recommended, is common practice, and which has
+ frequently not worked quite right. The \citeincite and
+ \citeincites commands always present short citations, and are
+ available in several fields, while \fullciteincite and
+ \fullciteincites always present long references, and are designed
+ only to be used in the "annotation" field for cases where an
+ annotated bibliography or reference list includes references to
+ works not cited in the main text. See sections 4.3.2 and 5.3.2 for
+ the details. If I've missed yet further tricky corners in this
+ functionality please let me know.
+
+ - After a request by Patrick Danilevici, I have added the four fields
+ "eventdate," "eventtitle," "eventtitleaddon," and "venue" to the
+ InProceedings, MVProceedings, and Proceedings drivers in all
+ styles, for compatibility with standard biblatex usage. See the
+ docs of those entry types in sections 4.1 and 5.1.
+
+ - The "postnotepunct" option should generally work now, both in more
+ contexts and with arbitrary "postnote" field contents.
+
+ - The "dashed" option governing the use of the 3-em dash in
+ bibliographies and reference lists is now available globally, per
+ type, and per entry.
+
+Note on the 16th-edition files:
+
+ - These have been updated for compatibility with the latest biblatex
+ and biber, and there are also a number of bug fixes included. I
+ haven't added any new functionality to the files, so for instance
+ if you want to use the new Romanian localization you'll need the
+ current 17th-edition styles. With this release I am marking the
+ 16th-edition files as deprecated, and will remove them in a future
+ release. Please consider moving your documents to the current
+ specification, where all of my development time is now spent.
+
+
Release notes for version 2.0 [2020-04-20]:
With this release biblatex-chicago now by default follows the 17th