summaryrefslogtreecommitdiff
path: root/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
diff options
context:
space:
mode:
Diffstat (limited to 'macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE')
-rw-r--r--macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE350
1 files changed, 349 insertions, 1 deletions
diff --git a/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE b/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
index 6c2ad051b2..428571c0fb 100644
--- a/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
+++ b/macros/latex/contrib/biblatex-contrib/biblatex-chicago/RELEASE
@@ -1,3 +1,351 @@
+Release notes for version 2.0 [2020-04-20]:
+
+With this release biblatex-chicago now by default follows the 17th
+edition of the Manual. If for any reason you need to keep using the
+16th-edition styles, they are still available by calling "notes16,"
+"authordate16," or "authordate-trad16" when you load biblatex-chicago.
+All six available styles require the latest biblatex (3.14) and also
+biber (2.14) as the backend -- other backends will no longer work
+properly in any style. I strongly encourage you to use the
+17th-edition styles if at all possible, simply because nearly all of
+my development time has been spent on them, and they contain a great
+many fixes and enhancements that haven't made it back into the
+16th-edition styles. In what follows you'll see what changes you'll
+need to make to update your documents for the new edition. In truth,
+the changes between these two editions have been largely additive, so
+the actual changes required in your .bib databases or documents will
+in most cases be very few indeed. After outlining the modifications
+you may need to make, I'll list the enhancements available in the
+various styles, including a short discussion of the changes to the
+16th-edition styles.
+
+Converting from the 16th to the 17th edition:
+
+ - The 17th edition of the Manual no longer encourages use of "ibid."
+ to replace repeated citations of the same work in the notes &
+ bibliography style, preferring instead to use the author's name
+ alone, along with any page number(s). If you wish to continue
+ using "ibid." in that style, you need to set the new option
+ "useibid=true" when loading biblatex-chicago in your preamble.
+
+ - If you are loading the package the old-fashioned way, with biblatex
+ and the "style=" option instead of with biblatex-chicago, please be
+ aware that there are two standard packages required by
+ biblatex-chicago that aren't automatically loaded by biblatex:
+ "xstring" and "refname". You'll need to load them in your preamble
+ yourself.
+
+ - If you've been using the "year" field to present decades like
+ "1950s", this will no longer work accurately in author-date
+ citations. The correct way to do so now is to use one of
+ biblatex's ISO8601-2 date specifications in the "date" field
+ instead, to wit, "195X". Generally, I've tried to make "year"
+ fields like "[1957?]" or "[ca. 1850]" continue to work properly,
+ but here too the best thing to do is to use the new "date" features
+ and present them like "1957?" or "1850~", respectively. This will
+ ensure that both sorting and punctuation work out properly. See
+ table 3 in biblatex-chicago.pdf, and the "date" docs in sections
+ 4.2 and 5.2 of the same document.
+
+ - If you have been using the "nameaddon" field to hold time stamps
+ for online comments, then you should put the time stamp into the
+ "date" or possibly "eventdate" field, instead, using the ISO8601-2
+ format implemented by biblatex. See the "date" and "nameaddon"
+ field docs in sections 4.2 and 5.2 of biblatex-chicago.pdf, along
+ with tables 1, 2, and 3.
+
+ - Following on from the previous item, the 17th edition of the Manual
+ includes more plentiful and more detailed instructions for
+ presenting online materials than were available in previous
+ editions. For users of biblatex-chicago this means that there is
+ now guidance for many more sorts of material than before, so if you
+ have been improvising citations of this sort of material in
+ previous releases it will be worth checking to see whether there
+ are now clearer instructions available. Tables 1 and 2 summarize
+ the new specifications for the notes & bibliography and author-date
+ styles, respectively. Cf. in particular the new "commenton"
+ "relatedtype" in sections 4.2.1 and 5.2.1 of biblatex-chicago.pdf.
+ Also, the Online entry type now prints both "author" and "editor"
+ (or other editorial role) if they exist, and I've moved the
+ "addendum" field _before_ the "url", which fits better with
+ indications in the Manual. If you've been using the "addendum"
+ field to present citations of other entries (as in older versions
+ of biblatex-chicago), please switch to the "related" mechanism,
+ which works better anyway.
+
+ - On the same subject, if you are using the notes & bibliography
+ style and are retaining the "crossref" field (instead of using the
+ "commenton" "relatedtype") in Review entries as a means of
+ presenting comments on blogs, such entries are now subject to the
+ settings of the "longcrossref" option and will appear in
+ abbreviated form in some full notes and in the bibliography, as has
+ always occurred in InCollection entries, for example. You can set
+ "longcrossref" to "true" to get back the old behavior.
+
+ - The 17th edition generally encourages more strongly than the 16th
+ the use of only one publisher in the "publisher" field. If you
+ decide to retain more than one, and one of them is a part of an
+ academic publishing consortium, it encourages you to specify this
+ relationship rather than merely listing the two using the keyword
+ "and" in the field. Please see the documentation of the field in
+ sections 4.2 and 5.2 of biblatex-chicago.pdf for the rather minor
+ (and rare) changes this might mandate for your .bib files.
+
+ - The 17th-edition presentation of Music entries has added a few
+ pieces of information it seems to find desirable -- track number in
+ "chapter" and specification of a lead performer's role in, e.g.,
+ "editortype" -- though the basic structure of a 16th-edition .bib
+ entry remains unchanged. Please see the documentation of that
+ entry type in sections 4.1 and 5.1 in biblatex-chicago.pdf.
+
+ - The 17th edition has added a couple of wrinkles to the Video type
+ specifications. You can now put the broadcast network of a TV show
+ in the "usera" field, and you can also supply the new
+ "entrysubtype" "tvepisode" to print the series title ("booktitle")
+ _before_ the episode title ("title"). Please see the documentation
+ of the entry type in sections 4.1 and 5.1 in biblatex-chicago.pdf.
+
+ - Both Chicago styles now sentence-case the "title" field in Patent
+ entries, so you may need to put curly braces around words that
+ shouldn't appear in lowercase.
+
+ - The "pubstate" field now has a more generalized functionality,
+ while maintaining the specialized uses present in earlier releases.
+ In particular, please note now that almost anything you put in the
+ field will be printed somewhere in the entry, and in the case of
+ the author-date styles may appear in a somewhat different part of
+ the entry than that to which you may have become accustomed. If
+ you wish to move this data back to the end of the entry in the
+ author-date styles, then the "addendum" field might be of service.
+ The documentation in sections 4.2 and 5.2 of biblatex-chicago.pdf
+ should help.
+
+Other new features common to all styles:
+
+ - Wouter Lancee has very generously provided a Dutch localization for
+ biblatex-chicago, called cms-dutch.lbx. You can use it by
+ including "dutch" when loading babel. Gustavo Barros has also very
+ kindly provided a much-revised version of his cms-brazilian.lbx.
+
+ - As mentioned above, this release for the first time implements
+ biblatex's elegant and long-standing support for the ISO8601-2
+ Extended Format date specification, which means there are now
+ greatly enhanced possibilities for presenting uncertain and
+ unspecified dates and date ranges, along with date eras, seasons,
+ time stamps, and time zones. Table 3 in biblatex-chicago.pdf
+ summarizes the implementation for all Chicago styles, but see also
+ the "date" field in sections 4.2 and 5.2, along with the new
+ package options "alwaysrange", "centuryrange", "decaderange",
+ "nodatebrackets", and "noyearbrackets".
+
+ - I have also implemented year-range compression in all styles,
+ governed by the new "compressyears" option, set to "true" by
+ default.
+
+ - Constanza Cordoni requested a way to turn off the printing of the
+ 3-em dash for repeated names in the bibliography or reference list,
+ and the Manual concedes that some publishers prefer this style.
+ Some of biblatex's standard styles have a "dashed" option, so for
+ compatibility purposes I've provided the same. By default, I have
+ set it to "true" to print the name dash, but you can set
+ "dashed=false" in your preamble to repeat names instead throughout
+ your document.
+
+ - Jan David Hauck suggested I extend the field-exclusion
+ functionality beyond the package options already provided by
+ biblatex-chicago (sections 4.4.2 and 5.4.2 of
+ biblatex-chicago.pdf). First, I made sure that all of those
+ options could be set globally, per type, and per entry. Second, I
+ added the command \suppressbibfield, designed to
+ appear in the preamble, and which will look something like:
+
+ \suppressbibfield[entrytype,entrytype,...]{field,field,field,...}
+
+ Please see sections 4.3.1 and 5.3.1 in the pdf for the details.
+
+ - After a request by user BenVB, I have added support for the
+ biblatex "shortseries" field, which allows you to present
+ abbreviated "series" in book-like entries in all the styles. You
+ can use the "seriesabbrev" option to control where in your document
+ these abbreviated forms will appear. By default, the field is
+ ignored in all styles. You can also print a list of series
+ abbreviations, rather in the manner of a list of shorthands, using
+ a command like: \printbiblist{shortseries}. Please see
+ "shortseries" in sections 4.2 and 5.2 of biblatex-chicago.pdf.
+
+ - I have added a new preamble option, "cmsbreakurl", which attempts
+ to follow the Manual's instructions for line-breaking inside URLs.
+ It doesn't work 100% accurately, and it doesn't play well with the
+ ragged2e package, but in most circumstances it is at least closer
+ to the Chicago ideal than the biblatex defaults. See sections
+ 4.4.3 and 5.4.3 in biblatex-chicago.pdf.
+
+ - The Manual now specifies how to present Articles with a unique
+ numeric or alphanumeric ID, which you can place in the "eid" field.
+ If you've been using this field in previous releases you'll notice
+ that the ID has moved to a different place in long notes,
+ bibliography, and list of references.
+
+ - In Jurisdiction entries, the presentation of the "title" changes
+ depending on whether it appears in a stand-alone citation or as
+ part of the flow of running text, no matter whether the citation is
+ in the main body or in a note. I have provided the \runcite
+ command, in both Chicago styles, for Jurisdiction citations that
+ appear in running text.
+
+ - N. Andrew Walsh suggested that I allow editorial roles that aren't
+ pre-defined \bibstrings to appear as-is in entries, just as the
+ standard biblatex styles do. I have followed this advice for the
+ "editortype", "editoratype", "editorbtype", "editorctype", and
+ "nameatype" fields, making sure to capitalize the string according
+ to its context.
+
+ - I have added the "venue" field to Misc entries, both with and
+ without an "entrysubtype". It also appears in the new Performance
+ type.
+
+ - I have added the "version" and "type" fields to Book entries to
+ help with multimedia app content. This material fits quite well in
+ such entries but needs extra fields to present information about
+ the version of the app and also the system type on which it runs.
+ I added the "type" field to Article, Review, and Online entries for
+ presenting medium information for online multimedia.
+
+ - I have added support for biblatex's new entry type, Dataset, to
+ allow the citation of scientific databases. See the docs in
+ sections 4.1 and 5.1 of biblatex-chicago.pdf
+
+ - I have added the "number" field to Misc entries with an
+ "entrysubtype" to help cope with the varieties of location
+ information in different archives. See the Misc docs in sections
+ 4.1 and 5.1.
+
+ - The new entry type Standard is now available to cite standards
+ published by national or international standards organizations. If
+ you have been using the Book type for such material it might be
+ worth switching to make sure your entries are more in line with the
+ Manual's specifications. See sections 4.1 and 5.1 of
+ biblatex-chicago.pdf for the details.
+
+ - The new entry type Performance is now available for citing live
+ performances. You can sometimes also use a Misc entry without an
+ "entrysubtype". Cf. sections 4.1 and 5.1.
+
+ - I have added the "eventdate" field to the Audio entry type to help
+ it cope with the presentation of podcasts, which are new to the
+ 17th edition. Please see the documentation of the entry type in
+ sections 4.1 and 5.1.
+
+ - I have added the "origdate", "eventdate", "userd", and
+ "howpublished" fields to the Artwork and Image entry types, in
+ response to additional information given in some of the Manual's
+ examples. Please see the documentation of Artwork in sections 4.1
+ and 5.1.
+
+ - I have added the "maintitle", "mainsubtitle", and "maintitleaddon"
+ fields to the Article, Periodical, and Review entry types, where it
+ (they) will hold the the name of any larger (usually periodical)
+ publication of which a blog is a part. This departs from standard
+ biblatex usage, but the need for two italicized titles demanded
+ something like it.
+
+ - I have added a new field-exclusion option, "urlstamp", set to
+ "true" by default, which means that any time stamp associated with
+ the "urldate" will always be printed. You can set it to "false" in
+ the preamble either for the whole document or for specific entry
+ types, or in the "options" field of individual entries. See the
+ docs in sections 4.4.2 and 5.4.2.
+
+ - The "howpublished" field has accumulated a series of new functions
+ in various entry types, bringing it far from its origins in
+ Booklet, Misc, and Unpublished entries. Please see its
+ documentation in sections 4.2 and 5.2.
+
+ - In InReference, MVReference, and Reference entries biblatex-chicago
+ no longer considers any of the name fields ("author", "editor",
+ etc.) for sorting purposes in the bibliography or reference list,
+ thus leaving the "title" as the first field to be considered. This
+ may simplify the creation of .bib database entries.
+
+New notes & bibliography features:
+
+ - In keeping with indications in the 17th edition of the Manual, I
+ have provided a means for altering the syntax when presenting
+ multi-volume works, i.e., for presenting the title of the whole
+ series ("maintitle") _before_ the title of individual volumes of
+ that series ("title" or "booktitle"). This involves the use of the
+ new "relatedtypes" "maintitle" and "maintitlenc", which may be used
+ in BookInBook, InBook, InCollection, InProceedings, Letter, MVBook,
+ MVCollection, MVProceedings, and MVReference entries. Please see
+ the detailed documentation of this feature in section 4.2.1,
+ s.v. "relatedtype" "maintitle".
+
+ - I have implemented a new system of back references from short notes
+ to long notes to help readers find fuller information about a
+ source more quickly and conveniently, as envisaged by the Manual.
+ The feature is enabled with the "noteref" option, and there are
+ several sub-options to control where and what is printed:
+ "fullnoterefs", "noterefinterval", "noterefintro", "pagezeros",
+ "hidezeros", and "endnotesplit". The dependent package
+ cmsendnotes.sty can assist if you use endnotes instead of footnotes
+ in this context. It too has numerous options: "hyper",
+ "enotelinks", "noheader", "blocknotes", "split", "subheadername",
+ "headername", "runningname", and "nosubheader", alongside the new
+ commands \theendnotesbypart and \cmsintrosection. Four new
+ citation commands complete the provisions: \shortrefcite,
+ \shorthandrefcite, \shortcite*, and \shorthandcite*. Please see
+ section 4.4.4 of biblatex-chicago.pdf for all the details, and also
+ cms-noteref-demo.pdf for a brief example and explanation of some of
+ the functionality.
+
+ - I have ported, with modifications, the author-date package option
+ "nodates" to the notes & bibliography style. It is set to "true"
+ by default. In conjunction with the "nodatebrackets" and
+ "noyearbrackets" options it provides an alternative presentation of
+ uncertain dates. See section 4.4.2.
+
+ - Pursuant to a bug report by David Purton, I have recoded the
+ various \headlesscite commands and included a new one,
+ \Headlesscite, which is the actually functional way to enforce
+ capitalization at the start of such a citation, should you need to
+ do so.
+
+New author-date features:
+
+ - The "verbc" field, which is standard but unused in the styles
+ included in biblatex, allows the user fine-grained control over if
+ and when an "extradate" letter (1976_a_) will appear after the year
+ in citations and the list of references. See its documentation in
+ section 5.2 of biblatex-chicago.pdf.
+
+ - The new "authortitle" type and entry option allows you to provide
+ author-title citations in the text instead of author-date. The
+ "entrysubtype" value "classical" does the same, but there may be
+ cases where using such an "entrysubtype" is impossible. This is
+ set to "true" by default for Dataset entries.
+
+ - On the same subject, you can also use the new citation commands
+ \atcite and \atpcite to achieve the same end. The former prints a
+ plain citation, the latter places it in parentheses.
+
+ - In the default configuration, when you use a "shorthand" field the
+ style will now sort properly by that field, which is the first
+ thing to appear in reference list entries. If you set
+ "cmslos=false" in your preamble then this no longer applies, as the
+ "shorthand" no longer appears in the reference list.
+
+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, many
+ of them already mentioned in changelog items above. The
+ "compressyears" option is available and turned on by default, and
+ so is the "dashed" option. Most of the new ISO8601-2 Extended
+ Format date specifications are available, also, though time stamps
+ won't be printed, as that edition of the Manual is mostly silent
+ about them.
+
+
Release notes for version 1.0rc5 [2018-01-16]:
- Recent releases of biblatex have introduced some compatibility
@@ -1067,7 +1415,7 @@ Other New Features:
in the "location" field. If you want to cite a comment to a blog
or to other online material, the Review entry type, "entrysubtype"
"magazine" will serve. The "eventdate" dates the comment, and any
- timestamp that is required can go in "nameaddon." These
+ time stamp that is required can go in "nameaddon." These
instructions work in both styles.
- Photographs are no longer presented differently from other sorts of