# texlive[54809] Master/texmf-dist: biblatex-chicago (20apr20)

commits+karl at tug.org commits+karl at tug.org
Mon Apr 20 23:05:08 CEST 2020

Revision: 54809
http://tug.org/svn/texlive?view=revision&revision=54809
Author:   karl
Date:     2020-04-20 23:05:08 +0200 (Mon, 20 Apr 2020)
Log Message:
-----------
biblatex-chicago (20apr20)

Modified Paths:
--------------
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.pdf
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.tex
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-intro.pdf
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-intro.tex
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-sample.pdf
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-sample.tex
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-legal-sample.pdf
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-legal-sample.tex
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-notes-intro.pdf
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-notes-intro.tex
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-notes-sample.pdf
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-notes-sample.tex
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/dates-test.bib
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/legal-test.bib
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/notes-test.bib
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/biblatex-chicago.sty
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-authordate.bbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-authordate.cbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-dates-common.cbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-notes.bbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-notes.cbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-american.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-brazilian.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-british.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-finnish.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-french.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-german.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-icelandic.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-ngerman.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-norsk.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-norwegian.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-nynorsk.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-swedish.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cmsdocs.sty

-----------
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.pdf
trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.tex
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-authordate16.bbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-authordate16.cbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-dates-common16.cbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-notes16.bbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/chicago-notes16.cbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cms-dutch.lbx
trunk/Master/texmf-dist/tex/latex/biblatex-chicago/cmsendnotes.sty

===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/README	2020-04-19 23:48:48 UTC (rev 54808)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/README	2020-04-20 21:05:08 UTC (rev 54809)
@@ -1,52 +1,54 @@
IMPORTANT NOTE:

This is the package formerly known as biblatex-chicago-notes-df.  It
-is designed for use with the latest version (3.10) of biblatex.  The
-package contains the 16th-edition Chicago style files only, as I have
-removed the long-obsolete 15th-edition styles in preparation for the
-forthcoming 17th-edition revisions.  If you have used the package
-before, then you should be sure to consult the RELEASE file to find
-out what alterations you may need to make to your .bib files and
-document preambles to bring them up to date.  Most particularly please
-note that Biber is now required for the author-date styles, and very
-strongly advised for the notes & bibliography style (version 2.10 is
-designed for use with the latest biblatex).
+is designed for use with the latest version (3.14) of biblatex.  The
+package contains the 17th-edition Chicago style files, and I am also
+maintaining the 16th-edition files for those for whom they remain a
+necessity.  I strongly encourage all users to move to the 17th-edition
+styles, as they have received and will continue to receive many new
+features and fixes as compared with the older styles.  If you have
+used the package before, then you should be sure to consult the
+RELEASE file to find out what alterations you may need to make to your
+.bib files and document preambles to bring them up to date.  Most
+particularly please note that biber is now the required backend for
+all the included styles (version 2.14 is designed for use with the
+latest biblatex).

Biblatex-chicago contains three biblatex styles implementing the
-specifications of the Chicago Manual of Style, 16th edition.  The
+specifications of the Chicago Manual of Style, 17th edition.  The
"notes & bibliography" style was formerly available in the package
biblatex-chicago-notes-df, and is intended primarily for writers in
the humanities.  The "author-date" style, generally favored by writers
-in the sciences and social sciences, comes in two flavors.  The 16th
-edition of the Manual has brought the presentation of sources in this
-style much more into line with the notes & bibliography specification,
-especially regarding the formatting of titles.  If you still require
-titles to be capitalized sentence style, and article titles, for
-example, not to be enclosed in quotation marks, then you may now use
-these features while in all other respects following the 16th-edition
-specifications.
+in the sciences and social sciences, comes in two flavors.  Recent
+editions of the Manual have brought the presentation of sources in
+this style much more into line with the notes & bibliography
+specification, especially regarding the formatting of titles.  If you
+still require titles to be capitalized sentence style, and article
+titles, for example, not to be enclosed in quotation marks, then you
+which provides these features while in all other respects following
+the 17th-edition specifications.

-This is a beta release, but its feature set is already fairly
-extensive.  If you have used the package before you may, after
-perusing the RELEASE file, want to look at the changelog at the end of
-biblatex-chicago.pdf, which contains cross-references to more detailed
-file.  If you are just getting started, the best way to learn the
-system is to read the Quickstart section in that same file, then read
-either cms-notes-intro.pdf or cms-dates-intro.pdf, each of which are
-fully cross-referenced and contain links to the complete reference
-guide to both styles in sections 4 or 5 of biblatex-chicago.pdf.  The
-package also contains annotated .bib files (notes-test.bib and
-dates-test.bib) which each offer over 100 entries demonstrating how to
-present a wide range of sources, nearly all of them taken from the
-Chicago Manual of Style itself, so that you can compare the output of
-cms-dates-sample.pdf, cms-trad-sample.pdf) with the actual examples in
-the Manual.
+The package is under active development, but its feature set is
+already fairly extensive.  If you have used the package before you
+may, after perusing the RELEASE file, want to look at the changelog at
+the end of biblatex-chicago.pdf, which contains cross-references to
+more detailed explanations about how this update will affect parts of
+your .bib file.  If you are just getting started, the best way to
+learn the system is to read the Quickstart section in that same file,
+then read either cms-notes-intro.pdf or cms-dates-intro.pdf, each of
+which are fully cross-referenced and contain links to the complete
+reference guide to both styles in sections 4 or 5 of
+biblatex-chicago.pdf.  The package also contains annotated .bib files
+(notes-test.bib and dates-test.bib) which each offer over 100 entries
+demonstrating how to present a wide range of sources, nearly all of
+them taken from the Chicago Manual of Style itself, so that you can
+compare the output of your system (cms-notes-sample.tex,
+the actual examples in the Manual.

I have, wherever possible, attempted to maintain backward
compatibility with the standard biblatex styles, but there are a
@@ -65,22 +67,23 @@

Installation:

-With the recent proliferation of files, I have adopted the directory
-structure found in biblatex.zip, so if you want to place these files
-recommend the following, which should be familiar from the main
-biblatex package:
+If you want to place these files in your TeX directory tree instead of
+in your working directory, I recommend the following, which should be
+familiar from other packages:

- - The twenty files biblatex-chicago.sty, chicago-notes.cbx,
-   chicago-notes.bbx, chicago-authordate.cbx, chicago-authordate.bbx,
-   chicago-dates-common.cbx, cms-american.lbx, cms-brazilian.lbx,
-   cms-british.lbx, cms-finnish.lbx, cms-french.lbx, cms-german.lbx,
+ - The thirty files biblatex-chicago.sty, cmsendnotes.sty,
+   chicago-notes.cbx, chicago-notes.bbx, chicago-authordate.cbx,
+   chicago-notes16.cbx, chicago-notes16.bbx, chicago-authordate16.cbx,
+   cms-american.lbx, cms-brazilian.lbx, cms-british.lbx,
+   cms-dutch.lbx, cms-finnish.lbx, cms-french.lbx, cms-german.lbx,
cms-icelandic.lbx, cms-ngerman.lbx, cms-norsk.lbx,
-   cms-norwegian.lbx, cms-nynorsk.lbx, and cms-swedish.lbx are located
-   in the latex/ subdirectory, itself further subdivided into bbx/,
-   cbx/, and lbx/.  The entire contents of this latex/ directory,
-   including its subdirectories, can go in
+   cms-norwegian.lbx, cms-nynorsk.lbx, cms-swedish.lbx, and
+   cmsdocs.sty are located in the latex/ subdirectory.  The entire
+   contents of this latex/ directory can go in
<TEXMFLOCAL>/tex/latex/biblatex-contrib/biblatex-chicago, where
<TEXMFLOCAL> is the root of your local TeX installation -- for
example, and depending on your system, /usr/share/texmf-local,
@@ -89,21 +92,21 @@
remember to update your TeX file name database so that TeX can find
them.

- - The twenty files biblatex-chicago.tex, biblatex-chicago.pdf,
+ - The twenty-one files biblatex-chicago.tex, biblatex-chicago.pdf,
cms-notes-intro.tex, cms-notes-intro.pdf, cms-dates-intro.tex,
cms-legal-sample.tex, cms-notes-sample.pdf, cms-dates.sample.pdf,
-   dates-test.bib, legal-test.bib, and cmsdocs.sty can all be found in
-   the doc/ directory in the package archive, the last 18 in the
-   examples/ subdirectory.  You can place all of this in
+   cms-noteref-demo.pdf, notes-test.bib, dates-test.bib, and
+   legal-test.bib can all be found in the doc/ directory in the
+   package archive.  You can place all of this in
<TEXMFLOCAL>/doc/latex/biblatex-contrib/biblatex-chicago.

Changelog: See the RELEASE file, and also the end of
biblatex-chicago.pdf.

-Copyright (c) 2008-2018 David Fussner.  This package is
+Copyright (c) 2008-2020 David Fussner.  This package is
author-maintained.  This work may be copied, distributed and/or
modified under the conditions of the LaTeX Project Public License,
either version 1.3 of this license or (at your option) any later

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE
===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE	2020-04-19 23:48:48 UTC (rev 54808)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE	2020-04-20 21:05:08 UTC (rev 54809)
@@ -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,"
+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
+
+ - If you are loading the package the old-fashioned way, with biblatex
+   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
+   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
+   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
+
+ - 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
+   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.
+
+   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",
+   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
+
+
Release notes for version 1.0rc5 [2018-01-16]:

- Recent releases of biblatex have introduced some compatibility
@@ -1067,7 +1415,7 @@
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

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.pdf
===================================================================
(Binary files differ)

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.tex
===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.tex	2020-04-19 23:48:48 UTC (rev 54808)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.tex	2020-04-20 21:05:08 UTC (rev 54809)
@@ -1,7 +1,7 @@
%
% This file documents the biblatex-chicago package, which allows users
% of the biblatex package to format references according to the
-% Chicago Manual of Style, 16th edition.
+% Chicago Manual of Style, 17th edition.
%
\documentclass[a4paper]{article}
\usepackage[T1]{fontenc}
@@ -9,11 +9,18 @@
\usepackage[latin1]{inputenc}
\usepackage[american]{babel}
\usepackage[autostyle]{csquotes}
+\usepackage{tabularx}
+\usepackage{threeparttable}
+\usepackage{booktabs}
+\usepackage{afterpage}
+%\usepackage[showframe=true]{geometry}
\usepackage{vmargin}
\setpapersize{A4}
\setmarginsrb{1.65in}{.9in}{1.75in}{.6in}{0pt}{0pt}{12pt}{24pt}
\setlength{\marginparwidth}{1in}
+\setlength{\belowcaptionskip}{1em}
+filecolor=Teal]{hyperref}
% \usepackage{lmodern}
\usepackage[scaled=0.9]{ClearSans}
\usepackage[p]{zlmtt}
@@ -20,7 +27,7 @@
\usepackage{gentium}
%\usepackage[osf]{mathpazo}
%\usepackage[scaled]{helvet}
-\usepackage[pdftex]{xcolor}
+\usepackage[pdftex,hyperref,svgnames]{xcolor}
%\usepackage[dvips]{xcolor}
\newcommand{\mycolor}[1]{\textcolor[HTML]{228B22}{#1}}
\usepackage{multicol}
@@ -31,6 +38,11 @@
\newcommand{\colmarginpar}[1]{\mymarginpar{\mycolor{#1}}}
\newcommand{\mybigspace}{\vspace{\baselineskip}}
\newcommand{\mylittlespace}{\vspace{.5\baselineskip}}
+\newcolumntype{L}{>{\raggedright}p}
+\newcolumntype{H}{>{\sffamily\bfseries}l}
+%\renewcommand{\textfraction}{0.0}
+%\renewcommand{\topfraction}{1.0}
+\setlength{\intextsep}{0pt}
\makeatletter
\renewcommand{\section}{\@startsection
{section}%
@@ -60,6 +72,16 @@
{\baselineskip}%3.25ex \@plus1ex \@minus.2ex}%
{0mm}%
{}}%
+\long\def\@makecaption#1#2{%
+  \vskip -3.5\abovecaptionskip
+  \sbox\@tempboxa{\sffamily\bfseries #1: #2}%
+  \ifdim \wd\@tempboxa >\hsize
+    #1: #2\par
+  \else
+    \global \@minipagefalse
+    \hb at xt@\hsize{\hfil\box\@tempboxa\hfil}%
+  \fi
+  \vskip\belowcaptionskip}
\makeatother
\begin{document}
\begin{center}
@@ -67,7 +89,7 @@
Style files for biblatex

\vspace{.3\baselineskip}
-\sffamily\normalsize\bfseries David Fussner\qquad Version 1.0rc5 (beta) \\

\end{center}
@@ -75,6 +97,7 @@
\begin{multicols}{2}
\footnotesize
\tableofcontents
+\listoftables
\end{multicols}
\normalsize
\vspace{-.5\baselineskip}
@@ -81,36 +104,35 @@
\section{Notice}
\label{sec:Notice}

+\textbf{This package is still under active development.  The
\textsf{biblatex} package by Philipp Lehman, Philip Kime, Audrey
-  Boruvka, and Joseph Wright is now quite stable, but I am still in
-  the process of taking advantage of the many enhancements it has
-  accumulated in recent releases.  As it has for several years, The
-  \textsf{biblatex-chicago} package itself implements the 16th edition
-  of the \emph{Chicago Manual of Style}, which has recently been
-  replaced by the 17th edition.  This is therefore the last feature
-  release for the 16th edition, though bug-fix releases will continue
-  for a while yet.  In preparation for the switch to the 17th edition,
-  I am removing all 15th-edition files from the package, as they have
-  long since been obsolete.  I also very strongly encourage all users
-  who haven't already done so to switch to \textsf{Biber} as their
-  backend; it has long been a requirement for the author-date styles,
-  but it is now becoming indispensable for accessing all the features
-  of the notes \&\ bibliography style, as well.}
-\mylittlespace\\
-\textbf{I have tried to implement as much of the \emph{Manual's}
-  specification as possible, though undoubtedly some gaps remain.  If
-  it seems like this package could be of use to you, yet it doesn't do
-  something you need/want it to do, please feel free to let me know,
-  and of course any suggestions for solving problems more elegantly or
-  accurately would be most welcome.}
+  Boruvka, and Joseph Wright is now quite stable, but my task of
+  incorporating the many enhancements it has accumulated in recent
+  releases is ongoing.  The \textsf{biblatex-chicago} package itself
+  now implements the 17th edition of the \emph{Chicago Manual of
+    Style}, though I have made it possible to continue to use the 16th
+  edition files if that is imperative for you.  The package relies
+  heavily, in all styles, on using \textsf{biber} as its backend;
+  other backends will not work properly.}

+\mylittlespace \textbf{I have tried to implement as much of the
+  \emph{Manual's} specification as possible, though undoubtedly some
+  gaps remain.  If it seems like this package could be of use to you,
+  yet it doesn't do something you need/want it to do, please feel free
+  to let me know, and of course any suggestions for solving problems
+  more elegantly or accurately would be most welcome.}
+
\mylittlespace\textbf{Important Note:} If you have used
RELEASE file that came with the package.  It details the changes
you'll need to make to your .bib database in order for it to work
-properly with this release.  If you are new to these styles, please
+properly with this release.  I do strongly recommend that you switch
+to the new edition.  The changes, as you can see from the RELEASE
+file, in the main involve \emph{additions} to the specification, with
+required alterations to your existing .bib databases actually being
+rather rare.  If, on the other hand, you are new to these styles or to
+following section.

\section{Quickstart}
\label{quickstart}
@@ -132,13 +154,12 @@
parentheses --- (Author Year) --- keyed to a list of references where

-%\enlargethispage{-\baselineskip}
-
\mylittlespace The documentation you are reading covers all three of
these Chicago styles and their variants.  I recommend that users new
to the package read this Quickstart section first, perhaps then
passing on to whichever of the two introductory files,
-\textsf{cms-notes-intro.pdf} or \textsf{cms-dates-intro.pdf}, is
+\href{file:cms-notes-intro.pdf}{\textsf{cms-notes-intro.pdf}} or
+\href{file:cms-dates-intro.pdf}{\textsf{cms-dates-intro.pdf}}, is
relevant to their needs, returning here afterward for more details on
those parts of the functionality concerning which they still have
questions.  Much of what follows is relevant to all users, but I have
@@ -153,7 +174,8 @@
only appears separately in section~\ref{sec:fields:authdate}, s.v.\
\enquote{title.} Throughout the documentation, any \mycolor{green}
text \colmarginpar{\textsf{New!}} indicates something \mycolor{new} in
-this release.
+this release, while \textcolor{Teal}{\textbf{blue-green}} text is a
+clickable link to an external document.

\mylittlespace Here's a list of things you will need in order to use
\textsf{biblatex-chicago}:
@@ -160,11 +182,17 @@

\begin{itemize}{}{}
\item The \textsf{biblatex} package, of course!  The current version
-  --- 3.10 at the time of writing --- has received extensive testing,
+  --- 3.14 at the time of writing --- has received extensive testing,
and contains features and bug fixes upon which my code relies.
-  \textsf{Biblatex} requires several packages, and it strongly
-  recommends several more:
+  Please don't use any earlier version.  \textsf{Biblatex} requires
+  several packages, and it strongly recommends several more:
\begin{itemize}{}{}
+  \item \textsf{biber} --- the next-generation \textsc{Bib}\TeX\
+    replacement by Philip Kime and Fran\xE7ois Charette, available from
+    to work with \textsf{biblatex} 3.14 and \textsf{biblatex-chicago};
+    please note that any other backend will not produce accurate
+    results.
\item e-\TeX\ (required)
\item \textsf{etoolbox} --- available from CTAN (required)
\item \textsf{keyval} --- a standard package (required)
@@ -173,55 +201,55 @@
\item \textsf{babel} --- a standard package (\emph{strongly}
recommended)
\item \textsf{csquotes} --- available from CTAN (recommended).
-  \item \textsf{bibtex8} --- a replacement for \textsc{Bib}\TeX, which
-    can, with the right com\-mand-line switches, process very large
-    .bib files.  It also does the right thing when alphabetizing
-    non-ASCII entries.  It is available from CTAN, but please be aware
-    that this database parser no longer suffices if you are using the
-    Chica\-go author-date style with any version of \textsf{biblatex}
-    from version 1.5 onward.  For that style, and to take full
-    advantage of all the features of the notes \&\ bibliography style,
-    in particular its enhanced handling of cross references, you must
-    use the following:
-  \item \textsf{Biber} --- the next-generation \textsc{Bib}\TeX\
-    replacement by Philip Kime and Fran\xE7ois Charette, available from
-    with \textsf{biblatex} 3.10 and \textsf{biblatex-chicago}, and it
-    is required for users who are either using the author-date styles
-    or processing a .bib file in Unicode.  See
-    \textsf{cms-dates-intro.pdf} and, for example, the
-    \textsf{crossref} documentation in section~\ref{sec:entryfields},
-    below, for more details.
\end{itemize}
+\item With the changes both to \textsf{biblatex} and to
+  \textsf{biblatex-chicago} in this release, \textsf{biblatex-chicago}
+  itself now requires two packages, which are both loaded for you if
+  you load \textsf{biblatex-chicago.sty}, but which you'll have to
+  load manually if not.  They are:
+  \begin{itemize}{}{}
+  \item \mycolor{\textsf{nameref}} --- a standard package, available
+    in CTAN.
+  \item \mycolor{\textsf{xstring}} --- also standard and available in
+    CTAN.
+  \end{itemize}
\item The line:
\begin{quote}
-    \cmd{usepackage[notes]\{biblatex-chicago\}}
+    \verb+\usepackage[notes,backend=biber]{biblatex-chicago}+
\end{quote}
the line:
\begin{quote}
-    \cmd{usepackage[authordate,backend=biber]\{biblatex-chicago\}}
+    \verb+\usepackage[authordate,backend=biber]{biblatex-chicago}+
\end{quote}
to load the author-date style, or the line:
\begin{quote}
-      backend=biber]\{biblatex-chicago\}}
\end{quote}

-  to load the traditional variant of the author-date style.  Any other
-  options you usually pass to \textsf{biblatex} can be given to
-  large number of other parameters automatically, parameters whose
-  absence may surprise you when processing your documents.  You can
-  load the package via the usual \cmd{usepackage\{bibla\-tex\}},
-  \texttt{style=chicago-authordate}, but this is intended mainly for
-  those, probably experienced users, who wish to set much of the
-  low-level formatting of their documents themselves.  Please see
-  fuller discussion of the issues involved here.
-\item You can use \cmd{usepackage[notes,short]\{biblatex-chicago\}} to
+  to load the traditional variant of the author-date style.  If you
+  add \enquote{\texttt{16}} to any of the keys above, e.g.,
+  \begin{quote}
+    \verb+\usepackage[authordate16,backend=biber]{biblatex-chicago}+
+  \end{quote}
+  you can continue to use the 16th-edition styles, if that should
+  prove necessary.  Any other options you usually pass to
+  \textsf{biblatex} can be given to \textsf{biblatex-chicago} instead,
+  but loading it this way sets up a large number of other parameters
+  automatically, parameters whose absence may surprise you when
+  processing your documents.  You can load the package via the usual
+  \texttt{style=chicago-notes} or \texttt{style=chicago-authordate},
+  but this is intended mainly for those, probably experienced users,
+  who wish to set much of the low-level formatting of their documents
+  \mycolor{\textsf{xstring}} and \mycolor{\textsf{nameref}} manually
+  if you use this latter method.
+\item You can use
+  \verb+\usepackage[notes,short,backend=biber]{biblatex-chicago}+ to
get the short note format even in the first reference of a notes \&\
bibliography document, letting the bibliography provide the full
reference.
@@ -228,8 +256,8 @@
\item If you are accustomed to using the \textsf{natbib} compatibility
option with \textsf{biblatex}, then you can continue to do so with
\textsf{biblatex-chicago}.  If you are using
-  \cmd{usepackage\hfill\{biblatex-chicago\}} to load the package, then the
-  option must be the plain \texttt{natbib} rather than
+  \cmd{usepackage\hfill\{biblatex-chicago\}} to load the package, then
+  the option must be the plain \texttt{natbib} rather than
\texttt{natbib=true}.  If you use the latter, you'll get a
\textsf{keyval} error.  Please see sections~\ref{sec:useropts} and
\ref{sec:authuseropts}, below.
@@ -239,41 +267,54 @@
\textsf{babel}-less setups, and also those choosing \texttt{english}
as the main text language, should work out of the box.
\textsf{Biblatex-chicago} also provides (at least partial) support
-  for Brazilian Portuguese, British, Finnish, French, German,
-  Icelandic, Norwegian, and Swedish.  Please see below
+  for Brazilian Portuguese, British, \mycolor{Dutch}, Finnish, French,
+  German, Icelandic, Norwegian, and Swedish.  Please see below
(section~\ref{sec:international}) for a fuller explanation of all
the options.
-\item \textsf{chicago-authordate.bbx, chicago-authordate.cbx,
-  \textsf{chicago-dates-common.cbx}, \textsf{chicago-notes.bbx},\break
-  \textsf{chi\-ca\-go-notes.cbx}, \textsf{cms-american.lbx},
-  \mycolor{\textsf{cms-brazilian.lbx}}, \textsf{cms-british.lbx},
-  \textsf{cms-fin\-nish.lbx}, \textsf{cms-french.lbx},
-  \textsf{cms-german.lbx}, \textsf{cms-icelandic.lbx},
-  \textsf{cms-ngerman.lbx},\break \textsf{cms-norsk.lbx},
-  \textsf{cms-norwegian.lbx}, \textsf{cms-nynorsk.lbx},
-  \textsf{cms-swedish.lbx}, and \textsf{bibla\-tex-chicago.sty}, all
+\item {\small \textsf{chicago-authordate.cbx,
+    \textsf{chi\-ca\-go-authordate.bbx},
+    \textsf{chicago-notes.bbx},\break \textsf{cms-american.lbx},
+    \textsf{cms-brazilian.lbx}, \textsf{cms-british.lbx},
+    \mycolor{\textsf{cms-dutch.lbx}}, \textsf{cms-finnish.lbx},
+    \textsf{cms-french.lbx}, \textsf{cms-german.lbx},
+    \textsf{cms-icelandic.lbx}, \textsf{cms-ngerman.lbx},
+    \textsf{cms-norsk.lbx}, \textsf{cms-nor\-wegian.lbx},
+    \textsf{cms-nynorsk.lbx}, \textsf{cms-swedish.lbx},
+    \textsf{bibla\-tex-chicago.sty}, and \textsf{cmsdocs.sty}}, all
from \textsf{biblatex-chicago}, installed either in a system-wide
\TeX\ directory, or in the working directory where you keep your
-  *.tex files.  The .zip file from CTAN contains several
-  subdirectories to help keep the growing number of files organized,
-  so the files listed above can be found in the \texttt{latex/}
-  subdirectory, itself further divided into the \texttt{bbx/},
-  \texttt{cbx/}, and \texttt{lbx/} subdirectories.  If you install in
-  a system-wide directory, I suggest a standard layout using
-  \texttt{<TEXMFLOCAL>\slash
+  *.tex files.  The .zip file from CTAN contains subdirectories to
+  help keep the growing number of files organized, so the files listed
+  above can be found in the \texttt{latex/} subdirectory.  If you
+  install in a system-wide directory, I suggest a standard layout
+  using \texttt{<TEXMFLOCAL>\slash
tex/latex/bib\-latex-contrib/biblatex-chicago}, where\
\texttt{<TEXMFLOCAL>} is the root of your local \TeX\ installation
--- for example, and depending on your system and preferences,
\texttt{/usr/share/texmflocal}, \texttt{/usr/local/share/texmf}, or
\texttt{C:\textbackslash{}Local TeX Files\textbackslash}.  Then you
-  can copy the contents of the \texttt{latex/} directory there,
-  subdirectories and all.  (If you install into your working
-  directory, then you'll need to copy the files directly there,
-  without subdirectories.)  Of course, if you choose to place them
-  anywhere in the \texttt{texmf} tree, you'll need to update the file
-  name database to make sure \TeX\ can find them.
+  can copy the contents of the \texttt{latex/} directory there.  (If
+  you install into your working directory, then you'll need to copy
+  the files directly there, without subdirectories.)  Of course, if
+  you choose to place them anywhere in the \texttt{texmf} tree, you'll
+  need to update the file name database to make sure \TeX\ can find
+  them.
+    chicago-dates-com\-mon16.cbx}, \textsf{chicago-authordate16.bbx},
+  \textsf{chicago-notes16.cbx}, and \textsf{chicago-notes16.bbx},
+  which, as their names suggest, allow you to continue using the
+  16th-edition specifications alongside the most recent
+  \textsf{biblatex}, if your project requires this.  They can be found
+  in the same directory as the 17th-edition equivalents.
+\item The new dependent \LaTeX\ package
+  \mycolor{\textsf{cmsendnotes.sty}}, found with the previous files.
+  It offers additional functionality for those wishing to use the new
+  \mycolor{\texttt{noteref}} option with endnotes instead of
+  footnotes.  See section~\ref{sec:noteref}, below, and also
+  \href{file:cms-noteref-demo.pdf}{\textsf{cms-noteref-demo.pdf}}.
\item The very clear and detailed documentation of the
\textsf{biblatex} system, available in that package as
\textsf{biblatex.pdf}.  Here the authors explain why you might want
@@ -280,43 +321,50 @@
to use the system, the rules for constructing .bib files for it, and
the (numerous) methods at your disposal for modifying the formatted
output.
-\item The files \textsf{cms-notes-intro.pdf},
-  the first two of which contain introductions to some of the main
+\item The files
+  \href{file:cms-notes-intro.pdf}{\textsf{cms-notes-intro.pdf}},
+  \href{file:cms-dates-intro.pdf}{\textsf{cms-dates-intro.pdf}},
+  and\break
+  \href{file:cms-noteref-demo.pdf}{\textsf{cms-noteref-demo.pdf}}, the
+  first two of which contain introductions to some of the main
features of the Chicago styles, while the third documents some of
the alterations you might need to make to your .bib files to use the
-  easily to jump from notes or citations to an annotated bibliography
-  or reference list, and thence to the .bib entries themselves.  If
-  you ensure that these three are in the \texttt{examples} directory
-  just below this one, marginal links there will take you to further
-  discussions here.  The file \textsf{cmsdocs.sty} contains code and
-  kludges designed specifically for compiling
-  \textsf{cms-dates-intro.tex}, \textsf{cms-notes-intro.tex} and
-  yourself anywhere else, as it redefines and interferes with some of
-  the macros from the main package.
+  \texttt{trad} style.  The fourth gives a brief example of the usage
+  of the \mycolor{\texttt{noteref}} package option to the notes \&\
+  bibliography style.  All four are fully hyperlinked, the first three
+  in particular allowing you easily to jump from notes or citations to
+  an annotated bibliography or reference list, and thence to the .bib
+  entries themselves.  If you ensure that all four are in the same
+  directory as the document you are reading (the \TeX\ Live default),
+  marginal links there will take you to further discussions here.  The
+  file \textsf{cmsdocs.sty} contains code and kludges designed
+  specifically for compiling \textsf{cms-dates-intro.tex},
+  please \emph{do not} load it yourself anywhere else, as it redefines
+  and interferes with some of the macros from the main package.
\item The annotated bibliography files \textsf{notes-test.bib} and
\textsf{dates-test.bib}, and the not-yet-annotated
-  \mycolor{\textsf{legal-test.bib}}, all of which will acquaint you
-  with many of the details on how to get started constructing your own
-  .bib files for use with the two \textsf{biblatex-chicago} styles.
-\item The files \textsf{cms-notes-sample.pdf},
-  \mycolor{\textsf{cms-legal-sample.pdf}}.  The first shows how my
-  system processes \textsf{notes-test.bib} and
+  \textsf{legal-test.bib}, all of which will acquaint you with many of
+  the details on how to get started constructing your own .bib files
+  for use with the three \textsf{biblatex-chicago} styles.
+\item The files
+  \href{file:cms-notes-sample.pdf}{\textsf{cms-notes-sample.pdf}},
+  \href{file:cms-dates-sample.pdf}{\textsf{cms-dates-sample.pdf}},
+  \href{file:cms-legal-sample.pdf}{\textsf{cms-legal-sample.pdf}}.
+  The first shows how my system processes \textsf{notes-test.bib} and
\textsf{cms-notes-sample.tex}, in both footnotes and bibliography,
the second and third are the result of processing
\textsf{dates-test.bib} with \textsf{cms-dates-sample.tex} or
-  \mycolor{\textsf{legal-test.bib}} using
-  \mycolor{\textsf{cms-legal-sam\-ple.tex}}.  All of these files are in
-  \texttt{doc/examples/}, and the \textsf{sample} files, aside from
-  the last named, are mainly included for testing purposes.
+  \textsf{legal-test.bib} using \textsf{cms-legal-sam\-ple.tex}.  All
+  of these files are in \texttt{doc/}, and the \textsf{sample} files,
+  aside from the last named, are mainly included for testing purposes.
\item The file you are reading, \textsf{biblatex-chicago.pdf}, which
aims to be as complete a description as possible of the rules for
creating a .bib file that will, when processed by \LaTeX\ and
-  \textsc{Bib}\TeX, at least somewhat ease the burden when you try to
+  \textsf{biber}, at least somewhat ease the burden when you try to
implement the \emph{Chicago Manual of Style}'s specifications.
These docs may seem frustratingly over-long, but remember that you
only need to read the part(s) that apply to the style in which you
@@ -326,17 +374,13 @@
preparation for the others.  If you have used a previous version of
this package, please pay particular attention to the sections on
Obsolete and Deprecated Features, starting on
-  page~\pageref{deprec:obsol}.  You will find the sixteen previous
+  page~\pageref{deprec:obsol}.  You will find the nineteen previous
files in the \texttt{doc/} subdirectory once you've extracted
\textsf{biblatex-chicago.zip}.  If you wish to place them in a
system-wide directory, I would recommend:\,\,\,
\texttt{<TEXMFLOCAL>/doc/latex/biblatex-contrib/biblatex-chicago},\\
all the while remembering, of course, to update the file name
-  database afterward.  (Let me reiterate, also, that if you currently
-  have quoted material in your .bib file, and are using \cmd{enquote}
-  or the standard \LaTeX\ mechanisms there, then the simplest
-  procedure is always to use \cmd{mkbibquote} instead in order to
-  ensure that punctuation works out right.)
+  database afterward.
\item Access to a copy of \emph{The Chicago Manual of Style} itself,
hope to present here.  It should always be your first port of call
@@ -346,7 +390,7 @@
\label{sec:lppl}

-Copyright \xA9 2008--2018 David Fussner.  This package is
+Copyright \xA9 2008--2020 David Fussner.  This package is
author-maintained.  This work may be copied, distributed and/or
modified under the conditions of the \LaTeX\ Project Public License,
either version 1.3 of this license or (at your option) any later
@@ -377,28 +421,30 @@
for the notes \&\ bibliography style, and her page-number-compression
code for both styles from the
\href{http://tex.stackexchange.com/questions/44492/biblatex-chicago-style-page-ranges}{same
-  site}.  I am very grateful to Gustavo Barros for the new Brazilian
-Portuguese localization, to Stefan Bj\xF6rk for the Swedish localization,
-to Antti-Juhani Kaijahano for the Finnish localization, to Baldur
-Kristinsson for providing the Icelandic localization, and to H\xE5kon
-Malmedal for the Norwegian localizations.  Kazuo Teramoto and Gildas
-Hamel both sent patches to improve the package, and Arne Skj\xE6rholt
-provided some code to get me started on the new \cmd{gentextcite}
-commands. There may be other \LaTeX\ code I've appropriated and
-forgotten, in which case please remind me.  Finally, Charles Schaum
-and Joseph Reagle Jr.\ were both extremely generous with their help
-and advice during the development of this package, and have both
-continued indefatigably to test it and suggest needed improvements.
-They were particularly instrumental in encouraging the greatest
-possible degree of compatibility with other \textsf{biblatex} styles.
-Indeed, if the task of adapting .bib files for use with the Chicago
-style seems onerous now, you should have tried it before they got
-their hands on it.
+  site}.  The dependent package \mycolor{\textsf{cmsendnotes.sty}}
+contains code by John Lavagnino and Ulrich Dirr.  I am very grateful
+to Wouter Lancee for the new Dutch localization, to Gustavo Barros for
+the Brazilian Portuguese localization, to Stefan Bj\xF6rk for the Swedish
+localization, to Antti-Juhani Kaijahano for the Finnish localization,
+to Baldur Kristinsson for providing the Icelandic localization, and to
+H\xE5kon Malmedal for the Norwegian localizations.  Kazuo Teramoto and
+Gildas Hamel both sent patches to improve the package, and Arne
+Skj\xE6rholt provided some code to get me started on the
+\cmd{gentextcite} commands. There may be other \LaTeX\ code I've
+appropriated and forgotten, in which case please remind me.  Finally,
+Charles Schaum and Joseph Reagle Jr.\ were both extremely generous
+with their help and advice during the development of this package, and
+have both continued indefatigably to test it and suggest needed
+improvements.  They were particularly instrumental in encouraging the
+greatest possible degree of compatibility with other \textsf{biblatex}
+styles.  Indeed, if the task of adapting .bib files for use with the
+Chicago style seems onerous now, you should have tried it before they
+got their hands on it.

\section{Detailed Introduction}
\label{sec:Intro}

-The \emph{Chicago Manual of Style}, implemented here in its 16th
+The \emph{Chicago Manual of Style}, implemented here in its 17th
edition, has long, in America at least, been one of the most
influential style guides for writers and publishers.  While one's
choices are now perhaps more extensive than ever, the \emph{Manual} at
@@ -409,12 +455,10 @@
your publisher's choice) of the \emph{Manual} as a style guide seems
set to be a happy one.

-%% %\enlargethispage{-\baselineskip}
-
\mylittlespace These very strengths, however, also make the style
difficult to use.  Admittedly, the \emph{Manual} emphasizes
consistency within a work, as opposed to rigid adherence to the
-specification, at least when writer and publisher agree (14.70).
+specification, at least when writer and publisher agree (14.4).
Sometimes a publisher demands such adherence, however, and anyone who
has attempted to produce it may well come away with the impression
that the specification itself is somewhat idiosyncratic in its
@@ -428,7 +472,7 @@
overburden the writer who wants to comply with the standard.  Many of
these complexities, in truth, make the specification very nearly
impossible to implement straightforwardly in a system like
-\textsc{Bib}\TeX\ --- options multiply, each requiring a particular
+\textsf{biblatex} --- options multiply, each requiring a particular
sort of formatting, until one almost reaches the point of believing
that every individual book or article should have its own entry type.
Completeness and usability tend each to exclude the other, so the code
@@ -474,8 +518,6 @@
important to you, until you have determined that this package does
what you need/want it to do.

-% %\enlargethispage{\baselineskip}
-
\mylittlespace When I first began working on this package, I made the
decision to alter as little as possible the main files from Lehman's
\textsf{biblatex}, so that my .bbx and .cbx files would use his
@@ -499,18 +541,18 @@
have also duplicated a lot of the information in
\textsf{biblatex.pdf}, which I hope won't badly annoy expert users of
the system.  Headings in \mycolor{green} \colmarginpar{\textsf{New in
-    this release}} indicate material new to this release, or
-occasionally old material that has undergone significant revision.
-Numbers in parentheses refer to sections of the \emph{Chicago Manual
-  of Style}, 16th edition.  The file \textsf{notes-test.bib} contains
-many examples from the \emph{Manual} which, when processed using
+    this release}} indicate either material new to this release or old
+material that has undergone significant revision.  Numbers in
+parentheses refer to sections of the \emph{Chicago Manual of Style},
+17th edition.  The file \textsf{notes-test.bib} contains many examples
+from the \emph{Manual} which, when processed using
\textsf{biblatex-chicago-notes}, should produce the same output as you
see in the \emph{Manual} itself, or at least compliant output, where
the specifications are vague or open to interpretation, a state of
affairs which does sometimes occur.  I have provided
-\textsf{cms-notes-sample.pdf}, which shows how my system processes
-\textsf{notes-test.bib}, and I have also included the reference keys
-from the latter file below in parentheses.
+\href{file:cms-notes-sample.pdf}{\textsf{cms-notes-sample.pdf}}, which
+shows how my system processes \textsf{notes-test.bib}, and I have also
+included the reference keys from the latter file below in parentheses.

\subsection{Entry Types}
\label{sec:entrytypes}
@@ -517,21 +559,24 @@

The complete list of entry types currently available in
\textsf{biblatex-chicago-notes}, minus the odd \textsf{biblatex}
-alias, is as follows: \mycolor{\textbf{article}}, \textbf{artwork},
-\textbf{audio}, \textbf{book}, \textbf{bookinbook}, \textbf{booklet},
-\textbf{collection}, \textbf{customc}, \textbf{image},
+alias, is as follows: \textbf{article}, \mycolor{\textbf{artwork}},
+\mycolor{\textbf{audio}}, \mycolor{\textbf{book}},
+\textbf{bookinbook}, \textbf{booklet}, \textbf{collection},
+\textbf{customc}, \mycolor{\textbf{dataset}}, \textbf{image},
\textbf{inbook}, \textbf{incollection}, \textbf{inproceedings},
-\textbf{inreference}, \mycolor{\textbf{jurisdiction}},
-\mycolor{\textbf{legal}}, \mycolor{\textbf{legislation}},
-\textbf{letter}, \textbf{manual},\textbf{misc}, \textbf{music},
-\textbf{mvbook}, \textbf{mvcollection}, \textbf{mvproceedings},
-\textbf{mvreference}, \textbf{online} (with its alias \textbf{www}),
-\textbf{patent}, \textbf{periodical}, \textbf{proceedings},
-\textbf{reference}, \mycolor{\textbf{report}} (with its alias
-\textbf{techreport}), \mycolor{\textbf{review}}, \textbf{suppbook},
-\textbf{suppcol\-lec\-tion}, \textbf{suppperiodical}, \textbf{thesis}
-(with its aliases \textbf{mastersthesis} and \textbf{phdthesis}),
-\mycolor{\textbf{unpublished}}, and \textbf{video}.
+\mycolor{\textbf{inreference}}, \textbf{jurisdiction}, \textbf{legal},
+\textbf{legislation}, \textbf{letter}, \textbf{manual}, \textbf{misc},
+\mycolor{\textbf{music}}, \mycolor{\textbf{mvbook}},
+\mycolor{\textbf{mvcollection}}, \mycolor{\textbf{mvproceedings}},
+\mycolor{\textbf{mvreference}}, \mycolor{\textbf{online}} (with its
+alias \textbf{www}), \textbf{patent}, \mycolor{\textbf{performance}},
+\textbf{periodical}, \textbf{proceedings}, \textbf{reference},
+\textbf{report} (with its alias \textbf{techreport}),
+\mycolor{\textbf{review}}, \mycolor{\textbf{standard}},
+\textbf{suppbook}, \textbf{suppcollection}, \textbf{suppperiodical},
+\textbf{thesis} (with its aliases \textbf{mastersthesis} and
+\textbf{phdthesis}), \textbf{unpublished}, and
+\mycolor{\textbf{video}}.

\mylittlespace What follows is an attempt to specify all the
differences between these types and the standard provided by
@@ -544,22 +589,20 @@
seemed to me better to gather information pertaining to fields in the
next section.

-%\enlargethispage{\baselineskip}
-
-\mybigspace The \colmarginpar{\textbf{article}} \emph{Chicago Manual of
-  Style} (14.170) recognizes three different sorts of periodical
+\mybigspace The \mymarginpar{\textbf{article}} \emph{Chicago Manual of
+  Style} (14.164) recognizes three different sorts of periodical
publication, \enquote{journals,} \enquote{magazines,} and
-\enquote{newspapers.} The first (14.172) includes \enquote{scholarly
-  or professional periodicals available mainly by subscription,} while
-the second refers to \enquote{weekly or monthly} publications that are
-\enquote{available either by subscription or in individual issues at
-  bookstores or newsstands or online.}  \enquote{Magazines} will tend
-to be \enquote{more accessible to general readers,} and typically
-won't have a volume number.  Indeed, by fiat I declare that should you
-need to refer to a journal that identifies its issues mainly by year,
-month, or week, then for the purposes of
-\textsf{biblatex-chicago-notes} such a publication is a
-\enquote{magazine,} and not a \enquote{journal.}
+\enquote{newspapers.} The first (14.166) is \enquote{a scholarly or
+  professional periodical available mainly by subscription,} while the
+second refers to \enquote{weekly or monthly (or sometimes daily)}
+publications that are \enquote{available in individual issues at
+  libraries or bookstores or newsstands or offered online, with or
+  without a subscription.}  \enquote{Magazines} will tend to be
+\enquote{more accessible to general readers,} and typically won't have
+a volume number.  Indeed, by fiat I declare that should you need to
+refer to a journal that identifies its issues mainly by year, month,
+or week, then for the purposes of \textsf{biblatex-chicago-notes} such
+a publication is a \enquote{magazine,} and not a \enquote{journal.}

\mylittlespace For articles in \enquote{journals} you can simply use
the traditional \textsc{Bib}\TeX\ --- and indeed \textsf{biblatex} ---
@@ -568,37 +611,33 @@
however, you need to refer to a \enquote{magazine} or a
\enquote{newspaper,} then you need to add an \textsf{entrysubtype}
field containing the exact string \texttt{magazine} or, now, its
-synonym \mycolor{\texttt{newspaper}}.  The main formatting differences
-between a \texttt{magazine/newspaper} and a plain \textsf{article} are
-that the year isn't placed within parentheses, and that page numbers
-are set off by a comma rather than a colon.  Otherwise, the two sorts
-of reference have much in common.  (For \textsf{article}, see
-\emph{Manual} 14.175--198; batson, beattie:crime, friedman:learning,
+synonym \texttt{newspaper}.  The main formatting differences between a
+\texttt{magazine/newspaper} and a plain \textsf{article} are that the
+year isn't placed within parentheses, and that page numbers are set
+off by a comma rather than a colon.  Otherwise, the two sorts of
+reference have much in common.  (For \textsf{article}, see
+\emph{Manual} 14.168--87; batson, beattie:crime, friedman:learning,
garaud:gatine, garrett, hlatky:hrt, kern, lewis, loften:hamlet,
mcmillen:antebellum, rozner:liberation, saberhagen:beluga,
warr:ellison, white:callimachus. For \textsf{entrysubtype}
-\texttt{magazine}, see 14.181, 14.199--202; assocpress:gun,
-morgenson:market, reaves:rosen, sten\-ger:privacy.)
+\texttt{magazine}, see 14.171, 14.188--200; assocpress:gun,
+morgenson:market, reaves:rosen, stenger:privacy.)

\mylittlespace It gets worse.  The \emph{Manual} treats reviews (of
books, plays, performances, etc.) as a sort of recognizable subset of
\enquote{journals,} \enquote{magazines,} and \enquote{newspapers,}
distinguished mainly by the way one formats the title of the review
-itself.  In \textsf{biblatex 0.7}, happily, Lehman provided a
-\textsf{review} entry type which will handle a large subset of such
-citations, though not all.  The key rule is this: if a review has a
-separate, non-generic title (gibbard; osborne:poison) in addition to
-something that reads like \enquote{review of \ldots,} then you need an
-\textsf{article} entry, with or without the \texttt{magazine}
-\textsf{entrysubtype}, depending on the sort of publication containing
-the review.  If the only title is the generic \enquote{review of
-  \ldots,} for example, then you'll need the \textsf{review} entry
-type, with or without this same \textsf{entrysubtype} toggle using
-\texttt{magazine}.  On \textsf{review} entries, see below.  (The
-curious reader will no doubt notice that the code for formatting any
-sort of review still exists in \textsf{article}, as it was initially
-designed for \textsf{biblatex 0.6}, but this new arrangement is
-somewhat simpler and therefore, I hope, better.)
+itself.  \textsf{Biblatex} provides a \textsf{review} entry type which
+will handle a large subset of such citations, though not all.  The key
+rule is this: if a review has a separate, non-generic title (gibbard;
+\enquote{review of \ldots,} then you need an \textsf{article} entry,
+with or without the \texttt{magazine} \textsf{entrysubtype}, depending
+on the sort of publication containing the review.  If the only title
+is the generic \enquote{review of \ldots,} for example, then you'll
+need the \textsf{review} entry type, with or without this same
+\textsf{entrysubtype} toggle using \texttt{magazine}.  On
+\textsf{review} entries, see below.

\mylittlespace In the case of a review with a specific as well as a
generic title, the former goes in the \textsf{title} field, and the
@@ -608,23 +647,27 @@
\textsf{biblatex-chicago-notes} uses it in just this way, with the
additional wrinkle that it can, if needed, replace the \textsf{title}
entirely, and this in, effectively, any entry type, providing a fairly
-powerful, if somewhat complicated, tool for getting \textsc{Bib}\TeX\
+powerful, if somewhat complicated, tool for getting \textsf{biblatex}
to do what you want.  Here, however, if all you need is a
\textsf{titleaddon}, then you want to switch to the \textsf{review}
type, where you can simply use the \textsf{title} field instead.

-\mylittlespace \textsf{Biblatex-chicago} \colmarginpar{New!} now also,
-at the behest of Bertold Schweitzer, supports the \textsf{relatedtype}
-\mycolor{\texttt{reviewof}}, which allows you to use the
-\textsf{related} mechanism to provide information about the work being
-reviewed.  This may be particularly helpful if you need to cite
-multiple reviews of the same work, but in any case the usual
-distinction between \textsf{article} and \textsf{review} entries still
-holds, with the \textsf{related} entry's \textsf{title} providing the
-\textsf{titleaddon} in the former type and the \textsf{title} in the
-latter.  Please see section \ref{sec:related} for further details.
+\mylittlespace \textsf{Biblatex-chicago} also, at the behest of
+Bertold Schweitzer, supports the \textsf{relatedtype}
+\texttt{reviewof}, which allows you to use the \textsf{related}
+mechanism to provide information about the work being reviewed,
+thereby simplifying how much information you need to provide in the
+reviewing entry.  In particular, it relieves you of the need to
+construct \textsf{titleaddon} or \textsf{title} fields like:
+\texttt{review of \textbackslash mkbibemph\{Book Title\} by Author
+  Name}, as the \textsf{related} entry's \textsf{title} automatically
+provides the \textsf{titleaddon} in the \textsf{article} type and the
+\textsf{title} in the \textsf{review} type, with the \textsf{related}
+mechanism providing the connecting string.  This may be particularly
+helpful if you need to cite multiple reviews of the same work; please
+see section \ref{sec:related} for further details.

-\mylittlespace No less than nine more things need explication here.
+\mylittlespace No less than ten more things need explication here.
First, since the \emph{Manual} specifies that much of what goes into a
\textsf{titleaddon} field stays unformatted --- no italics, no
quotation marks --- this plain style is the default for such text,
@@ -640,40 +683,36 @@
should go, as usual, in a \textsf{title} field, and the latter in
\textsf{titleaddon}.  As with reviews proper, if there is only the
generic title, then you want the \textsf{review} entry type.  (See
-14.203, 14.205, 14.208; morgenson:market, reaves:rosen.)
+14.191, 14.195--96; morgenson:market, reaves:rosen.)

-\mylittlespace Third, the 16th edition of the \emph{Manual} has, I
-believe, subtly changed its recommendations in the case of
-\enquote{unsigned newspaper articles or features} (14.207).
-Unfortunately, these changes aren't entirely clear to me.  First, it
-suggests that such pieces are \enquote{best dealt with in text or
-  notes.}  If, however, \enquote{a bibliography entry should be
-  needed, the name of the newspaper stands in place of the author.}
-The examples it provides, therefore, suggest quite different
-treatments of the same material in notes and bibliography, and they
-don't at any point that I can see recommend a format for short notes.
-I've implemented these recommendations fairly literally, which means
-that in an \textsf{article} entry, \textsf{entrysubtype}
-\texttt{magazine}, or in a \textsf{review} entry,
-\textsf{entrysubtype} \texttt{magazine}, and \emph{only} in such
-entries, a missing \textsf{author} field results in the name of the
-periodical (in the \textsf{journaltitle} field) being used as the
-missing author, but \emph{only} in the bibliography and in short
-notes.  In long notes, the \textsf{title} will appear first, before
-the \textsf{journaltitle}.  Note that the use of the name of the
-newspaper as an author creates sorting issues in the bibliography,
-issues that will mostly be solved for you if you use \textsf{Biber} as
-the backend.  If you don't, or if the \textsf{journaltitle} begins
-with a definite or indefinite article with which you can't dispense,
-then you'll need a \textsf{sortkey} field to ensure that the
-bibliography entry is alphabetized correctly.  (See
-lakeforester:pushcarts and, for the sorting issue,
+\mylittlespace Third, the \emph{Manual} has slightly complicated
+instructions concerning \enquote{unsigned newspaper articles or
+  features} (14.199).  First, it suggests that such pieces are
+\enquote{best dealt with in text or notes.}  If, however, \enquote{a
+  bibliography entry should be needed, the title of the newspaper
+  stands in place of the author.}  The examples it provides,
+therefore, suggest quite different treatments of the same material in
+notes and bibliography, and they don't at any point that I can see
+recommend a format for short notes.  I've implemented these
+recommendations fairly literally, which means that in an
+\textsf{article} entry, \textsf{entrysubtype} \texttt{magazine}, or in
+a \textsf{review} entry, \textsf{entrysubtype} \texttt{magazine}, and
+\emph{only} in such entries, a missing \textsf{author} field results
+in the name of the periodical (in the \textsf{journaltitle} field)
+being used as the missing author, but \emph{only} in the bibliography
+and in short notes.  In long notes, the \textsf{title} will appear
+first, before the \textsf{journaltitle}.  Note that the use of the
+name of the newspaper as an author creates sorting issues in the
+bibliography, issues that will mostly be solved for you if you use
+\textsf{Biber} as the backend.  If you don't, or if the
+\textsf{journaltitle} begins with a definite or indefinite article
+with which you can't dispense, then you'll need a \textsf{sortkey}
+field to ensure that the bibliography entry is alphabetized correctly.
+(See lakeforester:pushcarts and, for the sorting issue,
\cmd{DeclareSortingTemplate} in section~\ref{sec:formatopts} below.)

-\enlargethispage{\baselineskip}
-
\mylittlespace Fourth, Bertold Schweitzer has pointed out, following
-the \emph{Manual} (14.192), that while an \textsf{issuetitle} often
+the \emph{Manual} (14.183), that while an \textsf{issuetitle} often
has an \textsf{editor}, it is not too unusual for a \textsf{title} to
have, e.g., an \textsf{editor} and/or a \textsf{translator}.  In order
to allow as many permutations as possible on this theme, I have
@@ -687,24 +726,14 @@
rules still apply --- cf.\ \textsf{editor} and \textsf{editortype} in
section~\ref{sec:entryfields}, below.

-\mylittlespace Fifth, if you've been using
-\textsf{biblatex-chicago-notes} for a while, you may remember using
-the single-letter \cmd{bibstring} mechanism in order to help
-\textsf{biblatex} decide where to capitalize a wide variety of strings
-in numerous entry fields.  This mechanism was particularly common in
-all the periodical types, but if you've had a look in
-\textsf{notes-test.bib} while following this documentation, you'll
-have noticed that it no longer appears there.  The regular whole-word
-bibstrings still work as normal, but the single-letter ones are
-obsolete, replaced by the \cmd{autocap} macro, which itself only
-occurs twice in \textsf{notes-test.bib}.  Basically, in certain
-fields, just beginning your data with a lowercase letter activates the
-mechanism for capitalizing that letter depending on its context within
-a note or bibliography entry.  Please see \textbf{\textbackslash
-  autocap} below for the details, but both the \textsf{titleaddon} and
-\textsf{note} fields are among those treating their data this way, and
-since both appear regularly in \textsf{article} entries, I thought the
-problem merited a preliminary mention here.
+\mylittlespace Fifth, in certain fields just beginning your data with
+a lowercase letter activates the mechanism for capitalizing that
+letter depending on its context within a note or bibliography entry.
+Please see \cmd{autocap} in section~\ref{sec:formatcommands} below for
+the details, but both the \textsf{titleaddon} and \textsf{note} fields
+are among those treating their data this way, and since both appear
+regularly in \textsf{article} entries, I thought the problem merited a
+mention here.

\mylittlespace Sixth, if you need to cite an entire issue of any sort
of periodical, rather than one article in an issue, then the
@@ -714,55 +743,78 @@
normally be the \textsf{issuetitle} in the \textsf{title} field and
retaining the usual \textsf{journaltitle} field, but this arrangement
isn't compatible with standard \textsf{biblatex}.)  The \textsf{note}
-field is where you place something like \enquote{special issue} (with
-the small \enquote{s} enabling the automatic capitalization routines),
-whether you are citing one article or the whole issue
-(conley:fifthgrade, good:wholeissue).  Indeed, this is a somewhat
-specialized use of \textsf{note}, and if you have other sorts of
-information you need to include in an \textsf{article},
-\textsf{periodical}, or \textsf{review} entry, then you shouldn't put
-it in the \textsf{note} field, but rather in \textsf{titleaddon} or
+field is where you place something like \enquote{special issue} or
+\enquote{supplement} (with the small \enquote{s} enabling the
+automatic capitalization routines), whether you are citing one article
+or the whole issue (14.178--79; conley:fifthgrade, good:wholeissue).
+Indeed, this is a somewhat specialized use of \textsf{note}, and if
+you have other sorts of information you need to include in an
+\textsf{article}, \textsf{periodical}, or \textsf{review} entry, then
+you shouldn't put it in the \textsf{note} field, but rather in

-\mylittlespace Seventh, if you wish to cite a television or radio
-\texttt{magazine} is the place for it.  The name of the program would
-go in \textsf{journaltitle}, with the name of the episode in
+\mylittlespace Seventh, if you wish to cite certain kinds of
+also news segments or other \enquote{journalistic} material, then the
+\textsf{article} type, \textsf{entrysubtype} \texttt{magazine} is the
+place for it.  The name of the program as a whole would go in
+\textsf{journaltitle}, with the name of the episode or segment in
\textsf{title}, and the network's name in the \textsf{usera} field.
Of course, if the piece you are citing has only a generic name (an
interview, for example), then the \textsf{review} type would be the
-best place for it.  (8.185, 14.221; see bundy:macneil for an example
-of how this all might look in a .bib file.  Commercial recordings of
-such material would need one of the audiovisual entry types, probably
-\textsf{audio} or \textsf{video} [friends:leia], while recordings from
-archives fit best either into \textsf{online} or into \textsf{misc}
-entries with an \textsf{entrysubtype} [coolidge:speech,
-roosevelt:speech].)
+best place for it (8.189, 14.213; see bundy:macneil for an example
+of how this all might look in a .bib file.)  Other sorts of broadcast,
+usually accessible through commercial recordings, would need one of
+the audiovisual entry types, probably \textsf{audio}
+(danforth:podcast) or \textsf{video} (friends:leia), while recordings
+from archives fit best either into \textsf{online} or into
+\textsf{misc} entries with an \textsf{entrysubtype} (coolidge:speech,
+roosevelt:speech).

-\mylittlespace Eighth, the 16th edition of the \emph{Manual}
-(14.243--6) specifies that blogs and other, similar online material
-should be presented like \textsf{articles}, with \texttt{magazine}
-\textsf{entrysubtype} (ellis:blog).  The title of the specific entry
-goes in \textsf{title}, the general title of the blog goes in
-\textsf{journaltitle}, and the word \enquote{\texttt{blog}} in the
-\textsf{location} field (though you could just use special formatting
-in the \textsf{journaltitle} field itself, which may sometimes be
-necessary).  Comments on blogs, with generic titles like
-\enquote{comment on} or \enquote{reply to,} need a \textsf{review}
-entry with the same \textsf{entrysubtype}.  Such comments make
-particular use of the \textsf{eventdate} and of the \textsf{nameaddon}
-fields; please see the documentation of \textbf{review}, below.
+\mylittlespace Eighth, the \emph{Manual} (14.208) specifies that blogs
+and other, similar online material should be presented like
+\textsf{articles}, with \texttt{magazine} \textsf{entrysubtype}
+(ellis:blog), and needn't appear in a bibliography.  The title of the
+specific entry goes in \textsf{title}, the general title of the blog
+goes in \textsf{journaltitle}, and the word \enquote{\texttt{blog}} in
+the \textsf{location} field (though you could just use special
+formatting in the \textsf{journaltitle} field itself, which may
+sometimes be necessary).  The 17th \colmarginpar{New!} edition
+specifies that \enquote{blogs that are part of a larger publication
+  should include the name of that publication.}  This usually involves
+a newspaper or magazine which also publishes various blogs on its
+website, and it means that such entries need a more general title than
+the \textsf{journaltitle}.  It's not standard \textsf{biblatex} or
+anything, but you can now put such information in \textsf{maintitle}
+(with \textsf{mainsubtitle} and \textsf{maintitleaddon}, if needed),
+but only in \textsf{article} and \textsf{review} entries with a
+\texttt{magazine} \textsf{entrysubtype} (amlen:hoot).  To cite a whole
+blog, you'll need the \textsf{periodical} entry type, with a
+\textsf{title} instead of a \textsf{journaltitle}, along with a
+(possible) \textsf{maintitle}.  Comments on blogs, with generic titles
+like \enquote{comment on} or \enquote{reply to,} need a
+\textsf{review} entry with the same \textsf{entrysubtype}.  Such
+comments make particular use of the \textsf{eventdate} and of the
+\textbf{review}, below, and also of the \textsf{relatedtype}
+\mycolor{\texttt{commenton}} in section~\ref{sec:related}.

-\mylittlespace Finally, the special \textsf{biblatex} field
+\mylittlespace Ninth, the special \textsf{biblatex} field
\textsf{shortjournal} allows you to present shortened
\textsf{journaltitles} in \textsf{article}, \textsf{review}, and
\textsf{periodical} entries, as well as facilitating the creation of
lists of journal abbreviations in the manner of a \textsf{shorthand}
-list.  Please see the documentation of \textbf{shortjournal}
-in section~\ref{sec:entryfields} for all the details on how this
-works.
+list.  Please see the documentation of \textbf{shortjournal} in
+section~\ref{sec:entryfields} for all the details on how this works.

-\enlargethispage{\baselineskip}
+\mylittlespace Finally, \colmarginpar{New!} the 17th edition (14.191)
+specifies that, for news sites carrying \enquote{stories as they
+  unfold, it may be appropriate to include a time stamp for an article
+  that includes one.}  You can provide this by using the standard
+\textsf{biblatex} time stamp format inside the \textsf{date} field,
+e.g., \texttt{2008-07-01T10:18:00}.  Since the \emph{Manual} prefers
+the standard time zone initialisms, a separate \textsf{timezone} field
+would be required if you want to provide one.

\mylittlespace If you're still with me, allow me to recommend that you
browse through \textsf{notes-test.bib} to get a feel for just how many
@@ -775,24 +827,18 @@
cases are really rather rare, and that the vast majority of sources
won't require any knowledge of these onerous details.

-\mybigspace Arne \mymarginpar{\textbf{artwork}} Kjell Vikhagen has
+\mybigspace Arne \colmarginpar{\textbf{artwork}} Kjell Vikhagen
pointed out to me that none of the standard entry types were
-straightforwardly adaptable when referring to visual artworks.  The
-\emph{Manual} doesn't give any thorough specifications for such
-references, and indeed it's unclear that it believes it necessary to
-include them in the bibliographical apparatus at all.  Still, it's
-easy to conceive of contexts in which a list of artworks studied might
-be desirable, and \textsf{biblatex} includes entry types for just this
-purpose, though the standard styles leave them undefined.  The two I
-chose to include in previous releases were \textsf{artwork} and
-\textsf{image}, the former intended for paintings, sculptures,
-etchings, and the like, the latter for photographs.  The 16th edition
-of the \emph{Manual} has modified its specifications for presenting
-photographs so that they are the same as for works in all other media.
-The \textsf{image} type, therefore, is now merely a clone of the
-\textsf{artwork} type, maintained mainly to provide backward
-compatibility for users migrating from the old specification to the
-current one.
+straightforwardly adaptable when referring to visual artworks.  It's
+unclear that the \emph{Manual} (14.235) believes it necessary to
+include them in the bibliographical apparatus at all, but it's easy
+all the same to conceive of contexts in which a list of artworks
+studied might be desirable, and \textsf{biblatex} includes entry types
+for just this purpose, though the standard styles leave them
+undefined.  \textsf{Biblatex-chicago} defines both \textsf{artwork}
+and \textsf{image}, which are in fact now clones of each other, so you
+can use either of them indifferently, the distinction existing only
+for historical reasons.

\mylittlespace Constructing an entry is fairly straightforward.  As
one might expect, the artist goes in \textsf{author} and the name of
@@ -806,27 +852,49 @@
uses \textsf{biblatex's} automatic capitalization routines, so if the
first word only needs a capital letter at the beginning of a sentence,
use lowercase in the .bib file and let \textsf{biblatex} handle it for
-you.  (See \emph{Manual} 3.22, 8.193; leo:madonna, bedford:photo.)
+you.  (See \emph{Manual} 3.22, 8.198; leo:madonna, bedford:photo.)

-\mylittlespace As a final complication, the \emph{Manual} (8.193) says
+\mylittlespace The \colmarginpar{New!} 17th edition of the
+\emph{Manual} has included new information in some of its examples, so
+I have added 4 new fields to the drivers.  Alongside the usual
+\textsf{date} for the creation of a work, you may also want to include
+the printing date of a particular exemplar of a photograph or a print.
+The system I have designed uses the \emph{earlier} of the
+and the \emph{later} to be the printing date.  The style will
+automatically prefix the printing date with the localized
+\cmd{bibstring} \mycolor{\texttt{printed}}, so if that's the wrong
+string entirely then you can define \textsf{userd} any way you like to
+change it.  If only \emph{one} of those two dates is available, it
+will always serve as a creation date.
+
+\mylittlespace One of the \emph{Manual's} examples is of a photograph
+appears late in the entry, after the \textsf{type}.  I have included
+the \textsf{howpublished} field so that you can give information about
+the periodical (meaning that you'll have to format the title yourself
+with \cmd{mkbibemph}), and the \textsf{eventdate} field for you to
+provide the date of publication (mccurry:afghangirl).
+
+\mylittlespace As a final complication, the \emph{Manual} (8.198) says
that \enquote{the names of works of antiquity \ldots\,are usually set
in roman.}  If you should need to include such a work in the
reference apparatus, you can either define an \textsf{entrysubtype}
for an \textsf{artwork} entry --- anything will do --- or you could
use the \textsf{misc} entry type with an \textsf{entrysubtype}.
-Fortunately, in this instance the other fields in a \textsf{misc}
-entry function pretty much as in \textsf{artwork}.
+Assuming the complicated date handling I've just outlined isn't
+required for such a work, in this instance the other fields in a
+\textsf{misc} entry function pretty much as in \textsf{artwork}.

-\mybigspace Following \mymarginpar{\textbf{audio}} the request of
+\mybigspace Following \colmarginpar{\textbf{audio}} the request of
Johan Nordstrom, I have included three entry types, all undefined by
the standard styles, designed to allow users to present audiovisual
sources in accordance with the Chicago specifications.  The
-\emph{Manual's} presentation of such sources (14.274--280), though
-admirably brief, seems to me somewhat inconsistent; the proliferation
-of online sources has made the task yet more complex.  For the 15th
-edition I attempted to condense all the requirements into two new
-entry types, but ended up relying on three.  For the 16th edition, in
-particular, I also need to include the \textbf{online} and even the
+\emph{Manual's} presentation of such sources (14.261--68), though
+admirably brief, seems to me somewhat inconsistent, though perhaps I'm
+merely unable to spot the important regularities.  The proliferation
+of online sources has made the task yet more complex, requiring the
+inclusion of the \textbf{article}, the \textbf{online}, and even the
\textbf{misc} entry types, which see, under the audiovisual rubric.  I
shall attempt to delineate the main differences here, and though there
are likely to be occasions when your choice of entry type is not
@@ -839,27 +907,35 @@
and tapes.  The \textbf{video} type includes most visual media,
whether it be films, TV shows, tapes and DVDs of the preceding or of
any sort of performance (including music), or online multimedia.  The
-\emph{Manual's} treatment (14.280) of the latter suggests that online
+\emph{Manual's} treatment (14.267) of the latter suggests that online
video excerpts, short pieces, and interviews should generally use the
-The \textbf{audio} type, our current concern, fills gaps in the
-others, and presents its sources in a more \enquote{book-like} manner.
-Published musical scores need this type --- unpublished ones would use
-\textsf{misc} with an \textsf{entrysubtype} (shapey:partita) --- as do
-such favorite educational formats as the slideshow and the filmstrip
-(greek:filmstrip, schubert:muellerin, verdi:corsaro).  The
-\emph{Manual} (14.277--280) sometimes uses a similar format for audio
-books (twain:audio), though, depending on the sorts of publication
-facts you wish to present, this sort of material may fall under
-\textsf{music} (auden:reading).  Dated audio recordings that are part
-of an archive, online or no, may be presented either in an
-\textsf{online} or in a \textsf{misc} entry with an
+\textbf{online} type (horowitz:youtube, pollan:plant) or the
+\textbf{article} type (harwood:biden, kessler:nyt), depending on
+whether the pieces originate from an identifiably
+\enquote{journalistic} outlet.  The \textbf{audio} type, our current
+concern, fills gaps in the others, and presents its sources in a more
+\enquote{book-like} manner.  Published musical scores need this type
+--- unpublished ones would use \textsf{misc} with an
+\textsf{entrysubtype} (shapey:partita) --- as do \mycolor{podcasts}
+and such favorite educational formats as the slideshow and the
+filmstrip (danforth:podcast, greek:film\-strip, schubert:muellerin,
+verdi:corsaro).  The \emph{Manual} (14.264) sometimes uses a similar
+format for audio books (twain:audio), though, depending on the sorts
+of publication facts you wish to present, this sort of material may
+fall under \textsf{music} (auden:reading).  Dated audio recordings
+that are part of an archive, online or no, may be presented either in
+an \textbf{online} or in a \textbf{misc} entry with an
\textsf{entrysubtype}, the difference mainly being in just how closely
associated the \textsf{date} will be with the \textsf{title}
-(coolidge:speech, roosevelt:speech).
+opposed to podcasts) pose something of a conundrum.  Interviews and
+other sorts of \enquote{journalistic} material fit well into
+\textsf{article} or \textsf{review} entries (14.213), but other sorts
+of broadcast are not well represented in the \emph{Manual's} examples
+(8.189), and what little there is suggests that, counter-intuitively,
+the \textsf{video} type is the best fit, as it is well equipped to

-%\enlargethispage{\baselineskip}
-
\mylittlespace Once you've accepted the analogy of composer to
\textsf{author}, constructing an \textsf{audio} entry should be fairly
straightforward, since many of the fields function just as they do in
@@ -871,14 +947,35 @@
\textsf{date}, and a \textsf{location}, there may also be a
\textsf{booktitle} and/or a \textsf{maintitle} --- see
schubert:muellerin for an entry that uses all three in citing one song
-from a cycle.  If the medium in question needs specifying, the
-\textsf{type} field is the place for it.  Finally, the
-\textsf{titleaddon} field can specify functions for which
-\textsf{biblatex-chicago} provides no automated handling, e.g., a
-librettist (verdi:corsaro).
+from a cycle.  (As with the \textsf{music} and \textsf{video} types,
+you can cite an individual piece separate from any large collection by
+using the \textsf{title} field and by defining an
+\textsf{entrysubtype}, which will stop \textsf{biblatex-chicago}
+italicizing your \textsf{title} in the absence of a
+\textsf{booktitle}.)  If the medium in question needs specifying, the
+\textsf{type} field is the place for it.  Please note, also, that
+while the \textsf{titleaddon} field can still specify creative or
+editorial functions for which \textsf{biblatex-chicago} provides no
+automated, localized handling, you can also now provide the string you
+need in an \textsf{editor[abc]type} field, e.g.,
+\enquote{\texttt{libretto by}} (verdi:corsaro).

-\mybigspace This \mymarginpar{\textbf{book}} is the standard
-\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but the package
+\mylittlespace For \colmarginpar{New!} podcasts, newly covered by the
+17th edition (14.267), the \textsf{audio} type provides the nearest
+analogue I could find, and in general most of the data should fit
+comfortably into the fields already discussed above, the episode name
+in \textsf{title} and the name of the podcast in \textsf{booktitle},
+for starters.  Two details, however, need mentioning: first, the
+\textsf{note} field as the place to specify that it is a podcast, and
+the \textsf{eventdate} field for the date of publication of the
+specific episode (\textsf{title}) cited, which appears in close
+association with that \textsf{title}.  Indeed, the \textsf{eventdate}
+field helps \textsf{biblatex-chicago} know that the \textsf{audio}
+entry is a podcast episode, and helps it construct the entry
+appropriately (danforth:podcast).
+
+\mybigspace This \colmarginpar{\textbf{book}} is the standard
+\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, and the package
can automatically provide abbreviated references in notes and
bibliography when you use a \textsf{crossref} or an \textsf{xref}
field.  The functionality is not enabled by default, but you can
@@ -886,35 +983,35 @@
\texttt{booklongxref} option.  Please see \textbf{crossref} in
section~\ref{sec:entryfields} and \texttt{booklongxref} in
section~\ref{sec:chicpreset}, below.  Cf.\ harley:ancient:cart,
-harley:cartography, and harley:hoc for how this might look.
+harley:cartography, and harley:hoc for how this might look.  The
+\textsf{book} type is useful also to present multimedia app content,
+the added fields \textsf{version} and \textsf{type} providing
+information about the app's version and about the system on which it
+runs (14.268; angry:birds).

+\enlargethispage{\baselineskip}
+
\mybigspace This \mymarginpar{\textbf{bookinbook}} type provides the
means of referring to parts of books that are considered, in other
contexts, themselves to be books, rather than chapters, essays, or
articles.  Such an entry can have a \textsf{title} and a
-\textsf{maintitle}, but it can also contain a \textsf{booktitle}, all
+\textsf{booktitle}, but it can also contain a \textsf{maintitle}, all
three of which will be italicized when printed.  In general usage it
is, therefore, rather like the traditional \textsf{inbook} type, only
with its \textsf{title} in italics rather than in quotation marks.  As
-with the \textsf{book} type, you can automatically enable
-abbreviated references in notes and bibliography, though this isn't
-the default.  Please see \textbf{crossref} in
-section~\ref{sec:entryfields} and \texttt{booklongxref} in
-section~\ref{sec:chicpreset}, below.  (Cf.\ \emph{Manual} 14.114,
-14.127, 14.130; bernhard:boris, bernhard:ritter, and
-bernhard:themacher for the new abbreviating functionality; also
-euripides:orestes, plato:republic:gr.)
+with the \textsf{book} type, you can automatically enable abbreviated
+references in notes and bibliography, though this isn't the default.
+Please see \textbf{crossref} in section~\ref{sec:entryfields} and
+\texttt{booklongxref} in section~\ref{sec:chicpreset}, below.  (Cf.\
+\emph{Manual} 14.109, 14.122, 14.124; bernhard:boris, bernhard:ritter,
+and bernhard:themacher for the abbreviating functionality; also
+euripides:orestes [treated differently in 14.122 and 14.124],
+plato:republic:gr.)

-\mylittlespace \textbf{NB}: The Euripides play receives slightly
-different presentations in 14.127 and 14.130.  Although the
-specification is very detailed, it doesn't eliminate all choice or
-variation.  Using a system like \textsc{Bib}\TeX\ should help to
-maintain consistency.
-
\mybigspace This \mymarginpar{\textbf{booklet}} is the first of two
entry types --- the other being \textsf{manual}, on which see below
--- which are traditional in \textsc{Bib}\TeX\ styles, but which the
-\emph{Manual} (14.249) suggests may well be treated basically as
+\emph{Manual} (14.220) suggests may well be treated basically as
books.  In the interests of backward compatibility,
\textsf{biblatex-chica\-go-notes} will so format such an entry, which
uses the \textsf{howpublished} field instead of a standard
@@ -934,18 +1031,6 @@
harley:ancient:cart, harley:cartography, and harley:hoc for how this
might look.

-\mybigspace This \mymarginpar{\textbf{customa}} entry type is
-obsolete, and any such entries in your .bib file will trigger an
-error.  Please use the standard \textsf{biblatex} \textbf{letter} type
-
-%\enlargethispage{\baselineskip}
-
-\mybigspace This \mymarginpar{\textbf{customb}} entry type is
-obsolete, and any such entries in your .bib file will trigger an
-error.  Please use the standard \textsf{biblatex} \textbf{bookinbook}
-
\mybigspace This \mymarginpar{\textbf{customc}} entry type allows you
to include alphabetized cross-references to other, separate entries in
the bibliography, particularly to other names or pseudonyms, as
@@ -952,7 +1037,7 @@
recommen\-ded by the \emph{Manual}.  (This is different from the
\textsf{crossref}, \textsf{xref}, \textsf{userf} and \textsf{related}
mechanisms, all primarily designed to include cross-references to
-other works.  Cf.\ 14.84,86).  The lecarre:cornwell entry, for
+other works.  Cf.\ 14.81--82).  The lecarre:cornwell entry, for
pseudonym \enquote{John Le Carr\xE9} even if they were, for some reason,
looking under his real name \enquote{David John Moore Cornwell.}\ As I
@@ -961,38 +1046,47 @@
includes two or more works published by the same author but under
different pseudonyms.}\ The following entries in
\textsf{notes-test.bib} show one way of addressing this:
-crea\-sey:ashe:blast, crea\-sey:york:death, crea\-sey:mor\-ton:hide,
-ashe:crea\-sey, york:crea\-sey and mor\-ton:crea\-sey.
+creasey:ashe:blast, creasey:york:death, creasey:morton:hide,
+ashe:creasey, york:creasey and morton:creasey.

\mylittlespace In these latter cases, you would need merely to place
the pseudonym in the \textsf{author} field, and the author's real
-name, under which his or her works are presented in the bibliography,
-in the \textsf{title} field.  To make sure the cross-reference also
+name, under which their works are presented in the bibliography, in
+the \textsf{title} field.  To make sure the cross-reference also
appears in the bibliography, you can either manually include the entry
key in a \cmd{nocite} command, or you can put that entry key in the
-\textbf{userc} field in the main .bib entry, in which case
-\textsf{biblatex-chicago} will print the expanded abbreviation if and
-only if you cite the main entry.  (Cf.\ \textsf{userc}, below.)
+\textbf{userc} field in the work's main .bib entry, in which case
+\textsf{biblatex-chicago} will print the cross-reference if and only
+if you cite the main work.  (Cf.\ \textsf{userc}, below.)

-%%\enlargethispage{\baselineskip}
-
\mylittlespace Under ordinary circumstances, \textsf{biblatex-chicago}
will connect the two parts of the cross-reference with the word
\enquote{\emph{See}} --- or its equivalent in the document's language
---- in italics.  If you wish to present the cross-reference
-differently, you can put the connecting word(s) into the
+--- in italics.  If you wish to present it differently, you can put
+the connecting word(s) into the \textsf{nameaddon} field.

-\mybigspace This \mymarginpar{\textbf{image}} entry type, left
-undefined in the standard styles, was in previous releases of
-\textsf{bibla\-tex-chicago} intended for referring to photographs, but
-the 16th edition of the \emph{Manual} has changed its specifications
-for such works, which are now treated the same as works in all other
-media.  This means that this entry type is now a clone of the
-\textsf{artwork} type, which see.  I retain it here as a convenience
-for users migrating from the old to the new specification.  (See 3.22,
-8.193; bedford:photo.)
+\mybigspace This \colmarginpar{\textbf{dataset}} entry type, new in
+\textsf{biblatex} 3.13, allows you to cite scientific databases, for
+which the \emph{Manual} (14.257) presents some rather specific, if
+brief, instructions.  To construct your entry, you can put the name of
+the database into \textsf{author}, a \enquote{descriptive phrase or
+  record locator} in the \textsf{title} field, and if there's a
+specific accession number needed beyond the record locator you can put
+it into the \textsf{number} field, with the \textsf{type} field
+reserved to help explain what sort of \textsf{number} is involved.
+The \textsf{howpublished} field can also be used to provide extra
+descriptive detail about the \textsf{number}, if needed.  More
+generally, a \textsf{url} will locate the database as a whole and a
+\textsf{urldate} will specify the date you accessed it.  If, for some
+reason, an additional date is relevant, then the \textsf{date} field
+is available, while the \textsf{pubstate} field will appear before the
+\textsf{date} in case you need to modify the latter.  (See 14.257;
+genbank:db, nasa:db.)

+\mybigspace This \mymarginpar{\textbf{image}} entry type is now a
+clone of the \textsf{artwork} type, which see.  I retain it here for
+historical reasons (See 3.22, 8.198; bedford:photo.)
+
\mybigspace These \mymarginpar{\textbf{inbook}\\\textbf{incollection}}
two standard \textsf{biblatex} types have very nearly identical
formatting requirements as far as the Chicago specification is
@@ -1009,7 +1103,7 @@
from the same \textsf{collection}.  These abbreviations are activated
by default when you use the \textsf{crossref} or \textsf{xref} field
in \textsf{incollection} entries and in \textsf{inbook} entries,
-because although the \emph{Manual} (14.113) here specifies a
+because although the \emph{Manual} (14.108) here specifies a
\enquote{multiauthor book,} I believe the distinction between the two
is fine enough to encourage similar treatments.  (For more on this
mechanism see \textbf{crossref} in section~\ref{sec:entryfields},
@@ -1019,7 +1113,7 @@
the part of a book to which you are referring has had a separate
publishing history as a book in its own right, then you may wish to
use the \textsf{bookinbook} type, instead, on which see above.  (See
-\emph{Manual} 14.111--114; \textsf{inbook}: ashbrook:brain,
+\emph{Manual} 14.106--9; \textsf{inbook}: ashbrook:brain,
phibbs:diary, will:cohere; \textsf{incollection}: centinel:letters,
contrib:contrib, sirosh:visualcortex; ellet:galena, keating:dearborn,
and lippincott:chicago [and the \textsf{collection} entry
@@ -1043,7 +1137,7 @@
differences between it and \textsf{incollection} are the lack of an
\textsf{edition} field and the possibility that an
\textsf{organization} may be cited alongside the \textsf{publisher},
-even though the \emph{Manual} doesn't specify its use (14.226).
+even though the \emph{Manual} doesn't specify its use (14.217).
Please note, also, that the \textsf{crossref} and \textsf{xref}
mechanism for shortening citations of multiple pieces from the same
\textsf{proceedings} is operative here, just as it is in
@@ -1052,13 +1146,13 @@
\texttt{longcrossref} in section~\ref{sec:chicpreset} for more
details.

-\mybigspace This \mymarginpar{\textbf{inreference}} entry type is
+\mybigspace This \colmarginpar{\textbf{inreference}} entry type is
aliased to \textsf{incollection} in the standard styles, but the
\emph{Manual} has particular requirements, so if you are citing
\enquote{[w]ell-known reference books, such as major dictionaries and
encyclopedias,} then this type should simplify the task of
-conforming to the specifications (14.247--248).  The main thing to
-keep in mind is that I have designed this entry type for
+conforming to the specifications (14.232--34).  The main thing to keep
+in mind is that I have designed this entry type for
\enquote{alphabetically arranged} works, which you shouldn't cite by
page, but rather by the name(s) of the article(s).  Because of the
formatting required by the \emph{Manual}, we need one of
@@ -1070,10 +1164,11 @@
\textsf{biblatex-chicago-notes} will provide the appropriate prefatory
string (\texttt{s.v.}, plural \texttt{s.vv.}), and enclose each in its
own set of quotation marks (ency:britannica).  In a typical
-\textsf{inreference} entry, very few other fields are needed, as
-\enquote{the facts of publication are often omitted, but the edition
-  (if not the first) must be specified.}  In practice, this means a
-\textsf{title} and possibly an \textsf{edition} field.
+\textsf{inreference} entry very few other fields are needed, but
+\enquote{if a physical edition is cited, not only the edition number
+  (if not the first) but also the date the volume or set was issued
+  must be specified.}  In practice, this means a \textsf{title},
+\textsf{date}, and possibly an \textsf{edition} field.

\mylittlespace There are quite a few other peculiarities to explain
here.  First of all, you should present any well-known works
@@ -1086,36 +1181,30 @@
an article appearing in different editions.

\mylittlespace If the work is slightly less well known, it may be that
-full publication details are appropriate (times:guide), but this makes
-things more complicated.  In earlier releases of
-\textsf{biblatex-chicago-notes}, you would have had to format the
-\textsf{postnote} field of short notes appropriately, including the
-prefatory string and quotation marks I mentioned above.  Now you can
+full publication details are appropriate (times:guide).  Also, you can
put an article name in the \textsf{postnote} field of
-\textsf{inreference} entries and have it formatted for you, and this
-holds for both long and short notes, which could allow you to refer
-separately to many different articles from the same reference work
-using only one .bib entry.  (In a long note, any \textsf{postnote}
-field stops the printing of the contents of \textsf{lista}.)  The only
-limitation on this system is that the \textsf{postnote} field, unlike
-\textsf{lista}, is not a \textsf{biblatex} list, and therefore for the
-formatting to work correctly you can only put one article name in it.
-Despite this limitation, I hope that the current system might simplify
-things for users who cite numerous works of reference.
+\textsf{inreference} entries and have it properly formatted for you,
+and this holds for both long and short notes, which could allow you to
+refer separately to many different articles from the same reference
+work using only one .bib entry.  (In a long note, any
+\textsf{postnote} field stops the printing of the contents of
+\textsf{lista}.)  The only limitation on this system is that the
+\textsf{postnote} field, unlike \textsf{lista}, is not a
+\textsf{biblatex} list, and therefore for the formatting to work
+correctly you can only put one article name in it.  Despite this
+limitation, I hope that the system might simplify things for users who
+cite numerous works of reference.

-%\enlargethispage{-\baselineskip}
-
\mylittlespace If it seems appropriate to include such a work in the
bibliography, be aware that the contents of the \textsf{lista} field
will also be presented there, which may not be what you want.  A
-separate \textsf{reference} entry might solve this problem, but you
-may also need a \textsf{sortkey} field to ensure proper
-alphabetization, as \textsf{biblatex} will attempt to use an
-\textsf{editor} or \textsf{author} name, if either is present.  (Cf.\
-mla:style, a \textsf{reference} entry that uses section numbers
-\textsf{options} field instead of a \textsf{sortkey} to ensure the
-correct alphabetization.)
+separate \textsf{reference} entry might well solve this problem.  (The
+sorting issues with \textsf{inreference}, \textsf{mvreference}, and
+\textsf{reference} entries should no longer exist, as they should now
+always sort by \textsf{title} rather than by any \textsf{author},
+\textsf{editor}, or \textsf{namec} that might also be present.  If the
+\textsf{title} starts with a definite or indefinite article then a
+\textsf{sortkey} may still be necessary.)

\mylittlespace Speaking of the \textsf{author}, this field holds the
author of the specific entry (in \textsf{lista}), not the author of
@@ -1129,12 +1218,30 @@
choice for unfamiliar or non-standard reference works.

\mylittlespace Finally, all of these rules apply to online reference
-works, as well, for which you need to provide not only a \textsf{url}
-but also, always, a \textsf{urldate}, as these sources are in constant
-flux (wikiped:bibtex, grove:sibelius).
+works, along with a few more.  The \colmarginpar{New!} 17th edition of
+the \emph{Manual} now allows, \enquote{subject to editorial
+  discretion,} the alternative treatment of an online reference work
+which \enquote{does not have (and never had) a printed counterpart}
+(14.206, 14.233).  In effect this means that it can be treated more
+like an \textsf{online} entry than a \textsf{book}, its \textsf{title}
+therefore in plain roman rather than in italics.  You can achieve this
+in \textsf{inreference} entries by providing an \textsf{entrysubtype}
+in the entry.  Online reference works need not only a \textsf{url} but
+also, always, a \textsf{urldate} (instead of a \textsf{date)}, as
+these sources are in constant flux.  When that flux is of a
+particularly high frequency, as with Wikipedia, then a time stamp may
+also be needed.  You can provide this in the \textsf{urldate} field
+itself, using the standard \textsf{biblatex} format, e.g.,
+\texttt{2008-07-01T10:18:00}.  It is
+\colmarginpar{\texttt{urlstamp=true}} possible to turn off the
+printing of the \textsf{urltime} with the new
+\mycolor{\texttt{urlstamp}} option, which is set to \texttt{true} by
+default, but which can be changed in your preamble for the whole
+document, for specific entry types, or in the \textsf{options} field
+of specific entries (wikiped:bibtex, grove:sibelius).

\mybigspace I
-\colmarginpar{\textbf{jurisdiction}\\\textbf{legal}\\\textbf{legislation}}
+\mymarginpar{\textbf{jurisdiction}\\\textbf{legal}\\\textbf{legislation}}
document these three types in section~\ref{sec:legal} below, both
because they all follow the specifications of the \emph{Bluebook}
instead of the \emph{Manual}, and also because they are the only entry
@@ -1148,14 +1255,14 @@
Depending on what sort of information you need to present in a
citation, you may simply be able to get away with a standard
\textsf{book} entry, which may then be cited by page number (see
-\emph{Manual} 14.78, 14.88; meredith:letters, adorno:benj).  If,
-however, for whatever reason, you need to give full details of a
-specific letter, then you'll need to use the \textsf{letter} entry
-type, which attempts to simplify for you the \emph{Manual}'s rather
-complicated rules for formatting such references.  (See 14.117;
-jackson:paulina:letter, white:ross:memo, white:russ [a completely
-fictitious entry to show the \textsf{crossref} mechanism], white:total
-[a \textsf{book} entry, for the bibliography]).
+14.104; meredith:letters, adorno:benj).  If, however, for whatever
+reason, you need to give full details of a specific letter, then
+you'll need to use the \textsf{letter} entry type, which attempts to
+simplify for you the \emph{Manual}'s rather complicated rules for
+formatting such references.  (See 14.111; jackson:paulina:letter,
+white:ross:memo, white:russ [a completely fictitious entry to show the
+\textsf{crossref} mechanism], white:total [a \textsf{book} entry, for
+the bibliography]).

\mylittlespace To start, the name of the letter writer goes in the
\textsf{author} field, while the \textsf{title} field contains both
@@ -1165,7 +1272,7 @@
the type needn't be given, but if it's a memorandum or report or the
like, then this is the place to specify that fact.  Also, because the
\textsf{origdate} field only accepts numbers, if you want to use the
-abbreviation \enquote{n.d.}  (or \cmd{bibstring\{nodate\}}) for
+abbreviation \enquote{n.d.}  (or \verb+\bibstring{nodate}+) for
undated letters, then this is where you should put it.  If you need to
specify where a letter was written, then you can also use this field,
and, if both are present, remember to separate the location from the
@@ -1174,21 +1281,22 @@
\textsf{origlocation} field.  Most importantly, the date of the letter
itself goes in the \textsf{origdate} field (\texttt{year-month-day}),
which allows a full date specification, while the publishing date of
-the whole collection goes in the \textsf{date} field, instead of in
-the obsolete \textsf{origyear}.  As in other entry types, then, the
-\textsf{date} field has its ordinary meaning of \enquote{date of
-  publication.}  (You may have noticed here that the presentation of
-the \textsf{origdate} in this sort of reference is different from the
-date format required elsewhere by the \emph{Manual}.  This appears to
-result from some recent changes to the specification, and it may be
-that we could get away with choosing one or the other format for all
-occurrences [6.45], but for the moment I hope this mixed solution will
-suffice.)  Another difficulty arises when producing the short footnote
-form, which requires you to provide a \textsf{shorttitle} field of the
-form \enquote{\texttt{to Recipient},} the latter name as short as
-possible while avoiding ambiguity.  The remaining fields are fairly
-self explanatory, but do remember that the title of the published
-collection belongs in \textsf{booktitle} rather than in
+the whole collection goes in the \textsf{date} field.  As in other
+entry types, then, the \textsf{date} field has its ordinary meaning of
+\enquote{date of publication.}  (You may have noticed that the
+presentation of the \textsf{origdate} in this sort of reference uses
+the day-month-year format, unlike the month-day-year format seen
+elsewhere.  This follows a suggestion that material with \enquote{many
+  references to specific dates} may use this format [6.38, 9.35,
+14.224].  I should, I guess, make this configurable.)  Another
+difficulty arises when producing the short footnote form, which
+requires you to provide a \textsf{shorttitle} field of the form
+\enquote{\texttt{to Recipient},} the latter name as short as possible
+while avoiding ambiguity.  The \cmd{letterdatelong} command can be
+used in the \textsf{postnote} field of the citation to print the
+\textsf{origdate}, a possible aid to disambiguation.  The remaining
+fields are fairly self explanatory, but do remember that the title of
+the published collection belongs in \textsf{booktitle} rather than in
\textsf{title}.

\mylittlespace Finally, the \emph{Manual} specifies that if you cite
@@ -1196,31 +1304,29 @@
bibliography should contain only a reference to said collection,
rather than to each individual letter, while the form of footnotes
would remain the same.  This should be possible using
-\textsc{Bib}\TeX's standard \textsf{crossref} field, with each
-\textsf{letter} entry pointing to a \textsf{collection} or
-\textsf{book} entry, for example.  (If you are using \textsf{Biber},
-then \textsf{letter} entries correctly inherit fields from
-\textsf{book} and \textsf{collection} entries, and also from the
-\textsf{mvbook} and \textsf{mvcollection} types --- \textsf{titles}
-from the former provide a \textsf{booktitle} and from the latter a
-\textsf{maintitle}.)  I shall discuss cross references at length later
-(see esp.\ \textbf{crossref} in section~\ref{sec:entryfields}, below),
-but I should mention here that \textsf{letter} is one of the entry
-types in which a \textsf{crossref} or an \textsf{xref} field
-automatically results in special shortened forms in notes and
-bibliography if more than one piece from a single collection is cited.
-(The other entry types are \textsf{inbook}, \textsf{incollection}, and
-\textsf{inproceedings}; see 14.113 for the \emph{Manual}'s
-specification.)  This ordinarily won't be an issue for \textsf{letter}
-entries in the bibliography, as individual letters aren't included
-there, but it is operative in notes, where you can disable it by
-setting the \texttt{longcrossref=true} option, on which see
-section~\ref{sec:chicpreset}, below.  To stop individual letters
+\textsc{Bib}\TeX's and \textsf{biblatex's} standard \textsf{crossref}
+field, with each \textsf{letter} entry pointing to a
+\textsf{collection} or \textsf{book} entry, for example.  (If you are
+using \textsf{Biber}, then \textsf{letter} entries correctly inherit
+fields from \textsf{book} and \textsf{collection} entries, and also
+from the \textsf{mvbook} and \textsf{mvcollection} types ---
+\textsf{titles} from the former provide a \textsf{booktitle} and from
+the latter a \textsf{maintitle}.)  I shall discuss cross references at
+length later (see esp.\ \textbf{crossref} in
+section~\ref{sec:entryfields}, below), but I should mention here that
+\textsf{letter} is one of the entry types in which a \textsf{crossref}
+or an \textsf{xref} field automatically results in special shortened
+forms in notes and bibliography if more than one piece from a single
+collection is cited.  (The other entry types are \textsf{inbook},
+\textsf{incollection}, and \textsf{inproceedings}; see 14.108 for the
+\emph{Manual}'s specification.)  This ordinarily won't be an issue for
+\textsf{letter} entries in the bibliography, as individual letters
+aren't included there, but it is operative in notes, where you can
+disable it by setting the \texttt{longcrossref=true} option, on which
+see section~\ref{sec:chicpreset}, below.  To stop individual letters
turning up in the bibliography, you can use the \texttt{skipbib}
option in the \textsf{options} field.

-% %\enlargethispage{\baselineskip}
-
\mybigspace This \mymarginpar{\textbf{manual}} is the second of two
traditional \textsc{Bib}\TeX\ entry types that the \emph{Manual}
suggests formatting as books, the other being \textsf{booklet}. As
@@ -1237,7 +1343,8 @@
if you were to use a \textsf{book} entry for such a reference, then
you would need to define both \textsf{author} and \textsf{publisher}
using the name you here might have put in \textsf{organization}.  (See
-14.92; chicago:manual, dyna:browser, natrecoff:camera.)
+14.84; chicago:manual, dyna:browser, natrecoff:camera.  Cp.\ also the
+new \mycolor{\textbf{standard}} entry type.)

\mybigspace As \mymarginpar{\textbf{misc}} its name suggests, the
\textsf{misc} entry type was designed as a hold-all for citations that
@@ -1273,168 +1380,197 @@
the title inside a \cmd{mkbibquote} command manually.  Cf.\
roosevelt:speech, shapey:partita.)

-\mylittlespace If you are wondering what to put in
-\textsf{entrysubtype}, the answer is, currently, anything at all.  You
-no longer need to put the exact string \texttt{letter} there in order
-to move the date into closer proximity with the \textsf{title}.
-Indeed, recent reconsideration of the \emph{Manual} has suggested that
-the distinction to be drawn in this class of material hasn't to do
-with \emph{where} the date is presented but, rather, with \emph{how}
-it is presented.  As I understand the specification, it draws a
-distinction between archival material that is \enquote{letter-like}
-(letters, memoranda, reports, telegrams) and that which isn't
-(interviews, wills, contracts, speeches, or even personal
-communications you've received and which you wish to cite).  This may
-not always be the easiest distinction to draw, and in earlier releases
-of \textsf{biblatex-chicago} I ignored it, but once you've decided to
-classify it one way or the other you put the date in the
-\textsf{origdate} field for letters, etc., and into the \textsf{date}
-field for the others.
+\mylittlespace If you are presenting part of an unpublished archive,
+then constructing most of your \,.bib entry is fairly straightforward.
+\enquote{Letter-like} \textsf{misc} entries follow many of the same
+conventions as \textsf{letter} entries presenting published material.
+Titles are of the form \texttt{Author to Recipient}, and further
+information can be given in the \textsf{titleaddon} field, including
+the abbreviation \enquote{\texttt{n.d.}}\ (or
+\verb+\bibstring{nodate}+) for undated examples.  The place where a
+letter was written can go in \textsf{origlocation}, while the
+\textsf{note}, \textsf{organization}, \textsf{institution}, and
+\textsf{location} fields (in ascending order of generality) allow the
+specification of which manuscript collection now holds the letter,
+though the \emph{Manual} specifies (14.227) that well-known
+depositories don't usually need a city, state or country specified.
+(The traditional \textsf{misc} fields are all still available, also.)
+Both the long and short note forms can use the same \textsf{title},
+but in both cases you may need to use the \cmd{headlesscite} command
+to avoid the awkward repetition of the author's name, though that name
+will always appear in the bibliography (creel:house).  If the
+\textsf{misc} entry isn't a letter, remember that, as in
+\textsf{article} and \textsf{review} entries, words like
+\texttt{interview} or \texttt{memorandum} needn't be capitalized
+unless they follow a period --- the automatic capitalization routines
+(with the \textsf{title} field starting with a lowercase letter [see
+dinkel:agassiz, spock:interview, and \texttt{\textbackslash autocap}])
+will ensure correctness.  Also, please note that you can give
+if you're indicating that the \textsf{author} is pseudonymous, or
+parentheses if it's another sort of information of interest to your

-\mylittlespace In effect, whether it's a \textsf{letter} entry or a
-\enquote{letter-like} \textsf{misc} entry (with
-\textsf{entrysubtype}), it is by using the \textsf{origdate} field
-that you identify when it was written, and the \textsf{origlocation},
-if needed, identifies where it was written.  Other sorts of
-\textsf{misc} entry (with \textsf{entrysubtype}) use the \textsf{date}
-field (but still the \textsf{origlocation}).  This maintains
-consistency of usage across entry types and also, I hope, improves
-compliance when using the \textsf{misc} type for citing archival
-material.  Remember, however, that without an \textsf{entrysubtype}
-the entry will be treated as traditional \textsf{misc}, and the title
-italicized.  In addition, defining \textsf{entrysubtype} activates the
-automatic capitalization mechanism in the \textsf{title} field of
-\textsf{misc} entries, on which see\,\textbf{\textbackslash autocap}
-in section~\ref{sec:formatcommands} below.  (See 14.219-220, 14.231,
-14.232-242; creel:house, dinkel:agassiz, spock:interview.)
-
-\mylittlespace As in \textsf{letter} entries, the titles of
-unpublished letters are of the form \texttt{Author to Recipi\-ent}, and
-further information can be given in the \textsf{titleaddon} field,
-including the abbreviation \enquote{\texttt{n.d.}}\ (or
-\cmd{bibstring\{nodate\}}) for undated examples.  The \textsf{note},
-\textsf{organization}, \textsf{institution}, and \textsf{location}
-fields (in ascending order of generality) allow the specification of
-which manuscript collection now holds the letter, though the
-\emph{Manual} specifies (14.238) that well-known depositories don't
-usually need a city, state or country specified.  (The traditional
-\textsf{misc} fields are all still available, also.)  Both the long
-and short note forms can use the same \textsf{title}, but in both
-cases you may need to use the \cmd{headlesscite} command to avoid the
-awkward repetition of the author's name, though that name will always
-appear in the bibliography (creel:house).  If you want to include the
-date of a letter in a short note, I have provided the
+\mylittlespace Now for the subtleties.  First, the \emph{Manual}
+(14.224) allows in these entries, as it does in documentation
+generally \enquote{if numerous dates occur} (9.35), for a more
+streamlined presentation of dates using the day-month-year form,
+different from the standard American month-day-year.  In
+\textsf{letter} entries you use the \textsf{origdate} field to give
+the date of individual letters, and it is always presented in the more
+streamlined form.  Here, the same field will do exactly the same
+thing, though with the added wrinkle that if you'd prefer to use the
+standard day-month-year form you can, simply by putting the date into
+\textsf{misc} entries with an \textsf{entrysubtype} --- in
+\textsf{letter} entries the \textsf{date} refers to the published
+collection.) Again just as in \textsf{letter} entries, if you want to
+include the day-month-year in a short note, I have provided the
\cmd{letterdatelong} command for inclusion in the postnote field of
the citation command.  (The standard \textsf{biblatex} command
-\cmd{printdate} will work if you need to do the same for interviews.)
+\cmd{printdate} will work if you prefer the standard date form.)

-%\enlargethispage{\baselineskip}
+\enlargethispage{\baselineskip}

-\mylittlespace As with \textsf{letter} entries, the \emph{Manual}
-(14.233) suggests that bibliography entries contain only the name of
-the manuscript collection, unless only one item from that collection
-is cited.  The \textsf{crossref} field can be used, as well as the
-\texttt{skipbib} option, for preventing the individual items from
-turning up in the bibliography.  Obviously, this is a matter for your
-discretion, and if you're using only short notes (see the
-\texttt{short} option, section~\ref{sec:useropts} below), you may feel
-the need to include more information in the note if the bibliography
-doesn't contain a full reference to an individual item.
+\mylittlespace Second, some material (roosevelt:speech) includes a
+venue for the event recorded in the archive, so I have added the
+\mycolor{\textsf{venue}} field, which prints \emph{before} the date,
+with the \textsf{origlocation} appearing after it.  Somewhat
+confusingly, in published letters the \textsf{origlocation} itself
+prints before the date, rather than after, so if the inconsistency
+between published and unpublished letters bothers you then you could
+conceivably use \textsf{venue} instead of \textsf{origlocation} for
+that purpose here.

-\mylittlespace Finally, if the \textsf{misc} entry isn't a letter,
-remember that, as in \textsf{article} and \textsf{review} entries,
-words like \texttt{interview} or \texttt{memorandum} needn't be
-capitalized unless they follow a period --- the automatic
-capitalization routines (with the \textsf{title} field starting with a
-lowercase letter [see dinkel:agassiz, spock:interview, and
-\textbf{\textbackslash autocap}]) will ensure correctness.  In all
-this class of archived material, the \emph{Manual} (14.232) quite
-specifically requires more consistency within your own work than
-conformity to some external standard, so it is the former which you
-should pursue.  I hope that \textsf{biblatex-chicago-notes} proves
+\mylittlespace Finally, a few further notes.  First, please be aware
+that defining an \textsf{entrysubtype} activates the automatic
+capitalization mechanism in the \textsf{title} field of \textsf{misc}
+entries, on which see\,\texttt{\textbackslash autocap} in
+section~\ref{sec:formatcommands} below.  Second, and again as with
+\textsf{letter} entries, the \emph{Manual} (14.222) suggests that
+bibliography entries contain only the name of the manuscript
+collection, unless only one item from that collection is cited.  The
+\textsf{crossref} field can be used, as well as the \texttt{skipbib}
+option, for preventing the individual items from turning up in the
+bibliography.  Obviously, this is a matter for your discretion, and if
+you're using only short notes (see the \texttt{short} option,
+section~\ref{sec:useropts} below), you may feel the need to include
+full reference to an individual item.  Third, the \emph{Manual} offers
+several examples of specific location information for pieces from an
+archive, some of which appears \emph{before} the main archive name,
+and some of which appears \emph{after} it.  I assume this may depend
+on the exact nature of the archive itself, but in any case you can try
+the \textsf{type} or \textsf{howpublished} fields for the first case
+and the \textsf{number} field for the second.  Last, in all this class
+of archived material, the \emph{Manual} (14.221) quite specifically
+requires more consistency within your own work than conformity to some
+external standard, so it is the former which you should pursue.  I
+hope that \textsf{biblatex-chicago-notes} proves helpful in this
+regard.  (See 14.211, 14.219, 14.221-231, 14.256, 14.264; creel:house,
+dinkel:agassiz, roosevelt:speech, shapey:partita, spock:interview.)

-\mybigspace The \mymarginpar{\textbf{music}} 16th edition of the
-\emph{Manual} revised its recommendations more for this type than for
-any other, so if by any chance you have been using the 15th edition
-style the notes which follow present several large changes that you'll
-need to make to your .bib files.  The good news is that some, though
-by no means all, of those changes involve considerable
-simplifications.  \textsf{Music} is one of three audiovisual entry
-types, and is intended primarily to aid in the presentation of musical
-recordings that do not have a video component, though it can also
-include audio books (auden:reading).  A DVD or VHS of an opera or
-other performance, by contrast, should use the \textbf{video} type
-instead, while an online music video will probably need an
-\textbf{online} entry.  (Cf.\ \textsf{online} and \textsf{video};
-handel:messiah, horowitz:youtube.)  Because \textsf{biblatex} --- and
-\textsc{Bib}\TeX\ before it --- were designed primarily for citing
-book-like objects, some choices needed to be made in assigning the
-various roles found on the back of a CD to the fields in a typical
-.bib entry.  I have also implemented several bibstrings to help in
-identifying these roles within entries.  If you can think of a simpler
-way to distribute the roles, please let me know, so that I can
-consider making changes before anyone gets used to the current
-equivalences.
+\mybigspace This \colmarginpar{\textbf{music}} is one of three
+audiovisual entry types, and is intended primarily to aid in the
+presentation of musical recordings that do not have a video component,
+though it can also include audio books (auden:reading).  A DVD or VHS
+of an opera or other performance, by contrast, should use the
+\textbf{video} type instead, while an online music video will probably
+need an \textbf{online} entry.  (Cf.\ \textsf{online} and
+\textsf{biblatex} --- and \textsc{Bib}\TeX\ before it --- were
+designed primarily for citing book-like objects, some choices needed
+to be made in assigning the various roles found on the back of a CD to
+the fields in a typical .bib entry.  I have also implemented several
+bibstrings to help in identifying these roles within entries.  The
+17th edition of the \emph{Manual} once again revised its
+recommendations for this type, but fortunately the changes are
+additive, i.e., you can re-use 16th-edition citations but are
+encouraged to peruse the following guidelines to see if there's any
+into line with the spec.

-\mylittlespace These equivalences, in summary form, are:
+\mylittlespace These guidelines, in summary form, are:

\begin{description}
-\item[author =] composer, songwriter, or performer(s),
-  depending on whom you wish to emphasize by placing them at the head
-  of the entry.
-\item[editor, editora, editorb =] conductor, director or
+\item[author:] composer, songwriter, or performer(s), they will be
+  closely associated with the \textsf{title}, either before it at the
+  head of the entry or, at your discretion, just after it
+  (holiday:fool).
+\item[bookauthor:] Somewhat like an \textsf{author}, but it will hold
+  the name associated with a whole album rather than an individual
+  piece, should both be present, and will therefore appear in close
+  association with the \textsf{booktitle}, rather than the
+  \textsf{title} (rihanna:umbrella).
+\item[editor, editora, editorb:] conductor, director or
performer(s).  These will ordinarily follow the \textsf{title} of
the work, though the usual \texttt{useauthor} and \texttt{useeditor}
options can alter the presentation within an entry.  Because these
are non-standard roles, you will need to identify them using the
following:
-\item[editortype, editoratype, editorbtype:] The most common roles,
-  all associated with specific bibstrings (or their absence), will be
-  \texttt{conductor}, \texttt{director}, \texttt{producer}, and,
-  oddly, \texttt{none}.  The last is particularly useful when
+\item[\mycolor{editortype, editoratype, editorbtype:}] The most common
+  roles, all associated with specific bibstrings (or their absence),
+  will be \texttt{conductor}, \texttt{director}, \texttt{producer},
+  and, oddly, \texttt{none}.  The last is particularly useful when
identifying the group performing a piece, as it usually doesn't need
further specifying and this role prevents \textsf{biblatex} from
-  falling back on the default \texttt{editor} bibstring.
-\item[title, booktitle, maintitle:] As with the other audiovisual
-  types, \textsf{music} serves as an analogue both to books and to
-  collections, so the title will either be, e.g., the album title or a
-  song title, in which latter case the album title would go into
-  \textsf{booktitle}.  The \textsf{maintitle} might be necessary for
-  something like a box set of \emph{Complete Symphonies}.
+  falling back on the default \texttt{editor} bibstring.  The 17th
+  edition (14.263) also seems to favor, in some circumstances, using
+  strings to identify individual performers, e.g., \enquote{vocalist}
+  or \enquote{pianist,} so even though there's no \cmd{bibstring}
+  associated with these types you can now provide them, or anything
+  else you need, in whatever form (\enquote{vocalist} or \enquote{sung
+\item[note:] This field can also hold contributors, perhaps
+  collaborators or featured artists (holiday:fool, rihanna:umbrella).
+\item[\mycolor{title, booktitle, maintitle:}] As with the other
+  audiovisual types, \textsf{music} serves as an analogue both to
+  books and to collections, so the title will either be, e.g., the
+  album title or a song title, in which latter case the album title
+  would go into \textsf{booktitle}.  If you wish to cite a song that,
+  as may happen, isn't part of any larger collection, your entry will
+  in such a case have only a \textsf{title}, which
+  \textsf{biblatex-chicago} would normally interpret as an album
+  title.  You \colmarginpar{New!} can now define an
+  \textsf{entrysubtype} to let it know that the lone \textsf{title} is
+  in fact a song (cf.\ naraya).  The \textsf{maintitle} might be
+  necessary for something like a box set of \emph{Complete
+    Symphonies}.
+\item[\mycolor{chapter:}] The 17th edition seems more keen on having
+  track numbers for individual pieces, whether on a traditional format
+  or on a streaming service.  The \colmarginpar{New!} \textsf{chapter}
+  field is the place for this information, and
+  \textsf{biblatex-chicago} will automatically prepend the localized
+  string \texttt{track} (cf.\ holiday:fool, rihanna:umbrella).
\item[publisher, series, number:] These three closely-associated
-  by the music publisher.  The 16th edition generally only requires
+  by the music publisher.  The 17th edition generally only requires
the \textsf{series} and \textsf{number} fields (nytrumpet:art),
which hold the record label and catalog number, respectively.
Alternatively, \textsf{publisher} would function as a synonym for
\textsf{series} (holiday:fool), but there may be cases when you need
-  or want to specify a publisher in addition to a label, as was the
-  general requirement in the 15th edition.  (This might happen, for
-  example, when a single publisher oversees more than one label.)  You
-  can certainly put all of this information into one of the above
-  fields, but separating it may help make the .bib entry more
-\item[howpublished/pubstate:] The 16th edition of the \emph{Manual}
-  (14.276) has rather helpfully eliminated any reference to the
-  specialized symbols (\texttt{\textcircledP} \&\
-  \texttt{\textcopyright}) found in the 15th edition for presenting
-  publishing information for musical recordings.  This means that the
-  \textsf{howpublished} field is obsolete, and you can remove it from
-  \textsf{music} entries in your .bib files.  The \textsf{pubstate}
-  field, therefore, can revert to its standard use for identifying
-  reprints.  In \textsf{music} entries, putting \texttt{reprint} here
-  will transform the \textsf{origdate} from a recording date for an
-  entire album into an original release date for that album, notice of
-  which will be printed towards the end of a note or bibliography
-  entry.
-\item[date, eventdate, origdate:] As though to compensate for the
-  simplification I've just mentioned, the \textsf{Manual} now states
-  that \enquote{citations without a date are generally unacceptable}
-  (14.276).  Finding a date may take some research, but they will
-  basically fall into two types, i.e., the date(s) of the recording or
-  the copyright / publishing date(s).  Recording dates go either in
+  or want to specify a publisher in addition to a label, as perhaps
+  when a single publisher oversees more than one label.  You can
+  certainly put all of this information into one of the above fields,
+  but separating it may help make the .bib entry more readable.
+\item[pubstate:] The \textsf{pubstate} field in \textsf{music} entries
+  mainly has the usual meaning it has in other entry types, for which
+  see the documentation of the field in section~\ref{sec:entryfields},
+  below.  If the field contains \texttt{reprint}, however, this has a
+  special meaning in \textsf{music} entries, where it will transform
+  the \textsf{origdate} from a recording date for an entire album into
+  an original release date for that album, notice of which will be
+  printed towards the end of a note or bibliography entry.  No
+  \texttt{reprint} \cmd{bibstring} will be printed, as only the syntax
+  of the reference will have been altered.
+\item[date, eventdate, origdate:] The 17th edition of the
+  \emph{Manual}, like the 16th, considers \textsf{music} citations
+  without a date to be \enquote{generally unacceptable} (14.263).
+  Finding a date may take some research, but they will basically fall
+  into two types, i.e., the date(s) of the recording or the copyright
+  / publishing date(s).  Recording dates go either in
\textsf{origdate} (for complete albums) or \textsf{eventdate} (for
individual tracks).  The copyright or publishing dates go either in
the \textsf{date} field (which applies to the current medium you are
@@ -1452,114 +1588,379 @@
In \textsf{music} entries, \textsf{userd} will be prepended to an
\textsf{eventdate} if there is one, barring that to the
\textsf{origdate}, barring that to a \textsf{urldate}, and absent
-  those three to the \textsf{date}.  (See floyd:atom, nytrumpet:art.)
- \item[type:] As in all the audiovisual entry types, the \textsf{type}
-  field holds the medium of the recording, e.g., vinyl, 33 rpm,
-  8-track tape, cassette, compact disc, mp3, ogg vorbis.
+  those three to the \textsf{date}.  (See floyd:atom, holiday:fool,
+  nytrumpet:art.)
+\item[type, \mycolor{howpublished}:] As in all the audiovisual entry
+  types, the \textsf{type} field holds the medium of the recording,
+  e.g., vinyl, 33 rpm, 8-track tape, cassette, compact disc, mp3, ogg
+  vorbis.  The \colmarginpar {New!} \mycolor{\textsf{howpublished}}
+  field, newly included for the 17th edition, can hold similar
+  (14.263). It can also, alternatively, hold the name of the streaming
+  service, e.g., Spotify (cf.\ rihanna:umbrella).
\end{description}}

The entries in \textsf{notes-test.bib} should at least give you a good
idea of how this all works, and that file also contains an example of
an audio book presented in a \textsf{music} entry.  If you browse the
-examples in the \emph{Manual} you will see some variations in the
-formatting choices there, from which I have made selections for
-\textsf{biblatex-chicago}.  It wasn't always clear to me that these
-variations were rules as opposed to possibilities, so I've ignored
-some of them in the code.  Arguments as to why I'm wrong will, of
-course, be entertained.  (Cf. 14.276--77; \textsf{eventdate},
+examples in the \emph{Manual} you will see the sheer variety of
+possibilities for presenting these sources, my intention being that
+judicious manipulation of\ .bib entries should allow you to make
+\textsf{biblatex-chicago} do what you want.  Please let me know if
+I've ignored something you need.  (Cf. 14.263--64; \textsf{eventdate},
bernstein:shostakovich, floyd:atom, holiday:fool, nytrumpet:art,
rubinstein:chopin.)

-\mybigspace All \mymarginpar{\textbf{mvbook}\\\textbf{mvcollection}%
-  \\\textbf{mvproceedings}\\\textbf{mvreference}} four of these entry
-types function more or less as in standard \textsf{biblatex}.  I would
-like, however, to emphasize a couple of things.  First, each is
-aliased to the entry type that results from removing the \enquote{mv}
-from their names.  Second, assuming you are using \textsf{Biber} and
-not \textsc{Bib}\TeX, each has an important role as the target of
-cross-references from other entries, the \textsf{title} of the
-\textbf{mv*} entry \emph{always} providing a \textsf{maintitle} for
-the entry referencing it.  If you want to provide a \textsf{booktitle}
-for the referencing entry, please use another entry type, e.g.,
-\textbf{collection} for \textbf{incollection} or \textbf{book} for
-\textbf{inbook}.  (These distinctions are particularly important to
-the correct functioning of the abbreviated references that
-\textsf{biblatex-chicago}, in various circumstances, provides.  Please
-see the documentation of the \textbf{crossref} field in
-section~\ref{sec:entryfields}, below.)
+\mybigspace The \colmarginpar{\textbf{mvbook}\\\textbf{mvcollection}%
+  \\\textbf{mvproceedings}\\\textbf{mvreference}} 17th edition of the
+\emph{Manual} has deployed, in at least two contexts, a notable
+syntactic change in the presentation of works that form part of other,
+larger works.  Generally, the order of presentation, in
+\textsf{biblatex} terms, has always been \textsf{title} --
+\textsf{booktitle} -- \textsf{maintitle}, in increasing order of
+generality.  In the vast majority of cases this order still holds, but
+in TV episodes, for one example, the recommendation now is to present
+the name of the series (\textsf{booktitle}) \emph{before} the name of
+the episode (\textsf{title}).  The \textbf{video} type (14.265)
+provides this by using a new \textsf{entrysubtype},
+\mycolor{\texttt{tvepisode}}, which reverses the order for you in both
+long and short notes, and in the bibliography.  The other context in
+which this reversal occurs is multi-volume works (14.116--22).  Here,
+the preferred format, at least for notes, appears to be
+\textsf{maintitle} -- \textsf{[book]title} or, when all three titles
+are present, \textsf{title} -- \textsf{maintitle} --
+\textsf{booktitle}.  The \emph{Manual} doesn't carry this reordering
+through with absolute consistency, but I think it important at least
+to offer it as a possibility to users of \textsf{biblatex-chicago}.
+Reluctant as I am simply to change the data model and provide
+non-standard entry types, the least invasive method seemed, and seems,
+to me to be to modify the \textbf{mv*} entry types while maintaining
+backward compatibility with users' current deployments of these types.

-\mylittlespace On the same subject, when multi-volume works are
-presented in the reference apparatus, the \emph{Manual} (14.121--27)
-requires that any dates presented should be appropriate to the
-specific nature of the citation.  In short, this means that a date
-range that is right for the presentation of a multi-volume work in its
-entirety isn't right for citing, e.g., a single volume of that work
-which appeared in one of the years contained in the date range.
-Because child entries will by default inherit all the date fields from
-their parent (including the \textsf{endyear} of a date range), I have
-turned off the inheritance of \textsf{date} and \textsf{origdate}
-fields from all of the \textbf{mv*} entry types to any other entry
-type.  When the dates of the parent and of the child in such a
-situation are exactly the same, then this unfortunately requires an
-extra field in the child's .bib entry.  When they're not the same, as
-will, I believe, often be the case, this arrangement saves a lot of
-annoying work in the child entry to suppress wrongly-inherited fields.
-Other sorts of parent entries aren't affected by this, and of course
-you must be using \textsf{Biber} for the settings to apply.  See
-harley:ancient:cart, harley:cartography, and harley:hoc for how this
-might look.
+\mylittlespace So, while these types are no longer aliased to the
+entry type that results from removing the \enquote{mv} from their
+names, any\ .bib entries using them should, without modification,
+continue to function as they always have.  Should you wish to ignore
+the new syntax of presentation, and there are still examples in the
+\emph{Manual} which do just that, then no changes are necessary.
+These entries will still function, assuming you are using
+\textsf{Biber}, as the target of cross-references from other entries,
+the \textsf{title} of the \textbf{mv*} entry \emph{always} providing a
+\textsf{maintitle} for the entry referencing it.  (If you want to
+provide a \textsf{booktitle} for the referencing entry, please use
+another entry type, e.g., \textbf{collection} for
+\textbf{incollection} or \textbf{book} for \textbf{inbook}.  These
+distinctions are particularly important to the correct functioning of
+the abbreviated references that \textsf{biblatex-chicago}, in various
+circumstances, provides.  Please see the documentation of the
+\textbf{crossref} field in section~\ref{sec:entryfields}, below.)

-\paragraph*{\protect\mymarginpar{\textbf{online}}}
+\mylittlespace Also unchanged is the requirement, when multi-volume
+works are presented in the reference apparatus, that any dates should
+be appropriate to the specific nature of the citation.  This means
+that a date range that is right for the presentation of a multi-volume
+work in its entirety isn't right for citing, e.g., a single volume of
+that work which appeared in one of the years contained in the date
+range.  Because child entries will by default inherit all the date
+fields from their parent (including the \textsf{endyear} of a date
+range), I have turned off the inheritance of \textsf{date} and
+\textsf{origdate} fields from all of the \textbf{mv*} entry types to
+any other entry type.  When the dates of the parent and of the child
+in such a situation are exactly the same, then this unfortunately
+requires an extra field in the child's .bib entry.  When they're not
+the same, as will, I believe, often be the case, this arrangement
+saves a lot of annoying work in the child entry to suppress
+wrongly-inherited fields.  Other sorts of parent entries aren't
+affected by this, and of course you must be using \textsf{Biber} for
+the settings to apply.
+
+\enlargethispage{\baselineskip}
+
+\mylittlespace Should you wish to employ the new,
+\textsf{maintitle}-first syntax, then you'll
+\colmarginpar{\texttt{maintitle}} need to use the new
+\mycolor{\texttt{maintitle}} \textsf{relatedtype}.  In its simplest
+usage, to document one volume of a multi-volume set, you would have,
+e.g., an \textsf{mvcollection} entry with \textsf{relatedtype}
+\texttt{maintitle}, and a \textsf{related} field pointing to a
+\textsf{collection} entry.  When you cite the \textsf{mvcollection}
+entry itself, you'll get a long note like \emph{MVCollTitle}, vol.\ 1,
+\emph{CollTitle}, and a short note like \emph{MVCollTitle}, vol.\ 1.,
+or, with a \textsf{postnote} field, \emph{MVCollTitle}, 1:12, as the
+specification requires.  If you wanted to cite one essay in the
+\textsf{collection}, then you would, additionally, need an
+\textsf{incollection} entry with the \texttt{maintitle}
+\textsf{relatedtype} and a \textsf{related} field pointing to the
+\textsf{mvcollection} entry already mentioned, so you're creating a
+chain of three different related entries but presenting them in one
+reference.  It's important to keep in mind here that, in effect,
+you're \emph{not} actually citing the \textsf{mvcollection} entry, but
+the one volume of it represented by the \textsf{collection} entry, or
+indeed an essay in that one volume.  Please consult the \emph{Manual}
+(14.116--22), and also see harley:ancient:cart, harley:cartography,
+and harley:hoc for the \enquote{old style} presentation with
+abbreviated cross references using the \textsf{crossref} field,
+harleymt:ancient:cart, harleymt:cartography and harleymt:hoc for the
+new presentation using the \texttt{maintitle} \textsf{relatedtype},
+and also plato:timaeus:gr for an example of a three-work
+\texttt{maintitle} chain starting with a \textsf{bookinbook} entry.
+
+\mylittlespace The documentation of the \texttt{maintitle}
+\textsf{relatedtype} in section~\ref{sec:related} contains all the
+details, but there are several things I should like to mention here.
+First, while you can happily mix these two methods of presentation in
+means that if you are using a \textsf{crossref} field to an
+\textsf{mvcollection} entry in a \textsf{collection} entry, say, and
+the \textsf{collection} entry is itself the target of the
+\textsf{mvcollection} entry's \textsf{related} field, please be
+careful not to cite that \textsf{collection} entry independently, as
+it can lead to unexpected results.  (If things don't look right to
+you, try eliminating the use of \textsf{crossref} entirely from these
+\textsf{related} chains and see if that helps, then send me a bug
+report if it does.)  This restriction also means that, although the
+\emph{Manual} prefers the \textsf{maintitle}-first format in notes and
+allows either syntax in the bibliography, nonetheless with
+\textsf{biblatex-chicago} whichever syntax you choose for the notes
+will also appear in the bibliography.  Second, if you want to use a
+three-work chain to cite one part of one volume, then this is possible
+only by using the following entry types: \textsf{bookinbook},
+\textsf{inbook}, \textsf{incollection}, \textsf{inproceedings}, and
+\textsf{mv*} types.  Third, as might be apparent from the previous
+list, \textsf{mvreference} entries are special, in that their
+\textsf{related} field should point to an \textsf{inreference} entry
+if you want to cite an entry in an \enquote{alphabetically arranged
+  work}, or to a \textsf{reference} entry otherwise.
+
+\mylittlespace Fourth, please remember that, as these are citations
+not of an \textsf{mv*} entry but rather of that entry's
+\textsf{related} field, any \textsf{volumes} field in the former won't
+be printed by default.  You can change this by setting the
+\texttt{hidevolumes} option to \texttt{false} either in the preamble
+or in the \textsf{options} field of the entry referenced by the
+\textsf{mv*} entry's \textsf{related} field.  Finally, if you look at
+the \enquote{mt} variants of the harley* entries mentioned above,
+you'll see that harleymt:hoc has both subsidiary volumes included in
+its \textsf{related} field.  You can create a separate \textsf{mv*}
+entry pointing to each of it's subsidiary volumes, or you can list all
+of those volumes in one \textsf{mv*} entry's \textsf{related} field
+and \textsf{biblatex-chicago} will create separate clones for each
+volume listed, clones with a standardized entry key looking like
+\enquote{\texttt{mventrykey-singlevolumeentrykey},} which you should
+then use for your citations.  The original \texttt{mventrykey}, in
+this case, refers merely to the original \textsf{mv*} entry, as though
+it had never had a \textsf{related} field, though you do need to cite
+(or \cmd{nocite}) it somewhere in your document to make the
+single-volume clones available in your reference apparatus.  The
+mechanism's designed to save you some typing in common scenarios;
+please see all of the (multifarious) details in
+section~\ref{sec:related}, below.
+
+\paragraph*{\protect\colmarginpar{\textbf{online}}}
\label{sec:online}

-The \emph{Manual}'s scattered instructions (14.4--13, 14.166--169,
-14.184--185, 14.200, 14.223, 14.243--246) for citing online materials
-are slightly different from those suggested by standard
-\textsf{biblatex}.  Indeed, this is a case where complete backward
-compatibility with other \textsf{biblatex} styles may be impossible,
-because as a general rule the \emph{Manual} considers relevant not
-only where a source is found, but also the nature of that source,
-e.g., if it's an online edition of a book (james:ambassadors), then it
-calls for a \textsf{book} entry.  Even if you cite an intrinsically
-online source, if that source is structured more or less like a
-conventional printed periodical, then you'll probably want to use
-\textsf{article} or \textsf{review} instead of \textsf{online}
-(stenger:privacy, which cites \emph{CNN.com}).  The 16th edition's
-suggestions for blogs lend themselves well to the \textsf{article}
-type, too, while comments become, logically, \textsf{reviews}
-(14.243--6; ellis:blog, ac:comment).  Otherwise, for online documents
-not \enquote{formally published,} the \textsf{online} type is usually
-the best choice (evanston:library, powell:email).  Online videos, in
-particular short pieces or those that present excerpts of some longer
-event or work, and also online interviews, usually require this type,
-too.  (See harwood:biden, horowitz:youtube, pollan:plant, but cp.\
-weed:flatiron, a complete film, which requires a \textsf{video}
-entry.)  Online audio pieces, particularly dated ones from an archive,
-work well either with an \textsf{online} entry or with a \textsf{misc}
-entry with an \textsf{entrysubtype}; the latter will print the
-\textsf{date} in somewhat closer association with the \textsf{title}
-(coolidge:speech, roosevelt:speech).  Some online materials will, no
-doubt, make it difficult to choose an entry type, but so long as all
-locating information is present, then perhaps that is enough to
-fulfill the specification, or at least so I'd like to hope.
+One of the features of the 17th edition of the \emph{Manual} is the
+considerably extended, but still scattered, treatment of online
+materials (8.189--92, 14.6--18, 14.159--63, 14.175--76, 14.187,
+14.189, 14.205--10, 14.233).  The principles of that treatment have
+changed somewhat, as the \emph{Manual} now places greater emphasis on
+the \emph{location} of a source, which can in many cases outweigh, as
+far as choosing an entry type goes, the \emph{nature} of the source.
+Working out the correspondences between online sources and
+\textsf{biblatex-chicago} entry types can, therefore, be tricky, so I
+have included table~\ref{tab:online:types} summarizing the
+increasingly detailed instructions in the \emph{Manual}, along with
+some further annotations here that might help to clarify it.

-\mylittlespace Constructing an \textsf{online} .bib file entry is much
-the same as in \textsf{biblatex}.  The \textsf{title} field would
-contain the title of the page, the \textsf{organization} field could
-hold the title or owner of the whole site.  If there is no specific
-title for a page, but only a generic one (powell:email), then such a
-title should go in \textsf{titleaddon}, not forgetting to begin that
-field with a lowercase letter so that capitalization will work out
-correctly.  It is worth remarking here, too, that the 16th edition of
-the \emph{Manual} (14.7--8) prefers, if they're available, revision
-dates to access dates when documenting online material.  See
-\textsf{urldate} and \textsf{userd}, below.
+\afterpage{\clearpage

-%\enlargethispage{\baselineskip}
+\begin{table}[h!]
+  \caption[\hspace{-1em}\mycolor{Online Entry Types - Notes \&\ Bibliography}]%
+  {Online materials and notes \&\ bibliography entry types}
+  \label{tab:online:types}
+  \centering\small\sffamily
+  \hspace*{-6em}
+  \begin{tabularx}{160mm}{@{}>{\raggedright}p{25mm}>{\raggedright}p{20mm}p{15mm}p{26mm}X@{}}
+    \toprule
+    Online Material & Entry Type & CMS Ref. & Sample Entry &
+    Notes \\
+    \cmidrule{1-1}\cmidrule(l){2-2}\cmidrule(l){3-3}\cmidrule(l){4-4}
+    \cmidrule(l){5-5}
+    Online edition of trad.\ publ.\ matter. &&&& Use the same
+    entry type as you would choose were you citing it
+    & @Book & 14.161-62 & james:ambassadors &
+    CMS prefers (scanned) original page numbers
+    & @Article @Review & 14.175 & black:infectious & If
+    no \enquote{suitable URL} is available, e.g., if it points
+    to a generic portal page rather than to an abstract,
+    use the name of the commercial database in an \textsf{addendum}
+    \hspace{.5em} Entire & @Periodical & & amlen:wordplay & The
+    \textsf{maintitle} field holds the larger publication of which the
+    blog is a part. \\
+    \hspace{.5em} Single post & @Article & & amlen:hoot &
+    \hspace{.5em} Comment & @Review & & viv:amlen & You can also
+    use the new \mycolor{\texttt{commenton}} \textsf{relatedtype} for
+    Social Media & @Online &&& This includes anything --- posts, photos,
+    videos --- on these and similar sites.  In other words, the
+    \emph{location} of the material defines its treatment. \\\addlinespace[2mm]
+    \hspace{.5em} Mailing list or \hspace*{.5em} forum post & & 14.210 &
+    powell:email & Posts on private lists are to be treated as
+    \enquote{personal communications,} using @Misc w/
+    \hspace{.5em} Comments / \hspace*{.5em} replies & & 14.210
+    The \mycolor{\texttt{commenton}} \textsf{relatedtype} is \emph{required}
+    for this, and for the next entry, too.\\\addlinespace[.8mm]
+    && 14.209 & licis:diazcomment &\\\addlinespace[.8mm]
+    \hspace{.5em} Online video & @Online & 14.267 & pollan:plant &
+    This category includes TED talks and most informal videos on
+    \hspace{.5em} Online video, \hspace*{.5em} from a trad.\ \hspace*{.5em}
+    journal & @Article &&
+    kessler:nyt & You can use @Online, but this requires special
+    formatting in the \textsf{note} or \textsf{titleaddon} field.
+    \hspace{.5em} Published films in \hspace*{.5em} an archive & @Video &&
+    \hspace{.5em} Podcasts & @Audio && danforth:podcast & Note the
+    eventdate of the individual episode.\\\addlinespace[.8mm]
+    \hspace{.5em} Archival audio & @Misc w/ \textsf{entrysubtype} & 14.264 &
+    roosevelt:speech & Can have both a venue and an origlocation.
+    \hspace*{.5em} TV / Film & @Video & 14.265 & mayberry:brady &
+    The streaming service is supplied by the URL.  The
+    \mycolor{\texttt{tvepisode}} entrysubtype is new in the 17th
+    \hspace*{.5em} Music & @Music & 14.263 & rihanna:umbrella &
+    The streaming service is supplied by the howpublished field.
+    \hspace*{.5em} News / Interviews & @Article @Review & 14.213 &
+    bundy:macneil & Network information goes in the usera field.
+    Websites & @Online & 14.206-7 & evanston:library stenger:privacy &
+    An online source \enquote{analogous to a traditionally printed
+    work but [which] does not have (and never had) a printed counterpart}
+    may now use an @Online entry, at your discretion.
+    \hspace*{.5em} Reference works, \hspace*{.5em} cited by alpha-
+    \hspace*{.5em} betized entry & @InReference w/ entrysub-\par
+    type & 14.233 & wikiped:bibtex & As above, you can choose the
+    @Online treatment of the title, but it's best achieved
+    using an @InReference entry w/ entrysubtype. \\\addlinespace[.8mm]
+    \hspace*{.5em} Scientific data- \hspace*{.5em} bases & \mycolor{@Dataset} &
+    14.257 & genbank:db & New in this release.\\\addlinespace[.8mm]
+    \bottomrule
+  \end{tabularx}
+\end{table}}

+\mylittlespace The basic principle, as I've cited in the penultimate
+entry of table~\ref{tab:online:types}, is that \enquote{the title of a
+  website that is analogous to a traditionally printed work but does
+  not have (and never had) a printed counterpart can be treated like
+  the titles of other websites, subject to editorial discretion}
+(14.206).  This means that an intrinsically online entry like
+stenger:privacy (citing CNN.com) need no longer be an \textsf{article}
+but can be presented in an \textsf{online} entry.  (The same principle
+applies to wikiped:bibtex, but because of the code facilitating
+presentation of alphabetized entries in reference works, it's best in
+this case to keep the \textsf{inreference} entry but add an
+\textsf{entrysubtype} so that the \textsf{title} is presented as it
+would be in an \textsf{online} entry.)  The corollary of the
+principle, as the first entry in table~\ref{tab:online:types}
+suggests, is that an online edition of a printed work will generally
+require the same entry type as that printed work itself would.  Blogs
+are, therefore, somewhat anomalous in requiring the various periodical
+types, though the \emph{Manual} does specify that if you're not sure
+whether a website is a blog, then it probably requires the
+\textsf{online} type (14.206).  Social media, on the other hand, are
+very much subject to the first principle, requiring \textsf{online}
+entries no matter whether the citation is of text, a photo, or a
+video.  Without pretending that all of the correspondences flow
+deductively from the basic principles, I hope that the table might
+let me know and I'll see if I can improve it.
+
+\mylittlespace A few more notes are in order. I designed the
+\colmarginpar{New!} new \textsf{relatedtype}
+\mycolor{\texttt{commenton}} to facilitate citation of online
+comments, though it works slightly differently in the two entry types
+in which it is available, \textsf{online} and \textsf{review}.  In
+both types it allows you to mimic thread structure by citing a chain
+of replies to comments on posts, etc., all in a single entry, while
+also simplifying your\ .bib entries.  This simplification works
+differently depending on whether the comment itself has no specific
+title, as always in \textsf{review} entries, or does have such a
+title, as especially in \textsf{online} social media entries.  In the
+former case, the \textsf{related} apparatus allows you not to provide
+a \textsf{title} at all, but in the latter you still need a
+\textsf{title}, which will be followed by the \textsf{relatedstring}.
+In these latter entries, the \emph{only way to cite such comments} is
+by using the \texttt{commenton} \textsf{relatedtype}
+(licis:diazcomment).  If, in \textsf{online} entries, you decided
+\emph{not} to use \textsf{commenton} in an entry like braun:reply, and
+simply use a specially-crafted \textsf{titleaddon} field, you lose the
+possibility of having two dates in the entry, one for the comment and
+one for the original post, though to be fair it does end up looking
+like the example in 14.210, where it is ambiguous to which part of the
+citation the date applies.
+
+\mylittlespace As for the thread structure, I've not tested how far
+down the rabbit hole you can go, but a series of entries linked one to
+the next by this \textsf{relatedtype} will all turn up if you cite the
+first in the chain, though of course you can use the technique merely
+as a convenient way to structure and simplify your\ .bib file, without
+creating chains longer than 2 entries.  The default connecting string
+is the localized \texttt{commenton}, but you can use
+\textsf{relatedstring} to change it to \enquote{\texttt{reply to}} or
+whatever else you need.  Please see the documentation of this
+\textsf{relatedtype} in section~\ref{sec:related}, and also
+diaz:surprise and licis:diazcomment.
+
+\mylittlespace In general, constructing an \textsf{online}\ .bib file
+entry is much the same as in \textsf{biblatex}.  The \textsf{title}
+field would contain the title of the page, the \textsf{organization}
+field could hold the title or owner of the whole site.  If there is no
+specific title for a page, but only a generic one, then such a title
+should go in \textsf{titleaddon}, not forgetting to begin that field
+with a lowercase letter so that capitalization will work out
+correctly.  It is worth remarking here, too, that the \emph{Manual}
+(14.12--13) prefers, if they're available, revision dates to access
+dates when documenting online material.  Indeed, given how rapidly
+online sources may change (14.191, 14.209, 14.233), a time stamp may
+often be necessary further to specify a revision date
+(\textsf{urldate}) or the date of a comment or reply (\textsf{date}).
+This time specification should be added to the date field using
+\textsf{biblatex's} standard format, i.e.,
+\texttt{2008-07-01T10:18:00}.  If a time zone is needed, then a
+separate \textsf{timezone} or \textsf{urltimezone} field is the best
+way, as it allows you to provide the initialisms that the
+\emph{Manual} prefers (10.41, 14.191).  See \textsf{date},
+\textsf{timezone}, \textsf{urldate}, and \textsf{userd} in
+section~\ref{sec:entryfields}, below.
+
+\enlargethispage{\baselineskip}
+
\mybigspace The \mymarginpar{\textbf{patent}} \emph{Manual} is very
-brief on this subject (14.230), but very clear about which information
+brief on this subject (14.258), but very clear about which information
it wants you to present, so such entries may not work well with other
\textsf{biblatex} styles.  The important date, as far as Chicago is
concerned, is the filing date.  If a patent has been filed but not yet
@@ -1569,23 +1970,42 @@
bibstring \texttt{patentfiled} to it.  If the patent has been granted,
then you put the filing date in the \textsf{origdate} field, and you
put the date it was issued in the \textsf{date} field, to which the
-bibstring \texttt{patentissued} will automatically be prepended.  (In
-other words, you no longer need to use a hand-formatted
-in that field if desired, and it will be printed in close association
-with the dates.)  The patent number goes in the \textsf{number} field,
-and you should use the standard \textsf{biblatex} bibstrings in the
-\textsf{type} field.  Though it isn't mentioned by the \emph{Manual},
+bibstring \texttt{patentissued} will automatically be prepended.  You
+desired, and it will be printed in close association with the dates.
+The patent number goes in the \textsf{number} field, and you should
+use the standard \textsf{biblatex} bibstrings in the \textsf{type}
+field.  Though it isn't mentioned by the \emph{Manual},
\textsf{biblatex-chicago-notes} will print the \textsf{holder} after
-the \textsf{author}, if you provide one.  Finally, the 16th edition of
-the \emph{Manual} has removed the quotation marks from around
-\textsf{patent} titles, and also capitalized them sentence-style, both
-of which seem to be the generally-accepted conventions.  The former
-requires no intervention from you, but the latter may mean revision of
-the \textsf{title} field to provide the lowercase letters manually.
-See petroff:impurity.
+the \textsf{author}, if you provide one.  Finally, the style
+automatically capitalizes \textsf{patent} titles sentence-style, so if
+you need to keep a word capitalized then you should wrap it in curly
+braces.  See petroff:impurity.

+\mybigspace The \colmarginpar{\textbf{performance}} 17th edition of
+the \emph{Manual} includes a new section (14.266) on citing live
+performances, and even though such references can usually be limited
+to the main text it may sometimes be useful to include them in notes.
+Since \textsf{biblatex} provides the \mycolor{\textbf{performance}}
+type, albeit without using it in its standard styles, I though it
+might be useful to define it for \textsf{biblatex-chicago},
+particularly as the other option for such material is the
+\textsf{misc} entry without any \textsf{entrysubtype}, and that entry
+type is already somewhat overloaded, though you can still use it if
+you wish.

+\mylittlespace Such entries will generally have a \textsf{title}, a
+\textsf{venue}, a \textsf{location} for the venue, and a \textsf{date}
+for the performance, along with a possible plethora of authorial
+and/or editorial roles depending on which sorts of contributor(s) you
+wish to emphasize in the citation.  The \textsf{editor[abc]} and
+\textsf{editor[abc]type} fields should be most helpful here.  I have
+included strings for \mycolor{\texttt{choreographer}} in all
+localization files, but for others you may need to provide them in the
+\textsf{editor[abc]type} fields as you wish them printed ---
+\textsf{biblatex-chicago} will automatically capitalize any that start
+with a lowercase letter.
+
\mybigspace This \mymarginpar{\textbf{periodical}} is the standard
\textsf{biblatex} entry type for presenting an entire issue of a
periodical, rather than one article within it.  It has the same
@@ -1597,19 +2017,27 @@
\enquote{journal.}  Also, remember that the \textsf{note} field is the
place for identifying strings like \enquote{special issue,} with its
initial lowercase letter to activate the automatic capitalization
-routines.  (See \emph{Manual} 14.187; good:wholeissue.)
+routines.  (See \emph{Manual} 14.178; good:wholeissue.)

-\mylittlespace It is worth noting that the special \textsf{biblatex}
-field \textsf{shortjournal} allows you to present shortened
-\textsf{journaltitles} in \textsf{article}, \textsf{review}, and
-\textsf{periodical} entries, as well as facilitating the creation of
-lists of journal abbreviations in the manner of a \textsf{shorthand}
-list.  Because the \textsf{periodical} type uses the \textsf{title}
-automatically copies any \textsf{shorttitle} field, if one is present,
-into \textsf{shortjournal}.  Please see the documentation of
-\textbf{shortjournal} in section~\ref{sec:entryfields} for all the
-details on how this works.
+\mylittlespace It is worth noting a couple of things.  First, the
+special \textsf{biblatex} field \textsf{shortjournal} allows you to
+present shortened \textsf{journaltitles} in \textsf{article},
+\textsf{review}, and \textsf{periodical} entries, as well as
+facilitating the creation of lists of journal abbreviations in the
+manner of a \textsf{shorthand} list.  Because the \textsf{periodical}
+type uses the \textsf{title} field instead of \textsf{journaltitle},
+\textsf{biblatex-chicago} automatically copies any \textsf{shorttitle}
+field, if one is present, into \textsf{shortjournal}.  Please see the
+documentation of \textbf{shortjournal} in
+section~\ref{sec:entryfields} for all the details on how this works.
+Second, the \textsf{periodical} type is the place for citing whole
+blogs, rather than individual blog posts, which require either an
+\textsf{article} or a \textsf{review} entry.  In \colmarginpar{New!}
+such citations the 17th edition (14.208) recommends that you include
+the name of any larger (usually periodical) publication of which the
+blog is a part.  The \textsf{maintitle} field (with
+\textsf{mainsubtitle} and \textsf{maintitleaddon}, if needed) is the
+place for it. Cf.\ amlen:wordplay.

\mybigspace This \mymarginpar{\textbf{proceedings}} is the standard
\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but the package
@@ -1635,13 +2063,13 @@
numbered sections rather than alphabetized entries, and that appears
in the bibliography as well.)

-\mybigspace This \colmarginpar{\textbf{report}} entry type is a
+\mybigspace This \mymarginpar{\textbf{report}} entry type is a
\textsf{biblatex} generalization of the traditional \textsc{Bib}\TeX\
type \textsf{techreport}.  Instructions for such entries are rather
-thin on the ground in the \emph{Manual} (8.183, 14.249), so I have
+thin on the ground in the \emph{Manual} (8.186, 14.220), so I have
followed the generic advice about formatting it like a book, and hope
that the results conform to the specification.  At least one user has
-indicated a need, now filled, for an \mycolor{\texttt{unpublished}}
+indicated a need, now filled, for an \texttt{unpublished}
\textsf{entrysubtype}, which prints the \textsf{title} inside
quotation marks instead of in italics, but affects nothing else.  This
detail aside, the type's main peculiarities are the
@@ -1652,24 +2080,19 @@
Technical Report Number of a technical report.  As in standard
\textsf{biblatex}, if you use a \textsf{techreport} entry, then the
\textsf{type} field automatically defaults to
-\cmd{bibstring\{techreport\}}.  As with \textsf{booklet} and
+\verb+\bibstring{techreport}+.  As with \textsf{booklet} and
\textsf{manual}, you can also use a \textsf{book} entry, putting the
report type in \textsf{note} and the \textsf{institution} in
\textsf{publisher}.  (See herwign:office.)

-%%\enlargethispage{\baselineskip}
-
-\mybigspace The \colmarginpar{\textbf{review}} \textsf{review} entry
-type was added to \textsf{biblatex 0.7}, and it certainly eases the
-task of coping with the \emph{Manual}'s complicated requirements for
-citing periodicals of all sorts, though it doesn't, I admit, eliminate
-all difficulties.  As its name suggests, this entry type was designed
-\textsf{article} instructions above --- if you haven't, I recommend
-doing so now --- you'll know that \textsf{review} serves as well for
-citing other sorts of material with generic titles, like letters to
-the editor, obituaries, interviews, online comments and the like.  The
-primary rule is that any piece that has only a generic title, like
+\mybigspace As \colmarginpar{\textbf{review}} its name suggests, the
+\textsf{review} entry type was designed for reviews published in
+instructions above --- if you haven't, I recommend doing so now ---
+you'll know that \textsf{review} serves as well for citing other sorts
+of material with generic titles, like letters to the editor,
+obituaries, interviews, online comments and the like.  The primary
+rule is that any piece that has only a generic title, like
\enquote{review of \ldots,} \enquote{interview with \ldots,} or
\enquote{obituary of \ldots,} calls for the \textsf{review} type.  Any
piece that also has a specific title, e.g., \enquote{\enquote{Lost in
@@ -1678,8 +2101,8 @@
periodical of some sort.  Were it found in a book, then the
\textsf{incollection} type would serve your needs, and you could use
\textsf{title} and \textsf{titleaddon} there.  While we're on the
-topic of exceptions, the \emph{Manual} includes an example --- 14.221
---- where the \enquote{Interview} part of the title is considered a
+topic of exceptions, the \emph{Manual} includes an example (14.213)
+where the \enquote{Interview} part of the title is considered a
subtitle rather than a titleaddon, said part therefore being included
inside the quotation marks and capitalized accordingly.  Not having
the journal in front of me I'm not sure what prompted that decision,
@@ -1691,42 +2114,46 @@
for which are the same as for an \textsf{article} entry.  If it is a
\enquote{magazine} or a \enquote{newspaper}, then you need an
\textsf{entrysubtype} \texttt{magazine}, or the synonymous
-\textsf{entrysubtype} \mycolor{\texttt{newspaper}}.  The generic title
-goes in \textsf{title} and the other fields work just as as they do in
-an \textsf{article} entry with the same \textsf{entrysubtype},
-including the substitution of the \textsf{journaltitle} for the
-\textsf{author} if the latter is missing. (See 14.202--203, 14.205,
-14.208, 14.214--217, 14.221; barcott:review, bundy:macneil,
-Clemens:letter, gourmet:052006, kozinn:review, nyt:obittrevor,
-nyt:trevorobit, unsigned:ranke, wallraff:\\word.)  If, on the other
-hand, the piece comes from a \enquote{journal,} then you don't need an
-\textsf{entrysubtype}.  The generic title goes in \textsf{title}, and
-the remaining fields work just as they do in a plain \textsf{article}
-entry.  (See 14.215; ratliff:review.)
+\textsf{entrysubtype} \texttt{newspaper}.  The generic title goes in
+\textsf{title} and the other fields work just as as they do in an
+\textsf{article} entry with the same \textsf{entrysubtype}, including
+the substitution of the \textsf{journaltitle} for the \textsf{author}
+if the latter is missing. (See 14.190--91, 14.195--96, 14.201--4,
+14.213; barcott:review, bundy:macneil, Clemens:letter, gourmet:052006,
+kozinn:review, nyt:obittrevor, nyt:trevorobit, unsigned:ranke,
+wallraff:word.)  If, on the other hand, the piece comes from a
+\enquote{journal,} then you don't need an \textsf{entrysubtype}.  The
+generic title goes in \textsf{title}, and the remaining fields work
+just as they do in a plain \textsf{article} entry.  (See 14.202;
+ratliff:review.)

-\mylittlespace \textsf{Biblatex-chicago} \colmarginpar{New!} now also,
-at the behest of Bertold Schweitzer, supports the \textsf{relatedtype}
-\mycolor{\texttt{reviewof}}, which allows you to use the
-\textsf{related} mechanism to provide information about the work being
-reviewed.  This may be particularly helpful if you need to cite
-multiple reviews of the same work, but in any case the usual
-distinction between \textsf{article} and \textsf{review} entries still
-holds, with the \textsf{related} entry's \textsf{title} providing the
-\textsf{titleaddon} in the former type and the \textsf{title} in the
-latter.  Please see section \ref{sec:related} for further details.
+\mylittlespace \textsf{Biblatex-chicago} also, at the behest of
+Bertold Schweitzer, supports the \textsf{relatedtype}
+\texttt{reviewof}, which allows you to use the \textsf{related}
+mechanism to provide information about the work being reviewed,
+thereby simplifying how much information you need to provide in the
+reviewing entry.  In particular, it relieves you of the need to
+construct \textsf{title} or \textsf{titleaddon} fields like:
+\verb+review of \mkbibemph{Book Title} by Author+, as the
+\textsf{related} entry's \textsf{title} automatically provides the
+\textsf{title} in the \textsf{review} type and the \textsf{titleaddon}
+in the \textsf{article} type, with the \textsf{related} mechanism
+providing the connecting string.  This may be particularly helpful if
+you need to cite multiple reviews of the same work; please see section
+\ref{sec:related} for further information.

\mylittlespace Most of the onerous details are the same as I described
them in the \textbf{article} section above, but I'll repeat some of
them briefly here.  If anything in the \textsf{title} needs
formatting, you need to provide those instructions yourself, as the
-default is completely plain.  (The \textsf{related} mechanism just
-mentioned provides this automatically.)  \textsf{Author}-less reviews
+default is completely plain.  (As just mentioned, the \textsf{related}
+mechanism provides this automatically.)  \textsf{Author}-less reviews
are treated just like similar newspaper articles --- in short notes
and in the bibliography the \textsf{journaltitle} replaces the author
and heads the entry, while in long notes the \textsf{title} comes
first.  The sorting of such entries is an issue, solved if you use
\textsf{Biber} as your backend, and otherwise requiring manual
-intervention with a \textsf{sortkey} or the like (14.217;
+intervention with a \textsf{sortkey} or the like (14.204;
gourmet:052006, nyt:trevorobit, unsigned:ranke, and see
\cmd{DeclareSortingTemplate} in section~\ref{sec:formatopts}, below.).
As in \textsf{misc} entries with an \textsf{entrysubtype}, words like
@@ -1737,34 +2164,87 @@
lowercase letter.  The file \textsf{notes-test.bib} and the
documentation of \cmd{autocap} will provide guidance here.

-\mylittlespace One detail of the \textsf{review} type is fairly new,
-and responds to the needs of the 16th edition of the \emph{Manual}.
-As I mentioned above, blogs are best treated as \textsf{articles} with
-\texttt{magazine} \textsf{entrysubtype}, whereas comments on those
-blogs --- or on any similar sort of online content --- need the
-\textsf{review} type with the same \textsf{entrysubtype}.  What they
-will frequently also need is a date of some sort closely associated
-with the comment (14.246; ac:comment), so I have included the
+\mylittlespace One \colmarginpar{New!} detail of the \textsf{review}
+type is fairly new, and in particular has changed between the 16th and
+17th editions of the \emph{Manual}.  As I mentioned above, blogs are
+best treated as \textsf{articles} with \texttt{magazine}
+\textsf{entrysubtype}, whereas comments on those blogs --- or replies
+to those comments, etc.\ --- need the \textsf{review} type with the
+same \textsf{entrysubtype}.  (Neither need appear in the
+bibliography.)  What they also need is a date closely associated with
+the comment (14.208; ac:comment), so I have included the
\textsf{eventdate} in \textsf{review} entries for just this purpose.
It will be printed just after the \textsf{author} and before the
-\textsf{title}.  If you need a timestamp in addition, then the
-\textsf{nameaddon} field is the place for it, but you'll have to
-provide your own parentheses, in order to preserve the possibility of
-providing pseudonyms in square brackets that is the standard function
-of this field in all other entry types, and possibly in the the
-\textsf{review} type as well.
+\textsf{title}.  If you need a time stamp in addition, as may
+frequently be the case with multiple contributions by the same author
+to a single thread, then you should now use the standard
+\textsf{biblatex} time-stamp format (e.g.,
+\texttt{2008-07-01T10:18:00}) in the \textsf{eventdate} field itself,
+which \textsf{biblatex-chicago} will format and print appropriately.
+Please see the documentation concerning time stamps in
+section~\ref{sec:entryfields}, s.v.\ \mycolor{\textsf{date}}.  This
+change allows the \textsf{nameaddon} field to revert to its primary
+use, which is to provide extra information about the \textsf{author}.
+In blog comments, this could include the commenter's geographical
+location, which you need to enclose in parentheses, as I've removed
+the automatic square brackets from this field to allow it this more
+general usefulness.  You can, of course, still provide your own square
+brackets in \textsf{review} entries to indicate pseudonymous
+authorship, which is the standard function of \textsf{nameaddon} in
+most entry types.

-\mylittlespace For the reasons I explained in the \textsf{article}
-docs above, I have brought the \textsf{article} and \textsf{review}
-entry types into line with most of the other types in allowing the use
-of the \textsf{namea} and \textsf{nameb} fields in order to associate
-an editor or a translator specifically with the \textsf{title}.  The
-\textsf{editor} and \textsf{translator} fields, in strict homology
-with other entry types, are associated with the \textsf{issuetitle} if
-one is present, and with the \textsf{title} otherwise.  The usual
-string concatenation rules still apply --- cf.\ \textsf{editor} and
-\textsf{editortype} in section~\ref{sec:entryfields}, below.
+\mylittlespace In \colmarginpar{New!} this context I should mention a
+small change to the default behavior of \textsf{review} entries when
+they utilize a \textsf{crossref} or \textsf{xref} field, as is really
+only useful when the entry is a blog comment, as otherwise there won't
+generally be any fields worth inheriting from the reviewed entry.
+Assuming the default values of the \textsf{biblatex-chicago} option
+\texttt{longcrossref}, the driver now explicitly tests if the reviewed
+entry has already been cited, and accordingly shortens the reviewing
+citation, as the \emph{Manual} (14.208) suggests (viv:amlen).  (This
+would be incorrect for, say, a book review, so you should either not
+use a \textsf{crossref} or \textsf{xref} field there, or change the
+state of the \texttt{longcrossref} option --- cf.\ the documentation
+starting on page~\pageref{sec:crossref}, below.)  You
+\colmarginpar{\texttt{blogurl}} can, if you wish, and while we're on
+this subject, set the new preamble option \mycolor{\texttt{blogurl}}
+to allow your child comments to inherit the URL from the parent blog.

+\mylittlespace Also \colmarginpar{New!} new in this release is the
+\textsf{relatedtype} \mycolor{\texttt{commenton}}, which allows you to
+simplify your\ .bib entries in much the same way as the
+\texttt{reviewof} \textsf{relatedtype} does, i.e., it constructs your
+\textsf{title} field for you (which the \textsf{crossref} mechanism
+doesn't do).  It further allows you to mimic thread structure by
+citing a chain of replies to comments on blogs, etc., all in a single
+entry, while also simplifying your\ .bib entries.  I've not tested how
+far down the rabbit hole you can go, but a series of entries linked
+one to the next by this \textsf{relatedtype} will all turn up if you
+cite the first in the chain, though of course you can use the
+technique merely as a convenient way to structure and simplify your\
+.bib file, without creating chains longer than 2 entries.  The default
+connecting string is the localized \texttt{commenton}, but you can use
+\textsf{relatedstring} to change it to \enquote{\texttt{reply to}} or
+whatever else you need.  Please see the documentation of this
+\textsf{relatedtype} in section~\ref{sec:related}, and also
+ellis:blog, ac:comment, and the (fictional) ellis:reply.  Note also
+that this way of structuring your\ .bib file is by no means required
+in \textsf{review} entries, though if you want to cite replies and
+entry type, you will need to use this \textsf{relatedtype}.
+
+\mylittlespace Two more notes.  For the reasons I explained in the
+\textsf{article} docs above, I have brought the \textsf{article} and
+\textsf{review} entry types into line with most of the other types in
+allowing the use of the \textsf{namea} and \textsf{nameb} fields in
+order to associate an editor or a translator specifically with the
+\textsf{title}.  The \textsf{editor} and \textsf{translator} fields,
+in strict homology with other entry types, are associated with the
+\textsf{issuetitle} if one is present, and with the \textsf{title}
+otherwise.  The usual string concatenation rules still apply --- cf.\
+\textsf{editor} and \textsf{editortype} in
+section~\ref{sec:entryfields}, below.
+
\mylittlespace Finally, the special \textsf{biblatex} field
\textsf{shortjournal} allows you to present shortened
\textsf{journaltitles} in \textsf{review} entries, as well as in
@@ -1774,6 +2254,49 @@
\textbf{shortjournal} in section~\ref{sec:entryfields} for all the
details on how this works.

+\mybigspace In \colmarginpar{\textbf{standard}} older releases it was
+fairly straightforward to present published national or international
+standards using a \textsf{book} entry, but with some additional
+specifications now included in the 17th edition of the \emph{Manual}
+(14.259) I think it might be helpful to provide a separate entry type.
+The \mycolor{\textbf{standard}} type has long existed in
+\textsf{biblatex}, though none of its included styles use it.  In
+\textsf{biblatex-chicago} constructing such an entry is mostly
+straightforward.  The organization responsible for the standard goes
+in \textsf{organization}, the title in \textsf{title}, and the
+\textsf{series} and \textsf{number} fields provide the ID of the
+standard.  The \textsf{date} field generally provides the publication
+date, though for some standards there may also be a later
+reaffirmation date (or similar), for which you can use the
+\textsf{eventdate}.
+
+\mylittlespace Now, for the peculiarities.  In the bibliography, the
+\textsf{organization} will appear at the head of the entry, and will
+be reprinted as the publisher.  If you wish to provide a shortened
+version for the second appearance, then the \textsf{publisher} field
+is the place for it.  In long notes, the entry starts with the
+\textsf{title}, so there the code prefers the \textsf{organization} as
+publisher, because its shortened version may not be immediately
+recognizable.  In short notes, only the \textsf{title} will appear
+(along with any \textsf{pre} or \textsf{postnote} fields, obviously).
+You can use the \textsf{author} field in addition to the
+\textsf{organization}, but this is unnecessary.  If you absolutely
+must have the \textsf{organization} or \textsf{author} appear at the
+head of long and short notes, then providing any \textsf{entrysubtype}
+whatsoever will accomplish this.  Any named \textsf{editor} or
+\textsf{namec} will, as per the specification, \emph{not} appear at
+the head of entries.  You can really only alter this by using a
+
+\mylittlespace Finally, it is distinctly possible that an entry with
+two dates will need somehow to specify just what sort of dates are
+involved.  The usual \textsf{biblatex-chicago} method is the
+\textsf{userd} field, and here that field will act as a date-type for
+the \textsf{date} field itself.  For the \textsf{eventdate}, you'll
+need to use \textsf{howpublished}, which I have commandeered for this
+purpose in a few other entry types, as well.  (Cf.\ niso:bibref and
+\textbf{howpublished} in section~\ref{sec:entryfields}, below.)
+
\mybigspace This \mymarginpar{\textbf{suppbook}} is the entry type to
use if the main focus of a reference is supplemental material in a
book or in a collection, e.g., an introduction, afterword, or forward,
@@ -1799,15 +2322,13 @@
that unless you use a \cmd{bibstring} command in the \textsf{type}
field, the resultant entry will not be portable across languages.)

-%\enlargethispage{-\baselineskip}
-
\mylittlespace There are a few other rules for constructing your .bib
entry.  The \textsf{author} field refers to the author of the
introduction or afterword, while \textsf{bookauthor} refers to the
-author of the main text of the work, if the two differ.  For the 16th
-edition, the \emph{Manual} requires the inclusion of the page range of
-the part in question, though \emph{only} in the bibliography.  I have
-followed this advice literally, so the \textsf{pages} field of a
+author of the main text of the work, if the two differ.  The
+\emph{Manual} requires the inclusion of the page range of the part in
+question, though \emph{only} in the bibliography.  I have followed
+this advice literally, so the \textsf{pages} field of a
\textsf{suppbook} entry won't automatically appear in a long note.  If
you wish to include those pages in a note, then you'll need to repeat
them in the \textsf{postnote} field of the citation command.
@@ -1818,7 +2339,7 @@
normal \textsf{biblatex} rules apply, and you can just put their name
in the appropriate field of a \textsf{book} entry, that is, in the
\textsf{foreword}, \textsf{afterword}, or \textsf{introduction} field.
-(See \emph{Manual} 14.116; polakow:afterw, prose:intro).
+(See \emph{Manual} 14.110; polakow:afterw, prose:intro).

\mybigspace This \mymarginpar{\textbf{suppcollection}} fulfills a
function analogous to \textsf{suppbook}.  Indeed, I believe the
@@ -1826,19 +2347,16 @@
both types of work, so this entry type is an alias to
\textsf{suppbook}, which see.

-\mybigspace This \mymarginpar{\textbf{suppperiodical}} type, new in
-\textsf{biblatex} 0.8, is intended to allow reference to
-generically-titled works in periodicals, such as regular columns or
-letters to the editor.  Previous releases of
-\textsf{biblatex-chicago-notes} provided the \textsf{review} type for
-this purpose, and now you can use either of these, as I've added
+\mybigspace This \mymarginpar{\textbf{suppperiodical}} type is
+intended to allow reference to generically-titled works in
+periodicals, such as regular columns or letters to the editor.
+\textsf{Biblatex-chicago-notes} provides the \textsf{review} type for
+this purpose, and you can use either of these, as I've added
\textsf{suppperiodical} as an alias of \textsf{review}.  Please see
above under \textbf{review} for the full instructions on how to
construct a .bib entry for such a reference.

-%\enlargethispage{\baselineskip}
-
-\mybigspace The \colmarginpar{\textbf{unpublished}}
+\mybigspace The \mymarginpar{\textbf{unpublished}}
\textsf{unpublished} entry type works largely as it does in standard
\textsf{biblatex}, though it's worth remembering that you should use a
lowercase letter at the start of your \textsf{note} field (or perhaps
@@ -1852,15 +2370,22 @@
prompting of Jan David Hauck, you can use the \textsf{venue},
fields further to specify unpublished conference papers and the like

-\mybigspace This \mymarginpar{\textbf{video}} is the last of the three
-audiovisual entry types, and as its name suggests it is intended for
-citing visual media, be it films of any sort or TV shows, broadcast,
-on the Net, on VHS, DVD, or Blu-ray.  As with the \textsf{music} type
-production roles found, e.g., on a DVD, to those bookish ones provided
-by \textsf{biblatex}.  Here are the main correspondences:
+\mybigspace This \colmarginpar{\textbf{video}} is the last of the
+three audiovisual entry types, and as its name suggests it is intended
+for citing visual media, be it films of any sort or TV shows, whether
+broadcast, on the Net, on VHS, DVD, or Blu-ray, though it will serve
+as well, I think, for radio broadcasts of plays or drama serials.  As
+with the \textsf{music} type discussed above, certain choices had to
+be made when associating the production roles found, e.g., on a DVD,
+to those bookish ones provided by \textsf{biblatex}.  The 17th edition
+of the \emph{Manual} once again revised its recommendations for this
+type, but fortunately the changes are additive, i.e., you can re-use
+16th-edition citations but are encouraged to peruse the following
+guidelines to see if there's any information you might think of adding
+to bring your citations more into line with the spec.  Here are the
+main guidelines:

\begin{description}
@@ -1877,13 +2402,16 @@
usual \texttt{useauthor} and \texttt{useeditor} options can alter
the presentation within an entry.  Because these are non-standard
roles, you will need to identify them using the following:
-\item[editortype, editoratype, editorbtype:] The most common roles,
-  all associated with specific bibstrings (or their absence), will
-  likely be \texttt{director}, \texttt{produ\-cer}, and, oddly,
+\item[\mycolor{editortype, editoratype, editorbtype:}] The most common
+  roles, all associated with specific bibstrings (or their absence),
+  will likely be \texttt{director}, \texttt{producer}, and, oddly,
\texttt{none}.  The last is particularly useful if you want to
identify performers, as they usually don't need further specifying
and this role prevents \textsf{biblatex} from falling back on the
-  default \texttt{editor} bibstring.
+  default \texttt{editor} bibstring.  Any other roles you want to
+  emphasize, even if there is no pre-defined \cmd{bibstring}, can be
+  provided here, and will be printed as-is, contextually capitalized.
+  (Cf.\ hitchcock:nbynw.)
with the other audiovisual types, \textsf{video} serves as an
analogue both to books and to collections, so the \textsf{title} may
@@ -1890,33 +2418,57 @@
be of a whole film DVD or of a TV series, or it may identify one
episode in a series or one scene in a film.  In the latter cases,
the title of the whole would go in \textsf{booktitle}.  The
-  \textsf{booktitleaddon} field, in a change from the 15th edition,
-  may be useful for specifying the season and/or episode number of a
-  TV series, while the \textsf{titleaddon} is for for any information
-  that needs to come between the \textsf{title} and the
-  \textsf{booktitle} (cleese:holygrail, friends:leia, handel:messiah).
-  As in the \textsf{music} type, \textsf{maintitle} may be necessary
-  for a boxed set or something similar.
+  \textsf{booktitleaddon} field is the place for specifying the season
+  and/or episode number of a TV series, while the \textsf{titleaddon}
+  is for any information that needs to come between the \textsf{title}
+  and the \textsf{booktitle} (american:crime, cleese:holygrail,
+  friends:\break leia, handel:messiah, hitchcock:nbynw,
+  mayberry:brady).  As in the \textsf{music} type, a
+  \textsf{maintitle} may be necessary for a boxed set or something
+  similar.
+\item[\mycolor{entrysubtype:}] If, for some reason, you want to cite
+  an individual episode or scene without reference to any larger unit,
+  then your entry will contain only a \textsf{title}, which
+  \textsf{biblatex-chicago} would normally interpret as the title of a
+  complete film or TV series.  In such a case, you'll need to define
+  an \textsf{entrysubtype} to let it know that the lone \textsf{title}
+  is such a sub-unit.  In quite a different syntactic transformation,
+  the 17th edition (14.265) now recommends that, when presenting
+  episodes from a TV series, the name of the series
+  (\textsf{booktitle}) comes before the episode name (\textsf{title}).
+  The exact string \mycolor{\texttt{tvepisode}} in the
+  \textsf{entrysubtype} field achieves this reversal, which includes
+  using the \textsf{booktitle} as a \textsf{sorttitle} in the
+  bibliography and also as the \textsf{labeltitle} in short notes.
+\item[\mycolor{usera:}] When citing recordings of TV shows, the 17th
+  edition now wants you to include the TV network for the original
+  broadcast, and the \mycolor{\textsf{usera}} field is the place for
+  it.  \textsf{Biblatex-chicago} has long used this field for this
+  same purpose in \textsf{article, periodical}, and \textsf{review}
+  entries with a \texttt{magazine} \textsf{entrysubtype}, so its
+  inclusion here can at least hope to benefit from that prior
+  acquaintance.  It will appear after the broadcast date, i.e., the
+  \textsf{eventdate}, and will be separated from it by the
+  \cmd{bibstring} \enquote{\texttt{on.}}
\item[date, eventdate, origdate:] As with \textsf{music} entries, in
-  order to follow the specifications of the 16th edition of the
-  \emph{Manual}, I have had to provide three separate date fields for
-  citing \textsf{video} sources, but their uses differ somewhat
-  between the two types.  In both, the \textsf{date} will generally
-  provide the publishing or copyright date of the medium you are
-  referencing.  The \textsf{eventdate} will most commonly present
-  either the broadcast date of a particular TV program, or the
-  recording/performance date of, for example, an opera on DVD.  The
-  style will automatically prepend the bibstring \texttt{broadcast} to
-  such a date, though you can use the \textsf{userd} field to change
-  the string printed there.  (Absent an \textsf{eventdate}, the
-  \textsf{userd} field in \textsf{video} entries will modify the
-  \textsf{urldate}, and absent those two it will modify the
-  \textsf{date}.)  The \textsf{origdate} has more or less the same
-  function, and appears in the same places, as it does in standard
-  book-like entries, providing the date of first release of a film,
-  though there isn't any \texttt{reprint} string associated with it in
-  this entry type.  Cf.\ friends:leia, handel:messiah,
-  hitchcock:nbynw.
+  order to follow the specifications of the \emph{Manual}, I have had
+  to provide three separate date fields for citing \textsf{video}
+  sources, but their uses differ somewhat between the two types.  In
+  both, the \textsf{date} will generally provide the publishing or
+  copyright date of the medium you are referencing.  The
+  \textsf{eventdate} will most commonly present either the broadcast
+  date of a particular TV program, or the recording/performance date
+  of, for example, an opera on DVD.  The style will automatically
+  prepend the bibstring \texttt{broadcast} to such a date, though you
+  can use the \textsf{userd} field to change the string printed there.
+  (Absent an \textsf{eventdate}, the \textsf{userd} field in
+  \textsf{video} entries will modify the \textsf{urldate}, and absent
+  those two it will modify the \textsf{date}.)  The \textsf{origdate}
+  has more or less the same function, and appears in the same places,
+  as it does in standard book-like entries, providing the date of
+  first release of a film, though there isn't any \texttt{reprint}
+  string associated with it in this entry type.  Cf.\ friends:leia,
+  handel:messiah, hitchcock:nbynw.
\item[type:] As in all the audiovisual entry types, the \textsf{type}
field holds the medium of the \textsf{title}, e.g., 8 mm, VHS, DVD,
Blu-ray, MPEG.
@@ -1924,7 +2476,7 @@

As with the \textsf{music} type, entries in \textsf{notes-test.bib}
should at least give you a good idea of how all this works.  (Cf.\
-14.279--80; loc:city, weed:flatiron.)
+14.265, 14.267; loc:city, weed:flatiron.)

\subsection{Entry Fields}
\label{sec:entryfields}
@@ -1940,23 +2492,19 @@

\textsf{biblatex}, this field allows you to add miscellaneous
-information to the end of an entry, after publication data but, with
-the single exception of the \textsf{online} entry type, before any
-\textsf{url} or \textsf{doi} field.  In the \textsf{patent} entry type
-(which see), it will be printed in close association with the filing
-and issue dates.  In a few entry types --- \textsf{article},
-\textsf{audio}, \textsf{music}, \textsf{periodical}, \textsf{review},
-and \textsf{video} --- this information will come \emph{after} any
-\textsf{pages} or \textsf{postnote} references present in long notes,
-while in the remainder it comes \emph{before} such information,
-allowing you in particular to use the field to identify a particular
-type of book-like publication when such data won't fit well in another
-part of an entry.  In any entry type, if your data begins with a word
-that would ordinarily only be capitalized at the beginning of a
-sentence, then simply ensure that that word is in lowercase, and the
-style will take care of the rest.  Cf.\ \textsf{note}. (See
-\emph{Manual} 14.119, 14.166--168; davenport:attention,
-natrecoff:camera.)
+information to the end of an entry, after publication data but before
+any \textsf{url} or \textsf{doi} field.  In the \textsf{patent} entry
+type (which see), it will be printed in close association with the
+filing and issue dates.  In all other entry types this information
+will come \emph{after} any \textsf{pages} or \textsf{postnote}
+references present in long notes, allowing you in particular to use
+the field to identify a particular type of book-like publication when
+such data won't fit well in another part of an entry.  In any entry
+type, if your data begins with a word that would ordinarily only be
+capitalized at the beginning of a sentence, then simply ensure that
+that word is in lowercase, and the style will take care of the rest.
+Cf.\ \textsf{note}. (See \emph{Manual} 14.114, 14.159--63;
+davenport:attention, natrecoff:camera.)

\mybigspace In most \mymarginpar{\textbf{afterword}} circumstances,
this field will function as it does in standard \textsf{biblatex},
@@ -1969,8 +2517,6 @@
then \textsf{biblatex-chicago-notes} will concatenate these fields in
the formatted references.

-%\vspace{\baselineskip}
-
\mylittlespace As noted above, however, this field has a special
meaning in the \textsf{suppbook} entry type, used to make an
afterword, foreword, or introduction the main focus of a citation.  If
@@ -1977,29 +2523,28 @@
it's an afterword at issue, simply define \textsf{afterword} any way
you please, leave \textsf{foreword} and \textsf{introduction}
undefined, and \textsf{biblatex-chicago-notes} will do the rest. Cf.\
-\textsf{foreword} and \textsf{introduction}. (See \emph{Manual} 14.91,
-14.116; polakow:afterw.)
+\textsf{foreword} and \textsf{introduction}. (See \emph{Manual}
+14.105, 14.110; polakow:afterw.)

\paragraph*{\protect\mymarginpar{\textbf{annotation}}}
\label{sec:annote}

-At the request of Emil Salim, \textsf{biblatex-chicago-notes} has,
-since version 0.9, provided a package option (see \texttt{annotation}
-below, section \ref{sec:useropts}) to allow you to produce annotated
-bibliographies.  The formatting of such a bibliography is currently
-fairly basic, though it conforms with the \emph{Manual's} minimal
-guidelines (14.59).  The default in \textsf{chicago-notes.cbx} is to
-define \cmd{DeclareFieldFormat\{an\-notation\}} using
-\cmd{par}\cmd{no\-break} \cmd{vskip} \cmd{bibitemsep}, though you can
-alter it by re-declaring the format in your preamble.  The
-page-breaking algorithms don't always give perfect results here, but
-the default formatting looks, to my eyes, fairly decent.  In addition
-to tweaking the field formatting you can also insert \cmd{par} (or
-even \cmd{vadjust\{\cmd{eject}\}}) commands into the text of your
-annotations to improve the appearance.  Please consider the
-\texttt{annotation} option a work in progress, but it is usable now.
-(N.B.: The \textsc{Bib}\TeX\ field \textsf{annote} serves as an alias
-for this.)
+At the request of Emil Salim, \textsf{biblatex-chicago-notes} provides
+a package option (see \texttt{annotation} below, section
+\ref{sec:useropts}) to allow you to produce annotated bibliographies.
+The formatting of such a bibliography is currently fairly basic,
+though it conforms with the \emph{Manual's} minimal guidelines
+(14.64).  The default in \textsf{chicago-notes.cbx} is to define
+\verb+\DeclareFieldFormat{annotation}{\par\nobreak\vskip\bibitemsep #1}+;
+if ne\-cessary you can alter it by re-declaring the format in
+your preamble.  The page-breaking algorithms don't always give perfect
+results here, but the default formatting looks, to my eyes, fairly
+decent.  In addition to tweaking the field formatting you can also
+insert \cmd{par} (or even \verb+\vadjust{\eject}+) commands into
+consider the \texttt{annotation} option a work in progress, but it is
+usable now.  (N.B.: The old \textsc{Bib}\TeX\ field \textsf{annote}
+serves as an alias for this.)

\mybigspace I \mymarginpar{\textbf{annotator}} have implemented this
\textsf{biblatex} field pretty much as that package's standard styles
@@ -2006,30 +2551,27 @@
do, even though the \emph{Manual} doesn't actually mention it.  It may
be useful for some purposes.  Cf.\ \textsf{commentator}.

-%%\enlargethispage{\baselineskip}
-
\mybigspace For \mymarginpar{\textbf{author}} the most part, I have
-implemented this field in a completely standard \textsc{Bib}\TeX\
-fashion.  Remember that corporate or organizational authors need to
-have an extra set of curly braces around them (e.g.,
-\texttt{\{\{Associated Press\}\}}\,) to prevent \textsc{Bib}\TeX\ from
-treating one part of the name as a surname (14.92, 14.212;
-assocpress:gun, chicago:man\-ual).  If there is no \textsf{author}, then
-\textsf{biblatex-chicago-notes} will, in the bibliography and long
-notes, look in sequence, for a \textsf{namea}, an \textsf{editor}, a
-\textsf{nameb}, a \textsf{translator}, or a \textsf{namec} (i.e., a
-compiler) and use that name (or those names) instead, followed by the
-appropriate identifying string (esp.\ 14.87, also 14.76, 14.126,
-14.132, 14.189; boxer:china, brown:bre\-mer, harley:cartography,
-schellinger:novel, sechzer:women, silver:gawain, soltes:geor\-gia).
-\textsf{Biblatex's} sorting algorithms will use the first of those
-names found, which should ensure correct alphabetization in the
-bibliography.  (See \cmd{DeclareSortingTemplate} in
-section~\ref{sec:formatopts}, below.)  In short notes, where the
-\textsf{labelname} is used, the order searched is somewhat augmented:
-\textsf{shortauthor, author, shorteditor, namea, editor, nameb,
-  translator, namec}.  (See \cmd{DeclareLabelname} in
-section~\ref{sec:formatopts}.)
+implemented this field in a completely standard fashion.  Remember
+that corporate or organizational authors need to have an extra set of
+curly braces around them (e.g., \texttt{\{\{Associated Press\}\}}\,)
+to prevent \textsf{biber} from treating one part of the name as a
+surname (14.84, 14.200; assocpress:gun, chicago:manual).  If there is
+no \textsf{author}, then \textsf{biblatex-chicago-notes} will, in the
+bibliography and long notes, look in sequence, for a \textsf{namea},
+an \textsf{editor}, a \textsf{nameb}, a \textsf{translator}, or a
+\textsf{namec} (i.e., a compiler) and use that name (or those names)
+instead, followed by the appropriate identifying string (esp.\ 14.103,
+also 14.76, 14.121, 14.126, 14.180; boxer:china, brown:bre\-mer,
+harley:cartography, schellinger:novel, sechzer:women, silver:gawain,
+soltes:geor\-gia).  \textsf{Biblatex's} sorting algorithms will use
+the first of those names found, which should ensure correct
+alphabetization in the bibliography.  (See
+\cmd{DeclareSortingTemplate} in section~\ref{sec:formatopts}, below.)
+In short notes, where the \textsf{labelname} is used, the order
+searched is somewhat augmented: \textsf{shortauthor, author,
+  shorteditor, namea, editor, nameb, translator, namec}.  (See
+\cmd{DeclareLabelname} in section~\ref{sec:formatopts}.)

\mylittlespace In the rare cases when this substitution mechanism
isn't appropriate, you have (at least) two options: either you can
@@ -2046,11 +2588,13 @@
latter doesn't work as smoothly and completely as \textsf{biblatex's}
own name toggles.

+\enlargethispage{\baselineskip}
+
\mylittlespace This system of options, then, can turn off
\textsf{biblatex-chicago-notes}'s mechanism for finding a name to
place at the head of an entry, but it also very usefully adds the
possibility of citing a work with an \textsf{author} by its editor,
-compiler or translator instead (14.90; eliot:pound), something that
+compiler or translator instead (14.104; eliot:pound), something that
wasn't possible before.  For full details of how this works, see the
\textsf{editortype} documentation below.  (Of course, in
\textsf{collection}, \textsf{periodical} and \textsf{proceedings}
@@ -2063,7 +2607,7 @@

\mylittlespace \textbf{NB}: The \emph{Manual} provides specific
instructions for formatting the names of both anonymous and
-pseudonymous authors (14.79--84).  In the former case, if no author is
+pseudonymous authors (14.79--82).  In the former case, if no author is
known or guessed at, then it may simply be omitted
(virginia:plantation).  The use of \enquote{Anonymous} as the name is
\enquote{generally to be avoided,} but may in some cases be useful
@@ -2082,34 +2626,34 @@
\textsf{authortype} field, \textsf{biblatex-chicago-notes} will also
do the right thing automatically in the short note form.

-\mylittlespace In most entry types (except \textsf{customc} and
-\textsf{review}, which see), the \textsf{nameaddon} field furnishes
-the means to cope with the case of pseudonymous authorship.  If the
-author's real name isn't known, simply put \texttt{pseud.}\,(or
-\cmd{bibstring\{pseudonym\}}) in that field (centinel:letters).  If
-you wish to give a pseudonymous author's real name, simply include it
-there, formatted as you wish it to appear, as the contents of this
-field won't be manipulated as a name by \textsf{biblatex}
-(lecarre:quest).  If you have given the author's real name in the
-\textsf{author} field, then the pseudonym goes in \textsf{nameaddon},
-in the form \texttt{Firstname Lastname,\,pseud.}\ (creasey:ashe:blast,
-creasey:morton:hide, creasey:york:death).  This latter method will
-allow you to keep all references to one author's work under different
-pseudonyms grouped together in the bibliography, as recommended by the
-\emph{Manual}, though it is now recommended that, whichever system you
-employ, you include a cross-reference from one name to the other in
-the bibliography.  You can do this using a \textsf{customc} entry
-(ashe:creasey, morton:creasey, york:creasey).
+\mylittlespace In most entry types (except \textsf{customc}), the
+\textsf{nameaddon} field furnishes the means to cope with the case of
+pseudonymous authorship.  If the author's real name isn't known,
+simply put \texttt{pseud.}\,(or \verb+\bibstring{pseudonym}+) in that
+field (centinel:letters).  If you wish to give a pseudonymous author's
+real name, simply include it there, formatted as you wish it to
+appear, as the contents of this field won't be manipulated as a name
+by \textsf{biblatex} (lecarre:quest).  If you have given the author's
+real name in the \textsf{author} field, then the pseudonym goes in
+\textsf{nameaddon}, in the form \texttt{Firstname Lastname,\,pseud.}\
+(creasey:ashe:blast, creasey:morton:hide, creasey:york:death).  This
+latter method will allow you to keep references to one author's work
+under different pseudonyms grouped together in the bibliography, as
+recommended by the \emph{Manual}, though it is now recommended that,
+whichever system you employ, you include a cross-reference from one
+name to the other in the bibliography.  You can do this using a
+\textsf{customc} entry (ashe:creasey, morton:creasey, york:creasey).
+circumstances where you may need to provide your own square brackets
+when presenting a pseudonym.

-% %\enlargethispage{\baselineskip}
-
\mybigspace In \mymarginpar{\textbf{authortype}}
\textsf{biblatex-chicago}, this field serves a function very much in
keeping with the spirit of standard \textsf{biblatex}, if not with its
letter.  Instead of allowing you to change the string used to identify
an author, the field allows you to indicate when an author is
-anonymous, that is, when his or her name doesn't appear on the title
-page of the work you are citing.  As I've just detailed under
+anonymous, that is, when their name doesn't appear on the title page
+of the work you are citing.  As I've just detailed under
\textsf{author}, the \emph{Manual} generally discourages the use of
\enquote{Anonymous} as an author, preferring that you simply omit it.
If, however, the name of the author is known or guessed at, then
@@ -2121,7 +2665,7 @@
for these \emph{exact} strings, so check your typing if you don't see
the brackets.  Assuming the strings are correct,
\textsf{biblatex-chicago-notes} will also automatically do the right
-thing in the short note form.  Cf.\ \textsf{author}.  (See 14.80--81;
+thing in the short note form.  Cf.\ \textsf{author}.  (See 14.79--80;
cook:sotweed, horsley:prosodies.)

\mybigspace For \mymarginpar{\textbf{bookauthor}} the most part, as in
@@ -2133,7 +2677,7 @@
(\textsf{suppbook}) uses \textsf{bookauthor} as the author of
\textsf{title} (polakow:afterw, prose:intro).

-\mybigspace This, \mymarginpar{\vspace{-12pt}\textbf{bookpagination}}
+\mybigspace This, \mymarginpar{\vspace{-8pt}\textbf{bookpagination}}
a standard \textsf{biblatex} field, allows you automatically to prefix
the appropriate string to information you provide in a \textsf{pages}
field.  If you leave it blank, the default is to print no identifying
@@ -2155,7 +2699,7 @@
strings you expect.  Second, remember that \textsf{bookpagination}
applies only to the \textsf{pages} field --- if you need to format a
citation's \textsf{postnote} field, then you must use
-\textsf{pagination}, which see (10.43--44, 14.154--163).
+\textsf{pagination}, which see (10.42--43, 14.147--56).

\mybigspace The \mymarginpar{\textbf{booksubtitle}} subtitle for a
\textsf{booktitle}.  See the next entry for further information.
@@ -2173,8 +2717,8 @@
\textsf{book} or \textsf{collection}), but there it will almost
invariably be providing information for the traditional
\textsc{Bib}\TeX\ cross-referencing apparatus, which I discuss below
-(\textbf{crossref}).  This provision is unnecessary if you are using
-\textsf{Biber}.
+(\textbf{crossref}).  This provision is now unnecessary, assuming you
+are using \textsf{biber}.

\mybigspace An \mymarginpar{\textbf{booktitleaddon}} annex to the
\textsf{booktitle}.  It will be printed in the main text font, without
@@ -2187,10 +2731,12 @@
customize the punctuation that appears before the

-\mybigspace This \mymarginpar{\textbf{chapter}} field holds the
+\mybigspace This \colmarginpar{\textbf{chapter}} field holds the
chapter number, mainly useful only in an \textsf{inbook} or an
\textsf{incollection} entry where you wish to cite a specific chapter
-of a book (ashbrook:brain).
+of a book (ashbrook:brain).  It now also holds the track number of
+individual pieces of \textsf{music}, whether on a traditional format
+or on a streaming service (holiday:fool, rihanna:umbrella).

\mybigspace I \mymarginpar{\textbf{commentator}} have implemented this
\textsf{biblatex} field pretty much as that package's standard styles
@@ -2197,28 +2743,27 @@
do, even though the \emph{Manual} doesn't actually mention it.  It may
be useful for some purposes.  Cf.\ \textsf{annotator}.

-\enlargethispage{\baselineskip}
-
-\paragraph*{\protect\mymarginpar{\textbf{crossref}}}
+\paragraph*{\protect\colmarginpar{\textbf{crossref}}}
\label{sec:crossref}

This field is the standard \textsc{Bib}\TeX\ cross-referencing
mechanism, and \textsf{biblatex} has adopted it while also introducing
-a modified one of its own (\textsf{xref}).  If you are using
+a modified one of its own (\textsf{xref}).  If you have used
\textsc{Bib}\TeX\ (or \textsf{bibtex8)} the \textsf{crossref} field
-works exactly the same as it always has, while \textsf{xref} attempts
-to remedy some of the deficiencies of the usual mechanism by ensuring
+works much the same as it always has, while \textsf{xref} attempts to
+remedy some of the deficiencies of the usual mechanism by ensuring
that child entries will inherit no data at all from their parents.
-Section~2.4.1.1 of \textsf{biblatex.pdf} contains useful notes on the
-intricacies of managing cross-referenced entries with these
-traditional backends, and for the most part these backends are still
-usable, if inconvenient.  The functionality, discussed below, for
-abbreviating references in \textsf{book}, \textsf{bookinbook},
-\textsf{collection}, and \textsf{proceedings} entries, and for using
-the \textsf{mv*} entry types to do so, will prove extremely difficult
-to replicate with the older backends, so if you plan on lots of
-cross-referencing in \textsf{biblatex-chicago-notes} then I strongly
-recommend you use \textsf{Biber}.
+Section~2.4.1 of \textsf{biblatex.pdf} contains useful notes on
+managing cross-referenced entries, and section~3.15 explains some of
+the limitations of the traditional backends, which offer only a small
+subset of \textsf{Biber's} features.  The functionality, discussed
+below, for abbreviating references in \textsf{book},
+\textsf{bookinbook}, \textsf{collection}, and \textsf{proceedings}
+entries, and for using the \textsf{mv*} entry types to do so, will
+prove extremely difficult to replicate with the older backends, so if
+you plan on lots of cross-referencing in
+\textsf{biblatex-chicago-notes} then I strongly recommend you use
+\textsf{Biber}.

\mylittlespace (One reason for this is that when \textsf{Biber} is the
backend, \textsf{biblatex} defines a series of inheritance rules for
@@ -2237,7 +2782,7 @@
any of the new \textbf{mv*} entry types.)

\mylittlespace Turning now to the provision of abbreviated references
-in \textsf{biblatex-chicago-notes}, the \emph{Manual} (14.113)
+in \textsf{biblatex-chicago-notes}, the \emph{Manual} (14.108)
specifies that if you cite several contributions to the same
collection, all (including the collection itself) may be listed
separately in the bibliography, which the package does automatically,
@@ -2257,24 +2802,30 @@
functionality.

\mylittlespace First, I added five entry types --- \textbf{book},
-\textbf{bookinbook}, \textbf{collection}, \textbf{inbook}, and
-\textbf{proceedings} --- to the list of those which use shortened
-cross references, and I added two options --- \texttt{longcrossref}
-and \texttt{booklongxref}, on which more below --- which you can use
-in the preamble or in the \textsf{options} field of an entry to enable
-or disable the automatic provision of abbreviated references.  (The
-\textsf{crossref} or \textsf{xref} field are still necessary for this
-provision, but they are no longer sufficient on their own.)  The
-\textsf{inbook} type works exactly like \textsf{incollection} or
-\textsf{inproceedings}; in previous releases, you could use
-\textsf{inbook} instead of \textsf{incollection} to avoid the
-automatic abbreviation, the two types being otherwise identical.  Now
-that you can use an option to turn off abbreviated references even in
-the presence of a \textsf{crossref} or \textsf{xref} field, I have
-thought it sensible to include this entry type alongside the others.
-(Cf.\ ellet:galena, keating:dearborn, lippincott:chicago, and
-prairie:state to see this mechanism in action in both notes and
-bibliography.)
+\textbf{bookinbook}, \textbf{collection}, \textbf{inbook},
+\textbf{proceedings}, and \mycolor{\textbf{review}} --- to the list of
+those which use shortened cross references, and I added two options
+--- \texttt{longcrossref} and \texttt{booklongxref}, on which more
+below --- which you can use in the preamble or in the \textsf{options}
+field of an entry to enable or disable the automatic provision of
+abbreviated references.  (The \textsf{crossref} or \textsf{xref} field
+are still necessary for this provision, but they are no longer
+sufficient on their own.)  The \textsf{inbook} and
+\mycolor{\textsf{review}} types work exactly like
+\textsf{incollection} or \textsf{inproceedings}; in previous releases,
+you could use \textsf{inbook} instead of \textsf{incollection} to
+avoid the automatic abbreviation, the two types being otherwise
+identical.  Now that you can use an option to turn off abbreviated
+references even in the presence of a \textsf{crossref} or
+\textsf{xref} field, I have thought it sensible to include this entry
+type alongside the others.  (Cf.\ ellet:galena, keating:dearborn,
+lippincott:chicago, and prairie:state to see this mechanism in action
+in both notes and bibliography.)  In the \mycolor{\textsf{review}}
+type the mechanism is aimed primarily at blog comments, assuming you
+don't want to use the more convenient \mycolor{\texttt{commenton}}
+\textsf{relatedtype}, which absolves you even of the need to provide a
+\textsf{title} field for such entries.  See the documentation of the
+\textsf{review} type above for the details.

\mylittlespace The inclusion of \textbf{book}, \textbf{bookinbook},
\textbf{collection}, and \textbf{proceedings} entries fulfills a
@@ -2288,7 +2839,7 @@
below).  In \textsf{notes-test.bib} you can get a feel for how this
works by looking at bernhard:boris, bernhard:ritter,
bernhard:themacher, harley:ancient:cart, harley:carto\-graphy, and
-har\-ley:hoc.
+harley:hoc.

\mylittlespace Before discussing the new package options, I should say
a little about some subtleties involved in this mechanism.  First, and
@@ -2300,19 +2851,17 @@
\textsf{collection} entries.  Second, where and when to print
\textsf{volume} information in these references is extremely complex,
and I confess that I designed the tests primarily with \textsf{Biber}
-in mind.  If you can't get it to work using \textsc{Bib}\TeX, or if
-you find something that looks wrong to you, please let me know.
-Third, Andrew Goldstone long ago identified some other difficulties in
-the package's treatment of abbreviated citations, both in notes and
-bibliography, difficulties exacerbated now by the extension of the
-mechanism to book-like entries.  If you refer separately to chapters
-in a single-author \textsf{book}, then the shortened part of the
-reference, to the whole book, won't repeat the author's name before
-the title of the whole.  If, however, you refer separately to parts of
-a \textsf{collection} or \textsf{proceedings}, even when the
-\textsf{editor} of the \textsf{collection} is the same as the
-\textsf{author} of an essay in the collection, you will see the name
-repeated before the abbreviated part referencing the whole parent
+in mind.  Third, Andrew Goldstone long ago identified some other
+difficulties in the package's treatment of abbreviated citations, both
+in notes and bibliography, difficulties exacerbated now by the
+extension of the mechanism to book-like entries.  If you refer
+separately to chapters in a single-author \textsf{book}, then the
+shortened part of the reference, to the whole book, won't repeat the
+author's name before the title of the whole.  If, however, you refer
+separately to parts of a \textsf{collection} or \textsf{proceedings},
+even when the \textsf{editor} of the \textsf{collection} is the same
+as the \textsf{author} of an essay in the collection, you will see the
+name repeated before the abbreviated part referencing the whole parent
volume.

\mylittlespace Shortened references to book-like entries require, I
@@ -2341,10 +2890,8 @@
\texttt{omitxrefdate} and \texttt{xrefurl} in
section~\ref{sec:useropts}.

-%\enlargethispage{\baselineskip}
-
\mylittlespace Finally, a published collection of letters also
-requires different treatment (14.117).  If you cite more than one
+requires different treatment (14.111).  If you cite more than one
letter from the same collection, then the \emph{Manual} specifies that
only the collection itself should appear in the bibliography.  In
footnotes, you can use the \textsf{letter} entry type, documented
@@ -2353,40 +2900,21 @@
implemented the system of shortened references in \textsf{letter}
entries, even though the \emph{Manual} doesn't explicitly require it.
(See white:ross:memo, white:russ, and white:total, for examples of the
-\textsf{crossref} and \textsf{xref} field in action in this way, and
-please note that the second of these entries is entirely fictitious,
-provided merely for the sake of example.)  How then to keep the
-individual letters from appearing in the bibliography?  The simplest
-mechanism is probably just to use \enquote{\texttt{skipbib}} in the
+\textsf{crossref} field in action in this way, and please note that
+the second of these entries is entirely fictitious, provided merely
+for the sake of example.)  How then to keep the individual letters
+from appearing in the bibliography?  The simplest mechanism is
+probably just to use \enquote{\texttt{skipbib}} in the
\textsf{options} field.

-\mylittlespace If you look closely at the .bib entries for
-white:ross:memo and white:russ, you'll see that, despite the latter
-using \textsf{xref} instead of \textsf{crossref}, the first note
-referring to it inherits data from the parent (white:total).  In the
-abbreviated note and in abbreviated bibliography entries \emph{only},
-the driver is making a separate call to the parent's .bib entry,
-formatting the information there to fill out the bare data provided by
-the child.  For the first white:ross:memo note, which contains the
-full bibliographical information for the collection as a whole, I have
-used \textsf{crossref} because this unabbreviated note no longer makes
-a separate call to the parent's entry --- or, technically, it no
-longer makes a call that prints anything at all.  This is a change
-from earlier releases of \textsf{biblatex-chicago}, so if your
-documents came to rely on the side effects of this separate citation
-for providing data that haven't been inherited by the child, please be
-aware that it no longer works as before.  (You could see this by
-citing white:russ \emph{before} white:ross:memo.)  This change only
-affects the eight entry types that provide the abbreviated
-cross-references, a provision that is dependent on the settings of two
-preamble and entry options.
+\mylittlespace Returning, \mymarginpar{\texttt{longcrossref}} then, to
+the package options which control whether and where the abbreviated
+references may appear, they function, by default, asymmetrically.  The
+first, \texttt{longcrossref}, generally controls the settings for the
+entry types more-or-less authorized by the \emph{Manual}:
+\textsf{inbook}, \textsf{incollection}, \textsf{inproceedings},
+\textsf{letter}, and \mycolor{\textsf{review}}.

-\mylittlespace Those \mymarginpar{\texttt{longcrossref}} options
-function, by default, asymmetrically.  The first,
-\texttt{longcrossref}, generally controls the settings for the entry
-types more-or-less authorized by the \emph{Manual}: \textsf{inbook},
-\textsf{incollection}, \textsf{inproceedings}, and \textsf{letter}.
-
\begin{description}
\item[\qquad false:] This is the default.  If you use
\textsf{crossref} or \textsf{xref} fields in the four mentioned
@@ -2427,8 +2955,6 @@
preamble or in the \textsf{options} field of individual entries,
allowing you to change the settings on an entry-by-entry basis.

-\enlargethispage{\baselineskip}
-
\mylittlespace Please further note that in earlier releases of
\textsf{biblatex-chicago} I recommended against using
\textsf{shorthand}, \textsf{reprinttitle} and/or \textsf{userf} fields
@@ -2449,29 +2975,95 @@
\textsf{crossref} functionality in a single entry is now possible.  If
you come across any problems or inaccuracies, please report them.)

-\mybigspace This \mymarginpar{\textbf{date}} field may be used to
-specify an item's complete date of publication, in \textsc{iso}8601
-format, i.e., \texttt{yyyy-mm-dd}.  It may also be used to specify a
-date range, according to the instructions in \xA7~2.3.8 of
-\textsf{biblatex.pdf}.  Please be aware, however, that \textsf{Biber}
-is somewhat more exacting when parsing the \textsf{date} field than
-\textsc{Bib}\TeX, so a field looking like \texttt{1968/75} will simply
-be ignored --- you need \texttt{1968/1975} instead.  If you want to
-present a more compressed year range, or more generally if only part
-of a date is required, then the \textsf{month} and \textsf{year}
-fields may be more convenient.  The latter may be particularly useful
-in some entries because it can hold more than just numerical data, in
-contrast to \textsf{date} itself.  Cf.\ the \textsf{misc} entry type
-in section~\ref{sec:entrytypes} above for how to use this field to
-\textsf{origdate} and \textsf{urldate}.
+\mybigspace With\colmarginpar{\textbf{date}} this release I have
+implemented all of the applicable parts of \textsf{biblatex's}
+elegant, and long standing, support for the
+\mycolor{\textsc{iso}8601-2 Extended Format specification}, which
+means the package now provides greatly enhanced possibilities for
+presenting uncertain and unspecified dates and date ranges, along with
+date eras, seasons, and time stamps.  I have also implemented the
+\emph{Manual's} (9.64) guidelines for compressing year ranges, as well
+as providing a few more extras to help with some of the other tricky
+corners of the \emph{Manual's} instructions.  A combination of
+\textsf{biblatex} and \textsf{biblatex-chicago} package options allows
+you to define when, how, and where any of these extended
+specifications will appear in your documents.  I have attempted to
+provide as compliant a set of defaults as possible in
+\textsf{biblatex-chicago.sty}, but you can alter any of them according
+to your needs.  All are documented in section~\ref{sec:options},
+below, but table~\ref{ad:date:extras}, located in the author-date
+section, purports to serve as a convenient reference guide to how this
+all works.

-\mylittlespace I should also point out that you can, in most entry
-types, qualify a \textsf{date} with the \textsf{userd} field, assuming
-that the entry contains no \textsf{urldate}.  For \textsf{music} and
-\textsf{video} entries there are several other requirements --- please
-see the documentation of \textsf{userd}, below.
+\mylittlespace There are several more general remarks about the
+\textsf{date} field that may be helpful to users.  First, I highly
+recommend familiarizing yourself with the extended date
+specifications, as in many cases they will greatly simplify the
+creation of your .bib databases.  The new
+\mycolor{\texttt{compressyears}} option (\texttt{true} by default),
+for example, takes a year range in a date field and handles the
+somewhat tricky Chicago compression rules for you, while also giving
+you a simple means of turning it off that doesn't involve combing your
+.bib file for all the \textsf{year} fields that contain your
+hand-formatted ranges.  Clearly, situations may still arise when a
+specially-crafted \textsf{year} or \textsf{origyear} field may be
+necessary, but if you can use the enhanced specifications then I
+strongly advocate doing so.  Second, the fine-grained specification of
+a time stamp is really only necessary for news stories that are
+frequently updated \enquote{as they unfold} (14.191), for online
+sources that change rapidly enough for a time stamp to be necessary
+(14.207, 14.233; wikiped:bibtex), or for online posts, particularly
+comments, that may need a time stamp for disambiguation (14.208--10).
+If you wish to specify the time zone, the \emph{Manual} (10.41)
+prefers initialisms like \enquote{EST} or \enquote{PDT,} and these are
+most easily provided using the \textsf{timezone} field, where you can
+include your own parentheses if so desired (cp.\ 14.191).  For the
+\textsf{date} field itself, a time stamp will only appear in
+\textsf{article}, \textsf{review}, \textsf{suppperiodical}, and
+\textsf{online} entries, the first three only with a \texttt{magazine}
+\textsf{entrysubtype}.  All types can print such a stamp from the
+\textsf{urldate} (controllable using the
+new\colmarginpar{\texttt{urlstamp}} \mycolor{\texttt{urlstamp}}
+option), while only \textsf{review} and \textsf{suppperiodical}
+entries will print this data from an \textsf{eventdate}.  If you find
+a context in which a time stamp would be useful and which isn't
+included in this discussion, please let me know.

+\mylittlespace Third, an incomplete time specification will be ignored
+by \textsf{biber}, so include the seconds in it, as in
+table~\ref{ad:date:extras}, safe in the knowledge that they won't, by
+default, ever appear in your documents.  Should you want that level of
+discrimination, the \textsf{biblatex} option \texttt{seconds} set to
+\texttt{true} provides it.  Fourth, in the \textsf{misc} entry type
+the \textsf{date} field can help to distinguish between two classes of
+archival material, letters and \enquote{letter-like} sources using
+\textsf{origdate} while others (interviews, wills, contracts) use
+\textsf{date}.  (See \textsf{misc} in section~\ref{sec:entrytypes} for
+the details.)  Fifth, you can in most entry types qualify a
+\textsf{date} with the \textsf{userd} field, assuming that the entry
+contains no \textsf{urldate}.  For \textsf{music} and \textsf{video}
+entries, there are several other requirements --- please see the
+documentation of \textsf{userd}, below.
+
+\mylittlespace Sixth, and finally, please note that the
+\textsf{nameaddon} field, which see, is no longer the place for time
+stamps, as it was in the 16th-edition styles.  Any such data there
+should be moved into the corresponding date field (either the
+\textsf{date} or the \textsf{eventdate}, typically).  On all these
+questions generally please cf.\ also \textsf{origdate},
+\textsf{timezone}, and \textsf{year}, below; the \texttt{alldates},
+\texttt{alltimes}, \mycolor{\texttt{alwaysrange}},
+\mycolor{\texttt{centuryrange}}, \mycolor{\texttt{compressyears}},
+\texttt{datecirca}, \texttt{dateera}, \texttt{dateeraauto},
+\mycolor{\texttt{nodatebrackets}}, \mycolor{\texttt{nodates}},
+\mycolor{\texttt{noyearbrackets}}, \texttt{timezones},
+\mycolor{\texttt{urlstamp}}, and \texttt{urltime} options in
+sections~\ref{sec:presetopts}, \ref{sec:chicpreset}, and
+\ref{sec:useropts}; and section~4.5.10 in \textsf{biblatex.pdf}
+
+\enlargethispage{\baselineskip}
+
\mylittlespace (Users of the Chicago author-date style who wish to
minimize the labor needed to convert a .bib database for the notes \&\
bibliography style should be aware that the latter style includes
@@ -2483,18 +3075,16 @@
in question demonstrably interferes with the functioning of the notes
\&\ bibliography style.)

-%\enlargethispage{\baselineskip}
-
\mybigspace This \mymarginpar{\textbf{day}} field, as of
\textsf{biblatex} 0.9, is obsolete, and will be ignored if you use it

\mybigspace Standard \mymarginpar{\textbf{doi}} \textsf{biblatex}
-field, providing the Digital Object Identifier of the work.  The 16th
-edition of the \emph{Manual} specifies that, given their relative
-permanence compared to URLs, \enquote{authors should include DOIs
-  rather than URLs for sources that make them readily available}
-(14.6).  (14.184; friedman:learn\-ing).  Cf.\ \textsf{url}.
+field, providing the Digital Object Identifier of the work.  The
+\emph{Manual} specifies that, given their relative permanence compared
+to URLs, \enquote{authors should prefer a DOI- or Handle-based URL
+  whenever one is available} (14.8).  (14.175; friedman:learning).
+Cf.\ \textsf{url}.

\mybigspace Standard \mymarginpar{\textbf{edition}} \textsf{biblatex}
field.  If you enter a plain cardinal number, \textsf{biblatex} will
@@ -2509,13 +3099,6 @@
notes, but there is room for the user's discretion in specific
citations (emerson:nature).

-\mylittlespace In a previous release of
-\textsf{biblatex-chicago-notes}, I introduced the \textsf{userd} field
-to hold this non-numeric information, as \textsf{biblatex} only
-accepted an integer in the \textsf{edition} field, but this changed in
-version 0.8.  The \textsf{userd} field now has an entirely different
-function --- please see its documentation below.
-
\mybigspace As \mymarginpar{\textbf{editor}} far as possible, I have
implemented this field as \textsf{biblatex}'s standard styles do, but
the requirements specified by the \emph{Manual} present certain
@@ -2560,13 +3143,14 @@
releases of \textsf{biblatex} provide these fields as a means to
specify additional contributors to texts in a number of editorial
roles.  In the Chicago styles they seem most relevant for the
-audiovisual types, especially \textsf{music} and \textsf{video}, where
-they help to identify conductors, directors, producers, and
-performers.  To specify the role, use the fields \textsf{editoratype},
+audiovisual types, especially \textsf{music} and \textsf{video}, and
+now also the \mycolor{\textsf{performance}} type, in all of which they
+can help to identify conductors, directors, producers, and performers.
+To specify the role, use the fields \textsf{editoratype},
\textsf{editorbtype}, and \textsf{editorctype}, which see.  (Cf.\
-bernstein:shostakovich, handel:messiah.)
+bernstein:shostakovich, hamilton:miranda, handel:messiah.)

-\mybigspace Normally, \mymarginpar{\textbf{editortype}} with the
+\mybigspace Normally, \colmarginpar{\textbf{editortype}} with the
exception of the \textsf{article} and \textsf{review} types,
\textsf{biblatex-chicago-notes} will automatically find a name to put
at the head of an entry, starting with an \textsf{author}, and
@@ -2590,12 +3174,23 @@
field, and \textsf{biblatex} will print the correct string after the
name in both the bibliography and in the long note form.

-\enlargethispage{\baselineskip}
+\mylittlespace In \colmarginpar{New!} previous releases of
+\textsf{biblatex-chicago} you could only use defined \cmd{bibstrings}
+in this field, at least if you wanted anything printed.  N.~Andrew
+Walsh pointed out that the standard \textsf{biblatex} styles will just
+print the field as-is in this case, allowing them to handle a great
+many unforeseen editorial roles with comparative ease, so I've
+implemented this, too, making sure to capitalize the string if the
+context demands it.  The string you choose will differ depending on
+whether it will be printed after a name at the head of an entry or
+before a name later on in the entry, e.g., \enquote{cartographer} or
+\enquote{maps created by.}  A bit of trial and error should see you
+through.

-\mylittlespace There are a few details of which you need to be aware.
-Because \textsf{biblatex-chicago} has added the \textsf{namea} field,
-which gives you the ability to identify the editor specifically of a
-\textsf{title} as opposed to a \textsf{maintitle} or a
+\mylittlespace There are a few more details of which you need to be
+aware.  Because \textsf{biblatex-chicago} has added the \textsf{namea}
+field, which gives you the ability to identify the editor specifically
+of a \textsf{title} as opposed to a \textsf{maintitle} or a
\textsf{booktitle}, the name-finding algorithm checks first to see
whether a \textsf{namea} is defined.  If it is, that name will be used
at the head of the entry, if it isn't, or if you've set the option
@@ -2619,7 +3214,7 @@
the \textsf{editor} exactly matches a \textsf{translator} and/or a
\textsf{namec}, or alternatively if \textsf{namea} exactly matches a
\textsf{nameb} and/or a \textsf{namec}, then \textsf{biblatex} will
-print the appropriate strings.  The \emph{Manual} specifically (14.87)
+print the appropriate strings.  The \emph{Manual} specifically (14.32)
recommends not using these identifying strings in the short note form,
and \textsf{biblatex-chicago-notes} follows their recommendation.  If
you nevertheless need to provide such a string, you'll have to do it
@@ -2636,25 +3231,32 @@
\textsf{suppperiodical}.

\mybigspace These
-\mymarginpar{\textbf{editoratype\\editorbtype\\editorctype}} fields
+\colmarginpar{\textbf{editoratype\\editorbtype\\editorctype}} fields
identify the exact role of the person named in the corresponding
-\textsf{editor[a-c]} field.  Note that they are not part of the string
+\textsf{editor[a-c]} field, just as \textsf{editortype} (q.v.) does
+for the \textsf{editor}.  Note that they are not part of the string
concatenation mechanism.  I have implemented them just as the standard
-styles do, and they have now found a use particularly in
-\textsf{music} and \textsf{video} entries.  Cf.\
-bernstein:shostakovich, handel:messiah.
+styles do, that is, if the field isn't a pre-defined \cmd{bibstring}
+it will be printed as-is, contextually capitalized.  They have found a
+use particularly in \textsf{music}, \mycolor{\textsf{performance}},
+and \textsf{video} entries.  Cf.\ bernstein:shostakovich,
+hamilton:miranda, handel:messiah.

-\mybigspace Standard \mymarginpar{\textbf{eid}} \textsf{biblatex}
+\mybigspace Standard \colmarginpar{\textbf{eid}} \textsf{biblatex}
field, providing a string or number some journals use uniquely to
identify a particular article.  Only applicable to the
-\textsf{article} entry type.  Not typically required by the
-\emph{Manual}.
+\textsf{article} entry type, and only to those without a
+\texttt{magazine} \textsf{entrysubtype}.  The 17th edition of the
+\emph{Manual} now specifies where to print this (14.174), and I have
+moved it in accordance with its specifications.  It replaces the
+\textsf{pages} field in long notes and bibliography, and appears after
+any specific page cited in the \textsf{postnote} field of a long note.

-\paragraph*{\protect\mymarginpar{\textbf{entrysubtype}}}
+\paragraph*{\protect\colmarginpar{\textbf{entrysubtype}}}
\label{sec:entrysub}

Standard and very powerful \textsf{biblatex} field, left undefined by
-the standard styles.  In \textsf{biblatex-chicago-notes} it has four
+the standard styles.  In \textsf{biblatex-chicago-notes} it has eight
very specific uses, the first three of which I have designed in order
to maintain, as much as possible, backward compatibility with the
standard styles.  First, in \textsf{article}, \textsf{periodical}, and
@@ -2685,7 +3287,7 @@
the Renaissance and later, even if cited by the traditional divisions,
have short notes formatted normally, and therefore don't need an
-\textsf{entrysubtype} field.  (See \emph{Manual} 14.256--268;
+\textsf{entrysubtype} field.  (See \emph{Manual} 14.242--54;
aristotle:metaphy:gr, plato:republic:gr; euripides:orestes is an
example of a translation cited by page number in a modern edition.)

@@ -2695,18 +3297,39 @@
including the use of italics for the \textsf{title}.  Any string at
all in \textsf{entrysubtype} tells \textsf{biblatex-chicago-notes} to
treat the source as part of an unpublished archive.  A \textsf{misc}
-entry with \textsf{entrysubtype} defined is the least formatted of all
-those specified by the \emph{Manual} --- see
+entry with an \textsf{entrysubtype} defined is the least formatted of
+all those specified by the \emph{Manual} --- see
section~\ref{sec:entrytypes} above under \textbf{misc} for all the
details on how these citations work.

-\enlargethispage{\baselineskip}
-
-\mylittlespace Fourth, and finally, the field can be defined in the
+\mylittlespace Fourth, the field can be defined in the
\textsf{artwork} entry type in order to refer to a work from antiquity
whose title you do not wish to be italicized.  Please see the
-documentation of \textbf{artwork} above for the details.
+documentation of \textbf{artwork} above for the details.  Fifth, you
+can define it in a \mycolor{\textbf{standard}} entry, q.v., to change
+the appearance of both long and short notes.  Sixth, you can define it
+in an \textbf{audio}, \textbf{music}, or \textbf{video} entry if such
+an entry refers to an individual unit that isn't part of any larger
+collection, the entry therefore having only a \textsf{title} and not a
+\textsf{booktitle}, a \textsf{title} that \textsf{biblatex-chicago}
+would normally interpret as the title of a larger unit (and therefore
+italicize).  Seventh, and sticking with the \textbf{video} type,
+though enacting quite a different syntactic transformation, the 17th
+edition (14.265) now recommends that, when presenting episodes from a
+TV series, the name of the series (\textsf{booktitle}) comes before
+the episode name (\textsf{title}).  The exact string
+\mycolor{\texttt{tvepisode}} in the \textsf{entrysubtype} field
+achieves this reversal, which includes using the \textsf{booktitle} as
+a \textsf{sorttitle} in the bibliography and also as the
+\textsf{labeltitle} in short notes.

+\mylittlespace Eighth, and finally, you can use any
+\textsf{entrysubtype} whatever in \textsf{inreference} entries in
+order to treat them as inherently online works rather than standard
+published works.  See the documentation of \textbf{online} and
+\textbf{inreference} entries in section~\ref{sec:entrytypes}, above,
+and also 14.233 and wikiped:bibtex.
+
\mybigspace Kazuo
\mymarginpar{\textbf{eprint}\\\textbf{eprintclass}\\\textbf{eprinttype}}
@@ -2717,29 +3340,59 @@
abbreviated references to online content than conventional URLs,
though I can find no specific reference to them in the \emph{Manual}.

-\mybigspace This \mymarginpar{\textbf{eventdate}} is a standard
-\textsf{biblatex} field.  In the 15th edition it was barely used, but
-in order to comply with changes in the 16th edition of the
-\emph{Manual} it can now play a significant role in \textsf{music},
-\textsf{review}, and \textsf{video} entries.  In \textsf{music}
-entries, it identifies the recording or performance date of a
-particular song (rather than of a whole disc, for which you would use
-\textsf{origdate}), whereas in \textsf{video} entries it identifies
-either the original broadcast date of a particular episode of a TV
-series or the date of a filmed musical performance.  In both these
-cases \textsf{biblatex-chicago} will automatically prepend a bibstring
---- \texttt{recorded} and \texttt{aired}, respectively --- to the
-date, but you can change this string using the new \textsf{userd}
-field, something you'll definitely want to do for filmed musical
-performances (friends:leia, handel:messiah, holiday:fool).
+\enlargethispage{-\baselineskip}

-\mylittlespace The field's use in \textsf{review} entries is somewhat
-different.  There, it helps to identify a particular comment within an
-online thread.  There isn't a particular string associated with it,
-but you can further specify a comment by placing a time\-stamp in
-parentheses in the \textsf{nameaddon} field, in case the date alone
-isn't enough (ac:comment).
+\mybigspace This \colmarginpar{\textbf{eventdate}} is a standard
+\textsf{biblatex} field which has gradually accumulated functions in
+\textsf{biblatex-chicago}.  It can now play a role in
+\mycolor{\textsf{artwork}}, \mycolor{\textsf{audio}},
+\mycolor{\textsf{image}}, \textsf{music}, \textsf{review},
+\mycolor{\textsf{standard}}, \textsf{suppperiodical},
+\textsf{unpublished}, and \textsf{video} entries.  In \textsf{artwork}
+and \textsf{image} entries it identifies the publication date of, most
+frequently, a photograph, in association with the
+\textsf{howpublished} field which identifies the periodical or other
+medium in which it was published (mccurry:afghangirl).  In
+\textsf{standard} entries it will also usually be associated with a
+\textsf{howpublished} field, allowing you to specify a later renewal
+or reaffirmation of a standard (niso:bibref).  In \textsf{audio}
+entries, it specifies the release date of a single episode of a
+podcast (danforth:podcast).  In \textsf{music} entries, it identifies
+the recording or performance date of a particular song (rather than of
+a whole disc, for which you would use \textsf{origdate}), whereas in
+\textsf{video} entries it identifies either the original broadcast
+date of a particular episode of a TV series or the date of a filmed
+musical performance.  In both these cases \textsf{biblatex-chicago}
+will automatically prepend a bibstring --- \texttt{recorded} and
+\texttt{aired}, respectively --- to the date, but you can change this
+string using the \textsf{userd} field, something you'll definitely
+want to do for filmed musical performances (friends:leia,
+handel:messiah, holiday:fool).

+\mylittlespace In \textsf{unpublished} entries it identifies the date
+of an event at which an unpublished work was presented, though in
+truth the \textsf{date} will do as well here (nass:address).  The
+field's use in \textsf{review} entries, finally, includes a possible
+time stamp.  In this context, an \textsf{eventdate} helps to identify
+a particular comment on, or reply to another comment on, a blog post.
+Given that many such posts by a single \textsf{author} could appear on
+the same day, you can distinguish them by putting a time specification
+in the \textsf{eventdate} field itself (ac:comment).  Please see the
+\textbf{review} type, above, for the details of how to cite these
+materials, possibly with the help of the new
+\textsf{date} field docs, in particular table~\ref{ad:date:extras}
+(located in the author-date section), for\colmarginpar{New!} details on
+how the \mycolor{\textsc{iso}8601-2 Extended Format specifications}
+offered by \textsf{biblatex}, including time stamps and much else
+besides, have been implemented in \textsf{biblatex-chicago}.
+
+\mybigspace This \colmarginpar{\textbf{eventtimezone}} field can, if
+necessary, specify the time zone associated with a time stamp given as
+part of an \textsf{eventdate}.  The \emph{Manual} prefers initialisms
+like \enquote{EST} for this purpose, and you can provide parentheses
+around it at your discretion (cp.\ 10.41 and 14.191).
+
\mybigspace As \mymarginpar{\textbf{foreword}} with the
\textsf{afterword} field above, \textsf{foreword} will in general
function as it does in standard \textsf{biblatex}.  Like
@@ -2755,14 +3408,28 @@
subject, but \textsf{biblatex-chicago-notes} prints it (them), in
parentheses, just after the author(s).

-%\enlargethispage{\baselineskip}
+\mybigspace Standard \colmarginpar{\textbf{howpublished}}
+\textsf{biblatex} field which, like the \textsf{eventdate} field, is
+gradually accumulating functions in \textsf{biblatex-chicago}.  In the
+\textsf{booklet} type it retains something of its traditional usage,
+replacing the \textsf{publisher}, and has a similar (somewhat
+paradoxical) place in \textsf{unpublished} entries.  In the
+\textsf{misc} and \mycolor{\textsf{performance}} types it works almost
+as a second \textsf{note} field, bringing in extra information about a
+work in close association with the \textsf{type} and \textsf{version}
+fields, while in \mycolor{\textsf{dataset}} entries its information
+will be associated with both those fields and also with the
+\textsf{number} field.  17th-edition \textsf{music} entries require a
+field to provide the medium of downloaded music and/or the name of the
+streaming service, so \textsf{howpublished} works there as an online
+double of \textsf{type} and of \textsf{publisher}.  Finally, in
+\textsf{artwork}, \textsf{image}, and \mycolor{\textsf{standard}}
+entries it serves to qualify or modify an \textsf{eventdate}, almost
+as a \textsf{userd} field modifies a \textsf{date} or
+\textsf{urldate}.  Please see the docs of those entry types for more
+information, and also bedford:photo, clark:mesopot,
+mccurry:afghangirl, niso:bibref, rihanna:umbrella.

-\mybigspace Standard \mymarginpar{\textbf{howpublished}}
-\textsf{biblatex} field, mainly applicable in the \textsf{booklet}
-entry type, where it replaces the \textsf{publisher}.  I have also
-retained it in the \textsf{misc} and \textsf{unpublished} entry types,
-for historical reasons.
-
\mybigspace Standard \mymarginpar{\textbf{institution}}
\textsf{biblatex} field.  In the \textsf{thesis} entry type, it will
usually identify the university for which the thesis was written,
@@ -2769,6 +3436,8 @@
while in a \textsf{report} entry it may identify any sort of
institution issuing the report.

+\enlargethispage{\baselineskip}
+
\mybigspace As \mymarginpar{\textbf{introduction}} with the
\textsf{afterword} and \textsf{foreword} fields above,
\textsf{introduction} will in general function as it does in standard
@@ -2795,7 +3464,11 @@
field, designed for \textsf{article}, \textsf{periodical}, or
\textsf{review} entries identified by something like \enquote{Spring}
or \enquote{Summer} rather than by the usual \textsf{month} or
-\textsf{number} fields (brown:bremer).
+\textsf{number} fields (brown:bremer).  \textsf{Biblatex's} enhanced
+date handling allows you to specify a season in the \textsf{date}
+field, with the \enquote{months} 21--24 used for Spring, Summer,
+Autumn, and Winter, respectively.  Cf.\ table~\ref{ad:date:extras},
+below.

\mybigspace The \mymarginpar{\textbf{issuesubtitle}} subtitle for an
\textsf{issuetitle} --- see next entry.
@@ -2811,8 +3484,6 @@
issue}, with the initial letter lower-cased to enable automatic
contextual capitalization.

-%%\enlargethispage{\baselineskip}
-
\mybigspace The \mymarginpar{\textbf{journalsubtitle}} subtitle for a
\textsf{journaltitle} --- see next entry.

@@ -2834,30 +3505,12 @@
documentation below.

\mybigspace This \mymarginpar{\textbf{keywords}} field is
-\textsf{biblatex}'s extremely powerful and flexible technique for
-filtering bibliography entries, allowing you to subdivide a
-bibliography according to just about any criteria you care to invent.
-See \textsf{biblatex.pdf} (3.11.4) for thorough documentation.  In
-\textsf{biblatex-chicago}, the field can provide a convenient means to
-exclude certain entries from making their way into a bibliography.  We
-have already seen (\textbf{letter}, above) how the \emph{Manual}
-(14.117) requires, in the case of published collections of letters,
-that when more than one letter from the same collected is cited, the
-bibliography should contain only a reference to the collection as a
-whole (white:ross:memo, white:russ, white:total).  Similarly, when
-citing both an original text and its translation (see \textbf{userf},
-section~\ref{sec:related} below), the \emph{Manual} (14.109) suggests
-including the original at the end of the translation's bibliography
-entry, a procedure which requires that the original not also be
-printed as a separate bibliography entry (furet:passing:eng,
-furet:passing:fr, aristotle:metaphy:trans, aristotle:metaphy:gr).
-Finally, citations of well-known reference works (like the
-\emph{Encyclopaedia Britannica}, for example), need only be presented
-in notes, and not in the bibliography (14.247--248; ency:britannica,
-wikiped:bibtex; see \textsf{inreference}, above).  A \textsf{keywords}
-field can be a convenient way to exclude all such entries from
-appearing in a bibliography, though of course including
-\texttt{skipbib} in the \textsf{options} field works, too.
+\textsf{biblatex}'s powerful and flexible technique for filtering
+bibliography entries, allowing you to subdivide a bibliography
+according to just about any criteria you care to invent, or indeed to
+prevent entries in notes from appearing in the bibliography, as the
+\emph{Manual} sometimes recommends.  See \textsf{biblatex.pdf} (3.7)
+for thorough documentation.

\mybigspace A \mymarginpar{\textbf{language}} standard
\textsf{biblatex} field, designed to allow you to specify the
@@ -2869,8 +3522,8 @@
when the title of a work is given in translation, even though no
translation of the work has been published, something that might
happen when a title is in a language deemed to be unparseable by a
-pirumova, rozner:liberation).  In such a case, you should provide the
+rozner:liberation).  In such a case, you should provide the
language(s) involved using this field, connecting multiple languages
using the keyword \texttt{and}.  (I have retained \textsf{biblatex's}
\cmd{bibstring} mechanism here, which means that you can use the
@@ -2904,7 +3557,7 @@
\textsf{Biblatex-chicago-notes} will only print such a field in a
\textsf{book} or an \textsf{inreference} entry, and you should look at
the documentation of these entry types for further details.  (See
-\emph{Manual} 14.247--248; ency:britannica, grove:sibelius,
+\emph{Manual} 14.232--33; ency:britannica, grove:sibelius,
times:guide, wikiped:bibtex.)

\mybigspace This \mymarginpar{\textbf{location}} is
@@ -2911,15 +3564,13 @@
\textsf{biblatex}'s version of the usual \textsc{Bib}\TeX\ field
\textsf{address}, though the latter is accepted as an alias if that
simplifies the modification of older .bib files.  According to the
-\emph{Manual} (14.135), a citation usually need only provide the first
+\emph{Manual} (14.129), a citation usually need only provide the first
city listed on any title page, though a list of cities separated by
the keyword \enquote{\texttt{and}} will be formatted appropriately.
If the place of publication is unknown, you can use
-\cmd{autocap\{n\}.p.}\ instead (14.138).  For all cities, you should
-use the common English version of the name, if such exists (14.137).
+\verb+\autocap{n}.p.+\ instead (14.132).  For all cities, you should
+use the common English version of the name, if such exists (14.131).

-%%\enlargethispage{\baselineskip}
-
\mylittlespace Three more details need explanation here.  In
\textsf{article}, \textsf{periodical}, and \textsf{review} entries,
there is usually no need for a \textsf{location} field, but
@@ -2926,35 +3577,48 @@
\enquote{if a journal might be confused with another with a similar
title, or if it might not be known to the users of a bibliography,}
then this field can present the place or institution where it is
-published (14.191, 14.203; lakeforester:pushcarts, kimluu:diethyl, and
-garrett).  For blogs cited using \textsf{article} entries, this is a
-good place to identify the nature of the source --- i.e., the word
-\enquote{blog} --- letting the style automatically provide the
-parentheses (14.246; ellis:blog).  Less predictably, it is here that
-\emph{Manual} indicates that a particular book is a reprint edition
-(14.119), so in such a case you can use the \textsf{biblatex-chicago}
-macro \cmd{reprint}, followed by a comma, a space, and the location
-(aristotle:metaphy:gr, schweitzer:bach).  (You can also now, somewhat
-more simply, just put the string \texttt{reprint} into the
-\textsf{pubstate} field to achieve the same result.  See the
-\textsf{pubstate} documentation in section~\ref{sec:related}.)  The
-\textsf{origdate} field may be used to give the original date of
-publication, and of course more complicated situations should usually
-be amenable to inclusion in the \textsf{note} field (emerson:nature).
+published (14.182, 14.191, 14.193--94; lakeforester:pushcarts,
+kimluu:diethyl, and garrett).  For blogs cited using \textsf{article}
+entries, this is a good place to identify the nature of the source ---
+i.e., the word \enquote{blog} --- letting the style automatically
+provide the parentheses (14.208; ellis:blog).  Less predictably, it is
+in the vicinity of the \textsf{location} that the \emph{Manual}
+indicates that a particular book is a reprint edition (14.114), so in
+such a case you can use the \textsf{biblatex-chicago} macro
+\cmd{reprint}, followed by a comma, a space, and the location.
+Somewhat more cleanly and simply, and more in keeping with standard
+\textsf{biblatex} usage, you can just put the string \texttt{reprint}
+into the \textsf{pubstate} field to achieve the same result.  See the
+\textsf{pubstate} documentation below (aristotle:metaphy:gr,
+schweitzer:bach).  The \textsf{origdate} field may be used to give the
+original date of publication, and of course more complicated
+situations should usually be amenable to inclusion in the
+\textsf{note} field (emerson:nature).

\mybigspace The \mymarginpar{\textbf{mainsubtitle}} subtitle for a
\textsf{maintitle} --- see next entry.

-\mybigspace The \mymarginpar{\textbf{maintitle}} main title for a
+\mybigspace The \colmarginpar{\textbf{maintitle}} main title for a
multi-volume work, e.g., \enquote{Opera} or \enquote{Collected Works.}
(See donne:\hfill var, euripides:orestes, harley:cartography,
lach:asia, pelikan:christian, and plato:repub\-lic:gr.)  When using a
\textsf{crossref} field and \textsf{Biber}, the \textsf{title} of
\textbf{mv*} entry types always becomes a \textsf{maintitle} in the
-child entry.
+\mycolor{\texttt{maintitle}} \textsf{relatedtype} in the
+\textbf{mvbook} docs in section~\ref{sec:entrytypes}, above, and in
+section~\ref{sec:related}, below.

-%%\enlargethispage{\baselineskip}
+\mylittlespace Because \colmarginpar{New!} the 17th edition of the
+\emph{Manual} recommends that you present not only the names of blogs
+but also the names of their parent (usually periodical) publications,
+I have added this field to \textsf{article}, \textsf{periodical}, and
+\textsf{review} entries for just this purpose.  See the documentation of
+those entry types in section~\ref{sec:entrytypes}, above, and also
+table~\ref{tab:online:types} (14.208; amlen:hoot).

+\enlargethispage{\baselineskip}
+
\mybigspace An \mymarginpar{\textbf{maintitleaddon}} annex to the
\textsf{maintitle}, for which see previous entry.  Such an annex would
be printed in the main text font.  If your data begins with a word
@@ -2993,11 +3657,11 @@
role just as you can with \textsf{editortype}, which see.  Cf.\ also
\textsf{nameb}, \textsf{namec}, \textsf{translator}, and the macros
\cmd{partedit},\,\cmd{parttrans},\,\cmd{parteditandtrans},
-\cmd{partcomp},\,\cmd{part\-editandcomp}, \cmd{parttransandcomp}, and
+\cmd{partcomp},\,\cmd{parteditandcomp}, \cmd{parttransandcomp}, and
\cmd{partedittransandcomp}, for which see
section~\ref{sec:formatcommands}.

-\mybigspace This \mymarginpar{\textbf{nameaddon}} field is provided
+\mybigspace This \colmarginpar{\textbf{nameaddon}} field is provided
by \textsf{biblatex}, though not used by the standard styles.  In
\textsf{biblatex-chicago}, it allows you, in most entry types, to
specify that an author's name is a pseudo\-nym, or to provide either
@@ -3004,20 +3668,27 @@
the real name or the pseudonym itself, if the other is being provided
in the \textsf{author} field.  The abbreviation
\enquote{\texttt{pseud}.}\ (always lowercase in English) is specified,
-either on its own or after the pseudo\-nym (centinel:letters,
+either on its own or after the pseudonym (centinel:letters,
creasey:ashe:blast, creasey:morton:hide, creasey:york:death, and
-le\-carre:quest); \cmd{bibstring\{pseudonym\}} does the work for you.
+lecarre:quest); \verb+\bibstring{pseudonym}+ does the work for you.
See under \textbf{author} above for the full details.

-\mylittlespace In \textsf{review} entries, I have removed the
-automatic provision of square brackets from the field, allowing it to
-be used in at least two ways.  First, if you provide your own square
-brackets, then it can have its standard function, as above.  Second,
-and new to the 16th edition of the \emph{Manual}, you can further
-specify comments to blogs and other online content using a timestamp
-(in parentheses) that supplements the \textsf{eventdate}, particularly
-when the latter is too coarse a specification to identify a comment
-unambiguously.  Cf.\ ac:comment.
+\mylittlespace In \textsf{online, review,} and \textsf{suppperiodical}
+entries, as well as in \textsf{misc} entries with an
+\textsf{entrysubtype}, I have removed the automatic provision of
+square brackets from the field, allowing it to be used in at least two
+ways.  First, if you provide your own square brackets, then it can
+have its standard function, as above.  Second you can, within
+parentheses, provide a screen name for online social media, or merely
+archive.  (The 16th edition of the \emph{Manual} recommended
+specifying comments to blogs and other online content using a time
+stamp in parentheses after the \textsf{author}, but the 17th edition
+\colmarginpar{New!} handles time stamps both differently and more
+widely, so in this case you would now put time data into the
+\textsf{date} or \textsf{eventdate} field, particularly when the date
+itself is too coarse a specification to identify a comment
+unambiguously.  Cf.\ ac:comment, obrien:recycle.)

\mylittlespace In the \textsf{customc} entry type, finally, which is
used to create alphabetized cross-references to other bibliography
@@ -3057,7 +3728,7 @@
\cmd{partcomp},\,\, \cmd{parteditandcomp},\,\, \cmd{parttransandcomp}, and
\cmd{partedittransand-\break comp} in section~\ref{sec:formatcommands}.

-\mybigspace The \mymarginpar{\textbf{namec}} \emph{Manual} (14.87)
+\mybigspace The \mymarginpar{\textbf{namec}} \emph{Manual} (14.103)
specifies that works without an author may be listed under an editor,
translator, or compiler, assuming that one is available, and it also
specifies the strings to be used with the name(s) of compiler(s).  All
@@ -3085,8 +3756,6 @@
may, in certain circumstances, use that field, or the
\textsf{nameatype} field, to identify a compiler.)

-%\enlargethispage{\baselineskip}
-
\mylittlespace It might conceivably be necessary at some point to
identify the compiler(s) of a \textsf{title} separate from the
compiler(s) of a \textsf{booktitle} or \textsf{maintitle}, but for the
@@ -3123,13 +3792,17 @@
lowercase, and \textsf{biblatex-chicago-notes} will automatically do

-\mybigspace This \mymarginpar{\textbf{number}} is a standard
-\textsf{biblatex} field, containing the number of a
+\mybigspace This \colmarginpar{\textbf{number}} is a standard
+\textsf{biblatex} field, steadily accumulating uses in
+\textsf{biblatex-chicago}.  It may contain the number of a
\textsf{journaltitle} in an \textsf{article} or \textsf{review} entry,
the number of a \textsf{title} in a \textsf{periodical} entry, the
-volume/number of a book in a \textsf{series}, or the (generally
-numerical) specifier of the \textsf{type} in a \textsf{report} entry.
-Generally, in an \textsf{article}, \textsf{periodical}, or
+volume/number of a book (or musical recording) in a \textsf{series},
+the (generally numerical) specifier of the \textsf{type} in a
+\textsf{report} entry, the archive location (or database accession
+number) of a \mycolor{\textsf{dataset}} entry, and the number of a
+national or international standard in a \mycolor{\textsf{standard}}
+entry.  Generally, in an \textsf{article}, \textsf{periodical}, or
\textsf{review} entry, this will be a plain cardinal number, but in
such entries \textsf{biblatex-chicago} now does the right thing if you
have a list or range of numbers (unsigned:ranke).  In any
@@ -3138,14 +3811,14 @@
example, while the \textsf{series} field in such an entry will contain
the name of the series, rather than a number.  This field is also the
place for the patent number in a \textsf{patent} entry.  Cf.\
-\textsf{issue} and \textsf{series}.  (See \emph{Manual} 14.128--132
-and boxer:china, palmatary:pottery, wauchope:ceramics; 14.180--181 and
-gibbard, hlatky:hrt, mcmillen:antebellum, rozner:liberation,
-warr:el\-lison.)
+\textsf{issue} and \textsf{series}.  (Cf.\ 14.123--25 and boxer:china,
+palmatary:pottery, wauchope:ceramics; 14.171 and beattie:crime,
+mcmillen:antebellum, rozner:liberation, and warr:ellison; 14.257 and
+genbank:db; 14.259 and niso:bibref; 14.263 and holiday:fool.)

\mylittlespace \textbf{NB}: This may be an opportune place to point
-out that the \emph{Manual} (14.154) prefers arabic to roman numerals
+out that the \emph{Manual} (14.147) prefers arabic to roman numerals
in most circumstances (chapters, volumes, series numbers, etc.), even
when such numbers might be roman in the work cited.  The obvious
exception is page numbers, in which roman numerals indicate that the
@@ -3168,28 +3841,33 @@
\textsf{inproceedings} entry, and I have retained this as a
possibility, though the \emph{Manual} is silent on the matter.

-\mybigspace This \mymarginpar{\textbf{origdate}} \textsf{biblatex}
+\mybigspace This \colmarginpar{\textbf{origdate}} \textsf{biblatex}
field allows you to provide more than one full date specification for
those references which need it.  As with the analogous \textsf{date}
field, you provide the date (or range of dates) in \textsc{iso}8601
-format, i.e., \texttt{yyyy-mm-dd}.  In most entry types, you would use
-\textsf{origdate} to provide the date of first publication of a work,
-most usually needed only in the case of reprint editions, but also
-recommended by the \emph{Manual} for electronic editions of older
-works (14.119, 14.166, 14.169; aristotle:metaphy:gr, emerson:nature,
-james:ambassadors, schweitzer:bach).  In the \textsf{letter} and
-\textsf{misc} (with \textsf{entrysubtype}) entry types, the
-\textsf{origdate} identifies when a letter (or similar) was written.
-In such \textsf{misc} entries, some \enquote{non-letter-like}
-materials (like interviews) need the \textsf{date} field for this
-purpose, while in \textsf{letter} entries the \textsf{date} applies to
-the publication of the whole collection.  If such a published
-collection were itself a reprint, improvisation in the
-\textsf{location} field might be able to rescue the situation.  (See
-jackson:paulina:letter, white:ross:memo, white:russ, and white:total
-for how \textsf{letter} entries usually work; creel:house shows the
-field in action in a \textsf{misc} entry, while spock:interview uses
-\textsf{date}.)
+format, i.e., \texttt{yyyy-mm-dd}.  (You can also provide a time stamp
+in the field, after an uppercase \enquote{\texttt{T}}, but I foresee
+this being very rarely needed in the notes \&\ bibliography style.
+implementation of \textsf{biblatex's} enhanced date specifications.)
+In most entry types, you would use \textsf{origdate} to provide the
+date of first publication of a work, most usually needed only in the
+case of reprint editions, but also recommended by the \emph{Manual}
+for electronic editions of older works (14.114, 14.162;
+schweitzer:bach).  In the \textsf{letter} and \textsf{misc} (with
+\textsf{entrysubtype}) entry types, the \textsf{origdate} identifies
+when a letter (or similar) was written.  In such \textsf{misc}
+entries, you can choose between an \textsf{origdate} and a
+\textsf{date} field for this purpose, depending on how you want the
+date formatted (day-month-year or month-day-year, respectively), while
+in \textsf{letter} entries the \textsf{date} applies to the
+publication of the whole collection.  If such a published collection
+were itself a reprint, improvisation in the \textsf{location} field
+might be able to rescue the situation.  (See jackson:paulina:letter,
+white:ross:memo, white:russ, and white:total for how \textsf{letter}
+entries usually work; creel:house shows the field in action in a
+\textsf{misc} entry, while spock:interview uses \textsf{date}.)

\mylittlespace In \textsf{music} entries, you can use the
\textsf{origdate} in two separate but related ways.  First, it can
@@ -3197,8 +3875,8 @@
track on that disc, which would go in \textsf{eventdate}.  (Compare
holiday:fool with nytrumpet:art.)  The style will automatically
prepend the bibstring \texttt{recorded} to the date, but you can
-change it with the new \textsf{userd} field.  Be aware, however, that
-if an entry also has an \textsf{eventdate}, then \textsf{userd} will
+change it with the \textsf{userd} field.  Be aware, however, that if
+an entry also has an \textsf{eventdate}, then \textsf{userd} will
apply to that, instead, and you'll be forced to accept the default
string.  Second, the \textsf{origdate} can provide the original
release date of an album.  For this to happen, you need to put the
@@ -3206,13 +3884,18 @@
standard mechanism across many other entry types for identifying a
reprinted work.  (See floyd:atom.)

-\mylittlespace Because the \textsf{origdate} field only accepts
-numbers, some improvisation may be needed if you wish to include
-\enquote{n.d.}\ (\cmd{bibstring\{nodate\}}) in an entry.  In
-\textsf{letter} and \textsf{misc}, this information can be placed in
-\textsf{titleaddon}, but in other entry types you may need to use the
-\textsf{location} field.  (The \textsf{origyear} field usually works,
-too.)
+\mylittlespace A couple of further notes are in order.  First,
+\textsf{artwork} and \textsf{image} entries (which see) have their own
+scheme.  Here, the style uses the earlier of two dates as the creation
+date of the work while the later is the printing date of, e.g., a
+particular exemplar of a photograph or of an etching.  In such an
+entry, the \textsf{origdate} may well be a creation date.  Second,
+because the \textsf{origdate} field only accepts numbers, some
+improvisation may be needed if you wish to include \enquote{n.d.}\
+(\verb+\bibstring{nodate}+) in an entry.  In \textsf{letter} and
+\textsf{misc}, this information can be placed in \textsf{titleaddon},
+but in other entry types you may need to use the \textsf{location}
+field.  (The \textsf{origyear} field usually works, too.)

\mybigspace See
\vspace{-14.2pt}
@@ -3221,14 +3904,20 @@
section~\ref{sec:related}, below.
\vspace{18pt}

+\mybigspace This \colmarginpar{\textbf{origtimezone}} field can, if
+necessary, specify the time zone associated with a time stamp given as
+part of an \textsf{origdate}.  The \emph{Manual} prefers initialisms
+like \enquote{EST} for this purpose, and you can provide parentheses
+around it at your discretion (cp.\ 10.41 and 14.191).
+
\mybigspace This \mymarginpar{\textbf{pages}} is the standard
\textsf{biblatex} field for providing page references.  In many
\textsf{article} and \textsf{review} entries you'll find this contains
something other than a page number, e.g. a section name or edition
-specification (14.203, 14.209; kozinn:review, nyt:obittrevor,
-nyt:trevor\-obit).  Of course, the same may be true of almost any sort
+specification (14.191; kozinn:review, nyt:obittrevor,
+nyt:trevorobit).  Of course, the same may be true of almost any sort
of entry, though perhaps with less frequency.  Curious readers may
-wish to look at brown:bremer (14.189) for an example of a
+wish to look at brown:bremer (14.180) for an example of a
\textsf{pages} field used to facilitate reference to a two-part
\emph{Manual}'s preferences regarding the formatting of numerals;
@@ -3244,7 +3933,7 @@
regarding the automatic compression of page ranges, e.g., 101-{-}109
in the .bib file or in the \textsf{postnote} field would become 101--9
in the document.  \textsf{Biblatex} has long had the facilities for
-providing this, and though the \emph{Manual's} rules (9.60) are fairly
+providing this, and though the \emph{Manual's} rules (9.61) are fairly
complicated, Audrey Boruvka fortunately provided in that discussion
code that implements the specifications.  As some users may well be
accustomed to compressing page ranges themselves in their .bib files,
@@ -3251,7 +3940,10 @@
and in their \textsf{postnote} fields, I have made the activation of
this code a package option, so setting \texttt{compresspages=true}
-the Chicago-recommended page ranges.
+the Chicago-recommended page ranges.  \textbf{NB}: the code now
+resides in \textsf{biblatex-chicago.sty}, so if you don't load that
+package then you'll need to copy the code into your preamble for the
+option to have the desired effect.

\mybigspace This, \mymarginpar{\textbf{pagination}} a standard
\textsf{biblatex} field, allows you automatically to prefix the
@@ -3266,7 +3958,7 @@
field, which identifies physical parts of a single logical volume in
\textsf{book}-like entries, not in periodicals.  It has the same
purpose in \textsf{biblatex-chicago-notes}, but because the
-\emph{Manual} (14.126) calls such a thing a \enquote{book} and not a
+\emph{Manual} (14.121) calls such a thing a \enquote{book} and not a
\enquote{part,} the string printed in notes and bibliography will, at
least in English, be \enquote{\texttt{bk.}\hspace{-2pt}}\ instead of
the plain dot between volume number and part number
@@ -3284,42 +3976,65 @@
case would be \textsf{number} [palmatary:pottery]).  Cf.\
\textsf{volume}.

-\mybigspace Standard \mymarginpar{\textbf{publisher}}
+\mybigspace Standard \colmarginpar{\textbf{publisher}}
\textsf{biblatex} field.  Remember that \enquote{\texttt{and}} is a
keyword for connecting multiple publishers, so if a publisher's name
contains \enquote{and,} then you should either use the ampersand (\&)
or enclose the whole name in additional braces.  (See \emph{Manual}
-14.139--148; aristotle:metaphy:gr, cohen:schiff, creasey:ashe:blast,
+14.133--41; aristotle:metaphy:gr, cohen:schiff, creasey:ashe:blast,
dunn:revolutions.)

-\mylittlespace There are, as one might expect, a couple of further
-subtleties involved here.  Two publishers will be separated by a
-forward slash in both notes and bibliography, and you no longer, in
-the 16th edition, need to provide hand formatting if a company issues
-\enquote{certain books through a special publishing division or under
-  a special imprint,} as these, too, should be separated by a forward
-slash.  If a book has two co-publishers, \enquote{usually in different
-  countries,} (14.147) then the simplest thing to do is to choose one,
-probably the nearest one geographically.  If you feel it necessary to
-include both, then levistrauss:savage demonstrates one way of doing
-so, using a combination of the \textsf{publisher} and
-\textsf{location} fields.  Finally, if the publisher is unknown, then
-the \emph{Manual} recommends (14.143) simply using the place (if
-known) and the date.  If for some reason you need to indicate the
-absence of a publisher, the abbreviation given by the \emph{Manual} is
-\texttt{n.p.}, though this can also stand for \enquote{no place.}
-Some style guides apparently suggest using \texttt{s.n.}\,(=
-\emph{sine nomine}) to specify the lack of a publisher, but the
-\emph{Manual} doesn't mention this.
+\enlargethispage{\baselineskip}

-\mybigspace In addition to the functions involving reprinted titles,
-on which see \colmarginpar{\textbf{pubstate}}
-section~\ref{sec:related} below, you can now also use the
-\textsf{pubstate} field to indicate that a work is
-\enquote{forthcoming.}  Just put the exact string \texttt{forthcoming}
-into the field and the style will print \cmd{bibstring\{forth\-coming\}}
-as the \textsf{year} (author:forthcoming, contrib:contrib).
+\mylittlespace There are, as one might expect, a few further
+subtleties involved here.  If you give two publishers in the field
+they will both be printed, separated by a forward slash in both notes
+and bibliography (14.90; sereny:cries).  The 17th edition generally is
+rather keener than the 16th on using just one, particularly so in the
+case when the parent company of an imprint is also listed on a title
+page, in which case only the imprint need be included in your
+apparatus (14.138).  If an academic publisher issues \enquote{certain
+  books through a special publishing division or under a special
+  imprint or as part of a publishing consortium (or joint imprint),}
+this arrangement may be specified in the \textsf{publisher} field
+(14.139; cohen:schiff).  If a book has two co-publishers \enquote{in
+  different countries} (14.140), then the simplest thing to do is to
+choose one, probably the nearest one geographically.  If you feel it
+necessary to include both, then levistrauss:savage demonstrates one
+way of doing so, using a combination of the \textsf{publisher} and
+\textsf{location} fields.  If the work is self-published, you can
+specify this in the \textsf{pubstate} field (see below), and any
+commercial self-publishing platform would go in \textsf{publisher}
+(14.137).  Books published before 1900 can, at your discretion,
+include only the place (if known) and the date (14.128).  If for some
+reason you need to indicate the absence of a publisher, the
+abbreviation given by the \emph{Manual} is \texttt{n.p.}, though this
+can also stand for \enquote{no place.}  The \emph{Manual} also
+mentions {s.n.}\,(= \emph{sine nomine}) to specify the lack of a
+publisher (10.42).

+\mybigspace In \colmarginpar{\textbf{pubstate}} response to new
+specifications in the 17th edition of the \emph{Manual} (esp.\
+14.137), I have tried to generalize the functioning of the
+\textsf{pubstate} field in all entry types.  The \texttt{reprint}
+string still has a special status there, being ignored in
+\textsf{video} entries and provoking a syntactic change in the
+presentation of dates in \textsf{music} entries, while in other types
+allowing the presentation of reprinted titles.  Other strings are
+divided into two types: those which \textsf{biblatex-chicago} will
+print as the \textsf{year}, which currently means \emph{only} those
+for which \textsf{biblatex} contains bibstrings indicating works soon
+to be published, i.e., \texttt{forthcoming}, \texttt{inpreparation},
+\texttt{inpress}, and \texttt{submitted}; and those, i.e., everything
+else, which will be printed before, and in close association with,
+other information about the publisher of a work.  The four in the
+first category will always be localized, as will \texttt{reprint} and
+\mycolor{\texttt{selfpublished}} (and anything else that
+\textsf{biblatex} finds to be a \cmd{bibstring}) from the second
+category.  All other strings will be printed as-is, capitalized if
+needed, just before the publisher (author:forthcoming,
+contrib:contrib, schweitzer:bach).
+
\mybigspace I \mymarginpar{\textbf{redactor}} have implemented this
field just as \textsf{biblatex}'s standard styles do, even though the
\emph{Manual} doesn't actually mention it.  It may be useful for some
@@ -3331,10 +4046,12 @@
\mybigspace A \mymarginpar{\textbf{series}} standard \textsf{biblatex}
field, usually just a number in an \textsf{article},
\textsf{periodical}, or \textsf{review} entry, almost always the name
-of a publication series in \textsf{book}-like entries.  If you need to
-attach further information to the \textsf{series} name in a
-\textsf{book}-like entry, then the \textsf{number} field is the place
-for it, whether it be a volume, a number, or even something like
+of a publication series in \textsf{book}-like entries, and providing
+similar identifying information associated with a \textsf{number} in
+\textsf{music} and \mycolor{\textsf{standard}} entries.  If you need
+to attach further information to the \textsf{series} name in a
+\textsf{book}-like entry, then the \textsf{number} field is again the
+place for it, whether it be a volume, a number, or even something like
\enquote{2nd ser.} or \enquote{\cmd{bibstring\{oldseries\}}.}  Of
course, you can also use \cmd{bibstring\{oldseries\}} or
\cmd{bibstring\{newseries\}} in an \textsf{article} entry, but there
@@ -3342,7 +4059,7 @@
\textsf{series} field in \textsf{article}, \textsf{periodical}, and
\textsf{review} entries is one of the places where \textsf{biblatex}
allows you just to use the plain bibstring \texttt{oldseries}, for
-example, rather than making you type \cmd{bibstring\{oldseries\}}.
+example, rather than making you type \verb+\bibstring{oldseries}+.
The \textsf{type} field in \textsf{manual}, \textsf{patent},
\textsf{report}, and \textsf{thesis} entries also has this
auto-detection mechanism in place; see the discussion of
@@ -3349,14 +4066,12 @@
\cmd{bibstring} below for details.)  In whatever entry type, these
bibstrings produce the required abbreviation, which thankfully is the
same in both notes and bibliography.  (For books and similar entries,
-see \emph{Manual} 14.128--132; boxer:china, browning:aurora,
-palmatary:pottery, plato:republic:gr, wauchope:ceramics; for
-periodicals, see 14.195; garaud:gatine, sewall:letter.)  Cf.\
+see 14.123--26; boxer:china, browning:aurora, palmatary:pottery,
+plato:republic:gr, wauchope:ceramics; for periodicals, see 14.184;
+garaud:gatine, sewall:letter; also niso:bibref, nytrumpet:art) Cf.\
preferences regarding the formatting of numerals.

-\enlargethispage{-\baselineskip}
-
\paragraph*{\protect\mymarginpar{\textbf{shortauthor}}}
\label{sec:shortauthor}

@@ -3374,15 +4089,15 @@
\textsf{biblatex-chicago-notes} will use the \textsf{journaltitle} as
the author, you can use the \textsf{shortjournal} field instead, but
you'll need to set up the \texttt{journalabbrev} option to make sure
-it's actually printed.  (See below.)  In author-less \textsf{manual}
-entries, where the \textsf{organization} will be so used, the style
-automatically uses any \textsf{shortauthor} in the short note form,
-though you may still need to help the alphabetization routines by
-providing a \textsf{sortkey} field in such cases (dyna:browser,
+it's actually printed.  (See \textsf{shortjournal}, below.)  In
+author-less \textsf{manual} entries, where the \textsf{organization}
+will be so used, the style automatically uses any \textsf{shortauthor}
+in the short note form, though it will sort by the
+\textsf{organization} in the bibliography (dyna:browser,
gourmet:052006, lakeforester:pushcarts, nyt:trevorobit).

\mylittlespace As mentioned under \textsf{editortype}, the
-\emph{Manual} (14.87) recommends against providing the identifying
+\emph{Manual} (14.32) recommends against providing the identifying
string (e.g., ed.\ or trans.)\ in the short note form, and
\textsf{biblatex-chicago-notes} follows their recommendation.  If you
need to provide these strings in such a citation, then you'll have to
@@ -3417,7 +4132,7 @@
reader that the work will hereafter be cited by this abbreviation.  As
in \textsf{biblatex}, the \cmd{printshorthands} command, now for
\textsf{Biber} users at least an alias for
-\cmd{printbib\-list\{shorthand\}}, will produce a formatted list of
+\verb+\printbiblist{shorthand}+, will produce a formatted list of
abbreviations for reference purposes, a list which the \emph{Manual}
suggests should be placed either in the front matter (when using
footnotes) or before the endnotes, in case these are used.
@@ -3440,7 +4155,7 @@
\texttt{shorthandfull}, which prints entries in the list of shorthands
which contain full bibliographical information, effectively allowing
you to eschew the bibliography in favor of a fortified shorthand list.
-(See 13.65, 14.54--55, and also \textsf{biblatex.pdf} for more
+(See 13.67, 14.59--60, and also \textsf{biblatex.pdf} for more
information.)

\mylittlespace Alexandre Roberts suggested a further refinement to
@@ -3473,8 +4188,6 @@
have with this functionality to the email address at the head of this
documentation.

-%\enlargethispage{-\baselineskip}
-
\mybigspace When \mymarginpar{\textbf{shorthandintro}} you include a
\textsf{shorthand} in an entry, it will ordinarily appear the first
time you cite the work, at the end of a long note, surrounded by
@@ -3496,7 +4209,7 @@
itself.

\mybigspace A \mymarginpar{\textbf{shortjournal}} special
-\textsf{biblatex} field, used to provide both an abbreviated form of a
+\textsf{biblatex} field, used both to provide an abbreviated form of a
\textsf{journaltitle} in notes and/or bibliography and to facilitate
the creation of a list of journal abbreviations rather in the manner
of a \textsf{shorthand} list.  As requested by user BenVB, you can now
@@ -3520,7 +4233,7 @@
in notes and bibliography, \texttt{notes} only in notes, and
\texttt{bib} only in the bibliography.  Should you wish to present a
list of these abbreviations with their expansions, then you need to
-use the \cmd{printbiblist\{shortjour\-nal\}} command, perhaps with a
+use the \verb+\printbiblist{shortjournal}+ command, perhaps with a
\texttt{title} option to differentiate the list from any
\textsf{shorthand} list.  As with \textsf{shorthand} lists, I have
provided two \texttt{bibenvironments} for printing this list in foot-
@@ -3531,10 +4244,49 @@
the (oversized) default, and perhaps provide your own title within the
\cmd{footnote} command.  Finally, if you don't like the default
formatting of the abbreviations in the list (bold italic), you can
--- you can see its default definition at the top of
\textsf{chicago-notes.bbx}.

+\mybigspace A \colmarginpar{\textbf{shortseries}} special
+\textsf{biblatex} field, used both to provide an abbreviated form of a
+(book) \textsf{series} in notes and/or bibliography and to facilitate
+the creation of a list of such abbreviations rather in the manner of a
+\textsf{shorthand} list.  As with the \textsf{shortjournal} field, its
+inclusion in \textsf{biblatex-chicago} was requested by user BenVB,
+and it is now available in entry types which have book-like series
+titles rather than journal-like numbers in the \textsf{series} field,
+to wit: \textsf{audio, book, bookinbook, collection, inbook,
+  incollection, inproceedings, inreference, letter, manual, music,
+  mvbook, mvcollection, mvproceedings, mvreference, reference, report,
+  standard, suppbook,} and \textsf{video}.  There are several steps to
+take in order to use the field.  First, you'll need to provide both
+\textsf{shortseries} and \textsf{series} fields in the entry, then
+you'll need to set the \mycolor{\texttt{seriesabbrev}} option either
+specific entry types, or in the \textsf{options} field of individual
+.bib entries.  By default, this option is not set, so your
+\mycolor{\textsf{shortseries}} fields will be silently ignored.  There
+are three other settings:\ \texttt{true} prints the shortened fields
+both in notes and bibliography, \texttt{notes} only in notes, and
+\texttt{bib} only in the bibliography.  Should you wish to present a
+list of these abbreviations with their expansions, then you need to
+use the \verb+\printbiblist{shortseries}+ command, perhaps with a
+\texttt{title} option to differentiate the list from any
+\textsf{shorthand} list.  As with \textsf{shorthand} lists, I have
+provided two \texttt{bibenvironments} for printing this list in foot-
+or endnotes (\mycolor{\texttt{shsernotes}} and
+\mycolor{\texttt{shserendnotes}}, respectively), to be used with the
+\texttt{env} option to \cmd{printbiblist}.  Again as with
+\textsf{shorthands}, you'll probably want to use the option
+\texttt{heading=none} when using these environments, just to turn off
+the (oversized) default, and perhaps provide your own title within the
+\cmd{footnote} command.  Finally, if you don't like the default
+formatting of the abbreviations in the list (plain roman), you can
+roll your own using \verb+\DeclareFieldFormat{shortserieswidth}+ ---
+you can see its default definition at the top of
+\textsf{chicago-notes.bbx}.
+
\mybigspace A \mymarginpar{\textbf{shorttitle}} standard
\textsf{biblatex} field, primarily used to provide an abbreviated
title for short notes.  (It is also the way to hook
@@ -3542,41 +4294,34 @@
on which see the previous entry.)  In \textsf{biblatex-chicago-notes},
you need to take particular care with \textsf{letter} entries, where,
as explained above, the \emph{Manual} requires a special format
-(\enquote{\texttt{to Recipient}}).  (See 14.117;
+(\enquote{\texttt{to Recipient}}).  (See 14.111;
jackson:paulina:letter, white:ross:memo, white:russ.)  Some
\textsf{misc} entries (with an \textsf{entrysubtype}) also need
special attention.  (See creel:house, where the full \textsf{title} is
used as the \textsf{shortauthor} + \textsf{shorttitle} by using
-\cmd{headlesscite} commands.  Placing \cmd{isdot} into the
-\textsf{shortauthor} field no longer works in \textsf{biblatex} 1.6,
-so be sure to check your .bib files when you upgrade.)  Remember,
-also, that the generic titles in \textsf{review} and \textsf{misc}
-entries may not want capitalization in all contexts, so, as with the
-\textsf{title} field, if you begin a \textsf{shorttitle} with a
-lowercase letter the style will do the right thing (barcott:review,
-bundy:macneil, Clemens:letter, kozinn:review, ratliff:review,
-unsigned:ranke).
+\cmd{headlesscite} commands.)  Remember, also, that the generic titles
+in \textsf{review} and \textsf{misc} entries may not want
+capitalization in all contexts, so, as with the \textsf{title} field,
+if you begin a \textsf{shorttitle} with a lowercase letter the style
+will do the right thing (barcott:review, bundy:macneil,
+Clemens:letter, kozinn:review, ratliff:review, unsigned:ranke).

-%%\enlargethispage{\baselineskip}
-
-\mybigspace A \mymarginpar{\textbf{sortkey}} standard
-\textsf{biblatex} field, designed to allow you to specify how you want
-an entry alphabetized in a bibliography.  In general, if an entry
-doesn't turn up where you expect or want it, this field should provide
-the solution.  Entries with a corporate author can now omit the
-definite or indefinite article, which should help (14.85;
-cotton:manufacture, nytrumpet:art).  If you use \textsf{Biber} as your
-backend, \textsf{biblatex-chicago} also now includes the three
-supplemental name fields (\textsf{name[a-c]}) in the sorting
-algorithm, so once again you should find that this field is needed
-less than before.  Still, many entries without a name field of any
-sort, particularly those with a definite or indefinite article
-beginning the \textsf{title}, may require assistance (chaucer:alt,
-dyna:browser, gourmet:052006, greek:filmstrip, grove:sibelius,
-lakeforester:pushcarts, nyt:trevorobit, silver:ga\-wain,
-un\-signed:ran\-ke, vir\-gin\-ia:plan\-tation).  \textsf{Biblatex}
-also provides \textbf{sortname}, \textbf{sorttitle}, and
-\textbf{sortyear} for more fine-grained control.  Please consult
+\mybigspace Standard \mymarginpar{\textbf{sortkey} \\\textbf{sortname}
+  \\\textbf{sorttitle} \\\textbf{sortyear}} \textsf{biblatex} fields,
+designed to allow you to specify how you want an entry alphabetized in
+a bibliography.  The \textsf{sortkey} field trumps all other sorting
+information, while the others offer more fine-grained control.  In
+general, if an entry doesn't turn up where you expect or want it,
+these fields should provide the solution.  Entries with a corporate
+author can now omit the definite or indefinite article, which should
+help (14.70, 14.84; cotton:manufacture, nytrumpet:art).
+\textsf{Biblatex-chicago} also includes the three supplemental name
+fields (\textsf{name[a-c]}) in the sorting algorithm, so once again
+you should find that a \textsf{sortkey} is needed less than before.
+Still, some entries without a name field of any sort, particularly
+those with a definite or indefinite article beginning the
+\textsf{title}, may require assistance (greek:filmstrip,
\textsf{biblatex.pdf} and the remarks on \cmd{DeclareSortingTemplate}
in section~\ref{sec:formatopts}, below.

@@ -3583,6 +4328,12 @@
\mybigspace The \mymarginpar{\textbf{subtitle}} subtitle for a
\textsf{title} --- see next entry.

+\mybigspace This \colmarginpar{\textbf{timezone}} field can, if
+necessary, specify the time zone associated with a time stamp given as
+part of an \textsf{date}.  The \emph{Manual} prefers initialisms like
+\enquote{EST} for this purpose, and you can provide parentheses around
+it at your discretion (cp.\ 10.41 and 14.191).
+
\mybigspace In \mymarginpar{\textbf{title}} the vast majority of
cases, this field works just as it always has in \textsc{Bib}\TeX, and
just as it does in \textsf{biblatex}.  Nearly every entry will have
@@ -3592,7 +4343,7 @@
difficulties flows from the \emph{Manual}'s rules for formatting
\textsf{titles}, rules which also hold for \textsf{booktitles} and
\textsf{maintitles}.  The whole point of using a
-\textsc{Bib}\TeX-based system is for it to do the formatting for you,
+\textsf{biblatex}-based system is for it to do the formatting for you,
and in most cases \textsf{biblatex-chicago-notes} does just that,
surrounding titles with quotation marks, italicizing them, or
occasionally just leaving them alone.  When, however, a title is
@@ -3609,20 +4360,23 @@
\textsf{journaltitle} in all entry types; \textsf{title} of
\textsf{artwork}, \textsf{book}, \textsf{bookinbook},
\textsf{booklet}, \textsf{collection}, \textsf{image},
-  \textsf{inbook}, \textsf{manual}, \textsf{misc} (with no
-  \textsf{entrysubtype}), \textsf{periodical}, \textsf{proceedings},
-  \textsf{report}, \textsf{suppbook}, and \textsf{suppcollection}
-  entry types.
+  \textsf{manual}, \textsf{misc} (with no \textsf{entrysubtype}),
+  \mycolor{\textsf{performance}}, \textsf{periodical},
+  \textsf{proceedings}, \textsf{report}, \mycolor{\textsf{standard}},
+  \textsf{suppbook}, and \textsf{suppcollection} entry types.
\item[\qquad Quotation Marks:] \textsf{title} of \textsf{article},
-  \textsf{incollection}, \textsf{inproceedings}, \textsf{online},
-  \textsf{periodical}, \textsf{thesis}, and \textsf{unpublished} entry
-  types, \textsf{issuetitle} in \textsf{article}, \textsf{periodical},
-  and \textsf{review} entry types.
+  \textsf{inbook}, \textsf{incollection}, \textsf{inproceedings},
+  \textsf{online}, \textsf{periodical}, \textsf{thesis}, and
+  \textsf{unpublished} entry types, \textsf{issuetitle} in
+  \textsf{article}, \textsf{periodical}, and \textsf{review} entry
+  types.
+\item[\qquad Sentence cased:] \textsf{title} in \textsf{patent}
+  entries.
\textsf{title} of \textsf{customc}, \textsf{letter}, \textsf{misc}
-  (with an \textsf{entrysubtype}), \textsf{patent}, \textsf{review},
-  and \textsf{suppperiodical} entry types.
+  (with an \textsf{entrysubtype}), \textsf{review}, and
+  \textsf{suppperiodical} entry types.
\item[\qquad Italics or Quotation Marks:] All of the audiovisual entry
types --- \textsf{audio}, \textsf{music}, and \textsf{video} ---
have to serve as analogues both to \textsf{book} and to
@@ -3629,7 +4383,7 @@
\textsf{inbook}.  Therefore, if there is both a \textsf{title} and a
\textsf{booktitle}, then the \textsf{title} will be in quotation
marks.  If there is no \textsf{booktitle}, then the \textsf{title}
-  will be italicized.
+  will be italicized, unless you provide an \textsf{entrysubtype}.
\end{description}

Now, the rules for which entry type to use for which sort of work tend
@@ -3636,7 +4390,7 @@
to be fairly straightforward, but in cases of doubt you can consult
section \ref{sec:entrytypes} above, the examples in
\textsf{notes-test.bib}, or go to the \emph{Manual} itself,
-8.154--195.  Assuming, then, that you want to present a title within a
+8.156--201.  Assuming, then, that you want to present a title within a
title, and you know what sort of formatting each of the two would, on
its own, require, then the following rules apply:

@@ -3645,7 +4399,7 @@
quotation marks and italicized, so in such cases all you need to do
is provide the quotation marks using \cmd{mkbibquote}, which will
take care of any following punctuation that needs to be brought
-  within the closing quotation mark(s) (14.102; donne:var,
+  within the closing quotation mark(s) (14.94; donne:var,
mchugh:wake).
\item Inside a quoted title, you should present another title as it
would appear if it were on its own, so in such cases you'll need to
@@ -3653,8 +4407,8 @@
another quoted title would take single quotes --- the
\cmd{mkbibquote} command does this for you automatically, and also,
I repeat, takes care of any following punctuation that needs to be
-  brought within the closing quotation mark(s).  (See 14.177; garrett,
-  loften:hamlet, murphy:silent, white:calli\-machus.)
+  brought within the closing quotation mark(s).  (See 14.94--95;
+  garrett, loften:hamlet, murphy:silent, white:cal\-limachus.)
\item Inside a plain title (most likely in a \textsf{review} entry or
a \textsf{titleaddon} field), you should present another title as it
would appear on its own, once again formatting it yourself using
@@ -3666,11 +4420,13 @@
italicized in text should also be italicized in a quoted or plain-text
title, but should be in roman (\enquote{reverse italics}) in an
italicized title.  A quotation used as a (whole) title (with or
-without a subtitle) retains its quotation marks in an italicized title
-\enquote{only if it appears that way in the source,} but always
-retains them when the surrounding title is quoted or plain (14.104,
-14.177; lewis).  A word or phrase in quotation marks, but that isn't a
-quotation, retains those marks in all title types (kimluu:diethyl).
+without a subtitle) retains, according to the 16th edition, its
+quotation marks in an italicized title if it appears that way in the
+source, but I can't find similar instructions in the 17th.  Such a
+quotation always retains its quotation marks when the surrounding
+title is quoted or plain (14.94; lewis).  A word or phrase in
+quotation marks, but that isn't a quotation, retains those marks in
+all title types (kimluu:diethyl).

\mylittlespace Finally, please note that in all \textsf{review} (and
\textsf{suppperiodical}) entries, and in \textsf{misc} entries with an
@@ -3681,6 +4437,8 @@
your .bib database.  See\,\textbf{\textbackslash autocap} in
section~\ref{sec:formatcommands} below for more details.

+\enlargethispage{-\baselineskip}
+
\textsf{biblatex} intends this field for use with additions to titles
that may need to be formatted differently from the titles themselves,
@@ -3687,7 +4445,7 @@
and \textsf{biblatex-chicago-notes} uses it in just this way, with the
additional wrinkle that it can, if needed, replace the \textsf{title}
entirely, and this in, effectively, any entry type, providing a fairly
-powerful, if somewhat complicated, tool for getting \textsc{Bib}\TeX\
+powerful, if somewhat complicated, tool for getting \textsf{biblatex}
to do what you want (cf.\ centinel:letters, powell:email).  This field
will always be unformatted, that is, neither italicized nor placed
within quotation marks, so any formatting you may need within it
@@ -3709,8 +4467,6 @@
coolidge:speech shows both entry options for controlling the
punctuation.)

-%\enlargethispage{-\baselineskip}
-
\mybigspace As \mymarginpar{\textbf{translator}} far as possible, I
have implemented this field as \textsf{biblatex}'s standard styles do,
but the requirements specified by the \emph{Manual} present certain
@@ -3758,18 +4514,22 @@
\textsf{author}, \textsf{editor}, \textsf{namea}, \textsf{nameb}, and
\textsf{namec}.

-\mybigspace This \mymarginpar{\textbf{type}} is a standard
+\mybigspace This \colmarginpar{\textbf{type}} is a standard
\textsf{biblatex} field, and in its normal usage serves to identify
the type of a \textsf{manual}, \textsf{patent}, \textsf{report}, or
\textsf{thesis} entry.  \textsf{Biblatex} 0.7 introduced the ability,
in some circumstances, to use a bibstring without inserting it in a
-\cmd{bibstring} command, and in these entry types the \textsf{type}
-field works this way, allowing you simply to input, e.g.,
-\texttt{patentus} rather than \cmd{bibstring\{patentus\}}, though both
-will work.  (See petroff:im\-purity; herwign:office, murphy:silent, and
-ross:thesis all demonstrate how the \textsf{type} field may sometimes
-be automatically set in such entries by using one of the standard
-entry-type aliases).
+\cmd{bibstring} command, and in some entry types (\textsf{audio,
+  manual, music, patent, report, suppbook, suppcollection, thesis,}
+and \textsf{video}) the \textsf{type} field works this way, allowing
+you simply to input, e.g., \texttt{patentus} rather than
+\verb+\bibstring{patentus}+, though both will work.  (See
+petroff:impurity; herwign:office, murphy:silent, and ross:thesis all
+demonstrate how the \textsf{type} field may sometimes be automatically
+set in such entries by using one of the standard entry-type aliases).
+In other entry types (\textsf{artwork, image, book, online, article,
+  review,} and \textsf{suppperiodical}) \textsf{biblatex-chicago} will
+merely capitalize the contents according to context.

\mylittlespace In the \textsf{suppbook} entry type, and in its alias
\textsf{suppcollection}, you can use the \textsf{type} field to
@@ -3776,57 +4536,95 @@
specify what sort of supplemental material you are citing, e.g.,
\enquote{\texttt{preface to}} or \enquote{\texttt{post\-script to}.}
Cf.\ \textsf{suppbook} above for the details.  (See \emph{Manual}
-14.116; polakow:af\-terw, prose:intro).
+14.110; polakow:afterw, prose:intro).

-\mylittlespace You can also use the \textsf{type} field in
+\mylittlespace You can use the \textsf{type} field in
\textsf{artwork}, \textsf{audio}, \textsf{image}, \textsf{music}, and
\textsf{video} entries to identify the medium of the work, e.g.,
\texttt{oil on canvas}, \texttt{albumen print}, \texttt{compact disc}
-or \texttt{MPEG}.  If the first word in this field would normally only
-be capitalized at the beginning of a sentence, then leave it in
-lowercase in your .bib file and \textsf{biblatex} will automatically
-do the right thing in citations.  Cf.\ \textsf{artwork},
-\textsf{audio}, \textsf{image}, \textsf{music}, and \textsf{video},
-above, for all the details.  (See auden:reading, bedford:photo,
+or \texttt{MPEG}.  In \textsf{book} entries it will normally hold
+system information about multimedia app content (14.268), while in
+\textsf{online, article,} and \textsf{review} entries it will hold the
+medium of online multimedia (14.267).  Cf.\ under these entry types in
+section~\ref{sec:entrytypes}, above, for more details.  (See
+nytrumpet:art.)

-\enlargethispage{-\baselineskip}
-
\mybigspace A standard \mymarginpar{\textbf{url}} \textsf{biblatex}
field, it holds the url of an online publication, though you can
-provide one for all entry types.  The 16th edition of the
-\textsf{Manual} expresses a strong preference for DOIs over URLs if
-the former is available --- cf.\ \textsf{doi} above, and also
-\textsf{urldate} just below.  The required \LaTeX\ package
-\textsf{url} will ensure that your documents format such references
-properly, in the text and in the reference apparatus.  It may be worth
-noting that child entries no longer inherit \textsf{url} fields from
-their parents --- the information seems entry-specific enough to
-warrant a little bit of extra typing if you need to present the same
-locator in several entries.
+provide one for all entry types.  The \emph{Manual} expresses a strong
+preference for DOIs over URLs if the former is available --- cf.\
+\textsf{doi} above, and also \textsf{urldate} just below.  The
+required \LaTeX\ package \textsf{url} will ensure that your documents
+format such references properly, in the text and in the reference
+apparatus.  It may be worth noting that child entries generally won't
+inherit \textsf{url} fields from their parents --- the information
+seems entry-specific enough to warrant a little bit of extra typing if
+you need to present the same locator in several entries.  You
+\colmarginpar{\texttt{blogurl}} can, however, set the new preamble
+(\textsf{review}) to inherit the URL from the parent blog
+(\textsf{article}).

-\mybigspace A standard \mymarginpar{\textbf{urldate}}
+\mybigspace A standard \colmarginpar{\textbf{urldate}}
\textsf{biblatex} field, it identifies exactly when you accessed a
-given url, and is given in \textsc{iso}8601 format.  The 16th edition
-of the \emph{Manual} prefers DOIs to URLs; in the latter case it
-allows the use of access dates, particularly in contexts that require
-it, but prefers that you use revision dates, if these are available.
-To enable you to specify which date is at stake, I have provided the
-\textbf{userd} field, documented below.  If an entry doesn't have a
-\textsf{userd}, then the \textsf{urldate} will be treated, as before,
-as an access date (14.6--8, 14.184; evanston:library, grove:sibelius,
-hlatky:hrt, osborne:poison, sirosh:visualcortex, wikiped:bibtex).
+given url, and is given in \textsc{iso}8601 format.  The \emph{Manual}
+prefers DOIs to URLs; in the latter case it allows the use of access
+dates, particularly in contexts that require it, but prefers that you
+use revision dates, if these are available.  To enable you to specify
+which date is at stake, I have provided the \textbf{userd} field,
+documented below.  If an entry doesn't have a \textsf{userd}, then the
+\textsf{urldate} will be treated as an access date (14.8, 14.12--13,
+14.207; evanston:library, grove:sibelius, hlatky:hrt, osborne:poison,
+sirosh:visualcortex, wikiped:bibtex).  You can \colmarginpar{New!}
+also use the field to specify a time stamp, should the date alone not
+be specific enough.  The time stamp follows the date, separated by an
+uppercase \enquote{T}, like so: \texttt{yyyy-mm-dd\textbf{T}hh:mm:ss}.
+If you wish to specify the time zone, the \emph{Manual} (10.41)
+prefers initialisms like \enquote{EST} or \enquote{PDT,} and these are
+most easily provided using the \mycolor{\texttt{urltimezone}} field,
+where you can provide your own parentheses if so desired (cp.\
+14.191).  Following the examples in the \emph{Manual}, any
+\textsf{urldate} will by default be printed in 24-hour format, though
+other time stamps use 12-hour format.  The \textsf{biblatex} option
+\texttt{urltime}, discussed in section~\ref{sec:presetopts}, allows
+you to change this in your preamble.

-\mybigspace A \mymarginpar{\textbf{usera}} supplemental
-\textsf{biblatex} field which functions in \textsf{biblatex-chicago}
-almost as a \enquote{\textsf{journaltitleaddon}} field.  In
-\textsf{article}, \textsf{periodical}, and \textsf{review} entries
-with \textsf{entrysubtype} \texttt{magazine}, the contents of this
-field will be placed, unformatted and between commas, after the
-\textsf{journaltitle} and before the date.  The main use is for
-program (14.221; bundy:macneil).
+\mylittlespace A \textsf{urldate} time stamp (and
+\mycolor{\texttt{urltimezone}}) can appear in any entry whatsoever, if
+you judge the online source to be the sort that changes rapidly enough
+for a time stamp to be necessary (14.207, 14.233; wikiped:bibtex).
+You can stop it printing by setting the new
+\colmarginpar{\texttt{urlstamp}} \mycolor{\texttt{urlstamp}} option to
+\texttt{false} in your preamble for the whole document or for
+specified entry types, or in the \textsf{options} field of individual
+entries.  Please see the documentation of \textbf{date}, above, and
+stamps and other parts of \textsf{biblatex's} enhanced date
+specifications.  Table~\ref{tab:online:types} contains a summary of
+the current state of \textsf{biblatex-chicago's} handling of online
+materials.

+\mybigspace This \colmarginpar{\textbf{urltimezone}} field can, if
+necessary, specify the time zone associated with a time stamp given as
+part of an \textsf{urldate}.  The \emph{Manual} prefers initialisms
+like \enquote{EST} for this purpose, and you can provide parentheses
+around it at your discretion (cp.\ 10.41 and 14.191).
+
+\mybigspace A \colmarginpar{\textbf{usera}} supplemental
+\textsf{biblatex} field which in certain contexts in
+\textsf{biblatex-chicago} will identify the broadcast network when you
+cite a radio or television program.  In \textsf{article},
+\textsf{periodical}, and \textsf{review} entries with
+\textsf{entrysubtype} \texttt{magazine}, it acts almost as a
+\enquote{\textsf{journaltitleaddon}} field, and its contents will be
+placed, unformatted and between commas, after the
+\textsf{journaltitle} and before the \textsf{date}.  In \textsf{video}
+entries it comes after the \textsf{eventdate}, i.e., the date of first
+broadcast, and is separated from that date by the \cmd{bibstring}
+\enquote{\texttt{on}} (14.213, 14.265; american:crime, bundy:macneil,
+
\mybigspace I \mymarginpar{\textbf{userc}} have implemented this
supplemental \textsf{biblatex} field as part of Chicago's name
cross-referencing system.  (The \enquote{c} part is meant as a sort of
@@ -3842,7 +4640,7 @@
In the latter case, \textsf{biblatex-chicago} will call \cmd{nocite}
for you, and this method should ensure that there will be at least one
entry in the bibliography to which the cross-reference will point.
-(See 14.84, 14.86; creasey:ashe:blast, creasey:morton:hide,
+(See 14.81--82; creasey:ashe:blast, creasey:morton:hide,
creasey:york:death, lecarre:quest.)

\mybigspace The \mymarginpar{\textbf{userd}} \textsf{userd} field acts
@@ -3855,24 +4653,24 @@
way, what you include in \textsf{userd} will be printed \emph{before}
or \enquote{\texttt{last revised}} are what the field will typically
-contain (14.7--8; wikiped:bibtex).  In the absence of a
+contain (14.12--13; wikiped:bibtex).  In the absence of a
\textsf{urldate} you can, in most entry types, include a
\textsf{userd} field to qualify a \textsf{date} in the same way it
would have modified a \textsf{urldate}.

\mylittlespace Because of the rather specialized needs of some
-audio-visual references, this basic sche\-ma changes for \textsf{music}
-and \textsf{video} entries.  In \textsf{music} entries where an
-\textsf{eventdate} is present, \textsf{userd} will modify that date
-instead of any \textsf{urldate} that may also be present, and it will
-modify an \textsf{origdate} if it is present and there is no
-\textsf{eventdate}.  It will modify a \textsf{date} only in the
+audio-visual references, this basic sche\-ma changes for
+\textsf{music} and \textsf{video} entries.  In \textsf{music} entries
+where an \textsf{eventdate} is present, \textsf{userd} will modify
+that date instead of any \textsf{urldate} that may also be present,
+and it will modify an \textsf{origdate} if it is present and there is
+no \textsf{eventdate}.  It will modify a \textsf{date} only in the
absence of the other three.  In \textsf{video} entries it will modify
an \textsf{eventdate} if it is present, and in its absence the
\textsf{urldate}.  In the absence of those two, it can modify a
\textsf{date}.  Please see the documentation of the \textbf{music} and
\textbf{video} entry types, and especially of the \textsf{eventdate},
-\textsf{origdate}, and \textsf{urldate} fields, above (14.276--279;
+\textsf{origdate}, and \textsf{urldate} fields, above (14.263--65;
nytrumpet:art).

\mylittlespace In all cases, you can start the \textsf{userd} field
@@ -3891,23 +4689,34 @@
\textsf{title} and the translation in \textsf{usere}.  If you choose
the latter, you may need to provide a \textsf{shorttitle} so that the
short note form is also parseable.  Cf.\ \textbf{language}, above.
-(See 14.108--110, 14.194; kern, weresz.)
+(See 14.99; kern, weresz.)

\mybigspace See \mymarginpar{\textbf{userf}}
section~\ref{sec:related}, below.

-%%\enlargethispage{\baselineskip}
-
-\mybigspace Standard \mymarginpar{\textbf{venue}} \textsf{biblatex}
+\mybigspace Standard \colmarginpar{\textbf{venue}} \textsf{biblatex}
offers this field for use in \textsf{proceedings} and
-\textsf{inproceedings} entries, but I haven't yet implemented it,
-mainly because the \emph{Manual} has nothing to say about it.  Perhaps
-the \textsf{organization} field could be used, for the moment,
-instead.  Anything in a \textsf{venue} field will be ignored.
+\textsf{inproceedings} entries, but I haven't yet implemented it
+there, mainly because the \emph{Manual} has nothing to say about it.
+Perhaps the \textsf{organization} field could be used, for the moment,
+instead.  I have implemented the field in the \textbf{misc} entry
+type, both with and without an \textsf{entrysubtype}, in the new
+\mycolor{\textbf{performance}} type, and in the \textbf{unpublished}
+type.  In all uses it will normally present the actual venue of an
+event, as opposed, e.g., to the \textsf{origlocation}, which might
+present where a letter was written or where an earlier edition was
+printed.

-\mybigspace Standard \mymarginpar{\textbf{version}} \textsf{biblatex}
-field, currently only available in \textsf{misc} and \textsf{patent}
-entries in \textsf{biblatex-chicago-notes}.
+\mybigspace Standard \colmarginpar{\textbf{version}} \textsf{biblatex}
+field, formerly only available in \textsf{artwork}, \textsf{image},
+\textsf{misc}, \textsf{music}, and \textsf{pa\-tent} entries in
+\textsf{biblatex-chicago-notes}, but now also in \textbf{book} and
+\mycolor{\textbf{performance}} entries.  In most entry types it prints
+a localized \enquote{\texttt{version}} string, but there may be
+specialist needs in \textsf{artwork} and \textsf{image} entries, so
+there you'll need to specify the type of data inside the field
+itself.  In the \textsf{book} type it is particularly needed for
+presenting multimedia app content (14.268).

\mybigspace Standard \mymarginpar{\textbf{volume}} \textsf{biblatex}
field.  It holds the volume of a \textsf{journaltitle} in
@@ -3915,7 +4724,7 @@
volume of a multi-volume work in many other sorts of entry.  The
treatment and placement of \textsf{volume} information in
\textsf{book}-like entries is rather complicated in the \emph{Manual}
-(14.121--27).  In bibliography entries, the \textsf{volume} appears
+(14.116--22).  In bibliography entries, the \textsf{volume} appears
either before the \textsf{maintitle} or before the publication
information.  In long notes, the same applies, but with the additional
possibility of this information appearing \emph{after} the publication
@@ -3937,43 +4746,45 @@
but at the request of Clea~F.\ Rees I have made this punctuation
customizable, using the command \cmd{postvolpunct}.\
\mymarginpar{\cmd{postvolpunct}} By default it prints \cmd{addcolon},
-but you can use \cmd{renewcommand\{\textbackslash
-  postvolpunct\}\{\ldots\}} in your preamble to redefine it.  Cf.\
-\textsf{part}, and the command documentation in
-section~\ref{sec:formatcommands}.
+but you can use \verb+\renewcommand{\postvolpunct}{...}+ in your
+preamble to redefine it.  Cf.\ \textsf{part}, and the command
+documentation in section~\ref{sec:formatcommands}.

-%%\enlargethispage{\baselineskip}
-
\mybigspace Standard \mymarginpar{\textbf{volumes}} \textsf{biblatex}
-field.  It holds the total number of volumes of a multi-volume work,
-and in the 16th edition of the \emph{Manual} no longer triggers any
-odd changes to the punctuation of short notes (14.159;
-meredith:letters).  If both a \textsf{volume} and a \textsf{volumes}
+field.  It holds the total number of volumes of a multi-volume work
+(meredith:letters).  If both a \textsf{volume} and a \textsf{volumes}
field are present, as may occur particularly in cross-referenced
-entries, then \textsf{biblatex-chicago} will ordinarily suppress the
-\textsf{volumes} field in the list of references, except in some
-instances when a \textsf{maintitle} is present.  In this latter case,
-if the \textsf{volume} appears before the \textsf{maintitle}, the
-option \texttt{hidevolumes}, \mymarginpar{\texttt{hidevolumes}} set to
+entries or in entries using the new \mycolor{\texttt{maintitle}}
+\textsf{relatedtype}, then \textsf{biblatex-chicago} will ordinarily
+suppress the \textsf{volumes} field in your references, except in some
+instances when a \textsf{maintitle} is present.  If the
+\textsf{volume} appears before the \textsf{maintitle}, the option
+\texttt{hidevolumes}, \mymarginpar{\texttt{hidevolumes}} set to
\texttt{true} by default, controls whether to print the
-\textsf{volumes} field after that title or not.  Set it to
-\texttt{false} either in the preamble or in the \textsf{options} field
-of your entry to have it appear after the \textsf{maintitle}.  See the
-option's documentation in section~\ref{sec:chicpreset}, below.
+\textsf{volumes} field after that title or not.  If it appears after
+the \textsf{maintitle}, as with the new \textsf{relatedtype} just
+mentioned, the same option controls whether to print the
+\textsf{volumes} field in close association with the \textsf{volume}.
+Set the option to \texttt{false} either in the preamble or in the
+\textsf{options} field of your entry to have the \textsf{volumes}
+appear in these circumstances.  Cf.\ the option's documentation in
+section~\ref{sec:chicpreset}, below.

\mybigspace A \mymarginpar{\textbf{xref}} modified \textsf{crossref}
field provided by \textsf{biblatex}, which prevents inheritance of any
data from the parent entry.  See \textbf{crossref}, above.

-\mybigspace Standard \mymarginpar{\textbf{year}} \textsf{biblatex}
+\mybigspace Standard \colmarginpar{\textbf{year}} \textsf{biblatex}
field.  It usually identifies the year of publication, though unlike
the \textsf{date} field it allows non-numeric input, so you can put
\enquote{n.d.}\ (or, to be language agnostic,
-\cmd{bibstring\{nodate\}}) here if required, or indeed any other sort
-of non-numerical date information.  If you can guess the date then you
-can include that guess in square brackets instead of, or after, the
-\enquote{n.d.}\ abbreviation.  Cf.\ bedford:photo, clark:mesopot,
+\verb+\bibstring{nodate}+) here if required, or indeed any other sort
+of non-numerical date information.  For many kinds of uncertain and
+unspecified dates it is now much simpler to make use of
+\textsf{biblatex's} enhanced date specifications in the \textsf{date}
+of how \textsf{biblatex-chicago} implements these enhancements.  Cf.\

\subsubsection{Fields for Related Entries}
\label{sec:related}
@@ -4047,17 +4858,16 @@
\texttt{norwegian}, \texttt{portuguese}, \texttt{spanish}, or
\texttt{swedish}, to which I've added \texttt{russian}.

-\mybigspace The \mymarginpar{\textbf{origlocation}} 16th edition of
-the \emph{Manual} has somewhat clarified issues pertaining to the
-documentation of reprint editions and their corresponding originals
-(14.166).  In \textsf{biblatex-chicago} you can provide both an
-\textsf{origlocation} and an \textsf{origpublisher} to go along with
-the \textsf{origdate}, should you so wish, and all of this information
-will be printed in long notes and bibliography.  You can also use this
-field in a \textsf{letter} or \textsf{misc} (with
+\mybigspace This \mymarginpar{\textbf{origlocation}} field mainly
+serves to help document reprint editions and their corresponding
+originals (14.114).  In \textsf{biblatex-chicago} you can provide both
+an \textsf{origlocation} and an \textsf{origpublisher} to go along
+with the \textsf{origdate}, should you so wish, and all of this
+information will be printed in long notes and bibliography.  You can
+also use this field in a \textsf{letter} or \textsf{misc} (with
\textsf{entrysubtype}) entry to give the place where a published or
-unpublished letter was written (14.117).  (Jonathan Robinson has
-suggested that the \textsf{origlocation} may in some circumstances
+unpublished letter was written (14.111, 14.229).  (Jonathan Robinson
+has suggested that the \textsf{origlocation} may in some circumstances
actually be necessary for disambiguation, his example being early
printed editions of the same material printed in the same year but in
different cities.  The new functionality should make this simple to
@@ -4064,56 +4874,51 @@
achieve.  Cf.\ \textsf{origdate} (section~\ref{sec:entryfields}),
\textsf{origpublisher} and \textsf{pubstate}; schweitzer:bach.)
\textbf{NB:} It is impossible to present this same information, as
-here, \emph{inside} a single entry using a \texttt{related} field,
+here, \emph{inside} a single entry using a \textsf{related} field,
though the \textsf{relatedtype} \texttt{origpubin} presents much the
same information \emph{after} the entry, using data extracted from a
separate entry.

\mybigspace As \mymarginpar{\textbf{origpublisher}} with the
-\textsf{origlocation} field just above, the 16th edition of the
-\emph{Manual} has clarified issues pertaining to reprint editions and
-their corresponding originals (14.166).  You can provide an
-\textsf{origpublisher} and/or an \textsf{origlocation} in addition to
-the \textsf{origdate}, and all will be presented in long notes and
-bibliography.  (Cf.\ \textsf{origdate}
-(section~\ref{sec:entryfields}), \textsf{origlocation}, and
-\textsf{pubstate}; schweitzer:bach.)  \textbf{NB:} It is impossible to
-present this same information, as here, \emph{inside} a single entry
-using a \texttt{related} field, though the \textsf{relatedtype}
-\texttt{origpubin} presents much the same information \emph{after} the
-entry, using data extracted from a separate entry.
+\textsf{origlocation} field just above, this field mainly serves to
+help document reprint editions and their corresponding originals
+(14.114).  You can provide an \textsf{origpublisher} and/or an
+\textsf{origlocation} in addition to the \textsf{origdate}, and all
+will be presented in long notes and bibliography.  (Cf.\
+\textsf{origdate} (section~\ref{sec:entryfields}),
+\textsf{origlocation}, and \textsf{pubstate}; schweitzer:bach.)
+\textbf{NB:} It is impossible to present this same information, as
+here, \emph{inside} a single entry using a \textsf{related} field,
+though the \textsf{relatedtype} \texttt{origpubin} presents much the
+same information \emph{after} the entry, using data extracted from a
+separate entry.

-\mybigspace Due \mymarginpar{\textbf{pubstate}} to specific
-requirements in the author-date style, I have implemented this field
-there as a way of providing accurate citations of reprinted books.  As
-the functionality seemed useful, I have also included some of it in
-\textsf{biblatex-chicago-notes}.  In previous releases you could
-identify a reprint by placing \cmd{bibstring\{reprint\}} in the
-\textsf{location} field, followed by a comma, and the style would
-print the appropriate string in notes and bibliography.  Now, if it is
-more convenient, easier to remember, or if you want to reuse your .bib
-database for the author-date style, you can simply put the string
-\texttt{reprint} into the \textsf{pubstate} field, and the package
-will take care of everything for you.  Both of these methods will now
-work just fine, but please choose only one per entry, otherwise the
-string will be printed twice.
+\mybigspace In \colmarginpar{\textbf{pubstate}} response to new
+specifications in the 17th edition of the \emph{Manual} (esp.\
+14.137), I have tried to generalize the functioning of the
+\textsf{pubstate} field in all entry types.  The \texttt{reprint}
+string still has a special status there, being ignored in
+\textsf{video} entries and provoking a syntactic change in the
+presentation of dates in \textsf{music} entries (14.263; floyd:atom),
+while in other types allowing the presentation of reprinted titles.
+Other strings are divided into two types: those which
+\textsf{biblatex-chicago} will print as the \textsf{year}, which
+currently means \emph{only} those for which \textsf{biblatex} contains
+bibstrings indicating works soon to be published, i.e.,
+\texttt{forthcoming}, \texttt{inpreparation}, \texttt{inpress}, and
+\texttt{submitted}; and those, i.e., everything else, which will be
+printed before, and in close association with, other information about
+the publisher of a work.  The four in the first category will always
+be localized, as will \texttt{reprint} and
+\mycolor{\texttt{selfpublished}} (and anything else that
+\textsf{biblatex} finds to be a \cmd{bibstring}) from the second
+category.  All other strings will be printed as-is, capitalized if
+needed, just before the publisher (author:forthcoming,
+contrib:contrib, schweitzer:bach).  \textbf{NB:} The \textsf{pubstate}
+functionality currently has no equivalent using the \textsf{related}
+field.

-\mylittlespace There are a couple of exceptions to this basic
-functionality.  In \textsf{video} entries, no bibstring will be
-printed, as it's not appropriate there, so in effect the
-\textsf{pubstate} field will be ignored.  In \textsf{music} entries,
-the mechanism transforms the \textsf{origdate} from a recording date
-for an album into the original release date for that album.  Whereas a
-recording date will be printed in the middle of the note or
-bibliography entry, the original release date will be printed near the
-end, preceded by the appropriate string.  (Cf.\ 14.276; floyd:atom.)
-Aside from \texttt{reprint}, you can now put \texttt{forthcoming} into
-the field to present works that are about to be published
-(author:forthcoming, contrib:contrib).  Please remember that if you
-put anything else in the \textsf{pubstate} field it will silently be
-ignored, though this may change in future releases.  \textbf{NB:} The
-\textsf{pubstate} functionality currently has no equivalent using the
-\textsf{related} field.
+\enlargethispage{\baselineskip}

\mybigspace This \mymarginpar{\textbf{related}} field is required to
use \textsf{biblatex's} \textsf{related} functionality, and it should
@@ -4134,10 +4939,16 @@
package option \texttt{related} is set to print \textsf{related}
entries only in the bibliography.  If you would like them to appear
only in long notes, in both notes and bibliography, or indeed in
-neither, you can set this option, either in your preamble or in the
-\textsf{options} field of the relevant entry, to \texttt{notes},
-\texttt{true}, or \texttt{false}, respectively.  (See coolidge:speech
-and weed:flatiron.)
+neither, you can set this option, either in your preamble (globally or
+for specific entry types) or in the \textsf{options} field of the
+relevant entry, to \texttt{notes}, \texttt{true}, or \texttt{false},
+respectively (coolidge:speech and weed:flatiron).  For the three
+\textsf{relatedtypes} that construct a single entry using data
+extracted from related entries --- \mycolor{\texttt{commenton}},
+\mycolor{\textsf{maintitle}}, and \texttt{reviewof} ---
+\textsf{biblatex-chicago} will automatically set it to \texttt{true}
+for you entry by entry, as this is required to get properly-formatted
+citations in notes and bibliography.  See below for the details.

\mybigspace This \mymarginpar{\textbf{relatedoptions}} field will, I
should expect, only be needed very rarely.  If you want to set
@@ -4172,7 +4983,8 @@
\textsf{biblatex} styles define six \textsf{relatedtypes}, and I have
either simply adopted them wholesale or adapted them to the needs of
the Chicago style, retaining the basic syntax as much as possible.  I
-have also added one to these six (see below):
+have also added three to these six (see below).  First, the standard
+types:

\begin{description}
\item[\qquad bytranslator:] This prints a full citation of a
@@ -4181,7 +4993,7 @@
\ldots} The reference is fuller in \textsf{biblatex-chicago} than
in the standard styles, and for the first time allows users to
choose the \emph{Manual's} alternate method for presenting original
-  + translation (14.109; furet:related).  The old \textsf{userf}
+  + translation (14.99; furet:related).  The old \textsf{userf}
mechanism provides the other, as does the \texttt{origpubas}
\textsf{relatedtype} (see below).
\item[\qquad default:] This is the macro used when no
@@ -4218,17 +5030,327 @@
behaving oddly please let me know, including whether you are using
\textsf{babel} [which I've tested] or \textsf{polyglossia} [which I
haven't].)
-  package includes this type, and user Bertold Schweitzer suggested it
-  might be a useful addition to \textsf{biblatex-chicago}, so I've
-  added it to the standard six detailed above.  It differs from all of
-  them in that it prints the \textsf{relatedstring} (by default
-  \cmd{bibstring\{reviewof\}}) and the data from the \textsf{related}
-  entry in the middle of the parent entry, rather than at the end.  It
-  also differs from them in being available only in \textsf{article}
-  and \textsf{review} entries (along with the latter's clone,
-  \textsf{suppperiodical}).
+\end{description}
+Now, the Chicago-specific types:
+\begin{description}
+\item[\qquad \mycolor{commenton:}] I designed this new
+  \textsf{relatedtype} to facilitate citation of online comments,
+  though it works slightly differently in the two entry types in which
+  it is available, \textsf{online} and \textsf{review} (with its clone
+  \textsf{suppperiodical}) (14.208--10).  In both types it allows you
+  to mimic thread structure by citing a chain of replies to comments
+  on posts, etc., all in a single entry, while also simplifying your\
+  .bib entries.  This simplification works differently depending on
+  whether the comment itself has no specific title, as always in
+  \textsf{review} entries, or does have such a title, as especially in
+  \textsf{online} social media entries.  In the former case, as you
+  can see from ac:comment, the \textsf{related} apparatus allows you,
+  and indeed encourages you, not to provide a \textsf{title} at all,
+  as contrasted with the old system, still available of course, where
+  your \textsf{title} field contained special formatting for the title
+  of the blog on which this entry is a comment.  Note also here the
+  \textsf{eventdate} field, a requirement, with its optional time
+  stamp, which helps to differentiate multiple comments by the same
+  author posted on the same day.  The \textsf{options} field can be
+  used to prevent the entry appearing in the bibliography, and you can
+  also provide a \textsf{url} specific to the comment, though this is
+  by no means necessary.

+  In social media threads comments and replies may well have their own
+  title, so in such a case you still need a \textsf{title} field,
+  which will be followed by the \textsf{relatedstring}.  In such
+  \mymarginpar{NB!}  \textsf{online} entries, the \emph{only way to
+    cite these comments} is by using the \texttt{commenton}
+  \textsf{relatedtype} (licis:diazcomment).  Note that, unlike
+  \textsf{review} entries, the date, and possible time stamp, of a
+  comment should appear in the \textsf{date} field, not
+  \textsf{eventdate}.  (Other fields, like \textsf{url} and
+  \textsf{options}, have much the same uses as in \textsf{review}
+  entries.)  If, in other \textsf{online} entries, you decided
+  \emph{not} to use \textsf{commenton} in an entry like braun:reply,
+  and simply use a specially-crafted \textsf{titleaddon} field, you
+  lose the possibility of having two dates in the entry, one for the
+  comment and one for the original post, though to be fair it does end
+  up looking like the example in 14.210, where it is ambiguous to
+  which part of the citation the date applies.
+
+  As for the thread structure, I've not tested how far down the rabbit
+  hole you can go, but a series of entries linked one to the next by
+  this \textsf{relatedtype} will all turn up if you cite the first in
+  the chain, though of course you can use the technique merely as a
+  convenient way to structure and simplify your\ .bib file, without
+  creating chains longer than 2 entries.  The default connecting
+  string is the localized \texttt{commenton}, but you can use
+  \textsf{relatedstring} to change it to \enquote{\texttt{reply to}}
+  or whatever else you need.  I've tried to follow the rules for
+  abbreviating parts of the various works included in the one
+  reference, though in truth the \emph{Manual} provides no examples.
+  Depending on whether the various parts have already been cited or
+  not your references can take on quite varied appearances.  Let me
+  know if something looks wrong to you.  Cf.\ ac:comment,
+  diaz:surprise, ellis:blog, and licis:diazcomment for the use of the
+  new \textsf{relatedtype}; amlen:hoot, amlen:wordplay, and viv:amlen
+  for blogs and comments without the \textsf{related} mechanism.
+
+  There are a few other things to remember.  As with the next two
+  \textsf{relatedtypes}, \textsf{biblatex-chicago} will automatically
+  set the \texttt{related} option to \texttt{true} entry-by-entry to
+  ensure that the full data appears both in notes and in the
+  bibliography.  If your parent entry has no \textsf{title} of its
+  own, then, as with the \texttt{reviewof} \textsf{relatedtype}, it
+  will use the \textsf{related} functionality also in short notes,
+  which means that if you want to provide a \textsf{shorttitle} for
+  them then it goes in the \emph{child} entry rather than the parent.
+  Finally, the \textsf{title}-less comments are prime candidates for
+  the \texttt{shortextrafield} option, which prints a disambiguating
+  field after short notes when they would otherwise be
+  indistinguishable.  So endemic is this situation in this context
+  that I've set a default means of disambiguating them, which is the
+  \textsf{date} and \textsf{time} in \textsf{online} entries or the
+  \textsf{eventdate} and \textsf{eventtime} in \textsf{review} and
+  \textsf{suppperiodical}, though you can of course override these
+  defaults by setting the \texttt{shortextra} options yourself.  See
+  their documentation in section~\ref{sec:useropts}, below.
+\item[\qquad \mycolor{maintitle:}] The 17th edition of the
+  \emph{Manual} has deployed, in at least two contexts, a notable
+  syntactic change in the presentation of works that form part of
+  other, larger works.  Generally, the order of presentation, in
+  \textsf{biblatex} terms, has always been \textsf{title} --
+  \textsf{booktitle} -- \textsf{maintitle}, in increasing order of
+  generality.  In the vast majority of cases this order still holds,
+  but in TV episodes, for one example, the recommendation now is to
+  present the name of the series (\textsf{booktitle}) \emph{before}
+  the name of the episode (\textsf{title}). (See the \textbf{video}
+  type in section~\ref{sec:entrytypes}, above).  The other context in
+  which this reversal occurs is multi-volume works (14.116--22).
+  Here, the preferred format, at least for notes, appears to be
+  \textsf{maintitle} -- \textsf{[book]title} or, when all three titles
+  are present, \textsf{title} -- \textsf{maintitle} --
+  \textsf{booktitle}.  The \emph{Manual} doesn't carry this reordering
+  through with absolute consistency, but I think it important at least
+  to offer it as a possibility to users of \textsf{biblatex-chicago},
+  hence the new \mycolor{\texttt{maintitle}} \textsf{relatedtype},
+  which is currently the only way to achieve this reversal in this
+  context.
+
+  In its simplest usage, to document one volume of a multi-volume set,
+  you would have, e.g., an \textsf{mvcollection} entry with
+  \textsf{relatedtype} \texttt{maintitle}, and a \textsf{related}
+  field pointing to a \textsf{collection} entry.  When you cite the
+  \textsf{mvcollection} entry itself, you'll get a long note like
+  \emph{MVCollTitle}, vol.\ 1, \emph{CollTitle}, and a short note like
+  \emph{MVCollTitle}, vol.\ 1., or, with a \textsf{postnote} field,
+  \emph{MVCollTitle}, 1:12, as the specification requires.  If you
+  wanted to cite one essay in the \textsf{collection}, then you would,
+  additionally, need an \textsf{incollection} entry with the
+  \texttt{maintitle} \textsf{relatedtype} and a \textsf{related} field
+  pointing to the \textsf{mvcollection} entry already mentioned, so
+  you're creating a chain of three different related entries but
+  presenting them in one reference, i.e., (long form)
+  \enquote{InCollTitle,} in \emph{MVCollTitle}, vol.\ 1,
+  \emph{CollTitle}, and (short form) \enquote{InCollTitle.}  It's
+  important to keep in mind here that, in effect, you're \emph{not}
+  actually citing the \textsf{mvcollection} entry, but the one volume
+  of it represented by the \textsf{collection} entry, or indeed an
+  essay in that one volume.
+
+  Now, for the details, which are many.  First, any \textsf{mv*} entry
+  without the \texttt{maintitle} \textsf{relatedtype} should behave
+  just as it always has, and can still happily be used as the target
+  of \textsf{crossref} fields to supply a \textsf{maintitle} to other
+  entries.  The abbreviated references created when you have several,
+  e.g., \textsf{books crossref'd} to the same \textsf{mvbook} are
+  still available, assuming you enable them with the
+  \texttt{booklongxref} option.  You can happily mix the new and the
+  old methods of presentation in your documents, but please don't mix
+  them within individual entries, which means that if you are using a
+  \textsf{crossref} field to an \textsf{mvcollection} entry in a
+  \textsf{collection} entry, say, and the \textsf{collection} entry is
+  itself the target of the \textsf{mvcollection} entry's
+  \textsf{related} field, please be careful not to cite that
+  \textsf{collection} entry independently, as it can lead to
+  unexpected results.  (If things don't look right to you, try
+  eliminating the use of \textsf{crossref} entirely from these
+  \textsf{related} chains and see if that helps, then send me a bug
+  report if it does.)  This restriction also means that, although the
+  \emph{Manual} prefers the \textsf{maintitle}-first format in notes
+  and allows either syntax in the bibliography, nonetheless with
+  \textsf{biblatex-chicago} whichever syntax you choose for the notes
+  will also appear in the bibliography.
+
+  As for automatically abbreviating references using the
+  \texttt{maintitle} \textsf{relatedtype}, this works differently
+  depending on whether the \textsf{related} chain consists of 2 or 3
+  works.  In 2-work chains (\emph{MVCollTitle}, \emph{CollTitle}),
+  it's actually the first that needs abbreviating, and this didn't
+  look right, so these entries will always print in full.  (You can
+  still regulate how much information appears in the references to
+  individual volumes by regulating how much information appears in the
+  .bib entries for those volumes.  In the harleymt:* entries I've used
+  as examples below, the individual volumes have a \textsf{crossref}
+  field to the multi-volume work, so they inherit the
+  \textsf{publisher} and \textsf{location}, for example.  If you were
+  to omit the \textsf{crossref} field you would always get an
+  abbreviated reference which, were it to appear \emph{after} a
+  reference to the whole multi-volume work, would let that reference
+  give the complete publication details and itself behave like a
+  normal abbreviated cross reference to it.)
+
+  In 3-work chains, when you've cited more than one
+  \enquote{InCollTitle} from a given \emph{CollTitle}, you can choose
+  for the short note version of the second and third titles (with just
+  volume number rather than full \emph{CollTitle}) to appear in the
+  bibliography and in long notes after the first one.  This is
+  controlled using the same \texttt{booklongxref} option as you would
+  use to control the old automatic abbreviation mechanism.  See under
+  that option in section~\ref{sec:chicpreset}, below.
+
+  As with the other two \textsf{relatedtypes} I've added to
+  \textsf{biblatex's} standard six, the \texttt{maintitle} type is
+  somewhat restricted in its relevance.  If you want to use a
+  three-work chain to cite one part of one volume, then this is
+  possible only by starting with the following entry types:
+  \textsf{bookinbook}, \textsf{inbook}, \textsf{incollection},
+  \textsf{inproceedings}, and \textsf{letter}.  All two-work chains
+  must start with one of the \textsf{mv*} types.  As might be apparent
+  from the previous list, \textsf{mvreference} entries are special, in
+  that their \textsf{related} field should point to an
+  \textsf{inreference} entry if you want to cite an entry in an
+  \enquote{alphabetically arranged work}, or to a \textsf{reference}
+  entry otherwise.  In other words, \textsf{mvreference} entries
+  should only ever be used in 2-work chains.
+
+  It's possible it may have occurred to you that this
+  \textsf{relatedtype} could, given the presence of a many-volumed
+  collection, require rather a lot of extra entries in your\ .bib
+  files, i.e., one extra \textsf{mv*} entry for every volume of the
+  collection you wish to cite.  Borrowing an idea from the
+  \texttt{multivolume} \textsf{relatedtype}, you can put the entry
+  keys of \emph{all} the individual volumes into a single
+  \textsf{related} field in a single \textsf{mv*} entry, and
+  \textsf{biblatex-chicago} will still allow you to cite each volume
+  independently, and for each to appear independently in the
+  bibliography, too, unlike the \texttt{multivolume} mechanism.
+  Here's how it works.  When \textsf{Biber} detects more than one
+  entrykey in an \textsf{mv*} entry with \texttt{maintitle}
+  \textsf{relatedtype}, it produces a series of clones of the
+  \textsf{mv*} entry, each with the same \textsf{relatedtype} and a
+  \textsf{related} field containing exactly \emph{one} of the
+  entrykeys from the original \textsf{related} field.  It gives each
+  of these clones its own entrykey, of the form
+  \texttt{mventrykey-singlevolumeentrykey}, and it is these virtual,
+  cloned entries that you should cite.  Such entries don't exist in
+  your\ .bib file, but you can see them in your\ .bbl file, assuming
+  you've actually cited any of them.  The original
+  \texttt{mventrykey}, in this case, refers merely to the original
+  field, so it's available for citing the multi-volume set as a whole,
+  should that be necessary.  Indeed, to make the virtual clones
+  available to \textsf{Biber} (and \textsf{biblatex}) in the first
+  place, you do need to cite (or \cmd{nocite}) the original
+  \textsf{mv*} entry somewhere in your document.
+
+  As an example of how this might look, consider the
+  three entries from \textsf{notes-test.bib}: harleymt:hoc,
+  harleymt:ancient:cart, and harleymt:cartography.  The first, an
+  \textsf{mvcollection} entry, has a \textsf{related} field containing
+  both of the others (\textsf{collec\-tion} entries), and in
+  \textsf{cms-notes-sample.tex} you'll see citations of harleymt:hoc,
+  harleymt:hoc-harleymt:ancient:cart, and
+  harleymt:hoc-harleymt:cartography,\break which are themselves
+  \textsf{mvcollection} entries.  The latter two don't exist in the\
+  .bib file, only in the\ .bbl file, where you'd see that each has a
+  \textsf{related} field pointing to the entrykey that forms the
+  second half of its own hyphenated key.  If I hadn't somewhere cited
+  harleymt:hoc then \textsf{Biber} would give up entirely because it
+  wouldn't know where to find the two hyphenated keys.
+
+  A similar problem arises when you create a three-work chain in which
+  the first, e.g., \textsf{incollection}, entry contains a
+  \textsf{related} field pointing to just such a virtual, cloned
+  entry.  In this case, if you haven't already cited (or
+  \cmd{nocite}'d) the cloned entry, \textsf{Biber} really gets,
+  understandably, confused.  As a convenience feature for this
+  situation, I have included a very slightly modified version of the
+  \texttt{maintitle} \textsf{relatedtype}, called
+  \colmarginpar{\texttt{maintitlenc}} \mycolor{\texttt{maintitlenc}},
+  the \enquote{nc} standing for \cmd{nocite}.  As you might have
+  guessed, every clone produced by an \textsf{mv*} entry with multiple
+  entrykeys in its \textsf{related} field and \texttt{maintitlenc} as
+  its \textsf{relatedtype} will automatically be \cmd{nocite}'d, and
+  will then be available for inclusion in another entry's
+  \textsf{related} field.  The \texttt{maintitlenc} type differs in no
+  other way whatever from the \texttt{maintitle} type.
+
+  In general, the \textsf{maintitle} \textsf{relatedtype} attempts to
+  follow the Chicago specification with as little intervention needed
+  from the user as possible.  To that end, \textsf{biblatex-chicago}
+  automatically sets the \texttt{related} option to \texttt{true}
+  entry-by-entry to ensure that the full data appears both in notes
+  and in the bibliography.  It also attempts to spot duplicate
+  \textsf{authors} or \textsf{editors} and to print them only when
+  needed, and in its short-note version uses the \textsf{volume} and
+  \textsf{part} information from the \textsf{related}
+  \textsf{collection} entry, say, to specify the \textsf{labeltitle}
+  which comes from the \textsf{mvcollection}.  If you want the
+  \textsf{mv*} entry's \textsf{volumes} data to appear in notes and
+  bibliography, you can do so by setting the \texttt{hidevolumes}
+  option to \texttt{false} either in the preamble or in the
+  \textsf{options} field of the entry referenced by the \textsf{mv*}
+  entry's \textsf{related} field (cf.\ harleymt:cartography).
+
+  Another, trickier intervention involves the problem of sorting
+  entries in the bibliography.  The \emph{Manual's} rules are,
+  basically, to sort by name, then title, then year, and as every
+  \textsf{mv*} entry citing the same multi-volume work will basically
+  have identical values for all three, the sorting order in the
+  bibliography will fall back on the order in which such works are
+  cited, which may not be what you want.  If the pertinent
+  \textsf{related} fields in your\ .bib file only contain one
+  entrykey, then you can use a series of \textsf{sortkey},
+  \textsf{sorttitle}, or \textsf{sortyear} fields to arrange the
+  volumes as you wish.  If you are using \textsf{Biber's} cloning
+  facilities, however, any such fields in the \textsf{mv*} entry will
+  be copied into all of its clones, so you'll be back to square one.
+  My current solution to this dilemma \mymarginpar{\textsf{sorttitle}}
+  is to treat the \textsf{sorttitle} field as special, so that in
+  \textsf{mv*} entries with \textsf{relatedtype} \texttt{maintitle} or
+  \texttt{maintitlenc} and a \textsf{related} field containing more
+  than one entrykey any \textsf{sorttitle} field is indeed copied to
+  all of the clones, but it is also modified by appending the contents
+  of the clone's \textsf{related} field to the end of it.  (If there
+  is no \textsf{sorttitle} field, then the clones will have none,
+  either.)  In effect, the alphabetical order of the entrykeys in the
+  \textsf{mv*} entry's \textsf{related} field determines the sorting
+  order of the clones each of which contains a \textsf{related} field
+  holding one of those keys.  (In the examples from
+  \textsf{notes-test.bib}, harleymt:hoc retains its original
+  \textsf{sorttitle} field, and sorts first, then
+  harleymt:hoc-harleymt:ancient:cart sorts before
+  harleymt:hoc-harleymt:cartography --- the second half of the key,
+  after the hyphen, is the relevant part, and is what appears appended
+  to the original \textsf{sorttitle} field.)  It is rather onerous, I
+  know, to be required to choose entrykeys that sort properly; if I
+  come up with something better I'll include it in a later release.
+
+  Finally, although I've tested this functionality extensively, it's
+  new and rather complicated.  If something doesn't work right please
+  let me know at the email address at the head of this documentation.
+\item[\qquad reviewof:] Philip Kime's \textsf{biblatex-apa} package
+  includes this type, and user Bertold Schweitzer suggested it might
+  to the standard six detailed above.  It differs from all of them,
+  and resembles \mycolor{\texttt{commenton}} and
+  \mycolor{\texttt{maintitle}}, in that it prints the
+  \textsf{relatedstring} (by default \verb+\bibstring{reviewof}+) and
+  the data from the \textsf{related} entry in the middle of the parent
+  entry, rather than at the end.  It differs from
+  \mycolor{\texttt{commenton}} in that it's not possible to create a
+  chain of such entries to mimic online thread structures.  Finally,
+  it differs from all other \textsf{relatedtypes} in being available
+  only in \textsf{article} and \textsf{review} entries (along with the
+  latter's clone, \textsf{suppperiodical}).
+
In \textsf{article} entries it replaces the \textsf{titleaddon} with
the \textsf{relatedstring} followed by the \textsf{title} of the
child entry, and in \textsf{review} entries it replaces the
@@ -4242,18 +5364,18 @@
This mechanism automates both the provision of the localized
\cmd{bibstring} and also the formatting of the \textsf{title} of the
reviewed work, and it also obviates the need to use any of the
-  \cmd{partedit} macros in this context.  You should, however,
-  remember to set the \texttt{related} option to \texttt{true} (either
-  in the preamble or in individual entries) to ensure that the full
-  data appears both in notes and in the bibliography.  Also, if the
-  mechanism doesn't work for you in a particular context, remember
-  that the standard way of presenting reviewed works is still
-  available.  Finally, this \textsf{relatedtype} has the further
-  peculiarity that, in \textsf{review} and \textsf{suppperiodical}
-  entries only, it uses the \textsf{related} functionality also in
-  short notes, which means that if you want to provide a
-  \textsf{shorttitle} for short notes then it goes in the \emph{child}
-  entry rather than the parent.
+  \cmd{partedit} macros in this context.  Further,
+  \textsf{biblatex-chicago} automatically sets the \texttt{related}
+  option to \texttt{true} entry-by-entry to ensure that the full data
+  appears both in notes and in the bibliography.  Finally, this
+  \textsf{relatedtype} has the further peculiarity that, in
+  \textsf{review} and \textsf{suppperiodical} entries only, it uses
+  the \textsf{related} functionality also in short notes, which means
+  that if you want to provide a \textsf{shorttitle} for short notes
+  then it goes in the \emph{child} entry rather than the parent.
+  Please remember, too, that the standard way of presenting reviewed
+  works is still available if the mechanism doesn't work for you in a
+  particular context.
\end{description}

\mybigspace \textbf{NB:} \mymarginpar{\textbf{reprinttitle}}
@@ -4267,10 +5389,10 @@
original publication details of an essay or a chapter that you are
citing from a subsequent reprint, e.g., a \emph{Collected Essays}
volume.  In such a case, at least according to the \emph{Manual}
-(14.115), such details needn't be provided in notes, only in the
-bibliography, and then only if these details are \enquote{of
-  particular interest.}  The data would follow an introductory phrase
-like \enquote{originally published as,} making the problem strictly
+(14.181), such details needn't be provided in notes, only in the
+bibliography, and then only if these details are \enquote{of specific
+  interest.}  The data would follow an introductory phrase like
+\enquote{originally published as,} making the problem strictly
parallel to that of including details of a work in the original
language alongside the details of its translation.  I have addressed
the latter problem with the \textsf{userf} field, which provides a
@@ -4292,7 +5414,7 @@
\mybigspace This \mymarginpar{\textbf{userf}} is one of the
supplemental fields which \textsf{biblatex} provides, and is used by
\textsf{biblatex-chicago} for a very specific purpose.  When you cite
-both a translation and its original, the \emph{Manual} (14.109)
+both a translation and its original, the \emph{Manual} (14.99)
recommends that, in the bibliography at least, you combine references
to both texts in one entry, though the presentation in notes is pretty
much up to you.  In order to follow this specification, I have
@@ -4314,7 +5436,7 @@
the data for the translation will be printed first, followed by the
string \texttt{originally published as}, followed by the original,
author omitted, in what amounts to the same format that the
-\emph{Manual} uses for long footnotes (furet:pas\-sing:eng,
+\emph{Manual} uses for long footnotes (furet:passing:eng,
furet:passing:fr).  As explained above (\textbf{origlanguage}), I have
also included a way to modify the string printed before the original.
In the entry for the \emph{translation}, you put the original's
@@ -4371,9 +5493,9 @@
capital will always be retained.  (cf., e.g., creel:house,
morgenson:market.)  If, on the other hand, you for some reason need
such a field always to start with a lowercase letter, then you can try
-using the \cmd{isdot} macro at the start, which turns off the
-mechanism without printing anything itself.  Here, then, is the
-complete list of fields where this functionality is active:
+putting an empty set of curly braces\ \{\}\ at the start, which turns
+off the mechanism without printing anything itself.  Here, then, is
+the complete list of fields where this functionality is active:

\begin{enumerate}
\setlength{\parskip}{-4pt}
@@ -4413,75 +5535,24 @@
very powerful mechanism to allow \textsf{biblatex} automatically to
provide a localized version of a string, and to determine whether that
string needs capitalization, depending on where it falls in an entry.
-In the first release of \textsf{biblatex-chicago-notes}, the style
-relied very heavily on this macro, particularly on an extension I
-provided by defining all 26 letters of the (ASCII) alphabet as
-\texttt{bibstrings} (\cmd{bibstring\{a\}}, \cmd{bibstring\{b\}}, etc.)
-While you should continue to use the standard, whole-word bibstrings,
-\textbf{all use of the single-letter variants I formerly provided is
-  obsolete, and will generate an error}.  This functionality has been
-replaced by the \cmd{autocap} command, which does the same thing, only
-more elegantly.  For yet greater convenience I have implemented,
-following \textsf{biblatex's} example, a system automating this
-functionality in all of the entry fields where its use was, by my
-reckoning, most frequent.  This means that, when you require this
-functionality, all you need do is input the data in such a field
-starting with a lowercase letter, and \textsf{biblatex-chicago-notes}
-will do the rest with no further assistance.  In my
-\textsf{notes-test.bib} file, this mechanism in effect eliminated
-all need for the single-letter \texttt{bibstrings} and very nearly all
-need for the \cmd{autocap} command --- centinel:letters and
-powell:email being the only exceptions.  Please see
-\textbf{\textbackslash autocap} above for full details.
-
-%%\enlargethispage{\baselineskip}
-
-\mylittlespace I should also mention here that \textsf{biblatex 0.7}
-introduced functionality which sometimes allows you simply to input,
-\cmd{bibstring\{newse\-ries\}}, the package auto-detecting when a
+\textsf{Biblatex 0.7} introduced functionality which sometimes allows
+you simply to input, for example, \texttt{newseries} instead of
+\verb+\bibstring{newseries}+, the package auto-detecting when a
bibstring is involved and doing the right thing, though in all such
cases either form will work.  This functionality is available in the
-\textsf{series} field of \textsf{article}, \textsf{periodical}, and
-\textsf{review} entries; in the \textsf{type} field of
-\textsf{manual}, \textsf{patent}, \textsf{report}, and \textsf{thesis}
-entries; in the \textsf{location} field of \textsf{patent} entries; in
-the \textsf{language} field in all entry types; and in the
-\textsf{nameaddon} field in \textsf{customc} entries.  There may be
-other places where \textsf{biblatex's} standard styles support this
-feature, and I shall add them when they come to my attention.
+\textsf{series} field of \textsf{article}, \textsf{jurisdiction},
+\textsf{legislation}, \textsf{periodical}, and \textsf{review}
+entries; in the \textsf{type} field of \textsf{audio},
+\textsf{manual}, \textsf{music}, \textsf{patent}, \textsf{report},
+\textsf{suppbook}, \textsf{suppcollection}, \textsf{thesis}, and
+\textsf{video} entries; in the \textsf{location} field of
+\textsf{patent} entries; in the \textsf{language} field in all entry
+types; in the \textsf{nameaddon} field in \textsf{customc} entries;
+and in the \textsf{editor[abc]type} and \textsf{nameatype} fields in
+all entry types.  There may be other places where \textsf{biblatex's}
+standard styles support this feature, and I shall add them when they
+come to my attention.

-\mybigspace In \mymarginpar{\textbf{\textbackslash custpunct} \\
-  \textbf{\textbackslash custpunctb}} common with other American
-citation styles, the \emph{Manual} requires that the commas and
-periods separating units of a reference go inside any quotation marks
-that happen to be present.  As of version 0.8c, \textsf{biblatex}
-contains truly remarkable code that handles this situation in very
-nearly complete generality, detecting punctuation after the closing
-quotation mark and moving it inside when necessary, and also
-controlling which punctuation marks can be printed after which other
-punctuation marks, whether quotation marks intervene or not.  This
-functionality is now mature, and \textsf{biblatex-chicago-notes}
-relies on this code to place punctuation in the \enquote{American
-  style,} rather than on complicated \cmd{DeclareFieldFormat}
-instructions that attempt to anticipate all possible permutations.
-One result of this, thankfully, is that both \cmd{custpunct} and
-\cmd{cust\-punctb} are now basically unnecessary, as their only purpose
-was to supply context-appropriate punctuation inside any quotation
-marks that users themselves provided as part of various entry fields.
-A second consequence, and I've already recommended this in previous
-releases anyway, is that users now \emph{must} use \cmd{mkbibquote}
-instead of \cmd{enquote} or the usual \LaTeX\ mechanisms inside their
-.bib files.  For further details, please see the \cmd{mkbibquote}
-entry below.
-
-\mylittlespace I have retained the code for the \cmd{custpunct}
-commands in \textsf{chicago-notes.cbx}, in case a particularly gnarly
-entry might still require them, but I have already started to re-use
-the \textsf{type} field, which formerly served as a switch for
-\cmd{custpunct}, in other contexts (see \textbf{artwork},
-\textbf{image}, and \textbf{suppbook} above).
-
\mybigspace These \mymarginpar{\textbf{\textbackslash
foottextcite\\\textbackslash foottextcites}} two commands look
like citation commands, but are in fact wrappers for customizing the
@@ -4494,32 +5565,15 @@
preamble.  The default definitions are: \texttt{\{\textbackslash
behavior of previous releases of \textsf{biblatex-chicago}, for
example, you could change the first to: \texttt{\{\textbackslash
newcunit\textbackslash bibstring\{in\}\textbackslash
only using \cmd{headlesscites}.  (There is also, by the way, a
-\cmd{head\-lessparencite(s)} command if you want to retain the long
+\cmd{headlessparencite(s)} command if you want to retain the long
citations inside the parentheses.)

-%\enlargethispage{\baselineskip}
-
-\mybigspace This \mymarginpar{\textbf{\textbackslash isdot}} is a
-standard \textsf{biblatex} macro, which in previous releases of
-\textsf{biblatex-chicago} could function as a convenient placeholder
-in entry fields that, for one reason or another, you may have wanted
-to have defined and yet to print nothing.  With the release of
-\textsf{biblatex} 1.6, this no longer works as before, a situation
-which has revealed a number of inconsistencies and bugs in my code,
-the rectification of which may therefore require some changes to your
-.bib files, assuming you've taken advantage of this mechanism.  I
-believe that all the situations formerly calling for this specific use
-of the macro can now be addressed by more standard means, i.e., the
-declaration in the \textsf{options} field.  (See creel:house,
-nyt:obittrevor, sewall:letter, unsigned:ranke, and white:total.)
-
\mybigspace I \mymarginpar{\textbf{\textbackslash letterdatelong}}
have provided this macro mainly for use in the optional postnote field
of the various citation commands.  When citing a letter (published or
@@ -4526,9 +5580,10 @@
unpublished, \textsf{letter} or \textsf{misc}), it may be useful to
append the date to the usual short note form in order to disambiguate
references.  This macro simply prints the date of a letter, or indeed
-of any other sort of correspondence.  (If your main document language
-isn't English, it's better just to use the standard \textsf{biblatex}
-command \cmd{printorigdate}.)
+of any other sort of correspondence, in day-month-year order, as
+recommended by the \emph{Manual} (14.224).  (If your main document
+language isn't American, it's better just to use the standard
+\textsf{biblatex} command \cmd{printorigdate}.)

\mybigspace This \mymarginpar{\textbf{\textbackslash mkbibquote}} is
the standard \textsf{biblatex} command, which requires attention here
@@ -4549,10 +5604,10 @@
\mylittlespace In an \textsf{article} entry, the \textsf{title}
contains a quoted phrase:

-\begin{quotation}
-  \noindent\texttt{title = \{Diethylstilbestrol and Media Coverage of the \\
-    \indent\cmd{mkbibquote}\{Morning After\} Pill\}}
-\end{quotation}
+\begin{verbatim}
+  title = {Diethylstilbestrol and Media Coverage of the
+    \mkbibquote{Morning After} Pill}
+\end{verbatim}

Here, because the quoted text doesn't come at the end of title, and no
punctuation will ever need to be drawn within the closing quotation
@@ -4563,10 +5618,9 @@
\enquote{Diethylstilbestrol and Media Coverage of the \enquote{Morning
After} Pill.}  Here, by contrast, is a \textsf{book title}:

-\begin{quotation}
-  \noindent \texttt{title = \{Annotations to
-    \cmd{mkbibquote}\{Finnegans Wake\}\}}
-\end{quotation}
+\begin{verbatim}
+  title = {Annotations to \mkbibquote{Finnegans Wake}}
+\end{verbatim}

Because the quoted title within the title comes at the end of the
field, and because this bibliographical unit will be separated from
@@ -4582,7 +5636,7 @@

\mybigspace The \mymarginpar{\textbf{\textbackslash postvolpunct}}
-\emph{Manual} (14.121) unequivocally prescribes that when a
+\emph{Manual} (14.116) unequivocally prescribes that when a
\textsf{volume} number appears immediately before a page number,
\enquote{the abbreviation \emph{vol.}\ is omitted and a colon
separates the volume number from the page number with no intervening
@@ -4594,24 +5648,23 @@
\cmd{postvolpunct} command, which prints the punctuation between a
\textsf{volume} number and a page number.  It is set to \cmd{addcolon}
by default, except when the current language of the entry is French,
-You can use \cmd{renewcommand\{\textbackslash
-  postvolpunct\}\{\ldots\}} in your preamble to redefine it, but
-please note that the command only applies in this limited context, not
-more generally to the punctuation that appears between, e.g., a
-\textsf{volume} and a \textsf{part} field.
+\verb+\renewcommand{\postvolpunct}{...}+ in your preamble to redefine
+it, but please note that the command only applies in this limited
+context, not more generally to the punctuation that appears between,
+e.g., a \textsf{volume} and a \textsf{part} field.

-%\enlargethispage{-\baselineskip}
-
\mybigspace This \mymarginpar{\textbf{\textbackslash reprint}} and the
following 7 macros all help \textsf{biblatex-chicago-notes} cope with
the fact that many bibstrings in the Chicago system differ between
notes and bibliography, the former sometimes using abbreviated forms
when the latter prints them in full.  In the current case, if a book
-is a reprint, then the macro \cmd{reprint}, followed by a comma,
-should go in the \textsf{location} field before the city of
-publication (aristotle:metaphy:gr, schweit\-zer:bach).  See
-\textbf{location}, above.
+is a reprint, then the macro \cmd{reprint}, followed by a comma, could
+go in the \textsf{location} field before the city of publication.
+Simply putting \enquote{\texttt{reprint}} into the \textsf{pubstate}
+field is a simpler way to achieve the same result
+(aristotle:metaphy:gr, schweitzer:bach).  See \textsf{location} and
+\textsf{pubstate} in section~\ref{sec:entryfields}, above.

\mylittlespace \textbf{NB:} The rules for employing abbreviated or
full bibstrings in the \emph{Manual} are remarkably complex, but I
@@ -4653,8 +5706,6 @@
new version of the command should take care of this automatically for
you.)  See chaucer:liferecords.

-%\enlargethispage{-\baselineskip}
-
\mybigspace As \mymarginpar{\textbf{\textbackslash
partedit-\\andcomp}} before, but for use when an editor is also a
compiler.
@@ -4676,12 +5727,55 @@
whose name doesn't conveniently fit into the usual fields
(\textsf{translator} and \textsf{nameb}).

+\mylittlespace Unlike \colmarginpar{\textbf{\textbackslash
+    suppress-\\bibfield[]\{\}}} the other commands presented here,
+this should be used in your document preamble rather than in your
+bibliographical apparatus.  Also unlike them, it has two arguments,
+the first of which is optional, the second required.  Jan David Hauck
+suggested that, in addition to the field-exclusion package options
+provided by \textsf{biblatex-chicago} (see
+section~\ref{sec:chicpreset}), I might also provide a general-purpose
+macro to clear fields from selected entry types when the package
+options aren't quite right for a user's particular needs.  The
+\mycolor{\cmd{suppressbibfield}} command does this, so that
+\verb+\suppressbibfield{note}+ clears the \textsf{note} field from
+\emph{all} entries, while \verb+\suppressbibfield[report]{note}+
+clears it only from \textsf{report} entries.  Both arguments take
+comma-separated lists, so to suppress \textsf{titleaddon} and
+\textsf{volumes} fields from \textsf{report} and \textsf{manual}
+
+\mylittlespace A few usage notes are in order.  First, you can use as
+many calls to the command in your preamble as you wish.  Second, the
+command is a very basic user interface to \textsf{biblatex's} source
+mapping functionality (\textsf{biblatex.pdf} \S~4.5.3), so what it
+does is modify what \textsf{biber} takes from your .bib file in order
+to produce the .bbl file that \textsf{biblatex} actually reads.  As
+far as \textsf{biblatex} is concerned, the fields simply aren't there
+in the data source, so they can't appear anywhere in the
+bibliographical apparatus, whether in notes, bibliography or shorthand
+lists.  Third, because source mapping is involved, you'll need a
+complete cycle of \LaTeX-\textsf{biber}-\LaTeX\ runs to make the
+commands take effect.  Fourth, source mapping occurs at a very early
+stage in \textsf{biber's} operation, so if your field names or entry
+types are standard aliases, the command will only work on the names as
+they appear in your .bib file, not as they are aliased in the .bbl
+file.  If you have a \textsf{techreport} entry, for example, it won't
+be affected by a command that alters \textsf{report} entries, and a
+\textsf{date} field won't be affected by a command that suppresses the
+\textsf{year}.  Fifth, the code for the command resides in
+\textsf{biblatex-chicago.sty}, so if you load the styles without
+loading that package it won't be available to you.  Sixth and finally,
+the \mycolor{\cmd{suppressbibfield}} command is new and relatively
+untested, so please report any untoward behavior to me.
+
\subsubsection{Citation Commands}
\label{sec:citecommands}

The \textsf{biblatex} package is particularly rich in citation
commands, some of which (e.g., \cmd{supercite(s)}, \cmd{citeyear})
-provide functionality that isn't really needed by the Chi\-cago notes
+provide functionality that isn't really needed by the Chicago notes
and bibliography style offered here.  If you are getting unexpected
behavior when using them please have a look in your .log file ---
there may be warnings there that alert you to undefined citation
@@ -4703,7 +5797,7 @@
solution is to use \cmd{Cite} instead.  Alternatively, don't use a
\cmd{footnote} macro at all, rather try \cmd{footcite} or
\cmd{autocite} with the optional prenote and postnote arguments.  Cf.\
-\cmd{Citetitle} below, and also section~3.7 of \textsf{biblatex.pdf}.
+\cmd{Citetitle} below, and also section~3.8 of \textsf{biblatex.pdf}.

\mybigspace I \mymarginpar{\textbf{\textbackslash autocite}} haven't
adapted this in the slightest, but I thought it worth pointing out
@@ -4718,11 +5812,11 @@
\cmd{cite} command works just as you would expect it to, I have also
provided a starred version for the rare situations when you might need
to turn off the ibidem tracking mechanism.  \textsf{Biblatex} provides
-very sophisticated algorithms for using \enquote{Ibid} in notes, so in
-general you won't find a need for this command, but in case you'd
-prefer a longer citation where you might automatically find
-\enquote{Ibid,} I've provided this.  Of course, you'll need to put it
+very sophisticated algorithms for this mechanism, so in general you
+won't find a need for this command, but in case you'd prefer a longer
+citation where you might automatically find the shortest one, I've
+provided this.  Of course, you'll need to put it inside a
\ref{sec:useropts}, below.)

\mybigspace I \mymarginpar{\textbf{\textbackslash citeauthor}} have
@@ -4730,9 +5824,9 @@
bring it into line with \textsf{biblatex-chicago's} needs.  Its main
usage will probably be for references to works from classical
antiquity, when an \textsf{author's} name (abbreviated or not)
-sometimes suffices in the absence of a \textsf{title}, e.g.,
-Thuc.\ 2.40.2--3 (14.258).  You'll need to put it inside a
-\cmd{footnote} command manually.  (Cf.\ also \textsf{entrysubtype} in
+sometimes suffices in the absence of a \textsf{title}, e.g., Thuc.\
+2.40.2--3 (14.244).  You'll need to put it inside a \cmd{footnote}
+command manually.  (Cf.\ also \textsf{entrysubtype} in
section~\ref{sec:entryfields}, above.)

\mybigspace This \mymarginpar{\textbf{\textbackslash citejournal}}
@@ -4741,10 +5835,10 @@
\textsf{volume} number instead of the article \textsf{title} after the
\textsf{author's} name.  The \emph{Manual} suggests that this format
might be helpful \enquote{in the absence of a full bibliography}
-(14.196).  It may also prove useful when you want to provide
+(14.185).  It may also prove useful when you want to provide
parenthetical references to newspaper articles within the text rather
than in the bibliography, a style endorsed by the \emph{Manual}
-(14.206).  In such a case, an article's author, if there is one, could
+(14.198).  In such a case, an article's author, if there is one, could
form part of the running text.  As usual with these general citation
commands, if you want the reference to appear in a footnote you need
to put it inside a \cmd{footnote} command manually.
@@ -4764,17 +5858,15 @@
if the need arises.  Remember that you'll have to put it inside a
\cmd{footnote} command manually.

-%\enlargethispage{-\baselineskip}
-
\mybigspace Another \mymarginpar{\textbf{\textbackslash footfullcite}}
standard \textsf{biblatex} command, modified to work properly with
\textsf{biblatex-chicago-notes}, and provided in case you find
yourself in a situation where you really need the full citation in a
footnote, but where \cmd{autocite} would print a short note or even
-\enquote{Ibid.}  This may be particularly useful if you've chosen to use all
-short notes by setting the \texttt{short} option in the arguments to
-\cmd{usepackage\{biblatex\}}, yet still feel the need for the
-occasional full citation.
+engage the ibidem mechanism.  This may be particularly useful if
+you've chosen to use all short notes by setting the \texttt{short}
+option in the arguments to \cmd{usepackage\{biblatex\}}, yet still
+feel the need for the occasional full citation.

\mybigspace This, \mymarginpar{\textbf{\textbackslash fullcite}} too,
is a standard command, and it too provides a full citation, but unlike
@@ -4797,12 +5889,12 @@
two further sets of square brackets, because with only one set it
will, as with other citation commands, be interpreted as a
\textsf{postnote}, and with two a \textsf{prenote} and a
-\textsf{postnote}.  There is a \cmd{gentext\-cites} command as well, and
+\textsf{postnote}.  There is a \cmd{gentextcites} command as well, and
for it you may need to specify
-\cmd{gentextcites[<ending>]\\()()[][]\{entry:key1\}\{entry:key2\}},
+\cmd{gentextcites[<ending>]()()[][]\\\{entry:key1\}\{entry:key2\}},
though if you don't have a \textsf{pre-} or \textsf{postnote} to the
first citation you can make do with
-\cmd{gentextcites[<ending>]()\{entry:key1\}\\\{entry:key2\}}.
+\cmd{gentextcites[<ending>]()\{entry:key1\}\{entry:key2\}}.

\mylittlespace The syntax of multiple authors' names in running text
is unpredictable.  There is currently no way to add the genitival
@@ -4816,31 +5908,40 @@
but the \texttt{genallnames} preamble and/or entry option
set to \texttt{true} will attach the ending to each key's name(s).

+\mybigspace Matthew \mymarginpar{\textbf{\textbackslash
Lundin requested a more generalized \cmd{headlesscite} macro,
suppressing the author's name in specific contexts while allowing
users not to worry about whether a particular citation needs the long
or short form, a responsibility thereby handed over to
-\textsf{biblatex's} tracking mechanisms.  This citation command
-attempts to fulfill this request.  Please note that, in the short
-form, the result will be rather like a \cmd{citetitle} command, which
-may or may not be what you want.  Note, also, that as I have provided
-only the most flexible form of the command, you'll have to wrap it in
-a \cmd{footnote} yourself.  Please see the next entry for further
+\textsf{biblatex's} tracking mechanisms.  These citation commands
+attempt to fulfill this request.  The (new) capitalized command, as
+usual, will ensure capitalization of, e.g., \enquote{ibid.}\ at the
+beginning of notes, and was made necessary by fixes to a bug
+identified by David Purton.  Please note that, in the short form, the
+result will be rather like a \cmd{citetitle} command, which may or may
+not be what you want.  Note, also, that as I have provided only the
+most flexible form of the command, you'll have to wrap it in a
+\cmd{footnote} yourself.  Please see the next entry for further
discussion of some of the needs this command might help address.

\mybigspace I \mymarginpar{\textbf{\textbackslash
-    headless-\\fullcite}} have provided this command in case you want
-to print a full citation without the author's name.  The \emph{Manual}
-(14.78, 14.88) suggests this for brevity's sake in cases where that
-name is already obvious enough from the title, and where repetition
-might seem awkward (creel:house, feydeau:farces, meredith:letters, and
-sewall:letter).  \textsf{Letter} entries --- and only such entries ---
-do this for you automatically, and of course the repetition is
-tolerated in bibliographies for the sake of alphabetization, but in
-notes this command may help achieve greater elegance, even if it isn't
-strictly necessary.  As I've provided only the most flexible form of
-the command, you'll have to wrap it in a \cmd{footnote} yourself.
+      headless-\\fullcites}}} have provided these commands in case you
+want to print a full citation without the author's name.  The
+\emph{Manual} (14.78, 14.104) suggests this for brevity's sake in
+cases where that name is already obvious enough from the title, and
+where repetition might seem awkward (creel:house, feydeau:farces,
+meredith:letters, and sewall:letter).  \textsf{Letter} entries and
+\mycolor{\textsf{standard}} entries (where the \textsf{author} is
+usually the publishing \textsf{organization}) --- and only these
+entries --- do this for you automatically, and of course the
+repetition is tolerated in bibliographies for the sake of
+alphabetization, but in notes for other entry types this command may
+help achieve greater elegance, even if it isn't strictly necessary.
+As I've provided only the most flexible form of the command, you'll
+have to wrap it in a \cmd{footnote} yourself.

\mybigspace I \mymarginpar{\textbf{\textbackslash shortcite}} have
provided this command in case, for any reason, you specifically
@@ -4849,6 +5950,13 @@
of the command, so you'll have to wrap it in a \cmd{footnote}
manually.

+\mybigspace The \colmarginpar{\textbf{\textbackslash shortcite*}}
+starred version of the command turns off page and citation tracking
+for a short note, designed particularly to prevent a
+\mycolor{\texttt{noteref}} back reference from appearing, should you
+and the code have a disagreement over just when such back references
+might be necessary.
+
\mybigspace At \mymarginpar{\textbf{\textbackslash shorthandcite}}
the request of Kenneth Pearce, I have included this command which
always prints the \textsf{shorthand}, even at the first citation of a
@@ -4856,6 +5964,30 @@
command, so you'll need to place it inside parentheses or wrap it in a
\cmd{footnote} manually.

+\mybigspace The \colmarginpar{\textbf{\textbackslash shorthandcite*}}
+starred version of the command turns off page and citation tracking
+for a \textsf{shorthand} note, designed particularly to prevent a
+\mycolor{\texttt{noteref}} back reference from appearing, should you
+and the code have a disagreement over just when such back references
+might be necessary.
+
+\mybigspace This \colmarginpar{\textbf{\textbackslash
+    shorthand-\\refcite}} command, like the next, forces the printing
+of a back reference when you are using the new package option
+\mycolor{\texttt{noteref}}, only it prints a \textsf{shorthand} note
+rather than a short note.  It's the opposite of
+\mycolor{\cmd{shorthandcite*}}.
+
+\mybigspace The \colmarginpar{\textbf{\textbackslash shortrefcite}}
+new package option \mycolor{\texttt{noteref}} provides for the
+printing of back references from short notes to their corresponding
+long notes.  \textsf{Biblatex-chicago} provides several options to
+help you control when such back references should appear, but as there
+may well be occasions when you and the code disagree, this command
+forces the printing of a short note with a back reference.  It's the
+opposite, then, of \mycolor{\cmd{shortcite*}}, which prevents such a back
+reference from appearing.
+
\mybigspace This \mymarginpar{\textbf{\textbackslash surnamecite}}
command is analogous to \cmd{headlesscite}, but whereas the latter
allows you to omit an \textsf{author's} name when that name is obvious
@@ -4864,7 +5996,7 @@
\textsf{author} have already been provided in the text.  In short
notes this falls back to the standard format, but in long notes it
simply omits the given names of the \textsf{author} and provides only
-the surname, along with the full data of the entry.  (Cf.\ 14.52.)
+the surname, along with the full data of the entry (cf.\ 14.57).

\mybigspace Norman \mymarginpar{\textbf{\textbackslash textcite}} Gray
started a discussion on
@@ -4888,7 +6020,7 @@
\cmd{textcites}, specifies that you'll get the \textsf{author's}
name(s) followed by a headless \emph{short} citation (or citations)
placed within parentheses.  Such parentheses are generally discouraged
-by the \emph{Manual} (14.33), but are nonetheless somewhat better than
+by the \emph{Manual} (14.38), but are nonetheless somewhat better than
other solutions for smoothing the syntax of sentences that include
such a citation.  I have made the citation short, i.e., \textsf{title}
only, because this again seems likely to be the least awkward solution
@@ -4913,7 +6045,7 @@
settings are, I believe, consistent with the specification, but you
can alter them in the options to \textsf{biblatex-chicago} in your
-\cmd{usepackage[style=chicago-notes]\{biblatex\}}, which gives you the
+\verb+\usepackage[style=chicago-notes]{biblatex}+, which gives you the
\textsf{biblatex} defaults unless you redefine them yourself inside
the square brackets.

@@ -4933,37 +6065,74 @@
for the long format when presenting dates, slightly shortened when
presenting date ranges.

-%\enlargethispage{-\baselineskip}
+\mylittlespace In \colmarginpar{\texttt{alltimes=12h}} entries which
+print time stamps, they will, when the stamp is part of a
+\textsf{date}, \textsf{eventdate}, or \textsf{origdate}, appear in
+12-hour format, i.e., \enquote{4:45 p.m.}  Stamps that are part of a
+\textsf{urldate} are, by default, controlled by the
+\mycolor{\texttt{urltime}} option, which is set to
+\mycolor{\texttt{24h}}.  See that option below, and

\mylittlespace The \mymarginpar{\texttt{dateabbrev=\\false}}
\emph{Manual} prefers to use full month names in the notes \&\
bibliography style.

+\mylittlespace This \colmarginpar{\texttt{datecirca=true}} option
+enables \textsf{biblatex's} enhanced \enquote{circa} date
+specification, which given a \textsf{date} like \verb+1989~+ will
+
+\mylittlespace This \colmarginpar{\texttt{dateuncertain=\\true}}
+option enables \textsf{biblatex's} enhanced \enquote{uncertain} date
+specification, which given a \textsf{date} like \verb+1989?+ will
+print [1989?].  A field like \verb+1989%+ is both \enquote{circa}
+\emph{and} \enquote{uncertain,} like so: [ca.\ 1989?].  Cf.\
+
+\mylittlespace This \colmarginpar{\texttt{datezeros=false}} ensures
+that leading zeros don't appear in date specifications.
+
\mybigspace This \mymarginpar{\texttt{ibidtracker=\\constrict}}
-enables the use of \enquote{Ibid} in notes, but only in the most
+enables the use of the ibidem mechanism in notes, but only in the most
strictly-defined circumstances.  Whenever there might be any
ambiguity, \textsf{biblatex} should default to printing a more
informative reference.  Remember also that you can use the \cmd{cite*}
command to disable this functionality in any given reference, or
indeed one of the \texttt{fullcite} commands if you need the long note
-form for any reason.
+form for any reason.  Please see section~\ref{sec:useropts} for
+options (\texttt{noibid} and \mycolor{\texttt{useibid}}) managing how
+\textsf{biblatex-chicago} presents ibidem references, as the defaults
+have changed in the 17th edition (14.34).

\mylittlespace Roger \mymarginpar{\texttt{idemtracker=\\false}} Hart
suggested that it might be helpful, despite the \emph{Manual's}
-objections (14.30), to be able to turn on \textsf{biblatex's}
+objections (14.35), to be able to turn on \textsf{biblatex's}
\texttt{idemtracker}.  This replaces, in notes only, authors' names
with the string \enquote{Idem} when a work by the same author follows
a different work by that author, two consecutive references to the
same work by the same author generating, of course, \enquote{Ibid.}
-\texttt{idemtracker=constrict}.  It works very much like the standard
-\textsf{biblatex} styles which include this option, so that you never
-get \enquote{Idem} in long notes, but only in short ones, and
-(ideally) never when the repeated name might be somewhat ambiguous.
-Also, if you wish the localized string to be appropriately gendered,
-you need to employ the \textsf{biblatex} field \textsf{gender}, on
-which see \textsf{biblatex.pdf} \xA7~2.3.3.
+Indeed, if you are going to use the \texttt{idemtracker}, you should
+also set the package option \mycolor{\texttt{useibid}} to
+\texttt{true}, so that you don't get a mix of \enquote{Idem} and the
+new 17th-edition ibidem behavior which doesn't print \enquote{Ibid.}
+setting \texttt{idemtracker=constrict,useibid=true}.  It works very
+much like the standard \textsf{biblatex} styles which include this
+option, so that you never get \enquote{Idem} in long notes, but only
+in short ones, and (ideally) never when the repeated name might be
+somewhat ambiguous.  Also, if you wish the localized string to be
+appropriately gendered, you need to employ the \textsf{biblatex} field
+\textsf{gender}, on which see \textsf{biblatex.pdf} \xA7~2.3.3.

+\mylittlespace This \colmarginpar{\texttt{labeltitle=\\true}} option
+enables \textsf{biblatex-chicago-notes} to disambiguate shortened
+citations to different sources which might otherwise be confusingly
+identical.  Though I've set it in \textsf{biblatex-chicago.sty},
+you'll need to set the \texttt{shortextrafield} option yourself in
+order for it to have any visible effect.  See the documentation of
+that option in section~\ref{sec:useropts}, below.
+
\mylittlespace This \mymarginpar{\texttt{loccittracker\\=constrict}}
allows the package to determine whether two consecutive citations of
the same source also cite the same page of that source.  In such a
@@ -4976,7 +6145,7 @@
numbers follow the recommendations of the \emph{Manual} (14.76), and
they are different from those for use in notes.  With
\textsf{biblatex} 1.6 you can no longer redefine \texttt{maxnames} and
-\texttt{minnames} in the \cmd{printbiblio\-graphy} command at the bottom
+\texttt{minnames} in the \cmd{printbibliography} command at the bottom
of your document, so \textsf{biblatex-chicago} now does this
automatically for you, though of course you can change them in your
document preamble.
@@ -4987,15 +6156,19 @@
\enquote{Ibid.}  It tracks individual pages if \LaTeX\ is in oneside
mode, or whole spreads in twoside mode.

-\mylittlespace This \mymarginpar{\texttt{related=bib}} is the
-standard \textsf{biblatex} bibliography option, but I have given it
-some extra settings and also added an entry option as well.  By
-default it enables the use of \textsf{related} functionality in the
-bibliography only, not in long notes.  You can set it either in the
-preamble or in individual entries to enable the functionality in long
-notes only (\texttt{notes}), in both notes and bibliography
-(\texttt{true}), or in neither (\texttt{false}).  Cf.\
-coolidge:speech, weed:flatiron.
+\mylittlespace This \mymarginpar{\texttt{related=bib}} is the standard
+\textsf{biblatex} bibliography option, but I have given it some extra
+settings and also added entry and type options as well.  By default it
+enables the use of \textsf{related} functionality in the bibliography
+only, not in long notes.  You can set it either in the preamble or in
+individual entries to enable the functionality in long notes only
+(\texttt{notes}), in both notes and bibliography (\texttt{true}), or
+in neither (\texttt{false}).  When you use the
+\mycolor{\texttt{commenton}}, \mycolor{\texttt{maintitle}}, or
+\texttt{reviewof} \textsf{relatedtypes}, \textsf{biblatex-chicago}
+automatically sets this option to \texttt{true} on an entry-by-entry
+basis, as these \textsf{relatedtypes} require this for proper
+functioning.  Cf.\ coolidge:speech, weed:flatiron.

\mylittlespace This \mymarginpar{\texttt{sortcase=\\false}} turns off
the sorting of uppercase and lowercase letters separately, a practice
@@ -5009,14 +6182,23 @@
(\texttt{nty}).  Please see the discussion of
\cmd{DeclareSortingTemplate} just below.

-\mylittlespace This \colmarginpar{\texttt{uniquework=\\true}} option
-enables \textsf{biblatex-chicago-notes} to disambiguate shortened
-citations to different sources which might otherwise be confusingly
-identical.  Though I've set it in \textsf{biblatex-chicago.sty},
-you'll need to set the \mycolor{\texttt{shortextrafield}} option
-yourself in order for it to have any visible effect.  See the
-documentation of that option in section~\ref{sec:useropts}, below.
+\mylittlespace If \colmarginpar{\texttt{timezones=true}} you provide a
+timezone for a time stamp, usually using one of the \textsf{timezone}
+fields, this option ensures it will be printed.

+\mylittlespace In \colmarginpar{\texttt{urltime=24h}} entries with
+\textsf{urldate} fields containing time stamps, that stamp will by
+default appear in 24-hour format, i.e., \enquote{16:45.}  Cf.\
+\mycolor{\texttt{alltimes}}, above, \mycolor{\texttt{urlstamp}} in
+
+\mylittlespace In
+\colmarginpar{\texttt{[standard]\\useeditor=false\\usenamec=false}}
+\mycolor{\textsf{standard}} entries any editors' or compilers' names
+appear after the title, according to 14.259, so these
+entry-type-specific options encode this.  You can, of course, override
+these defaults in your preamble, should you deem it necessary.
+
\mylittlespace This \mymarginpar{\texttt{usetranslator\\=true}}
enables automatic use of the \textsf{translator} at the head of
entries in the absence of an \textsf{author} or an \textsf{editor}.
@@ -5036,10 +6218,10 @@
them to your own needs and tastes.  It may be as well you know that
the \emph{Manual} does state a preference for two of the formatting
options I've implemented by default: the 3-em dash as a replacement
-for repeated names in the bibliography (14.63--67, and just below);
+for repeated names in the bibliography (14.67--71, and just below);
and the formatting of note numbers, both in the main text and at the
bottom of the page / end of the essay (superscript in the text,
-in-line in the notes; 14.19).  The code for this last formatting is
+in-line in the notes; 14.24).  The code for this last formatting is
also in \textsf{biblatex-chicago.sty}, and I've wrapped it in a test
that disables it if you are using the \textsf{memoir} class, which I
believe has its own commands for defining these parameters.  You can
@@ -5052,9 +6234,8 @@
three dashes separated by gaps.  He suggested an alternative, which
I've adopted, with a minor tweak to make the dash thicker, though you
can toy with all the parameters to find what looks right with your
-chosen font.  The default definition is:
-\cmd{renewcommand*\{\textbackslash bibname\-dash\}\{\textbackslash
-  rule[.4ex]\{3em\}\{.6pt\}\}}.
+chosen font.  The default definition is:\\
+\verb+\renewcommand*{bibnamedash}{\rule[.4ex]{3em}{.6pt}}+.

\mylittlespace At \mymarginpar{\texttt{losnotes}
\&\\\texttt{losendnotes}} the request of Kenneth Pearce, I have
@@ -5068,14 +6249,16 @@
also want to use the option \texttt{heading=none} in order to get rid
of the [oversized] default, providing your own within the
\cmd{footnote} command.)  If you use a command like
-\cmd{printbiblist\{shortjournal\}} to print a list of journal
+\verb+\printbiblist{shortjournal}+ to print a list of journal
abbreviations, you can use the \texttt{sjnotes} and
-\texttt{sjendnotes} \texttt{biben\-vironments} in exactly the same way.
+\texttt{sjendnotes} \texttt{bibenvironments} in exactly the same way.
Please see the documentation of \textsf{shorthand} and
\textsf{shortjournal} in section~\ref{sec:entryfields} above for
further options available to you for presenting and formatting these
two types of \texttt{biblist}.

+\enlargethispage{\baselineskip}
+
\mylittlespace Formerly
\mymarginpar{\cmd{Declare-}\\\texttt{Labelname}} available only to
those using \textsf{Biber}, but since version 3.0 handled by
@@ -5107,30 +6290,28 @@
\texttt{nty}.  (You can find its definition in
\textsf{chicago-notes.cbx}.)  The advantages of this scheme are,
specifically, that any entry headed by one of the supplemental name
-fields (\textsf{name[a-c]}), a \textsf{manual} entry headed by an
-\textsf{organization}, or an \textsf{article} or \textsf{review} entry
-headed by a \textsf{journaltitle} won't need a \textsf{sortkey} set.
-Further, the \texttt{use<name>=false} options will remove any name
-field from the sorting order, again reducing the need for user
-intervention.
+fields (\textsf{name[a-c]}), a \textsf{manual} or a
+\mycolor{\textsf{standard}} entry headed by an \textsf{organization},
+or an \textsf{article} or \textsf{review} entry headed by a
+\textsf{journaltitle} won't need a \textsf{sortkey} set.  Further, the
+\texttt{use<name>=false} options will remove any name field from the
+sorting order, again reducing the need for user intervention.

\subsubsection{{Pre-Set \textsf{chicago} Options}}
\label{sec:chicpreset}

-At \mymarginpar{\texttt{bookpages=\\true}} the request
-of Scot Becker, I have included this rather specialized option, which
-controls the printing of the \textsf{pages} field in \textsf{book}
-entries.  Some bibliographic managers, apparently, place the total
-page count in that field by default, and this option allows you to
-stop the printing of this information in notes and bibliography.  It
-defaults to true, which means the field is printed, but it can be set
-to false either in the preamble, for the whole document, or on a
-per-entry basis in the \textsf{options} field (though rather than use
-this latter method it would make sense to eliminate the \textsf{pages}
-field from the affected entries).
+At \mymarginpar{\texttt{bookpages=\\true}} the request of Scot Becker,
+I have included this rather specialized option, which controls the
+printing of the \textsf{pages} field in \textsf{book} entries.  Some
+bibliographic managers, apparently, place the total page count in that
+field by default, and this option allows you to stop the printing of
+this information in notes and bibliography.  It defaults to true,
+which means the field is printed, but it can be set to false either in
+the preamble, for the whole document or for specific entry types, or
+on a per-entry basis in the \textsf{options} field (though rather than
+use this latter method it would make sense to eliminate the
+\textsf{pages} field from the affected entries).

-%\enlargethispage{\baselineskip}
-
\mylittlespace This \mymarginpar{\texttt{doi=true}} option controls
whether any \textsf{doi} fields present in the .bib file will be
printed in notes and bibliography.  At the request of Daniel
@@ -5141,17 +6322,18 @@
default remains the same, however --- it defaults to true, which will
print both \textsf{doi} and \textsf{url} if both are present.  The
option can be set to \texttt{only} or to \texttt{false} either in the
-preamble, for the whole document, or on a per-entry basis in the
-\textsf{options} field.  In \textsf{online} entries, the \textsf{doi}
-field will always be printed, but the \texttt{only} switch will still
-eliminate any \textsf{url}.
+preamble, for the whole document or for specific entry types, or on a
+per-entry basis in the \textsf{options} field.  In \textsf{online}
+entries, the \textsf{doi} field will always be printed, but the
+\texttt{only} switch will still eliminate any \textsf{url}.

\mylittlespace This \mymarginpar{\texttt{eprint=true}} option controls
whether any \textsf{eprint} fields present in the .bib file will be
printed in notes and bibliography.  It defaults to true, and can be
-set to false either in the preamble, for the whole document, or on a
-per-entry basis, in the \textsf{options} field.  In \textsf{online}
-entries, the \textsf{eprint} field will always be printed.
+set to false either in the preamble, for the whole document or for
+specific entry types, or on a per-entry basis, in the \textsf{options}
+field.  In \textsf{online} entries, the \textsf{eprint} field will
+always be printed.

\mylittlespace This \mymarginpar{\texttt{isbn=true}} option controls
whether any \textsf{isan}, \textsf{isbn}, \textsf{ismn},
@@ -5158,9 +6340,10 @@
\textsf{isrn}, \textsf{issn}, and \textsf{iswc} fields present in the
.bib file will be printed in notes and bibliography.  It defaults to
true, and can be set to false either in the preamble, for the whole
-document, or on a per-entry basis, in the \textsf{options} field.
+document or for specific entry types, or on a per-entry basis, in the
+\textsf{options} field.

-\mylittlespace Once \mymarginpar{\texttt{numbermonth=\\true}} again at
+\mylittlespace Once \mymarginpar{\texttt{numbermonth\\=true}} again at
the request of Scot Becker, I have included this option, which
controls the printing of the \textsf{month} field in all the
periodical-type entries when a \textsf{number} field is also present.
@@ -5169,31 +6352,52 @@
information is available the \emph{Manual} (14.180, 14.185) prints
everything, so this option defaults to true, which means the field is
printed, but it can be set to false either in the preamble, for the
-whole document, or on a per-entry basis in the \textsf{options} field.
+whole document or for specific entry types, or on a per-entry basis in
+the \textsf{options} field.

\mylittlespace This \mymarginpar{\texttt{url=true}} option controls
whether any \textsf{url} fields present in the .bib file will be
printed in notes and bibliography.  It defaults to true, and can be
-set to false either in the preamble, for the whole document, or on a
-per-entry basis, in the \textsf{options} field.  Please note that, as
-in standard \textsf{biblatex}, the \textsf{url} field is always
-printed in \textsf{online} entries, regardless of the state of this
-option.
+set to false either in the preamble, for the whole document or for
+specific entry types, or on a per-entry basis, in the \textsf{options}
+field.  Please note that, as in standard \textsf{biblatex}, the
+\textsf{url} field is always printed in \textsf{online} entries,
+regardless of the state of this option.

+\mylittlespace This \colmarginpar{\texttt{urlstamp=true}} option
+controls whether any \textsf{urltime} fields, included as part of the
+\textsf{urldate}, will be printed in notes and bibliography.  It
+defaults to true, and can be set to false either in the preamble, for
+the whole document or for specific entry types, or on a per-entry
+basis in the \textsf{options} field.  Please note that, unlike the
+\texttt{url} option, this option \emph{does} control what is printed
+in \textsf{online} entries.
+
\mylittlespace This \mymarginpar{\texttt{includeall=\\true}} is the
-one option that rules the six preceding, either printing all the
+one option that rules the seven preceding, either printing all the
fields under consideration --- the default --- or excluding all of
them.  It is set to \texttt{true} in \textsf{chicago-notes.cbx}, but
-you can change it either in the preamble for the whole document or,
-for specific fields, in the \textsf{options} field of individual
-entries.  The rationale for all of these options is the availability
-of bibliographic managers that helpfully present as much data as
-possible, in every entry, some of which may not be felt to be entirely
-necessary.  Setting \texttt{includeall} to \texttt{true} probably
-works just fine for those compiling their .bib databases by hand, but
-others may find that some automatic pruning helps clear things up, at
-least to a first approximation.  Some per-entry work afterward may
-then polish up the details.
+you can change it either in the preamble for the whole document or for
+specific entry types, or in the \textsf{options} field of individual
+entries.  The seven individual options above are similarly available
+in the same places, for finer-grained control.  The rationale for all
+of these options is the availability of bibliographic managers that
+helpfully present as much data as possible, in every entry, some of
+which may not be felt to be entirely necessary.  Setting
+\texttt{includeall} to \texttt{true} probably works just fine for
+those compiling their .bib databases by hand, but others may find that
+some automatic pruning helps clear things up, at least to a first
+approximation.  Some per-type or per-entry work afterward may then
+polish up the details.  If you find that you need control over fields
+that aren't included among these options, I have provided the
+\mycolor{\cmd{suppressbibfield}} command for your preamble, as
+suggested by Jan David Hauck.  It is in fact a user interface to the
+source mapping feature of \textsf{biblatex}, and it is something of a
+nuclear option, preventing fields from even appearing in the .bbl file
+generated by \textsf{biber} from your .bib database.  See the
+\mycolor{\cmd{suppressbibfield}} command in
+section~\ref{sec:formatcommands} and the source mapping docs in
+\textsf{biblatex.pdf} \S~4.5.3.

of Roger Hart, I have included this option, which controls the
@@ -5203,7 +6407,7 @@
\textsf{options} field.

\mylittlespace According \mymarginpar{\texttt{bookseries=\\true}} to
-the \emph{Manual} (14.128), the \textsf{series} field in book-like
+the \emph{Manual} (14.123), the \textsf{series} field in book-like
entries \enquote{may be omitted to save space (especially in a
footnote).}  This option allows you to control the printing of that
field in long notes.  It defaults to true, and can be set to false
@@ -5265,15 +6469,26 @@
\texttt{longcrossref}, below, and also the documentation of
\textsf{crossref} in section~\ref{sec:entryfields}.

+\mylittlespace The \colmarginpar{\texttt{compressyears\\=true}}
+\emph{Manual} has long recommended (9.64, 14.117, 14.144), as a
+space-saving measure, the compression of year ranges when presenting
+dates.  I have, finally, implemented this in the current release, and
+have made it the default, which you can change in your document
+preamble.  Please note that the rules for compressing years are
+different from those for compressing other numbers (e.g., page
+numbers), and also that the compression code is in
+\textsf{biblatex-chicago.sty}, which will have to be loaded for this
+option to make any difference.  Cf.\ table~\ref{ad:date:extras}.
+
\mylittlespace Roger
requested a way to control the punctuation printed before the
\textsf{maintitleaddon} fields.  By default, this is
-occurrences in notes and for nearly all \textsf{book-} and
+in notes and for nearly all \textsf{book-} and
before most \textsf{titleaddons} in the bibliography.  If the
punctuation printed isn't correct for your needs, you can set the
relevant option either in the preamble or in individual entries.
@@ -5284,10 +6499,10 @@
\setlength{\parskip}{-4pt}
\item[\qquad none] = no punctuation at all
\end{description}

If you need something a little more exotic, you can directly
@@ -5299,6 +6514,17 @@
relevant option to \texttt{none} in your entry and then include the
punctuation in the \textsf{titleaddon} field itself.

+\mylittlespace Constanza Cordoni \colmarginpar{\texttt{dashed=true}}
+has requested a way to turn off the 3-em dash for replacing repeated
+names in the bibliography, and the \emph{Manual} admits that some
+publishers prefer this, as the dash can carry with it certain
+inconveniences, especially for electronic formats (14.67).  Some of
+\textsf{biblatex's} standard styles have a \texttt{dashed} option, so
+for compatibility purposes I've provided the same.  By default, I have
+set it to print the name dash, but you can set
+\mycolor{\texttt{dashed=false}} in your preamble to repeat names
+
\mylittlespace If \mymarginpar{\texttt{hidevolumes=\\true}} both a
\textsf{volume} and a \textsf{volumes} field are present, as may occur
particularly in cross-referenced entries, then
@@ -5311,19 +6537,20 @@
\texttt{false} either in the preamble or in the \textsf{options} field
of your entry to have it appear after the \textsf{maintitle}.

-\mylittlespace This \mymarginpar{\texttt{longcrossref=\\false}} is
-the second option, requested by Bertold Schweitzer, for controlling
+\mylittlespace This \mymarginpar{\texttt{longcrossref=\\false}} is the
+second option, requested by Bertold Schweitzer, for controlling
whether and where \textsf{biblatex-chicago} will print abbreviated
references when you cite more than one part of a given collection or
series.  It controls the settings for the entry types more-or-less
authorized by the \emph{Manual}, i.e., \textsf{inbook},
-\textsf{incollection}, \textsf{inproceedings}, and \textsf{letter}.
-The mechanism itself is enabled by multiple \textsf{crossref} or
-\textsf{xref} references to the same parent, whether that be, e.g., a
-\textsf{collection}, an \textsf{mvcollection}, a \textsf{proceedings},
-or an \textsf{mvproceedings} entry.  Given these multiple cross
-references, the presentation in the reference apparatus will be
-governed by the following options:
+\textsf{incollection}, \textsf{inproceedings}, \textsf{letter}, and
+\mycolor{\textsf{review}}.  The mechanism itself is enabled by
+multiple \textsf{crossref} or \textsf{xref} references to the same
+parent, whether that be, e.g., a \textsf{collection}, an
+\textsf{mvcollection}, a \textsf{proceedings}, or an
+\textsf{mvproceedings} entry.  Given these multiple cross references,
+the presentation in the reference apparatus will be governed by the
+following options:

\begin{description}
\item[\qquad false:] This is the default.  If you use
@@ -5350,6 +6577,20 @@
above, and also the documentation of \textsf{crossref} in
section~\ref{sec:entryfields}.

+\mylittlespace This \colmarginpar{\texttt{nodates=true}} option means
+that \textsf{biblatex-chicago} automatically provides
+\verb+\bibstring{nodate}+ in any \enquote{circa} or
+\enquote{uncertain} date specification where the user has also turned
+off the printing of brackets around the date using the
+\mycolor{\texttt{nodatebrackets}} or \mycolor{\texttt{noyearbrackets}}
+options (section~\ref{sec:useropts}; 14.145).  If you set
+\texttt{nodates=false} either in your preamble (for global coverage or
+for specific entry types) or in individual entries then the package
+will simply print the unbracketed date specification in this context.
+See table~\ref{ad:date:extras}, below.  (The bibstring expands to
+\enquote{\texttt{n.d.}} in English; please note that this option works
+quite differently in the author-date styles.)
+
\mylittlespace This
\mymarginpar{\texttt{shorthand\\punct\\=space}}
option controls the punctuation that appears before the first
@@ -5364,36 +6605,43 @@
\setlength{\parskip}{-4pt}
\item[\qquad none] = no punctuation at all
\end{description}

You can, in emergencies, directly
-\cmd{renewcommand\{\cmd{shorthandpunct}\}} in the pream\-ble, but it
-might be easier to use the \texttt{none} option to
-\texttt{shorthandpunct} and hand-craft solutions inside the
-\textsf{shorthandintro} fields of individual entries.
+\verb+\renewcommand{\shorthandpunct}+ in the pream\-ble, but it might
+be easier to use the \texttt{none} option to \texttt{shorthandpunct}
+and hand-craft solutions inside the \textsf{shorthandintro} fields of
+individual entries.

-\mylittlespace As \mymarginpar{\texttt{usecompiler=\\true}}
-\textsf{biblatex} automatically includes a \texttt{usenamec} option as
-standard, the Chicago-specific option \texttt{usecompiler} is now
-\texttt{usenamec}, which works much better across the board.
-
\subsubsection{Style Options -- Preamble}
\label{sec:useropts}

These are parts of the specification that not everyone will wish to
-enable.  All except the fourth can be used even if you load the
-package in the old way via a call to \textsf{biblatex}, but most users
-can just place the appropriate string(s) in the options to the
+enable.  All except the fifth and eighth can be used even if you load
+the package in the old way via a call to \textsf{biblatex}, but most
+users can just place the appropriate string(s) in the options to the
\cmd{usepackage} \texttt{\{biblatex-chicago\}} call in your preamble.

+\mylittlespace \textsf{Biblatex-chicago}
+\colmarginpar{\texttt{alwaysrange}} now implements \textsf{biblatex's}
+enhanced date specifications, one part of which is the presentation of
+decades and centuries not as year ranges but as localized strings like
+\enquote{19th c.} or \enquote{1970s.}  The
+\mycolor{\texttt{alwaysrange}} option set to \texttt{true}, either in
+your preamble or in individual entries, simply tells the package to
+present the year range instead.  This allows you to use the efficient
+enhanced notations in the \textsf{date} field (\verb+{18XX}+ or
+\verb+{197X}+) without the localized strings appearing, should you
+require it.  The two options \mycolor{\texttt{centuryrange}} and
+\mycolor{\texttt{decaderange}} limit the same effect to centuries and
+
\mylittlespace At \mymarginpar{\texttt{annotation}} the request of
Emil Salim, I included in \textsf{biblatex-chicago} the ability to
produce annotated bibliographies.  If you turn this option on then the
@@ -5400,22 +6648,59 @@
contents of your \textsf{annotation} (or \textsf{annote}) field will
be printed after the bibliographical reference.  (You can also use
external files to store annotations -- please see
-\textsf{biblatex.pdf} \xA7~3.11.8 for details on how to do this.)  This
+\textsf{biblatex.pdf} \xA7~3.13.8 for details on how to do this.)  This
functionality is currently in a beta state, so before you use it
please have a look at the documentation for the \textsf{annotation}
field, on page~\pageref{sec:annote} above.

+\mylittlespace As \colmarginpar{\texttt{blogurl}} a convenience
+feature, this option, available only in the preamble, allows
+\textsf{review} entries to inherit a \textsf{url} from
+\textsf{article} entries.  The main use, as the name suggests, is when
+you want to provide the same \textsf{url} for a blog comment as you
+have for a blog post.  You'll need an extra \LaTeX - \textsf{Biber} -
+\LaTeX\ run to make sure any changes to this option take effect.
+
+\mylittlespace This \colmarginpar{\texttt{centuryrange}} option works
+just like \mycolor{\texttt{alwaysrange}}, above, but only affects
+
+\mylittlespace The \colmarginpar{\texttt{cmsbreakurl}} \emph{Manual}
+gives fairly specific instructions about breaking URLs across lines
+(14.18), so I have attempted to implement them by tweaking
+\textsf{biblatex's} default settings, which are found in
+\textsf{biblatex.def}.  In truth, I haven't succeeded in getting
+\textsf{biblatex} flawlessly to follow all of the \emph{Manual's}
+instructions, nor do the changes I have made work well in all
+circumstances, being particularly unsightly if you happen to be using
+the \textsf{ragged2e} package.  For these reasons, I have made my
+changes dependent on a package option, \mycolor{\texttt{cmsbreakurl}},
+which you can set in your preamble.  I have placed all of this code in
+\textsf{biblatex-chicago.sty}, so if you load the package with a call
+to \textsf{biblatex} instead, then URL line breaking will revert to
+the \textsf{biblatex} defaults.  See
+\href{file:cms-notes-sample.pdf}{\textsf{cms-notes-sample.pdf}} for a
+lot of examples of what URLs look like when the option is set, and
+
\mylittlespace When \mymarginpar{\texttt{compresspages}} set to
\texttt{true}, any page ranges in your .bib file or in the
\textsf{postnote} field of your citation commands will be compressed
-in accordance with the \emph{Manual's} specifications (9.60).
+in accordance with the \emph{Manual's} specifications (9.61).
Something like 321-{-}328 in your .bib file would become 321--28 in
your document.  See the \textsf{pages} field in
-section~\ref{sec:entryfields}, above.
+section~\ref{sec:entryfields}, above.  Please note that the code for
+this is in \textsf{biblatex-chicago.sty}, so if you load the package
+with a call to \textsf{biblatex} instead then you'll get the default
+\textsf{biblatex} compression style.

+just like \mycolor{\texttt{alwaysrange}}, above, but only affects
+
\mylittlespace The \mymarginpar{\texttt{delayvolume}} presentation of
\textsf{volume} information in the notes \&\ bibliography style is
-complicated (\emph{Manual}, 14.121--27).  Depending on entry type and
+complicated (\emph{Manual}, 14.116--22).  Depending on entry type and
on the presence or absence of a \textsf{booktitle} or a
\textsf{maintitle}, \textsf{volume} data will be presented, in the
bibliography, either before a \textsf{maintitle} or after a
@@ -5433,7 +6718,7 @@
\textsf{maintitle}.  Cf.\ also \cmd{postvolpunct}, below.

\mylittlespace Although \mymarginpar{\texttt{footmarkoff}} the
-\emph{Manual} (14.19) recommends specific formatting for footnote (and
+\emph{Manual} (14.24) recommends specific formatting for footnote (and
endnote) marks, i.e., superscript in the text and in-line in foot- or
endnotes, Charles Schaum has brought it to my attention that not all
publishers follow this practice, even when requiring Chicago style.  I
@@ -5478,7 +6763,7 @@
section~\ref{sec:entryfields}, above.

\mylittlespace The \mymarginpar{\texttt{juniorcomma}} \emph{Manual}
-(6.47) states that \enquote{commas are not required around \emph{Jr.}\
+(6.43) states that \enquote{commas are not required with \emph{Jr.}\
and \emph{Sr.},} so by default \textsf{biblatex-chicago} has
followed standard \textsf{biblatex} in using a simple space in names
like \enquote{John Doe Jr.}  Charles Schaum has pointed out that
@@ -5502,21 +6787,49 @@
\textsf{biblatex-chicago.sty} simpler for the moment I have
reimplemented it there, from whence it is merely passed on to
\textsf{biblatex}.  If you load the Chicago style with
-\cmd{usepackage\{bibla\-tex-chicago\}}, then the option should simply
+\verb+\usepackage{biblatex-chicago}+, then the option should simply
read \texttt{natbib}, rather than \texttt{natbib=true}.  The shorter
form also works if you load the style using
-\cmd{usepackage[style=chicago\-notes]\{biblatex\}}, so I hope this
+\cmd{usepackage[style=chicago-notes]\\\{biblatex\}}, so I hope this
requirement isn't too onerous.

-\mylittlespace At \mymarginpar{\texttt{noibid}} the request of an
+\mylittlespace When \colmarginpar{\texttt{nodatebrackets}\\
+  \texttt{noyearbrackets}} you use \textsf{biblatex's} enhanced date
+specifications to present an uncertain date (\verb+{1956?}+), a
+\enquote{circa} date (\verb+{1956~}+), or one that is both at the same
+time (\verb+{1956%}+), the date that by default will appear in your
+documents will have square brackets around it.  This accords with the
+\emph{Manual's} instructions concerning such dates (14.145), but that
+section also includes an alternative form, where the guessed at date
+appears, without brackets, after the \verb+\bibstring{nodate}+, e.g.,
+\enquote{\texttt{n.d., ca.\ 1750.}}  These two package options, which
+may appear in the preamble either for the whole document or for
+specific entry types, or in individual entries, allow you to control
+when these brackets will appear, while the \mycolor{\texttt{nodates}}
+option, set to \texttt{true} by default, decides whether to print
+\verb+\bibstring{nodate}+ before the date.  In truth, users of the
+notes \&\ bibliography style will probably only ever need
+\mycolor{\texttt{nodatebrackets}}, which controls most of the dates
+that will appear in your documents, with the exception of dates in
+some \textsf{article}, \textsf{review}, and \textsf{periodical}
+entries without an \textsf{entrysubtype}, which are governed by
+\mycolor{\texttt{noyearbrackets}}.  (The distribution is different in
+the author-date styles, so it's impossible to do without both
+
+\mylittlespace At \colmarginpar{\texttt{noibid}} the request of an
early tester, I have included this option to allow you globally to
-turn off the \texttt{ibidem} mechanism that
+turn off the \emph{ibidem} mechanism that
\textsf{biblatex-chicago-notes} uses by default.  Some publishers, it
-would appear, require this.  Setting this option will mean that all
-possible instances of \emph{ibid.}\ will be replaced by the short note
-form.  For more fine-grained control of individual citations you'll
-probably want to use specialized citation commands, instead.  See
-section \ref{sec:citecommands}.
+would appear, require this.  Setting this option will mean that
+instead of the \emph{ibidem} mechanism you'll get the short note form.
+Please note that the 17th edition no longer recommends the use of
+\enquote{\emph{ibid.}}\ at all (14.34), so depending on the state of
+the \mycolor{\texttt{useibid}} option, below, what you'll be turning
+off may well no longer be the appearance of \emph{ibid.}\ itself.  For
+more fine-grained control of individual citations you'll probably want
+to use specialized citation commands, instead.  See section
+\ref{sec:citecommands}.

\mylittlespace As \mymarginpar{\texttt{omitxrefdate}} part of the
abbreviated cross-referencing functionality for \textsf{book},
@@ -5536,7 +6849,7 @@
\textsf{date} specification as an ordinal number: 26th March 2017.
The new package default prints 26 March 2017, which is more in keeping
both with standard British usage and with the recommendations of the
-\emph{Manual} (9.36).  The option is available only in the preamble.
+\emph{Manual} (6.38).  The option is available only in the preamble.

\mylittlespace Several
\mymarginpar{\texttt{postnotepunct}\\(experimental)} users, most
@@ -5557,11 +6870,22 @@
Note also that the option only affects the \textsf{postnote} field of
citation commands, not the \textsf{pages} field in your .bib file.

-\enlargethispage{-\baselineskip}
+\mylittlespace This \colmarginpar{\texttt{seriesabbrev}} option
+controls the printing of the \mycolor{\textsf{shortseries}} field in
+place of the \textsf{series} field in book-like entries in notes and
+bibliography.  It is \texttt{false} by default, so as shipped
+\textsf{biblatex-chicago-notes} will silently ignore such fields, but
+you can set it, either in the preamble for the whole document or for
+specific entry types, or in individual entries, to one of three other
+values: \texttt{true} prints the abbreviated form in notes and
+bibliography, \texttt{notes} in notes only, and \texttt{bib} in the
+bibliography only.  For more details, see the documentation of
+\mycolor{\textsf{shortseries}} in section~\ref{sec:entryfields},
+above.

\mylittlespace This \mymarginpar{\texttt{short}} option means that
your text will only use the short note form, even in the first
-citation of a particular work.  The \emph{Manual} (14.14) recommends
+citation of a particular work.  The \emph{Manual} (14.19) recommends
this space-saving format only when you provide a \emph{full}
bibliography, though even with such a bibliography you may feel it
easier for your readers to present long first citations.  If you do
@@ -5571,33 +6895,41 @@
bibliography is not complete, then you should not use this option.

\mylittlespace N.\
-Andrew\colmarginpar{\texttt{shortextra-\\field\\shortextra-\\format\\shortextra-\\punct}}
+Andrew\mymarginpar{\texttt{shortextra-\\field\\shortextra-\\format\\shortextra-\\punct}}
Walsh has remarked that it is quite possible for documents to cite
works that, though perfectly distinguishable in their long form, end
up looking identical in short notes; multiple performances of the same
work by the same artist, for example, might end up producing such a
-situation.  While the use of a \textsf{shorthand} field could provide
-some sort of remedy, he requested a way to disambiguate short notes by
-adding a user-configurable field to the note, thereby keeping it both
-short and unique without the need to consult a list of shorthands.
-The \emph{Manual} (15.28) itself provides just such a mechanism in the
+situation.  (In \textsf{online} and \textsf{review} entries using the
+\mycolor{\texttt{commenton}} \textsf{relatedtype} this situation is so
+endemic that I've set a default method of disambiguating short notes
+there, though you can still override it with the following options.
+See section~\ref{sec:related}, above.)  While the use of a
+\textsf{shorthand} field could provide some sort of remedy, he
+requested a way to disambiguate short notes by adding a
+user-configurable field to the note, thereby keeping it both short and
+unique without the need to consult a list of shorthands.  The
+\emph{Manual} (15.29) itself provides just such a mechanism in the
author-date specification, so I've added one to the notes \&\
bibliography style, as well.  It consists of the standard
-\textsf{biblatex} option \texttt{uniquework}, now set to \texttt{true}
+\textsf{biblatex} option \texttt{labeltitle}, now set to \texttt{true}
by default, along with three package options for the user to
configure.  All three of these options are settable for the whole
document, for individual entries, or for individual entry types.

-\mylittlespace The first is \mycolor{\texttt{shortextrafield}}, which
+\mylittlespace The first is \texttt{shortextrafield}, which
\emph{must} be set in order for the mechanism to print anything at
all.  You should set this option to the name of the field you wish to
be printed in addition to the \textsf{author} and \textsf{labeltitle}.
-By default, it will be printed after the latter, separated from it by
-a comma.  You can manually define this punctuation by setting the
-\mycolor{\texttt{shortextrapunct}} option to one of \texttt{none,
-  space, comma, period, colon,} or \texttt{semicolon}.  You can also
-enclose the extra field in parentheses or square brackets by setting
-the \mycolor{\texttt{shortextraformat}} option to \texttt{parens} or
+(Possibilities include, but are not limited to, the 4 \textsf{*date}
+fields and the 4 \textsf{*time} fields, the latter of which will print
+the appropriate \textsf{*date} and the \textsf{*time}.)  By default,
+it will be printed after the latter, separated from it by a comma.
+You can manually define this punctuation by setting the
+\texttt{shortextrapunct} option to one of \texttt{none, space, comma,
+  period, colon,} or \texttt{semicolon}.  You can also enclose the
+extra field in parentheses or square brackets by setting the
+\texttt{shortextraformat} option to \texttt{parens} or
\texttt{brackets}.

\mylittlespace User \mymarginpar{\texttt{shorthand-\\first}} laudecir
@@ -5616,12 +6948,14 @@
section~\ref{sec:entryfields} above for information on further options
available to you for presenting and formatting the list of shorthands.

+\enlargethispage{\baselineskip}
+
\mylittlespace Chris Sparks \mymarginpar{\texttt{shorthandibid}}
pointed out that \textsf{biblatex-chicago-notes} would never use
\emph{ibid.}\ in the case of entries containing a \textsf{shorthand}
field, but rather that consecutive references to such an entry
continued to provide the shorthand, instead.  The \emph{Manual} isn't,
-as far as I can tell, completely clear on this question.  In 14.258,
+as far as I can tell, completely clear on this question.  In 14.244,
discussing references to works from classical antiquity, it states
that \enquote{when abbreviations are used, these rather than
\emph{ibid.}\ should be used in succeeding references to the same
@@ -5632,7 +6966,7 @@
though the default behavior remains the same as it always has.

\mylittlespace This \mymarginpar{\texttt{strict}} still-experimental
-option attempts to follow the \emph{Manual}'s recommendations (14.36)
+option attempts to follow the \emph{Manual}'s recommendations (14.41)
for formatting footnotes on the page, using no rule between them and
the main text unless there is a run-on note, in which case a short
rule intervenes to emphasize this continuation.  I haven't tested this
@@ -5647,6 +6981,16 @@
\texttt{false} either in the preamble or in individual entries, but
please note that it does not apply to \textsf{online} entries.

+\mylittlespace In \colmarginpar{\texttt{useibid}} a change to previous
+recommendations, the 17th edition of the \emph{Manual}
+\enquote{discourages the use of \emph{ibid.,}}\ preferring instead a
+shortened reference with only the author's name (14.34).
+\textsf{Biblatex-chicago} now implements these recommendations by
+default, including the repetition of page references even when they're
+exactly the same as the previous note.  If you prefer to continue
+using \emph{ibid.}, then set \mycolor{\texttt{useibid=true}} in your
+document preamble and you'll get the traditional behavior.
+
\mylittlespace Stefan \mymarginpar{\texttt{xrefurl}} Bj\xF6rk pointed
out that when, using the \texttt{longcrossref} or
\texttt{booklongxref} options, you turn on the automatic abbreviation
@@ -5658,6 +7002,851 @@
individual entries will allow the \textsf{url}, \textsf{doi}, or
\textsf{eprint} field to appear even in these abbreviated references.

+\subsubsection{Back References: The \mycolor{\texttt{noteref}} Option}
+\label{sec:noteref}
+
+\textsf{Biblatex} has always provided the \texttt{backref} option,
+which prints, in the bibliography, those pages on which individual
+works have been cited.  The \emph{Manual} (14.31) recommends another,
+related system, which involves, at the end of short notes,
+cross-referen\-ces to the note where the reader can find the full,
+long citation of the same source, \enquote{especially in the absence
+  of a full bibliography.}  The general idea is that, where a short
+note is \enquote{far} from the long citation, a back reference to that
+long note may prove \enquote{helpful.}  The recommended format is
+something like this: \texttt{(see chap.\ 1, n.\ 4)}.  The previous
+release of \textsf{biblatex-chicago} provided something similar only
+for certain subsets of material from the \emph{Bluebook} guidelines
+for legal citations.  That provision is very basic and has a different
+rationale, so it remains both unaltered and entirely separate.  With
+this release, in the notes \&\ bibliography style only, I have
+provided Chicago-style back references for all other entry types,
+enabled through the new \mycolor{\texttt{noteref}} preamble option.
+(Cf.\ \href{file:cms-noteref-demo.pdf}{\textsf{cms-noteref-demo.pdf}}
+for a brief introduction.)
+
+\mylittlespace Before embarking on a description of this new option,
+and its many sub-options, I would like to point out that
+\textsf{biblatex} provides a number of mechanisms designed to help
+\textsf{biblatex-chicago hyperref} interface, so electronic documents
+long notes or, in a document with all short notes, from such notes to
+bibliography entries.  (The \mycolor{\textsf{noteref}} mechanism
+cooperates well with \textsf{hyperref}, and therefore can add another
+offers the \texttt{refsection} and \texttt{citereset} preamble
+options, which allow you to choose how its citation trackers behave.
+Using these you can, for example, always have a long note appear for a
+given source at its first appearance in a chapter or a section,
+something which the \emph{Manual} recommends in any case, and which
+may mean that your short notes are never too \enquote{far} from a
+longer citation.  (See \textsf{biblatex.pdf, \S~3.1.2.1}.)
+
+\mylittlespace All \colmarginpar{\texttt{noteref}} the same, sometimes
+chapters or sections can get rather long, or a too-frequent
+reappearance of the long form may not be optimal for your work, so in
+such situations the \texttt{noteref} option may well prove useful.
+Its general principle is this: if a short note appears on the same
+page as its corresponding long note, or on the same double-page spread
+for \texttt{twoside} mode, then nothing will appear.  Similarly, if a
+short note appears on the same page or double-page spread as a
+previous short citation of the same source which \emph{does} have a
+\texttt{noteref}, then this subsequent short citation will once again
+\emph{not} present any \texttt{noteref}.  (This behavior is
+configurable --- please see below.)  If a back reference is to be
+printed, then the value of the \texttt{noteref} option determines what
+it will look like.  Its six possible values are:
+
+\begin{description}
+\item[none:] This is the default, and will always produce a back
+  reference like this: (see n.~1).  It may well be useful when you are
+  using the \texttt{citereset} or \texttt{refsection} options and know
+  that any short note will always be in the same chapter or section of
+  the text as the full reference to which it points.
+\item[page:] This will always produce a back reference like this: (see
+  p.\ 1, n.\ 1).  It can be a tidy way of directing the reader, as
+  page numbers are usually simpler to track than sections or chapters.
+  It's also a good setting if you've set the \LaTeX\ \texttt{secnumdepth}
+  counter so that sections aren't numbered.
+\item[chapter:] This is the example provided by the \emph{Manual}, and
+  as implemented here it produces two different sorts of back
+  reference.  If the short note is in the \emph{same} chapter as the
+  long note to which it points, then by default it will only mention
+  the note number, as with the \texttt{none} switch, above.  If the
+  long reference is in a different chapter, then it prints like so:
+  (see chap.\ 1, n.\ 4).  All of the options that name an organizing
+  division of the text work the same way in footnotes, i.e., only when
+  the short note and the long note to which it refers are in different
+  \texttt{parts, chapters, sections, or subsections} will the actual
+  division type appear in the \texttt{noteref}.  If you want the
+  longer form in \emph{all} of your \texttt{noterefs}, you can set
+  \colmarginpar{\texttt{fullnoterefs}} the \textsf{biblatex-chicago}
+  the package.  In endnotes, depending on which options you've chosen
+  for presenting them, you may well never get the short version of the
+  back reference.  Please see the details starting on
+  page~\pageref{sec:endnoterefs}, below.
+\item[section:] This key is particularly intended for documents, like
+  the standard \LaTeX\ \textsf{article} class, which don't offer
+  chapters, but rather start their divisions at the section level, but
+  it's perfectly usable even in a document that also uses chapters.
+  Assuming the short note and its long antecedent are in different
+  sections, the \texttt{noteref} will look like so: w/o chapter (see
+  \S~2, n.\ 6), w/\ chapter (see \S~1.2, n.\ 6).
+\item[subsection:] I'm not sure there's any need for this key, but I
+  include it for the sake of completeness.  It's usable in documents
+  both with and without chapter divisions, and assuming the short note
+  and its long antecedent are in different subsections the
+  \textsf{noteref} will look like so: w/o chapter (see \S~3.2, n.\ 5),
+  w/\ chapter (see \S~2.3.2, n.\ 5).
+\item[part:] This is, I suspect, even less likely to be useful than
+  \texttt{subsection}, but assuming the short note and its long
+  antecedent are in different parts the back reference will look like
+  so: (see pt.\ I, n.\ 4).  You'll need to be careful that note
+  numbering is continuous across chapters for this to work correctly,
+  otherwise the plain note number might well be ambiguous.  Also, if
+  you'd like the part number not to be roman, you can try putting this
+\end{description}}
+
+Several comments are in order, before moving on to the onerous
+details.  In case it's not already clear, the \texttt{noteref} option
+is only relevant if your document includes full notes, that is, if you
+aren't using the \texttt{short} option.  Even in documents that use
+long notes, it can occasionally happen that the \texttt{noteref} code
+won't be able to find a full citation of a particular source.  In this
+case, no back reference will appear, and you will find a warning in
+your\ .log file informing you about it.  (If you combine
+\texttt{short} and \texttt{noteref}, you'll see a lot of such
+warnings.)  It can happen that even the first citation of a particular
+source appears in a somewhat abbreviated form, as when multiple
+contributions to the same \textsf{collection} are present in your
+reference apparatus.  The \texttt{noteref} will point to this
+abbreviated first citation all the same, given that it is at least
+\texttt{noteref} from a \textsf{collection} may well point to the long
+citation of an essay from that collection, as that long citation will
+contain all the details of the collection, too.  I hope this doesn't
+prove too surprising.  I should also clarify that all of the strings
+in the \texttt{noterefs} as printed above are localized, so should
+idiomatically.  Finally, the code assumes that the standard \LaTeX\
+counters for parts, chapters, and sections are available, which I
+believe is almost universally the case even for classes and styles
+that redefine a lot of the relevant functionality, but I confess I
+haven't tested \texttt{noteref} at all extensively against the
+possibilities offered by CTAN, so please do let me know if something
+breaks for you.
+
+\mylittlespace I \colmarginpar{\texttt{noterefinterval}} mentioned
+above that the gap between appearances of a \texttt{noteref} for a
+along with four new citation commands which I discuss below.  The
+\mycolor{\texttt{noterefinterval}} preamble option allows you to
+define the number of references that must have intervened since the
+last \texttt{noteref} before another to the same source will appear.
+If you judge that your readers don't need a pointer on every new page
+but only after a certain number of other citations have passed, you
+can set this to a number higher than zero (the default).  You can't,
+currently, use this mechanism to make new pointers appear on the same
+page as previous ones, but you can spread them out if they appear
+too frequently for your tastes.  Also, the counter that this option
+uses is \texttt{instcount}, which will be incremented not only by new
+references but also, e.g., by uses of the \textsf{related}
+functionality to extract data from other entries.  A value of
+\texttt{15} may not delay a reappearance for exactly that many notes,
+so you will need to experiment a little to find a value that suits
+
+\mylittlespace If \colmarginpar{\cmd{shortrefcite}\\
+  \cmd{shorthand-}\\\texttt{refcite}\\ \cmd{shortcite*}\\
+  \cmd{shorthandcite*}} you require more fine-grained control over the
+spacing between \texttt{noterefs}, or indeed if you want them to
+appear more frequently than the previous mechanisms allow, then these
+new citation commands will allow you to do so, though perhaps without
+maximum convenience.  The first two commands present, respectively,
+short notes and \textsf{shorthand} notes where the \texttt{noteref}
+will absolutely be printed (unless, of course, no full citation can be
+found).  The second two commands prevent the printing of the
+\texttt{noteref}, no matter where the resulting note appears.  All of
+them will need enclosing in a \cmd{footnote} command if you want them
+to appear in one, as I've provided only the most general form of each.
+I suppose, finally, that it would be safest to introduce these
+commands into your documents at quite a late stage in their
+preparation.
+
+\subsubsection*{Zero Sections}
+\label{sec:zero}
+
+The \LaTeX\ sectioning counters all start from zero, so if you put a
+note into material occurring \emph{before} the first \cmd{part},
+\cmd{chapter}, \cmd{section}, or \cmd{subsection} command then any
+back reference to this citation will, by default, present that zero
+(or zeros).  This may, in fact, be exactly what you want, in which
+case you can ignore the following options.  If you don't want a zero
+to appear in your \texttt{noterefs}, you can either make sure no
+citations occur in contexts that will produce them, or you can use a
+combination of the next three options to hide them.
+
+\mylittlespace This \colmarginpar{\texttt{noterefintro}} option is
+special in that it handles only zeros that occur in the \emph{first}
+position in a sectioning identifier, e.g., \S~0.x.x or chap.~0.  It's
+possible that this zero represents some sort of introductory material
+before, e.g., the numbered chapters appear.  If you say
+\texttt{noterefintro=introduction}, then instead of (see chap.~0,
+n.~1), you'll have (see intro., n.~1).  If the value of the option is
+a \cmd{bibstring} known to \textsf{biblatex}, then it will appear in
+localized, and possibly abbreviated, form, as above.  If the section
+title you want isn't a known \cmd{bibstring}, you can either define a
+new one for your language in your preamble, or you can just set the
+option to whatever it is you want to appear in such \texttt{noterefs}.
+Both will work, particularly because you don't need to worry too much
+about capitalization because the word always appears after the
+\verb+\bibstring{see}+.
+
+\enlargethispage{\baselineskip}
+
+\mylittlespace Now, it's perfectly possible for an introduction to
+have numbered sections of its own, so a citation there may produce a
+back reference like \S~0.1 or \S~0.1.0.  The rules are: 1.\ any back
+reference which is all zeros will just print the \texttt{noterefintro}
+string alone, assuming you've provided one; 2.\ any back reference that
+has the zero \emph{only} in the first place will print something like
+(see intro., \S~1, n.~1); 3.\ a back reference of the form 0.x.0 or
+0.0.x --- this can only occur if \texttt{noteref=subsection} and the
+document class provides a \cmd{chapter} command --- such a reference
+will either print the zero after the \texttt{noterefintro} string, or
+you can use the \texttt{pagezeros} option, to which I turn.
+
+\mylittlespace This \colmarginpar{\texttt{pagezeros}} boolean option
+deals with the problem of zero sections by changing such
+back references, and only such back references, to behave as though
+\texttt{noteref=page}.  In the absence of a \textsf{noterefintro}
+\emph{all} such zero citations will be so treated, but if both options
+are set then zero sections with the zero in the first position of the
+identifier will fall first under the jurisdiction of the
+\texttt{noterefintro} option, only then turning to \texttt{pagezeros}
+if there's a zero remaining that hasn't yet been eliminated by the
+first option's rules.  Some examples:
+\begin{verse}
+  \textbf{Without noterefintro:}\\
+  Any zero ---> (see p.~3, n.~1)\\
+  No zero ---> (see \S~1.2.3, n.~1)
+
+  \textbf{With noterefintro:}\\
+  1.2.3 ---> (see \S~1.2.3, n.~1)\\
+  0.0.0 ---> (see intro., n.~1)\\
+  1.1.0 ---> (see p.~24, n.1)\\
+  0.1.0 ---> (see intro., p.~2, n.~1)
+\end{verse}
+
+As you see, this produces a mixed system of back references, so you'll
+need to decide whether you and your readers might still find it
+acceptable.
+
+\mylittlespace This \colmarginpar{\texttt{hidezeros}} boolean option
+attempts, with varying degrees of success, to disguise the zeros in
+section identifiers without mixing different sorts of back reference
+in one document.  Unlike \texttt{pagezeros}, it will never modify
+identifiers where the first number is zero.  It leaves all such
+identifiers to the \texttt{noterefintro} option, so if your identifier
+looks like 0.1.0, the second zero will still appear.  The only thing
+you can do about it is to move the citation so that it isn't in a zero
+section.  The rationale is that \texttt{hidezeros} places a string ---
+by default \enquote{pref.} --- \emph{inside} the section identifier so
+that a reader knows that the citation occurred in the prefatory
+material to a particular section.  Combining this with another string
+for the prefatory material to a whole work is unattractive, and I've
+avoided it.  Here are some examples of how it looks:
+\begin{verse}
+  1.1.1 ---> (see \S~1.1.1, n.~1)\\
+  1.0.1 ---> (see \S~1.pref.1, n.~1); should this even be possible?\\
+  1.1.0 ---> (see \S~1.1.1 [pref.], n.~1)\\
+  1.0.0 ---> (see \S~1.1 [pref.], n.~1)\\
+  1.0 ---> (see \S~1.1 [pref.], n.~1)
+\end{verse}
+
+The \colmarginpar{\cmd{cmspref}} brackets and placement of the
+identifying string are hard coded, but you can change the string
+itself with a line something like this in your preamble:\\
+\verb+\renewrobustcmd{\cmspref}{\emph{pref.\@}}+ <--- \textbf{NB} the
+\verb+\@+
+after the dot\\
+The \texttt{hidezeros} method at least produces more uniform back
+references, though it perhaps sacrifices something in immediate
+readability in order to do so.  I would be glad to entertain
+suggestions for other solutions.
+
+\mylittlespace If your documentation uses footnotes, then the guide to
+the \texttt{noteref} option(s) concludes here.  I have, however, been
+determined, at least in this context, to provide for endnote users the
+same features as for footnote users, mainly because the \emph{Manual}
+caters equally to both.  Unfortunately, because footnotes are a core
+part of \LaTeX\ formats and endnotes are provided by means of extra
+packages, users of the latter will face some additional complications
+if they wish to provide Chicago-style back references.  I document
+these forthwith.
+
+\subsubsection*{Endnotes and \mycolor{\texttt{noteref}}}
+\label{sec:endnoterefs}
+
+document is to use the \textsf{endnotes} package by John Lavagnino,
+and \textsf{biblatex} provides a reliable interface to that package,
+making it relatively simple to use and control (cf.\ esp.\ the
+\texttt{notetype} option in \textsf{biblatex.pdf, \S~3.1.2.1}).  The
+package does have its limitations --- on which see more below --- so I
+did have a look at its next-generation replacement, Clemens
+Niederberger's \textsf{enotez}.  This adds all the needed
+functionality, I think, and is also more future proof, relying as it
+does on the work of the \LaTeX 3 project.  The downside is that my
+\TeX nical abilities fell short of being able to make it work with the
+\mycolor{\texttt{noteref}} option, so I have instead created a new
+package \colmarginpar{\small\texttt{\textbf{cmsendnotes.sty}}} which
+combines functionality from \textsf{endnotes}, from Ulrich Dirr's
+\textsf{hyperendnotes}, and from \textsf{biblatex-chicago}.  If you
+need some functionality that \textsf{endnotes} doesn't provide, then
+tested any of this with the \textsf{memoir} class, which has its own
+endnote mechanism, so please let me know if it doesn't work and I'll
+try to have a look.)  The documentation that follows should clarify
+when you might want to load the new package, and also the options
+available to get \textsf{cmsendnotes} to do what you want.
+
+\mylittlespace Before we begin, I should just point out that, as usual
+with \textsf{biblatex}, you can mix foot- and endnotes in the same
+document, but if \texttt{noterefs} are going to appear in both sorts
+of note --- surely this situation is highly unlikely --- then you need
+to be careful that they refer back \emph{only} to long references in
+the \emph{same} sort of note.  A \texttt{noteref} from an endnote to a
+long citation in a footnote will be inaccurate, and vice versa, so
+careful use of the \cmd{citereset} command (as in
+\href{file:cms-noteref-demo.pdf}{\textsf{cms-noteref-demo.pdf}}) or
+perhaps of the \textsf{biblatex} \texttt{citereset} option should
+allow you to keep the two sorts of note distinct.
+
+\mylittlespace The principle to keep in mind is that back references
+to full endnotes point not to the place in the main text where you've
+cited a source, but rather to the place where that citation is
+actually printed, which may well be in another division of your
+document altogether.  If you are providing endnotes at the end of each
+chapter, or (less likely) at the end of each section of a long
+article, then this means that an endnote to a later chapter or section
+will point to the earlier chapter or section after which the full
+citation was printed.  This interacts very well with the
+\textsf{endnotes} package's \cmd{theendnotes} command, which prints,
+and then clears, all the endnotes created up to the point at which you
+call it.  Subsequent calls to \cmd{theendnotes} do the same, and short
+notes will always have a reasonably accurate sense of where their
+antecedent long note has appeared, i.e., in the endnotes to a
+particular chapter or section.  (This even has the side effect of
+making the zero section problem somewhat more tractable, as the back
+reference doesn't mind that the \cmd{endnote} command occurs in
+section 1.0, but rather that the citation appears in the notes to
+section 1.1.)
+
+\mylittlespace Similarly, if your endnotes appear all together at the
+end of an article, then you can just use the \texttt{page} option to
+\texttt{noteref}, or no option at all, and the back references will be
+both accurate and usable (assuming the notes are all numbered
+consecutively, I suppose, which seems a safe assumption).  The upshot
+is that, if you are providing endnotes in either of these scenarios,
+both of them envisaged by the \emph{Manual} (14.46), and \emph{either}
+if you don't need the \textsf{hyperref} functionality, \emph{or} if
+the somewhat restricted functionality available through the
+\textsf{endnotes} package is good enough, then you can happily ignore
+the new \textsf{cmsendnotes} package entirely.
+
+\mylittlespace If back references are, in the scenarios discussed
+above, basically working for you, but you want more elaborate
+\textsf{hyperref} functionality, then you can load the
+\textsf{cmsendnotes} package without any options instead of the
+\textsf{endnotes} package.  Please be aware, however, that
+\emph{after} \textsf{biblatex-chicago} for it to work properly.  What
+you'll then get by default, assuming you've loaded \textsf{hyperref},
+are links from endnote numbers in the main text to the corresponding
+numbers in the endnotes section itself, and vice versa, along with
+more accurate links from the back references to particular endnotes in
+preceding sections or chapters.  There are several options available
+for changing the default appearance of your endnotes, four of which
+are package options to \textsf{cmsendnotes} and two of which are
+commands that you can redefine to your liking.
+
+\mylittlespace Two \colmarginpar{\texttt{hyper}} package options
+control the \textsf{hyperref} behavior of endnote numbers.  They are
+both set to \texttt{true} by default, if the \textsf{hyperref} package
+is loaded.  If you set the first, \texttt{hyper}, to \textsf{false}
+endnote numbers at all.  If you \colmarginpar{\texttt{enotelinks}} set
+the second, \texttt{enotelinks}, which I've borrowed from
+\textsf{hyperendnotes.sty}, to \texttt{false}, then only endnote
+numbers in the main text will function as links, the numbers in the
+endnote sections themselves ceasing to act as such.
+
+if set to \texttt{true}, stops the printing of the usual section
+header before the endnotes themselves, in case this might help to
+solve some formatting problems in your documents.
+
+\mylittlespace This \mymarginpar{\cmd{enoteheading}} is the standard
+\textsf{endnotes} package command for defining exactly what is printed
+in the heading.  I have slightly redefined it (for reasons I shall
+explain later), but you can redefine it in your preamble if you wish,
+and that will be respected by \textsf{cmsendnotes}.
+
+\mylittlespace This \colmarginpar{\texttt{blocknotes}} package option,
+if set to \texttt{true}, presents the text of each endnote as a
+flush-left block, i.e., without the first line being indented.
+
+\mylittlespace This \colmarginpar{\cmd{enoteskip}} command, which was
+inspired by a similar provision in \textsf{hyperendnotes.sty}, sets
+the vertical space between individual endnotes.  By default it doesn't
+change basic interline space, but you can define it in your preamble
+to something like \cmd{smallskip} or \cmd{medskip} in case you want a
+bit more light inside your endnote sections.
+
+\mylittlespace So far, then, I have discussed contexts where
+\textsf{cmsendnotes.sty} only brings cosmetic changes to functionality
+which basically already works using \textsf{endnotes.sty}.  Indeed, if
+you are using either of these packages in the ways already outlined,
+then the setting of the main \mycolor{\texttt{noteref}} option defines
+how your back references will look, and
+\colmarginpar{\texttt{fullnoterefs}} the
+\mycolor{\texttt{fullnoterefs}} option will still govern the
+\mycolor{\texttt{chapter}}, \mycolor{\texttt{section}},
+\mycolor{\texttt{subsection}}, and \mycolor{\texttt{part}} values of
+the \texttt{noteref} option, just as in the general discussion above.
+In the methods discussed below, additional steps are required for
+defining how your back references will look, and the
+\texttt{fullnoterefs} option is irrelevant, as the back references
+will always appear in their fullest form.
+
+\mylittlespace The methods of endnote presentation to which I now turn
+involve, in the \emph{Manual's} words, when notes to \enquote{each
+  chapter of a book are \ldots\ grouped in the end matter} (14.46).
+Here, you would want not only a main heading for the endnotes section
+but also \enquote{a subhead bearing the chapter number or title or
+  both.}  It is perfectly possible to achieve the subdivision and
+subheading of a long endnotes section by using \textsf{endnote's}
+a sectioning command of some sort in its argument, for example.  Using
+\texttt{noteref} back references in this context can be a little
+complicated, however, mainly because of the principle I explained
+above, i.e., that back references point to the place where the long
+note was printed, not to the section of the main document where the
+source was actually cited.  For our purposes, this means that, unless
+you have set \texttt{noteref} to \texttt{page} or \texttt{none},
+\textsf{biblatex-chicago} actually has to extract data from the
+sectioning command you've included in \cmd{addtoendnotes} and, most
+frequently, modify that data to make it work inside a \texttt{noteref}
+back reference in way that is both consistent and useful.  The
+\textsf{cmsendnotes} package tries to automate this process as much as
+possible so that with, in the best-case scenario, only one option
+given to the package the whole system can be made to work without
+further user intervention.  Further package options can help with
+slightly more complicated scenarios, but if your requirements are more
+complex than the automatic system can provide, then there are two ways
+to handcraft a divided endnote section: one uses traditional
+\cmd{addtoendnotes} functionality from the \textsf{endnotes} package,
+and the other uses new commands available from \textsf{cmsendnotes}.
+I believe the second handcrafted option to be slightly more convenient
+than the first, but in any case I'll start by explaining the automatic
+provisions, then move on to the two handcrafted options, leaving you
+to judge which seems best suited to your needs.
+
+\enlargethispage{-\baselineskip}
+
+\mylittlespace For \colmarginpar{\texttt{\textbf{split}}} the
+automatic subdivision of an endnotes section I have borrowed a
+concept, if not its implementation, from \textsf{enotez}, and provided
+the \textsf{cmsendnotes} option \mycolor{\texttt{split}}, which has 4
+possible values: \texttt{part}, \texttt{chapter}, \texttt{section} and
+\texttt{subsection}.  (If you don't provide a key, it defaults to
+\texttt{chapter}.)  With this option set, you need to use a new
+command for printing the endnotes, the ungainly
+\colmarginpar{\cmd{\textbf{theendnotes\-bypart}}} but I hope memorable
+\mycolor{\cmd{theendnotesbypart}}.  When you do this,
+\textsf{cmsendnotes} does something in the background that's worth
+understanding.  Ordinarily, in the standard \textsf{endnotes} package,
+any call to \cmd{theendnotes} produces an\ .ent file containing all of
+the endnote data in the document up to that point, and proceeds to
+print it.  Another call to \cmd{theendnotes} gathers the endnote data
+occurring between it and the first call, overwriting the\ .ent file,
+and again printing it, and so on.  Whenever you use any version of
+\cmd{theendnotesbypart}, \textsf{cmsendnotes} will write one\ .ent
+file per section named by the \texttt{split} option, assuming that
+said section actually contains any endnotes.  The plain
+\cmd{theendnotesbypart} command, with no further options, proceeds to
+print, in sequence, \emph{all} the\ .ent files in numerical order.  In
+the first instance, then, the value of the \texttt{split} option
+decides how your endnotes are distributed to different\ .ent files.
+These files are named after the main document suffixed with the number
+of the section, e.g., \textsf{jobname1.ent} for chapters or
+\textsf{jobname1.3.ent} for sections.
+
+\mylittlespace In the second instance, the \texttt{split} option
+The main header is produced by a \cmd{section*} command, and by
+produced by \cmd{subsection*} commands, and will take their name from
+the \textsf{split} option and their number from the number of the\
+.ent file currently being processed: \texttt{\textbf{Chapter 1}}
+\ldots\ \texttt{\textbf{Chapter 2}}.  The headers are localized,
+assuming you're using a language supported by
+\textsf{biblatex-chicago}.  Even if you're not using \texttt{noteref}
+back references in your document, this mechanism can still provide a
+convenient means of subdividing an endnotes section.
+
+\mylittlespace If you are using \textsf{noteref}, then the value of
+that option leads to two possible outcomes.  If set to \texttt{page}
+or \texttt{none}, any back references will point to full notes by page
+plus note number or just by note number, as usual, bearing in mind
+that the page involved is where the full note was printed, not where
+it was cited in the main body of the text.  If set to any of the other
+possible sections of your document, then the \texttt{split} option has
+a third function, which is to provide the (localized) string for the
+back reference itself --- (see chap.~1, n.~2) --- which will refer to
+a subsection of the endnotes section named \texttt{\textbf{Chapter~1}}
+rather than to the actual first chapter of the main document.  This
+setup will usually involve setting \texttt{split} to the same value as
+the \texttt{noteref} option itself, but if they differ, and
+\texttt{noteref} isn't \texttt{page} or \texttt{none}, then
+\texttt{split} takes precedence and governs the appearance of the back
+reference.
+
+\mylittlespace Let's say, then, that your document is in English and
+you've set the \textsf{biblatex-chicago} option
+\texttt{noteref=chapter}, and the \textsf{cmsendnotes} option
+\texttt{split}, then what you can expect to see, when you use
+\cmd{theendnotesbypart}, is something like this, subject to the usual
+rules for the appearance or non-appearance of \texttt{noterefs}, and
+remembering that in this context, as noted above, all
+\texttt{noterefs} will appear in their long form:
+\begin{verse}
+  \textbf{Notes}\\
+
+  \textbf{Chapter~1}\\
+  1. Book.\\
+  2. Article.\\
+  3. InCollection.\\
+
+  \textbf{Chapter~2}\\
+  1. InCollection (see chap.~1, n.~3).\\
+  2. BookInBook.\\
+  3. Article (see chap.~1, n.~2).\\
+
+  \textbf{Chapter~3}\\
+  1. BookInBook (see chap.~2, n.~2).\\
+  2. Book (see chap.~1, n.~1).
+\end{verse}
+
+It won't, unfortunately, always be this simple, but it may be a
+comfort to know that some of the complications are the same as those
+faced by users of \texttt{noteref} with footnotes, in particular
+\mymarginpar{\textbf{Zero Sections}} the zero section problem.  To
+deal with this issue you use the same options to
+\textsf{biblatex-chicago} as you would for footnotes, with one
+difference.  In the case of split endnotes, the code has to handle the
+zeros both in the \cmd{subsection*} names \emph{and} in the back
+references, which means that the \texttt{pagezeros} option is no
+longer relevant, as it can't do the right thing in section names.
+This leaves the \texttt{noterefintro} option for hiding zeros that
+start a section number, and the \texttt{hidezeros} option for zeros
+anywhere else.  These \textsf{biblatex-chicago} options work here just
+as described in the footnote section above, but with one or two
+
+\mylittlespace First, I probably shouldn't have bothered trying to
+implement the combination of \texttt{note\-refintro} and
+\texttt{hidezeros}, as any sections of a zero chapter in your document
+will appear by default with zeros intact in the text itself, unless
+measures are taken.  I did \colmarginpar{\cmd{cmsintrosec\-tion}} do
+this thing, however, and part of the implementation is a command
+\mycolor{\cmd{cmsintrosection}}, which provides the identifying string
+for subsections of the introduction.  It is set by default to \S, and
+though you can redefine it in your preamble, please remember that it
+will appear as such in both \cmd{subsection*} names and
+\texttt{noterefs}.
+
+\mylittlespace Indeed, it is the need to cater for two quite distinct
+contexts that makes the automatic provision of \textsf{noteref} back
+references in a divided endnotes section surprisingly tricky.  You
+need \colmarginpar{\cmd{introduction\-name}\\\cmd{forewordname}\\
+  \cmd{sectionname}\\ \cmd{subsection\-name}} one mechanism to take
+\texttt{chapter} and turn it into Chapter, and quite another to turn
+it into chap., bearing in mind that \cmd{bibstrings} don't work
+outside of the reference apparatus, and therefore not in
+\cmd{subsection*} names, though obviously they're perfect for the back
+references themselves.  My solution is to borrow a principle from
+\textsf{babel}, which provides for its languages commands like
+\cmd{prefacename} and \cmd{chaptername}, which print the localized
+version of the term, usually capitalized.  In the\ .lbx files that
+come with \textsf{biblatex-chicago} I have added
+\cmd{introductionname} and \cmd{forewordname}, along with
+\cmd{sectionname} and \cmd{subsectionname}, so at least the most
+common types of prefatory material, when provided to the
+\texttt{noterefintro} option, should work properly both in headings
+and in \texttt{noterefs}, and across languages.
+
+\mylittlespace So, another caveat.  Should you wish to provide a
+\texttt{noterefintro} value that isn't a standard \cmd{bibstring} or
+doesn't have a corresponding \cmd{[value]name} command, then it may
+not work well for you in one or other of the two contexts in which it
+can appear.  The code does test whether the bibstring and command
+exist, and it will capitalize anything in section headers, but
+otherwise you can just cunningly craft a string that's good in both
+contexts or you can define a \cmd{[value]name} command and a new
+
+applies if you want to supply your own name for the \cmd{subsection*}
+commands that divide up the general endnotes \cmd{section*}.  Let's
+say for some reason you want subsections called \textbf{Further
+  Remarks} instead of \textbf{Chapter}.  Strings of more than one word
+are difficult for the code to manage correctly, so instead you could
+include in your preamble lines looking approximately like this:
+\begin{verbatim}
+  \NewBibliographyString{furthrem}
+  \DefineBibliographyStrings{american}%
+  \def\furthremname{Further Remarks}
+\end{verbatim}
+
+Then you could set \texttt{subheadername=furthrem} in the options to
+\textsf{cmsendnotes} and you'll get what you want.  It's not wildly
+convenient, but it's slightly less typing than the handcrafted options
+I discuss below, though for anything more complicated you'll probably
+need those options.
+
+\mylittlespace Before \colmarginpar{\texttt{headername}} I move on to
+the handcrafted methods, I should point out two more
+\textsf{cmsendnotes} options.  The first,
+\mycolor{\texttt{headername}}, sets the name of the main
+\cmd{section*} command at the start of the endnotes section.  It
+defaults to the usual \textsf{endnotes} package command
+\cmd{notesname}, which gives \textbf{Notes} in English.  I have kept
+this separate from the standard \cmd{enoteheading} because it needs
+slightly different treatment in a divided endnotes section.  If the
+definitions I have provided of \cmd{notesname} in the\ .lbx files that
+come with \textsf{biblatex-chicago} aren't to your liking, you can
+provide a string here instead, which is simpler to do because it
+shouldn't be turning up in any \texttt{noterefs}.  If you'd like to
+redefine any of the \cmd{*name} commands, the best place to do so is
+very near to where you actually print the endnotes, where it can
+override the definitions in the\ .lbx files (or in \textsf{babel's}
+files).  Remember, too, that you can use the
+\mycolor{\texttt{noheader}} option to turn off the printing of this
+
+\mylittlespace This \colmarginpar{\texttt{runningname}}
+\textsf{cmsendnotes} option controls the text that appears in running
+providing them.  I have followed the style of the \textsf{endnotes}
+package, so that the default reads something like: \emph{NOTES TO
+  CHAPTER 1}.  The section name and number are controlled by the other
+options already discussed, but the \enquote{Notes to} part is
+controlled by \mycolor{\texttt{runningname}}, so if your document
+isn't in English, and/or you're unhappy with the default string, you
+
+\mylittlespace Should \colmarginpar{\texttt{\textbf{endnotesplit}}}
+the options above not fulfil your needs, you can control more or less
+all parts of the subdivision of your endnotes section, of the running
+headers there, and of back references from short notes to full ones,
+wish to use \texttt{noteref} back references in this context, you
+\mymarginpar{\textbf{NB}} must first set the \textsf{biblatex-chicago}
+option \mycolor{\texttt{endnotesplit}} to \texttt{true}, no matter
+which of the two possible implementation methods you choose.  With the
+standard \textsf{endnotes} package you would then use the command
+\cmd{addtoendnotes}, while with \textsf{cmsendnotes} it involves
+variants of the endnote-printing command \cmd{theendnotesbypart}.
+\texttt{cmsendnotes}, in case that's useful to you; and second, that
+with any other endnote implementation, you'll have to consult its
+documentation to see if there's a compatible means of dividing the
+notes.)
+
+\mylittlespace First, \mymarginpar{Handcrafting
+  w/\\\texttt{cmsendnotes}} I introduce the methods provided by
+\textsf{cmsendnotes}.  The command \cmd{theendnotesbypart} has three
+variants.  The first, \mycolor{\cmd{theendnotesbypart*}}, simply
+suppresses the printing of the \texttt{headername}, so it works more
+or less like setting \texttt{noheader} in the options to
+\textsf{cmsendnotes}.  The other two involve an optional argument,
+\colmarginpar{\cmd{theendnotes\-bypart[]}} in square brackets,
+containing an individual section number, which prints the endnotes
+from that section.  This command never prints the general endnote
+it will print the individual
+controlled by the \texttt{subheadername} option.  To turn that
+printing off you can either use the starred version of the command,
+i.e., \mycolor{\cmd{theendnotesbypart*[]}}, or you can set the
+\mycolor{\texttt{nosubheader}} to \texttt{true}.  A sequence of
+commands, each with one section of the document inside square
+brackets, will give you a complete endnotes section wherever you
+decide to place it, while the starred forms or \texttt{nosubheader}
+
+\mylittlespace First, \mymarginpar{\textbf{NB}} please note that what
+you need to place inside the square brackets is the \emph{number that
+  forms part of the name of the\ .ent file in your working directory.}
+In other words, it's the number \emph{before} any manipulations by the
+\textsf{cmsendnotes} package remove zeros from it.  Depending on the
+
+\begin{verbatim}
+Chapters                             Sections
+\theendnotesbypart*[0]          \theendnotesbypart*[0.0] <-- "introname"
+\theendnotesbypart*[1]          \theendnotesbypart*[1.1]
+\theendnotesbypart*[2] etc.    \theendnotesbypart*[1.2] etc.
+\end{verbatim}
+
+When in doubt, have a look in your working directory for the\ .ent
+files produced for your document, and use the numbers from there.  (If,
+for some reason, you decide to split by \texttt{part}, you'll probably
+have roman numerals there, for example, apart from the zero.)
+
+\mylittlespace The \mymarginpar{\textbf{Sectioning}} next step is to
+provide some sort of sectioning command for the subheaders and for the
+\texttt{noteref} back references.  This is slightly complicated, but
+works the same whether you're using \textsf{cmsendnotes} or
+\textsf{endnotes}.  The basic principle is that the main name of the
+section appears in the endnotes section, while the optional name
+\texttt{noteref}:
+
+\begin{verbatim}
+\subsubsection[chap. 1]{Chapter 1} --> Chapter 1 ... (see chap. 1, n.1)
+\end{verbatim}
+
+You'll notice that the sectioning command isn't starred, as only
+unstarred commands provide the optional [toc] argument.  (The
+\cmd{addcontentsline} command can also be used with starred forms, but
+an issue, so please read on.)  The unusual form of the [toc] argument
+the actual header in your endnotes section shouldn't have a number in
+it provided by the standard \LaTeX\ methods, so you'll have to pick a
+section type that falls underneath the thresholds of the \LaTeX\
+counters \texttt{tocdepth} and \texttt{secnumdepth}.  By default, in
+the standard \texttt{book} and \texttt{report} classes,
+\cmd{subsubsection} works for this, while in the \texttt{article}
+class you may need \cmd{paragraph}.  (You could, of course, also
+change the counters, should you wish.)
+
+\mylittlespace So, let's say you want to subdivide your endnotes
+section with subheaders containing both the chapter number and the
+chapter title, as envisaged by the \emph{Manual} (14.46).  Your
+endnotes section might start like this:
+
+\begin{verbatim}
+\section*{Notes}
+\subsubsection[intro.]{Introduction: The History of the Problem}
+\theendnotesbypart*[0]
+\subsubsection[chap. 1]{Chapter 1: Renewing the Question}
+\theendnotesbypart*[1]   (etc.)
+\end{verbatim}
+
+There remain a couple of formatting issues with this code.  The
+\textsf{endnotes} package points out that the first endnote after such
+a sectioning command won't be indented properly, so it and
+\textsf{cmsendnotes} use \verb+\mbox{}\par\vskip-\baselineskip+ after
+sectioning commands to prevent this.  Additionally, both packages
+provide code for running headers using \cmd{@mkboth}, so if you use
+such headers you can either do the same inside \cmd{makeatletter} and
+\cmd{makeatother} commands or just use \cmd{markboth}.  Taking all of
+this into account gives code looking something like this, perhaps:
+
+\begin{verbatim}
+\section*{Notes}
+\subsubsection[intro.]{Introduction: The History of the Problem
+\markboth{NOTES TO INTRODUCTION}%
+      {NOTES TO INTRODUCTION}}%
+\mbox{}\par\vskip-\baselineskip
+\theendnotesbypart*[0]
+\subsubsection[chap. 1]{Chapter 1: Renewing the Question
+\markboth{NOTES TO CHAPTER 1}%
+      {NOTES TO CHAPTER 1}}%
+\mbox{}\par\vskip-\baselineskip
+\theendnotesbypart*[1]   (etc.)
+\end{verbatim}
+
+One of the, perhaps minor, advantages of using the
+\textsf{cmsendnotes} commands for this is that they will at least all
+typically be grouped together in one place in your document, rather
+than scattered throughout, as when you use \textsf{endnotes'}
+\cmd{addtoendnotes} command, to which we now turn.
+
+\mylittlespace To \mymarginpar{Handcrafting w/ \textsf{endnotes}} use
+the \textsf{endnotes} package with its main command \cmd{theendnotes}
+to produce a subdivided endnotes section, you must first remember to
+set the \textsf{biblatex-chicago} option
+\mycolor{\texttt{endnotesplit}} to \texttt{true}, that is, assuming
+you want to provide \texttt{noteref} back references.  For splitting
+the endnotes, you \mymarginpar{\cmd{addtoendnotes}} need the
+yourself.  Ordinarily, you'll need one such command for each relevant
+division of your text, placed just after the sectioning command
+itself, so that any endnotes that occur in the section will appear
+grouped underneath the heading you provide.  At the next section,
+another such command starts a new subsection of endnotes.
+
+\mylittlespace To provide the same endnotes section divided by chapter
+like this:
+
+\begin{verbatim}
+\chapter*{Introduction: The History of the Problem}
+  \protect\subsubsection[intro.]{Introduction: The History of the%
+   Problem%
+    \protect\markboth{NOTES TO INTRODUCTION}%
+    {NOTES TO INTRODUCTION}}%
+   \mbox{}\par\vskip-\baselineskip} ...
+\chapter{Renewing the Question}
+  \protect\subsubsection[chap. 1]{Chapter 1: Renewing the Question%
+    \protect\markboth{NOTES TO CHAPTER 1}%
+    {NOTES TO CHAPTER 1}}%
+   \mbox{}\par\vskip-\baselineskip} ... (etc.)
+\end{verbatim}
+
+The commands you use are the same as with \cmd{theendnotesbypart[]},
+but in this context both the sectioning command \emph{and} the command
+for running headers need to be \cmd{protected}.  I would also
+default definition produces too much extra vertical space before the
+that you can use \textsf{cmsendnotes} (without a \texttt{split}
+option) instead of \textsf{endnotes}, if the extra \textsf{hyperref}
+functionality is important to you.  The command sequence above will
+continue to work in the same way.
+
+\mylittlespace There are tradeoffs for both systems.  With
+\textsf{endnotes}, at least the single \cmd{theendnotes} command keeps
+things simple, but you still have to keep track of which sections have
+endnotes in them, else spurious subheaders will appear.  Rooting
+around in your working directory to make sure you've printed all the\
+.ent files is annoying, but at least those represented there will be
+those which contain endnotes in the first place.  Both methods are, I
+think it's fair to say, a fair amount of labor, but they do give you
+complete control over how your endnotes section looks, and over how
+\texttt{noteref} back references within it look.  As with all new
+functionality, \texttt{noteref} and \textsf{cmsendnotes} may well
+contain bugs, so if you find any please let me know, but do please
+also send along a minimum working example so I have a chance to
+identify what's a bug in the code and what's resulted from inadequate
+documentation.
+
\subsection{General Usage Hints}
\label{sec:hints}

@@ -5672,17 +7861,17 @@
changed.  With early versions of \textsf{bibla\-tex-chicago-notes},
the standard way of loading the package was via a call to
\textsf{biblatex}, e.g.:
-\begin{quote}
-  \cmd{usepackage[style=chicago-notes,strict,backend=bibtex8,\%\\
-    babel=other,bibencoding=inputenc]\{biblatex\}}
-\end{quote}
+\begin{verbatim}
+  \usepackage[style=chicago-notes,strict,backend=bibtex8,%
+    babel=other,bibencoding=inputenc]{biblatex}
+\end{verbatim}
Now, the default way to load the style, and one that will in the
vast majority of standard cases produce the same results as the old
invocation, will look like this:
-\begin{quote}
-  \cmd{usepackage[notes,strict,backend=biber,autolang=other,\%\\
-    bibencoding=inputenc]\{biblatex-chicago\}}
-\end{quote}
+\begin{verbatim}
+  \usepackage[notes,strict,backend=biber,autolang=other,%
+    bibencoding=inputenc]{biblatex-chicago}
+\end{verbatim}

method without the \texttt{notes} option will still work, but only
@@ -5708,15 +7897,16 @@
You'll lose all the definitions in \textsf{biblatex-chicago.sty},
including those to which I've already alluded and also the code that
sets the note number in-line rather than superscript in endnotes or
-footnotes.  Also in this file is the code that calls
-\textsf{cms-american.lbx}, which means that you'll lose all the
-Chicago-specific bibstrings I've defined unless you provide, in your
-preamble, a \cmd{DeclareLanguageMapping} command adapted for your
+footnotes, the URL line-breaking code, and the Chicago-specific
+number- and date-range compression code.  You'll need to load the
+required packages \textsf{xstring} and \textsf{nameref} yourself, as
+\textsf{biblatex} doesn't do it for you.  Also, you'll lose the code
+that calls \textsf{cms-american.lbx}, which means that you'll lose all
+the Chicago-specific bibstrings I've defined unless you provide, in
setup, on which see section~\ref{sec:international} below and also
\xA7\xA7~4.9.1 and 4.11.8 in \textsf{biblatex.pdf}.

-%%\enlargethispage{-\baselineskip}
-
\mylittlespace What you \emph{will not} lose is the ability to call
the package options \texttt{annotation, strict, short,} and
\texttt{noibid} (section~\ref{sec:useropts}, above), in case these
@@ -5775,13 +7965,12 @@
periods after long notes, bugs that were byproducts of my attempt to
fix other end-of-entry errors.  One of the side effects of this older
code was (wrongly) to put a period after a long note produced, e.g.,
-by a command like \cmd{footnote\{\textbackslash headlessfullcite\}},
-whereas only the \enquote{foot} cite commands (including
-\cmd{autocite} in the default \textsf{biblatex-chicago-notes} set up)
-should do so.  If you came to rely on this side effect, please note
-now that you'll have to put the period in yourself when explicitly
-calling \cmd{footnote}, like so: \cmd{footnote\{\textbackslash
+by a command like \verb+\footnote{\headlessfullcite}+, whereas only
+the \enquote{foot} cite commands (including \cmd{autocite} in the
+default \textsf{biblatex-chicago-notes} set up) should do so.  If you
+came to rely on this side effect, please note now that you'll have to
+put the period in yourself when explicitly calling \cmd{footnote},

\mylittlespace When you use abbreviations at the ends of fields in
your .bib file (e.g., \enquote{\texttt{n.d.}} or
@@ -5796,33 +7985,26 @@
\textsf{misc} entry (see house:papers).  If you find you need to
provide such formatting elsewhere, please let me know.

-\mylittlespace Finally, allow me to reiterate what
-\textsf{biblatex.pdf} says, to wit, use \textsf{Biber} if you can.
-It's not absolutely required for the notes \&\ bibliography style, but
-it is required for an increasing amount of very useful functionality
-in all \textsf{biblatex} styles.  The \textbf{mv*} entry types, for
-example, can help streamline your .bib database, particularly when
-used as \textsf{crossref} targets, but this utility is severely
-limited if you are using one of the older backends.  If you have to
-use one of these older backends, then the \textsf{biblatex} authors
-advise using \textsf{bibtex8}, rather than standard \textsc{Bib}\TeX,
-to avoid the cryptic errors that ensue when your .bib file gets to a
-certain size.
+\mylittlespace Finally, allow me to re-emphasize that, in its current
+form, the notes \&\ bibliography style \emph{requires} the use of
+\textsf{biber} as your backend --- variants of \textsc{Bib}\TeX\
+simply cannot produce accurate output anymore, given how many features
+now depend on the more modern backend.

\section{The Specification: Author-Date}
\label{sec:authdate}

The \textsf{biblatex-chicago} package contains two different
-author-date styles.  The first, \textsf{bibla\-tex-chicago-authordate},
-implements the specifications of the 16th edition of the \emph{Chicago
-  Manual of Style}.  Numbers in parentheses refer to sections of the
-\emph{Manual}, though as this latest edition now recommends \enquote{a
-  uniform treatment for the main elements of citation in both of its
-  systems of documentation} (15.2), many of these references will in
-fact be to the chapter on the notes \&\ bibliography style (chap.\
-14), which chapter is, by design, considerably more detailed than that
-devoted to the author-date style.  The second,
+author-date styles.  The first,
+\textsf{bibla\-tex-chicago-authordate}, implements the specifications
+of the 17th edition of the \emph{Chicago Manual of Style}.  Numbers in
+parentheses refer to sections of the \emph{Manual}, though many of
+these references will in fact be to the chapter on the notes \&\
+bibliography style (chapter 14), which chapter is, by design,
+considerably more detailed than that devoted to the author-date style,
+and which \textsf{biblatex-chicago-authordate} always modifies
+according to the guidelines in chapter 15.  The second author-date
specification but with a markedly different style of title
presentation, including sentence-style capitalization and an absence
of quotation marks around the (plain-text) titles of \textsf{article}
@@ -5829,10 +8011,10 @@
or \textsf{incollection} entries, \emph{inter alia}.  The
\textsf{trad} style is so named because older versions of the
\emph{Manual}, up to and including the 15th edition, recommended this
-plainer style for author-date titles, and the 16th edition itself
+plainer style for author-date titles, and the 17th edition itself
suggests the possibility, when needed, of retaining such title
presentation in combination with its own recommendations for other
-parts of the reference apparatus (15.45).  In practice, the
+parts of the reference apparatus (15.38).  In practice, the
differences between the two styles necessitate separate discussions of
the \textsf{title} field and one extra package option
@@ -5845,10 +8027,10 @@
have also duplicated a lot of the information in
\textsf{biblatex.pdf}, which I hope won't badly annoy expert users of
the system.  As usual, headings in \mycolor{green}
-\colmarginpar{\textsf{New in this release}} indicate material new to
-this release, or occasionally old material that has undergone
-significant revision.  The file \textsf{dates-test.bib} contains many
-examples from the \emph{Manual} which, when processed using
+\colmarginpar{\textsf{New in this release}} indicate either material
+new to this release or old material that has undergone significant
+revision.  The file \textsf{dates-test.bib} contains many examples
+from the \emph{Manual} which, when processed using
\textsf{biblatex-chicago-authordate}, should produce the same output
as you see in the \emph{Manual} itself, or at least compliant output,
where the specifications are vague or open to interpretation, a state
@@ -5856,7 +8038,8 @@
but you'd have to keep one eye on the 15th edition of the
\emph{Manual} (chap.\ 17) for the titles.  I have provided
+\href{file:cms-dates-sample.pdf}{\textsf{cms-dates-sample.pdf}} and
show how my system processes \textsf{dates-test.bib}, and I have also
included the reference keys from the latter file below in parentheses.

@@ -5864,23 +8047,24 @@
\label{sec:types:authdate}

The complete list of entry types currently available in
minus the odd \textsf{biblatex} alias, is as follows:
-\mycolor{\textbf{article}}, \textbf{artwork}, \textbf{audio},
+\textbf{article}, \mycolor{\textbf{artwork}}, \textbf{audio},
\textbf{book}, \textbf{bookinbook}, \textbf{booklet},
-\textbf{collection}, \textbf{customc}, \textbf{image},
-\textbf{inbook}, \textbf{incollection}, \textbf{inproceedings},
-\textbf{inreference}, \mycolor{\textbf{jurisdiction}},
-\mycolor{\textbf{legal}}, \mycolor{\textbf{legislation}},
-\textbf{letter}, \textbf{manual}, \textbf{misc}, \textbf{music},
-\textbf{mvbook}, \textbf{mvcollection}, \textbf{mvproceedings},
-\textbf{mvreference}, \textbf{online} (with its alias \textbf{www}),
-\textbf{patent}, \textbf{periodical}, \textbf{proceedings},
-\textbf{reference}, \mycolor{\textbf{report}} (with its alias
-\textbf{techreport}), \mycolor{\textbf{review}}, \textbf{suppbook},
+\textbf{collection}, \textbf{customc}, \mycolor{\textbf{dataset}},
+\textbf{image}, \textbf{inbook}, \textbf{incollection},
+\textbf{inproceedings}, \textbf{inreference}, \textbf{jurisdiction},
+\textbf{legal}, \textbf{legislation}, \textbf{letter},
+\textbf{manual}, \textbf{misc}, \textbf{music}, \textbf{mvbook},
+\textbf{mvcollection}, \textbf{mvproceedings}, \textbf{mvreference},
+\textbf{online} (with its alias \textbf{www}), \textbf{patent},
+\mycolor{\textbf{performance}}, \textbf{periodical},
+\textbf{proceedings}, \textbf{reference}, \textbf{report} (with its
+alias \textbf{techreport}), \textbf{review},
+\mycolor{\textbf{standard}}, \textbf{suppbook},
\textbf{suppcollection}, \textbf{suppperiodical}, \textbf{thesis}
(with its aliases \textbf{mastersthesis} and \textbf{phdthesis}),
-\mycolor{\textbf{unpublished}}, and \textbf{video}.
+\textbf{unpublished}, and \textbf{video}.

\mylittlespace What follows is an attempt to specify all the
differences between these types and the standard provided by
@@ -5893,22 +8077,21 @@
it seemed to me better to gather information pertaining to fields in
the next section.

-\paragraph*{\protect\colmarginpar{\textbf{article}}}
+\paragraph*{\protect\mymarginpar{\textbf{article}}}
-The \emph{Chicago Manual of Style} (14.170) recognizes three different
+The \emph{Chicago Manual of Style} (14.164) recognizes three different
sorts of periodical publication, \enquote{journals,}
-\enquote{magazines,} and \enquote{newspapers.}  The first (14.172)
-includes \enquote{scholarly or professional periodicals available
-  mainly by subscription,} while the second refers to \enquote{weekly
-  or monthly} publications that are \enquote{available either by
-  subscription or in individual issues at bookstores or newsstands.}
+\enquote{magazines,} and \enquote{newspapers.}  The first (14.166) is
+\enquote{a scholarly or professional periodical available mainly by
+  subscription,} while the second refers to \enquote{weekly or monthly
+  (or sometimes daily)} publications that are \enquote{available in
+  individual issues at libraries or bookstores or newsstands or
+  offered online, with or without a subscription.}
\enquote{Magazines} will tend to be \enquote{more accessible to
general readers,} and typically won't have a volume number.  The
following paragraphs detail how to construct your .bib entries for all
these sorts of periodical publication.

-\enlargethispage{\baselineskip}
-
\mylittlespace For articles in \enquote{journals} you can simply use
the traditional \textsc{Bib}\TeX\ --- and indeed \textsf{biblatex} ---
\textsf{article} entry type, which will work as expected and set off
@@ -5916,28 +8099,28 @@
by the \emph{Manual}.  If, however, you wish to cite a
\enquote{magazine} or a \enquote{newspaper}, then you need to add an
\textsf{entrysubtype} field containing the exact string
-\texttt{magazine} or, now, its synonym \mycolor{\texttt{newspaper}}.
-The main formatting differences between a \texttt{magazine/newspaper}
-and a plain \textsf{article} are that time specifications (month, day,
+\texttt{magazine} or, now, its synonym \texttt{newspaper}.  The main
+formatting differences between a \texttt{magazine/newspaper} and a
+plain \textsf{article} are that time specifications (month, day,
season) aren't placed within parentheses, and that page numbers are
set off by a comma rather than a colon.  Otherwise, the two sorts of
reference have much in common.  (For \textsf{article}, see
-\emph{Manual} 14.175--198, 15.9, 15.43--46; batson, beattie:crime,
+\emph{Manual} 14.168--87, 15.9, 15.46--49; batson, beattie:crime,
chu:panda, connell:chronic, conway:evolution, friedman:learning,
garaud:gatine, garrett, hlatky:hrt, kern, lewis, loften:hamlet,
loomis:structure, rozner:liberation, schneider:mittelpleistozaene,
-terborgh:pre\-ser\-vation, wall:ra\-di\-o, warr:ellison,
-white:callima\-chus. With \textsf{entrysubtype} \texttt{maga\-zine},
-cf.\ 14.181, 14.199--202, 15.47; assocpress:gun,
-lakeforester:pushcarts, mor\-genson:\-mar\-ket, reaves:ro\-sen,
+white:callima\-chus. For \textsf{entrysubtype} \texttt{maga\-zine},
+cf.\ 14.171, 14.188--200, 15.49; assocpress:gun,
+lakeforester:pushcarts, morgenson:market, reaves:rosen,
stenger:privacy.)

-\mylittlespace The \emph{Manual} now suggests that, no matter which
+\mylittlespace The \emph{Manual} suggests that, no matter which
citation style you are using, it is \enquote{usually sufficient to
cite newspaper and magazine articles entirely within the text}
-(15.47).  This involves giving the title of the journal and the full
+(15.49).  This involves giving the title of the journal and the full
date of publication in a parenthetical reference, including any other
-information in the main text (14.206), thereby obviating the need to
+information in the main text (14.198), thereby obviating the need to
present such an entry in the list of references.  To utilize this
method in the author-date styles, in addition to a \texttt{magazine}
\textsf{entrysubtype}, you'll need to place \texttt{cmsdate=full} into
@@ -5948,30 +8131,20 @@
you'll also need \texttt{useauthor=false} in the \textsf{options}
field.  Other surplus fields will be ignored.  (See osborne:poison.)

-%\enlargethispage{\baselineskip}
-
\mylittlespace If you are familiar with the notes \&\ bibliography
style, you'll know that the \emph{Manual} treats reviews (of books,
plays, performances, etc.) as a sort of recognizable subset of
\enquote{journals,} \enquote{magazines,} and \enquote{newspapers,}
distinguished mainly by the way one formats the title of the review
-itself.  With the 16th edition's changes to the way titles are
-presented in the \textsf{authordate} style, users need to learn how to
-present this sort of material, which involves using an entry type
-(\textsf{review}) that wasn't necessary in the 15th edition.  The key
-rule is this: if a review has a separate, non-generic title (gibbard;
-\enquote{review of \ldots,} then you need an \textsf{article} entry,
-with or without the \texttt{magazine} \textsf{entrysubtype}, depending
-on the sort of publication containing the review.  If the only title
-is the generic \enquote{review of \ldots,} for example, then you'll
-need the \textsf{review} entry type, with or without this same
-\textsf{entrysubtype} toggle using \texttt{magazine}.  On
-\textsf{review} entries, see below.  (The curious reader will no doubt
-notice that the code for formatting any sort of review still exists in
-\textsf{article}, as it was initially designed for \textsf{biblatex
-  0.6}, but the current arrangement is somewhat simpler and therefore,
-I hope, better.)
+itself.  The key rule is this: if a review has a separate, non-generic
+like \enquote{review of \ldots,} then you need an \textsf{article}
+entry, with or without the \texttt{magazine} \textsf{entrysubtype},
+depending on the sort of publication containing the review.  If the
+only title is the generic \enquote{review of \ldots,} for example,
+then you'll need the \textsf{review} entry type, with or without this
+same \textsf{entrysubtype} toggle using \texttt{magazine}.  On
+\textsf{review} entries, see below.

\mylittlespace In the case of a review with a specific as well as a
generic title, the former goes in the \textsf{title} field, and the
@@ -5982,23 +8155,26 @@
the additional wrinkle that it can, if needed, replace the
\textsf{title} entirely, and this in, effectively, any entry type,
providing a fairly powerful, if somewhat complicated, tool for getting
-\textsc{Bib}\TeX\ to do what you want.  Here, however, if all you need
+\textsf{biblatex} to do what you want.  Here, however, if all you need
is a generic title like \enquote{review of \ldots,} then you want to
switch to the \textsf{review} type, where you can simply use the
\textsf{title} field for it.

-\mylittlespace \textsf{Biblatex-chicago} \colmarginpar{New!} now also,
-at the behest of Bertold Schweitzer, supports the \textsf{relatedtype}
-\mycolor{\texttt{reviewof}}, which allows you to use the
-\textsf{related} mechanism to provide information about the work being
-reviewed.  This may be particularly helpful if you need to cite
-multiple reviews of the same work, but in any case the usual
-distinction between \textsf{article} and \textsf{review} entries still
-holds, with the \textsf{related} entry's \textsf{title} providing the
-\textsf{titleaddon} in the former type and the \textsf{title} in the
-latter.  Please see section \ref{sec:authrelated} for further details.
+\mylittlespace \textsf{Biblatex-chicago} also, at the behest of
+Bertold Schweitzer, supports the \textsf{relatedtype}
+\texttt{reviewof}, which allows you to use the \textsf{related}
+mechanism to provide information about the work being reviewed.  In
+particular, it relieves you of the need to construct
+\textsf{titleaddon} or \textsf{title} fields like: \texttt{review of
+  \textbackslash mkbibemph\{Book Title\} by Author Name}, as the
+\textsf{related} entry's \textsf{title} automatically provides the
+\textsf{titleaddon} in the \textsf{article} type and the
+\textsf{title} in the \textsf{review} type, with the \textsf{related}
+mechanism providing the connecting string.  This may be particularly
+helpful if you need to cite multiple reviews of the same work; please
+see section \ref{sec:authrelated} for further details.

-\mylittlespace No less than nine more things need explication under
+\mylittlespace No less than ten more things need explication under
this heading.  First, since the \emph{Manual} specifies that what goes
into the \textsf{titleaddon} field of \textsf{article} entries stays
unformatted --- no italics, no quotation marks --- this plain style is
@@ -6013,25 +8189,25 @@
should go, as usual, in a \textsf{title} field, and the latter in
\textsf{titleaddon}.  As with reviews proper, if there is only the
generic title, then you want the \textsf{review} entry type.  (See
-14.203, 14.205, 14.208; morgenson:market, reaves:rosen.)
+14.191, 14.195--96; morgenson:market, reaves:rosen.)

-\mylittlespace Third, the 16th edition of the \emph{Manual} suggests
-that \enquote{unsigned newspaper articles or features are best dealt
-  with in text \ldots} (14.207).  As with newspaper or magazine
-articles in general, you can place \texttt{cmsdate=full} and
-\texttt{skipbib} into the \textsf{options} field to produce an
-augmented in-text citation whilst keeping this material out of the
-reference list.  If you do use the reference list, then the standard
-shorter citation will be sufficient, and in both cases the name of the
-periodical (in the \textsf{journaltitle} field) will be used in place
-of the missing author.  Just to clarify: in \textsf{article} or
-\textsf{review} entries, \textsf{entrysubtype} \texttt{magazine}, a
-missing \textsf{author} field results in the name of the periodical
-(in the \textsf{journaltitle} field) being used as the missing author.
+\mylittlespace Third, the \emph{Manual} suggests that
+\enquote{unsigned newspaper articles or features are best dealt with
+  in text \ldots} (14.199).  As with newspaper or magazine articles in
+general, you can place \texttt{cmsdate=full} and \texttt{skipbib} into
+the \textsf{options} field to produce an augmented in-text citation
+whilst keeping this material out of the reference list.  If you do use
+the reference list, then the standard shorter citation will be
+sufficient, and in both cases the name of the periodical (in the
+\textsf{journaltitle} field) will be used in place of the missing
+author.  Just to clarify: in \textsf{article} or \textsf{review}
+entries, \textsf{entrysubtype} \texttt{magazine}, a missing
+\textsf{author} field results in the name of the periodical (in the
+\textsf{journaltitle} field) being used as the missing author.
Without an \textsf{entrysubtype}, and assuming that no name whatsoever
can be found to put at the head of the entry, the \textsf{title} will
be used, not the \textsf{journaltitle}, or so I interpret the
-\emph{Manual} (14.175).  The default sorting scheme in
+\emph{Manual} (14.168).  The default sorting scheme in
\textsf{biblatex-chicago-authordate} considers the
\textsf{journaltitle} before the \textsf{title}, so if the latter
heads an entry you'll need a \textsf{sortkey}, just as you will if you
@@ -6045,7 +8221,7 @@
lakeforester:pushcarts, nyt:trevorobit, unsigned:ranke.)

\mylittlespace Fourth, Bertold Schweitzer has pointed out, following
-the \emph{Manual} (14.192), that while an \textsf{issuetitle} often
+the \emph{Manual} (14.183), that while an \textsf{issuetitle} often
has an \textsf{editor}, it is not too unusual for a \textsf{title} to
have, e.g., an \textsf{editor} and/or a \textsf{translator}.  In order
to allow as many permutations as possible on this theme, I have
@@ -6059,14 +8235,12 @@
rules still apply --- cf.\ \textsf{editor} and \textsf{editortype} in
section~\ref{sec:fields:authdate}, below.

-%\enlargethispage{\baselineskip}
-
\mylittlespace Fifth, in certain fields, just beginning your data with
a lowercase letter activates the mechanism for capitalizing that
-letter depending on its context within a list of references entry.
-This is less important in the author-date styles, where this
-information only turns up in the reference list and not in citations,
-but you can consult\,\textbf{\textbackslash autocap} in
+letter depending on its context within a reference list entry.  This
+is less important in the author-date styles, where this information
+only turns up in the reference list and not in citations, but you can
+consult\,\textbf{\textbackslash autocap} in
section~\ref{sec:formatting:authdate} below for all the details.  Both
the \textsf{titleaddon} and \textsf{note} fields are among those
treating their data this way, and since both appear regularly in
@@ -6091,34 +8265,66 @@
\textsf{note} field, but rather in \textsf{titleaddon} or perhaps

-\mylittlespace Seventh, I would suggest that if you wish to cite a
+\mylittlespace Seventh, I would suggest that if you wish to cite
+interviews but perhaps also news segments or other
+\enquote{journalistic} material, then the \textsf{article} type,
\textsf{entrysubtype} \texttt{magazine} is the place for it.  The name
-of the program would go in \textsf{journaltitle}, with the name of the
-episode in \textsf{title}.  The network's name goes into the
-\textsf{usera} field.  (8.185, 14.221; see bundy:macneil for an
-example of how this all might look in a .bib file.  Commercial
-recordings of such material would need one of the audiovisual entry
-types, probably \textsf{audio} or \textsf{video} [friends:leia], while
-recordings from archives fit best either into \textsf{online} or into
-\textsf{misc} entries with an \textsf{entrysubtype} [coolidge:speech,
-roosevelt:speech].)
+of the program as a whole would go in \textsf{journaltitle}, with the
+name of the episode in \textsf{title}.  The network's name goes into
+the \textsf{usera} field.  Of course, if the piece you are citing has
+only a generic name (an interview, for example), then the
+\textsf{review} type would be the best place for it (8.189, 14.213;
+see bundy:macneil for an example of how this all might look in a .bib
+file.)  Other sorts of broadcast, usually accessible through
+commercial recordings, would need one of the audiovisual entry types,
+probably \textsf{audio} (danforth:podcast) or \textsf{video}
+(friends:leia), while recordings from archives fit best either into
+\textsf{online} or into \textsf{misc} entries with an
+\textsf{entrysubtype} (coolidge:speech, roosevelt:speech).

-\mylittlespace Eighth, the 16th edition of the \emph{Manual}
-(14.243--6) specifies that blogs and other, similar online material
-should be presented like \textsf{articles}, with \texttt{magazine}
-\textsf{entrysubtype} (ellis:blog).  The title of the specific entry
-goes in \textsf{title}, the general title of the blog goes in
+\mylittlespace Eighth, the \emph{Manual} (14.208, 15.51) specifies
+that blogs and other, similar online material should be presented like
+\textsf{articles}, with \texttt{magazine} \textsf{entrysubtype}
+(ellis:blog), and needn't appear in a reference list at all, if you'd
+prefer to provide relevant details in the text.  I've attempted,
+however, to make \textsf{biblatex-chicago-authordate} as useful as
+possible when managing references to such sources, so I'll outline
+these facilities here.  The title of the specific entry goes in
+\textsf{title}, the general title of the blog goes in
\textsf{journaltitle}, and the word \enquote{\texttt{blog}} in the
\textsf{location} field (though you could just use special formatting
in the \textsf{journaltitle} field itself, which may sometimes be
-necessary).  Comments on blogs, with generic titles like
-\enquote{comment on} or \enquote{reply to,} need a \textsf{review}
-entry with the same \textsf{entrysubtype}.  Such comments make
-particular use of the \textsf{eventdate} and of the \textsf{nameaddon}
-fields; please see the documentation of \textbf{review}, below.
+necessary).  The 17th \colmarginpar{New!} edition specifies that
+\enquote{blogs that are part of a larger publication should include
+  the name of that publication.}  This usually involves a newspaper or
+magazine which also publishes various blogs on its website, and it
+means that such entries need a more general title than the
+\textsf{journaltitle}.  It's not standard \textsf{biblatex} or
+anything, but you can now put such information in \textsf{maintitle}
+(with \textsf{mainsubtitle} and \textsf{maintitleaddon}, if needed),
+but only in \textsf{article} and \textsf{review} entries with a
+\texttt{magazine} \textsf{entrysubtype} (amlen:hoot).

-\mylittlespace Finally, the special \textsf{biblatex} field
+\mylittlespace The \emph{Manual} (15.51) is even more emphatic about
+whole blogs (rather than individual posts) and comments on blogs not
+appearing in reference lists, but I've kept as many options open as
+possible, including fairly simple ways you can provide all the
+information needed in text citations alone.  To cite a whole blog,
+you'll need the \textsf{periodical} entry type, with a \textsf{title}
+instead of a \textsf{journaltitle}, along with a (possible)
+\textsf{maintitle} (amlen:wordplay).  Comments on blogs, with generic
+titles like \enquote{comment on} or \enquote{reply to,} need a
+\textsf{review} entry with the same \textsf{entrysubtype} (viv:amlen).
+Such comments make particular use of the \textsf{eventdate} and
+\textsf{nameaddon} fields, and also of specialized \textbf{customc}
+documentation of \textbf{customc}, \textbf{periodical}, and
+\textbf{review}, the \textsf{relatedtype} \mycolor{\texttt{commenton}}
+in section~\ref{sec:authrelated}, and the general discussion of online
+sources in the \textbf{online} documentation.
+
+\mylittlespace Ninth, the special \textsf{biblatex} field
\textsf{shortjournal} allows you to present shortened
\textsf{journaltitles} in \textsf{article}, \textsf{review}, and
\textsf{periodical} entries, as well as facilitating the creation of
@@ -6127,7 +8333,14 @@
section~\ref{sec:fields:authdate} for all the details on how this
works.

-% %\enlargethispage{-\baselineskip}
+\mylittlespace Finally, \colmarginpar{New!} the 17th edition (14.191)
+specifies that, for news sites carrying \enquote{stories as they
+  unfold, it may be appropriate to include a time stamp for an article
+  that includes one.}  You can provide this by using the standard
+\textsf{biblatex} time stamp format inside the \textsf{date} field,
+e.g., \texttt{2008-07-01T10:18:00}.  Since the \emph{Manual} prefers
+the standard time zone initialisms, a separate \textsf{timezone} field
+would be required if you want to provide one.

\mylittlespace If you're still with me, allow me to recommend that you
browse through \textsf{dates-test.bib} to get a feel for just how many
@@ -6137,24 +8350,17 @@
able to simplify these procedures somewhat, but with any luck the vast
majority of sources won't require knowledge of these onerous details.

-\mybigspace Arne \mymarginpar{\textbf{artwork}} Kjell Vikhagen has
-pointed out to me that none of the standard entry types were
-straightforwardly adaptable when referring to visual artworks.  The
-\emph{Manual} doesn't give any thorough specifications for such
-references, and indeed it's unclear that it believes it necessary to
-include them in the reference apparatus at all.  Still, it's easy to
-conceive of contexts in which a list of artworks studied might be
-desirable, and \textsf{biblatex} includes entry types for just this
-purpose, though the standard styles leave them undefined.  The two I
-chose to include in previous releases were \textsf{artwork} and
-\textsf{image}, the former intended for paintings, sculptures,
-etchings, and the like, the latter for photographs.  The 16th edition
-of the \emph{Manual} has modified its specifications for presenting
-photographs so that they are the same as for works in all other media.
-The \textsf{image} type, therefore, is now merely a clone of the
-\textsf{artwork} type, maintained mainly to provide backward
-compatibility for users migrating from the old specification to the
-current one.
+\mybigspace Arne \colmarginpar{\textbf{artwork}} Kjell Vikhagen pointed
+out to me that none of the standard entry types were straightforwardly
+adaptable when referring to visual artworks.  It's unclear that the
+\emph{Manual} (14.235) believes it necessary to include them in the
+reference apparatus at all, but it's easy to conceive of contexts in
+which a list of artworks studied might be desirable, and
+\textsf{biblatex} includes entry types for just this purpose, though
+the standard styles leave them undefined.  \textsf{Biblatex-chicago}
+defines both \textsf{artwork} and \textsf{image}, which are in fact
+now clones of each other, so you can use either of them indifferently,
+the distinction existing only for historical reasons.

\mylittlespace As one might expect, the artist goes in \textsf{author}
and the name of the work in \textsf{title}.  The \textsf{type} field
@@ -6167,49 +8373,86 @@
uses \textsf{biblatex's} automatic capitalization routines, so if the
first word only needs a capital letter at the beginning of a sentence,
use lowercase in the .bib file and let \textsf{biblatex} handle it for
-you.  (See \emph{Manual} 3.22, 8.193; leo:madonna, bedford:photo.)
+you.  (See \emph{Manual} 3.22, 8.198; leo:madonna, bedford:photo.)

-\mylittlespace As a final complication, the \emph{Manual} (8.193) says
+\mylittlespace The \colmarginpar{New!} 17th edition of the
+\emph{Manual} has included new information in some of its examples, so
+I have added 4 new fields to the driver.  Alongside the usual
+\textsf{date} for the creation of a work, you may also want to include
+the printing date of a particular exemplar of a photograph or a print.
+The system I have designed uses the \emph{earlier} of the
+and the \emph{later} to be the printing date.  The style will
+automatically prefix the printing date with the localized
+\cmd{bibstring} \mycolor{\texttt{printed}}, so if that's the wrong
+string entirely then you can define \textsf{userd} any way you like to
+change it.  If only \emph{one} of those two dates is available, it
+will always serve as a creation date.  Any date specification provided
+will always appear in full somewhere in the reference list entry,
+though sometimes that could be the plain year at the head of the
+entry.  This system, which is unlike other entry types, helps to avoid
+ambiguities in some situations.
+
+\mylittlespace One of the \emph{Manual's} examples is of a photograph
+appears late in the entry, after the \textsf{type}.  I have included
+the \textsf{howpublished} field so that you can give information about
+the periodical (meaning that you'll have to format the title yourself
+with \cmd{mkbibemph}), and the \textsf{eventdate} field for you to
+provide the date of publication (mccurry:afghangirl).
+
+\mylittlespace Depending on the presence or absence of these three
+date fields, and also on how you've set the \texttt{cmsdate} option,
+any of the three can appear in citations and at the head of reference
+list entries, allowing you to order entries by creation date, printing
+date, or publication date.  See the documentation of \textbf{date} on
+page~\pageref{sec:ad:date}, below, for all the complicated details.
+fields ostensibly replace most of the possible uses of the
+\textsf{pubstate} field in \textsf{artwork} entries, though this field
+continues to function here more or less as before, should you still
+require it.
+
+\mylittlespace As a final complication, the \emph{Manual} (8.198) says
that \enquote{the names of works of antiquity \ldots\,are usually set
in roman.}  If you should need to include such a work in the
reference apparatus, you can either define an \textsf{entrysubtype}
for an \textsf{artwork} entry --- anything will do --- or you could
-use the \textsf{image} type, or you could try the \textsf{misc} entry
-type with an \textsf{entrysubtype}.  Fortunately, in this instance the
-other fields in a \textsf{misc} entry function pretty much as in
-\textsf{artwork} or \textsf{image}.
+try the \textsf{misc} entry type with an \textsf{entrysubtype}.
+Assuming the complicated date handling I've just outlined isn't
+required for such a work, in this instance the other fields in a
+\textsf{misc} entry function pretty much as in \textsf{artwork}.

-\mybigspace Following \mymarginpar{\textbf{audio}} the request of
+\mybigspace Following \colmarginpar{\textbf{audio}} the request of
Johan Nordstrom, I have included three entry types, all undefined by
the standard styles, designed to allow users to present audiovisual
sources in accordance with the Chicago specifications.  The
-\emph{Manual's} presentation of such sources (14.263--273, 15.53),
-though admirably brief, seems to me somewhat inconsistent; the
-For the 15th edition I attempted to condense all the requirements into
-two entry types, but ended up relying on three.  For the 16th edition,
-in particular, I also need to include the \textbf{online} and even the
-\textbf{misc} entry types, which see, under the audiovisual rubric.  I
-shall attempt to delineate the main differences here, and though there
-are likely to be occasions when your choice of entry type is not
-maintain consistency.
+\emph{Manual's} presentation of such sources (14.261--68, 15.57),
+though admirably brief, seems to me somewhat inconsistent, though
+perhaps I'm merely unable to spot the important regularities.  The
+requiring the inclusion of the \textbf{article}, the \textbf{online},
+and even the \textbf{misc} entry types, which see, under the
+audiovisual rubric.  I shall attempt to delineate the main differences
+here, and though there are likely to be occasions when your choice of
+entry type is not obvious, at the very least \textsf{biblatex-chicago}

-\mylittlespace For users of the author-date styles, the 16th edition
-of the \emph{Manual} (15.53) \enquote{recommends a more comprehensive
-  approach to dating audiovisual materials than in previous editions,}
-meaning that nearly all such entries will have some sort of dating
-information and will therefore fit better stylistically with other
-references.  In particular, \enquote{the date of the original
-  recording should be privileged in the citation.}  Guidance for
-supplying dates for this class of material will be found below under
-the different entry types in use, though it will also be worthwhile to
-look at the documentation of \textsf{date}, \textsf{eventdate},
-\textsf{origdate}, and \textsf{urldate}, in
+\mylittlespace For users of the author-date styles, the 17th edition
+of the \emph{Manual} continues to emphasize the need to provide dating
+information for audiovisual materials (14.263), meaning that nearly
+all such entries will have some such information and will therefore
+fit better, stylistically, with other author-date references.  In
+particular, it continues to recommend that \enquote{the date of the
+  original recording should be privileged in the citation} (15.57).
+Guidance for supplying dates for this class of material will be found
+below under the different entry types in use, though it will also be
+worthwhile to look at the documentation of \textsf{date},
+\textsf{eventdate}, \textsf{origdate}, and \textsf{urldate}, in
section~\ref{sec:fields:authdate}, below.  The \emph{Manual} continues
to suggest, also, that \enquote{it is often more appropriate to list
such materials in running text and group them in a separate section
-  or discography}.
+  or discography.}

\mylittlespace The \textbf{music} type is intended for all musical
recordings that do not have a video component.  This means, for
@@ -6217,23 +8460,34 @@
and tapes.  The \textbf{video} type includes most visual media,
whether it be films, TV shows, tapes and DVDs of the preceding or of
any sort of performance (including music), or online multimedia.  The
-\emph{Manual's} treatment (14.280) of the latter suggests that online
+\emph{Manual's} treatment (14.267) of the latter suggests that online
video excerpts, short pieces, and interviews should generally use the
-The \textbf{audio} type, our current concern, fills gaps in the
-others, and presents its sources in a more \enquote{book-like} manner.
-Published musical scores need this type --- unpublished ones would use
-\textsf{misc} with an \textsf{entrysubtype} (shapey:partita) --- as do
-such favorite educational formats as the slideshow and the filmstrip
-(greek:filmstrip, schubert:muellerin, verdi:corsaro).  The
-\emph{Manual} (14.277--280) sometimes uses a similar format for audio
-books (twain:audio), though, depending on the sorts of publication
-facts you wish to present, this sort of material may fall under
-\textsf{music} (auden:reading).  Dated audio recordings that are part
-of an archive, online or no, may be presented either in an
-\textsf{online} or in a \textbf{misc} entry with an
-\textsf{entrysubtype}, the latter sometimes requiring extra formatting
-in the \textsf{title} field (coolidge:speech, roosevelt:speech).
+\textbf{online} type (horowitz:youtube, pollan:plant) or the
+\textbf{article} type (harwood:biden, kessler:nyt), depending on
+whether the pieces originate from an identifiably
+\enquote{journalistic} outlet.  The \textbf{audio} type, our current
+concern, fills gaps in the others, and presents its sources in a more
+\enquote{book-like} manner.  Published musical scores need this type
+--- unpublished ones would use \textsf{misc} with an
+\textsf{entrysubtype} (shapey:partita) --- as do \mycolor{podcasts}
+and such favorite educational formats as the slideshow and the
+filmstrip (danforth:podcast, greek:film\-strip, schubert:muellerin,
+verdi:corsaro).  The \emph{Manual} (14.264) sometimes uses a similar
+format for audio books (twain:audio), though, depending on the sorts
+of publication facts you wish to present, this sort of material may
+fall under \textsf{music} (auden:reading).  Dated audio recordings
+that are part of an archive, online or no, may be presented either in
+an \textbf{online} or in a \textbf{misc} entry with an
+\textsf{entrysubtype}, the difference mainly being in just how closely
+associated the \textsf{date} will be with the \textsf{title}
+opposed to podcasts) pose something of a conundrum.  Interviews and
+other sorts of \enquote{journalistic} material fit well into
+\textsf{article} or \textsf{review} entries (14.213), but other sorts
+of broadcast are not well represented in the \emph{Manual's} examples
+(8.189), and what little there is suggests that, counter-intuitively,
+the \textsf{video} type is the best fit, as it is well equipped to

\mylittlespace Once you've accepted the analogy of composer to
\textsf{author}, constructing an \textsf{audio} entry should be fairly
@@ -6246,15 +8500,38 @@
\textsf{date}, and a \textsf{location}, there may also be a
\textsf{booktitle} and/or a \textsf{maintitle} --- see
schubert:muellerin for an entry that uses all three in citing one song
-from a cycle.  If the medium in question needs specifying, the
-\textsf{type} field is the place for it.  Finally, the
-\textsf{titleaddon} field can specify functions for which
-\textsf{biblatex-chicago} provides no automated handling, e.g., a
-librettist (verdi:corsaro).
+from a cycle.  (As with the \textsf{music} and \textsf{video} types,
+you can cite an individual piece separate from any large collection by
+using the \textsf{title} field and by defining an
+\textsf{entrysubtype}, which will stop \textsf{biblatex-chicago}
+italicizing your \textsf{title} in the absence of a
+\textsf{booktitle}.)  If the medium in question needs specifying, the
+\textsf{type} field is the place for it.  Please note, also, that
+while the \textsf{titleaddon} field can still specify creative or
+editorial functions for which \textsf{biblatex-chicago} provides no
+automated, localized handling, you can also now provide the string you
+need in an \textsf{editor[abc]type} field, e.g.,
+\enquote{\texttt{libretto by}} (verdi:corsaro).

-\mybigspace This \mymarginpar{\textbf{book}} is the standard
+\mylittlespace For \colmarginpar{New!} podcasts, newly covered by the
+17th edition (14.267), the \textsf{audio} type provides the nearest
+analogue I could find, and in general most of the data should fit
+comfortably into the fields already discussed above, the episode name
+in \textsf{title} and the name of the podcast in \textsf{booktitle},
+for starters.  Two details, however, need mentioning: first, the
+\textsf{note} field as the place to specify that it is a podcast, and
+the \textsf{eventdate} field for the date of publication of the
+specific episode (\textsf{title}) cited, which appears in close
+association with that \textsf{title}.  Indeed, the \textsf{eventdate}
+field helps \textsf{biblatex-chicago} know that the \textsf{audio}
+entry is a podcast episode, and helps it construct the entry
+appropriately (danforth:podcast).
+
+\enlargethispage{\baselineskip}
+
+\mybigspace This \colmarginpar{\textbf{book}} is the standard
\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but the package
-can provide automatically abbreviated references in the reference list
+can automatically provide abbreviated references in the reference list
when you use a \textsf{crossref} or an \textsf{xref} field.  The
functionality is not enabled by default, but you can enable it in the
preamble or in the \textsf{options} field using the
@@ -6261,7 +8538,11 @@
\texttt{booklongxref} option.  Please see \textbf{crossref} in
section~\ref{sec:fields:authdate} and \texttt{booklongxref} in
section~\ref{sec:authpreset}, below.  Also, cf.\ harley:ancient:cart,
-harley:cartography, and harley:hoc for how this might look.
+harley:cartography, and harley:hoc for how this might look.  The
+\textsf{book} type is useful also to present multimedia app content,
+the added fields \textsf{version} and \textsf{type} providing
+information about the app's version and about the system on which it
+runs (14.268, 15.57; angry:birds).

\mybigspace This \mymarginpar{\textbf{bookinbook}} type provides the
means of referring to parts of books that are considered, in other
@@ -6275,21 +8556,16 @@
abbreviated references in the reference list, though this isn't the
section~\ref{sec:fields:authdate} and \texttt{booklongxref} in
-section~\ref{sec:preset:authdate}, below.  (Cf.\ \emph{Manual} 14.114,
-14.127, 14.130; bernhard:boris, bernhard:ritter, and
+section~\ref{sec:preset:authdate}, below.  (Cf.\ \emph{Manual} 14.109,
+14.122, 14.124; bernhard:boris, bernhard:ritter, and
bernhard:themacher for the abbreviating functionality; also
-euripides:orestes, plato:republic:gr.)
+euripides:orestes [treated differently in 14.122 and 14.124],
+plato:republic:gr.)

-\mylittlespace \textbf{NB}: The Euripides play receives slightly
-different presentations in 14.127 and 14.130.  Although the
-specification is very detailed, it doesn't eliminate all choice or
-variation.  Using a system like \textsc{Bib}\TeX\ should help to
-maintain consistency.
-
\mybigspace This \mymarginpar{\textbf{booklet}} is the first of two
entry types --- the other being \textsf{manual}, on which see below
--- which are traditional in \textsc{Bib}\TeX\ styles, but which the
-\emph{Manual} (14.249) suggests may well be treated basically as
+\emph{Manual} (14.220) suggests may well be treated basically as
books.  In the interests of backward compatibility,
\textsf{biblatex-chica\-go-authordate} will so format such an entry,
which uses the \textsf{howpublished} field instead of a standard
@@ -6309,90 +8585,105 @@
harley:ancient:cart, harley:cartography, and harley:hoc for how this
might look.

-\mybigspace This \mymarginpar{\textbf{customa}} entry type is
-obsolete, and any such entries in your .bib file will trigger an
-error.  Please use the standard \textsf{biblatex} \textbf{letter} type
-
-%%\enlargethispage{-\baselineskip}
-
-\mybigspace This \mymarginpar{\textbf{customb}} entry type is
-obsolete, and any such entries in your .bib file will trigger an
-error.  Please use the standard \textsf{biblatex} \textbf{bookinbook}
-
-\mybigspace This \mymarginpar{\textbf{customc}} entry type allows you
+\mybigspace This \colmarginpar{\textbf{customc}} entry type allows you
to include alphabetized cross-references to other, separate entries in
the bibliography, particularly to other names or pseudonyms, as
recommen\-ded by the \emph{Manual}.  (This is different from the usual
\textsf{crossref}, \textsf{xref}, \textsf{userf}, and \textsf{related}
mechanisms, all primarily designed to include cross-references to
-other works.  Cf.\ 14.84,86).  In the 15th edition's specification of
-the author-date style, it allowed you, in particular, to include the
-expansions of abbreviations and shorthands --- usually of corporate
-\textsf{authors} --- \emph{inside} the list of references itself,
-rather than in the list of shorthands.  The 16th edition of the
-\emph{Manual} (15.36), however, has a different specification for such
-corporate authors.  As in the old specification, the shorthand appears
-in citations and at the head of the entry in the list of references,
-but its expansion now appears within parentheses \emph{directly after}
-the shorthand, i.e., \emph{within} the same entry.  This means you no
-longer need the \textsf{customc} entry for shorthands of this sort.
-(See \textsf{shorthand}, below; bsi:abbreviation, iso:electrodoc.)
-
-specification (14.84,86, 15.34), the alphabetized cross-references
+other works.  Cf.\ 14.81--82, 15.35).  I should add immediately that,
+as I read the specification, the alphabetized cross-references
provided by \textsf{customc} are particularly encouraged, bordering on
required, when a reference list \enquote{includes two or more works
following entries in \textsf{dates-test.bib} show one way of
-crea\-sey:mor\-ton:hide, ashe:crea\-sey, york:crea\-sey and
-mor\-ton:crea\-sey.  In these latter cases, you would need merely to
-place the pseudo\-nym in the \textsf{author} field, and the author's
-real name, under which his or her works are presented in the
-bibliography, in the \textsf{title} field.  To make sure the
-cross-reference also appears in the bibliography, you can either
-manually include the entry key in a \cmd{nocite} command, or you can
-put that entry key in the \textbf{userc} field in the main .bib entry,
-in which case \textsf{biblatex-chicago} will print the expanded
-abbreviation if and only if you cite the main entry.  (Cf.\
-\textsf{userc}, below.)
+creasey:morton:hide, ashe:creasey, york:creasey and morton:creasey.
+In these latter cases, you would need merely to place the pseudonym in
+the \textsf{author} field, and the author's real name, under which his
+or her works are presented in the bibliography, in the \textsf{title}
+field.  To make sure the cross-reference also appears in the
+bibliography, you can either manually include the entry key in a
+\cmd{nocite} command, or you can put that entry key in the
+\textbf{userc} field in the work's main .bib entry, in which case
+\textsf{biblatex-chicago} will print the cross-reference if and only
+if you cite the main work.  (Cf.\ \textsf{userc}, below.)

\mylittlespace Under ordinary circumstances, \textsf{biblatex-chicago}
will connect the two parts of the cross-reference with the word
\enquote{\emph{See}} --- or its equivalent in the document's language
---- in italics.  If you wish to present the cross-reference
-differently, you can put the connecting word(s) into the
+--- in italics.  If you wish to present it differently, you can put
+the connecting word(s) into the \textsf{nameaddon} field.

\mylittlespace Finally, you may need to use this entry type if you
wish to include a comment inside the parentheses of a citation, as
-specified by the \emph{Manual} (15.23).  If you have a
+specified by the \emph{Manual} (15.24).  If you have a
\textsf{postnote}, then you can manually provide the punctuation and
comment there, e.g., \cmd{autocite[4; the unrevised
trans.]\{stendhal:parma\}}.  Without a \textsf{postnote}, you have
-two solutions.  You can enable the \texttt{postnotepunct} option, which
-allows you simply to type \cmd{autocite[; the unrevised
-  trans.]\{stendhal:parma\}}, or you can continue to use a separate
-\textsf{misc} or \textsf{customc} entry containing just the text of
-the comment in the \textsf{title} field, \textsf{entrysubtype}
-\texttt{classical}, and \textsf{options} \texttt{skipbib}.  An
-\cmd{autocites} command calling both the main text and the comment
-then does the trick, e.g.,
-\cmd{autocites\{chica\-go:manual\}\{chicago:comment\}}.  Cf.\
+two solutions.  You can enable the \texttt{postnotepunct} option,
+which allows you simply to type \cmd{autocite[; the unrevised
+  trans.]\{stendhal:parma\}}, or you can use a separate
+\textsf{customc} entry containing just the text of the comment in the
+\textsf{title} field, \textsf{entrysubtype} \texttt{classical}, and
+\textsf{options} \texttt{skipbib}.  An \cmd{autocites} command calling
+both the main text and the comment then does the trick, e.g.,
+\cmd{autocites\{chicago:manual\}\{chicago:comment\}}.  Cf.\
\texttt{postnotepunct} in section~\ref{sec:authuseropts}, below.

-\mybigspace This \mymarginpar{\textbf{image}} entry type, left
-undefined in the standard styles, was in previous releases of
-\textsf{bibla\-tex-chicago} intended for referring to photographs, but
-the 16th edition of the \emph{Manual} has changed its specifications
-for such works, which are now treated the same as works in all other
-media.  This means that this entry type is now a clone of the
-\textsf{artwork} type, which see.  I retain it here as a convenience
-for users migrating from the old to the new specification.  (See 3.22,
-8.193; bedford:photo.)
+\mylittlespace For \colmarginpar{New!} its 17th edition, the
+\emph{Manual} has provided a more detailed treatment of online
+comments, whether on blogs, mailing lists, or social media posts
+(15.50--52).  Such comments \enquote{are cited only in the text, in
+  reference to the related post,} an arrangement most easily created
+using \textsf{customc} entries referencing the main post.  The new
+\mycolor{\texttt{commenton}} \texttt{relatedtype} in \textsf{online}
+and \textsf{review} entries attempts to automate this for you,
+creating a separate \textsf{customc} entry to be used in an
+\cmd{autocites} command together with the comment's own entry.  Please
+see the details of this in the \textbf{online} and \textbf{review}
+entry types, below, and in the \mycolor{\texttt{commenton}} docs in
+section~\ref{sec:authrelated}.  Cf.\ also ac:comment, diaz:surprise,
+ellis:blog, licis:diazcomment, and the associated
+automatically-created entries ellis:blog-customc and
+diaz:surprise-customc.

+\mybigspace This \colmarginpar{\textbf{dataset}} entry type, new in
+\textsf{biblatex} 3.13, allows you to cite scientific databases, for
+which the \emph{Manual} (14.257) presents some rather specific, if
+brief, instructions.  To construct your entry, you can put the name of
+the database into \textsf{author}, a \enquote{descriptive phrase or
+  record locator} in the \textsf{title} field, and if there's a
+specific accession number needed beyond the record locator you can put
+it into the \textsf{number} field, with the \textsf{type} field
+reserved to help explain what sort of \textsf{number} is involved.
+The \textsf{howpublished} field can also be used to provide extra
+descriptive detail about the \textsf{number}, if needed.  More
+generally, a \textsf{url} will locate the database as a whole and a
+\textsf{urldate} will specify the date you accessed it.  If, for some
+reason, an additional date is relevant, then the \textsf{date} field
+is available, while the \textsf{pubstate} field will appear before the
+\textsf{date} in case you need to modify the latter.  (See 14.257;
+genbank:db, nasa:db.)  Given that usually the only relevant date in
+such entries is the access date, which means that they would usually
+have \enquote{n.d.}\ at the head of reference-list entries and in
+citations, I have thought it sensible to treat
+\mycolor{\textsf{dataset}} entries by default as author-title instead
+of author-date in citations, and to stop the printing of
+\enquote{n.d.}\ in reference lists just as in \textsf{misc} entries.
+You can shorten the component parts of the author-title citation using
+the usual \textsf{shortauthor}, \textsf{shorthand}, and/or
+\textsf{shorttitle} fields, and you can also restore author-date
+formatting to these entries by setting the
+\mycolor{\texttt{authortitle}} option to \texttt{false} either in
+individual entries or in the preamble for all examples of the entry
+type.
+
+
+\mybigspace This \mymarginpar{\textbf{image}} entry type is now a
+clone of the \textsf{artwork} type, which see.  I retain it here for
+historical reasons (See 3.22, 8.198; bedford:photo.)
+
\mybigspace These \mymarginpar{\textbf{inbook}\\\textbf{incollection}}
two standard \textsf{biblatex} types have very nearly identical
formatting requirements as far as the Chicago specification is
@@ -6403,27 +8694,23 @@
which forms a self-contained unit with a distinct author and its own
title.}  The \textsf{title} of both sorts will be placed within
quotation marks, and in general you can use either type for most
-material falling into these categories.  There was an important
-difference between them, as in previous releases of
-\textsf{biblatex-chicago} it was only in \textsf{incollection} entries
-that I implemented the \emph{Manual's} recommendations for
-space-saving abbreviations in the reference list when you cite
-multiple pieces from the same \textsf{collection}.  These
-abbreviations are activated by default when you use the
-\textsf{crossref} or \textsf{xref} field in \textsf{incollection}
-entries \emph{and} in \textsf{inbook} entries, because although the
-\emph{Manual} (14.113) here specifies a \enquote{multiauthor book,} at
-least for the notes \&\ bibliography style, I believe the distinction
-between the two is fine enough, and the author-date discussion in
-15.37 general enough, to encourage similar treatments.  (For more on
-this mechanism see \textbf{crossref} in
-section~\ref{sec:fields:authdate}, below, and the option
+material falling into these categories.  I have, in both types,
+implemented the \emph{Manual's} recommendations for space-saving
+abbreviations in the reference list when you cite multiple pieces from
+the same \textsf{collection}.  These abbreviations are activated by
+default when you use the \textsf{crossref} or \textsf{xref} field in
+\textsf{incollection} entries \emph{and} in \textsf{inbook} entries,
+because although the \emph{Manual} (15.42) here specifies a
+\enquote{multiauthor book,} I believe the distinction between the two
+is fine enough, and the discussion general enough, to encourage
+similar treatments.  (For more on this mechanism see \textbf{crossref}
+in section~\ref{sec:fields:authdate}, below, and the option
that it is also active by default in \textsf{letter} and
\textsf{inproceedings} entries.)  If the part of a book to which you
are referring has had a separate publishing history as a book in its
own right, then you may wish to use the \textsf{bookinbook} type,
-instead, on which see above.  (See \emph{Manual} 14.111--114, 15.37;
+instead, on which see above.  (See \emph{Manual} 14.106--9, 15.42;
\textsf{inbook}:\,ashbrook:brain, phibbs:diary, will:cohere;
\textsf{incollection}:\,centi\-nel:letters, contrib:contrib,
sirosh:visualcortex; ellet:galena, keating:dearborn, and
@@ -6431,6 +8718,8 @@
demonstrate the use of the \textsf{crossref} field with its attendant
abbreviations in the list of references.)

+\enlargethispage{\baselineskip}
+
\mylittlespace \textbf{NB}: The \emph{Manual} suggests that, when
referring to a chapter, one use either a chapter number or the
inclusive page numbers, not both.  In-text citations, of course,
@@ -6437,14 +8726,12 @@
require any \textsf{postnote} field to specify if it is a whole
chapter to which you are referring.

-%\enlargethispage{-\baselineskip}
-
\mybigspace This \mymarginpar{\textbf{inproceedings}} entry type works
pretty much as in standard \textsf{biblatex}.  Indeed, the main
differences between it and \textsf{incollection} are the lack of an
\textsf{edition} field and the possibility that an
\textsf{organization} may be cited alongside the \textsf{publisher},
-even though the \emph{Manual} doesn't specify its use (14.226).
+even though the \emph{Manual} doesn't specify its use (14.217).
Please note, also, that the \textsf{crossref} and \textsf{xref}
mechanism for shortening citations of multiple pieces from the same
\textsf{proceedings} is operative here, just as it is in
@@ -6453,19 +8740,18 @@
\texttt{longcrossref} in section~\ref{sec:authpreset}, below, for more
details.

-\paragraph*{\protect\mymarginpar{\textbf{inreference}}}
+\paragraph*{\protect\colmarginpar{\textbf{inreference}}}
This entry type is aliased to \textsf{incollection} in the standard
-styles, but the \emph{Manual's} requirements for the notes \&\
-bibliography style prompted a thoroughgoing revision.  Unfortunately,
-instructions for the author-date style are considerably less copious,
-so parts of what follows are my best guess at following the
-specification (14.247--248).
+styles, but the \emph{Manual's} requirements prompted a thoroughgoing
+revision.  Instructions for the author-date style are not copious, so
+what follows is my best guess at following the specification
+(14.232--34).

-\mylittlespace One thing, at least, seems clear.  If your reference
-work can easily or conveniently be presented like a regular book, that
-is, with an author or editor, a year of publication, and a title, and
-if you you will be citing it by page or section number, then you
+easily or conveniently be presented like a regular author-date book,
+that is, with an author or editor, a year of publication, and a title,
+and if you will be citing it by page or section number, then you
should almost certainly simply choose the \textsf{book} entry type for
your .bib entry. (Cf.\ mla:style, schellinger:novel, times:guide.  The
latter was presented as an \textsf{inreference} entry for the notes
@@ -6474,29 +8760,31 @@
in the list of references, then it seemed better just to choose a
\textsf{book} entry for the author-date styles.)

-\mylittlespace If you simply cannot make your source fit the template
-for a \textsf{book}, then you may need to use the \textsf{inreference}
-type, the main feature of which is the \textsf{lista} field, which you
-use to present citations from \enquote{alphabetically arranged} works
-by named article rather than by page number.  You should present these
-article names just as they appear in the work, separated by the
-keyword \enquote{\texttt{and}} if there is more than one, and
-\textsf{biblatex-chicago-authordate} will provide the appropriate
-prefatory string (\texttt{s.v.}, plural \texttt{s.vv.}), and enclose
-each in its own set of quotation marks (times:guide).  More relevant
-to the author-date styles is the fact that the \textsf{postnote} field
-works the same way in \textsf{inreference} entries, the only
-limitation on this system being that this field, unlike
-\textsf{lista}, is not a list, and therefore for the formatting to
-work correctly you can only put one article name in it.  In the case
-of \enquote{[w]ell-known reference books, such as major dictionaries
-  and encyclopedias,} you are encouraged not to include them in the
-list of references, so the \textsf{lista} field actually may be of
-less use than this special formatting of \textsf{postnote}.  You may
-want to look at ency:britannica, where only a (carefully-formatted)
-\textsf{shorttitle} and an \textsf{options} field are necessary to
-allow you to produce in-text citations that look like (\emph{Ency.\
-  Brit.}\ 15th ed., s.v. \enquote{Article}).
+\mylittlespace If your source simply doesn't fit the standard
+author-date template for a \textsf{book}, most especially if it is a
+\enquote{well-known} reference work, then you may need to use the
+\textsf{inreference} type, the main feature of which is the
+\textsf{lista} field, which you use to present citations from
+\enquote{alphabetically arranged} works by named article rather than
+by page number.  You should present these article names just as they
+appear in the work, separated by the keyword \enquote{\texttt{and}} if
+there is more than one, and \textsf{biblatex-chicago-authordate} will
+provide the appropriate prefatory string (\texttt{s.v.}, plural
+\texttt{s.vv.}), and enclose each in its own set of quotation marks
+(times:guide).  More relevant to the author-date styles is the fact
+that the \textsf{postnote} field works the same way in
+\textsf{inreference} entries, the only limitation on this system being
+that this field, unlike \textsf{lista}, is not a list, and therefore
+for the formatting to work correctly you can only put one article name
+in it.  In the case of \enquote{[w]ell-known reference books, such as
+  major dictionaries and encyclopedias,} you are encouraged not to
+include them in the list of references, so the \textsf{lista} field
+actually may be of less use than this special formatting of
+\textsf{postnote}.  You may want to look at ency:britannica, where
+only a (carefully-formatted) \textsf{shorttitle}, a \textsf{year}, and
+an \textsf{options} field are necessary to allow you to produce
+in-text citations that look like (\emph{Ency.\ Brit.}, 15th ed. 1985,
+s.v. \enquote{Article}).

\mylittlespace If it seems appropriate to include such a work in the
list of references, perhaps because the work is not so well known that
@@ -6504,32 +8792,47 @@
it is an online work, which requires you to provide a \textsf{urldate}
(see below), be aware that the contents of the \textsf{lista} field
will also be presented there, which may not be what you want.  A
-separate \textsf{inreference} or \textsf{reference} entry might solve
-this problem, but you may also need a \textsf{sortkey} field to ensure
-proper alphabetization, as \textsf{biblatex} will attempt to use an
-\textsf{editor} or \textsf{author} name, if either is present.  In a
-typical \textsf{inreference} entry, very few fields are needed, as
-\enquote{the facts of publication are often omitted, but the edition
-  (if not the first) must be specified.}  In practice, this means a
-\textsf{title} and possibly an \textsf{edition} field.  The
-\textsf{author} field holds the author of the specific article (in
-\textsf{lista}), not the author of the \textsf{title} as a whole.
-This name will be printed in parentheses after the entry's name
-(grove:sibelius).
+separate \textsf{inreference} or \textsf{reference} entry might well
+solve this problem.  In a typical \textsf{inreference} entry very few
+fields are needed, but \enquote{if a physical edition is cited, not
+  only the edition number (if not the first) but also the date the
+  volume or set was issued must be specified.}  In practice, this
+means a \textsf{title}, \textsf{date}, and possibly an
+\textsf{edition} field.  The \textsf{author} field holds the author of
+the specific article (in \textsf{lista}), not the author of the
+\textsf{title} as a whole.  This name will be printed in parentheses
+after the alphabetized entry's title (grove:sibelius).

-\mylittlespace All of these rules apply to online reference works, as
-well, for which you need to provide not only a \textsf{url} but also,
-always, a \textsf{urldate}, as these sources are in constant flux
-(wikiped:bibtex, grove:sibelius).  The author-date styles will
-automatically use this as the identifying date in citations and the
-list of references, assuming a more conventional \textsf{date} isn't
-available.  Please note, however, that the automatic provision of the
-\enquote{n.d.} abbreviation, in the absence of any sort of date
-whatsoever, has been turned off for \textsf{inreference} entries, as
-for \textsf{misc} and \textsf{reference} entries.
+\mylittlespace Finally, all of these rules apply to online reference
+works, along with a few more.  The \colmarginpar{New!} 17th edition of
+the \emph{Manual} now allows, \enquote{subject to editorial
+  discretion,} the alternative treatment of an online reference work
+which \enquote{does not have (and never had) a printed counterpart}
+(14.206, 14.233).  In effect this means that it can be treated more
+like an \textsf{online} entry than a \textsf{book}, its \textsf{title}
+therefore in plain roman rather than in italics.  You can achieve this
+in \textsf{inreference} entries by providing an \textsf{entrysubtype}
+in the entry.  Online reference works need not only a \textsf{url} but
+also, always, a \textsf{urldate} (instead of a \textsf{date)}, as
+these sources are in constant flux.  When that flux is of a
+particularly high frequency, as with Wikipedia, then a time stamp may
+also be needed.  You can provide this in the \textsf{urldate} field
+itself, using the standard \textsf{biblatex} format, e.g.,
+\texttt{2008-07-01T10:18:00}.  It is
+\colmarginpar{\texttt{urlstamp=true}} possible to turn off the
+printing of the \textsf{urltime} with the new
+\mycolor{\texttt{urlstamp}} option, which is set to \texttt{true} by
+default, but which can be changed in your preamble for the whole
+document, for specific entry types, or in the \textsf{options} field
+of specific entries (wikiped:bibtex, grove:sibelius).  In keeping with
+the rules of the 17th edition, changed since the 16th, any
+\textsf{inreference} entry with no date, or with only an access date,
+as opposed to a revision date or another, more traditional publishing
+date, will use the \texttt{nodate} abbreviation at the head of the
+entry and in citations (15.44, 15.50).

\mybigspace I
-\colmarginpar{\textbf{jurisdiction}\\\textbf{legal}\\\textbf{legislation}}
+\mymarginpar{\textbf{jurisdiction}\\\textbf{legal}\\\textbf{legislation}}
document these three types in section~\ref{sec:legal} below, both
because they all follow the specifications of the \emph{Bluebook}
instead of the \emph{Manual}, and also because they are the only entry
@@ -6540,7 +8843,7 @@
to be used for citing letters, memoranda, or similar texts, but
\emph{only} when they appear in a published collection.  (Unpublished
material of this nature needs a \textsf{misc} entry, for which see
-below.)  The author-date specification (15.40), however, recommends
+below.)  The author-date specification (15.43), however, recommends
against individual letters appearing in a list of references,
suggesting instead that you put the whole published collection in a
\textsf{book} entry and use a notice in the text to specify the letter
@@ -6547,10 +8850,10 @@
(white:total).

\mylittlespace If you absolutely must include individual letters in
-the list of references, for whatever reason, then the instructions
-above for the notes \&\ bibliography style in
-section~\ref{sec:entrytypes}, s.v.\ \enquote{\textsf{letter,}} should
-get you started.  There are a few wrinkles, related to date
+the list of references, for whatever reason, then please consult the
+instructions above for the notes \&\ bibliography style in
+section~\ref{sec:entrytypes}, s.v.\ \enquote{\textsf{letter,}} which
+cover all the details.  There are a few wrinkles, related to date
specifications, that I shall attempt to clarify here.  If you look at
white:ross:memo and white:russ, you'll see two letters from the same
published collection, both written in the same year.  You can simply
@@ -6559,24 +8862,14 @@
and \textsf{biblatex} will use the \textsf{origyear} as the
\textsf{labelyear}, putting it at the head of the entry and in the
citation, and also ensuring that the letters \texttt{a,b,c} are
-appended to disambiguate the two sources.  You no longer need anything
-in the \textsf{options} field at all, thanks to the way
-\cmd{DeclareLabeldate} works through the possibilities and finds a
-date to head the entry.  In this case, it works because we are using
-the \textsf{xref} mechanism to refer to the whole published collection
-(white:total), so a separate citation of that entry provides the
-\textsf{date} for the shortened cross-reference included in the list
-of references, and the \textsf{letter} entry never sees that
-\textsf{date} at all.
+appended to disambiguate the two sources.  In this case, it works
+because we are using the \textsf{xref} mechanism to refer to the whole
+published collection (white:total), so a separate citation of that
+entry provides the \textsf{date} for the shortened cross-reference
+included in the list of references, and the \textsf{letter} entry
+never sees that \textsf{date} at all.  (Cf.\ also the documentation of
+the \textsf{date} field in section~\ref{sec:fields:authdate} below.)

-%\enlargethispage{\baselineskip}
-
-\mylittlespace If this all seems clear as mud, I'm not surprised, but
-let me suggest that you experiment with the different date settings to
-see what kinds of effects they have on the final result, and also read
-the documentation of the \textsf{date} field in
-section~\ref{sec:fields:authdate} below.
-
\mybigspace This \mymarginpar{\textbf{manual}} is the second of two
traditional \textsc{Bib}\TeX\ entry types that the \emph{Manual}
suggests formatting as books, the other being \textsf{booklet}. As
@@ -6586,11 +8879,13 @@
\textsf{organization} producing the manual will be provided both as
author and as publisher.  (You can give a shortened form of the
\textsf{organization} in the \textsf{shortauthor} field for text
-citations, if needed.)  Of course, if you were to use a \textsf{book}
-entry for such a reference, then you would need to define both
-\textsf{author} and \textsf{publisher} using the name you here might
-have put in \textsf{organization}.  (See 14.92; chicago:manual,
-dyna:browser, natrecoff:camera.)
+citations, if needed, or use the \textsf{shorthand} field.)  Of
+course, if you were to use a \textsf{book} entry for such a reference,
+then you would need to define both \textsf{author} and
+\textsf{publisher} using the name you here might have put in
+\textsf{organization}.  (See 14.84; chicago:manual, dyna:browser,
+natrecoff:camera.  Cp.\ also the new \mycolor{\textbf{standard}} entry
+type.)

\paragraph*{\protect\mymarginpar{\textbf{misc}}}
@@ -6612,51 +8907,70 @@
\textsf{misc} type provides a means for citing unpublished letters,
memoranda, private contracts, wills, interviews, and the like, making
it something of an unpublished analogue to the \textsf{letter},
-\textsf{article}, and \textsf{review} entry types (which see).
-Typically, such an entry will cite part of an archive, and equally
-typically the text cited won't have a specific title, but only a
-generic one, whereas an \textsf{unpublished} entry will ordinarily
-have a specific author and title, and won't come from a named archive.
-The \textsf{misc} type with an \textsf{entrysubtype} defined is the
-least formatted of all those specified by the \emph{Manual}, so titles
-are in plain text by default.  It is quite possible, though somewhat
-unusual, for archival material to have a specific title, rather than a
-generic one.  In these cases, you will need to enclose the title
-inside a \cmd{mkbibquote} command manually.  Cf.\ roosevelt:speech,
-shapey:partita.  As a rule, and as with the \textsf{letter} type, the
-\emph{Manual} (15.49) suggests that the list of references will
+\textsf{article}, and \textsf{review} entry types (which see).  It
+also works well for presenting online audio pieces, particularly dated
+ones, like speeches.  Typically, such an entry will cite part of an
+archive, and equally typically the text cited won't have a specific
+title, but only a generic one, whereas an \textsf{unpublished} entry
+will ordinarily have a specific author and title, and won't come from
+a named archive.  The \textsf{misc} type with an \textsf{entrysubtype}
+defined is the least formatted of all those specified by the
+\emph{Manual}, so titles are in plain text by default.  (It is quite
+possible, though somewhat unusual, for archival material to have a
+specific title, rather than a generic one.  In these cases, you will
+need to enclose the title inside a \cmd{mkbibquote} command manually.
+Cf.\ roosevelt:speech, shapey:partita.)
+
+\mylittlespace If you are presenting part of an unpublished archive,
+then it's worth remembering that, as with the \textsf{letter} type,
+the \emph{Manual} (15.54) suggests that the list of references will
usually contain only the name of the whole archived collection, with
more specific information about individual items provided in the text,
outside the parentheses.  If, on the other hand, \enquote{only one
item from a collection has been mentioned in text, the entry may
-  begin with the writer's name (if known).}  (See 14.219-220, 14.231,
-14.232-242; house:papers cites a whole archive, while creel:house,
+  begin with the writer's name (if known).}  (See 14.211--12, 14.219,
+14.221--31; house:papers cites a whole archive, while creel:house,
dinkel:agassiz, and spock:interview cite individual pieces.)

\mylittlespace As far as constructing your .bib entry goes, you should
-first know that, like the \textsf{inreference} and \textsf{reference}
-types, the absence of any date will not result in the \enquote{n.d.}
-abbreviation automatically being provided.  As for presenting the
-date, the \emph{Manual} draws a distinction between archival material
-that is \enquote{letter-like} (letters, memoranda, reports, telegrams)
-and that which isn't (interviews, wills, contracts, or even personal
-communications you've received and which you wish to cite).  This may
-not always be the easiest distinction to draw, and in previous
-releases of \textsf{biblatex-chicago} I have been ignoring it, but
-once you've decided to classify it one way or the other you put the
-date in the \textsf{origdate} field for letters, etc.\ (creel:house),
-and into the \textsf{date} field for the others (spock:interview).  As
-with the \textsf{letter} type, if the only date present is an
-\textsf{origdate}, you don't need to set the \texttt{cmsdate} option
-in your .bib entry to make sure that that year appears at the head of
-the entry (and in citations) --- this happens automatically.  (Cf.\
-particularly the documentation in section~\ref{sec:fields:authdate}
-below, s.v.\ \enquote{date}, and also the \textsf{letter} type above
-for some of the date-related complications that can arise, and how you
-can address them with judicious use of the \textsf{options},
-\textsf{date}, and \textsf{origdate} fields.)
+first know that the absence of any date will not result in the
+\enquote{n.d.}\ abbreviation automatically being provided.  Indeed, no
+date at all will be required for entries referring to entire archival
+collections.  In such entries, you may wish to use the word
+\enquote{\texttt{classical}} as your \textsf{entrysubtype}, which will
+have no effect on the list of references but will change the look of
+the in-text citations (house:papers).  Instead of any date, the
+citation will include the \textsf{title}, separated from the
+\textsf{author's} name by a space, e.g., (House Papers).  This same
+arrangement, happily, allows you easily to cite individual books of
+the Bible, and also certain other sacred texts (14.238--41; genesis).
+section~\ref{sec:fields:authdate} below for all the details of the
+\texttt{classical} toggle.

-%\enlargethispage{\baselineskip}
+\mylittlespace As for presenting the date of individual items, the
+\emph{Manual} (14.224) allows in these entries, as it does in
+documentation generally \enquote{if numerous dates occur} (9.35), for
+a more streamlined presentation of dates using the day-month-year
+form, different from the standard American month-day-year.  In
+\textsf{letter} entries you use the \textsf{origdate} field to give
+the date of individual letters, and it is always presented in the more
+streamlined form.  Here, the same field will do exactly the same
+thing, though with the added wrinkle that if you'd prefer to use the
+standard day-month-year form you can, simply by putting the date into
+\textsf{misc} entries with an \textsf{entrysubtype} --- in
+\textsf{letter} entries the \textsf{date} refers to the published
+collection.)  As with the \textsf{letter} type, if the only date
+present is an \textsf{origdate}, you don't need to set the
+\texttt{cmsdate} option in your .bib entry to make sure that that year
+appears at the head of the entry (and in citations) --- this happens
+automatically.  (Cf.\ particularly the documentation in
+section~\ref{sec:fields:authdate} below, s.v.\ \enquote{date}, and
+also the \textsf{letter} type above for some of the date-related
+complications that can arise, and how you can address them with
+judicious use of the \textsf{options}, \textsf{date}, and
+\textsf{origdate} fields.)

\mylittlespace As in \textsf{letter} entries, the titles of
unpublished letters are of the form \texttt{Author to Recipi\-ent},
@@ -6666,50 +8980,53 @@
different sort of title, but all types will use the \textsf{note},
\textsf{organization}, \textsf{institution}, and \textsf{location}
fields (in ascending order of generality) to identify the archive,
-though the \emph{Manual} specifies (14.238) that well-known
+though the \emph{Manual} specifies (14.227) that well-known
depositories don't usually need a city, state or country specified.
(The traditional \textsf{misc} fields are all still available, also.)

-\mylittlespace When your .bib entry refers to an entire archived
-collection, then you may wish to use the word
-\enquote{\texttt{classical}} as your \textsf{entrysubtype}, which will
-have no effect on the list of references but will change the look of
-the in-text citations (house:papers).  Instead of any date, the
-citation will include the \textsf{title}, separated from the
-\textsf{author's} name by a space, e.g., (House Papers).  This same
-arrangement, happily, allows you easily to cite individual books of
-the Bible, and also certain other sacred texts (14.252--55; genesis).
-section~\ref{sec:fields:authdate} below for all the details of the
-\texttt{classical} toggle.
+\mylittlespace There are a few more subtleties involved here.  Some
+material (roosevelt:speech) includes a venue for the event recorded in
+the archive, so I have added the \mycolor{\textsf{venue}} field, which
+prints \emph{before} the date, with the \textsf{origlocation}
+appearing after it.  Somewhat confusingly, in published letters the
+\textsf{origlocation} itself prints before the date, rather than
+after, so if the inconsistency between published and unpublished
+letters bothers you then you could conceivably use \textsf{venue}
+instead of \textsf{origlocation} for that purpose here.  Also, the
+\emph{Manual} offers several examples of specific location information
+\emph{within} an archive, some of which appears \emph{before} the main
+archive name, and some of which appears \emph{after} it.  I assume
+this may depend on the exact nature of the archive itself, but in any
+case you can try the \textsf{type} or \textsf{howpublished} fields for
+the first case and the \textsf{number} field for the second.

\mylittlespace In all this class of archived material, the
-\emph{Manual} (14.232) quite specifically requires more consistency
+\emph{Manual} (14.221) quite specifically requires more consistency
within your own work than conformity to some external standard, so it
is the former which you should pursue.  I hope that
\textsf{biblatex-chicago} proves helpful in this regard.

-\mybigspace The \mymarginpar{\textbf{music}} 16th edition of the
-manual has revised its recommendations more for this type than for any
-other, so the notes which follow present several large changes that
-you'll need to make to your .bib files.  The good news is that some,
-though by no means all, of those changes involve considerable
-simplifications.  \textbf{Music} is one of three audiovisual entry
-types, and is intended primarily to aid in the presentation of musical
-recordings that do not have a video component, though it can also
-include audio books (auden:reading).  A DVD or VHS of an opera or
-other performance, by contrast, should use the \textbf{video} type
-instead (handel:messiah).  Because \textsf{biblatex} --- and
-\textsc{Bib}\TeX\ before it --- were designed primarily for citing
-book-like objects, some choices needed to be made in assigning the
-various roles found on the back of a CD to the fields in a typical
-.bib entry.  I have also implemented several bibstrings to help in
-identifying these roles within entries.  If you can think of a simpler
-way to distribute the roles, please let me know, so that I can
-consider making changes before anyone gets used to the current
-equivalences.
+\mybigspace This \colmarginpar{\textbf{music}} is one of three
+audiovisual entry types, and is intended primarily to aid in the
+presentation of musical recordings that do not have a video component,
+though it can also include audio books (auden:reading).  A DVD or VHS
+of an opera or other performance, by contrast, should use the
+\textbf{video} type instead, while an online music video will probably
+need an \textbf{online} entry.  (Cf.\ \textsf{online} and
+\textsf{biblatex} --- and \textsc{Bib}\TeX\ before it --- were
+designed primarily for citing book-like objects, some choices needed
+to be made in assigning the various roles found on the back of a CD to
+the fields in a typical .bib entry.  I have also implemented several
+bibstrings to help in identifying these roles within entries.  The
+17th edition of the \emph{Manual} once again revised its
+recommendations for this type, but fortunately the changes are
+additive, i.e., you can re-use 16th-edition citations but are
+encouraged to peruse the following guidelines to see if there's any
+into line with the spec.

-\mylittlespace These equivalences, in summary form, are:
+\mylittlespace These guidelines, in summary form, are:

\begin{description}
@@ -6716,6 +9033,11 @@
\item[author =] composer, songwriter, or performer(s),
depending on whom you wish to emphasize by placing them at the head
of the entry.
+\item[bookauthor:] Somewhat like an \textsf{author}, but it will hold
+  the name associated with a whole album rather than an individual
+  piece, should both be present, and will therefore appear in close
+  association with the \textsf{booktitle} rather than at the head of
+  the entry.
\item[editor, editora, editorb =] conductor, director or
performer(s).  These will ordinarily follow the \textsf{title} of
the work, though the usual \texttt{useauthor} and \texttt{useeditor}
@@ -6722,96 +9044,116 @@
options can alter the presentation within an entry.  Because these
are non-standard roles, you will need to identify them using the
following:
-\item[editortype, editoratype, editorbtype:] The most common roles,
-  all associated with specific bibstrings (or their absence), will be
-  \texttt{conductor}, \texttt{director}, \texttt{producer}, and,
-  oddly, \texttt{none}.  The last is particularly useful when
+\item[\mycolor{editortype, editoratype, editorbtype:}] The most common
+  roles, all associated with specific bibstrings (or their absence),
+  will be \texttt{conductor}, \texttt{director}, \texttt{producer},
+  and, oddly, \texttt{none}.  The last is particularly useful when
identifying the group performing a piece, as it usually doesn't need
further specifying and this role prevents \textsf{biblatex} from
-  falling back on the default \texttt{editor} bibstring.
-\item[title, booktitle, maintitle:] As with the other audiovisual
-  types, \textsf{music} serves as an analogue both to books and to
-  collections, so the title will either be, e.g., the album title or a
-  song title, in which latter case the album title would go into
-  \textsf{booktitle}.  The \textsf{maintitle} might be necessary for
-  something like a box set of \emph{Complete Symphonies}.
+  falling back on the default \texttt{editor} bibstring.  The 17th
+  edition (15.57) also seems to favor, in some circumstances, using
+  strings to identify individual performers, e.g., \enquote{vocalist}
+  or \enquote{pianist,} so even though there's no \cmd{bibstring}
+  associated with these types you can now provide them, or anything
+  else you need, in whatever form (\enquote{vocalist} or \enquote{sung
+\item[note:] This field can also hold contributors, perhaps
+  collaborators or featured artists (holiday:fool, rihanna:umbrella).
+\item[\mycolor{title, booktitle, maintitle:}] As with the other
+  audiovisual types, \textsf{music} serves as an analogue both to
+  books and to collections, so the title will either be, e.g., the
+  album title or a song title, in which latter case the album title
+  would go into \textsf{booktitle}.  If you wish to cite a song that,
+  as may happen, isn't part of any larger collection, your entry will
+  in such a case have only a \textsf{title}, which
+  \textsf{biblatex-chicago} would normally interpret as an album
+  title.  You \colmarginpar{New!} can now define an
+  \textsf{entrysubtype} to let it know that the lone \textsf{title} is
+  in fact a song (cf.\ naraya).  The \textsf{maintitle} might be
+  necessary for something like a box set of \emph{Complete
+    Symphonies}.
+\item[\mycolor{chapter:}] The 17th edition seems more keen on having
+  track numbers for individual pieces, whether on a traditional format
+  or on a streaming service.  The \colmarginpar{New!} \textsf{chapter}
+  field is the place for this information, and
+  \textsf{biblatex-chicago} will automatically prepend the localized
+  string \texttt{track} (cf.\ holiday:fool, rihanna:umbrella).
\item[publisher, series, number:] These three closely-associated
-  by the music publisher.  The 16th edition generally only requires
+  by the music publisher.  The 17th edition generally only requires
the \textsf{series} and \textsf{number} fields (nytrumpet:art),
which hold the record label and catalog number, respectively.
Alternatively, \textsf{publisher} would function as a synonym for
\textsf{series} (holiday:fool), but there may be cases when you need
-  or want to specify a publisher in addition to a label, as was the
-  general requirement in the 15th edition.  (This might happen, for
-  example, when a single publisher oversees more than one label.)  You
-  can certainly put all of this information into one of the above
-  fields, but separating it may help make the .bib entry more
-\item[howpublished/pubstate:] The 16th edition of the \emph{Manual}
-  (14.276, 15.53) has rather helpfully eliminated any reference to the
-  specialized symbols (\texttt{\textcircledP} \&\
-  \texttt{\textcopyright}) found in the 15th edition for presenting
-  publishing information for musical recordings.  This means that the
-  \textsf{howpublished} field is obsolete, and you can remove it from
-  \textsf{music} entries in your .bib files.  The \textsf{pubstate}
-  field, therefore, can revert to its standard use for identifying
-  reprints.  In \textsf{music} entries, putting \texttt{reprint} here
-  will transform the \textsf{origdate} from a recording date for an
-  entire album into an original release date for that album, notice of
-  which will be printed towards the end of a reference list entry,
-  always assuming that the \textsf{origdate} hasn't already appeared
-  at the head of the entry and in citations.
-\item[date, eventdate, origdate:] As though to compensate for the
-  simplification I've just mentioned, the \textsf{Manual} now
-  \enquote{recommends a more comprehensive approach to dating
-    audiovisual materials than in previous editions} (15.53).  Indeed,
-  \enquote{citations without a date are generally unacceptable}
-  (14.276), while if there is more than one date \enquote{the date of
-    the original recording should be privileged} (15.53).  Finding
-  these dates may take some research, but they will basically fall
-  into two types, i.e., the date of the recording or the copyright /
-  publishing date.  Recording dates go either in \textsf{origdate}
-  (for complete albums) or \textsf{eventdate} (for individual tracks).
-  The current copyright or publishing date goes in the \textsf{date}
-  field, while the original release date goes in \textsf{origdate}.
-  You may have noticed that the \textsf{origdate} has two slightly
-  different uses --- you can tell \textsf{biblatex-chicago} which sort
-  you intend by using the string \texttt{reprint} in the
-  \textsf{pubstate} field, which transforms the \textsf{origdate} from
-  a recording date into an original release date.  The style will
-  automatically use the \textsf{eventdate} or the \textsf{origdate} in
-  citations and at the head of the list of references, falling back on
-  a \textsf{date} or even a \textsf{urldate} in their absence.  It
-  will also prepend the bibstring \texttt{recorded} to any part of the
-  \textsf{eventdate} that doesn't appear at the head of the list of
-  references or, in the absence of the \textsf{pubstate} mechanism, to
-  the \textsf{origdate}, or indeed to both.  You can modify what is
+  or want to specify a publisher in addition to a label, as perhaps
+  when a single publisher oversees more than one label.  You can
+  certainly put all of this information into one of the above fields,
+  but separating it may help make the .bib entry more readable.
+\item[pubstate:] The \textsf{pubstate} field in \textsf{music} entries
+  mainly has the usual meaning it has in other entry types, for which
+  see the documentation of the field in
+  section~\ref{sec:fields:authdate}, below.  If the field contains
+  \texttt{reprint}, however, this has a special meaning in
+  \textsf{music} entries, where it will transform the
+  \textsf{origdate} from a recording date for an entire album into an
+  original release date for that album, notice of which will be
+  printed towards the end of a reference list entry, always assuming
+  the entry and in citations.  No \texttt{reprint} \cmd{bibstring}
+  will be printed, as only the syntax of the reference will have been
+  altered.
+\item[date, eventdate, origdate:] The 17th edition of the
+  \emph{Manual}, like the 16th, considers \textsf{music} citations
+  without a date to be \enquote{generally unacceptable} (14.263),
+  while if there is more than one date \enquote{the date of the
+    original recording should be privileged} (15.57).  Finding these
+  dates may take some research, but they will basically fall into two
+  types, i.e., the date of the recording or the copyright / publishing
+  date.  Recording dates go either in \textsf{origdate} (for complete
+  albums) or \textsf{eventdate} (for individual tracks).  The current
+  copyright or publishing date goes in the \textsf{date} field, while
+  the original release date goes in \textsf{origdate}.  You may have
+  noticed that the \textsf{origdate} has two slightly different uses
+  --- you can tell \textsf{biblatex-chicago} which sort you intend by
+  using the string \texttt{reprint} in the \textsf{pubstate} field,
+  which transforms the \textsf{origdate} from a recording date into an
+  original release date.  The style will automatically use the
+  \textsf{eventdate} or the \textsf{origdate} in citations and at the
+  head of the list of references, falling back on a \textsf{date} or
+  even a \textsf{urldate} in their absence.  It will also prepend the
+  bibstring \texttt{recorded} to any part of the \textsf{eventdate}
+  that doesn't appear at the head of the list of references or, in the
+  absence of the \textsf{pubstate} mechanism, to the
+  \textsf{origdate}, or indeed to both.  You can modify what is
printed here using the \textsf{userd} field, which acts as a sort of
date type modifier.  In \textsf{music} entries, \textsf{userd} will
be prepended to an \textsf{eventdate} if there is one, barring that
to the \textsf{origdate}, barring that to a \textsf{urldate}, and
-  absent those three to a \textsf{date}.  (See holiday:fool,
-  nytrumpet:art.)
-\item[type:] As in all the audiovisual entry types, the \textsf{type}
-  field holds the medium of the recording, e.g., vinyl, 33 rpm,
-  8-track tape, cassette, compact disc, mp3, ogg vorbis.
+  absent those three to a \textsf{date}.  (See floyd:atom,
+  holiday:fool, nytrumpet:art.)
+\item[type, \mycolor{howpublished}:] As in all the audiovisual entry
+  types, the \textsf{type} field holds the medium of the recording,
+  e.g., vinyl, 33 rpm, 8-track tape, cassette, compact disc, mp3, ogg
+  vorbis.  The \colmarginpar {New!} \mycolor{\textsf{howpublished}}
+  field, newly included for the 17th edition, can hold similar
+  (14.263, 15.57). It can also, alternatively, hold the name of the
+  streaming service, e.g., Spotify (cf.\ rihanna:umbrella).
\end{description}}

-The entries in \textsf{dates-test.bib} should at least give you a good
+The entries in \textsf{notes-test.bib} should at least give you a good
idea of how this all works, and that file also contains an example of
an audio book presented in a \textsf{music} entry.  If you browse the
-examples in the \emph{Manual} you will see some variations in the
-formatting choices there, from which I have made selections for
-\textsf{biblatex-chicago}.  It wasn't always clear to me that these
-variations were rules as opposed to possibilities, so I've ignored
-some of them in the code.  Arguments as to why I'm wrong will, of
-course, be entertained.  (Cf. 14.276--77, 15.53; \textsf{eventdate},
-\textsf{origdate}, \textsf{userd}; \cmd{DeclareLabeldate} in
-section~\ref{sec:authformopts} and \texttt{avdate} in
-bernstein:shostakovich, floyd:atom, holiday:fool, nytrumpet:art,
-rubinstein:chopin.)
+examples in the \emph{Manual} you will see the sheer variety of
+possibilities for presenting these sources, my intention being that
+judicious manipulation of\ .bib entries should allow you to make
+\textsf{biblatex-chicago} do what you want.  Please let me know if
+I've ignored something you need.  (Cf. 14.263--64, 15.57;
+\textsf{eventdate}, \textsf{origdate}, \textsf{userd};
+\cmd{DeclareLabeldate} in section~\ref{sec:authformopts} and
+beethoven:sonata29, bernstein:shostakovich, floyd:atom, holiday:fool,
+nytrumpet:art, rubinstein:chopin.)

\mybigspace All \mymarginpar{\textbf{mvbook}\\\textbf{mvcollection}%
\\\textbf{mvproceedings}\\\textbf{mvreference}} four of these entry
@@ -6830,11 +9172,9 @@
circumstances, provides.  Please see the documentation of the
\textbf{crossref} field in section~\ref{sec:fields:authdate}, below.)

-%\enlargethispage{\baselineskip}
-
\mylittlespace On the same subject, when multi-volume works are
-presented in the reference apparatus, the \emph{Manual} (14.121--27,
-15.39) requires that any dates presented should be appropriate to the
+presented in the reference apparatus, the \emph{Manual} (14.116--22,
+15.41) requires that any dates presented should be appropriate to the
specific nature of the citation.  In short, this means that a date
range that is right for the presentation of a multi-volume work in its
entirety isn't right for citing, e.g., a single volume of that work
@@ -6852,78 +9192,303 @@
harley:ancient:cart, harley:cartography, and harley:hoc for how this
might look.

-\mybigspace The \mymarginpar{\textbf{online}} \emph{Manual}'s
-scattered instructions (14.4--13, 14.166--169, 14.184--185, 14.200,
-14.223, 14.243--246, 15.4, 15.9) for citing online materials are
-slightly different from those suggested by standard \textsf{biblatex}.
-Indeed, this is a case where complete backward compatibility with
-other \textsf{biblatex} styles may be impossible, because as a general
-rule the \emph{Manual} considers relevant not only where a source is
-found, but also the nature of that source, e.g., if it's an online
-edition of a book (james:ambassadors), then it calls for a
-\textsf{book} entry.  Even if you cite an intrinsically online source,
-if that source is structured more or less like a conventional printed
-periodical, then you'll probably want to use \textsf{article} or
-\textsf{review} instead of \textsf{online} (stenger:privacy, which
-cites \emph{CNN.com}).  The 16th edition's suggestions for blogs lend
-themselves well to the \textsf{article} type, too, while comments
-become, logically, \textsf{reviews} (14.243--6; ellis:blog,
-ac:comment).  Otherwise, for online documents not \enquote{formally
-  published,} the \textsf{online} type is usually the best choice
-(evanston:library, powell:email).  Online videos, in particular short
-pieces or those that present excerpts of some longer event or work,
-and also online interviews, usually require this type, too.  (See
-harwood:biden, horowitz:youtube, pollan:plant, but cp.\ weed:flatiron,
-a complete film, which requires a \textsf{video} entry.)  Online audio
-pieces, particularly dated ones from an archive, work well either with
-an \textsf{online} entry or with a \textsf{misc} entry with an
-\textsf{entrysubtype}: (coolidge:speech, roosevelt:speech.)  Some
-online materials will, no doubt, make it difficult to choose an entry
-type, but so long as all locating information is present, then perhaps
-that is enough to fulfill the specification, or at least so I'd like
-to hope.
+\mylittlespace Finally, in order to cope with parts of the notes \&\
+bibliography specification I have fairly thoroughly revised the
+\textbf{mv*} types there for the 17th edition.  The author-date
+specification is, as I read it, simpler, so I haven't revised these
+types here.  If you should happen to leave a stray \texttt{maintitle
+  relatedtype} in an entry when switching specifications that entry
+will use the \texttt{multivolume relatedtype} instead, which will very
+likely not be what you want.

-\mylittlespace Constructing an \textsf{online} .bib file entry is much
-the same as in \textsf{biblatex}.  The \textsf{title} field would
-contain the title of the page, the \textsf{organization} field could
-hold the title or owner of the whole site.  If there is no specific
-title for a page, but only a generic one (powell:email), then such a
-title should go in \textsf{titleaddon}, not forgetting to begin that
-field with a lowercase letter so that capitalization will work out
-correctly.  It is worth remarking here, too, that the 16th edition of
-the \emph{Manual} (14.7--8) prefers, if they're available, revision
-dates to access dates when documenting online material.  See
-\textsf{urldate} and \textsf{userd}, below.
+\mybigspace One \colmarginpar{\textbf{online}} of the features of the
+17th edition of the \emph{Manual} is the considerably extended, but
+still scattered, treatment of online materials (8.189--92, 14.6--18,
+14.159--63, 14.175--76, 14.187, 14.189, 14.205--10, 14.233, 15.4,
+15.9, 15.49--52, 15.57).  The principles of that treatment have
+changed somewhat, as the \emph{Manual} now places greater emphasis on
+the \emph{location} of a source, which can in many cases outweigh, as
+far as choosing an entry type goes, the \emph{nature} of the source.
+Working out the correspondences between online sources and
+\textsf{biblatex-chicago} entry types can, therefore, be tricky, so I
+increasingly detailed instructions in the \emph{Manual}, along with
+some further annotations here that might help to clarify it.

+\afterpage{\clearpage
+
+\begin{table}[h!]
+  \caption[\hspace{-1em}\mycolor{Online Entry Types - Author-Date}]%
+  {Online materials and author-date entry types}
+  \centering\small\sffamily
+  \hspace*{-6em}
+  \begin{tabularx}{160mm}{@{}>{\raggedright}p{25mm}>{\raggedright}p{20mm}p{15mm}p{26mm}X@{}}
+    \toprule
+    Online Material & Entry Type & CMS Ref. & Sample Entry &
+    Notes \\
+    \cmidrule{1-1}\cmidrule(l){2-2}\cmidrule(l){3-3}\cmidrule(l){4-4}
+    \cmidrule(l){5-5}
+    Online edition of trad.\ publ.\ matter. &&&& Use the same
+    entry type as you would choose were you citing it
+    & @Book & 14.161-62 & james:ambassadors &
+    CMS prefers (scanned) original page nos. \\\addlinespace[.6mm]
+    & @Article @Review & 14.175 15.47-49 & black:infectious & If
+    no \enquote{suitable URL} is available, e.g., if it points
+    to a generic portal page rather than to an abstract,
+    use the name of the commercial database in an addendum
+    \hspace{.5em} Single post & @Article & & amlen:hoot & The
+    \textsf{maintitle} field holds the larger publication of which the
+    \hspace{.5em} Whole Blog & @Periodical & & amlen:wordplay & This \&\
+    the next usually not in the ref.\ list.
+    \hspace{.5em} Comment & @Review & & viv:amlen & The
+    \mycolor{\texttt{commenton}} \textsf{relatedtype} helps manage these,
+    in or out of the reference list. \\\addlinespace[.6mm]
+    Social Media & @Online & 15.52 && This includes anything ---
+    posts, photos, videos --- on these and similar sites; the
+    \emph{location} of the material defines its treatment. \\\addlinespace[2mm]
+    \hspace{.5em} Mailing list or \hspace*{.5em} forum post & & 14.210 &
+    powell:email & Posts on private lists are to be treated as
+    \enquote{personal communications,} using @Misc w/
+    \hspace{.5em} Comments / \hspace*{.5em} replies & & 14.210
+    & braun:reply &This and the next are usually not included in the
+    reference list. The
+    \mycolor{\texttt{commenton}} \textsf{relatedtype} helps manage them,
+    in or out of that list.
+    \\
+    && 14.209 & licis:diazcomment &\\\addlinespace[.6mm]
+    Online Multimedia && 15.57 &&\\\addlinespace[.6mm]
+    \hspace{.5em} Online video & @Online & 14.267 & pollan:plant &
+    This category includes TED talks and most informal videos on
+    \hspace{.5em} Online video, \hspace*{.5em} from a trad.\ \hspace*{.5em}
+    journal & @Article &&
+    kessler:nyt & You can use @Online, but this requires special
+    formatting in the \textsf{note} or \textsf{titleaddon} field.
+    \hspace{.5em} Published films in \hspace*{.5em} an archive & @Video &&
+    \hspace{.5em} Podcasts & @Audio && danforth:podcast & Note the
+    eventdate of the individual episode.\\\addlinespace[.6mm]
+    \hspace{.5em} Archival audio & @Misc w/ \textsf{entrysubtype} & 14.264 &
+    roosevelt:speech & Can have both a venue and an origlocation.
+    \hspace*{.5em} TV / Film & @Video & 14.265 & mayberry:brady &
+    The streaming service is supplied by the URL.  The
+    \mycolor{\texttt{tvepisode}} entrysubtype is new in the 17th
+    \hspace*{.5em} Music & @Music & 14.263 & rihanna:umbrella &
+    The streaming service is supplied by the howpublished field.
+    \hspace*{.5em} News / Interviews & @Article @Review & 14.213 &
+    bundy:macneil & Network information goes in the usera field.
+    Websites & @Online & 14.206-7 15.50 & evanston:library stenger:privacy &
+    An online source \enquote{analogous
+    work but [which] does not have (and never had) a printed counterpart}
+    may now use an @Online entry, at your discretion.
+    If you only have an access date, \enquote{n.d.}\ will appear as
+    the publication date.
+    \hspace*{.5em} Reference works, \hspace*{.5em} cited by alpha-
+    \hspace*{.5em} betized entry & @InReference w/ entrysub-\par
+    type & 14.233 & wikiped:bibtex & As above, you can choose the
+    @Online treatment of the title, but it's best achieved
+    using an @InReference entry w/ entrysubtype. \\\addlinespace[.6mm]
+    \hspace*{.5em} Scientific data- \hspace*{.5em} bases & \mycolor{@Dataset} &
+    14.257 & genbank:db & Treated as author-title by
+    \bottomrule
+  \end{tabularx}
+\end{table}}
+
+\mylittlespace The basic principle, as I've cited in the penultimate
+entry of table~\ref{tab:online:adtypes}, is that \enquote{the title of a
+  website that is analogous to a traditionally printed work but does
+  not have (and never had) a printed counterpart can be treated like
+  the titles of other websites, subject to editorial discretion}
+(14.206).  This means that an intrinsically online entry like
+stenger:privacy (citing CNN.com) need no longer be an \textsf{article}
+but can be presented in an \textsf{online} entry.  (The same principle
+applies to wikiped:bibtex, but because of the code facilitating
+presentation of alphabetized entries in reference works, it's best in
+this case to keep the \textsf{inreference} entry but add an
+\textsf{entrysubtype} so that the \textsf{title} is presented as it
+would be in an \textsf{online} entry.)  The corollary of the
+principle, as the first entry in table~\ref{tab:online:adtypes}
+suggests, is that an online edition of a printed work will generally
+require the same entry type as that printed work itself would.  Blogs
+are, therefore, somewhat anomalous in requiring the various periodical
+types, though the \emph{Manual} does specify that if you're not sure
+whether a website is a blog, then it probably requires the
+\textsf{online} type (14.206).  Social media, on the other hand, are
+very much subject to the first principle, requiring \textsf{online}
+entries no matter whether the citation is of text, a photo, or a
+video.  Without pretending that all of the correspondences flow
+deductively from the basic principles, I hope that the table might
+let me know and I'll see if I can improve it.
+
\enlargethispage{\baselineskip}

+\mylittlespace A few more notes are in order. I designed the
+\colmarginpar{New!} new \textsf{relatedtype}
+\mycolor{\texttt{commenton}} to facilitate citation of online
+comments, and it is available in two entry types, \textsf{online} and
+\textsf{review}.  In both types the \emph{Manual} (15.51--52)
+recommends that such material appear \emph{only} in the text and not
+in the reference list, but I have attempted to simplify the
+presentation of such material wherever you want it to appear.
+Following the specifications, then, the default when you use
+\mycolor{\texttt{commenton}} is for
+\textsf{biblatex-chicago-authordate} to modify how your .bib entry
+appears in the .bbl file by setting both \texttt{skipbib} and
+\texttt{cmsdate=full} in the \textsf{options} field, so that nothing
+appears in the reference list and citations present the full date and
+possibly also a time stamp (see below).  Further, the style sets the
+\mycolor{\textsf{verbc}} field so that these entries don't interfere
+with the provision of extra date letters --- the full date and time
+should be enough to individuate separate comments.  Finally, the style
+creates a new \textsf{customc} entry in your .bbl file which you can
+cite after your initial \mycolor{\texttt{commenton}} entry using
+\cmd{autocites} and which will, as a comment to your initial entry,
+say whether it's a comment or a reply or what have you, and then
+giving the short citation of that upon which it is a comment.
+
+\mylittlespace As an example, take the Facebook post diaz:surprise,
+which does appear in the reference list.  The entry licis:diazcomment
+presents a comment on this post using the \textsf{relatedtype}
+\mycolor{\texttt{commenton}}, so \textsf{biblatex-chicago-authordate}
+creates a new entry, diaz:surprise-customc, which won't appear in your
+.bib file (which is never altered) but in the .bbl file that
+\textsf{biber} produces to supply \textsf{biblatex} with the data for
+its citations.  A command like
+\verb+\autocites{licis:diazcomment}{diaz:surprise-customc}+ will
+produce a citation like (Licis, February 24, 2016; comment on D\'iaz
+2016).  You can alter the string connecting the two citations (by
+default \verb+\bibstring{commenton}+) by using the
+\textsf{relatedstring} field in the first of them (cf.\
+powell:comment).  (Note how minimal the .bib entry of a comment using
+this system can be --- \textsf{author}, \textsf{related},
+\textsf{relatedtype}, and \textsf{date} are pretty much the only
+fields required.)
+
+\mylittlespace Those who want \textsf{online} comments to appear in
+the reference list can still use the \mycolor{\texttt{commenton}}
+\textsf{relatedtype}, and the same citation of the commented piece
+will appear there, connected by the same string that the
+\textsf{customc} entry provides.  Here, though, you can also provide a
+separate \textsf{title} for the comment, and/or a separate
+\textsf{url} for it, should they exist, which will be printed
+before/after the citation of the commented piece, respectively.  (In
+\textsf{review} entries, which use the same \textsf{relatedtype}, only
+the generic title is available, as is always the case with such
+entries.)  If you manually set either (or both) of the
+\texttt{cmsdate} or the \texttt{skipbib} options in your entry then
+\textsf{biblatex-chicago} will assume you want to hand-craft that
+entry without its intervention, though it will still provide the
+virtual \textsf{customc} entry in your .bbl file, as that may still
+prove convenient.  Note also that any \mycolor{\textsf{verbc}} field
+you provide will never be altered by the package.
+
+\mylittlespace In general, constructing an \textsf{online}\ .bib file
+entry is much the same as in \textsf{biblatex}.  The \textsf{title}
+field would contain the title of the page, the \textsf{organization}
+field could hold the title or owner of the whole site.  If there is no
+specific title for a page, but only a generic one, then such a title
+should go in \textsf{titleaddon}, not forgetting to begin that field
+with a lowercase letter so that capitalization will work out
+correctly.  It is worth remarking here, too, that the \emph{Manual}
+(15.50) strongly prefers, if they're available, revision dates to
+access dates when documenting online material.  If there is only a
+\textsf{urldate} in an entry, and that date is an access date (i.e.,
+there's no \textsf{userd} field), then \enquote{n.d.} will appear in
+citations and at the head of the entry in the reference list.
+Moreover, given how rapidly online sources can change (14.191, 14.209,
+14.233), a time stamp may often be necessary further to specify a
+revision date (\textsf{urldate}) or the date of a comment or reply
+(\textsf{date}).  This time specification should be added to the date
+field using \textsf{biblatex's} standard format, i.e.,
+\texttt{2008-07-01T10:18:00}.  If a time zone is needed, then a
+separate \textsf{timezone} or \textsf{urltimezone} field is the best
+way, as it allows you to provide the initialisms that the
+\emph{Manual} prefers (10.41, 14.191).  On all of this please see
+\textsf{date}, \mycolor{\textsf{timezone}}, \textsf{urldate},
+\textsf{userd}, and \mycolor{\textsf{verbc}} in
+section~\ref{sec:fields:authdate}, below.  Cf.\ also the documentation
+of the \mycolor{\texttt{commenton}} \textsf{relatedtype} in
+section~\ref{sec:authrelated}.
+
\mybigspace The \mymarginpar{\textbf{patent}} \emph{Manual} is very
-brief on the subject of patents (15.50), but very clear about which
+brief on the subject of patents (15.55), but very clear about which
information it wants you to present, so such entries may not work well
-with other \textsf{biblatex} styles.  In a change to previous
-practice, the 16th edition of Chicago's author-date style prefers the
-\emph{later} of the two possible dates to appear in citations and at
-the head of the entry in the list of references.  If a patent has been
-filed but not yet granted, then you can place the filing date in
-either the \textsf{date} field or the \textsf{origdate} field, and
-\textsf{biblatex-chicago-authordate} will automatically prepend the
-bibstring \texttt{patentfiled} to it.  If the patent has been granted,
-then you put the filing date in the \textsf{origdate} field, and you
-put the date it was issued in the \textsf{date} field, to which the
-bibstring \texttt{patentissued} will automatically be prepended, and
-it is this later date that will head the entry and appear in
-citations.  The patent number goes in the \textsf{number} field, and
-you should use the standard \textsf{biblatex} bibstrings in the
-\textsf{type} field.  Though it isn't mentioned by the \emph{Manual},
-\textsf{biblatex-chicago-authordate} will print the \textsf{holder}
-after the \textsf{author}, if you provide one.  Finally, the 16th
-edition of the \emph{Manual} capitalizes the \textsf{title}
-sentence-style, which seems to be the generally-accepted convention,
-across both Chicago styles.  As I've removed all of the automatic
-down-casing code from previous editions, you may need manually to
-revise the \textsf{title} field to provide the lowercase letters.  See
-petroff:impurity.
+with other \textsf{biblatex} styles.  Chicago's author-date style
+prefers the \emph{later} of the two possible dates to appear in
+citations and at the head of the entry in the list of references.  If
+a patent has been filed but not yet granted, then you can place the
+filing date in either the \textsf{date} field or the \textsf{origdate}
+field, and \textsf{biblatex-chicago-authordate} will automatically
+prepend the bibstring \texttt{patentfiled} to it.  If the patent has
+been granted, then you put the filing date in the \textsf{origdate}
+field, and you put the date it was issued in the \textsf{date} field,
+to which the bibstring \texttt{patentissued} will automatically be
+prepended, and it is this later date that will head the entry and
+appear in citations.  The patent number goes in the \textsf{number}
+field, and you should use the standard \textsf{biblatex} bibstrings in
+the \textsf{type} field.  Though it isn't mentioned by the
+\emph{Manual}, \textsf{biblatex-chicago-authordate} will print the
+\textsf{holder} after the \textsf{author}, if you provide one.
+Finally, the style capitalizes the \textsf{title} sentence-style,
+which seems to be the generally-accepted convention across all Chicago
+specifications.  If you need to keep a word capitalized then you
+should wrap it in curly braces.  See petroff:impurity.

+\mybigspace The \colmarginpar{\textbf{performance}} 17th edition of
+the \emph{Manual} includes a new section (14.266) on citing live
+performances, and even though such references can usually be limited
+to the main text (cf.\ 15.57) it may sometimes be useful to include
+them in a reference list.  Since \textsf{biblatex} provides the
+\mycolor{\textbf{performance}} type, albeit without using it in its
+standard styles, I though it might be useful to define it for
+\textsf{biblatex-chicago}, particularly as the other option for such
+material is the \textsf{misc} entry without any \textsf{entrysubtype},
+still use it if you wish.
+
+\mylittlespace Such entries will generally have a \textsf{title}, a
+\textsf{venue}, a \textsf{location} for the venue, and a \textsf{date}
+for the performance, along with a possible plethora of authorial
+and/or editorial roles depending on which sorts of contributor(s) you
+wish to emphasize in the citation.  The \textsf{editor[abc]} and
+\textsf{editor[abc]type} fields should be most helpful here.  I have
+included strings for \mycolor{\texttt{choreographer}} in all
+localization files, but for others you may need to provide them in the
+\textsf{editor[abc]type} fields as you wish them printed ---
+\textsf{biblatex-chicago} will automatically capitalize any that start
+with a lowercase letter.  For the author-date styles it will probably
+be convenient to allow one of these names to appear at the head of the
+entry and in citations, as this will facilitate the appearance of the
+\textsf{extradate} to distinguish, e.g., multiple performances of the
+same work or performances of different works by the same producer or
+choreographer.
+
\mybigspace This \mymarginpar{\textbf{periodical}} is the standard
\textsf{biblatex} entry type for presenting an entire issue of a
periodical, rather than one article within it.  It has the same
@@ -6938,17 +9503,32 @@
routines, though this isn't strictly necessary in the author-date
styles.  (See \emph{Manual} 14.187; good:wholeissue.)

-\mylittlespace It is worth noting that the special \textsf{biblatex}
-field \textsf{shortjournal} allows you to present shortened
-\textsf{journaltitles} in \textsf{article}, \textsf{review}, and
-\textsf{periodical} entries, as well as facilitating the creation of
-lists of journal abbreviations in the manner of a \textsf{shorthand}
-list.  Because the \textsf{periodical} type uses the \textsf{title}
-automatically copies any \textsf{shorttitle} field, if one is present,
-into \textsf{shortjournal}.  Please see the documentation of
-\textbf{shortjournal} in section~\ref{sec:fields:authdate} for all the
-details on how this works.
+\mylittlespace It is worth noting two things.  First, the special
+\textsf{biblatex} field \textsf{shortjournal} allows you to present
+shortened \textsf{journaltitles} in \textsf{article}, \textsf{review},
+and \textsf{periodical} entries, as well as facilitating the creation
+of lists of journal abbreviations in the manner of a
+\textsf{shorthand} list.  Because the \textsf{periodical} type uses
+the \textsf{title} field instead of \textsf{journaltitle},
+\textsf{biblatex-chicago} automatically copies any \textsf{shorttitle}
+field, if one is present, into \textsf{shortjournal}.  Please see the
+documentation of \textbf{shortjournal} in
+section~\ref{sec:fields:authdate} for all the details on how this
+works.  Second, although the 17th edition recommends that references
+to whole blogs, as opposed to individual blog posts, need appear only
+in the text (15.51), using the \textsf{periodical} type for such
+material can help with this, in or out of the reference list.  The
+\colmarginpar{New!} new \mycolor{\texttt{authortitle}} entry option
+will ensure the presence of the name of the blog (as opposed to the
+non-existent date) in citations, and you could also use a
+\cmd{citeurl} command to give the URL in the text (or a note).
+Alternately, you could let the entry appear in the reference list and
+cite it in the usual way.  In that list the \emph{Manual} (14.208)
+recommends that you include the name of any larger (usually
+periodical) publication of which the blog is a part.  The
+\textsf{maintitle} field (with \textsf{mainsubtitle} and
+\textsf{maintitleaddon}, if needed) is the place for it. Cf.\
+amlen:wordplay.

\mybigspace This \mymarginpar{\textbf{proceedings}} is the standard
\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but the package
@@ -6972,15 +9552,13 @@
will be printed verbatim, rather than formatted as an alphabetized
entry.  (Cf.\ \textsf{inreference}, above.)

-%\enlargethispage{-\baselineskip}
-
-\mybigspace This \colmarginpar{\textbf{report}} entry type is a
+\mybigspace This \mymarginpar{\textbf{report}} entry type is a
\textsf{biblatex} generalization of the traditional \textsc{Bib}\TeX\
type \textsf{techreport}.  Instructions for such entries are rather
-thin on the ground in the \emph{Manual} (8.183, 14.249), so I have
+thin on the ground in the \emph{Manual} (8.186, 14.220), so I have
followed the generic advice about formatting it like a book, and hope
that the results conform to the specification.  At least one user has
-indicated a need, now filled, for an \mycolor{\texttt{unpublished}}
+indicated a need, now filled, for an \texttt{unpublished}
\textsf{entrysubtype}, which prints the \textsf{title} inside
quotation marks (or, in \textsf{authordate-trad}, in plain roman)
instead of in italics, but affects nothing else.  This detail aside,
@@ -6990,34 +9568,28 @@
the International Standard Technical Report Number of a technical
report.  As in standard \textsf{biblatex}, if you use a
\textsf{techreport} entry, then the \textsf{type} field automatically
-defaults to \cmd{bibstring\{techreport\}}.  As with \textsf{booklet}
+defaults to \verb+\bibstring{techreport}+.  As with \textsf{booklet}
and \textsf{manual}, you can also use a \textsf{book} entry, putting
the report type in \textsf{note} and the \textsf{institution} in
\textsf{publisher}.  (See herwign:office.)

-\mybigspace The \colmarginpar{\textbf{review}} \textsf{review} entry
-type wasn't, strictly speaking, necessary for the 15th edition
-author-date specification.  With the major changes to the presentation
-of the title fields in the 16th edition, however, it has become
-necessary for \textsf{authordate} users, if not
-\textsf{authordate-trad} users, to familiarize themselves with it as a
-means of coping with the \emph{Manual}'s complicated requirements for
-citing periodicals of all sorts.  As its name suggests, this entry
-type was designed for reviews published in periodicals, and if you've
-haven't, I recommend doing so now --- you'll know that \textsf{review}
-serves as well for citing other sorts of material with generic titles,
-like letters to the editor, obituaries, interviews, online comments
-and the like.  The primary rule is that any piece that has only a
-generic title, like \enquote{review of \ldots,} \enquote{interview
-  with \ldots,} or \enquote{obituary of \ldots,} calls for the
-\textsf{review} type.  Any piece that also has a specific title, e.g.,
-\enquote{\enquote{Lost in \textsc{Bib}\TeX,} an interview with
-  \ldots,} requires an \textsf{article} entry.  (This assumes the text
-is found in a periodical of some sort.  Were it found in a book, then
-the \textsf{incollection} type would serve your needs, and you could
-use \textsf{title} and \textsf{titleaddon} there.  While we're on the
-topic of exceptions, the \emph{Manual} includes an example --- 14.221
+\mybigspace As \colmarginpar{\textbf{review}} its name suggests, the
+\textsf{review} entry type was designed for reviews published in
+instructions above --- if you haven't, I recommend doing so now ---
+you'll know that \textsf{review} serves as well for citing other sorts
+of material with generic titles, like letters to the editor,
+obituaries, interviews, online comments and the like.  The primary
+rule is that any piece that has only a generic title, like
+\enquote{review of \ldots,} \enquote{interview with \ldots,} or
+\enquote{obituary of \ldots,} calls for the \textsf{review} type.  Any
+piece that also has a specific title, e.g., \enquote{\enquote{Lost in
+    \textsc{Bib}\TeX,} an interview with \ldots,} requires an
+\textsf{article} entry.  (This assumes the text is found in a
+periodical of some sort.  Were it found in a book, then the
+\textsf{incollection} type would serve your needs, and you could use
+\textsf{title} and \textsf{titleaddon} there.  While we're on the
+topic of exceptions, the \emph{Manual} includes an example --- 14.213
--- where the \enquote{Interview} part of the title is considered a
subtitle rather than a titleaddon, said part therefore being included
inside the quotation marks and capitalized accordingly.  Not having
@@ -7030,18 +9602,18 @@
for which are the same as for an \textsf{article} entry.  If it is a
\enquote{magazine} or a \enquote{newspaper}, then you need an
\textsf{entrysubtype} \texttt{magazine}, or the synonymous
-\textsf{entrysubtype} \mycolor{\texttt{newspaper}}.  The generic title
-goes in \textsf{title} and the other fields work just as as they do in
-an \textsf{article} entry with the same \textsf{entrysubtype},
-including the substitution of the \textsf{journaltitle} for the
-\textsf{author} if the latter is missing. (See 14.202--203, 14.205,
-14.208, 14.214--217, 14.221, 15.47; barcott:review, bundy:macneil,
-Clemens:letter, gourmet:052006, kozinn:review, nyt:trevorobit,
-unsigned:ranke, wallraff:word.)  If, on the other hand, the piece
-comes from a \enquote{journal,} then you don't need an
-\textsf{entrysubtype}.  The generic title goes in \textsf{title}, and
-the remaining fields work just as they do in a plain \textsf{article}
-entry.  (See 14.215; ratliff:review.)
+\textsf{entrysubtype} \texttt{newspaper}.  The generic title goes in
+\textsf{title} and the other fields work just as as they do in an
+\textsf{article} entry with the same \textsf{entrysubtype}, including
+the substitution of the \textsf{journaltitle} for the \textsf{author}
+if the latter is missing. (See 14.190--91, 14.195--96, 14.201--4,
+14.213, 15.49; barcott:review, bundy:macneil, Clemens:letter,
+gourmet:052006, kozinn:review, nyt:trevorobit, unsigned:ranke,
+wallraff:word.)  If, on the other hand, the piece comes from a
+\enquote{journal,} then you don't need an \textsf{entrysubtype}.  The
+generic title goes in \textsf{title}, and the remaining fields work
+just as they do in a plain \textsf{article} entry.  (See 14.202;
+ratliff:review.)

\mylittlespace The \emph{Manual} now suggests that, no matter which
citation style you are using, it is \enquote{usually sufficient to
@@ -7059,17 +9631,23 @@
you'll also need \texttt{useauthor=false} in the \textsf{options}
field.  Other surplus fields will be ignored.  (See osborne:poison.)

-\mylittlespace \textsf{Biblatex-chicago} \colmarginpar{New!} now also,
-at the behest of Bertold Schweitzer, supports the \textsf{relatedtype}
-\mycolor{\texttt{reviewof}}, which allows you to use the
-\textsf{related} mechanism to provide information about the work being
-reviewed.  This may be particularly helpful if you need to cite
-multiple reviews of the same work, but in any case the usual
-distinction between \textsf{article} and \textsf{review} entries still
-holds, with the \textsf{related} entry's \textsf{title} providing the
-\textsf{titleaddon} in the former type and the \textsf{title} in the
-latter.  Please see section \ref{sec:authrelated} for further details.
+\enlargethispage{\baselineskip}

+\mylittlespace \textsf{Biblatex-chicago} also, at the behest of
+Bertold Schweitzer, supports the \textsf{relatedtype}
+\texttt{reviewof}, which allows you to use the \textsf{related}
+mechanism to provide information about the work being reviewed,
+thereby simplifying how much information you need to provide in the
+reviewing entry.  In particular, it relieves you of the need to
+construct \textsf{title} or \textsf{titleaddon} fields like:
+\verb+review of \mkbibemph{Book Title} by Author+, as the
+\textsf{related} entry's \textsf{title} automatically provides the
+\textsf{title} in the \textsf{review} type and the \textsf{titleaddon}
+in the \textsf{article} type, with the \textsf{related} mechanism
+providing the connecting string.  This may be particularly helpful if
+you need to cite multiple reviews of the same work.  Please see
+section \ref{sec:authrelated} for further information.
+
\mylittlespace Most of the onerous details are the same as I described
them in the \textbf{article} section above, but I'll repeat some of
them briefly here.  If anything in the \textsf{title} needs
@@ -7081,37 +9659,110 @@
\textsf{entrysubtype} the \textsf{title} does the same.  In the former
case, \textsf{Biber} handles the sorting for you, but in the latter
you'll need a \textsf{sortkey} because \textsf{journaltitle} comes
-before \textsf{title} in the sorting scheme.  (14.175, 14.217;
-gourmet:052006, nyt:trevorobit, unsigned:ranke, and see
-\cmd{DeclareSortingTemplate} in section~\ref{sec:authformopts}, below.).
-As in \textsf{misc} entries with an \textsf{entrysubtype}, words like
-\enquote{interview,} \enquote{review,} and \enquote{letter} only need
-capitalization after a full stop, so you can start the \textsf{title}
-field with a lowercase letter and let the automatic field formatting
-with \cmd{autocap} do its work, though this isn't strictly necessary
-with \textsf{biblatex-chicago-authordate}.
+before \textsf{title} in the sorting scheme.  (14.204; gourmet:052006,
+nyt:trevorobit, unsigned:ranke, and see \cmd{DeclareSortingTemplate}
+in section~\ref{sec:authformopts}, below.).  As in \textsf{misc}
+entries with an \textsf{entrysubtype}, words like \enquote{interview,}
+\enquote{review,} and \enquote{letter} only need capitalization after
+a full stop, so you can start the \textsf{title} field with a
+lowercase letter and let the automatic field formatting with
+\cmd{autocap} do its work, though this isn't strictly necessary with
+\textsf{biblatex-chicago-authordate}.

-\mylittlespace One detail of the \textsf{review} type is new to both
-specifications, and responds to the needs of the 16th edition of the
-\emph{Manual}.  As I mentioned above, blogs are best treated as
-\textsf{articles} with \texttt{magazine} \textsf{entrysubtype},
-whereas comments on those blogs --- or on any similar sort of online
-content --- need the \textsf{review} type with the same
-\textsf{entrysubtype}.  What they will frequently also need is a date
-of some sort closely associated with the comment (14.246; ac:comment),
-so I have included the \textsf{eventdate} in \textsf{review} entries
-for just this purpose.  The \textsf{eventyear} will appear in
-citations and at the head of the reference list entry, while the
-remainder of the \textsf{eventdate} will be printed just after the
-\textsf{title}.  If, in addition, you need an identifying timestamp,
-then the \textsf{nameaddon} field is the place for it, but you'll have
-to provide your own parentheses, in order to preserve the possibility
-of providing pseudonyms in square brackets that is the standard
-function of this field in all other entry types, and possibly in the
-the \textsf{review} type as well.  (Cf.\ the documentation of
-\textsf{eventdate} in section~\ref{sec:fields:authdate},
+\mylittlespace A \colmarginpar{New!} few details of the
+\textsf{review} type are fairly new, and in particular have changed
+between the 16th and 17th editions of the \emph{Manual}.  As I
+mentioned above, blogs are best treated as \textsf{articles} with
+\texttt{magazine} \textsf{entrysubtype}, whereas comments on those
+blogs --- or replies to those comments, etc.\ --- need the
+\textsf{review} type with the same \textsf{entrysubtype}.  The 17th
+edition recommends that blog comments appear only in the text, and not
+in the reference list (15.51), so just as with comments in social
+media threads, for which see the \textbf{online} type above, I have
+provided the \mycolor{\texttt{commenton}} \texttt{relatedtype} to
+simplify the presentation of such material wherever you want it to
+appear.  Following the specifications, then, the default when you use
+\mycolor{\texttt{commenton}} is for
+\textsf{biblatex-chicago-authordate} to modify how your .bib entry
+appears in the .bbl file by setting both \texttt{skipbib} and
+\texttt{cmsdate=full} in the \textsf{options} field, so that nothing
+appears in the reference list and citations present the full date and
+possibly also a time stamp (see below).  Further, the style sets the
+\mycolor{\textsf{verbc}} field so that these entries don't interfere
+with the provision of extra date letters --- the full date and time
+should be enough to individuate separate comments.  Finally, the style
+creates a new \textsf{customc} entry in your .bbl file which you can
+cite after your initial \mycolor{\texttt{commenton}} entry using
+\cmd{autocites} and which will, as a comment to your initial entry,
+say whether it's a comment or a reply or what have you, and then
+giving the short citation of that upon which it is a comment.
+
+\mylittlespace As an example, take the blog ellis:blog, which does
+appear in the reference list.  The entry ac:comment presents a comment
+on this post using the \textsf{relatedtype}
+\mycolor{\texttt{commenton}}, so \textsf{biblatex-chicago-authordate}
+creates a new entry, ellis:blog-customc, which won't appear in your
+.bib file (which is never altered) but in the .bbl file that
+\textsf{biber} produces to supply \textsf{biblatex} with the data for
+its citations.  A command in your document like
+\verb+\autocites{ac:comment}{ellis:blog-customc}+ will produce a
+citation like (AC, July 1, 2008, 10:18 a.m.; comment on Ellis 2008).
+You can alter the string connecting the two citations (by default
+\verb+\bibstring{commenton}+) by using the \textsf{relatedstring}
+field in the first of them.  (Note how minimal the .bib entry of a
+comment using this system can be --- \textsf{author},
+\textsf{entrysubtype}, \textsf{related}, \textsf{relatedtype}, and
+\textsf{eventdate} are pretty much the only fields required.)
+
+\mylittlespace Those who want \textsf{online} comments to appear in
+the reference list can still use the \mycolor{\texttt{commenton}}
+\textsf{relatedtype}, and the same citation of the commented piece
+will appear there, connected by the same string that the
+\textsf{customc} entry provides.  Here, though, you can also provide a
+separate \textsf{url} for the comment, should it exist, which will be
+printed after the citation of the commented piece.  (In
+\textsf{online} entries, which use the same \textsf{relatedtype}, you
+can also provide a separate title for the comment.)  If you manually
+set either (or both) of the \texttt{cmsdate} or the \texttt{skipbib}
+options in your entry then \textsf{biblatex-chicago} will assume you
+want to hand-craft that entry without its intervention, though it will
+still provide the virtual \textsf{customc} entry in your .bbl file, as
+that may still prove convenient.  Note also that any
+\mycolor{\textsf{verbc}} field you provide will never be altered by
+the package.  (Please see the documentation of this
+\textsf{relatedtype} in section~\ref{sec:authrelated}, that of
+\mycolor{\textsf{verbc}} in section~\ref{sec:fields:authdate}, and
+also the information about online materials in
+
+\mylittlespace The new edition of the \emph{Manual} retains the
+requirement for a date closely associated with the comment (14.208,
+15.51), so in such entries you now have a choice.  If you are using
+the \mycolor{\texttt{commenton}} \textsf{relatedtype}, you can use the
+\textsf{date} or \textsf{eventdate} indifferently, as even when you
+print the entry in the reference list the reference to the main blog
+provides its own date.  If, in 16th-edition style, you print a fuller
+entry in the reference list, then you'll need the \textsf{eventdate}
+for the comment, as the \textsf{date} applies to the main blog post.
+If you need a time stamp in addition, as may frequently be the case
+with multiple contributions by the same author to a single thread,
+then you should now use the standard \textsf{biblatex} time-stamp
+format (e.g., \texttt{2008-07-01T10:18:00}) in whichever of the two
+date fields you're using, and not, as previously, in the
+\textsf{nameaddon} field.  \textsf{Biblatex-chicago} will format and
+print it appropriately.  This change allows the \textsf{nameaddon}
+field to revert to its primary use, which is to provide extra
+include the commenter's geographical location, which you need to
+enclose in parentheses, as I've removed the automatic square brackets
+from this field to allow it this more general usefulness.  You can, of
+course, still provide your own square brackets in \textsf{review}
+entries to indicate pseudonymous authorship, which is the standard
+documentation of \textsf{date}, \textsf{eventdate}, and
+\textsf{timezone} in section~\ref{sec:fields:authdate},
\cmd{DeclareLabeldate} in section~\ref{sec:authformopts}, and
-\texttt{avdate} in section~\ref{sec:authpreset}.)
+\texttt{avdate} in section~\ref{sec:authpreset}.

\mylittlespace For the reasons I explained in the \textsf{article}
docs above, I have brought the \textsf{article} and \textsf{review}
@@ -7133,8 +9784,54 @@
\textbf{shortjournal} in section~\ref{sec:fields:authdate} for all the
details on how this works.

-%%\enlargethispage{\baselineskip}
+\mybigspace In \colmarginpar{\textbf{standard}} older releases it was
+fairly straightforward to present published national or international
+standards using a \textsf{book} entry, but with some additional
+specifications now included in the 17th edition of the \emph{Manual}
+(14.259, 15.37) I think it might be helpful to provide a separate
+entry type.  The \mycolor{\textbf{standard}} type has long existed in
+\textsf{biblatex}, though none of its included styles use it.  In
+\textsf{biblatex-chicago} constructing such an entry is mostly
+straightforward.  The organization responsible for the standard goes
+in \textsf{organization}, the title in \textsf{title}, and the
+\textsf{series} and \textsf{number} fields provide the ID of the
+standard.  The \textsf{date} field generally provides the publication
+date, though for some standards there may also be a later
+reaffirmation date (or similar), for which you can use the
+\textsf{eventdate}.  To choose which year appears in citations, the
+\mycolor{\textbf{standard}} type follows, by default, the same
+ordering as \textsf{review} and \textsf{music} entries, so that the
+\textsf{eventdate} will, if present, provide the year.  (Cf.\
+\texttt{avdate} in section~\ref{sec:authpreset}, below.)

+\mylittlespace Now, for the peculiarities.  In the reference list, the
+\textsf{organization} will appear at the head of the entry, and will
+be reprinted as the publisher.  If you wish to provide a shortened
+version for the second appearance, then the \textsf{publisher} field
+is the place for it.  You can also use an \textsf{author} instead of
+an \textsf{organization}, but in such a case you'll have to provide a
+\textsf{publisher}, and no matter which field you choose to appear at
+the head of the entry you'll usually have to think about providing
+some sort of abbreviated form for citations.  A \textsf{shortauthor}
+will appear only in citations, while a \textsf{shorthand} can also
+appear at the head of the entry in the list of references.  (If you
+provide the latter, \textsf{biblatex-chicago} will automatically sort
+entries by it.)  Any named \textsf{editor} or \textsf{namec} will, as
+per the specification, \emph{not} appear at the head of entries.  You
+can really only alter this by using a \textsf{book} entry, instead.
+(Cf.\ w3c:xml, and the \textsf{shorthand} docs on
+
+\mylittlespace Finally, it is distinctly possible that an entry with
+two dates will need somehow to specify just what sort of dates are
+involved.  The usual \textsf{biblatex-chicago} method is the
+\textsf{userd} field, and here that field will act as a date-type for
+the \textsf{date} field itself, assuming as usual that there is no
+\textsf{urldate}.  For the \textsf{eventdate}, you'll need to use
+\textsf{howpublished}, which I have commandeered for this purpose in a
+few other entry types, as well.  (Cf.\ niso:bibref and
+\textbf{howpublished} in section~\ref{sec:fields:authdate}, below.)
+
\mybigspace This \mymarginpar{\textbf{suppbook}} is the entry type to
use if the main focus of a reference is supplemental material in a
book or in a collection, e.g., an introduction, afterword, or forward,
@@ -7160,13 +9857,11 @@
that unless you use a \cmd{bibstring} command in the \textsf{type}
field, the resultant entry will not be portable across languages.)

-% %\enlargethispage{\baselineskip}
-
\mylittlespace The other rules for constructing your .bib entry remain
the same.  The \textsf{author} field refers to the author of the
introduction or afterword, while \textsf{bookauthor} refers to the
-author of the main text of the work, if the two differ.  For the 16th
-edition, the \emph{Manual} requires that you include the page range
+author of the main text of the work, if the two differ.  Recent
+editions of the \emph{Manual} requires that you include the page range
for the cited part in the list of references.  As ever, if the focus
of the reference is the main text of the book, but you want to mention
the name of the writer of an introduction or afterword for
@@ -7173,7 +9868,7 @@
completeness, then the normal \textsf{biblatex} rules apply, and you
can just put their name in the appropriate field of a \textsf{book}
entry, that is, in the \textsf{foreword}, \textsf{afterword}, or
-\textsf{introduction} field.  (See \emph{Manual} 14.116;
+\textsf{introduction} field.  (See \emph{Manual} 14.110;
friedman:intro, polakow:afterw, prose:intro).

\mybigspace This \mymarginpar{\textbf{suppcollection}} fulfills a
@@ -7187,12 +9882,11 @@
periodicals, such as regular columns or letters to the editor.
\textsf{Biblatex} also provides the \textsf{review} type for this
purpose, so in both Chicago styles \textsf{suppperiodical} is an alias
-of \textsf{review}.  In the 16th edition of the \textsf{authordate}
-style, as discussed above, the use of this latter entry type has
-become necessary, so please see its documentation for instructions on
-how to construct a .bib entry for such works.
+of \textsf{review}.  Please see above under \textbf{review} for the
+full instructions on how to construct a .bib entry for such a
+reference.

-\mybigspace The \colmarginpar{\textbf{unpublished}}
+\mybigspace The \mymarginpar{\textbf{unpublished}}
\textsf{unpublished} entry type works largely as it does in standard
\textsf{biblatex}, though it's worth remembering that you should use a
lowercase letter at the start of your \textsf{note} field (or perhaps
@@ -7206,15 +9900,22 @@
prompting of Jan David Hauck, you can use the \textsf{venue},
fields further to specify unpublished conference papers and the like

-\mybigspace This \mymarginpar{\textbf{video}} is the last of the three
-audiovisual entry types, and as its name suggests it is intended for
-citing visual media, be it films of any sort or TV shows, broadcast,
-on the Net, on VHS, DVD, or Blu-ray.  As with the \textsf{music} type
-production roles found, e.g., on a DVD, to those bookish ones provided
-by \textsf{biblatex}.  Here are the main correspondences:
+\mybigspace This \colmarginpar{\textbf{video}} is the last of the
+three audiovisual entry types, and as its name suggests it is intended
+for citing visual media, be it films of any sort or TV shows,
+broadcast, on the Net, on VHS, DVD, or Blu-ray, though it will serve
+as well, I think, for radio broadcasts of plays or drama serials.  As
+with the \textsf{music} type discussed above, certain choices had to
+be made when associating the production roles found, e.g., on a DVD,
+to those bookish ones provided by \textsf{biblatex}.  The 17th edition
+of the \emph{Manual} once again revised its recommendations for this
+type, but fortunately the changes are additive, i.e., you can re-use
+16th-edition citations but are encouraged to peruse the following
+guidelines to see if there's any information you might think of adding
+to bring your citations more into line with the spec.  Here are the
+main guidelines:

\begin{description}
@@ -7233,11 +9934,14 @@
roles, you will need to identify them using the following:
\item[editortype, editoratype, editorbtype:] The most common roles,
all associated with specific bibstrings (or their absence), will
-  likely be \texttt{director}, \texttt{produ\-cer}, and, oddly,
+  likely be \texttt{director}, \texttt{producer}, and, oddly,
\texttt{none}.  The last is particularly useful if you want to
identify performers, as they usually don't need further specifying
and this role prevents \textsf{biblatex} from falling back on the
-  default \texttt{editor} bibstring.
+  default \texttt{editor} bibstring.  Any other roles you want to
+  emphasize, even if there is no pre-defined \cmd{bibstring}, can be
+  provided here, and will be printed as-is, contextually capitalized.
+  (Cf.\ hitchcock:nbynw.)
with the other audiovisual types, \textsf{video} serves as an
analogue both to books and to collections, so the \textsf{title} may
@@ -7244,25 +9948,37 @@
be of a whole film DVD or of a TV series, or it may identify one
episode in a series or one scene in a film.  In the latter cases,
the title of the whole would go in \textsf{booktitle}.  The
-  \textsf{booktitleaddon} field, in a change from the 15th edition,
-  may be useful for specifying the season and/or episode number of a
-  TV series, while the \textsf{titleaddon} is for any information that
-  needs to come between the \textsf{title} and the \textsf{booktitle}
-  (cleese:holygrail, episode:tv, handel:messiah).  As in the
-  \textsf{music} type, \textsf{maintitle} may be necessary for a boxed
-  set or something similar.
-\item[date, eventdate, origdate, pubstate:] The 16th edition of the
-  \textsf{Manual} now \enquote{recommends a more comprehensive
-    approach to dating audiovisual materials than in previous
-    editions} (15.53).  Indeed, \enquote{citations without a date are
-    generally unacceptable} (14.276), while if there is more than one
-  date \enquote{the date of the original recording should be
-    privileged} (15.53).  As with \textsf{music} entries, in order to
-  date fields for citing \textsf{video} sources, but their uses differ
-  somewhat between the two types.  In both, the \textsf{date} will
-  generally provide the publishing or copyright date of the medium you
-  are referencing.  More specific to this entry type, the
+  \textsf{booktitleaddon} field is the place for specifying the season
+  and/or episode number of a TV series, while the \textsf{titleaddon}
+  is for any information that needs to come between the \textsf{title}
+  and the \textsf{booktitle} (american:crime, cleese:holygrail,
+  friends:\break leia, handel:messiah, hitchcock:nbynw,
+  mayberry:brady).  As in the \textsf{music} type, \textsf{maintitle}
+  may be necessary for a boxed set or something similar.
+\item[\mycolor{entrysubtype:}] If, for some reason, you want to cite
+  an individual episode or scene without reference to any larger unit,
+  then your entry will contain only a \textsf{title}, which
+  \textsf{biblatex-chicago} would normally interpret as the title of a
+  complete film or TV series.  In such a case, you'll need to define
+  an \textsf{entrysubtype} to let it know that the lone \textsf{title}
+  is such a sub-unit.  In quite a different syntactic transformation,
+  the 17th edition (14.265) now recommends that, when presenting
+  episodes from a TV series, the name of the series
+  (\textsf{booktitle}) comes before the episode name (\textsf{title}).
+  The exact string \mycolor{\texttt{tvepisode}} in the
+  \textsf{entrysubtype} field achieves this reversal, which includes
+  using the \textsf{booktitle} as a \textsf{sorttitle} in the
+  reference list and also as the \textsf{labeltitle} in short notes.
+\item[date, eventdate, origdate, pubstate:] The 17th edition of the
+  \emph{Manual} continues to encourage writers to find some way of
+  dating audiovisual materials, while if there is more than one date
+  \enquote{the date of the original recording should be privileged}
+  (15.57).  As with \textsf{music} entries, in order to follow these
+  specifications I have had to provide three separate date fields for
+  citing \textsf{video} sources, but their uses differ somewhat
+  between the two types.  In both, the \textsf{date} will generally
+  provide the publishing or copyright date of the medium you are
+  referencing.  More specific to this entry type, the
\textsf{origdate} will generally hold the date of the original
theatrical release of a film, while the \textsf{eventdate} will most
commonly present either the broadcast date of a particular TV
@@ -7282,9 +9998,6 @@
the entry, though I have altered the string that is printed there.
Cf.\ friends:leia, handel:messiah, hitchcock:nbynw;
\textsf{pubstate}, below.
-\item[entrysubtype:] With the changes to the date fields detailed just
-  above, this field is no longer needed for \textsf{video} entries,
-  and will be ignored.
\item[type:] As in all the audiovisual entry types, the \textsf{type}
field holds the medium of the \textsf{title}, e.g., 8 mm, VHS, DVD,
Blu-ray, MPEG.
@@ -7292,10 +10005,11 @@

As with the \textsf{music} type, entries in \textsf{dates-test.bib}
should at least give you a good idea of how all this works.  (Cf.\
-14.279--80; \textsf{eventdate}, \textsf{origdate}, \textsf{userd};
+14.265, 14.267; \textsf{eventdate}, \textsf{origdate}, \textsf{userd};
\cmd{DeclareLabeldate} in section~\ref{sec:authformopts}, and
\texttt{avdate} in section~\ref{sec:authpreset}; cleese:holygrail,
-friends:leia, handel:messiah, hitchcock:nbynw, loc:city.)
+friends:leia, handel:messiah, hitchcock:nbynw, loc:city,
+weed:flatiron.)

\subsection{Entry Fields}
\label{sec:fields:authdate}
@@ -7318,7 +10032,7 @@
word that would ordinarily only be capitalized at the beginning of a
sentence, then simply ensure that that word is in lowercase, and the
style will take care of the rest.  Cf.\ \textsf{note}. (See
-\emph{Manual} 14.119, 14.166--68; davenport:attention,
+\emph{Manual} 14.114, 14.159--63; davenport:attention,
natrecoff:camera.)

\mybigspace In most \mymarginpar{\textbf{afterword}} circumstances,
@@ -7338,28 +10052,26 @@
it's an afterword at issue, simply define \textsf{afterword} any way
you please, leave \textsf{foreword} and \textsf{introduction}
undefined, and \textsf{biblatex-chicago} will do the rest. Cf.\
-\textsf{foreword} and \textsf{introduction}. (See \emph{Manual} 14.91,
-14.116; polakow:afterw.)
+\textsf{foreword} and \textsf{introduction}. (See \emph{Manual}
+14.105, 14.110; polakow:afterw.)

-%\enlargethispage{\baselineskip}
-
\mybigspace At \mymarginpar{\textbf{annotation}} the request of Emil
-Salim, \textsf{biblatex-chicago} has, as of version 0.9, added a
-package option (see \texttt{annotation} below, section
-\ref{sec:useropts}) to allow you to produce annotated lists of
-references.  The formatting of such a list is currently fairly basic,
-though it conforms with the \emph{Manual's} minimal guidelines
-(14.59).  The default in \textsf{chicago-authordate.cbx} is to define
-\cmd{DeclareFieldFormat\{an\-notation\}} using \cmd{par}\cmd{nobreak}
-\cmd{vskip} \cmd{bibitem\-sep}, though you can alter it by re-declaring
-the format in your preamble.  The page-breaking algorithms don't
-always give perfect results here, but the default formatting looks, to
-my eyes, fairly decent.  In addition to tweaking the field formatting
-you can also insert \cmd{par} (or even \cmd{vadjust\{\cmd{eject}\}})
-commands into the text of your annotations to improve the appearance.
-Please consider the \texttt{annotation} option a work in progress, but
-it is usable now.  (N.B.: The \textsc{Bib}\TeX\ field \textsf{annote}
-serves as an alias for this.)
+Salim, \textsf{biblatex-chicago} provides a package option (see
+\texttt{annotation} below, section~\ref{sec:authuseropts}) to allow
+you to produce annotated lists of references.  The formatting of such
+a list is currently fairly basic, though it conforms with the
+\emph{Manual's} minimal guidelines (14.64).  The default in
+\textsf{chicago-dates-common.cbx} is to define
+\verb+\DeclareFieldFormat{annotation}+ using
+\verb+\par\nobreak\vskip\bibitemsep #1+, though you can alter it by
+re-declaring the format in your preamble.  The page-breaking
+algorithms don't always give perfect results here, but the default
+formatting looks, to my eyes, fairly decent.  In addition to tweaking
+the field formatting you can also insert \cmd{par} (or even
+improve the appearance.  Please consider the \texttt{annotation}
+option a work in progress, but it is usable now.  (N.B.: The old
+\textsc{Bib}\TeX\ field \textsf{annote} serves as an alias for this.)

\mybigspace I \mymarginpar{\textbf{annotator}} have implemented this
\textsf{biblatex} field pretty much as that package's standard styles
@@ -7369,17 +10081,17 @@
\paragraph*{\protect\mymarginpar{\textbf{author}}}
For the most part, I have implemented this field in a completely
-standard \textsc{Bib}\TeX\ fashion.  Remember that corporate or
-organizational authors need to have an extra set of curly braces
-around them (e.g., \texttt{\{\{Associated Press\}\}}\,) to prevent
-\textsc{Bib}\TeX\ from treating one part of the name as a surname
-(14.92, 14.212, 15.36; assocpress:gun, chicago:man\-ual).  If there is
-no \textsf{author}, then \textsf{biblatex-chicago} will look, in
-sequence, for a \textsf{namea}, an \textsf{editor}, a \textsf{nameb},
-a \textsf{translator}, or a \textsf{namec} (i.e., a compiler) and use
+standard fashion.  Remember that corporate or organizational authors
+need to have an extra set of curly braces around them (e.g.,
+\texttt{\{\{Associated Press\}\}}\,) to prevent \textsf{biber} from
+treating one part of the name as a surname (14.84, 14.200, 15.37;
+assocpress:gun, chicago:manual).  If there is no \textsf{author}, then
+\textsf{biblatex-chicago} will look, in sequence, for a
+\textsf{namea}, an \textsf{editor}, a \textsf{nameb}, a
+\textsf{translator}, or a \textsf{namec} (i.e., a compiler) and use
that name (or those names) instead, followed by the appropriate
-identifying string (esp.\ 15.35, also 14.76, 14.87, 14.126, 14.132,
-14.189; boxer:china, brown:bremer, harley:cartography,
+identifying string (esp.\ 15.36, also 14.76, 14.103, 14.121, 14.126,
+14.180; boxer:china, brown:bremer, harley:cartography,
schellin\-ger:novel, sechzer:women, silver:gawain, soltes:georgia).
\textsf{Biber} and \textsf{biblatex} take care of alphabetizing
entries no matter which name appears at their head.  In citations,
@@ -7389,7 +10101,7 @@
\textsf{translator}, and \textsf{namec}.

\mylittlespace If you wish to emphasize the activity of an editor, a
-translator, or a compiler (14.90; eliot:pound), you can use the
+translator, or a compiler (14.104; eliot:pound), you can use the
\textsf{biblatex} options \texttt{useauthor=false},
\texttt{usenamea=false}, \texttt{use\-editor=false},
\texttt{usenameb=false}, \texttt{usetranslator=false}, and
@@ -7399,7 +10111,7 @@
remember to use the new option \texttt{usenamec} instead of the old
\texttt{usecompiler} (which I've deprecated), as the latter doesn't
work as smoothly and completely as \textsf{biblatex's} own name
-toggles.  See \cmd{DeclareSort\-ingTemplate} in
+toggles.  See \cmd{DeclareSortingTemplate} in
section~\ref{sec:authformopts}, and the \textsf{editortype}
documentation, below.

@@ -7414,24 +10126,22 @@
types, for further details.

\mylittlespace Recommendations concerning anonymous authors in other
-kinds of references have changed somewhat in the 16th edition of the
-\emph{Manual} (15.32), placing greater emphasis on using the
-\textsf{title} in citations and at the head of reference list entries,
-rather than \enquote{Anonymous.}  The latter may still in some cases
-be useful \enquote{in a bibliography in which several anonymous works
-  need to be grouped} (14.79), but even with a source like
-virginia:plantation, \enquote{the reference list entry should normally
-  begin with the title\ldots\ Text citations may refer to a short form
-  of the title but must include the first word (other than an initial
-  article)} (15.32).  The \textsf{shorttitle} field is the place for
-the short form, and you'll also need a \textsf{sortkey} of some sort
-if the full title begins with an article that is to be ignored when
-alphabetizing.
+kinds of references (15.34) emphasize using the \textsf{title} in
+citations and at the head of reference list entries, rather than
+\enquote{Anonymous.}  The latter may still in some cases be useful
+\enquote{in a bibliography in which several anonymous works need to be
+  grouped} (14.79), but even with a source like virginia:plantation,
+\enquote{the reference list entry should normally begin with the
+  title\ldots\ Text citations may refer to a short form of the title
+  but must include the first word (other than an initial article)}
+(15.34).  The \textsf{shorttitle} field is the place for the short
+form, and you'll also need a \textsf{sortkey} of some sort if the full
+title begins with an article that is to be ignored when alphabetizing.

\mylittlespace If \enquote{the authorship is known or guessed at but
was omitted on the title page,} then you need to use the
\textsf{authortype} field to let \textsf{biblatex-chicago} know this
-fact (15.33).  If the author is known (horsley:prosodies), then put
+fact (15.34).  If the author is known (horsley:prosodies), then put
\texttt{anon} in the \textsf{authortype} field, if guessed at
(cook:sotweed) put \texttt{anon?}\ there.  (In both cases,
\textsf{biblatex-chicago} tests for these \emph{exact} strings, so
@@ -7441,28 +10151,31 @@
\textsf{authortype} field, \textsf{biblatex-chicago-authordate} will
also do the right thing automatically in text citations.

-\enlargethispage{-\baselineskip}
-
-\mylittlespace The \textsf{nameaddon} field furnishes the means to
-cope with the case of pseudonymous authorship.  If the author's real
-name isn't known, simply put \texttt{pseud.}\ (or
-\cmd{bibstring\hfill\{pseudonym\}}) in that field (centinel:letters).
-If you wish to give a pseudonymous author's real name, simply include
-it there, formatted as you wish it to appear, as the contents of this
-field won't be manipulated as a name by \textsf{biblatex}
-(lecarre:quest, stendhal:parma).  If you have given the author's real
-name in the \textsf{author} field, then the pseudo\-nym goes in
-\textsf{nameaddon}, in the form \texttt{Firstname Lastname,\,pseud.}\
-(creasey:ashe:blast, creasey:morton:hide, creasey:york:death).
-This latter method will allow you to keep all references to one
-author's work under different pseudonyms grouped together in the list
-of references, a method recommended by the \emph{Manual}.  The 16th
-edition of the \emph{Manual} (14.84) has strengthened its policies
-about cross-references from author to pseudonym or vice versa, so in
-these latter examples I have included such references from the various
+\mylittlespace In most entry types (except \textsf{customc}) the
+\textsf{nameaddon} field furnishes the means to cope with the case of
+pseudonymous authorship.  If the author's real name isn't known,
+simply put \texttt{pseud.}\ (or \verb+\bibstring{pseudonym}+) in that
+field (centinel:letters).  If you wish to give a pseudonymous author's
+real name, simply include it there, formatted as you wish it to
+appear, as the contents of this field won't be manipulated as a name
+by \textsf{biblatex} (lecarre:quest, stendhal:parma).  If you have
+given the author's real name in the \textsf{author} field, then the
+pseudonym goes in \textsf{nameaddon}, in the form \texttt{Firstname
+  Lastname,\,pseud.}\ (creasey:ashe:blast, creasey:morton:hide,
+creasey:york:death).  This latter method will allow you to keep all
+references to one author's work under different pseudonyms grouped
+together in the list of references, a method recommended by the
+\emph{Manual}.  The \emph{Manual} (14.82) recommends using
+cross-references from author to pseudonym or vice versa, so in these
+latter examples I have included such references from the various
pseudonyms back to the author's name, using the \textsf{customc} entry
-type, which see (ashe:creasey, morton:creasey, york:creasey).
+type, which see (ashe:creasey, morton:creasey, york:creasey).  Please
+where you may need to provide your own square brackets when presenting
+a pseudonym.

+\enlargethispage{\baselineskip}
+
\mylittlespace As its name suggests, the author-date style very much
wants to have a name of some sort present both for the entries in the
list of references and for the in-text citations.  The \emph{Manual}
@@ -7479,20 +10192,18 @@
too long for in-text citations.  In unsigned:ranke I placed an
abbreviated form of the \textsf{journaltitle} into
\textsf{shortjournal}, adapting for a periodical the practice
-recommended for books in 15.32.  In iso:electrodoc, I provided a
+recommended for books in 15.37.  In iso:electrodoc, I provided a
\textsf{shorthand} field, which by default in
-\textsf{biblatex-chicago-authordate} will appear in text citations.
-Pursuant to the 16th edition's specifications, this \textsf{shorthand}
-will also appear at the head of the entry in the list of references,
+\textsf{biblatex-chicago-authordate} will appear both in text
+citations and at the head of the entry in the list of references,
followed, within the entry, by its expansion, this latter placed
-within parentheses.  You no longer, therefore, need to use a
-\textsf{customc} entry to provide the expansion --- please see
-\textsf{shorthand} below for the details.  (You can still utilize the
-list of shorthands to clarify the abbreviation, if you wish, and you
-can also provide a separate list of journal abbreviations using the
-\textbf{shortjournal} documentation, below, and the
-\texttt{journalabbrev} option in section~\ref{sec:authpreset}.)
+within parentheses.  Please see under \textbf{shorthand} below for the
+details.  (You can utilize the list of shorthands to clarify the
+abbreviation, if you wish, and you can also provide a separate list of
+journal abbreviations using the \cmd{printbiblist\{shortjournal\}}
+command.  Please cf.\ the \textbf{shortjournal} documentation, below,
+and the \texttt{journalabbrev} option in
+section~\ref{sec:authpreset}.)

\mybigspace In \mymarginpar{\textbf{authortype}}
\textsf{biblatex-chicago}, this field serves a function very much in
@@ -7499,8 +10210,8 @@
keeping with the spirit of standard \textsf{biblatex}, if not with its
letter.  Instead of allowing you to change the string used to identify
an author, the field allows you to indicate when an author is
-anonymous, that is, when his or her name doesn't appear on the title
-page of the work you are citing.  As I've just detailed under
+anonymous, that is, when their name doesn't appear on the title page
+of the work you are citing.  As I've just detailed under
\textsf{author}, the \emph{Manual} generally discourages the use of
\enquote{Anonymous} (or \enquote{Anon.} as an author, though in some
cases it may well be your best option.  If, however, the name of the
@@ -7514,10 +10225,8 @@
the brackets.  Assuming the strings are correct,
\textsf{biblatex-chicago} will also automatically do the right thing
in citations.  (See the \textsf{author} docs just above.  Also
-\emph{Manual} 15.33; cook:sotweed, horsley:prosodies.)
+\emph{Manual} 15.34; cook:sotweed, horsley:prosodies.)

-%%\enlargethispage{-\baselineskip}
-
\mybigspace For \mymarginpar{\textbf{bookauthor}} the most part, as in
\textsf{biblatex}, a \textsf{bookauthor} is the author of a
\textsf{booktitle}, so that, for example, if one chapter in a book has
@@ -7527,7 +10236,7 @@
(\textsf{suppbook}) uses \textsf{bookauthor} as the author of
\textsf{title} (polakow:afterw, prose:intro).

-\mybigspace This, \mymarginpar{\vspace{-12pt}\textbf{bookpagination}}
+\mybigspace This, \mymarginpar{\vspace{-8pt}\textbf{bookpagination}}
a standard \textsf{biblatex} field, allows you automatically to prefix
the appropriate string to information you provide in a \textsf{pages}
field.  If you leave it blank, the default is to print no identifying
@@ -7549,7 +10258,7 @@
strings you expect.  Second, remember that \textsf{bookpagination}
applies only to the \textsf{pages} field --- if you need to format a
citation's \textsf{postnote} field, then you must use
-\textsf{pagination}, which see (10.43--44, 14.154--163).
+\textsf{pagination}, which see (10.42--43, 14.147--56).

\mybigspace The \mymarginpar{\textbf{booksubtitle}} subtitle for a
\textsf{booktitle}.  See the next entry for further information.
@@ -7567,13 +10276,11 @@
\textsf{book} or \textsf{collection}), but there it will almost
invariably be providing information for the traditional
\textsc{Bib}\TeX\ cross-referencing apparatus (prairie:state), which I
-discuss below (\textbf{crossref}).  Such provision is unnecessary when
-using \textsf{Biber}.  The \textsf{booktitle} no longer takes
-sentence-style capitalization in \textsf{authordate}, though it does
+discuss below (\textbf{crossref}).  Such provision is now unnecessary,
+assuming you are using \textsf{biber}.  The \textsf{booktitle} no
+longer takes sentence-style capitalization in \textsf{authordate},

-%%\enlargethispage{\baselineskip}
-
\mybigspace An \mymarginpar{\textbf{booktitleaddon}} annex to the
\textsf{booktitle}.  It will be printed in the main text font, without
quotation marks.  If your data begins with a word that would
@@ -7585,10 +10292,12 @@
customize the punctuation that appears before the

-\mybigspace This \mymarginpar{\textbf{chapter}} field holds the
+\mybigspace This \colmarginpar{\textbf{chapter}} field holds the
chapter number, mainly useful only in an \textsf{inbook} or an
\textsf{incollection} entry where you wish to cite a specific chapter
-of a book (ashbrook:brain).
+of a book (ashbrook:brain).  It now also holds the track number of
+individual pieces of \textsf{music}, whether on a traditional format
+or on a streaming service (holiday:fool, rihanna:umbrella).

\mybigspace I \mymarginpar{\textbf{commentator}} have implemented this
\textsf{biblatex} field pretty much as that package's standard styles
@@ -7600,9 +10309,13 @@
introduced a modified one of its own (\textsf{xref}).  The latter
works as it always has, attempting to remedy some of the deficiencies
of the traditional mechanism by ensuring that child entries will
-inherit no data at all from their parents.  For the \textsf{crossref}
-field, when \textsf{Biber} is the backend, \textsf{biblatex} defines a
-series of inheritance rules which make it much more convenient to use.
+inherit no data at all from their parents.  Section~2.4.1 of
+\textsf{biblatex.pdf} contains useful notes on managing
+cross-referenced entries, and section~3.15 explains some of the
+limitations of the traditional backends, which offer only a small
+subset of \textsf{Biber's} features.  For the \textsf{crossref} field,
+when \textsf{Biber} is the backend, \textsf{biblatex} defines a series
+of inheritance rules which make it much more convenient to use.
Appendix B of \textsf{biblatex.pdf} explains the defaults, to which
\textsf{biblatex-chicago} has added several that I should mention
here: \textsf{incollection} entries can inherit from \textsf{book} and
@@ -7620,7 +10333,7 @@
function of the \textsf{crossref} and \textsf{xref} fields in
\textsf{biblatex-chicago} is as a trigger for the provision of
abbreviated entries in the list of references.  The \emph{Manual}
-(15.37) specifies that if you cite several contributions to the same
+(15.42) specifies that if you cite several contributions to the same
collection, all (including the collection itself) may be listed
separately in the list, which the package does automatically, using
the default inclusion threshold of 2 in the case both of
@@ -7631,7 +10344,7 @@
always implemented these instructions, but only if you use a
\textsf{crossref} or an \textsf{xref} field, and only in
\textsf{incollection}, \textsf{inproceedings}, or \textsf{letter}
-entries (on the last named, see just below).  More recently, I have
+entries (on the last named, see just below).  Recent releases have
considerably extended this functionality.

\mylittlespace First, I added five entry types --- \textbf{book},
@@ -7666,8 +10379,6 @@
looking at bernhard:boris, bernhard:ritter, bernhard:themacher,
harley:ancient:cart, harley:cartogra\-phy, and harley:hoc.

-%%\enlargethispage{\baselineskip}
-
\mylittlespace A published collection of letters requires a somewhat
different treatment (15.40).  In the author-date style, the
\emph{Manual} discourages individual letters from appearing in the
@@ -7704,7 +10415,7 @@
setting to provide abbreviated citations not just of the four entry
types mentioned but also of \textsf{book}, \textsf{bookinbook},
\textsf{collection}, and \textsf{proceedings} entries.
-\item[\qquad notes,bib:] These two options are carried over from the
+\item[\qquad notes, bib:] These two options are carried over from the
notes \&\ bibliography style; here they are synonymous with
\texttt{false} and \textsf{true}, respectively.
\end{description}
@@ -7720,7 +10431,7 @@
\emph{not} get any abbreviated citations in the reference list.
\item[\qquad false:] You'll get abbreviated citations in these entry
types in the reference list.
-\item[\qquad notes,bib:] These two options are carried over from the
+\item[\qquad notes, bib:] These two options are carried over from the
notes \&\ bibliography style; here they are synonymous with
\texttt{false} and \textsf{true}, respectively.
\end{description}
@@ -7733,16 +10444,16 @@
\textsf{biblatex-chicago} I recommended against using
\textsf{shorthand}, \textsf{reprinttitle} and/or \textsf{userf} fields
in combination with this abbreviated cross-referencing mechanism.  I
-have, however, received a request from Alexandre Ro\-berts to allow
-the shorthand to appear in the place of the abbreviated
-cross-reference as an additional space-saving measure, and one from
-Kenneth Pearce to permit the combination of the other two fields with
-\textsf{crossref}, as well.  All three of these fields, in any
-combination, should just work in such circumstances in
-\textsf{biblatex-chicago-authordate}, though if you are using a list
-of shorthands then you may need to include \texttt{skipbiblist} in the
-\textsf{options} field of some entries to avoid duplicates.  If you
-come across any problems or inaccuracies, please report them.
+received, however a request from Alexandre Roberts to allow the
+shorthand to appear in the place of the abbreviated cross-reference as
+an additional space-saving measure, and one from Kenneth Pearce to
+permit the combination of the other two fields with \textsf{crossref},
+as well.  All three of these fields, in any combination, should just
+work in such circumstances in \textsf{biblatex-chicago-authordate},
+though if you are using a list of shorthands then you may need to
+include \texttt{skipbiblist} in the \textsf{options} field of some
+entries to avoid duplicates.  If you come across any problems or

\mylittlespace Finally, there is also an \texttt{xrefurl} option
available to control the printing of \textsf{url}, \textsf{doi}, and
@@ -7750,7 +10461,7 @@
information might otherwise never appear.  See \texttt{xrefurl} in
section~\ref{sec:authuseropts}.

-\paragraph*{\protect\mymarginpar{\textbf{date}}}
+\paragraph*{\protect\colmarginpar{\textbf{date}}}
Predictably, this is one of the key fields for the author-date styles,
and one which, as a general rule, every .bib entry designed for this
@@ -7757,10 +10468,12 @@
system ought to contain.  So important is it, that
\textsf{biblatex-chicago-authordate} will, in most entry types, supply
a missing \cmd{bibstring\{nodate\}} if there is no date otherwise
-provided (15.41); citations will look like (Author, n.d.), and entries
-in the list of references will begin: Author, Firstname.\ n.d.  This
-seems simple enough, but there are a surprising number of
-complications which require attention.
+provided (15.44), or if there is only a \textsf{urldate}, and that
+date is an access\colmarginpar{New!} date, i.e., there's no
+\textsf{userd} field (15.50).  Citations will look like (Author,
+n.d.), and entries in the list of references will begin: Author,
+Firstname.\ n.d.  This seems simple enough, but there are a surprising
+number of complications which require attention.

\mylittlespace To start, in each entry, \textsf{Biber} attempts to
find something which it can designate a \textsf{labeldate}, which
@@ -7776,78 +10489,66 @@
instances, \textsf{Biber} will search each entry in the declared
order, and the first match will provide the \textsf{labeldate}.  Only
when it finds no match at all will it fall back on
-\cmd{bibstring\{nodate\}}.  Now, the entry types in which this
-automatic provision is turned off are \textsf{inreference},
-\textsf{misc}, and \textsf{reference}, none of which may be expected
-in the standard case to have a date provided.  In all other entry
-types \enquote{\texttt{n.d.}}\ will appear if no date is provided,
-though you can turn this off throughout the document in all entry
+\verb+\bibstring{nodate}+.  (In the \textsf{misc} and
+\mycolor{\textsf{dataset}} types this automatic provision is turned
+off, as such material may not be expected in many standard cases to
+have a usable date provided.)  You can prevent the appearance of
+\verb+\bibstring{nodate}+ throughout your document in all entry types
+\textsf{biblatex-chicago} in your preamble, or you can set it in the
+options field of individual entries.  (See
section~\ref{sec:authpreset}, below.)

\mylittlespace The thing to keep in mind is that \emph{only} for a
\textsf{labelyear} will \textsf{biblatex} provide what it calls the
-\textsf{extrayear} field, which means the alphabetical suffix
+\textsf{extradate} field, which means the alphabetical suffix
(1978\textbf{a}) to differentiate entries with the same author and
year.  A style can print any year it wants in a citation, but only the
-\textsf{labelyear} comes equipped with an \textsf{extrayear}.  (It is
+\textsf{labelyear} comes equipped with an \textsf{extradate}.  (It is
also, by the way, the field that the sorting algorithm will use for
ordering the list of references.)  So the challenge, in a style
wherein entries can contain more than one date, is to allow different
dates to appear in citations and at the head of reference list
entries, but to ensure that, as often as is possible, that date
-\emph{is} the \textsf{labeldate}.  In previous releases of
-\textsf{biblatex-chicago-authordate}, the search for a
-\textsf{labeldate} could occur in two possible orders: in
-\textsf{music}, \textsf{review}, and \textsf{video} entries, the
-default order was \textsf{eventdate, origdate, date, urldate}, while
-in all other entry types the order was \textsf{date, eventdate,
-  origdate, urldate}.  This, I believe, still works well for reference
-lists that contain relatively few entries with multiple dates, where
-using, e.g., an \textsf{origdate} at the head of an entry, even if it
-wasn't the \textsf{labeldate}, would rarely cause problems, because it
-was unlikely that there would be another entry by the same author with
-the same date (or \textsf{origdate}) requiring the \textsf{extrayear}
-field.  Judging from the feedback I've received, I significantly
-overestimated the likelihood that most reference lists would be so
-cooperative.  Users could always eliminate some of these dates from
-the running, or change the search order, using \cmd{DeclareLabeldate}
-in their preamble, but I had to hard-code the default order(s) into
-the author-date styles in order to cope with some tricky corners of
-the specification.  If users modified \cmd{DeclareLabeldate}, and
-their references entered these tricky corners, the results could be
-surprising.
+\emph{is} the \textsf{labeldate}.  This sounds simple, but in practice
+it requires a series of options for date presentation, and multiple
+iterations of the \cmd{DeclareLabeldate} command.  There are
+\emph{two} standard search orders set up by default: in
+\textsf{music}, \textsf{review}, \mycolor{\textsf{standard}},
+\textsf{suppperiodical}, and \textsf{video} entries, the default order
+is \textsf{eventdate, origdate, date, urldate}, while in all other
+entry types the default is \textsf{date, eventdate, origdate,
+  urldate}.  I believe that these defaults work well for most
+reference lists, especially those that contain relatively few entries
+with multiple dates, but if they don't work for you then the following
+options can help.

-\mylittlespace I have, therefore, included several means of coping
-with multiple dates in database entries, hoping that users might be
-able to choose one that works well for them.  These mechanisms include
-the \texttt{avdate} option, set to \texttt{true} by default, which
-treats as \emph{sui generis} \textsf{music}, \textsf{review}, and
-\textsf{video} entries.  They have their own rules, and their own
-version of \cmd{DeclareLabeldate} (\textsf{eventdate, origdate, date,
-  urldate}), so please see their documentation above in
-section~\ref{sec:types:authdate} for the details of how multiple dates
-will be treated in such entries, and also see \texttt{avdate} in
+\mylittlespace In the case of \textsf{music}, \textsf{review},
+\mycolor{\textsf{standard}}, \textsf{suppperiodical}, and
+\textsf{video} entries, the \texttt{avdate} (i.e., audio-visual date)
+option, set to \texttt{true} by default, can be set to \texttt{false}
+in your preamble to return these entry types to the general defaults.
+Please see the documentation of the entry types in
+section~\ref{sec:types:authdate} above for the details of how multiple
+dates will be treated in such entries, and also see \texttt{avdate} in
section~\ref{sec:authpreset}, below.  If you don't alter the
-\textsf{avdate} settings, the other settings I describe below don't
-apply to such entries.
+\texttt{avdate} settings, the other settings I am about to describe
+won't apply to such entries.  For the entry types not covered by the
+\texttt{avdate} option, the \emph{Manual} (15.40) presents a fairly
+simple scheme for when a particular entry has more than one date, but
+I have been unable to make its implementation quite as
+straightforward.  If a reprinted book, say, has both a \textsf{date}
+of publication for the reprint edition and an \textsf{origdate} for
+the original edition, then by default
+\textsf{biblatex-chicago-authordate} will use the \textsf{date} in
+citations and at the head of the entry in the reference list.  If you
+inform \textsf{biblatex-chicago} that the book is a reprint by putting
+the string \texttt{reprint} in the \textsf{pubstate} field, then a
+notice will be printed at the end of the entry saying \enquote{First
+  published 1898.}  With no \textsf{pubstate} field (and no
+\texttt{cmsdate} option), the algorithms will ignore the
+\textsf{origdate}.

-\mylittlespace For other entry types, the 16th edition of the
-\emph{Manual} (15.38) presents a fairly simple scheme for when a
-particular entry has more than one date, but I have been unable to
-make its implementation quite as straightforward.  If a reprinted
-book, say, has both a \textsf{date} of publication for the reprint
-edition and an \textsf{origdate} for the original edition, then by
-default \textsf{biblatex-chicago-authordate} will use the
-\textsf{date} in citations and at the head of the entry in the
-reference list.  If you inform \textsf{biblatex-chicago} that the book
-is a reprint by putting the string \texttt{reprint} in the
-\textsf{pubstate} field, then a notice will be printed at the end of
-the entry saying \enquote{Originally published in 1898.}  With no
-\textsf{pubstate} field (and no \texttt{cmsdate} option), the
-algorithms will ignore the \textsf{origdate}.
-
\mylittlespace If, \mymarginpar{\texttt{cmsdate}\\\emph{in entry}}
for any reason, you wish the \textsf{origdate} to appear at the head
of the entry, then your first option is to use the \texttt{cmsdate}
@@ -7868,7 +10569,7 @@
options.  If you want to present the \textsf{origdate} at the head
of an entry, then generally speaking you should probably use
\texttt{cmsdate=both}.  I have nevertheless retained this option for
-  certain cases where it has proved useful.  The 15th-edition options
+  certain cases where it has proved useful.  The obsolete options
\texttt{new} and \texttt{old} work like \texttt{both}.
\end{enumerate}

@@ -7896,7 +10597,7 @@
--- of the two works were the same?  Just as when it is ordering
entries, \textsf{biblatex} will always first process the contents of
the \textsf{labelyear} field when it is deciding whether to add the
-\textsf{extrayear} alphabetical suffix (\texttt{a,b,c} etc.)\ to the
+\textsf{extradate} alphabetical suffix (\texttt{a,b,c} etc.)\ to the
year to distinguish different works by the same author published in
the same year.  Our current hypothetical examples would look like
this: ([1896] 1974a) and ([1898] 1974b), with the suffixes
@@ -7911,8 +10612,6 @@
the \textsf{date} --- (Author [1898] 1974a) and (Author [1898] 1974b)
--- again avoiding ambiguity.

-\enlargethispage{\baselineskip}
-
\mylittlespace The \emph{Manual} doesn't give clear instructions for
how to cope with these situations, but
\textsf{biblatex-chicago-authordate} provides help.  You can't
@@ -7933,12 +10632,12 @@
\item \texttt{cmsdate=off} (the default) and \texttt{cmsdate=on}
\emph{both} print the \textsf{date} at the head of the entry in the
list of references and in citations: (Author 1898a), (Author 1898b).
-  As noted above, this style is no longer recommended by the 16th
-  edition of the \emph{Manual}, but it is still useful in some cases.
+  As noted above, this style is no longer recommended by the
+  \emph{Manual}, but may still be useful in some cases.
\item \texttt{cmsdate=both} prints both the \textsf{date} and the
\textsf{origdate}, using the \emph{Manual's}\ preferred format:
-  (Author [1898a] 1952), (Author [1898b] 1974).  The 15th-edition
-  options \texttt{old} and \texttt{new} are synonyms for this.
+  (Author [1898a] 1952), (Author [1898b] 1974).  The obsolete options
+  \texttt{old} and \texttt{new} are synonyms for this.
\end{enumerate}

If, for some reason, the automatic switching of the dates cannot be
@@ -7954,8 +10653,8 @@
preamble}} drastic method of simplifying the creation of databases
with a great many multi-date entries is to use the \texttt{cmsdate}
option \emph{in the preamble}.  Despite warnings in previous releases,
-users have plainly already been setting this option in their
-preambles, so I thought I might at least attempt to make it work as
+so I thought I might at least attempt to make it work as
\enquote{correctly} as I can.  The switches for this option are the
same as for the entry-only option, that is:

@@ -7971,15 +10670,15 @@
options.  If you want to present the \textsf{origdate} at the head
of an entry, then generally speaking you should probably use
\texttt{cmsdate=both}.  I have nevertheless retained this option for
-  certain cases where it has proved useful.  The 15th-edition options
+  certain cases where it might proved useful.  The obsolete options
\texttt{new} and \texttt{old} work like \texttt{both}.
\end{enumerate}

The important change for the user is that, when you set this option in
-your preamble to \texttt{on} or \texttt{both} (or to the 15th-edition
+your preamble to \texttt{on} or \texttt{both} (or to the obsolete
synonyms for the latter, \texttt{new} or \texttt{old}), then
\textsf{biblatex-chicago-authordate} will change the default
-\cmd{DeclareLa\-bel\-date} definition so that the \textsf{labelyear}
+\cmd{DeclareLabeldate} definition so that the \textsf{labelyear}
search order will be \textsf{origdate, date, eventdate, urldate}.
This means that for entry types not covered by the \texttt{avdate}
option, and for those types as well if you turn off that option, the
@@ -7987,7 +10686,7 @@
be that very date.  If you want \emph{every} such entry to present its
\textsf{origdate} in citations and at the head of reference list
entries, then setting the option this way makes sense, as you should
-automatically get the proper \textsf{extrayear} and the correct
+automatically get the proper \textsf{extradate} and the correct
sorting, without having to switch dates around counter-intuitively in
your .bib file.  A few clarifications may yet be in order.

@@ -8015,7 +10714,7 @@
a work has only one date, and there is no \texttt{switchdates} in the
\textsf{options} field, then \texttt{cmsdate=on} and
\texttt{cmsdate=both} will both result in the suppression of the
-\textsf{extrayear} field in that entry, that is, the year will no
+\textsf{extradate} field in that entry, that is, the year will no
longer be printed with its following lowercase letter used to
distinguish works by the same \textsf{author} published in the same
year.  Obviously, if the same options are set in the preamble, this
@@ -8022,52 +10721,205 @@
behavior is turned off, so that single-date entries will still work
properly without manual intervention.

+\mylittlespace Up\colmarginpar{\textsc{iso}8601-2\\Extended\\Format}
+to this point, the discussion of the \textsf{date} field has in fact
+presented no substantive alterations to the way it behaved in previous
+releases of \textsf{biblatex-chicago.}  With this release, however, I
+have implemented all of the applicable parts of \textsf{biblatex's}
+elegant, and long standing, support for the \textsc{iso}8601-2
+Extended Format specification, which means the package now provides
+greatly enhanced possibilities for presenting uncertain and
+unspecified dates and date ranges, along with date eras, seasons, and
+time stamps.  I have also implemented the \emph{Manual's} (9.64)
+guidelines for compressing year ranges, as well as providing a few
+more extras to help with some of the other tricky corners of the
+\emph{Manual's} instructions.  A combination of \textsf{biblatex} and
+\textsf{biblatex-chicago} package options allows you to define when,
+how, and where any of these extended specifications will appear in
+your documents.  I have attempted to provide as compliant a set of
+defaults as possible in \textsf{biblatex-chicago.sty}, but you can
+alter any of them according to your needs.  All are documented in
+purports to serve as a convenient reference guide to how this all
+works.
+
+\afterpage{\clearpage
+
+\begin{table}[h!]
+\hspace*{-2.5em}
+\begin{threeparttable}
+  \caption[\hspace{-1em}\mycolor{Enhanced Date Specifications}]
+  {Enhanced Date Specifications in biblatex-chicago}
+\begin{tabularx}{140mm}{@{}>{\ttfamily}llX@{}}
+\toprule
+\multicolumn{1}{@{}H}{Date Specification} &
+\multicolumn{2}{H}{Formatted Date (Examples use \texttt{american}
+  localization)\tnote{\textmd{a}}} \\
+\cmidrule(l){2-3}
+&
+\multicolumn{1}{H}{Output Format} &
+\multicolumn{1}{H}{Output Format Notes} \\
+\cmidrule{1-1}\cmidrule(l){2-2}\cmidrule(l){3-3}
+1723? & [1723?]\tnote{b} & \texttt{dateuncertain=true} set by default\\
+1723\textasciitilde & [ca. 1723]\tnote{b} & \texttt{datecirca=true} set by
+default\\
+1723\% & [ca. 1723?]\tnote{b} & Both \textsf{biblatex} options \texttt{true} by
+2016-05-24T15:34:00 & May 2, 2016, 3:34 p.m.\tnote{c} &
+\texttt{alltimes=12h} set by default \\
+2016-05-24T15:34:00 & May 2, 2016, 15:34\tnote{c} &
+-0876 & 877 BC & \texttt{dateera=christian} set in your preamble\\
+-0876/-0866 & 877--867 BC & \\
+0876 & AD 876\tnote{d} & \texttt{dateeraauto=1000} also in preamble\\
+-0876/0866 & 877 BC--AD 866 & \\
+0866/0876 & AD 866--76 & Cf.\ \mycolor{\texttt{compressyears}}, below\\
+-0876 & 877 BCE & \texttt{dateera=secular}, \texttt{dateeraauto=1000}\\
+-0876/-0866 & 877--867 BCE & \\
+0876 & 876 CE &  \\
+-0876/0866 & 877 BCE--866 CE & \\
+0866/0876 & 866--76 CE & Cf.\ \mycolor{\texttt{compressyears}}, below\\
+0343-02-03 & February 3, 343 CE & \\\addlinespace[.8mm]
+195X & 1950s\tnote{e,f} & Chicago option
+19XX & 20th c.\tnote{f} & Chicago option
+\mycolor{\texttt{centuryrange=true}} gets you 1900--1999;
+\mycolor{\texttt{alwaysrange=true}} does the same for this and the
+2004-22 & Summer 2004 &  \\
+1908/1912 & 1908--12\tnote{g} & Chicago option
+\mycolor{\texttt{compressyears=true}} set by default \\
+\bottomrule
+\end{tabularx}
+  \def\TPTnoteSettings{%
+    \setlength\leftmargin{1.5em}%
+    \setlength\labelwidth{.5em}%
+    \setlength\labelsep{.2em}%
+    \footnotesize
+    \rightskip\tabcolsep \leftskip\tabcolsep}%
+\begin{tablenotes}
+\item[a] In other languages both the strings and their
+    placement with respect to the year can and will differ.
+\item[b] The two Chicago options \mycolor{\texttt{nodatebrackets}}
+    and \mycolor{\texttt{noyearbrackets}} can remove the brackets
+    around the year in this context, though please note that they work
+    quite differently in the notes \&\ bibliography and author-date
+    styles. Please see their documentation in
+    sections~\ref{sec:useropts} and \ref{sec:authuseropts},
+    respectively.
+\item[c] Any time stamp that is part of a \textsf{urldate} will
+    appear in any entry type, though you can prevent this by setting
+    \mycolor{\texttt{urlstamp=false}}. Time stamps in \textsf{date}
+    and \textsf{origdate} fields will appear only in \textsf{article}
+    and \textsf{periodical} entries with a \texttt{magazine}
+    \textsf{entrysubtype}, as well as in all \textsf{online},
+    \textsf{review}, and \textsf{suppperiodical} entries. Such data in
+    \textsf{eventdate} fields will appear only in \textsf{review} and
+    \textsf{suppperiodical} entries. For timezones the four
+    \textsf{timezone} fields allow you to present Chicago's preferred
+    initialisms (\enquote{PST}). The \texttt{timezones} option is
+    \texttt{true} by default. By contrast, the \texttt{seconds} option
+    is not set by default, though you still need to include the
+    seconds, as above, for \textsf{biber} to process the time stamp.
+\item[d] The \texttt{annodomini} string appears before the year
+  \emph{only} in documents in some variant of English.
+\item[e] When the decade string would be ambiguous ---
+  \enquote{1900s} --- the style prints \enquote{1900--1909} instead.
+\item[f] For decades and centuries, the current state of the
+  \textsf{biber} code cannot process dates BCE / BC.
+\item[g] The Chicago rules for year-range compression differ from its
+  rules for page-range compression (9.61 \&\ 9.64). Dates BCE~/ BC are
+  never compressed. You must have loaded \textsf{biblatex-chicago.sty}
+  for the compression code to be available.
+\end{tablenotes}
+\vspace*{2em}
+\end{threeparttable}
+\end{table}}
+
\mylittlespace There are several more general remarks about the
-\textsf{date} field that may be helpful to users.  First, for most
-entry types, only a year is really necessary, and in most situations
-only the year --- or year range --- will be printed in text citations
-and at the head of entries in the list of references.  More specific
-\textsf{date} fields are often present, however, in \textsf{article},
-\textsf{misc}, \textsf{music}, \textsf{online}, \textsf{patent},
-\textsf{unpublished}, and \textsf{video} entries, for all of which any
-day or month provided will be printed later in the reference list
-entry.  If you follow the recommendations of the 16th edition of the
-\emph{Manual} and present newspaper and magazine articles
-\enquote{entirely within the text} (15.47), then the citations need to
-contain the complete \textsf{date} along with the
-\textsf{journaltitle}.  Placing \mymarginpar{\texttt{cmsdate=full}}
-\texttt{cmsdate=full} (and \texttt{skipbib}) in the \textsf{options}
-field of an \textsf{article} or a \textsf{review} entry, alongside a
-possible \texttt{useauthor=false}, should allow you to achieve this.
+\textsf{date} field that may be helpful to users of the author-date
+styles.  First, I highly recommend familiarizing yourself with the
+extended date specifications, as in many cases they will greatly
+simplify the creation of your .bib databases.  A \textsf{date} field
+like \verb+{1957?}+ in clark:mesopot not only lets the package provide
+the appropriate square brackets for you, it also means that the
+\textsf{year} field in the .bbl file sorts just as it should, and can
+be tested numerically for its relation to other date years in the
+entry.  A \textsf{year} field like \verb+{[1957?]}+ in the .bib
+database produces a field in the .bbl that neither sorts nor can be
+numerically tested.  The same holds for a compressed year range, as in
+tillich:system.  With \mycolor{\texttt{compressyears}} set to
+\texttt{true} by default, a \textsf{date} field like
+\verb+{1951/1963}+ lets the package decide what compression is
+correct, and provides \textsf{year} and \textsf{endyear} fields that
+sort and compare numerically for both \textsf{switchdates} and
+\textsf{extradate} tests.  Clearly, situations may still arise when a
+specially-crafted \textsf{year} or \textsf{origyear} field may be
+necessary, but if you can use the enhanced specifications then I
+
+\mylittlespace One\colmarginpar{\textsf{verbc}} possible drawback is
+that using these facilities makes a great many more dates available to
+the \textsf{extradate} mechanism which, it turns out, is something of
+a mixed blessing.  The \emph{Manual} isn't entirely forthcoming about
+what to do in the (vanishingly rare) case that two works by the same
+\textsf{author} have the same uncertain \textsf{date}.
+\textsf{Biblatex-chicago} will print the \textsf{extradate} in such
+situations, so that you could have \texttt{[1957?]a} followed by
+\texttt{[ca.~1957]b}, which may not be exactly right, nor exactly what
+you want.  Here, the new \mycolor{\textsf{verbc}} field can help ---
+giving the two entries different values of this field will prevent the
+the \mycolor{\textsf{verbc}} field below for all the details.
+
+\mylittlespace Second, for most entry types, only a year is really
+necessary, and in most situations only the year --- or year range ---
+will be printed in text citations and at the head of entries in the
+list of references.  More specific \textsf{date} fields are often
+present, however, in an unpredictably broad range of entries.  In a
+change to previous practice, a \textsf{date} with a year, month, and
+day will, even if the year appears at the head of the entry, be
+repeated in full later in the entry, while if there's only a month (or
+a season) and a year the month (or season) alone will follow.  Also
+new is the presentation of time stamps, which you can easily provide
+in your \textsf{date} fields (see examples and usage notes in
+really only necessary for news stories that are frequently updated
+\enquote{as they unfold} (14.191), or for online posts, particularly
+comments, that may need a time stamp for disambiguation.  If you wish
+to specify the time zone, the \emph{Manual} (10.41) prefers
+initialisms like \enquote{EST} or \enquote{PDT,} and these are most
+easily provided using the \mycolor{\texttt{timezone}} field, where you
+can include your own parentheses if so desired (cp.\ 14.191).  If you
+follow the recommendations of the \emph{Manual} and present newspaper
+and magazine articles \enquote{entirely within the text} (15.49), then
+the citations need to contain the complete \textsf{date} (and possible
+time stamp) along with the \textsf{journaltitle}.  Placing
+\mymarginpar{\texttt{cmsdate=full}} \texttt{cmsdate=full} (and
+\texttt{skipbib}) in the \textsf{options} field of an \textsf{article}
+or a \textsf{review} entry, alongside a possible
+\texttt{useauthor=false}, should allow you to achieve this.  For
+online comments in \textsf{online} or \textsf{review} entries this
+presentation is the default when you use the new
+\mycolor{\texttt{commenton}} \textsf{relatedtype}.  (See the
+documentation of those two types in section~\ref{sec:types:authdate},
+as well as \textsf{relatedtype} in section~\ref{sec:authrelated}.)
While we're on this subject, the \emph{Manual} is flexible (in both
-specifications) on abbreviating the names of months (14.180).  By
+specifications) on abbreviating the names of months (14.171).  By
default, \textsf{biblatex-chicago-authordate} uses the full names,
which you can change by setting the option \texttt{dateabbrev=true} in
-the preamble.  (Cf.\ assocpress:gun, barcott:review, batson,
-petroff:\-impurity, powell:email.)
+the preamble.  (Cf.\ ac:comment, assocpress:gun, barcott:review,
+petroff:impurity, powell:e\-mail.)

-\mylittlespace Second, when you need to indicate that a work is
-\enquote{\texttt{forthcoming},} and for some reason can't put
-\texttt{forthcoming} in the \textsf{pubstate} field, then the
-\textsf{year} field, instead of the \textsf{date} field, is the place
-for it, though you should use the \cmd{autocap} macro there to make
-sure the word comes out correctly in both citations and the list of
-references.  (The \textsf{pubstate} field more conveniently takes the
-bare string.)  The reason for the field switch is that the
-\textsf{date} field accepts only numerical data, in \textsc{iso}8601
-format (\texttt{yyyy-mm-dd}), whereas \textsf{year} can, conveniently,
-hold just about anything.  Third, it may be worth noting here that
-\textsf{Biber} is somewhat more exacting when parsing the
-\textsf{date} field than \textsc{Bib}\TeX, so a field looking like
-\texttt{1968/75} will simply be ignored, producing
-\enquote{\texttt{n.d.}}\ in the output --- you need \texttt{1968/1975}
-instead.  If you want a more compressed year range, then you'll want
-to use the \textsf{year} field.
-
-%%\enlargethispage{\baselineskip}
-
-\mylittlespace Fourth, in the \textsf{misc} entry type the
+\mylittlespace Third, in the \textsf{misc} entry type the
\textsf{date} field can help to distinguish between two classes of
archival material, letters and \enquote{letter-like} sources using
\textsf{origdate} while others (interviews, wills, contracts) use
@@ -8075,40 +10927,48 @@
for the details.)  If such an entry, as may well occur, contains only
an \textsf{origdate}, as can also be the case in \textsf{letter}
entries, then \textsf{Biber} and either \cmd{DeclareLabeldate}
-definition will make it work without further intervention.  Fifth, and
-finally, you can in most entry types qualify a \textsf{date} with the
+definition will make it work without further intervention.  Fourth,
+you can in most entry types qualify a \textsf{date} with the
\textsf{userd} field, assuming that the entry contains no
\textsf{urldate}.  For \textsf{music} and \textsf{video} entries,
there are several other requirements --- please see the documentation
-of \textsf{userd}, below.
+of \textsf{userd}, below.  Fifth, and finally, please note that the
+\textsf{nameaddon} field, which see, is no longer the place for time
+stamps, as it was in the 16th-edition styles.  Any such data there
+should be moved into the corresponding date field (either the
+\textsf{date} or the \textsf{eventdate}, typically).

\mylittlespace I recommend that you have a look through
\textsf{dates-test.bib} to see how all these complications will affect
the construction of your .bib database, especially at the following
entries: aristotle:metaphy:gr, creel:house, emerson:nature,
-james:ambas\-sa\-dors, mait\-land:canon, mait\-land:equity,
-schweit\-zer:bach, spock:in\-terview, white:ross:me\-mo, and
-white:russ.  Cf.\ also \textsf{origdate} and \textsf{year}, below; the
-\texttt{cmsdate}, \texttt{nodates}, and \texttt{switchdates} options
-in sections~\ref{sec:preset:authdate}, \ref{sec:authuseropts}, and
-\ref{sec:authentryopts}; and section~4.5.8 in \textsf{biblatex.pdf},
-and section \ref{sec:authformopts}, below, for the
-\cmd{DeclareLabeldate} command
+spock:interview, white:ross:memo, and white:russ.  Cf.\ also
+\textsf{origdate}, \textsf{timezone}, \mycolor{\textsf{verbc}}, and
+\textsf{year}, below; the \texttt{alldates}, \texttt{alltimes},
+\mycolor{\texttt{alwaysrange}}, \mycolor{\texttt{centuryrange}},
+\texttt{cmsdate}, \mycolor{\texttt{compressyears}},
+\texttt{datecirca}, \texttt{dateera}, \texttt{dateera\-auto},
+\mycolor{\texttt{nodatebrackets}}, \texttt{nodates},
+\mycolor{\texttt{noyearbrackets}},\break \texttt{switchdates},
+\texttt{timezones}, \mycolor{\texttt{urlstamp}}, and \texttt{urltime}
+options in sections~\ref{sec:preset:authdate}, \ref{sec:authuseropts},
+and \ref{sec:authentryopts}; and section~4.5.10 in
+\textsf{biblatex.pdf}, and section \ref{sec:authformopts}, below, for
+the \cmd{DeclareLabeldate} command.

-
\mybigspace This \mymarginpar{\textbf{day}} field, as of
\textsf{biblatex} 0.9, is obsolete, and will be ignored if you use it

\mybigspace Standard \mymarginpar{\textbf{doi}} \textsf{biblatex}
-field, providing the Digital Object Identifier of the work.  The 16th
-edition of the \emph{Manual} specifies that, given their relative
-permanence compared to URLs, \enquote{authors should include DOIs
-  rather than URLs for sources that make them readily available}
-(14.6; cf.\ 15.9).  (14.184; friedman:learn\-ing).  Cf.\ \textsf{url}.
+field, providing the Digital Object Identifier of the work.  The
+\emph{Manual} specifies that, given their relative permanence compared
+to URLs, \enquote{authors should prefer a DOI- or Handle-based URL
+  whenever one is available} (14.8).  (14.175; friedman:learning).
+Cf.\ \textsf{url}.

-%%\enlargethispage{-\baselineskip}
-
\mybigspace Standard \mymarginpar{\textbf{edition}} \textsf{biblatex}
field.  If you enter a plain cardinal number, \textsf{biblatex} will
convert it to an ordinal (chicago:manual), followed by the appropriate
@@ -8168,12 +11028,13 @@
as a means to specify additional contributors to texts in a number of
editorial roles.  In the Chicago styles they seem most relevant for
the audiovisual types, especially \textsf{music} and \textsf{video},
-where they help to identify conductors, directors, producers, and
+and now also the \mycolor{\textsf{performance}} type, in all of which
+they help to identify conductors, directors, producers, and
performers.  To specify the role, use the fields \textsf{editoratype},
\textsf{editorbtype}, and \textsf{editorctype}, which see.  (Cf.\
-bernstein:shostakovich, handel:messiah.)
+bernstein:shostakovich, hamilton:miranda, handel:messiah.)

-\mybigspace Normally, \mymarginpar{\textbf{editortype}} with the
+\mybigspace Normally, \colmarginpar{\textbf{editortype}} with the
exception of the \textsf{article} and \textsf{review} types with a
\texttt{magazine} \textsf{entrysubtype},
\textsf{biblatex-chicago-authordate} will automatically find a name to
@@ -8199,7 +11060,18 @@
field, and \textsf{biblatex} will print the correct string after the
name in the list of references.

-%\enlargethispage{\baselineskip}
+\mylittlespace In \colmarginpar{New!} previous releases of
+\textsf{biblatex-chicago} you could only use defined \cmd{bibstrings}
+in this field, at least if you wanted anything printed.  N.~Andrew
+Walsh pointed out that the standard \textsf{biblatex} styles will just
+print the field as-is in this case, allowing them to handle a great
+many unforeseen editorial roles with comparative ease, so I've
+implemented this, too, making sure to capitalize the string if the
+context demands it.  The string you choose will differ depending on
+whether it will be printed after a name at the head of an entry or
+before a name later on in the entry, e.g., \enquote{cartographer} or
+\enquote{maps created by.}  A bit of trial and error should see you
+through.

\mylittlespace There are a few details of which you need to be aware.
Because \textsf{biblatex-chicago} has added the \textsf{namea} field,
@@ -8222,6 +11094,8 @@
(\textsf{namea} or \textsf{editor}) appears at the head of the
reference-list entry.

+\enlargethispage{\baselineskip}
+
\mylittlespace In \textsf{biblatex} 0.9 Lehman reworked the string
concatenation mechanism, for reasons he outlines in his RELEASE file,
and I have followed his lead.  In short, if you define the
@@ -8244,29 +11118,36 @@
for example -- the \texttt{useauthor=false} mechanism is either
unnecessary or won't work properly in the following entry types:
\textsf{collection}, \textsf{letter}, \textsf{patent},
-\textsf{periodical}, \textsf{proceedings}, \textsf{suppbook},
-\textsf{suppcollection}, and \textsf{suppperiodical}.
+\textsf{periodical}, \textsf{proceedings}, \textsf{review},
+\textsf{suppbook}, \textsf{suppcollection}, and
+\textsf{suppperiodical}.

\mybigspace These
-\mymarginpar{\textbf{editoratype\\editorbtype\\editorctype}} fields
+\colmarginpar{\textbf{editoratype\\editorbtype\\editorctype}} fields
identify the exact role of the person named in the corresponding
-\textsf{editor[a-c]} field.  Note that they are not part of the string
+\textsf{editor[a-c]} field, just as \textsf{editortype} (q.v.) does
+for the \textsf{editor}.  Note that they are not part of the string
concatenation mechanism.  I have implemented them just as the standard
-styles do, and they have found a use particularly in \textsf{music}
+styles do, that is, if the field isn't a pre-defined \cmd{bibstring}
+it will be printed as-is, contextually capitalized.  They have found a
+use particularly in \textsf{music}, \mycolor{\textsf{performance}},
and \textsf{video} entries.  Cf.\ bernstein:shostakovich,
-handel:messiah.
+hamilton:miranda, and handel:messiah.

-\mybigspace Standard \mymarginpar{\textbf{eid}} \textsf{biblatex}
+\mybigspace Standard \colmarginpar{\textbf{eid}} \textsf{biblatex}
field, providing a string or number some journals use uniquely to
identify a particular article.  Only applicable to the
-\textsf{article} entry type.  Not typically required by the
-\emph{Manual}.
+\textsf{article} entry type, and only to those without a
+\texttt{magazine} \textsf{entrysubtype}.  The 17th edition of the
+\emph{Manual} now specifies where to print this (14.174), and I have
+moved it in accordance with its specifications.  It replaces the
+\textsf{pages} field in the list of references.

\paragraph*{\protect\mymarginpar{\textbf{entrysubtype}}}
Standard and very powerful \textsf{biblatex} field, left undefined by
the standard styles.  In \textsf{biblatex-chicago-authordate} it has
-four very specific uses, the first three of which I have designed in
+seven very specific uses, the first three of which I have designed in
order to maintain, as much as possible, backward compatibility with
the standard styles.  First, in \textsf{article} and
\textsf{periodical} entries, the field allows you to differentiate
@@ -8298,13 +11179,12 @@
\mylittlespace If you wish to reference a classical or medieval work
by the page numbers of a particular, non-standard edition, then you
shouldn't use the \texttt{classical} \textsf{entrysubtype} toggle.
-from the Renaissance and later, even if cited by the traditional
-divisions, seem to have citations formatted normally, and therefore
-don't need an \textsf{entrysubtype} field.  (See \emph{Manual}
-14.256--268; aristotle:metaphy:gr, plato:republic:gr;
-euripides:orestes is an example of a translation cited by page number
-in a modern edition.)
+the Renaissance and later, even if cited by the traditional divisions,
+seem to have citations formatted normally, and therefore don't need an
+\textsf{entrysubtype} field.  (See \emph{Manual} 14.242--54;
+aristotle:metaphy:gr, plato:republic:gr; euripides:orestes is an
+example of a translation cited by page number in a modern edition.)

\mylittlespace The third use of the \textsf{entrysubtype} field occurs
in \textsf{misc} entries.  If such an entry contains no such field,
@@ -8316,17 +11196,32 @@
above under \textbf{misc} for all the details on how these citations
work.

-\enlargethispage{-\baselineskip}
-
\mylittlespace Fourth, the field can be defined in the
\textsf{artwork} entry type in order to refer to a work from antiquity
whose title you do not wish to be italicized.  Please see the
-documentation of \textsf{artwork} above for the details.  (In previous
-releases, there was a special \texttt{tv} \textsf{entrysubtype} for
-\textsf{video} entries.  This is no longer necessary.  Please see the
-documentation of \textsf{video} in section~\ref{sec:types:authdate}
-above, and that of \textsf{userd} below.)
+documentation of \textsf{artwork} above for the details.  Fifth, you
+can define it in an \textbf{audio}, \textbf{music}, or \textbf{video}
+entry if such an entry refers to an individual unit that isn't part of
+any larger collection, the entry therefore having only a
+\textsf{title} and not a \textsf{booktitle}, a \textsf{title} that
+\textsf{biblatex-chicago} would normally interpret as the title of a
+larger unit (and therefore italicize).  Sixth, and sticking with the
+\textbf{video} type, though enacting quite a different syntactic
+transformation, the 17th edition (14.265) now recommends that, when
+presenting episodes from a TV series, the name of the series
+(\textsf{booktitle}) comes before the episode name (\textsf{title}).
+The exact string \mycolor{\texttt{tvepisode}} in the
+\textsf{entrysubtype} field achieves this reversal, which includes
+using the \textsf{booktitle} as a \textsf{sorttitle} in the list of
+references.

+\mylittlespace Seventh, and finally, you can use any
+\textsf{entrysubtype} whatever in \textsf{inreference} entries in
+order to treat them as inherently online works rather than standard
+published works.  See the documentation of \textbf{online} and
+\textbf{inreference} entries in section~\ref{sec:types:authdate},
+above, and also 14.233 and wikiped:bibtex.
+
\mybigspace Kazuo
\mymarginpar{\textbf{eprint}\\\textbf{eprintclass}\\\textbf{eprinttype}}
@@ -8337,45 +11232,72 @@
abbreviated references to online content than conventional URLs,
though I can find no specific reference to them in the \emph{Manual}.

-\mybigspace This \mymarginpar{\textbf{eventdate}} is a standard
-\textsf{biblatex} field.  In the 15th edition it was barely used, but
-in order to comply with changes in the 16th edition of the
-\emph{Manual} it plays a significant role in \textsf{music},
-\textsf{review}, and \textsf{video} entries.  In \textsf{music}
-entries, it identifies the recording or performance date of a
-particular song (rather than of a whole disc, for which you would use
-\textsf{origdate}), whereas in \textsf{video} entries it identifies
-either the original broadcast date of a particular episode of a TV
-series or the date of a filmed musical performance.  In both these
-cases \textsf{biblatex-chicago} will automatically prepend a bibstring
---- \texttt{recorded} and \texttt{aired}, respectively --- to the
-date, but you can change this string using the \textsf{userd} field,
-something you'll definitely want to do for filmed musical performances
-(friends:leia, handel:messiah, holiday:fool).
+\mybigspace This \colmarginpar{\textbf{eventdate}} is a standard
+\textsf{biblatex} field which has gradually accumulated functions in
+\textsf{biblatex-chicago}.  It can now play a role in
+\mycolor{\textsf{artwork}}, \mycolor{\textsf{audio}},
+\mycolor{\textsf{image}}, \textsf{music}, \textsf{review},
+\mycolor{\textsf{standard}}, \textsf{suppperiodical},
+\textsf{unpublished}, and \textsf{video} entries.  In \textsf{artwork}
+and \textsf{image} entries it identifies the publication date of, most
+frequently, a photograph, in association with the
+\textsf{howpublished} field which identifies the periodical or other
+medium in which it was published (mccurry:afghangirl).  In
+\textsf{standard} entries it will also usually be associated with a
+\textsf{howpublished} field, allowing you to specify a later renewal
+or reaffirmation of a standard (niso:bibref).  In \textsf{audio}
+entries, it specifies the release date of a single episode of a
+podcast (danforth:podcast).  In \textsf{music} entries, it identifies
+the recording or performance date of a particular song (rather than of
+a whole disc, for which you would use \textsf{origdate}), whereas in
+\textsf{video} entries it identifies either the original broadcast
+date of a particular episode of a TV series or the date of a filmed
+musical performance.  In both these cases \textsf{biblatex-chicago}
+will automatically prepend a bibstring --- \texttt{recorded} and
+\texttt{aired}, respectively --- to the date, but you can change this
+string using the \textsf{userd} field, something you'll definitely
+want to do for filmed musical performances (friends:leia,
+handel:messiah, holiday:fool).

+\mylittlespace In \textsf{unpublished} entries it identifies the date
+of an event at which an unpublished work was presented, though in
+truth the \textsf{date} will do as well here (nass:address).  The
+field's use in \textsf{review} and \textsf{suppperiodical} entries,
+finally, includes a possible time stamp.  In this context, an
+\textsf{eventdate} helps to identify a particular comment on, or reply
+to another comment on, a blog post.  Given that many such posts by a
+single \textsf{author} could appear on the same day, you can
+distinguish them by putting a time specification in the
+\textsf{eventdate} field itself (ac:comment).  Please see the
+\textbf{review} type, above, for the details of how to cite these
+materials, possibly with the help of the new
+\textsf{date} field docs above, in particular
+table~\ref{ad:date:extras}, for\colmarginpar{New!} details on how the
+\mycolor{\textsc{iso}8601-2 Extended Format specifications} offered by
+\textsf{biblatex}, including time stamps and much else besides, have
+been implemented in \textsf{biblatex-chicago}.
+
\mylittlespace In the default configuration of \cmd{DeclareLabeldate},
dates for citations and for the head of reference list entries are
searched for in the order \textsf{date, eventdate, origdate, urldate}.
This suits the Chicago author-date styles very well, except for
-\textsf{music} and \textsf{video} entries, where the general rule is
-to emphasize the earliest date, whether that be, for example, the
-recording date or original release date (15.53).  For these two entry
+\textsf{music}, \textsf{review}, \mycolor{\textsf{standard}},
+\textsf{suppperiodical}, and \textsf{video} entries.  In
+\textsf{music} and \textsf{video} entries the general rule is to
+emphasize the earliest date, whether that be, for example, the
+recording date or original release date (15.57).  The other three
+types have special requirements that once again necessitate putting
+the \textsf{eventdate} at the head of the queue.  For these five entry
types, then, \cmd{DeclareLabeldate} uses the order \textsf{eventdate,
origdate, date, urldate}.  (See the \texttt{avdate} option in
section~\ref{sec:authpreset}, below.)

-\mylittlespace For \textsf{review} entries I use the same, custom
-definition of \cmd{DeclareLabeldate}, but for somewhat different
-reasons.  In general, such an entry will only have a \textsf{date},
-but an \textsf{eventdate} can be used to identify a particular comment
-within an online thread.  The year of the comment will therefore
-appear at the head of the entry and in citations, while the remainder
-of the \textsf{eventdate} will appear just after the \textsf{title},
-and the \textsf{date} after the \textsf{journaltitle}.  There isn't a
-particular string associated with the \textsf{eventdate}, but you can
-further specify a comment by placing a time\-stamp in parentheses in
-the \textsf{nameaddon} field, in case the date alone isn't enough
-(14.246; ac:comment, ellis:blog).
+\mybigspace This \colmarginpar{\textbf{eventtimezone}} field can, if
+necessary, specify the time zone associated with a time stamp given as
+part of an \textsf{eventdate}.  The \emph{Manual} prefers initialisms
+like \enquote{EST} for this purpose, and you can provide parentheses
+around it at your discretion (cp.\ 10.41 and 14.191).

\mybigspace As \mymarginpar{\textbf{foreword}} with the
\textsf{afterword} field above, \textsf{foreword} will in general
@@ -8392,14 +11314,28 @@
subject, but \textsf{biblatex-chicago} prints it (them), in
parentheses, just after the author(s).

-\enlargethispage{-\baselineskip}
+\mybigspace Standard \colmarginpar{\textbf{howpublished}}
+\textsf{biblatex} field which, like the \textsf{eventdate} field, is
+gradually accumulating functions in \textsf{biblatex-chicago}.  In the
+\textsf{booklet} type it retains something of its traditional usage,
+replacing the \textsf{publisher}, and has a similar (somewhat
+paradoxical) place in \textsf{unpublished} entries.  In the
+\textsf{misc} and \mycolor{\textsf{performance}} types it works almost
+as a second \textsf{note} field, bringing in extra information about a
+work in close association with the \textsf{type} and \textsf{version}
+fields, while the \mycolor{\textsf{dataset}} entry type associates it
+both with those two fields and with the \textsf{number} field.
+17th-edition \textsf{music} entries require a field to provide the
+so \textsf{howpublished} works there as an online double of
+\textsf{type} and of \textsf{publisher}.  Finally, in
+\textsf{artwork}, \textsf{image}, and \mycolor{\textsf{standard}}
+entries it serves to qualify or modify an \textsf{eventdate}, almost
+as a \textsf{userd} field modifies a \textsf{date} or
+\textsf{urldate}.  Please see the docs of those entry types for more
+information, and also bedford:photo, clark:mesopot,
+mccurry:afghangirl, niso:bibref, rihanna:umbrella.

-\mybigspace Standard \mymarginpar{\textbf{howpublished}}
-\textsf{biblatex} field, mainly applicable in the \textsf{booklet}
-entry type, where it replaces the \textsf{publisher}.  I have also
-retained it in the \textsf{misc} and \textsf{unpublished} entry types,
-for historical reasons.
-
\mybigspace Standard \mymarginpar{\textbf{institution}}
\textsf{biblatex} field.  In the \textsf{thesis} entry type, it will
usually identify the university for which the thesis was written,
@@ -8432,7 +11368,10 @@
field, designed for \textsf{article} or \textsf{periodical} entries
identified by something like \enquote{Spring} or \enquote{Summer}
rather than by the usual \textsf{month} or \textsf{number} fields
-(brown:bre\-mer).
+(brown:bre\-mer).  \textsf{Biblatex's} enhanced date handling allows
+you to specify a season in the \textsf{date} field, with the
+\enquote{months} 21--24 used for Spring, Summer, Autumn, and Winter,

\mybigspace The \mymarginpar{\textbf{issuesubtitle}} subtitle for an
\textsf{issuetitle} --- see next entry.
@@ -8468,27 +11407,13 @@
print a list of journal abbreviations.  Cf.\ the \textsf{shortjournal}
documentation below.

-\enlargethispage{\baselineskip}
-
\mybigspace This \mymarginpar{\textbf{keywords}} field is
-\textsf{biblatex}'s extremely powerful and flexible technique for
-filtering entries in a list of references, allowing you to subdivide
-it according to just about any criteria you care to invent.  See
-\textsf{biblatex.pdf} (3.11.4) for thorough documentation.  In
-\textsf{biblatex-chicago}, the field provides one convenient means to
-exclude certain entries from making their way into a list of
-references, though the toggle \texttt{skipbib} in the \textsf{options}
-field works just as well, and perhaps more simply.  There are a few
-reasons for so excluding entries.  When citing both an original text
-and its translation (see \textbf{userf}, below), the \emph{Manual}
-(14.109) suggests including the original at the end of the
-translation's reference list entry, a procedure which requires that
-the original not also be printed as a separate entry
-(aristotle:metaphy:trans, aristotle:metaphy:gr).  Well-known reference
-works (like the \emph{Encyclopaedia Britannica}, for example) and many
-sacred texts need only be presented in citations, and not in the list
-of references (14.247--248; ency:britannica, genesis, wikiped:bibtex;
-see \textsf{inreference} and \textsf{misc}, above).
+\textsf{biblatex}'s powerful and flexible technique for filtering
+entries in a list of references, allowing you to subdivide it
+according to just about any criteria you care to invent, or indeed to
+prevent entries in citations from appearing in reference list, as the
+\emph{Manual} sometimes recommends.  See \textsf{biblatex.pdf} (3.7)
+for thorough documentation.

\mybigspace A \mymarginpar{\textbf{language}} standard
\textsf{biblatex} field, designed to allow you to specify the
@@ -8500,15 +11425,15 @@
when the title of a work is given in translation, even though no
translation of the work has been published, something that might
happen when a title is in a language deemed to be unparseable by a
-chu:panda, pirumova, rozner:liberation).  In such a case, you should
-provide the language(s) involved using this field, connecting multiple
-languages using the keyword \texttt{and}.  (I have retained
-\textsf{biblatex's} \cmd{bibstring} mechanism here, which means that
-you can use the standard bibstrings or, if one doesn't exist for the
-language you need, just give the name of the language, capitalized as
-it should appear in your text.  You can also mix these two modes
-inside one entry without apparent harm.)
+rozner:liberation).  In such a case, you should provide the
+language(s) involved using this field, connecting multiple languages
+using the keyword \texttt{and}.  (I have retained \textsf{biblatex's}
+\cmd{bibstring} mechanism here, which means that you can use the
+standard bibstrings or, if one doesn't exist for the language you
+need, just give the name of the language, capitalized as it should
+appear in your text.  You can also mix these two modes inside one
+entry without apparent harm.)

\mylittlespace An alternative arrangement suggested by the
\emph{Manual} is to retain the original title of a piece but then to
@@ -8525,8 +11450,6 @@
probably manage it with special formatting inside those fields
themselves.

-%%\enlargethispage{\baselineskip}
-
\mybigspace I \mymarginpar{\textbf{lista}} intend this field
specifically for presenting citations from reference works that are
arranged alphabetically, where the name of the article rather than a
@@ -8538,7 +11461,7 @@
\enquote{s.vv.}).  \textsf{Biblatex-chicago} will only print such a
field in a \textsf{book} or an \textsf{inreference} entry, and you
should look at the documentation of these entry types for further
-details.  (See \emph{Manual} 14.247--248; grove:sibelius, times:guide,
+details.  (See \emph{Manual} 14.232--33; grove:sibelius, times:guide,
wikiped:bibtex.)

\mybigspace This \mymarginpar{\textbf{location}} is
@@ -8545,15 +11468,13 @@
\textsf{biblatex}'s version of the usual \textsc{Bib}\TeX\ field
\textsf{address}, though the latter is accepted as an alias if that
simplifies the modification of older .bib files.  According to the
-\emph{Manual} (14.135), a citation usually need only provide the first
+\emph{Manual} (14.129), a citation usually need only provide the first
city listed on any title page, though a list of cities separated by
the keyword \enquote{\texttt{and}} will be formatted appropriately.
If the place of publication is unknown, you can use
-\cmd{autocap\{n\}.p.}\ instead (14.138).  For all cities, you should
-use the common English version of the name, if such exists (14.137).
+\verb+\autocap{n}.p.+\ instead (14.132).  For all cities, you should
+use the common English version of the name, if such exists (14.131).

-%%\enlargethispage{\baselineskip}
-
\mylittlespace Two other uses need explanation here.  In
\textsf{article}, \textsf{periodical}, and \textsf{review} entries,
there is usually no need for a \textsf{location} field, but
@@ -8560,16 +11481,16 @@
\enquote{if a journal might be confused with another with a similar
title, or if it might not be known to the users of a bibliography,}
then this field can present the place or institution where it is
-published (14.191, 14.203; garrett, kimluu:diethyl, and
+published (14.182, 14.191, 14.193--94; garrett, kimluu:diethyl, and
lakeforester:pushcarts).  For blogs cited using \textsf{article}
entries, this is a good place to identify the nature of the source ---
i.e., the word \enquote{blog} --- letting the style automatically
-provide the parentheses (14.246; ellis:blog).
+provide the parentheses (15.51; ellis:blog).

\mybigspace The \mymarginpar{\textbf{mainsubtitle}} subtitle for a
\textsf{maintitle} --- see next entry.

-\mybigspace The \mymarginpar{\textbf{maintitle}} main title for a
+\mybigspace The \colmarginpar{\textbf{maintitle}} main title for a
multi-volume work, e.g., \enquote{Opera} or \enquote{Collected Works.}
It no longer takes sentence-style capitalization in
\textsf{authordate}, though it does in \textsf{authordate-trad}.  In
@@ -8579,6 +11500,14 @@
euripides:orestes, harley:carto\-graphy, lach:asia,
pelikan:christian, and plato:republic:gr.)

+\mylittlespace Because \colmarginpar{New!} the 17th edition of the
+\emph{Manual} recommends that you present not only the names of blogs
+but also the names of their parent (usually periodical) publications,
+I have added this field to \textsf{article}, \textsf{periodical}, and
+\textsf{review} entries for just this purpose.  See the documentation
+of those entry types in section~\ref{sec:types:authdate}, above, and
+
\mybigspace An \mymarginpar{\textbf{maintitleaddon}} annex to the
\textsf{maintitle}, for which see previous entry.  Such an annex would
be printed in the main text font.  If your data begins with a word
@@ -8618,30 +11547,47 @@
\textsf{namec}, \textsf{translator}, and the macros \cmd{partedit},
\cmd{parttrans}, \cmd{parteditandtrans}, \cmd{partcomp},
\cmd{parteditandcomp}, \cmd{parttransandcomp}, and
-\cmd{partedittransand\-comp}, for which see
+\cmd{partedittransandcomp}, for which see
section~\ref{sec:formatting:authdate}.

-\mybigspace This \mymarginpar{\textbf{nameaddon}} field is provided
+\mybigspace This \colmarginpar{\textbf{nameaddon}} field is provided
by \textsf{biblatex}, though not used by the standard styles.  In
\textsf{biblatex-chicago}, it allows you to specify that an author's
-name is a pseudo\-nym, or to provide either the real name or the
+name is a pseudonym, or to provide either the real name or the
pseudonym itself, if the other is being provided in the
\textsf{author} field.  The abbreviation
\enquote{\texttt{pseud.}\hspace{-2pt}}\ (always lowercase in English)
is specified, either on its own or after the pseudonym
(centinel:letters, creasey:ashe:blast, creasey:morton:hide,
-creasey:york:death, and le\-carre:quest); \cmd{bibstring\{pseudonym\}}
+creasey:york:death, and lecarre:quest); \verb+\bibstring{pseudonym}+
does the work for you.  See under \textbf{author} above for the full
details.

-\mylittlespace In \textsf{review} entries, I have removed the
-automatic provision of square brackets from the field, allowing it to
-be used in at least two ways.  First, if you provide your own square
-brackets, then it can have its standard function, as above.  Second,
-you can further specify comments to blogs and other online content
-using a timestamp (in parentheses) that supplements the
-\textsf{eventdate}, particularly when the latter is too coarse a
-specification to identify a comment unambiguously.  Cf.\ ac:comment.
+\mylittlespace In \textsf{online, review,} and \textsf{suppperiodical}
+entries, as well as in \textsf{misc} entries with an
+\textsf{entrysubtype}, I have removed the automatic provision of
+square brackets from the field, allowing it to be used in at least two
+ways.  First, if you provide your own square brackets, then it can
+have its standard function, as above.  Second you can, within
+parentheses, provide a screen name for online social media, or merely
+archive.  (The 16th edition of the \emph{Manual} recommended
+specifying comments to blogs and other online content using a time
+stamp in parentheses after the \textsf{author}, but the 17th edition
+\colmarginpar{New!} handles time stamps differently.  In this case the
+\emph{Manual} (15.52) now specifies that comments should appear
+\enquote{only in the text, in reference to the related post,} so I've
+provided some new functionality to enable this.  Please see the
+\textbf{online} and \textbf{review} types, above, especially
+table~\ref{tab:online:adtypes}, for the details of how to cite these
+materials, possibly with the help of the new
+\mycolor{\texttt{commenton}} \textsf{relatedtype} and a separate
+in particular table~\ref{ad:date:extras}, for details on how the
+\mycolor{\textsc{iso}8601-2 Extended Format specifications} offered by
+\textsf{biblatex}, including time stamps and much else besides, have
+been implemented in \textsf{biblatex-chicago}.  Cf.\ ellis:blog,
+obrien:recycle.)

\mylittlespace In the \textsf{customc} entry type, finally, which is
used to create alphabetized cross-references to other entries in the
@@ -8680,7 +11626,7 @@
\cmd{partcomp}, \cmd{parteditandcomp}, \cmd{parttransandcomp}, and
\cmd{partedittransandcomp} in section~\ref{sec:formatting:authdate}.

-\mybigspace The \mymarginpar{\textbf{namec}} \emph{Manual} (15.35)
+\mybigspace The \mymarginpar{\textbf{namec}} \emph{Manual} (15.36)
specifies that works without an author may be listed under an editor,
translator, or compiler, assuming that one is available, and it also
specifies the strings to be used with the name(s) of compiler(s).  All
@@ -8746,11 +11692,15 @@
automatically do the right thing.  Cf.\ \textsf{addendum}.

\mybigspace This \mymarginpar{\textbf{number}} is a standard
-\textsf{biblatex} field, containing the number of a
+\textsf{biblatex} field, steadily accumulating uses in
+\textsf{biblatex-chicago}.  It may contain the number of a
\textsf{journaltitle} in an \textsf{article} or \textsf{review} entry,
the number of a \textsf{title} in a \textsf{periodical} entry, the
-volume/number of a book in a \textsf{series}, or the (generally
-numerical) specifier of the \textsf{type} in a \textsf{report} entry.
+volume/number of a book (or musical recording) in a \textsf{series},
+the (generally numerical) specifier of the \textsf{type} in a
+\textsf{report} entry, the archive location (or database accession
+number) of a \textsf{dataset} entry, and the number of a national or
+international standard in a \mycolor{\textsf{standard}} entry.
Generally, in an \textsf{article}, \textsf{periodical}, or
\textsf{review} entry, this will be a plain cardinal number, but in
such entries \textsf{biblatex-chicago} does the right thing if you
@@ -8760,21 +11710,19 @@
example, while the \textsf{series} field in such an entry will contain
the name of the series, rather than a number.  This field is also the
place for the patent number in a \textsf{patent} entry.  Cf.\
-\textsf{issue} and \textsf{series}.  (See \emph{Manual} 14.128--132
-and boxer:china, palmatary:pottery, wauchope:ceramics; 14.180--181 and
-gibbard, hlatky:hrt, mcmillen:antebellum, rozner:liberation,
-warr:el\-lison.)
+\textsf{issue} and \textsf{series}.  (See 14.123--25 and boxer:china,
+palmatary:pottery, wauchope:ceramics; 14.171 and beattie:crime,
+mcmillen:antebellum, rozner:liberation, warr:ellison; 14.257 and
+genbank:db; 14.259 and niso:bibref; 14.263 and holiday:fool.)

\mylittlespace \textbf{NB}: This may be an opportune place to point
-out that the \emph{Manual} (14.154) prefers arabic to roman numerals
+out that the \emph{Manual} (14.147) prefers arabic to roman numerals
in most circumstances (chapters, volumes, series numbers, etc.), even
when such numbers might be roman in the work cited.  The obvious
exception is page numbers, in which roman numerals indicate that the
citation came from the front matter, and should therefore be retained.

-\enlargethispage{\baselineskip}
-
\mybigspace A \mymarginpar{\textbf{options}} standard
\textsf{biblatex} field, for setting certain options on a per-entry
basis rather than globally.  Information about some of the more common
@@ -8792,25 +11740,31 @@
\textsf{inproceedings} entry, and I have retained this as a
possibility, though the \emph{Manual} is silent on the matter.

-\mybigspace This \mymarginpar{\textbf{origdate}} is a standard
+\enlargethispage{\baselineskip}
+
+\mybigspace This \colmarginpar{\textbf{origdate}} is a standard
\textsf{biblatex} field which allows more than one full date
-specification for those references which need to provide more than
-just one.  As with the analogous \textsf{date} field, you provide the
-date (or range of dates) in \textsc{iso}8601 format, i.e.,
-\texttt{yyyy-mm-dd}.  In most entry types, you would use
+specification for those references which need it.  (You can also
+provide a time stamp in the field, after an uppercase
+\enquote{\texttt{T}}, but I foresee this being very rarely needed in
+the author-date styles.  See table~\ref{ad:date:extras} for
+\textsf{biblatex-chicago's} implementation of \textsf{biblatex's}
+enhanced date specifications.)  As with the analogous \textsf{date}
+field, you provide the date (or range of dates) in \textsc{iso}8601
+format, i.e., \texttt{yyyy-mm-dd}.  In most entry types, you would use
\textsf{origdate} to provide the date of first publication of a work,
most usually needed only in the case of reprint editions, but also
recommended by the \emph{Manual} for electronic editions of older
-works (15.38, 14.119, 14.166, 14.169; aristotle:metaphy:gr,
-emerson:nature, james:ambassadors, schweitzer:bach).  In both the
-\textsf{letter} and \textsf{misc} (with \textsf{entrysubtype)} entry
-types, the \textsf{origdate} identifies when a letter (or similar) was
-written.  In such \textsf{misc} entries, some
-\enquote{non-letter-like} materials (like interviews) need the
-\textsf{date} field for this purpose, while in \textsf{letter} entries
-the \textsf{date} applies to the publication of the whole collection.
-If such a published collection were itself a reprint, judicious use of
-the \textsf{pubstate} field or perhaps improvisation in the
+works (15.40, 14.114, 14.162; aristotle:metaphy:gr, emerson:nature,
+james:ambassadors, schweitzer:bach).  In both the \textsf{letter} and
+\textsf{misc} (with \textsf{entrysubtype)} entry types, the
+\textsf{origdate} identifies when a letter (or similar) was written.
+In such \textsf{misc} entries, some \enquote{non-letter-like}
+materials (like interviews) need the \textsf{date} field for this
+purpose, while in \textsf{letter} entries the \textsf{date} applies to
+the publication of the whole collection.  If such a published
+collection were itself a reprint, judicious use of the
+\textsf{pubstate} field or perhaps improvisation in the
\textsf{location} field might be able to rescue the situation.  (See
white:ross:memo, white:russ, and white:total for how \textsf{letter}
entries can work; creel:house shows the field in action in a
@@ -8818,7 +11772,7 @@

\mylittlespace Because of the importance of date specifications in the
-author-date styles, \textsf{bibla\-tex-chicago-authordate} and
+author-date styles, \textsf{biblatex-chicago-authordate} and
\textsf{authordate-trad} provide options and automated behaviors that
allow you to emphasize the \textsf{origdate} in citations and at the
head of entries in the list of references.  In entries which have
@@ -8827,14 +11781,14 @@
\cmd{DeclareLabeldate} configuration make it possible to do without a
\texttt{cmsdate} option, as the \textsf{origdate} will automatically
appear where and as it should.  In \textsf{book}-like entries with
-both a \textsf{date} and an \textsf{origdate}, the 16th edition of the
-\emph{Manual} recommends that you present, in citations and at the
-head of reference list entries, only the \textsf{date} or both dates
-together.  The latter is accomplished using the \texttt{cmsdate} entry
-option.  In some cases it may even be necessary to reverse the two
-date fields, putting the earlier year in \textsf{date} and the later
-in \textsf{origdate}.  If your reference apparatus contains many such
-instances, it may well be convenient for you instead to use the
+both a \textsf{date} and an \textsf{origdate}, the \emph{Manual}
+recommends that you present, in citations and at the head of reference
+list entries, only the \textsf{date} or both dates together.  The
+latter is accomplished using the \texttt{cmsdate} entry option.  In
+some cases it may even be necessary to reverse the two date fields,
+putting the earlier year in \textsf{date} and the later in
+\textsf{origdate}.  If your reference apparatus contains many such
+instances, it may well be convenient for you instead to use the
\mymarginpar{\texttt{cmsdate}\\\emph{in preamble}} \texttt{cmsdate}
preamble option, which I have designed in an attempt to reduce the
amount of manual intervention needed to present lots of entries with
@@ -8842,7 +11796,7 @@
or \texttt{on} in the preamble promotes the \textsf{origdate} to the
top of the search for a \textsf{labeldate} to use in citations and at
the head of entries in the reference list.  This can solve many
-problems with the \textsf{extrayear} field --- 1978\textbf{a} --- and
+problems with the \textsf{extradate} field --- 1978\textbf{a} --- and
also with sorting in the reference list.  Please see above under
\textbf{date} for all the details on how these options interact.

@@ -8852,9 +11806,10 @@
If you set the \texttt{cmsdate} preamble options I've just mentioned,
this changes to \textsf{origdate, date, eventdate, urldate}.  These
generally cover the needs of the Chicago author-date styles well,
-except for \textsf{music} and \textsf{video} entries, and,
-exceptionally, some \textsf{review} entries.  Here the general rule is
-to emphasize the earliest date.  For these three entry types, then,
+except for \textsf{music}, \mycolor{\textsf{standard}}, and
+\textsf{video} entries, and, exceptionally, some \textsf{review} and
+\textsf{suppperiodical} entries.  Here the general rule is to
+emphasize the earliest date.  For these five entry types, then,
\cmd{DeclareLabeldate} uses the order \textsf{eventdate, origdate,
date, urldate}.  In \textsf{music} entries, you can use the
\textsf{origdate} in two separate but related ways.  First, it can
@@ -8875,19 +11830,26 @@
different string using the \textsf{userd} field, but please be aware
that if an entry also has an \textsf{eventdate}, then \textsf{userd}
will apply to that, instead, and you'll be forced to accept the
-default string.  (Compare friends:leia with hitchcock:nbynw; 15.53,
-14.279-280; cf.\ \texttt{cmsdate} in sections~\ref{sec:authuseropts}
+default string.  (Compare friends:leia with hitchcock:nbynw; 15.57,
+14.263--65; Cf.\ \texttt{cmsdate} in sections~\ref{sec:authuseropts}
and \ref{sec:authentryopts}, \cmd{DeclareLabeldate} in
section~\ref{sec:authformopts}, and \texttt{avdate} in
section~\ref{sec:authpreset}.)

-\mylittlespace Because the \textsf{origdate} field only accepts
-numbers, some improvisation may be needed if you wish to include
-\enquote{n.d.}\ (\cmd{bibstring\{nodate\}}) in an entry.  In
-\textsf{letter} and \textsf{misc}, this information can be placed in
-\textsf{titleaddon}, but in other entry types you may need to use the
-\textsf{location} field.  (The \textsf{origyear} field usually works,
-too.)
+\mylittlespace A couple of further notes are in order.  First,
+\textsf{artwork} and \textsf{image} entries (which see) have their own
+scheme, and are not governed by the \texttt{avdate} option.  Here, the
+style uses the earlier of two dates as the creation date of the work
+while the later is the printing date of, e.g., a particular exemplar
+of a photograph or of an etching.  Depending on how you want this
+information presented in an entry, you can distribute these dates
+between the \textsf{date} and \textsf{origdate} fields as you wish.
+Second, because the \textsf{origdate} field only accepts numbers, some
+improvisation may be needed if you wish to include \enquote{n.d.}\
+(\verb+\bibstring{nodate}+) in an entry.  In \textsf{letter} and
+\textsf{misc}, this information can be placed in \textsf{titleaddon},
+but in other entry types you may need to use the \textsf{location}
+field.  (The \textsf{origyear} field usually works, too.)

\mybigspace See
\vspace{-14.2pt}
@@ -8896,21 +11858,27 @@
section~\ref{sec:authrelated}, below.
\vspace{18pt}

+\mybigspace This \colmarginpar{\textbf{origtimezone}} field can, if
+necessary, specify the time zone associated with a time stamp given as
+part of an \textsf{origdate}.  The \emph{Manual} prefers initialisms
+like \enquote{EST} for this purpose, and you can provide parentheses
+around it at your discretion (cp.\ 10.41 and 14.191).
+
\mybigspace This \mymarginpar{\textbf{pages}} is the standard
\textsf{biblatex} field for providing page references.  In many
\textsf{article} entries you'll find this contains something other
than a page number, e.g. a section name or edition specification
-(14.203, 14.209; kozinn:review, nyt:trevorobit).  Of course, the same
-may be true of almost any sort of entry, though perhaps with less
-frequency.  Curious readers may wish to look at brown:bremer (14.189)
-for an example of a \textsf{pages} field used to facilitate reference
-to a two-part journal article.  Cf.\ \textsf{number} for more
-information on the \emph{Manual}'s preferences regarding the
-formatting of numerals; \textsf{bookpagination} and
-mechanisms for specifying what sort of division a given \textsf{pages}
-field contains; and \textsf{usera} discusses a different way to
-present the section information pertaining to a newspaper article.
+(14.191; kozinn:review, nyt:trevorobit).  Of course, the same may be
+true of almost any sort of entry, though perhaps with less frequency.
+Curious readers may wish to look at brown:bremer (14.180) for an
+example of a \textsf{pages} field used to facilitate reference to a
+on the \emph{Manual}'s preferences regarding the formatting of
+numerals; \textsf{bookpagination} and \textsf{pagination} provide
+details about \textsf{biblatex's} mechanisms for specifying what sort
+of division a given \textsf{pages} field contains; and \textsf{usera}
+discusses a different way to present the section information
+pertaining to a newspaper article.

\mylittlespace David Gohlke brought to my attention a discussion that
took place a couple of years ago on
@@ -8918,7 +11886,7 @@
regarding the automatic compression of page ranges, e.g., 101-{-}109
in the .bib file or in the \textsf{postnote} field would become 101--9
in the document.  \textsf{Biblatex} has long had the facilities for
-providing this, and though the \emph{Manual's} rules (9.60) are fairly
+providing this, and though the \emph{Manual's} rules (9.61) are fairly
complicated, Audrey Boruvka fortunately provided in that discussion
code that implements the specifications.  As some users may well be
accustomed to compressing page ranges themselves in their .bib files,
@@ -8925,7 +11893,10 @@
and in their \textsf{postnote} fields, I have made the activation of
this code a package option, so setting \texttt{compresspages=true}
-the Chicago-recommended page ranges.
+the Chicago-recommended page ranges.  \textbf{NB}: the code now
+resides in \textsf{biblatex-chicago.sty}, so if you don't load that
+package then you'll need to copy the code into your preamble for the
+option to have the desired effect.

\mybigspace This, \mymarginpar{\textbf{pagination}} a standard
\textsf{biblatex} field, allows you automatically to prefix the
@@ -8940,7 +11911,7 @@
field, which identifies physical parts of a single logical volume in
\textsf{book}-like entries, not in periodicals.  It has the same
purpose in \textsf{biblatex-chicago}, but because the \emph{Manual}
-(14.126) calls such a thing a \enquote{book} and not a \enquote{part,}
+(14.121) calls such a thing a \enquote{book} and not a \enquote{part,}
the string printed in the list of references will, at least in
English, be \enquote{\texttt{bk.}\hspace{-2pt}}\ instead of the plain
dot between volume number and part number (harley:cartography,
@@ -8958,43 +11929,84 @@
\textsf{number} [palmatary:pottery]).  Cf.\ \textsf{volume};
iso:electrodoc.

-\mybigspace Standard \mymarginpar{\textbf{publisher}}
+\mybigspace Standard \colmarginpar{\textbf{publisher}}
\textsf{biblatex} field.  Remember that \enquote{\texttt{and}} is a
keyword for connecting multiple publishers, so if a publisher's name
contains \enquote{and,} then you should either use the ampersand (\&)
or enclose the whole name in additional braces.  (See \emph{Manual}
-14.139--148; aristotle:metaphy:gr, cohen:schiff, creasey:ashe:blast,
+14.133--41; aristotle:metaphy:gr, cohen:schiff, creasey:ashe:blast,
dunn:revolutions.)

-\mylittlespace There are, as one might expect, a couple of further
-subtleties involved here.  Two publishers will be separated by a
-forward slash in the list of references, and you no longer, in the
-16th edition, need to provide hand formatting if a company issues
-\enquote{certain books through a special publishing division or under
-  a special imprint,} as these, too, should be separated by a forward
-slash.  If a book has two co-publishers, \enquote{usually in different
-  countries,} (14.147) then the simplest thing to do is to choose one,
-probably the nearest one geographically.  If you feel it necessary to
-include both, then levistrauss:savage demonstrates one way of doing
-so, using a combination of the \textsf{publisher} and
-\textsf{location} fields.  Finally, if the publisher is unknown, then
-the \emph{Manual} recommends (14.143) simply using the place (if
-known) and the date.  If for some reason you need to indicate the
-absence of a publisher, the abbreviation given by the \emph{Manual} is
-\texttt{n.p.}, though this can also stand for \enquote{no place.}
-Some style guides apparently suggest using \texttt{s.n.}\,(=
-\emph{sine nomine}) to specify the lack of a publisher, but the
-\emph{Manual} doesn't mention this.
+\mylittlespace There are, as one might expect, a few further
+subtleties involved here.  If you give two publishers in the field
+they will both be printed, separated by a forward slash in both notes
+and bibliography (14.90; sereny:cries).  The 17th edition generally is
+rather keener than the 16th on using just one, particularly so in the
+case when the parent company of an imprint is also listed on a title
+page, in which case only the imprint need be included in your
+apparatus (14.138).  If an academic publisher issues \enquote{certain
+  books through a special publishing division or under a special
+  imprint or as part of a publishing consortium (or joint imprint),}
+this arrangement may be specified in the \textsf{publisher} field
+(14.139; cohen:schiff).  If a book has two co-publishers \enquote{in
+  different countries} (14.140), then the simplest thing to do is to
+choose one, probably the nearest one geographically.  If you feel it
+necessary to include both, then levistrauss:savage demonstrates one
+way of doing so, using a combination of the \textsf{publisher} and
+\textsf{location} fields.  If the work is self-published, you can
+specify this in the \textsf{pubstate} field (see below), and any
+commercial self-publishing platform would go in \textsf{publisher}
+(14.137).  Books published before 1900 can, at your discretion,
+include only the place (if known) and the date (14.128).  If for some
+reason you need to indicate the absence of a publisher, the
+abbreviation given by the \emph{Manual} is \texttt{n.p.}, though this
+can also stand for \enquote{no place.}  The \emph{Manual} also
+mentions {s.n.}\,(= \emph{sine nomine}) to specify the lack of a
+publisher (10.42).

-\mybigspace In addition to the functions involving reprinted titles,
-on which see \colmarginpar{\textbf{pubstate}}
-section~\ref{sec:authrelated} below, you can now also use the
-\textsf{pubstate} field to indicate that a work is
-\enquote{forthcoming.}  Just put the exact string \texttt{forthcoming}
-into the field and the style will print
-\cmd{bibstring\{forth\-coming\}} as the \textsf{year}
-(author:forthcoming, contrib:contrib).
+\mybigspace In \colmarginpar{\textbf{pubstate}} response to new
+specifications in the 17th edition of the \emph{Manual} (esp.\
+14.137), I have tried to generalize the functioning of the
+\textsf{pubstate} field in all entry types.  Because the author-date
+style has fairly complicated rules about presenting reprinted editions
+(15.40), the \texttt{reprint} string still has a special status.
+Depending on which date(s) you have chosen to appear at the head of
+the entry, \textsf{biblatex-chicago-authordate} will either print the
+(localized) string \texttt{reprint} in the proper place or otherwise
+provide a notice at the end of the entry detailing the original
+publication date.  See under \textbf{date} above for the available
+permutations.  (Cf.\ aristotle:metaphy:gr, maitland:canon,
+maitland:equity, schweitzer:bach.)

+\mylittlespace Other strings are divided into two types: those which
+\textsf{biblatex-chicago} will print as the \textsf{year}, which
+currently means \emph{only} those for which \textsf{biblatex} contains
+bibstrings indicating works soon to be published, i.e.,
+\texttt{forthcoming}, \texttt{inpreparation}, \texttt{inpress}, and
+\texttt{submitted}; and those, i.e., everything else, which will be
+printed before, and in close association with, other information about
+the publisher of a work.  (This \colmarginpar{\textbf{NB}} is a change
+from previous behavior, where non-\texttt{reprint} strings were
+printed \emph{after} the publication information, as in the standard
+styles.  You can still use the \textsf{addendum} field to present
+information here, of course.)  The four strings that replace the
+\textsf{year} will always be localized, as will \texttt{reprint} and
+\mycolor{\texttt{selfpublished}} (and anything else that
+\textsf{biblatex} finds to be a \cmd{bibstring}) from the second
+category.  All other strings will be printed as-is, capitalized if
+needed, just before the publisher (author:forthcoming,
+contrib:contrib, schweitzer:bach).
+
+\mylittlespace There is one further subtlety of which you ought to be
+aware.  In \textsf{music} and \textsf{video} entries, the
+\texttt{reprint} string in \textsf{pubstate} will only make a
+difference to your entries when the date which it modifies --- the
+\textsf{origdate}, typically --- \emph{doesn't} appear in citations
+and at the head of reference-list entries.  In this case the date is
+treated as an original release date, and it will be printed, preceded
+by the appropriate string, near the end of the entry.  Other strings
+don't show this special behavior in these entries.
+
\mybigspace I \mymarginpar{\textbf{redactor}} have implemented this
field just as \textsf{biblatex}'s standard styles do, even though the
\emph{Manual} doesn't actually mention it.  It may be useful for some
@@ -9003,11 +12015,15 @@
\mybigspace See \mymarginpar{\textbf{reprinttitle}}
section~\ref{sec:authrelated}, below.

+\enlargethispage{\baselineskip}
+
\mybigspace A \mymarginpar{\textbf{series}} standard \textsf{biblatex}
field, usually just a number in an \textsf{article},
\textsf{periodical}, or \textsf{review} entry, almost always the name
-of a publication series in \textsf{book}-like entries.  If you need to
-attach further information to the \textsf{series} name in a
+of a publication series in \textsf{book}-like entries, and providing
+similar identifying information associated with a \textsf{number} in
+\textsf{music} and \mycolor{\textsf{standard}} entries.  If you need
+to attach further information to the \textsf{series} name in a
\textsf{book}-like entry, then the \textsf{number} field is the place
for it, whether it be a volume, a number, or even something like
\enquote{2nd ser.} or \enquote{\cmd{bibstring\{oldseries\}}.}  Of
@@ -9017,14 +12033,14 @@
\textsf{series} field in \textsf{article} and \textsf{periodical}
entries is one of the places where \textsf{biblatex} allows you just
to use the plain bibstring \texttt{oldseries}, for example, rather
-than making you type \cmd{bibstring\{oldseries\}}.  The \textsf{type}
+than making you type \verb+\bibstring{oldseries}+.  The \textsf{type}
field in \textsf{manual}, \textsf{patent}, \textsf{report}, and
\textsf{thesis} entries also has this auto-detection mechanism in
place; see the discussion of \cmd{bibstring} below for details.)  In
whatever entry type, these bibstrings produce the required
abbreviation.  (For books and similar entries, see \emph{Manual}
-14.128--132; boxer:china, browning:aurora, palmatary:pottery,
-plato:republic:gr, wauchope:ceramics; for periodicals, see 14.195;
+14.123--26; boxer:china, browning:aurora, palmatary:pottery,
+plato:republic:gr, wauchope:ceramics; for periodicals, see 14.184;
garaud:gatine, sewall:letter.)  Cf.\ \textsf{number} for more
information on the \emph{Manual}'s preferences regarding the
formatting of numerals.
@@ -9031,7 +12047,7 @@

\mybigspace This \mymarginpar{\textbf{shortauthor}} is a standard
\textsf{biblatex} field, but \textsf{biblatex-chicago} makes
-considerably grea\-ter use of it than the standard styles.  For the
+considerably greater use of it than the standard styles.  For the
purposes of the author-date specification, the field provides the name
to be used in text citations.  In the vast majority of cases, you
don't need to specify it, because the \textsf{biblatex} system selects
@@ -9055,7 +12071,7 @@
\textbf{shorthand} for another method of saving space.

\mylittlespace As mentioned under \textsf{editortype}, the
-\emph{Manual} (15.21) recommends against providing the identifying
+\emph{Manual} (15.36) recommends against providing the identifying
string (e.g., ed.\ or trans.)\ in text citations, and
\textsf{biblatex-chicago} follows their recommendation.  If you need
to provide these strings in such a citation, then you'll have to do so
@@ -9077,7 +12093,6 @@
shortened \textsf{namea} here instead of a shortened \textsf{editor}
in such cases.Cf.\ \textsf{editortype}, above.

-% %\enlargethispage{\baselineskip}
\paragraph*{\protect\mymarginpar{\textbf{shorthand}}}

@@ -9106,26 +12121,26 @@
conventions of your field or, alternately, provide a list of journal
abbreviations using \cmd{printbiblist\{shortjournal\}}.

-\enlargethispage{\baselineskip}
+\enlargethispage{-\baselineskip}

\mylittlespace For long institutional names the \emph{Manual's}
-recommendation (15.36), and this has changed for the 16th edition,
-involves using an abbreviation, an abbreviation which will appear not
-only in citations but also at the head of the entry in the list of
-references.  Such an entry should therefore be alphabetized by the
-abbreviation, with its expansion placed (inside parentheses) between
-the abbreviation and the date.  This formatting can be produced in one
-of two ways: either you can provide a specially-formatted
-\textsf{author} field (for the reference list, and including both the
-abbreviation and the parenthesized expansion) + a \textsf{shortauthor}
-(for the citations), or you can use a normal \textsf{author} field + a
-\textsf{shorthand}, in which case \textsf{biblatex-chicago-authordate}
-will automatically use the \textsf{shorthand} in text citations and
-also place it at the head of the reference list entry, followed by the
-\textsf{author} within parentheses.  This method is simpler and more
-compatible with other styles, though you do need a \textsf{sortkey}
-when you use the \textsf{shorthand} field this way.  (Cf.\
-bsi:abbreviation, iso:electrodoc.)
+recommendation (15.37) involves using an abbreviation which will
+appear not only in citations but also at the head of the entry in the
+list of references.  Such an entry should therefore be alphabetized by
+the abbreviation, with its expansion placed (inside parentheses)
+between the abbreviation and the date.  This formatting can be
+produced in one of two ways: either you can provide a
+specially-formatted \textsf{author} field (for the reference list, and
+including both the abbreviation and the parenthesized expansion) + a
+\textsf{shortauthor} (for the citations), or you can use a normal
+\textsf{author} field + a \textsf{shorthand}, in which case
+\textsf{biblatex-chicago-authordate} will automatically use the
+\textsf{shorthand} in text citations and also place it at the head of
+the reference list entry, followed by the \textsf{author} within
+parentheses.  This method is simpler and more compatible with other
+styles, and will also produce a list that is correctly sorted by the
+\textsf{shorthand}.  (Cf.\ niso:bibref, bsi:abbreviation,
+iso:electrodoc.)

\mylittlespace I should clarify here that this automatic placement of
the \textsf{shorthand} at the head of the entry will \emph{not} occur
@@ -9140,7 +12155,7 @@

\mylittlespace Indeed, I have provided two options to add to this
flexibility.  First, I have included two \texttt{bibenvironments} for
-use with the \texttt{env} option to the \cmd{printshort\-hands} command:
+use with the \texttt{env} option to the \cmd{printshorthands} command:
\texttt{losnotes} is designed to allow a list of shorthands to appear
inside footnotes, while \texttt{losendnotes} does the same for
endnotes.  Their main effect is to change the font size, and in the
@@ -9149,16 +12164,14 @@
use the option \texttt{heading=none} in order to get rid of the
[oversized] default, providing your own within the \cmd{footnote}
command.)  Second, I have provided a package option,
-\texttt{short\-handfull}, which prints entries in the list of
-shorthands which contain full bibliographical information, effectively
-allowing you to eschew the list of references in favor of a fortified
-shorthand list.  This option will only work if used in tandem with
+\texttt{shorthandfull}, which prints entries in the list of shorthands
+which contain full bibliographical information, effectively allowing
+you to eschew the list of references in favor of a fortified shorthand
+list.  This option will only work if used in tandem with
\texttt{cmslos=false}, as otherwise the shorthand will be printed
-twice.  (See 15.36, 13.65, 14.54--55, and also \textsf{biblatex.pdf}
+twice.  (See 15.37, 13.67, 14.59--60, and also \textsf{biblatex.pdf}

-%%\enlargethispage{-\baselineskip}
-
\mylittlespace As I mentioned above under \textbf{crossref}, I believe
it is safe to use shorthands in parent entries, as this, in the
standard configuration, gives you the shorthand itself in the child
@@ -9173,7 +12186,7 @@
requested by user BenVB, you can now utilize this functionality in
your documents, but there are a few details worth mentioning here.
First, users in some fields may well already be accustomed to using a
-set of standard journal abbreviations (15.44), in which case the
+set of standard journal abbreviations (15.46), in which case the
\textsf{journaltitle} field may well already contain the abbreviation,
which will appear wherever that field is printed.  In such cases, it
usually isn't necessary to provide a list of abbreviations in
@@ -9199,7 +12212,7 @@
reference list, \texttt{bib} prints them only in the reference list,
and \texttt{false} ignores them.  Should you wish to present a list of
these abbreviations with their expansions, then you need to use the
-\cmd{printbiblist\{shortjournal\}} command, perhaps with a
+\verb+\printbiblist{shortjournal}+ command, perhaps with a
\texttt{title} option to differentiate the list from any
\textsf{shorthand} list.  As with \textsf{shorthand} lists, I have
provided two \texttt{bibenvironments} for printing this list in foot-
@@ -9210,12 +12223,48 @@
the (oversized) default, and perhaps provide your own title within the
\cmd{footnote} command.  Finally, if you don't like the default
formatting of the abbreviations in the list (bold italic), you can
-roll your own using \cmd{DeclareFieldFormat\{shortjournalwidth\}} ---
+change it with \verb+\DeclareFieldFormat{shortjournal-width}+ --- you
+can see its default definition at the top of
+\textsf{chicago-authordate.bbx}.
+
+\mybigspace A \colmarginpar{\textbf{shortseries}} special
+\textsf{biblatex} field, used both to provide an abbreviated form of a
+(book) \textsf{series} in a reference list and to facilitate the
+creation of a list of such abbreviations rather in the manner of a
+\textsf{shorthand} list.  As with the \textsf{shortjournal} field, its
+inclusion in \textsf{biblatex-chicago} was requested by user BenVB,
+and it is now available in entry types which have book-like series
+titles rather than journal-like numbers in the \textsf{series} field,
+to wit: \textsf{audio, book, bookinbook, collection, inbook,
+  incollection, inproceedings, inreference, letter, manual, music,
+  mvbook, mvcollection, mvproceedings, mvreference, reference, report,
+  standard, suppbook,} and \textsf{video}.  There are several steps to
+take in order to use the field.  First, you'll need to provide both
+\textsf{shortseries} and \textsf{series} fields in the entry, then
+you'll need to set the \mycolor{\texttt{seriesabbrev}} option either
+specific entry types, or in the \textsf{options} field of individual
+.bib entries.  By default, this option is not set, so your
+\mycolor{\textsf{shortseries}} fields will be silently ignored.
+Setting it to \texttt{true} prints the shortened fields in the
+reference list.  Should you wish to present a list of these
+abbreviations with their expansions, then you need to use the
+\verb+\printbiblist{shortseries}+ command, perhaps with a
+\texttt{title} option to differentiate the list from any
+\textsf{shorthand} list.  As with \textsf{shorthand} lists, I have
+provided two \texttt{bibenvironments} for printing this list in foot-
+or endnotes (\mycolor{\texttt{shsernotes}} and
+\mycolor{\texttt{shserendnotes}}, respectively), to be used with the
+\texttt{env} option to \cmd{printbiblist}.  Again as with
+\textsf{shorthands}, you'll probably want to use the option
+\texttt{heading=none} when using these environments, just to turn off
+the (oversized) default, and perhaps provide your own title within the
+\cmd{footnote} command.  Finally, if you don't like the default
+formatting of the abbreviations in the list (plain roman), you can
+roll your own using \verb+\DeclareFieldFormat{shortserieswidth}+ ---
you can see its default definition at the top of
\textsf{chicago-authordate.bbx}.

-\enlargethispage{\baselineskip}
-
\mybigspace A \mymarginpar{\textbf{shorttitle}} standard
\textsf{biblatex} field, primarily used to provide an abbreviated
title for citation styles that need one.  (It is also the way to hook
@@ -9225,87 +12274,83 @@
only very rarely (unlike in the notes \&\ bibliography style), and is
most likely to turn up in \textsf{inreference} or \textsf{reference}
entries (where the \textsf{title} takes the place of the
-\textsf{author}), or in any sort of entry with a \texttt{classical}
-\textsf{entrysubtype}.  This latter toggle makes citations use
-\textsf{author} and \textsf{title} instead of \textsf{author} and
-\textsf{year}, and if an abbreviated version of that title would save
-space in your running text this is the field where you can provide it.
-(Cf.\ ency:britannica, grove:sibelius, aristotle:metaphy:gr.)
+\textsf{author}), in \mycolor{\textsf{dataset}} entries, or in any
+sort of entry with a \texttt{classical} \textsf{entrysubtype} or with
+\mycolor{\texttt{authortitle}} set in its \textsf{options} field.
+These latter three contexts make citations use \textsf{author} and
+\textsf{title} instead of \textsf{author} and \textsf{year}, and if an
+abbreviated version of that title would save space in your running
+text this is the field where you can provide it.  (Cf.\
+ency:britannica, grove:sibelius, aristotle:metaphy:gr.)

-\mybigspace A \mymarginpar{\textbf{sortkey}} standard
-\textsf{biblatex} field, designed to allow you to specify how you want
-an entry alphabetized in a list of references.  In general, if an
-entry doesn't turn up where you expect or want it, this field should
-provide the solution.  Entries with a corporate author can omit the
-definite or indefinite article, which should help (14.85;
-cotton:manufacture, nytrumpet:art).  The default settings of
-\cmd{DeclareSortingTemplate} include the three supplemental name
-fields (\textsf{name[a-c]}) and also the \textsf{journaltitle} in the
-sorting algorithm, so once again you should find those algorithms
-needing less help than before.  Entries using a \textsf{shorthand},
-and entries headed by a \textsf{title} beginning with the definite or
-indefinite article, may well now require such assistance
-(bsi:abbreviation, grove:sibelius, iso:electrodoc).  There may be
-circumstances --- several reprinted books by the same author, for
-example --- when the \textbf{sortyear} field is more appropriate, on
-which see below.  \textsf{Biblatex} also provides \textbf{sortname}
-and \textbf{sorttitle} for equally fine-grained control.  Please
-consult \textsf{biblatex.pdf} for the details.
+\mybigspace Standard \mymarginpar{\textbf{sortkey} \\\textbf{sortname}
+  \\\textbf{sorttitle} \\\textbf{sortyear}} \textsf{biblatex} fields,
+designed to allow you to specify how you want an entry alphabetized in
+a list of references.  The \textsf{sortkey} field trumps all other
+sorting information, while the others offer more fine-grained control.
+In general, if an entry doesn't turn up where you expect or want it,
+one of these fields should provide the solution.  Entries with a
+corporate author can omit the definite or indefinite article, which
+should help (14.70, 14.84; cotton:manufacture, nytrumpet:art).  The
+default settings of \cmd{DeclareSortingTemplate} include the three
+supplemental name fields (\textsf{name[a-c]}) and also the
+\textsf{journaltitle} in the sorting algorithm, so once again you
+should find those algorithms needing less help than before.  Entries
+headed by a \textsf{title} beginning with the definite or indefinite
+article may well still require such assistance (grove:sibelius).
+There may be circumstances --- several reprinted books by the same
+author, for example --- when the \textsf{sortyear} field is the best
+choice.  Please consult \textsf{biblatex.pdf} for the details.

-\mybigspace A \mymarginpar{\textbf{sortyear}} standard
-\textsf{biblatex} field, provided for more fine-grained control over
-the sorting of entries in a list of references, and possibly useful in
-\textsf{biblatex-chicago-authordate} to help present several reprinted
-books by the same author.  See \textsf{sortkey} and \textsf{date}
-above.
-
\mybigspace The \mymarginpar{\textbf{subtitle}} subtitle for a
\textsf{title} --- see next entry.

-\mybigspace This \mymarginpar{\textbf{title}} release of
-designed as a kind of hybrid style according to indications contained
-in the 16th edition of the \emph{Manual} (14.45).  This \textsf{trad}
-style differs \emph{only} in the way it treats the \textsf{title} and
-the Chicago author-date specifications prior to the latest edition.
-Where the new edition uses headline-style capitalization, the older
-editions used sentence-style; where the new edition places
-\textsf{article} or \textsf{incollection} \textsf{titles} within
-quotation marks, the older editions presented them in plain text.  If
-you have been using the 15th-edition author-date style, then your
-\textsf{title} fields won't need any changes for
-\textsf{authordate-trad}, but I shall include just below, under a
-separate rubric, full documentation for \textsf{trad} \textsf{title}
-fields for those just coming to the package.  First, though, I
-document the same field(s) for the standard author-date style.
+\mybigspace This \colmarginpar{\textbf{timezone}} field can, if
+necessary, specify the time zone associated with a time stamp given as
+part of an \textsf{date}.  The \emph{Manual} prefers initialisms like
+\enquote{EST} for this purpose, and you can provide parentheses around
+it at your discretion (cp.\ 10.41 and 14.191).

+\mybigspace \textsf{Biblatex-chicago} \mymarginpar{\textbf{title}}
+includes the \textsf{authordate-trad} style, designed as a kind of
+hybrid style according to indications contained in the \emph{Manual}
+(15.38).  This \textsf{trad} style differs \emph{only} in the way it
+treats the \textsf{title} and related fields, which retain the forms
+capitalization, the older editions used sentence-style; where newer
+editions place \textsf{article} or \textsf{incollection}
+\textsf{titles} within quotation marks, the older editions presented
+them in plain text.  I include below, under a separate rubric, full
+documentation of \textsf{trad} \textsf{title} fields for those needing
+or wishing to use them.  First, though, I document the same field(s)
+for the standard author-date style.
+
\mylittlespace In the vast majority of cases, this field works just as
it always has in \textsc{Bib}\TeX, and just as it does in
-\textsf{biblatex}.  In a major change to previous editions of the
-\emph{Manual}, the 16th edition now recommends that \textsf{titles} be
-treated more or less identically across both its systems of
-documentation (15.2, 15.6, 15.13).  This means that users of the
-author-date style no longer need to worry about sentence-style
+\textsf{biblatex}.  The \emph{Manual} recommends that \textsf{titles}
+be treated more or less identically across both its systems of
+documentation (15.3, 15.6, 15.13).  This means that users of the
+author-date style don't need to worry about sentence-style
capitalization when compiling their .bib databases, and so can eschew
the extra curly braces needed to preserve uppercase letters in this
-context.  The other new rules, however, mean that a few new
-complications, familiar to users of the notes \&\ bibliography style,
-will arise.  First, although nearly every entry will have a
-\textsf{title}, there are some exceptions, particularly
-\textsf{incollection} or \textsf{online} entries with a merely generic
-title, instead of a specific one (centinel:letters, powell:email).
-Second, the \emph{Manual}'s rules for formatting \textsf{titles},
-which also hold for \textsf{booktitles} and \textsf{maintitles},
-require additional attention.  The whole point of using a
-\textsc{Bib}\TeX-based system is for it to do the formatting for you,
-and in most cases \textsf{biblatex-chicago-authordate} does just that,
-surrounding titles with quotation marks, italicizing them, or
-occasionally just leaving them alone.  When, however, a title is
-quoted within a title, then you need to know some of the rules.  A
-summary here should serve to clarify them, and help you to understand
-when \textsf{biblatex-chicago-authordate} might need your help in
-order to comply with them.
+context.  These rules, however, mean that a few complications familiar
+to users of the notes \&\ bibliography style do arise.  First,
+although nearly every entry will have a \textsf{title}, there are some
+exceptions, particularly \textsf{incollection} or \textsf{online}
+entries with a merely generic title, instead of a specific one
+(centinel:letters, powell:email).  Second, the \emph{Manual}'s rules
+for formatting \textsf{titles}, which also hold for
+attention.  The whole point of using a \textsf{biblatex}-based system
+is for it to do the formatting for you, and in most cases
+\textsf{biblatex-chicago-authordate} does just that, surrounding
+titles with quotation marks, italicizing them, or occasionally just
+leaving them alone.  When, however, a title is quoted within a title,
+then you need to know some of the rules.  A summary here should serve
+\textsf{biblatex-chicago-authordate} might need your help in order to
+comply with them.

\mylittlespace The internal rules of
\textsf{biblatex-chicago-authordate} are as follows:
@@ -9315,15 +12360,16 @@
\textsf{journaltitle} in all entry types; \textsf{title} of
\textsf{artwork}, \textsf{book}, \textsf{bookinbook},
\textsf{booklet}, \textsf{collection}, \textsf{image},
-  \textsf{inbook}, \textsf{manual}, \textsf{misc} (with no
-  \textsf{entrysubtype}), \textsf{periodical}, \textsf{proceedings},
-  \textsf{report}, \textsf{suppbook}, and \textsf{suppcollection}
-  entry types.
+  \textsf{manual}, \textsf{misc} (with no \textsf{entrysubtype}),
+  \mycolor{\textsf{performance}}, \textsf{periodical},
+  \textsf{proceedings}, \textsf{report}, \mycolor{\textsf{standard}},
+  \textsf{suppbook}, and \textsf{suppcollection} entry types.
\item[\qquad Quotation Marks:] \textsf{title} of \textsf{article},
-  \textsf{incollection}, \textsf{inproceedings}, \textsf{online},
-  \textsf{periodical}, \textsf{thesis}, and \textsf{unpublished} entry
-  types, \textsf{issuetitle} in \textsf{article}, \textsf{periodical},
-  and \textsf{review} entry types.
+  \textsf{inbook} \textsf{incollection}, \textsf{inproceedings},
+  \textsf{online}, \textsf{periodical}, \textsf{thesis}, and
+  \textsf{unpublished} entry types, \textsf{issuetitle} in
+  \textsf{article}, \textsf{periodical}, and \textsf{review} entry
+  types.
\textsf{title} of \textsf{customc}, \textsf{letter}, \textsf{misc}
@@ -9335,7 +12381,7 @@
\textsf{inbook}.  Therefore, if there is both a \textsf{title} and a
\textsf{booktitle}, then the \textsf{title} will be in quotation
marks.  If there is no \textsf{booktitle}, then the \textsf{title}
-  will be italicized.
+  will be italicized, unless you provide an \textsf{entrysubtype}.
\end{description}

Now, the rules for which entry type to use for which sort of work tend
@@ -9342,7 +12388,7 @@
to be fairly straightforward, but in cases of doubt you can consult
section~\ref{sec:types:authdate} above, the examples in
\textsf{dates-test.bib}, or go to the \emph{Manual} itself,
-8.154--195.  Assuming, then, that you want to present a title within a
+8.156--201.  Assuming, then, that you want to present a title within a
title, and you know what sort of formatting each of the two would, on
its own, require, then the following rules apply:

@@ -9351,7 +12397,7 @@
quotation marks and italicized, so in such cases all you need to do
is provide the quotation marks using \cmd{mkbibquote}, which will
take care of any following punctuation that needs to be brought
-  within the closing quotation mark(s) (14.102; donne:var,
+  within the closing quotation mark(s) (14.94; donne:var,
mchugh:wake).
\item Inside a quoted title, you should present another title as it
would appear if it were on its own, so in such cases you'll need to
@@ -9359,8 +12405,8 @@
another quoted title would take single quotes --- the
\cmd{mkbibquote} command does this for you automatically, and also,
I repeat, takes care of any following punctuation that needs to be
-  brought within the closing quotation mark(s).  (See 14.177; garrett,
-  loften:hamlet, murphy:silent, white:calli\-machus.)
+  brought within the closing quotation mark(s).  (See 14.94--95;
+  garrett, loften:hamlet, murphy:silent, white:cal\-limachus.)
\item Inside a plain title (most likely in a \textsf{review} entry or
a \textsf{titleaddon} field), you should present another title as it
would appear on its own, once again formatting it yourself using
@@ -9372,11 +12418,13 @@
italicized in text should also be italicized in a quoted or plain-text
title, but should be in roman (\enquote{reverse italics}) in an
italicized title.  A quotation used as a (whole) title (with or
-without a subtitle) retains its quotation marks in an italicized title
-\enquote{only if it appears that way in the source,} but always
-retains them when the surrounding title is quoted or plain (14.104,
-14.177; lewis).  A word or phrase in quotation marks, but that isn't a
-quotation, retains those marks in all title types (kimluu:diethyl).
+without a subtitle) retains, according to the 16th edition, its
+quotation marks in an italicized title if it appears that way in the
+source, but I can't find similar instructions in the 17th.  Such a
+quotation always retains its quotation marks when the surrounding
+title is quoted or plain (14.94; lewis).  A word or phrase in
+quotation marks, but that isn't a quotation, retains those marks in
+all title types (kimluu:diethyl).

\mylittlespace Finally, please note that in all \textsf{review} (and
\textsf{suppperiodical}) entries, and in \textsf{misc} entries with an
@@ -9387,22 +12435,20 @@
your .bib database.  See\,\textbf{\textbackslash autocap} in
section~\ref{sec:formatting:authdate} below for more details.

-% %\enlargethispage{\baselineskip}
-
\mybigspace When \mymarginpar{\textbf{title (trad)}} you choose the
will need extra care, familiar to users of the 15th-edition
-author-date style.  The whole point of using a \textsc{Bib}\TeX-based
+author-date style.  The whole point of using a \textsf{biblatex}-based
system is for it to do the formatting for you, and in most cases
-them sentence-style, italicizing them, and sometimes both.  There are
-two situations that require user intervention.  First, in titles that
-take sentence-style capitalization, you need, as always in traditional
-\textsc{Bib}\TeX, to assist the algorithms by placing anything that
-needs to remain capitalized within an extra pair of curly braces.
-Second, when a title is quoted within a title, you need to know some
-of the rules of the Chicago style.  A summary here should serve to
+titles sentence-style, italicizing them, and sometimes both.  There
+are two situations that require user intervention.  First, in titles
+that take sentence-style capitalization, you need, as always in
+traditional \textsc{Bib}\TeX, to assist the algorithms by placing
+anything that needs to remain capitalized within an extra pair of
+curly braces.  Second, when a title is quoted within a title, you need
+to know some of the rules of the Chicago style.  A summary here should
order to comply with them.

@@ -9415,15 +12461,17 @@
\textsf{articles}), and \textsf{title} in \textsf{periodical}
entries.
\item[\qquad Sentence Style:] every other \textsf{title},
-  \emph{except} in \textsf{letter} entries, \textsf{review} entries,
-  and in \textsf{misc} entries with an \textsf{entrysubtype}.  Also,
-  the \textsf{booktitle}, \textsf{issuetitle}, and \textsf{maintitle}
-  in all entry types use sentence style.
+  \emph{except} in \textsf{letter} entries, \textsf{review} and
+  \textsf{suppperiodical} entries, and in \textsf{misc} entries with
+  an \textsf{entrysubtype}.  Also, the \textsf{booktitle},
+  \textsf{issuetitle}, and \textsf{maintitle} in all entry types use
+  sentence style.
\item[\qquad Contextual Capitalization of First Word:]
\textsf{maintitle\-addon} in all entry types, also the
-  \textsf{title} of \textsf{review} entries and of \textsf{misc}
-  entries with an \textsf{entrysubtype}.
+  \textsf{title} of \textsf{review} entries, of
+  \textsf{suppperiodical} entries, and of \textsf{misc} entries with
+  an \textsf{entrysubtype}.
\item[\qquad Plain:] \textsf{title} in \textsf{letter} entries.
\end{description}

@@ -9464,19 +12512,20 @@
\textsf{journaltitle} in all entry types; \textsf{title} of
\textsf{artwork}, \textsf{book}, \textsf{bookinbook},
-  \textsf{booklet}, \textsf{collection}, \textsf{inbook},
-  \textsf{manual}, \textsf{misc} (with no \textsf{entrysubtype}),
-  \textsf{periodical}, \textsf{proceedings}, \textsf{report},
-  \textsf{suppbook}, and \textsf{suppcollection} entry types.
+  \textsf{booklet}, \textsf{collection}, \textsf{manual},
+  \textsf{misc} (w/o \textsf{entrysubtype}),
+  \mycolor{\textsf{performance}}, \textsf{periodical},
+  \textsf{proceedings}, \textsf{report}, \mycolor{\textsf{standard}},
+  \textsf{suppbook}, and \textsf{suppcollection} types.
\item[\qquad Main Text Font (Roman):] \textsf{title} of
-  \textsf{article}, \textsf{image}, \textsf{incollection},
-  \textsf{inproceedings}, \textsf{letter}, \textsf{misc} (with an
-  \textsf{entrysubtype}), \textsf{online}, \textsf{patent},
-  \textsf{periodical}, \textsf{review}, \textsf{suppperiodical},
-  \textsf{thesis}, and \textsf{unpublished} entry types,
-  \textsf{issuetitle} in \textsf{article} and \textsf{periodical}
-  \textsf{titleaddon} in all entry types.
+  \textsf{article}, \textsf{image}, \textsf{inbook},
+  \textsf{incollection}, \textsf{inproceedings}, \textsf{letter},
+  \textsf{misc} (with an \textsf{entrysubtype}), \textsf{online},
+  \textsf{patent}, \textsf{periodical}, \textsf{review},
+  \textsf{suppperiodical}, \textsf{thesis}, and \textsf{unpublished}
+  entry types, \textsf{issuetitle} in \textsf{article} and
\item[\qquad Italics or Roman:] All of the audiovisual entry types ---
\textsf{audio}, \textsf{music}, and \textsf{video} --- have to serve
as analogues both to \textsf{book} and to \textsf{inbook}.
@@ -9483,7 +12532,7 @@
Therefore, if there is both a \textsf{title} and a
\textsf{booktitle}, then the \textsf{title} will be in the main text
font.  If there is no \textsf{booktitle}, then the \textsf{title}
-  will be italicized.
+  will be italicized, unless you provide an \textsf{entrysubtype}.
\end{description}

Now, the rules for which entry type to use for which sort of work tend
@@ -9490,7 +12539,7 @@
to be fairly straightforward, but in cases of doubt you can consult
section~\ref{sec:types:authdate} above, the examples in
\textsf{dates-test.bib}, or go to the \emph{Manual} itself,
-8.154--195.  Assuming, then, that you want to present a title within a
+8.156--201.  Assuming, then, that you want to present a title within a
title, and you know what sort of formatting each of the two would, on
its own, require, then the following rules apply:

@@ -9499,7 +12548,7 @@
quotation marks and italicized, so in such cases all you need to do
is provide the quotation marks using \cmd{mkbibquote}, which will
take care of any following punctuation that needs to be brought
-  within the closing quotation mark(s) (14.102; donne:var,
+  within the closing quotation mark(s) (14.94; donne:var,
mchugh:wake).
\item Inside a plain-text title, you should set off other plain-text
titles with quotation marks, while italicized titles should appear
@@ -9506,7 +12555,7 @@
as they would if they were on their own.  In such cases you'll need
to do the formatting yourself, using \cmd{mkbibemph} or
\cmd{mkbibquote}.  (See barcott:review, garrett, gibbard,
-  loften:hamlet, loomis:structure, murphy:silent, osborne:poi\-son,
+  loften:hamlet, loomis:structure, murphy:silent, osborne:poison,
ratliff:review, unsigned:ranke, white:callimachus.)
\end{enumerate}

@@ -9514,10 +12563,12 @@
italicized in text should also be italicized in a plain-text title,
but should be in roman (\enquote{reverse italics}) in an italicized
title.  A quotation used as a (whole) title (with or without a
-subtitle) retains its quotation marks when it is plain, but loses them
-when it is italicized, unless it specifically retains them in the
-source (14.104, 14.177; lewis).  A word or phrase in quotation marks,
-but that isn't a quotation, retains those marks in all title types
+subtitle) retains, according to the 16th edition, its quotation marks
+in an italicized title if it appears that way in the source, but I
+can't find similar instructions in the 17th.  Such a quotation always
+retains its quotation marks when the surrounding title is quoted or
+plain (14.94; lewis).  A word or phrase in quotation marks, but that
+isn't a quotation, retains those marks in all title types
(kimluu:diethyl).

\mylittlespace Finally, please note that there is also a preamble
@@ -9537,7 +12588,7 @@
and \textsf{biblatex-chicago} uses it in just this way, with the
additional wrinkle that it can, if needed, replace the \textsf{title}
entirely, and this in, effectively, any entry type, providing a fairly
-powerful, if somewhat complicated, tool for getting \textsc{Bib}\TeX\
+powerful, if somewhat complicated, tool for getting \textsf{biblatex}
to do what you want (cf.\ centinel:letters).  This field will always
be unformatted, that is, neither italicized nor placed within
quotation marks, so any formatting you may need within it you'll need
@@ -9559,8 +12610,6 @@
coolidge:speech shows an entry option for controlling the
punctuation.)

-%\enlargethispage{\baselineskip}
-
\mybigspace As \mymarginpar{\textbf{translator}} far as possible, I
have implemented this field as \textsf{biblatex}'s standard styles do,
but the requirements specified by the \emph{Manual} present certain
@@ -9611,20 +12660,22 @@
\textsf{options} field.  Cf.\ \textsf{author}, \textsf{editor},
\textsf{namea}, \textsf{nameb}, and \textsf{namec}.

-%%\enlargethispage{\baselineskip}
-
-\mybigspace This \mymarginpar{\textbf{type}} is a standard
+\mybigspace This \colmarginpar{\textbf{type}} is a standard
\textsf{biblatex} field, and in its normal usage serves to identify
the type of a \textsf{manual}, \textsf{patent}, \textsf{report}, or
\textsf{thesis} entry.  \textsf{Biblatex} implements the possibility,
in some circumstances, to use a bibstring without inserting it in a
-\cmd{bibstring} command, and in these entry types the \textsf{type}
-field works this way, allowing you simply to input, e.g.,
-\texttt{patentus} rather than \cmd{bibstring\{patentus\}}, though both
-will work.  (See petroff:impurity; herwign:office, murphy:silent, and
-ross:thesis all demonstrate how the \textsf{type} field may sometimes
-be automatically set in such entries by using one of the standard
-entry-type aliases).
+\cmd{bibstring} command, and in some entry types (\textsf{audio,
+  manual, music, patent, report, suppbook, suppcollection, thesis,}
+and \textsf{video}) the \textsf{type} field works this way, allowing
+you simply to input, e.g., \texttt{patentus} rather than
+\verb+\bibstring{patentus}+, though both will work.  (See
+petroff:impurity; herwign:office, murphy:silent, and ross:thesis all
+demonstrate how the \textsf{type} field may sometimes be automatically
+set in such entries by using one of the standard entry-type aliases).
+In other entry types (\textsf{artwork, image, book, online, article,
+  review,} and \textsf{suppperiodical}) \textsf{biblatex-chicago} will
+merely capitalize the contents according to context.

\mylittlespace Another use for the field is to generalize the
functioning of the \textsf{suppbook} entry type, and of its alias
@@ -9632,67 +12683,109 @@
specify what sort of supplemental material you are citing, e.g.,
\enquote{\texttt{preface to}} or \enquote{\texttt{postscript to}.}
Cf.\ \textsf{suppbook} above for the details.  (See \emph{Manual}
-17.74--75; polakow:afterw, prose:intro).
+14.110; polakow:afterw, prose:intro).

-\mylittlespace You can also use the \textsf{type} field in
+\mylittlespace You can use the \textsf{type} field in
\textsf{artwork}, \textsf{audio}, \textsf{image}, \textsf{music}, and
\textsf{video} entries to identify the medium of the work, e.g.,
-\texttt{oil on canvas}, \texttt{albumen print}, \texttt{compact disc},
-or \texttt{MPEG}.  If the first word in this field would normally only
-be capitalized at the beginning of a sentence, then leave it in
-lowercase in your .bib file and \textsf{biblatex} will automatically
-do the right thing in citations.  Cf.\ \textsf{artwork},
-\textsf{audio}, \textsf{image}, \textsf{music}, and \textsf{video},
-above, for all the details.  (See auden:reading, bedford:photo,
+\texttt{oil on canvas}, \texttt{albumen print}, \texttt{compact disc}
+or \texttt{MPEG}.  In \textsf{book} entries it will normally hold
+system information about multimedia app content, while in
+\textsf{online, article,} and \textsf{review} entries it will hold the
+medium of online multimedia (15.57, 14.267--68).  Cf.\ under these
+entry types in section~\ref{sec:types:authdate}, above, for more

\mybigspace Standard \mymarginpar{\textbf{url}} \textsf{biblatex}
field, it holds the url of an online publication, though you can
-provide one for all entry types.  The 16th edition of the
-\textsf{Manual} expresses a strong preference for DOIs over URLs if
-the former is available --- cf.\ \textsf{doi} above, and also
-\textsf{urldate} just below.  The required \LaTeX\ package
-\textsf{url} will ensure that your documents format such references
-properly, in the text and in the reference apparatus.  It may be worth
-noting that child entries no longer inherit \textsf{url} fields from
-their parents --- the information seems entry-specific enough to
-warrant a little bit of extra typing if you need to present the same
-locator in several entries.
+provide one for all entry types.  The \emph{Manual} expresses a strong
+preference for DOIs over URLs if the former is available --- cf.\
+\textsf{doi} above, and also \textsf{urldate} just below.  The
+required \LaTeX\ package \textsf{url} will ensure that your documents
+format such references properly, in the text and in the reference
+apparatus.  It may be worth noting that child entries no longer
+inherit \textsf{url} fields from their parents --- the information
+seems entry-specific enough to warrant a little bit of extra typing if
+you need to present the same locator in several entries.

-\mybigspace Standard \mymarginpar{\textbf{urldate}} \textsf{biblatex}
-field, it identifies exactly when you accessed a given url.  The 16th
-edition of the \emph{Manual} prefers DOIs to URLs; in the latter case
-it allows the use of access dates, particularly in contexts that
-require it, but prefers that you use revision dates, if these are
-available.  To enable you to specify which date is at stake, I have
-provided the \textbf{userd} field, documented below.  If an entry
-doesn't have a \textsf{userd}, then the \textsf{urldate} will be
-treated, as before, as an access date (14.6--8, 14.184, 15.9;
-evanston:library, grove:sibelius, hlatky:hrt, osborne:poison,
-sirosh:visualcortex, wikiped:bibtex).  In the default setting of
-\cmd{DeclareLabeldate}, any entry without a \textsf{date},
-\textsf{eventdate}, or \textsf{origdate} will use the \textsf{urldate}
-to find a year for citations and the list of references
-(grove:sibelius, wikiped:bibtex).
+\mybigspace Standard \colmarginpar{\textbf{urldate}} \textsf{biblatex}
+field, it identifies exactly when you accessed a given url.  The
+\emph{Manual} prefers DOIs to URLs; in the latter case it allows the
+use of access dates, particularly in contexts that require it, but
+prefers that you use revision dates, if these are available.  To
+enable you to specify which date is at stake, I have provided the
+\textbf{userd} field, documented below.  If an entry doesn't have a
+\textsf{userd}, then the \textsf{urldate} will be treated as an access
+date (14.8, 14.12--13, 15.50; evanston:library, grove:sibelius,
+hlatky:hrt, osborne:poison, sirosh:visualcortex, wikiped:bibtex).  In
+the default setting of \cmd{DeclareLabeldate}, any entry without a
+\textsf{date}, \textsf{eventdate}, or \textsf{origdate} will use the
+\textsf{urldate} to find a year for citations and the list of
+references (grove:sibelius, wikiped:bibtex), but \colmarginpar{New!}
+\emph{only} if the \textsf{urldate} isn't an access date, that is,
+only if a \textsf{userd} field is present.  If the only date available
+is an online access date, then the entry is considered to have no
+date, and \enquote{n.d.} will appear instead, though of course the
+access date will still be printed later in the reference list entry.
+(If you were to put the string \texttt{accessed} into the
+\textsf{userd} field, you could work around this prohibition.)

-% %\enlargethispage{\baselineskip}
+\mylittlespace You can \colmarginpar{New!} also use the
+\textsf{urldate} field to specify a time stamp, should the date alone
+not be specific enough.  The time stamp follows the date, separated by
+an uppercase \enquote{T}, like so:
+\texttt{yyyy-mm-dd\textbf{T}hh:mm:ss}.  If you wish to specify the
+time zone, the \emph{Manual} (10.41) prefers initialisms like
+\enquote{EST} or \enquote{PDT,} and these are most easily provided
+using the \mycolor{\texttt{urltimezone}} field, where you can provide
+your own parentheses if so desired (cp.\ 14.191).  Following the
+examples in the \emph{Manual}, any \textsf{urldate} will by default be
+printed in 24-hour format, though other time stamps use 12-hour
+format.  The \textsf{biblatex} option \texttt{urltime}, discussed in
+section~\ref{sec:preset:authdate}, allows you to change this in your
+preamble.

-\mybigspace A \mymarginpar{\textbf{usera}} supplemental
-\textsf{biblatex} field which functions in \textsf{biblatex-chicago}
-almost as a \enquote{\textsf{journaltitleaddon}} field.  In
-\textsf{article}, \textsf{periodical}, and \textsf{review} entries
-with \textsf{entrysubtype} \texttt{maga\-zine}, the contents of this
-field will be placed, unformatted and between commas, after the
-\textsf{journaltitle} and before the date.  The main use is for
-program (14:221; bundy:macneil).
+\mylittlespace A \textsf{urldate} time stamp (and
+\mycolor{\texttt{urltimezone}}) can appear in any entry whatsoever, if
+you judge the online source to be the sort that changes rapidly enough
+for a time stamp to be necessary (14.207, 14.233; wikiped:bibtex).
+You can stop it printing by setting the new
+\colmarginpar{\texttt{urlstamp}} \mycolor{\texttt{urlstamp}} option to
+\texttt{false} in your preamble for the whole document or for
+specified entry types, or in the \textsf{options} field of individual
+entries.  Please see the documentation of \textbf{date} and also
+and other parts of \textsf{biblatex's} enhanced date specifications.
+Table~\ref{tab:online:adtypes} contains a summary of the current state
+of \textsf{biblatex-chicago's} handling of online materials.

+\mybigspace This \colmarginpar{\textbf{urltimezone}} field can, if
+necessary, specify the time zone associated with a time stamp given as
+part of an \textsf{urldate}.  The \emph{Manual} prefers initialisms
+like \enquote{EST} for this purpose, and you can provide parentheses
+around it at your discretion (cp.\ 10.41 and 14.191).
+
+\mybigspace A \colmarginpar{\textbf{usera}} supplemental
+\textsf{biblatex} field which in certain contexts in
+\textsf{biblatex-chicago} will identify the broadcast network when you
+cite a radio or television program.  In \textsf{article},
+\textsf{periodical}, and \textsf{review} entries with
+\textsf{entrysubtype} \texttt{magazine}, it acts almost as a
+\enquote{\textsf{journaltitleaddon}} field, and its contents will be
+placed, unformatted and between commas, after the
+\textsf{journaltitle} and before the \textsf{date}.  In \textsf{video}
+entries it comes after the \textsf{eventdate}, i.e., the date of first
+broadcast, and is separated from that date by the \cmd{bibstring}
+\enquote{\texttt{on}} (14.213, 14.265; american:crime, bundy:macneil,
+
\mybigspace I \mymarginpar{\textbf{userc}} have implemented this
supplemental \textsf{biblatex} field as part of the Chicago
author-date style's handling of cross-references within the list of
references.  (The \enquote{c} part is meant as a sort of mnemonic for
-this latter function.)  In the 16th edition of the \emph{Manual}, you
-no longer need to use the \textbf{customc} entry type to include
+this latter function.)  In recent editions of the \emph{Manual} you no
+longer need to use the \textbf{customc} entry type to include
alphabetized expansions of \textsf{shorthands} in the reference list,
but you may still need to provide cross-references of some sort to
separate entries in that list, perhaps when a single author uses
@@ -9704,24 +12797,27 @@
or you can place that entry key in the \textsf{userc} field of the
.bib entry that actually contains one of the full citations.  In the
latter case, \textsf{biblatex-chicago} will call \cmd{nocite} for you
-when you cite the main entry.  (See 14.84, 14.86; creasey:ashe:blast,
+when you cite the main entry.  (See 14.81--82; creasey:ashe:blast,
creasey:morton:hide, creasey:york:death, lecarre:quest.)

-\mybigspace The \mymarginpar{\textbf{userd}} \textsf{userd} field,
-recently added to the package, acts as a sort of
-\enquote{\textsf{datetype}} field, allowing you in most entry types to
-identify whether a \textsf{urldate} is an access date or a revision
-date.  The general usage is fairly simple.  If this field is absent,
-then a \textsf{urldate} will be treated as an access date, as has long
-been the default in \textsf{biblatex} and in
+\mybigspace The \mymarginpar{\textbf{userd}} \textsf{userd} field acts
+as a sort of \enquote{\textsf{datetype}} field, allowing you in most
+entry types to identify whether a \textsf{urldate} is an access date
+or a revision date.  The general usage is fairly simple.  If this
+field is absent, then a \textsf{urldate} will be treated as an access
+date, as has long been the default in \textsf{biblatex} and in
\textsf{biblatex-chicago}.  If you need to identify it in any other
way, what you include in \textsf{userd} will be printed \emph{before}
or \enquote{\texttt{last revised}} are what the field will typically
-contain (14.7--8; wikiped:bibtex).  In the absence of a
+contain (14.12--13; wikiped:bibtex).  In the absence of a
\textsf{urldate}, you can in most entry types include a \textsf{userd}
field to qualify a \textsf{date} in the same way it would have
-modified a \textsf{urldate}.
+modified a \textsf{urldate}.  If an entry contains \emph{only} a
+\textsf{urldate} and no other sort of date, and has no \textsf{userd}
+field, that entry will now \colmarginpar{New!} be treated as though it
+had no date, and \enquote{n.d.} will appear in citations and at the
+head of entries in the reference list (15.50).

\mylittlespace Because of the rather specialized needs of some
audio-visual references, this basic sche\-ma changes for
@@ -9754,29 +12850,79 @@
\textsf{title} field, providing the original language in
\textsf{language}, or you can give the original title in
\textsf{title} and the translation in \textsf{usere}.  Cf.\
-\textbf{language}, above.  (See 14.108--110, 14.194; kern,
-pirumova:russian, weresz.)
+\textbf{language}, above.  (See 14.99; kern, pirumova:russian,
+weresz.)

\mybigspace See \mymarginpar{\textbf{userf}}
section~\ref{sec:authrelated}, below.

-\mybigspace Standard \mymarginpar{\textbf{venue}} \textsf{biblatex}
+\mybigspace Standard \colmarginpar{\textbf{venue}} \textsf{biblatex}
offers this field for use in \textsf{proceedings} and
-\textsf{inproceedings} entries, but I haven't yet implemented it,
-mainly because the \emph{Manual} has nothing to say about it.  Perhaps
-the \textsf{organization} field could be used, for the moment,
-instead.  Anything in a \textsf{venue} field will be ignored.
+\textsf{inproceedings} entries, but I haven't yet implemented it
+there, mainly because the \emph{Manual} has nothing to say about it.
+Perhaps the \textsf{organization} field could be used, for the moment,
+instead.  I have implemented the field in the \textbf{misc} entry
+type, both with and without an \textsf{entrysubtype}, in the new
+\mycolor{\textbf{performance}} type, and in the \textbf{unpublished}
+type.  In all uses it will normally present the actual venue of an
+event, as opposed, e.g., to the \textsf{origlocation}, which might
+present where a letter was written or where an earlier edition was
+printed.

-\mybigspace Standard \mymarginpar{\textbf{version}} \textsf{biblatex}
-field, currently only available in \textsf{misc} and \textsf{patent}
-entries in \textsf{biblatex-chicago}.
+\mybigspace Author-date \colmarginpar{\textbf{verbc}} styles in
+\textsf{biblatex} use the \textsf{extradate} field, automatically
+provided by \textsf{biber}, to distinguish citations of different
+works by the same \textsf{author} that were published in the same
+year, e.g., (Surname 1978\textbf{a}).  The Chicago author-date styles
+recommend that some sorts of material --- online comments, newspaper
+articles, and live performances, \emph{inter alia} --- needn't appear
+in reference lists, but only in the text, often accompanied by a full
+date reference (\texttt{cmsdate=full}) rather than by the rather less
+informative year on its own.  In most circumstances a simple
+\texttt{skipbib} in the \textsf{options} field will suffice, but,
+especially with online materials, it is possible, even probable, that
+users will have .bib databases containing different works by the same
+\textsf{author} from the same \textsf{year}, only \emph{some} of which
+need to appear in the reference list.  \textsf{Biber} will provide
+\textsf{extradate} fields for all these entries, however, so it is
+easy to get an extradate letter in a reference even when only one work
+by that \textsf{author} appears in the list, or perhaps a series of
+letters with some missing from the sequence.

+\mylittlespace The \mycolor{\textbf{verbc}} field allows you manually
+to intervene to control these side effects.  (It's a standard
+\textsf{biblatex} field, but isn't used in the standard styles.)
+Putting anything in the field prevents that entry from interfering in
+the \textsf{extradate} provision of entries that don't contain such a
+field, and in more complicated scenarios you could group entries by
+identical \textsf{verbc} field to prevent them from interfering both
+with entries not having any \textsf{verbc} field \emph{and} with
+entries having a different value for that field.  By default, the
+\mycolor{\texttt{commenton}} \textsf{relatedtype} for \textbf{online}
+and \textbf{review} entries adds a \textsf{verbc} field to its entry,
+but you can in all cases control this and provide your own in any
+circumstances and in any entry type you wish.  Please see the
+documentation of those two entry types in
+section~\ref{sec:types:authdate}, and of the \textsf{commenton}
+\textsf{relatedtype} in section~\ref{sec:authrelated}.
+
+\mybigspace Standard \colmarginpar{\textbf{version}} \textsf{biblatex}
+field, formerly only available in \textsf{artwork}, \textsf{image},
+\textsf{misc}, \textsf{music}, and \textsf{pa\-tent} entries in
+\textsf{biblatex-chicago-authordate}, but now also in \textbf{book} and
+\mycolor{\textbf{performance}} entries.  In most entry types it prints
+a localized \enquote{\texttt{version}} string, but there may be
+specialist needs in \textsf{artwork} and \textsf{image} entries, so
+there you'll need to specify the type of data inside the field
+itself.  In the \textsf{book} type it is particularly needed for
+presenting multimedia app content (15.57, 14.268).
+
\mybigspace Standard \mymarginpar{\textbf{volume}} \textsf{biblatex}
field.  It holds the volume of a \textsf{journaltitle} in
\textsf{article} entries, and also the volume of a multi-volume work
in many other sorts of entry.  The treatment and placement of
\textsf{volume} information in \textsf{book}-like entries is rather
-complicated in the \emph{Manual} (14.121--27, 15.39).  In the
+complicated in the \emph{Manual} (14.116--22, 15.41).  In the
reference list, the \textsf{volume} appears either before the
\textsf{maintitle} or before the publication information, while in
citations you may need to provide it in the \textsf{postnote} field
@@ -9783,15 +12929,14 @@
--- see the \textsf{volumes} field, just below.  In a number of these
contexts, and in both books and periodicals, \textsf{volume}
information can appear \emph{immediately before} the page number(s).
-In such a case, the \emph{Manual} (14.121) prescribes the same
+In such a case, the \emph{Manual} (14.116) prescribes the same
treatment for both sorts of sources, that is, that \enquote{a colon
separates the volume number from the page number with no intervening
space.}  I have implemented this, but at the request of Clea~F.\
-Rees I have made this punctuation customizable, using the command
-\cmd{postvolpunct} \mymarginpar{\cmd{postvolpunct}}.  By default it
-prints \cmd{addcolon}, but you can use
-\cmd{renewcommand\{\textbackslash postvolpunct\}\{\ldots\}} in your
-preamble to redefine it.  Cf.\ \textsf{part}, and the command
+Rees \mymarginpar{\cmd{postvolpunct}} I have made this punctuation
+customizable, using the command \cmd{postvolpunct}.  By default it
+in your preamble to redefine it.  Cf.\ \textsf{part}, and the command
documentation in section~\ref{sec:formatting:authdate};
conway:evolution shows how sometimes this field may hold series
information, as well.
@@ -9802,9 +12947,9 @@
in the \textsf{postnote} field of the relevant \cmd{cite} command,
e.g.:

-\begin{quote}
-\cmd{autocite}\texttt{[3:25]\{bibfile:key\}}.
-\end{quote}
+\begin{verbatim}
+\autocite[3:25]{bibfile:key}.
+\end{verbatim}

Cf.\ 15.22; meredith:letters, tillich:system, weber:saugetiere,
wright:evolution.  The entry wright:theory presents one volume of such
@@ -9826,17 +12971,17 @@
field provided by \textsf{biblatex}, which prevents inheritance of any
data from the parent entry.  See \textbf{crossref}, above.

-%\enlargethispage{\baselineskip}
-
-\mybigspace Standard \mymarginpar{\textbf{year}} \textsf{biblatex}
+\mybigspace Standard \colmarginpar{\textbf{year}} \textsf{biblatex}
field, especially important for the author-date specification.  Please
see all the details under \textbf{date} above.  Unlike the
\textsf{date} field \textsf{year} allows non-numeric input, so you can
-put \cmd{bibstring\{nodate\}} here if required, or indeed any other
-sort of non-numerical date information.  If you can guess the date
-then you can include that guess in square brackets instead of
-\cmd{bibstring\{nodate\}}.  Cf.\ bedford:photo, clark:meso\-pot,
+put \verb+\bibstring{nodate}+ here if required, or indeed any other
+sort of non-numerical date information.  For many kinds of uncertain
+and unspecified dates it is now much simpler to make use of
+\textsf{biblatex's} enhanced date specifications in the \textsf{date}
+of how \textsf{biblatex-chicago} implements these enhancements.  Cf.\

\subsubsection{Fields for Related Entries}
\label{sec:authrelated}
@@ -9910,21 +13055,20 @@
\texttt{norwegian}, \texttt{portuguese}, \texttt{spanish}, or
\texttt{swedish}, to which I've added \texttt{russian}.

-\mybigspace The \mymarginpar{\textbf{origlocation}} 16th edition of
-the \emph{Manual} has somewhat clarified issues pertaining to the
-documentation of reprint editions and their corresponding originals
-(14.166, 15.38).  In \textsf{biblatex-chicago} you can provide both an
-\textsf{origlocation} and an \textsf{origpublisher} to go along with
-the \textsf{origdate}, should you so wish, and all of this information
-will be printed in the reference list.  You can also use this field in
-a \textsf{letter} or \textsf{misc} (with \textsf{entrysubtype}) entry
-to give the place where a published or unpublished letter was written
-(14.117).  (Jonathan Robinson has suggested that the
-\textsf{origlocation} may in some circumstances actually be helpful
-for disambiguation, his example being early printed editions of the
-same material printed in the same year but in different cities.  The
-new functionality should make this simple to achieve.  Cf.\
-\textsf{origdate} [section~\ref{sec:fields:authdate}],
+\mybigspace This \mymarginpar{\textbf{origlocation}} field mainly
+serves to help document reprint editions and their corresponding
+originals (14.114, 15.40).  In \textsf{biblatex-chicago} you can
+provide both an \textsf{origlocation} and an \textsf{origpublisher} to
+go along with the \textsf{origdate}, should you so wish, and all of
+this information will be printed in the reference list.  You can also
+use this field in a \textsf{letter} or \textsf{misc} (with
+\textsf{entrysubtype}) entry to give the place where a published or
+unpublished letter was written (14.111, 14.229).  (Jonathan Robinson has
+suggested that the \textsf{origlocation} may in some circumstances
+actually be helpful for disambiguation, his example being early
+printed editions of the same material printed in the same year but in
+different cities.  The new functionality should make this simple to
+achieve.  Cf.\ \textsf{origdate} [section~\ref{sec:fields:authdate}],
\textsf{origpublisher} and \textsf{pubstate}; schweitzer:bach.)
\textbf{NB:} It is impossible to present this same information, as
here, \emph{inside} a single entry using a \texttt{related} field,
@@ -9933,48 +13077,60 @@
separate entry.

\mybigspace As \mymarginpar{\textbf{origpublisher}} with the
-\textsf{origlocation} field just above, the 16th edition of the
-\emph{Manual} has clarified issues pertaining to reprint editions and
-their corresponding originals (14.166, 15.38).  You can provide an
-\textsf{origpublisher} and/or an \textsf{origlocation} in addition to
-the \textsf{origdate}, and all will be presented in long notes and
-bibliography.  (Cf.\ \textsf{origdate}
+\textsf{origlocation} field just above, this field mainly serves to
+help document reprint editions and their corresponding originals
+(14.114, 15.40).  You can provide an \textsf{origpublisher} and/or an
+\textsf{origlocation} in addition to the \textsf{origdate}, and all
+will be presented in the reference list.  (Cf.\ \textsf{origdate}
[section~\ref{sec:fields:authdate}], \textsf{origlocation}, and
-\textsf{pubstate}; schweitzer:bach.)  \textbf{NB:} It is impossible to
+\textsf{pubstate}; schweitzer:\break bach.)  \textbf{NB:} It is impossible to
present this same information, as here, \emph{inside} a single entry
using a \texttt{related} field, though the \textsf{relatedtype}
\texttt{origpubin} presents much the same information \emph{after} the
entry, using data extracted from a separate entry.

-\mybigspace A \mymarginpar{\textbf{pubstate}} standard
-\textsf{biblatex} field.  Because the author-date specification has
-fairly complicated rules about presenting reprinted editions (15.38),
-I have adopted this field as a means of simplifying the problem for
-users.  Instead of manually formatting the \textsf{location} field,
-you can simply put the string \texttt{reprint} into the
-\textsf{pubstate} field, and depending on which date(s) you have
-chosen to appear at the head of the entry,
-\textsf{biblatex-chicago-authordate} will either print the (localized)
-string \texttt{reprint} in the proper place or otherwise provide a
-notice at the end of the entry detailing the original publication
-date.  See under \textbf{date} above for the available permutations.
-(Cf.\ aristotle:metaphy:gr, maitland:canon, maitland:equity,
-schweitzer:bach.)  Aside from the word \texttt{reprint}, the field may
-also contain the word \texttt{forthcoming}, which instructs the styles
-to print that \cmd{bibstring} instead of the \textsf{year}
-(author:forthcoming, contrib:contrib).  Anything else in the field
-will be treated as in the standard styles and printed after the
-publication information.
+\mybigspace In \colmarginpar{\textbf{pubstate}} response to new
+specifications in the 17th edition of the \emph{Manual} (esp.\
+14.137), I have tried to generalize the functioning of the
+\textsf{pubstate} field in all entry types.  Because the author-date
+style has fairly complicated rules about presenting reprinted editions
+(15.40), the \texttt{reprint} string still has a special status.
+Depending on which date(s) you have chosen to appear at the head of
+the entry, \textsf{biblatex-chicago-authordate} will either print the
+(localized) string \texttt{reprint} in the proper place or otherwise
+provide a notice at the end of the entry detailing the original
+publication date.  See under \textbf{date} above for the available
+permutations.  (Cf.\ aristotle:metaphy:gr, maitland:canon,
+maitland:equity, schweitzer:bach.)

-\mylittlespace There is one subtlety of which you ought to be aware.
-In \textsf{music} entries, the \textsf{pubstate} mechanism transforms
-the \textsf{origdate} from a recording date for an album into the
-original release date for that album.  If that date appears in
-citations and at the head of reference-list entries, then this
-mechanism won't generally make much difference, but if it appears
-elsewhere then a recording date will be printed in the middle of the
-reference list entry, while the original release date will be printed
-near the end, preceded by the appropriate string.  \textbf{NB:} For
+\mylittlespace Other strings are divided into two types: those which
+\textsf{biblatex-chicago} will print as the \textsf{year}, which
+currently means \emph{only} those for which \textsf{biblatex} contains
+bibstrings indicating works soon to be published, i.e.,
+\texttt{forthcoming}, \texttt{inpreparation}, \texttt{inpress}, and
+\texttt{submitted}; and those, i.e., everything else, which will be
+printed before, and in close association with, other information about
+the publisher of a work.  (This \colmarginpar{\textbf{NB}} is a change
+from previous behavior, where non-\texttt{reprint} strings were
+printed \emph{after} the publication information, as in the standard
+styles.  You can still use the \textsf{addendum} field to present
+information here, of course.)  The four strings that replace the
+\textsf{year} will always be localized, as will \texttt{reprint} and
+\mycolor{\texttt{selfpublished}} (and anything else that
+\textsf{biblatex} finds to be a \cmd{bibstring}) from the second
+category.  All other strings will be printed as-is, capitalized if
+needed, just before the publisher (author:forthcoming,
+contrib:contrib, schweitzer:bach).
+
+\mylittlespace There is one further subtlety of which you ought to be
+aware.  In \textsf{music} and \textsf{video} entries, the
+\texttt{reprint} string in \textsf{pubstate} will only make a
+difference to your entries when the date which it modifies --- the
+\textsf{origdate}, typically --- \emph{doesn't} appear in citations
+and at the head of reference-list entries.  In this case the date is
+treated as an original release date, and it will be printed, preceded
+by the appropriate string, near the end of the entry.  Other strings
+don't show this special behavior in these entries.  \textbf{NB:} For
those uses of the \textsf{pubstate} field that print a notice at the
end of the entry, the \textsf{relatedtype} \texttt{origpubin} provides
much the same information, using data extracted from a different
@@ -10001,7 +13157,11 @@
entries in the list of references.  If you would like to turn this off
you can set this option, either in your preamble or in the
\textsf{options} or \textsf{relatedoptions} field of the relevant
-entry, to \texttt{false}.
+entry, to \texttt{false}.  For the two \textsf{relatedtypes} that
+construct a single entry using data extracted from related entries ---
+\mycolor{\texttt{commenton}} and \texttt{reviewof} --- you'll need to
+make sure this is \texttt{true} to get properly-formatted citations in
+the reference list.  See below for the details.

\mybigspace This \mymarginpar{\textbf{relatedoptions}} field will, I
should expect, only be needed very rarely.  If you want to set
@@ -10036,11 +13196,11 @@
\texttt{origpubin} string, which brings it into line with the notes
\&\ bibliography style.

-\mybigspace The \colmarginpar{\textbf{relatedtype}} standard
+\mybigspace The \mymarginpar{\textbf{relatedtype}} standard
\textsf{biblatex} styles define six \textsf{relatedtypes}, and I have
either simply adopted them wholesale or adapted them to the needs of
the Chicago style, retaining the basic syntax as much as possible.  I
-have also added one to these six (see below):
+have also added two to these six (see below):

\begin{description}
\item[\qquad bytranslator:] This prints a full reference to a
@@ -10049,7 +13209,7 @@
\ldots} The reference is fuller in \textsf{biblatex-chicago} than
in the standard styles, and for the first time allows users to
choose the \emph{Manual's} alternate method for presenting original
-  + translation (14.109; furet:passing:fr).  The old \textsf{userf}
+  + translation (14.99; furet:passing:fr).  The old \textsf{userf}
mechanism provides the other, as does the \texttt{origpubas}
\textsf{relatedtype} (see below).
\item[\qquad default:] This is the macro used when no
@@ -10084,11 +13244,78 @@
behaving oddly please let me know, including whether you are using
\textsf{babel} [which I've tested] or \textsf{polyglossia} [which I
haven't].)
-  package includes this type, and user Bertold Schweitzer suggested it
-  might be a useful addition to \textsf{biblatex-chicago}, so I've
-  added it to the standard six detailed above.  It differs from all of
-  them in that it prints the \textsf{relatedstring} (by default
+\end{description}
+Now, the Chicago-specific types:
+\begin{description}
+\item[\qquad \mycolor{commenton:}] I designed the new
+  \textsf{relatedtype} \mycolor{\texttt{commenton}} to facilitate
+  citation of online comments, and it is available in two entry types,
+  \textsf{online} and \textsf{review} (with its clone
+  \textsf{suppperiodical}).  In both types the \emph{Manual}
+  (15.51--52) recommends that such material appear \emph{only} in the
+  text and not in the reference list, but I have attempted to simplify
+  the presentation of such material wherever you want it to appear.
+  Following the specifications, then, the default when you use
+  \mycolor{\texttt{commenton}} is for
+  \textsf{biblatex-chicago-authordate} to modify how your .bib entry
+  appears in the .bbl file by setting both \texttt{skipbib} and
+  \texttt{cmsdate=full} in the \textsf{options} field, so that nothing
+  appears in the reference list and citations present the full date
+  and possibly also a time stamp (see below).  Further, the style sets
+  the \mycolor{\textsf{verbc}} field so that these entries don't
+  interfere with the provision of extra date letters --- the full date
+  and time should be enough to individuate separate comments.
+  Finally, the style creates a new \textsf{customc} entry in your .bbl
+  file which you can cite after your initial
+  \mycolor{\texttt{commenton}} entry using \cmd{autocites} and which
+  will, as a comment to your initial entry, say whether it's a comment
+  or a reply or what have you, and then giving the short citation of
+  that upon which it is a comment.  (Just to be clear: your .bib file
+  will itself never be altered, only the .bbl file, which is produced
+  by \textsf{biber} and which provides the data from which
+  \textsf{biblatex} actually typesets citations.)
+
+  As an example, take the Facebook post diaz:surprise, which does
+  appear in the reference list.  The entry licis:diazcomment presents
+  a comment on this post using the \textsf{relatedtype}
+  \mycolor{\texttt{commenton}}, so
+  \textsf{biblatex-chicago-authordate} creates a new entry,
+  diaz:surprise-customc.  When you cite the comment in your document a
+  command like
+  \verb+\autocites{licis:diazcomment}{diaz:surprise-customc}+ will
+  produce a citation like (Licis, February 24, 2016; comment on D\'iaz
+  2016).  You can alter the string connecting the two citations (by
+  default \verb+\bibstring{commenton}+) by using the
+  \textsf{relatedstring} field in the first of them (cf.\
+  powell:comment).  (Note how minimal the .bib entry of a comment
+  using this system can be --- \textsf{author}, \textsf{related},
+  \textsf{relatedtype}, and \textsf{date} are pretty much the only
+  fields required.)
+
+  Those who want \textsf{online} comments to appear in the reference
+  list can still use the \mycolor{\texttt{commenton}}
+  \textsf{relatedtype}, and the same citation of the commented piece
+  will appear there, connected by the same string that the
+  \textsf{customc} entry provides.  Here, though, you can also provide
+  a separate \textsf{title} for the comment, and/or a separate
+  \textsf{url} for it, should they exist, which will be printed
+  before/after the citation of the commented piece, respectively.  (In
+  \textsf{review} entries, which use the same \textsf{relatedtype},
+  only the generic title is available, as is always the case with such
+  entries.)  If you manually set either (or both) of the
+  \texttt{cmsdate} or the \texttt{skipbib} options in your entry then
+  \textsf{biblatex-chicago} will assume you want to hand-craft that
+  entry without its intervention, so it won't alter the
+  \textsf{options} field or indeed provide any
+  \mycolor{\textsf{verbc}} field, though it will still provide the
+  virtual \textsf{customc} entry in your .bbl file, as that may still
+  prove convenient.  Note also that any \mycolor{\textsf{verbc}} field
+  you provide will never be altered by the package.
+\item[\qquad reviewof:] Philip Kime's \textsf{biblatex-apa} package
+  includes this type, and user Bertold Schweitzer suggested it might
+  to the standard six detailed above.  It differs from all of them in
+  that it prints the \textsf{relatedstring} (by default
\cmd{bibstring\{reviewof\}}) and the data from the \textsf{related}
entry in the middle of the parent entry, rather than at the end.  It
also differs from them in being available only in \textsf{article}
@@ -10129,33 +13356,32 @@
original publication details of an essay or a chapter that you are
citing from a subsequent reprint, e.g., a \emph{Collected Essays}
volume.  In such a case, at least according to the \emph{Manual}
-(14.115), such details needn't be provided in notes, only in the
-bibliography, and then only if these details are \enquote{of
-  particular interest.}  The data would follow an introductory phrase
-like \enquote{originally published as,} making the problem strictly
-parallel to that of including details of a work in the original
-language alongside the details of its translation.  I have addressed
-the latter problem with the \textsf{userf} field, which provides a
-sort of cross-referencing method for this purpose, and
-\textsf{reprinttitle} works in \emph{exactly} the same way.  In the
-.bib entry for the reprint you include a cross-reference to the cite
-key of the original location using the \textsf{reprinttitle} field
-(which it may help mnemonically to think of as a \enquote{reprinted
-  title} field).  The main difference between the two forms is that
-\textsf{userf} prints all but the \textsf{author} of the original
-work, whereas \textsf{reprinttitle} suppresses both the
-\textsf{author} and the \textsf{title} of the original, giving only
-the more general details, beginning with, e.g., the
-\textsf{journaltitle} or \textsf{booktitle} and continuing from there.
-The string prefacing this information will be \enquote{Originally
-  published in.}  Please see the documentation on \textsf{userf} below
-for all the details on how to create .bib entries for presenting your
-data.
+(14.181), these details would only appear in the reference list, and
+then only if these details are \enquote{of particular interest.}  The
+data would follow an introductory phrase like \enquote{originally
+  published as,} making the problem strictly parallel to that of
+including details of a work in the original language alongside the
+details of its translation.  I have addressed the latter problem with
+the \textsf{userf} field, which provides a sort of cross-referencing
+method for this purpose, and \textsf{reprinttitle} works in
+\emph{exactly} the same way.  In the .bib entry for the reprint you
+include a cross-reference to the cite key of the original location
+using the \textsf{reprinttitle} field (which it may help mnemonically
+to think of as a \enquote{reprinted title} field).  The main
+difference between the two forms is that \textsf{userf} prints all but
+the \textsf{author} of the original work, whereas
+\textsf{reprinttitle} suppresses both the \textsf{author} and the
+\textsf{title} of the original, giving only the more general details,
+beginning with, e.g., the \textsf{journaltitle} or \textsf{booktitle}
+and continuing from there.  The string prefacing this information will
+be \enquote{Originally published in.}  Please see the documentation on
+\textsf{userf} below for all the details on how to create .bib entries

\mybigspace This \mymarginpar{\textbf{userf}} is one of the
supplemental fields which \textsf{biblatex} provides, and is used by
\textsf{biblatex-chicago} for a very specific purpose.  When you cite
-both a translation and its original, the \emph{Manual} (14.109)
+both a translation and its original, the \emph{Manual} (14.99)
recommends that, in a reference list at least, you combine references
to both texts in one entry.  Lacking specific instructions about the
author-date style, I have nonetheless chosen to implement this
@@ -10189,8 +13415,6 @@
\textsf{relatedstring} field to achieve the same result as with
\textsf{origlanguage}.

-%\enlargethispage{\baselineskip}
-
\subsection{Commands}
\label{sec:commands:authdate}

@@ -10240,10 +13464,10 @@
capital will always be retained.  (cf., e.g., creel:house,
morgenson:market.)  If, on the other hand, you for some reason need
such a field always to start with a lowercase letter, then you can try
-using the \cmd{isdot} macro at the start, which turns off the
-mechanism without printing anything itself.  Here, then, for reference
-purposes, is the complete list of fields where this functionality is
-active:
+putting an empty set of curly braces\ \{\}\ at the start, which turns
+off the mechanism without printing anything itself.  Here, then, for
+reference purposes, is the complete list of fields where this
+functionality is active:

\begin{enumerate}
\setlength{\parskip}{-4pt}
@@ -10273,7 +13497,7 @@
\end{enumerate}

If you accidentally use the \cmd{autocap} macro in one of the above
-fields, it frankly shouldn't matter at all, and you'll still get what
+fields, it really shouldn't matter at all, and you'll still get what
you want, but taking advantage of the automatic provisions should at
least save some typing.

@@ -10283,7 +13507,7 @@
string needs capitalization, depending on where it falls in an entry.
\textsf{Biblatex} also provides functionality which allows you
sometimes simply to input, for example, \texttt{newseries} instead of
-\cmd{bib\-string\{newseries\}}, the package auto-detecting when a
+\verb+\bibstring{newseries}+, the package auto-detecting when a
bibstring is involved and doing the right thing, though in all such
cases either form will work.  This functionality is available in the
\textsf{series} field of \textsf{article}, \textsf{periodical}, and
@@ -10297,7 +13521,16 @@
style-specific, one.  If the \textsf{biblatex} authors generalize it
still further in a future release, I shall do the same, if possible.

-%\enlargethispage{-2\baselineskip}
+\mybigspace I \colmarginpar{\textbf{\textbackslash letterdatelong}}
+have provided this macro mainly for use in the optional postnote field
+of the various citation commands.  When citing a letter (published or
+unpublished, \textsf{letter} or \textsf{misc}), it may be useful to
+include the date in the citation in order to disambiguate references.
+This macro simply prints the date of a letter, or indeed of any other
+sort of correspondence, in day-month-year order, as recommended by the
+\emph{Manual} (14.224).  (If your main document language isn't
+American, it's better just to use the standard \textsf{biblatex}
+command \cmd{printorigdate}.)

\mybigspace This \mymarginpar{\textbf{\textbackslash mkbibquote}} is
the standard \textsf{biblatex} command, which requires attention here
@@ -10343,10 +13576,10 @@

\mylittlespace Note in both cases that you only need to be careful
with the capitalization inside the curly brackets if you are using
-\textsf{authordate-trad}, as the 16th edition of the \textsf{Manual}
-has unified the title formatting for the two remaining styles, which
-means that, for them, all lower- and uppercase letters remain as they
-are typed in your .bib file.
+\textsf{authordate-trad}, as recent editions of the \emph{Manual} have
+unified the title formatting for the two remaining styles, which means
+that, for them, all lower- and uppercase letters remain as they are

\mylittlespace Let me also add that this command interacts well with
Lehman's \textsf{csquotes} package, which I highly recommend, though
@@ -10355,7 +13588,7 @@

\mybigspace The \mymarginpar{\textbf{\textbackslash postvolpunct}}
-\emph{Manual} (14.121) unequivocally prescribes that when a
+\emph{Manual} (14.116) unequivocally prescribes that when a
\textsf{volume} number appears immediately before a page number,
\enquote{the abbreviation \emph{vol.}\ is omitted and a colon
separates the volume number from the page number with no intervening
@@ -10395,8 +13628,6 @@
specific \textsf{title}, rather than to a \textsf{maintitle} or
\textsf{booktitle} (cf.\ \textbf{namea} and \textbf{nameb}, above).

-% %\enlargethispage{\baselineskip}
-
\mylittlespace In the present instance, you can use \cmd{partcomp} to
identify a compiler when \textsf{namec} (or \textsf{editortype}) won't
do, e.g., in a \textsf{note} field or the like.  In such a case,
@@ -10432,6 +13663,54 @@
whose name doesn't conveniently fit into the usual fields
(\textsf{translator} and \textsf{nameb}).

+\mylittlespace This \mymarginpar{\textbf{\textbackslash reprint}} is
+equivalent to \verb+\bibstring{reprint}+.  It is useful in the notes
+\&\ bibliography style, and I include it in the author-date styles for
+compatibility.
+
+\mylittlespace Unlike \colmarginpar{\textbf{\textbackslash
+    suppress-\\bibfield[]\{\}}} the other commands presented here,
+this should be used in your document preamble rather than in your
+bibliographical apparatus.  Also unlike them, it has two arguments,
+the first of which is optional, the second required.  Jan David Hauck
+suggested that, in addition to the field-exclusion package options
+provided by \textsf{biblatex-chicago} (see
+section~\ref{sec:authpreset}), I might also provide a general-purpose
+macro to clear fields from selected entry types when the package
+options aren't quite right for a user's particular needs.  The
+\mycolor{\cmd{suppressbibfield}} command does this, so that
+\verb+\suppressbibfield{note}+ clears the \textsf{note} field from
+\emph{all} entries, while \verb+\suppressbibfield[report]{note}+
+clears it only from \textsf{report} entries.  Both arguments take
+comma-separated lists, so to suppress \textsf{titleaddon} and
+\textsf{volumes} fields from \textsf{report} and \textsf{manual}
+
+\mylittlespace A few usage notes are in order.  First, you can use as
+many calls to the command in your preamble as you wish.  Second, the
+command is a very basic user interface to \textsf{biblatex's} source
+mapping functionality (\textsf{biblatex.pdf} \S~4.5.3), so what it
+does is modify what \textsf{biber} takes from your .bib file in order
+to produce the .bbl file that \textsf{biblatex} actually reads.  As
+far as \textsf{biblatex} is concerned, the fields simply aren't there
+in the data source, so they can't appear anywhere in the
+bibliographical apparatus, whether in citations, reference lists, or
+shorthand lists.  Third, because source mapping is involved, you'll
+need a complete cycle of \LaTeX-\textsf{biber}-\LaTeX\ runs to make
+the commands take effect.  Fourth, source mapping occurs at a very
+early stage in \textsf{biber's} operation, so if your field names or
+entry types are standard aliases, the command will only work on the
+names as they appear in your .bib file, not as they are aliased in the
+.bbl file.  If you have a \textsf{techreport} entry, for example, it
+won't be affected by a command that alters \textsf{report} entries,
+and a \textsf{date} field won't be affected by a command that
+suppresses the \textsf{year}.  Fifth, the code for the command resides
+in \textsf{biblatex-chicago.sty}, so if you load the styles without
+loading that package it won't be available to you.  Sixth and finally,
+the \mycolor{\cmd{suppressbibfield}} command is new and relatively
+untested, so please report any untoward behavior to me.
+
\subsubsection{Citation Commands}
\label{sec:cite:authordate}

@@ -10448,6 +13727,19 @@
commands that would be useful, please let me know, and it should be
possible to fix or add them.

+\mybigspace These \colmarginpar{\textbf{\textbackslash atcite
+    \\\textbackslash atpcite}} two new citation commands allow you
+quickly and easily to provide an author-title citation of any entry,
+instead of an author-date citation.  The \texttt{classical}
+\textsf{entrysubtype} field does this, but it also changes punctuation
+in the citation, so I've provided other means to achieve the same end.
+The first of these new citation commands presents the plain citation,
+the second includes it in parentheses for inclusion in running text.
+The new \mycolor{\texttt{authortitle}} type and entry option
+(section~\ref{sec:authuseropts}) has the same effect when using the
+standard citation commands, but it's possible that using these new
+
\mybigspace I \mymarginpar{\textbf{\textbackslash autocite}} haven't
adapted this in the slightest, but I thought it worth pointing out
that \textsf{biblatex-chicago-authordate} sets this command to use
@@ -10459,7 +13751,7 @@
Skj\xE6rholt requested, for the author-date styles, a variant of the
\cmd{textcite} command that presented the author's name in the
genitive case in running text, thereby simplifying certain syntactic
-constructions (15.24).  The \cmd{gentextcite} command, in effect,
+constructions (15.25).  The \cmd{gentextcite} command, in effect,
provides a way to include almost anything in between the name and the
parenthesized date in a \cmd{textcite}, so its use may well not be
limited to the possessive.  In most respects it behaves exactly like
@@ -10535,11 +13827,37 @@

\mybigspace The \mymarginpar{\texttt{alldates=comp}} specification
calls for the long format when presenting dates, slightly shortened
-when presenting date ranges.  Please note that because of the
-author-date style's complicated requirements with respect to dates,
-there will be cases when printed ranges don't look exactly right ---
-cf., e.g., nass:address.  I'm working on this.
+when presenting date ranges.  The new style option
+\mycolor{\texttt{compressyears}}, enabled by default, means that year
+ranges are now compressed automatically according to the
+\emph{Manual's} instructions (9.64; section~\ref{sec:authpreset}).

+\mylittlespace In \colmarginpar{\texttt{alltimes=12h}} entries which
+print time stamps, they will, when the stamp is part of a
+\textsf{date}, \textsf{eventdate}, or \textsf{origdate}, appear in
+12-hour format, i.e., \enquote{4:45 p.m.}  Stamps that are part of a
+\textsf{urldate} are, by default, controlled by the
+\mycolor{\texttt{urltime}} option, which is set to
+\mycolor{\texttt{24h}}.  See that option below, and
+
+\enlargethispage{\baselineskip}
+
+\mylittlespace This \colmarginpar{\texttt{datecirca=true}} option
+enables \textsf{biblatex's} enhanced \enquote{circa} date
+specification, which given a \textsf{date} like \verb+1989~+ will
+
+\mylittlespace This \colmarginpar{\texttt{dateuncertain=\\true}}
+option enables \textsf{biblatex's} enhanced \enquote{uncertain} date
+specification, which given a \textsf{date} like \verb+1989?+ will
+print [1989?].  A field like \verb+1989%+ is both \enquote{circa}
+\emph{and} \enquote{uncertain,} like so: [ca.\ 1989?].  Cf.\
+
+\mylittlespace This \colmarginpar{\texttt{datezeros=false}} ensures
+that leading zeros don't appear in date specifications.
+
\mylittlespace This \mymarginpar{\texttt{ibidtracker=\\constrict}}
enables an \emph{ibidem} mechanism in citations, but only in the most
strictly-defined circumstances.  The Chicago author-date style doesn't
@@ -10546,7 +13864,7 @@
print \enquote{Ibid} in citations, but in general a repeated citation
on the same page will print only the page reference.  Technically,
this should only occur when a source is cited \enquote{more than once
-  in one paragraph} (15.26), so you can use the \cmd{citereset}
+  in one paragraph} (15.27), so you can use the \cmd{citereset}
command from \textsf{biblatex} to achieve the greatest compliance, as
the package only offers automatic resetting on part, chapter, section,
and subsection boundaries, while \textsf{biblatex-chicago}
@@ -10560,24 +13878,20 @@
empty parentheses, but you will get another standard citation, which

-\enlargethispage{-\baselineskip}
+\mylittlespace This \mymarginpar{\texttt{labeldateparts\\=true}}
+option tells \textsf{biblatex} to provide the special
+\textsf{labelyear} and \textsf{extradate} fields for author-date
+styles.  (This is the option formerly known as \texttt{labelyear} and
+then \texttt{labeldate}, both of which are obsolete.)

-\mylittlespace This \mymarginpar{\texttt{labelyear=\\true}} option
-tells \textsf{biblatex} to provide the special \textsf{labelyear} and
-\textsf{extrayear} fields for author-date styles.
-
\mylittlespace These \mymarginpar{\textsf{\texttt{maxbibnames\\=10\\
minbibnames\\=7}}} two options control the number of names
printed in the list of references when that number exceeds 10.  These
-numbers follow the recommendations of the \emph{Manual} (17.29--30),
-and they are different from those for use in citations.  With
-\textsf{biblatex} 1.6 you can no longer redefine \texttt{maxnames} and
-\texttt{minnames} in the \cmd{printbibliography} command at the bottom
-of your document, so \textsf{biblatex-chicago} does this automatically
-for you, though of course you can change them in your document
-preamble.  Please see section~\ref{sec:otherhints:auth} below (and the
-file \textsf{cms-dates-sample.pdf}) for hints on dealing with entries
-with more than three authors.
+numbers follow the recommendations of the \emph{Manual} (14.76, 15.9),
+and they are different from those for use in citations.  Please see
+section~\ref{sec:otherhints:auth} below (and the file
+\href{file:cms-dates-intro.pdf}{\textsf{cms-dates-intro.pdf}}) for
+hints on dealing with entries with more than three authors.

\mylittlespace This \mymarginpar{\texttt{pagetracker=\\true}} enables
page tracking for the \cmd{iffirstonpage} and \cmd{ifsamepage}
@@ -10608,25 +13922,40 @@
Chicago author-date specification.  Please see the documentation of
\cmd{DeclareSortingTemplate} in section~\ref{sec:authformopts}, below.

+\mylittlespace If \colmarginpar{\texttt{timezones=true}} you provide a
+timezone for a time stamp, usually using one of the \textsf{timezone}
+fields, this option ensures it will be printed.
+
\mylittlespace This \mymarginpar{\texttt{uniquelist=\\minyear}} option
enables \textsf{biblatex-chicago-authordate} to disambiguate entries
which have more than three \textsf{authors}, but which differ
\emph{after} the first name in the list.  This will only occur when
-two such entries have the same \textsf{year} (15.28).  The option is
+two such entries have the same \textsf{year} (15.29).  The option is
\textsf{Biber}-only, like the following, which means that this
next-generation \textsc{Bib}\TeX\ replacement is required for the
-author-date styles.  Please see \textsf{cms-dates-sample.pdf} (or
-below, for further details.
+\href{file:cms-dates-intro.pdf}{\textsf{cms-dates-intro.pdf}} and
+section~\ref{sec:otherhints:auth}, below, for further details.

\mylittlespace This \mymarginpar{\texttt{uniquename=\\minfull}}
enables the package to distinguish different authors who share a
surname, using initials in the first instance, and whole names if
-initials aren't enough (15.21).  The option is \textsf{Biber}-only,
+initials aren't enough (15.22).  The option is \textsf{Biber}-only,
like the previous one.

-%\enlargethispage{\baselineskip}
+\mylittlespace In \colmarginpar{\texttt{urltime=24h}} entries with
+\textsf{urldate} fields containing time stamps, that stamp will by
+default appear in 24-hour format, i.e., \enquote{16:45.}  Cf.\
+\mycolor{\texttt{alltimes}}, above, \mycolor{\texttt{urlstamp}} in

+\mylittlespace In
+\colmarginpar{\texttt{[standard]\\useeditor=false\\usenamec=false}}
+\mycolor{\textsf{standard}} entries any editors' or compilers' names
+appear after the title, according to 14.259, so these
+entry-type-specific options encode this.  You can, of course, override
+these defaults in your preamble, should you deem it necessary.
+
\mylittlespace This \mymarginpar{\texttt{usetranslator\\=true}}
enables automatic use of the \textsf{translator} at the head of
entries in the absence of an \textsf{author} or an \textsf{editor}.
@@ -10649,7 +13978,7 @@
replacement for repeated names in the list of references (15.17--19,
and just below); and the formatting of note numbers, both in the main
text and at the bottom of the page / end of the essay (superscript in
-the text, in-line in the notes; 14.19).  The code for this last
+the text, in-line in the notes; 14.24).  The code for this last
formatting is also in \textsf{biblatex-chicago.sty}, and I've wrapped
it in a test that disables it if you are using the \textsf{memoir}
class, which I believe has its own commands for defining these
@@ -10679,7 +14008,7 @@
use the option \texttt{heading=none} in order to get rid of the
[oversized] default, providing your own within the \cmd{footnote}
command.)  If you use a command like
-\cmd{printbiblist\{shortjournal\}} to print a list of journal
+\verb+\printbiblist{shortjournal}+ to print a list of journal
abbreviations, you can use the \texttt{sjnotes} and
\texttt{sjendnotes} \texttt{bibenvironments} in exactly the same way.
Please see the documentation of \textsf{shorthand} and
@@ -10691,10 +14020,8 @@
\textsf{biblatex} offer enhanced functionality in many areas,
including the next three declarations.  If the default definitions
don't work well for you, you can redefine all of them in your document
-preamble --- see \textsf{biblatex.pdf} \xA7\xA74.5.8 and 4.5.5.
+preamble --- see \textsf{biblatex.pdf} \xA7\xA74.5.6 and 4.5.10.

-%\enlargethispage{\baselineskip}
-
\mylittlespace This \mymarginpar{\cmd{Declare-}\\\texttt{Labelname}}
option allows you to add name fields for consideration when
\textsf{biblatex} is attempting to find a shortened name for in-text
@@ -10746,14 +14073,15 @@

\mylittlespace The advantages of this scheme are, specifically, that
any entry headed by one of the supplemental name fields
-(\textsf{name[a-c]}), a \textsf{manual} entry headed by an
-\textsf{organization}, or an \textsf{article} or \textsf{review} entry
-with an \textsf{entrysubtype} and headed by a \textsf{journaltitle}
-will no longer need a \textsf{sortkey} set.  Further, the
-\textsf{biblatex} \texttt{use<name>=false} options will remove any
-name field from the sorting order, again reducing the need for user
-intervention.  The main disadvantage should only occur very rarely.
-In \textsf{author}-less \textsf{article} and \textsf{review} entries
+(\textsf{name[a-c]}), a \textsf{manual} or a
+\mycolor{\textsf{standard}} entry headed by an \textsf{organization},
+or an \textsf{article} or \textsf{review} entry with an
+\textsf{entrysubtype} and headed by a \textsf{journaltitle} will no
+longer need a \textsf{sortkey} set.  Further, the \textsf{biblatex}
+\texttt{use<name>=false} options will remove any name field from the
+sorting order, again reducing the need for user intervention.  The
+main disadvantage should only occur very rarely.  In
+\textsf{author}-less \textsf{article} and \textsf{review} entries
without an \textsf{entrysubtype}, the \textsf{title} will appear
instead of the \textsf{journaltitle}, and since the latter appears
before the former in the sorting scheme, you'll need a
@@ -10769,32 +14097,33 @@
field by default, and this option allows you to stop the printing of
this information in the reference list.  It defaults to true, which
means the field is printed, but it can be set to false either in the
-preamble, for the whole document, or on a per-entry basis in the
-\textsf{options} field (though rather than use this latter method it
-would make sense to eliminate the \textsf{pages} field from the
-affected entries).
+preamble, for the whole document or for specific entry types, or on a
+per-entry basis in the \textsf{options} field (though rather than use
+this latter method it would make sense to eliminate the \textsf{pages}
+field from the affected entries).

\mylittlespace This \mymarginpar{\texttt{doi=true}} option controls
whether any \textsf{doi} fields present in the .bib file will be
printed in the reference list.  At the request of Daniel Possenriede,
and keeping in mind the \emph{Manual's} preference for this field
\texttt{only}, which prints the \textsf{doi} if it is present and the
\textsf{url} only if there is no \textsf{doi}.  The package default
remains the same, however --- it defaults to true, which will print
both \textsf{doi} and \textsf{url} if both are present.  The option
can be set to \texttt{only} or to \texttt{false} either in the
-preamble, for the whole document, or on a per-entry basis in the
-\textsf{options} field.  In \textsf{online} entries, the \textsf{doi}
-field will always be printed, but the \texttt{only} switch will still
-eliminate any \textsf{url}.
+preamble, for the whole document or for specific entry types, or on a
+per-entry basis in the \textsf{options} field.  In \textsf{online}
+entries, the \textsf{doi} field will always be printed, but the
+\texttt{only} switch will still eliminate any \textsf{url}.

\mylittlespace This \mymarginpar{\texttt{eprint=true}} option controls
whether any \textsf{eprint} fields present in the .bib file will be
printed in the list of references.  It defaults to true, and can be
-set to false either in the preamble, for the whole document, or on a
-per-entry basis, in the \textsf{options} field.  In \textsf{online}
-entries, the \textsf{eprint} field will always be printed.
+set to false either in the preamble, for the whole document or for
+specific entry types, or on a per-entry basis, in the \textsf{options}
+field.  In \textsf{online} entries, the \textsf{eprint} field will
+always be printed.

\mylittlespace This \mymarginpar{\texttt{isbn=true}} option controls
whether any \textsf{isan}, \textsf{isbn}, \textsf{ismn},
@@ -10801,60 +14130,81 @@
\textsf{isrn}, \textsf{issn}, and \textsf{iswc} fields present in the
.bib file will be printed in the list of references.  It defaults to
true, and can be set to false either in the preamble, for the whole
-document, or on a per-entry basis, in the \textsf{options} field.
+document or for specific entry types, or on a per-entry basis, in the
+\textsf{options} field.

-%%\enlargethispage{-\baselineskip}
-
-\mylittlespace Once \mymarginpar{\texttt{numbermonth=\\true}} again
-at the request of Scot Becker, I have included this option, which
+\mylittlespace Once \mymarginpar{\texttt{numbermonth\\=true}} again at
+the request of Scot Becker, I have included this option, which
controls the printing of the \textsf{month} field in all the
periodical-type entries when a \textsf{number} field is also present.
Some bibliographic software, apparently, always includes the month of
publication even when a \textsf{number} is present.  When all this
-information is available the \emph{Manual} (17.181) prints everything,
+information is available the \emph{Manual} (14.171) prints everything,
so this option defaults to true, which means the field is printed, but
-it can be set to false either in the preamble, for the whole document,
-or on a per-entry basis in the \textsf{options} field.
+it can be set to false either in the preamble, for the whole document
+or for specific entry types, or on a per-entry basis in the
+\textsf{options} field.

\mylittlespace This \mymarginpar{\texttt{url=true}} option controls
whether any \textsf{url} fields present in the .bib file will be
printed in the reference list.  It defaults to true, and can be set to
-false either in the preamble, for the whole document, or on a
-per-entry basis, in the \textsf{options} field.  Please note that, as
-in standard \textsf{biblatex}, the \textsf{url} field is always
-printed in \textsf{online} entries, regardless of the state of this
-option.
+false either in the preamble, for the whole document or for specific
+entry types, or on a per-entry basis, in the \textsf{options} field.
+Please note that, as in standard \textsf{biblatex}, the \textsf{url}
+field is always printed in \textsf{online} entries, regardless of the
+state of this option.

+\mylittlespace This \colmarginpar{\texttt{urlstamp=true}} option
+controls whether any \textsf{urltime} fields, included as part of the
+\textsf{urldate}, will be printed in citations and reference list.  It
+defaults to true, and can be set to false either in the preamble, for
+the whole document or for specific entry types, or on a per-entry
+basis in the \textsf{options} field.  Please note that, unlike the
+\texttt{url} option, this option \emph{does} control what is printed
+in \textsf{online} entries.
+
\mylittlespace This \mymarginpar{\texttt{includeall=\\true}} is the
-one option that rules the six preceding, either printing all the
+one option that rules the seven preceding, either printing all the
fields under consideration --- the default --- or excluding all of
them.  It is set to \texttt{true} in \textsf{chicago-authordate.cbx},
-but you can change it either in the preamble for the whole document
-or, for specific fields, in the \textsf{options} field of individual
-entries.  The rationale for all of these options is the availability
-of bibliographic managers that helpfully present as much data as
+but you can change it either in the preamble for the whole document or
+for specific entry types, or in the \textsf{options} field of
+individual entries.  The seven individual options above are similarly
+available in the same places, for finer-grained control.  The
+rationale for all of these options is the availability of
+bibliographic managers that helpfully present as much data as
possible, in every entry, some of which may not be felt to be entirely
necessary.  Setting \texttt{includeall} to \texttt{true} probably
works just fine for those compiling their .bib databases by hand, but
others may find that some automatic pruning helps clear things up, at
-least to a first approximation.  Some per-entry work afterward may
-then polish up the details.
+least to a first approximation.  Some per-type or per-entry work
+afterward may then polish up the details.  If you find that you need
+control over fields that aren't included among these options, I have
+provided the \mycolor{\cmd{suppressbibfield}} command for your
+preamble, as suggested by Jan David Hauck.  It is in fact a user
+interface to the source mapping feature of \textsf{biblatex}, and it
+is something of a nuclear option, preventing fields from even
+appearing in the .bbl file generated by \textsf{biber} from your .bib
+database.  See the \mycolor{\cmd{suppressbibfield}} command in
+section~\ref{sec:formatting:authdate} and the source mapping docs in
+\textsf{biblatex.pdf} \S~4.5.3.

\paragraph*{\protect\mymarginpar{\texttt{avdate=true}}}
-For \textsf{music} and \textsf{video} entries, the 16th edition of the
-\emph{Manual} (15.53) strongly recommends both that you provide a
-that this earlier date should appear in citations and at the head of
-reference list entries.  In the default setting of
-\cmd{DeclareLabeldate}, \textsf{biblatex} searches for dates in the
-following order: \textsf{year, eventyear, origyear, urlyear}.  This
-option changes the default ordering in \textsf{music} and
-\textsf{video} entries to the following: \textsf{eventyear, origyear,
-  year, urlyear}.  \textsf{Review} entries presenting on-line comments
-have similar needs, so the same reordering applies to that entry type,
-too.  If you simply want to apply the defaults to these three entry
+For \textsf{music} and \textsf{video} entries, the \emph{Manual}
+(14.263, 15.57) strongly recommends both that you provide a recording,
+earlier date should appear in citations and at the head of reference
+list entries.  In the default setting of \cmd{DeclareLabeldate},
+\textsf{biblatex} searches for dates in the following order:
+\textsf{year, eventyear, origyear, urlyear}.  This option changes the
+default ordering in \textsf{music} and \textsf{video} entries to the
+following: \textsf{eventyear, origyear, year, urlyear}.
+\textsf{Review} entries presenting on-line comments have similar
+needs, as do \mycolor{\textsf{standard}} entries, so the same
+reordering applies to those entry types, too.  If you simply want to
+apply the defaults to these four entry types, you can use
\textsf{biblatex-chicago}.  If, however, you want to tailor the
algorithm to your own needs, then you can use \cmd{DeclareLabeldate}
@@ -10861,9 +14211,10 @@
of the style hard-code the search syntax, and although they take
account of the \texttt{avdate} setting, if you use your own
definitions of \cmd{DeclareLabeldate} the results may, in some corner
-cases, surprise.  Please see \textsf{music}, \textsf{review}, and
-\textsf{video} in section~\ref{sec:types:authdate}; \textsf{date},
-\textsf{eventdate}, \textsf{origdate}, and \textsf{urldate} in
+cases, surprise.  Please see \textsf{music}, \textsf{review},
+\mycolor{\textsf{standard}}, and \textsf{video} in
+section~\ref{sec:types:authdate}; \textsf{date}, \textsf{eventdate},
+\textsf{origdate}, and \textsf{urldate} in
section~\ref{sec:fields:authdate}; and \cmd{DeclareLabeldate} in
section~\ref{sec:authformopts}.

@@ -10887,7 +14238,7 @@
\emph{not} get any abbreviated citations in the reference list.
\item[\qquad false:] You'll get abbreviated citations in these entry
types in the reference list.
-\item[\qquad notes,bib:] These two options are carried over from the
+\item[\qquad notes, bib:] These two options are carried over from the
notes \&\ bibliography style; here they are synonymous with
\texttt{false} and \textsf{true}, respectively.
\end{description}
@@ -10905,25 +14256,36 @@
recommend the use of shorthands as abbreviations for long authors'
names, particularly institutional names, which means the shorthand
will replace only the name part in citations rather than the whole
-citation (15.36; bsi:abbreviation, iso:electrodoc).  The 16th edition
-now suggests placing the abbreviation at the head of the entry,
-followed by its expansion inside parentheses, an arrangement
-automatically provided by \textsf{biblatex-chicago-authordate} when
-you use the \textsf{shorthand} field, assuming you retain the default
-setting of this option.  Please note that you can still print a list
-of shorthands if you wish, and you can also get back something
+citation (15.37; bsi:abbreviation, iso:electrodoc).  Recent editions
+suggest placing the abbreviation at the head of the entry, followed by
+its expansion inside parentheses, an arrangement automatically
+provided by \textsf{biblatex-chicago-authordate} when you use the
+\textsf{shorthand} field, assuming you retain the default setting of
+this option.  Please note that you can still print a list of
+shorthands if you wish, and you can also get back something
approaching the \enquote{standard} behavior of shorthands if you give
the \texttt{cmslos=false} option to \textsf{biblatex-chicago} in your
document preamble.  Cf.\ section~\ref{sec:fields:authdate},
s.v. \enquote{\textbf{shorthand}} above, and also
-\textsf{cms-dates-sample.pdf}.
+\href{file:cms-dates-intro.pdf}{\textsf{cms-dates-intro.pdf}}.

+\mylittlespace The \colmarginpar{\texttt{compressyears\\=true}}
+\emph{Manual} has long recommended (9.64, 15.41), as a space-saving
+measure, the compression of year ranges when presenting dates.  I
+have, finally, implemented this in the current release, and have made
+it the default, which you can change in your document preamble.
+Please note that the rules for compressing years are different from
+those for compressing other numbers (e.g., page numbers), and also
+that the compression code is in \textsf{biblatex-chicago.sty}, which
+will have to be loaded for this option to make any difference.  Cf.\
+
\mylittlespace Roger
requested a way to control the punctuation printed before the
\textsf{maintitleaddon} fields.  By default, this is
\textsf{book-} and \textsf{maintitleaddons} in the list of references,
default before most \textsf{titleaddons} there.  If the punctuation
@@ -10950,6 +14312,17 @@
relevant option to \texttt{none} in your entry and then include the
punctuation in the \textsf{titleaddon} field itself.

+\mylittlespace Constanza Cordoni \colmarginpar{\texttt{dashed=true}}
+has requested a way to turn off the 3-em dash for replacing repeated
+names in the reference list, and the \emph{Manual} admits that some
+publishers prefer this, as the dash can carry with it certain
+inconveniences, especially for electronic formats (15.17).  Some of
+\textsf{biblatex's} standard styles have a \texttt{dashed} option, so
+for compatibility purposes I've provided the same.  By default, I have
+set it to print the name dash, but you can set
+\mycolor{\texttt{dashed=false}} in your preamble to repeat names
+
\mylittlespace If \mymarginpar{\texttt{hidevolumes=\\true}} both a
\textsf{volume} and a \textsf{volumes} field are present, as may occur
particularly in cross-referenced entries, then
@@ -10974,7 +14347,7 @@
note that in \textsf{periodical} entries the \textsf{title} and
\textsf{shorttitle} fields behave in exactly the same manner.  For
more details, see the documentation of \textbf{shortjournal} in
-section~\ref{sec:entryfields}, above.
+section~\ref{sec:fields:authdate}, above.

\mylittlespace This \mymarginpar{\texttt{longcrossref=\\false}} is
the second option, requested by Bertold Schweitzer, for controlling
@@ -11001,7 +14374,7 @@
setting to provide abbreviated citations not just of the four entry
types mentioned but also of \textsf{book}, \textsf{bookinbook},
\textsf{collection}, and \textsf{proceedings} entries.
-\item[\qquad notes,bib:] These two options are carried over from the
+\item[\qquad notes, bib:] These two options are carried over from the
notes \&\ bibliography style; here they are synonymous with
\texttt{false} and \textsf{true}, respectively.
\end{description}
@@ -11013,33 +14386,39 @@
above, and also the documentation of \textsf{crossref} in
section~\ref{sec:fields:authdate}.

-%\enlargethispage{\baselineskip}
-
\mylittlespace This \mymarginpar{\texttt{nodates=true}} option means
-that for all entry types except \textsf{inreference}, \textsf{misc},
-and \textsf{reference}, \textsf{bibla\-tex-chicago} will automatically
-provide \cmd{bibstring\{nodates\}} for any entry that doesn't
-otherwise provide a date for citations and for the heads of entries in
-the list of references.  If you set \texttt{nodates=false} in your
-preamble, then the package won't perform this substitution in any
-entry type whatsoever.  (The bibstring expands to
-\enquote{\texttt{n.d.}} in English.)
+that for all entry types except \textsf{misc} and
+\mycolor{\textsf{dataset}} \textsf{biblatex-chicago} will
+automatically provide \verb+\bibstring{nodate}+ for any entry that
+doesn't otherwise provide a date for citations and for the heads of
+entries in the list of references.  If you set \texttt{nodates=false}
+either in your preamble (for global coverage) or in individual entries
+then the package won't perform this substitution.  (The bibstring
+expands to \enquote{\texttt{n.d.}} in English.)

-\mylittlespace As \mymarginpar{\texttt{usecompiler=\\true}}
-\textsf{biblatex} automatically includes a \texttt{usenamec} option as
-standard, the Chicago-specific option \texttt{usecompiler} is now
-\texttt{usenamec}, which works much better across the board.
-
\subsubsection{Style Options -- Preamble}
\label{sec:authuseropts}

These are parts of the specification that not everyone will wish to
-enable.  All except the fifth can be used even if you load the package
-in the old way via a call to \textsf{biblatex}, but most users can
-just place the appropriate string(s) in the options to the
+enable.  All except the sixth and eighth can be used even if you load
+the package in the old way via a call to \textsf{biblatex}, but most
+users can just place the appropriate string(s) in the options to the

+\mylittlespace \textsf{Biblatex-chicago}
+\colmarginpar{\texttt{alwaysrange}} now implements \textsf{biblatex's}
+enhanced date specifications, one part of which is the presentation of
+decades and centuries not as year ranges but as localized strings like
+\enquote{19th c.} or \enquote{1970s.}  The
+\mycolor{\texttt{alwaysrange}} option set to \texttt{true}, either in
+your preamble or in individual entries, simply tells the package to
+present the year range instead.  This allows you to use the efficient
+enhanced notations in the \textsf{date} field (\verb+{18XX}+ or
+\verb+{197X}+) without the localized strings appearing, should you
+require it.  The two options \mycolor{\texttt{centuryrange}} and
+\mycolor{\texttt{decaderange}} limit the same effect to centuries and
+
\mylittlespace At \mymarginpar{\texttt{annotation}} the request of
Emil Salim, I have added to this version of \textsf{biblatex-chicago}
the ability to produce annotated reference lists.  If you turn this
@@ -11046,11 +14425,52 @@
option on then the contents of your \textsf{annotation} (or
\textsf{annote}) field will be printed after the reference.  (You can
also use external files to store annotations -- please see
-\textsf{biblatex.pdf} \xA7~3.11.8 for details on how to do this.)  This
+\textsf{biblatex.pdf} \xA7~3.13.8 for details on how to do this.)  This
functionality is currently in a beta state, so before you use it
please have a look at the documentation for the \textsf{annotation}
field, in section~\ref{sec:fields:authdate} above.

+\mylittlespace In \colmarginpar{\texttt{authortitle}} a few contexts
+--- classical references, some archival material, perhaps scientific
+data\-bases --- the provision of a date for citations may well be
+impossible, irrelevant, or both.  The \textsf{entrysubtype} value
+\texttt{classical} results in author-title citations for the entry
+containing it, but it modifies punctuation in those citations in a way
+that might be wrong for some sources, and it's also possible that you
+may need the \textsf{entrysubtype} field for some other purpose yet
+still wish to present author-title citations.  You can set
+\mycolor{\texttt{authortitle}} to \texttt{true} either for a specific
+entry type in the preamble or in the \textsf{options} field of
+individual entries to achieve this.  You can also use the citation
+if that's more convenient.  The \textsf{shorttitle} field provides a
+way to abbreviate long titles in this context.  Please note that
+\textsf{biblatex-chicago} by default sets this to \texttt{true} for
+the new \mycolor{\textsf{dataset}} entry type, so you can set it to
+\texttt{false} if you want to present such entries differently.
+
+\mylittlespace This \colmarginpar{\texttt{centuryrange}} option works
+just like \mycolor{\texttt{alwaysrange}}, above, but only affects
+
+\mylittlespace The \colmarginpar{\texttt{cmsbreakurl}} \emph{Manual}
+gives fairly specific instructions about breaking URLs across lines
+(14.18), so I have attempted to implement them by tweaking
+\textsf{biblatex's} default settings, which are found in
+\textsf{biblatex.def}.  In truth, I haven't succeeded in getting
+\textsf{biblatex} flawlessly to follow all of the \emph{Manual's}
+instructions, nor do the changes I have made work well in all
+circumstances, being particularly unsightly if you happen to be using
+the \textsf{ragged2e} package.  For these reasons, I have made my
+changes dependent on a package option, \mycolor{\texttt{cmsbreakurl}},
+which you can set in your preamble.  I have placed all of this code in
+\textsf{biblatex-chicago.sty}, so if you load the package with a call
+to \textsf{biblatex} instead, then URL line breaking will revert to
+the \textsf{biblatex} defaults.  See
+\href{file:cms-dates-sample.pdf}{\textsf{cms-dates-sample.pdf}} for a
+lot of examples of what URLs look like when the option is set, and
+
\mylittlespace This \mymarginpar{\texttt{cmsdate}} option used
\emph{in the preamble} provides a method for simplifying the creation
of data\-bases with a great many multi-date entries.  Despite warnings
@@ -11074,28 +14494,27 @@
options.  If you want to present the \textsf{origdate} at the head
of an entry, then generally speaking you should probably use
\texttt{cmsdate=both}.  I have nevertheless retained this option for
-  certain cases where it has proved useful.  The 15th-edition options
+  certain cases where it has proved useful.  The old options
\texttt{new} and \texttt{old} work like \texttt{both}.
\end{enumerate}

The important information for the user is that, when you set this
-option in your preamble to \texttt{on} or \texttt{both} (or to the
-15th-edition synonyms for the latter, \texttt{new} or \texttt{old}),
-then \textsf{biblatex-chicago-authordate} (and
-\cmd{DeclareLa\-beldate} definition so that the \textsf{labelyear}
-search order will be \textsf{origdate, date, eventdate, urldate}.
-This means that for entry types not covered by the \texttt{avdate}
-option, and for those types as well if you turn off that option, the
-\textsf{labelyear} will, in any entry containing an \textsf{origdate},
-be that very date.  If you want \emph{every} such entry to present its
-\textsf{origdate} in citations and at the head of reference list
-entries, then setting the option this way makes sense, as you should
-automatically get the proper \textsf{extrayear} letter
-(1926\textbf{a}) and the correct sorting, without having to use the
-counter-intuitive .bib file date switching that sometimes accompanied
-the entry-only \texttt{cmsdate} option.  A few clarifications may yet
-be in order.
+option in your preamble to \texttt{on} or \texttt{both} (or to the old
+synonyms for the latter, \texttt{new} or \texttt{old}), then
+will change the default \cmd{DeclareLabeldate} definition so that the
+\textsf{labelyear} search order will be \textsf{origdate, date,
+  eventdate, urldate}.  This means that for entry types not covered by
+the \texttt{avdate} option, and for those types as well if you turn
+off that option, the \textsf{labelyear} will, in any entry containing
+an \textsf{origdate}, be that very date.  If you want \emph{every}
+such entry to present its \textsf{origdate} in citations and at the
+head of reference list entries, then setting the option this way makes
+sense, as you should automatically get the proper \textsf{extradate}
+letter (1926\textbf{a}) and the correct sorting, without having to use
+the counter-intuitive .bib file date switching that sometimes
+accompanied the entry-only \texttt{cmsdate} option.  A few
+clarifications may yet be in order.

\mylittlespace Obviously, any entry with only a \textsf{date} should
behave as usual.  Also, since \textsf{patent} entries have fairly
@@ -11131,11 +14550,18 @@
\mylittlespace When \mymarginpar{\texttt{compresspages}} set to
\texttt{true}, any page ranges in your .bib file or in the
\textsf{postnote} field of your citation commands will be compressed
-in accordance with the \emph{Manual's} specifications (9.60).
+in accordance with the \emph{Manual's} specifications (9.61).
Something like 321-{-}328 in your .bib file would become 321--28 in
your document.  See the \textsf{pages} field in
-section~\ref{sec:fields:authdate}, above.
+section~\ref{sec:fields:authdate}, above.  Please note that the code
+for this is in \textsf{biblatex-chicago.sty}, so if you load the
+package with a call to \textsf{biblatex} instead then you'll get the
+default \textsf{biblatex} compression style.

+just like \mycolor{\texttt{alwaysrange}}, above, but only affects
+
\mylittlespace Although \mymarginpar{\texttt{footmarkoff}} the
\emph{Manual} (14.19) recommends specific formatting for footnote (and
endnote) marks, i.e., superscript in the text and in-line in foot- or
@@ -11169,7 +14595,7 @@
latter anywhere in your document please be aware that it will also be
turned off there.

-\mylittlespace When \colmarginpar{\texttt{hypertitle}} you use the
+\mylittlespace When \mymarginpar{\texttt{hypertitle}} you use the
\textsf{hyperref} package with the author-date styles, the in-text
citations will provide a hyperlink to the full information in the list
of references.  Timo Thoms rightly pointed out that, generally, one
@@ -11179,12 +14605,12 @@
\textsf{date}, but if you set this option to \texttt{true} globally in
your preamble then all \textsf{titles} and \textsf{shorthands} will
link, regardless of whether a \textsf{date} is also present.  You can
-also set \mycolor{\texttt{hypertitle}} in the \textsf{options} field
-of individual entries, allowing you to provide a hyperlink in cases
-where the automatic mechanism gets it wrong (ency:britannica).
+also set \texttt{hypertitle} in the \textsf{options} field of
+individual entries, allowing you to provide a hyperlink in cases where
+the automatic mechanism gets it wrong (ency:britannica).

\mylittlespace The \mymarginpar{\texttt{juniorcomma}} \emph{Manual}
-(6.47) states that \enquote{commas are not required around \emph{Jr.}\
+(6.43) states that \enquote{commas are not required around \emph{Jr.}\
and \emph{Sr.},} so by default \textsf{biblatex-chicago} has
followed standard \textsf{biblatex} in using a simple space in names
like \enquote{John Doe Jr.}  Charles Schaum has pointed out that
@@ -11214,6 +14640,22 @@
\texttt{[style=chicago-authordate]\{bibla\-tex\}}, so I hope this
requirement isn't too onerous.

+\mylittlespace When \colmarginpar{\texttt{nodatebrackets}\\
+  \texttt{noyearbrackets}} you use \textsf{biblatex's} enhanced date
+specifications to present an uncertain date (\verb+{1956?}+), a
+\enquote{circa} date (\verb+{1956~}+), or one that is both at the same
+time (\verb+{1956%}+), the date that by default will appear in your
+documents will have square brackets around it.  This accords with the
+\emph{Manual's} instructions concerning such dates (15.44), but may in
+some circumstances prove syntactically awkward, or may perhaps be out
+of step with a specific house style.  These two options, which may
+appear in the preamble either for the whole document or for specific entry
+types, or in individual entries, allow you to control when these
+brackets will appear.  The first controls, mainly, dates that appear
+in the body of an entry in the reference list, while the second
+controls dates in citations and at the head of entries in the
+
\mylittlespace At \mymarginpar{\texttt{noibid}} the request of an
early tester, I have included this option to allow you globally to
turn off the \texttt{ibidem} mechanism that
@@ -11233,12 +14675,12 @@
\textsf{date} specification as an ordinal number: 26th March 2017.
The new package default prints 26 March 2017, which is more in keeping
both with standard British usage and with the recommendations of the
-\emph{Manual} (9.36).  The option is available only in the preamble.
+\emph{Manual} (9.35).  The option is available only in the preamble.

\mylittlespace Originally
\mymarginpar{\texttt{postnotepunct}\\(experimental)} designed for the
-notes \&\ bibliography style, this option may in fact be more useful in
-the \textsf{authordate} styles.  If set to \texttt{true}, it allows
+notes \&\ bibliography style, this option may in fact be more useful
+in the \textsf{authordate} styles.  If set to \texttt{true}, it allows
you to alter the punctuation that appears just before the
\textsf{postnote} argument of citation commands, simplifying in
particular the provision of comments within parenthetical citations.
@@ -11245,18 +14687,31 @@
In previous releases, you either needed to include the comment after a
page number, e.g., \cmd{autocite[16; some comment]\{citekey\}}, or
provide a separate .bib entry using the \textsf{customc} entry type,
-e.g., \cmd{autocites\{chicago:man\-ual\}\{chicago:comment\}}.  With
-this option enabled, \cmd{autocite[;\,some\,comment]\{citekey\}} will
-do.  More generally, the \texttt{postnotepunct} option
-allows you to start the \textsf{postnote} field with a punctuation
-mark (.\,,\,;\,:) and have it appear as the \cmd{postnotedelim} in
-place of whatever the package might otherwise automatically have
-chosen.  Please note that this functionality relies on a very nifty
-macro by Philipp Lehman which I haven't extensively tested, so I'm
-labeling this option \enquote{experimental.}  Note also that the
-option only affects the \textsf{postnote} field of citation commands,
-not the \textsf{pages} field in your .bib file.
+e.g., \cmd{autocites\{chicago:manual\}\{chicago:comment\}}.  With this
+option enabled, \cmd{autocite[;\,some\,comment]\{citekey\}} will do.
+More generally, the \texttt{postnotepunct} option allows you to start
+the \textsf{postnote} field with a punctuation mark (.\,,\,;\,:) and
+have it appear as the \cmd{postnotedelim} in place of whatever the
+package might otherwise automatically have chosen.  Please note that
+this functionality relies on a very nifty macro by Philipp Lehman
+which I haven't extensively tested, so I'm labeling this option
+\enquote{experimental.}  Note also that the option only affects the
+\textsf{postnote} field of citation commands, not the \textsf{pages}

+\enlargethispage{\baselineskip}
+
+\mylittlespace This \colmarginpar{\texttt{seriesabbrev}} option
+controls the printing, in the reference list, of the
+\mycolor{\textsf{shortseries}} field in place of the \textsf{series}
+field in book-like entries.  It is \texttt{false} by default, so as
+shipped \textsf{biblatex-chicago-authordate} will silently ignore such
+fields, but you can set it to \texttt{true} either in the preamble for
+the whole document or for specific entry types, or in individual
+entries, and it will appear in the reference list.  For more details,
+see the documentation of \mycolor{\textsf{shortseries}} in
+section~\ref{sec:fields:authdate}, above.
+
\mylittlespace Kenneth Pearce \mymarginpar{\texttt{shorthandfull}} has
suggested that, in some fields of study, a list of shorthands
providing full bibliographical information may replace the list of
@@ -11292,12 +14747,11 @@
\label{sec:authentryopts}

These options are settable on a per-entry basis in the
-\textsf{options} field; both relate to the presentation of dates in
-citations and the list of references.
+\textsf{options} field.

-\mylittlespace The \mymarginpar{\texttt{cmsdate}} 16th edition of the
-\emph{Manual} has simplified the options for entries with more than
-one date (15.38).  You can choose among them using the
+\mylittlespace Recent \mymarginpar{\texttt{cmsdate}} editions of the
+\emph{Manual} have simplified the options for entries with more than
+one date (15.40).  You can choose among them using the
\texttt{cmsdate} entry option.  It has 3 possible states relevant to
this problem, alongside a fourth which I discuss below.  An example
should make this clearer.  Let us assume that an entry presents a
@@ -11313,13 +14767,13 @@
If you want to present the \textsf{origdate} at the head of an
entry, then generally speaking you should probably use
\texttt{cmsdate=both}.  I have retained the option because in some
-  cases it is still useful.  The 15th-edition options \texttt{new} and
+  cases it is still useful.  The old options \texttt{new} and
\texttt{old} work like \texttt{both}.
\end{description}

As I explained in detail above in section~\ref{sec:fields:authdate},
s.v.\ \enquote{\textbf{date},}\ because \textsf{biblatex's} sorting
-algorithms and automatic creation of the \textsf{extrayear} field
+algorithms and automatic creation of the \textsf{extradate} field
refer by default to the \textsf{date} before the \textsf{origdate}
when both are present, there may be situations when you need to have
the \emph{earlier} year in the \textsf{date} field, and the later one
@@ -11331,14 +14785,12 @@

\begin{description}
\item[\qquad off:] This is the default.  The citation will look like
-  (Smith 1926a).  This style is no longer recommended by the 16th
-  edition of the \emph{Manual}.
+  (Smith 1926a).  This style is no longer recommended by the
+  \emph{Manual}.
\item[\qquad both:] The citation will look like (Smith [1926a] 1985).
-  The 15th-edition options \texttt{old} and \texttt{new} are synonyms
-  for this.
+  The old options \texttt{old} and \texttt{new} are synonyms for this.
\item[\qquad on:] The citation will look like (Smith 1926a).  As noted
-  above, this style is no longer recommended by the 16th edition of
-  the \emph{Manual}.
+  above, this style is no longer recommended by the \emph{Manual}.
\end{description}

If, \mymarginpar{\texttt{switchdates}} for any reason, simply
@@ -11352,8 +14804,8 @@
of the \textbf{date} field to which I referred just above, at the
preamble \texttt{cmsdate} documentation in
section~\ref{sec:authuseropts}, and also at
-\textsf{cms-dates-sample.pdf} and \textsf{dates-test.bib} for examples
-of how all this works.
+\href{file:cms-dates-sample.pdf}{\textsf{cms-dates-sample.pdf}} and
+\textsf{dates-test.bib} for examples of how all this works.

\mylittlespace Bertold Schweitzer has brought to my attention certain
difficult corner cases involving cross-referenced works with more than
@@ -11362,19 +14814,19 @@
and \texttt{cmsdate=both} work.  If, and only if, a work has only one
date, and there is no \texttt{switchdates} in the \textsf{options}
field, then \texttt{cmsdate=on} and \texttt{cmsdate=both} will both
-result in the suppression of the \textsf{extrayear} field in that
+result in the suppression of the \textsf{extradate} field in that
entry.  Obviously, if the same options are set in the preamble, this
behavior is turned off, so that single-date entries will still work
properly without manual intervention.

-\mylittlespace The 16th edition of the \emph{Manual} now specifies
-that it is \enquote{usually sufficient to cite newspaper and magazine
-  articles entirely within the text} (15.47).  This will apply mainly
-to \textsf{article} and \textsf{review} entries with
+\mylittlespace Recent editions of the \emph{Manual} specify that it is
+\enquote{usually sufficient to cite newspaper and magazine articles
+  entirely within the text} (15.49).  This will apply mainly to
+\textsf{article} and \textsf{review} entries with
\textsf{entrysubtype} \texttt{magazine}, and involves a parenthetical
citation giving the \textsf{journaltitle} and then the full
\textsf{date}, not just the year, with any other relevant identifying
-information incorporated into running text.  (Cf.\ 14.206.)\ In order
+information incorporated into running text.  (Cf.\ 14.198.)\ In order
to facilitate this, I have added a further switch to the
\texttt{cmsdate} option \mymarginpar{\texttt{cmsdate=full}} ---
\texttt{full} --- which \emph{only} affects the presentation of
@@ -11398,17 +14850,17 @@
of which you put in the options to the \cmd{usepackage} command.  With
early versions of \textsf{biblatex-chicago}, the standard way of
-\begin{quote}
-  \cmd{usepackage[style=chicago-authordate,strict,backend=biber,\%\\
-    babel=other,bibencoding=inputenc]\{biblatex\}}
-\end{quote}
+\begin{verbatim}
+  \usepackage[style=chicago-authordate,strict,backend=biber,%
+    babel=other,bibencoding=inputenc]{biblatex}
+\end{verbatim}
Now, the default way to load the style, and one that will in the
vast majority of standard cases produce the same results as the old
invocation, will look like this:
-\begin{quote}
-  \cmd{usepackage[authordate,strict,backend=biber,autolang=other,\%\\
-    bibencoding=inputenc]\{biblatex-chicago\}}
-\end{quote}
+\begin{verbatim}
+  \usepackage[authordate,strict,backend=biber,autolang=other,%
+    bibencoding=inputenc]{biblatex-chicago}
+\end{verbatim}

If you read through \textsf{biblatex-chicago.sty}, you'll see that it
sets a number of \textsf{biblatex} options aimed at following the
@@ -11430,12 +14882,16 @@
You'll lose all the definitions in \textsf{biblatex-chicago.sty},
including those to which I've already alluded and also the code that
sets the note number in-line rather than superscript in endnotes or
-footnotes.  Also in this file is the code that calls all of the
-package's localization files, which means that you'll lose all the
-Chicago-specific bibstrings I've defined unless you provide, in your
-preamble, a \cmd{DeclareLanguageMapping} command, or several, adapted
-for your setup, on which see section~\ref{sec:international} below and
-also \xA7\xA7~4.9.1 and 4.11.8 in \textsf{biblatex.pdf}.
+footnotes, the URL line-breaking code, and the Chicago-specific
+number- and date-range compression code.  You'll need to load the
+required packages \textsf{xstring} and \textsf{nameref} yourself, as
+\textsf{biblatex} doesn't do it for you.  Also in this file is the
+code that calls all of the package's localization files, which means
+that you'll lose all the Chicago-specific bibstrings I've defined
+unless you provide, in your preamble, a \cmd{DeclareLanguageMapping}
+section~\ref{sec:international} below and also \xA7\xA7~4.9.1 and 4.11.8 in
+\textsf{biblatex.pdf}.

\mylittlespace What you \emph{will not} lose is the ability to call
the package options \texttt{annotation, strict, cmslos=false} and
@@ -11455,14 +14911,13 @@
variants) will no longer provide all the required features.  This
document assumes that you are using \textsf{Biber}; if you wish to
continue using \textsc{Bib}\TeX\ then you need \textsf{biblatex}
-version 1.4c and, if you have any problems with the current release,
-possibly \textsf{biblatex-chicago} 0.9.7a.
+version 1.4c and \textsf{biblatex-chicago} 0.9.7a.

\mylittlespace If your .bib file contains a large number of entries
with more than three authors, then you may run into some limitations
of the \textsf{biblatex-chicago} code.  The default settings are
\texttt{maxnames=3,minnames=1} in citations and
-\texttt{max\-bibnames=10,minbibnames=7} in the list of references.  In
+\texttt{maxbibnames=10,minbibnames=7} in the list of references.  In
practice, this means that an entry like hlatky:hrt, with 5 authors,
will present all of them in the list of references but will truncate
to one in citations, like so: (Hlatky et al. 2002).  For the vast
@@ -11471,7 +14926,7 @@
list includes another work of the same date that would also be
abbreviated as [\enquote{Hlatky et al.}] but whose coauthors are
different persons or listed in a different order, the text citations
-  must distinguish between them} (15.28).  The (\textsf{Biber}-only)
+  must distinguish between them} (15.29).  The (\textsf{Biber}-only)
\textsf{biblatex} option \texttt{uniquelist}, set for you in
\textsf{biblatex-chicago.sty}, will automatically handle many of these
situations for you, but it is as well to understand that it does so by
@@ -11516,8 +14971,6 @@
data-rich citations, but there may be instances where you can save
yourself some typing by keeping it simple.

-% %\enlargethispage{\baselineskip}
-
\mylittlespace Scot Becker has pointed out to me that the inverse
problem not only exists but may well become increasingly common, to
wit, .bib database entries generated by bibliographic managers which
@@ -11532,14 +14985,8 @@
option to excise with one command all the fields under consideration

-\mylittlespace Finally, allow me to reiterate what
-\textsf{biblatex.pdf} says, to wit, if you aren't going to use
-\textsf{Biber}, use \textsf{bibtex8}, rather than standard
-\textsc{Bib}\TeX, and avoid the cryptic errors that ensue when your
-.bib file gets to a certain size.
-
-\section{The \mycolor{\textsf{Jurisdiction}},
-  \mycolor{\textsf{Legislation}}, and \mycolor{\textsf{Legal}} Entry
+\section{The \textsf{Jurisdiction},
+  \textsf{Legislation}, and \textsf{Legal} Entry
Types}
\label{sec:legal}

@@ -11546,25 +14993,24 @@
I have received numerous requests over the years to include some means
of referring to legal and public documents which, broadly speaking,
don't fit easily into any of the standard \textsf{biblatex} entry
-types.  The \emph{Manual} (14.281--317) recommends using the
+types.  The \emph{Manual} (14.269--305) recommends using the
\emph{Bluebook} as a guide for formatting such references, while also
suggesting certain modifications to this formatting to bring it more
into line with Chicago's usual practices.  \textsf{Biblatex-chicago}
-now offers three entry types --- \mycolor{\textbf{jurisdiction}},
-\mycolor{\textbf{legal}}, and \mycolor{\textbf{legislation}} --- which
-allow you to present at least a substantial subset of what the
-\emph{Bluebook} offers.  As the rules for your .bib entries are the
-same in the notes \&\ bibliography style and in the author-date
-styles, and as these rules mainly come from a source outside the
-\emph{Manual,} and additionally as these rules apparently require even
-the author-date styles to use a system of foot- or endnotes (15.54), I
-have documented these types in a section of their own, applicable to
-all the Chicago styles.  (Some few changes needed when using the
-author-date styles, mainly to do with citation commands, will be
-outlined at the end.)  You can also consult the example files
-\mycolor{\textsf{legal-test.bib}} and
-\mycolor{\textsf{cms-legal-sample.pdf}} to see how you might construct
+now offers three entry types --- \textbf{jurisdiction},
+\textbf{legal}, and \textbf{legislation} --- which allow you to
+present at least a substantial subset of what the \emph{Bluebook}
+offers.  As the rules for your .bib entries are the same in the notes
+\&\ bibliography style and in the author-date styles, and as these
+rules mainly come from a source outside the \emph{Manual,} and
+additionally as these rules apparently require even the author-date
+styles to use a system of foot- or endnotes (15.58), I have documented
+these types in a section of their own, applicable to all the Chicago
+styles.  (Some few changes needed when using the author-date styles,
+mainly to do with citation commands, will be outlined at the end.)
+You can also consult the example files \textsf{legal-test.bib} and
+\href{file:cms-legal-sample.pdf}{\textsf{cms-legal-sample.pdf}} to see
+how you might construct your database entries.

\subsection{Types, Subtypes, and Fields}
\label{sec:legal:types}
@@ -11582,7 +15028,7 @@
\textsf{biblatex-chicago} excludes these types from the latter, though
you can control this using an option (see below).

-\mybigspace This \colmarginpar{\textbf{jurisdiction}} type is for
+\mybigspace This \mymarginpar{\textbf{jurisdiction}} type is for
presenting legal cases and court decisions.  A typical entry will
contain the following fields:

@@ -11598,9 +15044,10 @@
either in the \textsf{journaltitle} or in the \textsf{shortjournal}
field.  If you wish to present your readers with a list of
abbreviations with their expansions, then the expansion goes in
-  \textsf{journaltitle} and the abbreviation in
-  \textsf{shortjournal}.  (Cf.\
-  \mycolor{\textsf{cms-legal-sample.pdf}} to see how this might look.)
+  \textsf{journaltitle} and the abbreviation in \textsf{shortjournal}.
+  (Cf.\
+  \href{file:cms-legal-sample.pdf}{\textsf{cms-legal-sample.pdf}} to
+  see how this might look.)
\item[pages \emph{or} issue] When using a standard official reporter,
this will contain the opening page of the decision in that reporter,
while any \textsf{postnote} field will contain the specific page on
@@ -11632,25 +15079,24 @@
uk:case:square).
\end{description}}

-These are, so to speak, the basic elements of a
-\mycolor{\textsf{jurisdiction}} citation, which may, depending on
-specific circumstances, require supplementation by the following:
+These are, so to speak, the basic elements of a \textsf{jurisdiction}
+citation, which may, depending on specific circumstances, require
+supplementation by the following:

\begin{description}
\setlength{\parskip}{-2pt}
-\item[entrysubtype\{\mycolor{square}\} \textrm{or}
-  \{\mycolor{round}\}] The \emph{Manual} includes examples for citing
-  cases in Canada and in the United Kingdom, and the \texttt{square}
-  \textsf{entrysubtype} identifies the reporter either as Canadian or
-  as a UK reporter for which the year is essential to locating the
-  case, that is, when \enquote{there is either no volume number or the
-    volumes for each year are numbered anew, not cumulatively}
-  (14.310).  The \texttt{round} subtype, by contrast, identifies a UK
-  reporter where the volumes are numbered cumulatively, making the
-  year inessential.  (The names refer to the shapes of the brackets
-  placed around the year in each case.  Cf.\ canada:case,
-  uk:case:round, and uk:case:square.)
+\item[entrysubtype\{square\} \textrm{or} \{round\}] The \emph{Manual}
+  includes examples for citing cases in Canada and in the United
+  Kingdom, and the \texttt{square} \textsf{entrysubtype} identifies
+  the reporter either as Canadian or as a UK reporter for which the
+  year is essential to locating the case, that is, when \enquote{there
+    is either no volume number or the volumes for each year are
+    numbered anew, not cumulatively} (14.298).  The \texttt{round}
+  subtype, by contrast, identifies a UK reporter where the volumes are
+  numbered cumulatively, making the year inessential.  (The names
+  refer to the shapes of the brackets placed around the year in each
+  case.  Cf.\ canada:case, uk:case:round, and uk:case:square.)
\item[origlocation \textrm{or} origpublisher] If you need to cite more
than one reporter for a given case, then there are two
possibilities.  Either the second (and subsequent) reporter(s)
@@ -11666,19 +15112,19 @@
\textsf{relatedstring} field.  (Cf.\ federal:lower:related.)
\end{description}}

-This \colmarginpar{\textbf{legislation}} is the most complicated of
+This \mymarginpar{\textbf{legislation}} is the most complicated of
the new entry types, with several \textsf{entrysubtypes} and a number
of tricky corners, particularly with regard to the provision of
subsequent short notes after the first full citation.  It is intended
to cope with constitutions and with legislative and executive
documents of all kinds, with the exception of treaties, for which you
-can use the \mycolor{\textsf{legal}} type, below.  In effect, the type
-tries to cover federal, state, and municipal laws and ordinances,
-statutes, bills, resolutions, reports, debates, hearings, presidential
-and congressional documents, and constitutions, none of which it does
-with particular elegance, so consider it a work in progress.  Many of
-the fields have close analogues in the \textsf{jurisdiction} type, so
-at least there is some bare minimum of consistency when dealing with
+can use the \textsf{legal} type, below.  In effect, the type tries to
+cover federal, state, and municipal laws and ordinances, statutes,
+bills, resolutions, reports, debates, hearings, presidential and
+congressional documents, and constitutions, none of which it does with
+particular elegance, so consider it a work in progress.  Many of the
+fields have close analogues in the \textsf{jurisdiction} type, so at
+least there is some bare minimum of consistency when dealing with
public and legal material.

@@ -11691,8 +15137,8 @@
\textsf{title} which, please note, quite frequently will not turn up
in short notes, depending on which other fields are present.
\item[titleaddon] This field is considerably more important in
-  \mycolor{\textsf{legislation}} entries than the \textsf{shorttitle}
-  field, mainly because it will turn up in many short notes where the
+  \textsf{legislation} entries than the \textsf{shorttitle} field,
+  mainly because it will turn up in many short notes where the
\textsf{title} will not.  It will frequently contain specifying
information on legislative material, and will therefore often allow
short notes to differentiate citations of sources that might have
@@ -11706,15 +15152,16 @@
congress:publiclaw.)
\item[journaltitle \textrm{and/or} shortjournal] There is usually a
standard place for publishing various sorts of legislative material,
-  and as in \mycolor{\textsf{jurisdiction}} entries it is
-  \emph{always} presented in a standard abbreviated form available in
-  the \emph{Bluebook}.  You can place the abbreviation either in the
+  and as in \textsf{jurisdiction} entries it is \emph{always}
+  presented in a standard abbreviated form available in the
+  \emph{Bluebook}.  You can place the abbreviation either in the
\textsf{journaltitle} or in the \textsf{shortjournal} field.  If you
wish to present your readers with a list of abbreviations with their
expansions, then the expansion goes in \textsf{journaltitle} and the
this field will often appear in short notes.  (Cf.\
-  \mycolor{\textsf{cms-legal-sample.pdf}} to see how this might look.)
+  \href{file:cms-legal-sample.pdf}{\textsf{cms-legal-sample.pdf}} to
+  see how this might look.)
\item[volume] The volume number of the \textsf{shortjournal}.  It can
be a cardinal or an ordinal, depending on the \textsf{shortjournal}.
(Cf.\ congress:publiclaw and congress:bill.)
@@ -11721,17 +15168,16 @@
\item[series] In citations of American material, this will usually
contain session information pertaining to a legislative publication.
Elsewhere it will often contain just be a plain number, not unlike
-  in \mycolor{\textsf{jurisdiction}} entries.  (Cf.\
-  congress:debate:globe, state:statute:okla, and uk:hansard.)
+  in \textsf{jurisdiction} entries.  (Cf.\ congress:debate:globe,
+  state:statute:okla, and uk:hansard.)
\item[issue] This field can provide an identifying number in some
circumstances, particularly when you don't want it prefixed by any
bibstring --- cf.\ uk:command.
-\item[pages] Somewhat similar to its use in
-  \mycolor{\textsf{jurisdiction}} entries, this will usually contain
-  the opening page, or sometimes the section number, of the material
-  in the \textsf{shortjournal}, while any \textsf{postnote} field will
-  contain the specific page on which a particular citation appears (a
-  \enquote{pincite}).
+\item[pages] Somewhat similar to its use in \textsf{jurisdiction}
+  entries, this will usually contain the opening page, or sometimes
+  the section number, of the material in the \textsf{shortjournal},
+  while any \textsf{postnote} field will contain the specific page on
+  which a particular citation appears (a \enquote{pincite}).
\item[part \textrm{or} chapter] Some sources use \textsf{part} or
\textsf{chapter} numbers instead of \textsf{pages} or sections.
@@ -11755,10 +15201,10 @@
congress:debate:new, congress:hearing, state:statute:ky, and
uk:statute.)
\item[entrysubtype] The sheer variety of sources included under the
-  \mycolor{\textsf{legislation}} type, and the specialized rules for
-  presenting them, have necessitated the introduction of a substantial
-  network of \textsf{entrysubtypes}:
+  \textsf{legislation} type, and the specialized rules for presenting
+  them, have necessitated the introduction of a substantial network of
+  \textsf{entrysubtypes}:
\begin{description}
\setlength{\parskip}{-2pt}
@@ -11777,15 +15223,14 @@
\end{description}}
\end{description}}

-A glance through the \mycolor{\textsf{legal-test.bib}} file should
-help enormously when you're trying to work out how to present a
-particular source, and all suggestions for pruning the foliage will be
-welcome.
+A glance through the \textsf{legal-test.bib} file should help
+enormously when you're trying to work out how to present a particular
+source, and all suggestions for pruning the foliage will be welcome.

-\mybigspace This \colmarginpar{\textbf{legal}} type is intended as a
+\mybigspace This \mymarginpar{\textbf{legal}} type is intended as a
catch-all for miscellaneous public documents not included in the
previous two types, but for the moment the only sort of material for
-which it is required is international treaties (14.302; treaty).  The
+which it is required is international treaties (14.290; treaty).  The
usual fields for such material include:

@@ -11804,7 +15249,8 @@
with a list of abbreviations with their expansions, then the
expansion goes in \textsf{journaltitle} and the abbreviation in
\textsf{shortjournal}.  (Cf.\
-  \mycolor{\textsf{cms-legal-sample.pdf}} to see how this might look.)
+  \href{file:cms-legal-sample.pdf}{\textsf{cms-legal-sample.pdf}} to
+  see how this might look.)
\item[issue] This will contain the identifying number provided by the
\textsf{shortjournal}.
\item[volume] The volume number of the \textsf{shortjournal}.
@@ -11827,10 +15273,16 @@
separate set of notes in addition to the standard author-year
citations, which means that for these three legal entry types you'll
have to remember to use new citation commands that I've provided:
-\mycolor{\cmd{fullcite}}, \mycolor{\cmd{footfullcite}}, and
-\mycolor{\cmd{parenfullcite}}.  The first prints the reference, the
-second does so in a footnote, and the third does so inside
-parentheses.
+\cmd{fullcite}, \cmd{footfullcite}, and \cmd{parenfullcite}.  The
+first prints the reference, the second does so in a footnote, and the
+third does so inside parentheses.  For both styles,
+\colmarginpar{\cmd{runcite}} there is a new command that you should
+use if you are citing a \textsf{jurisdiction} entry in the running
+flow of text rather than as a stand-alone citation, whether that text
+is in a note or in the main body (14.276).  This requires a different
+presentation of the \textsf{title} field, and using
+circumstance.

\subsection{Options}
\label{sec:legal:options}
@@ -11839,7 +15291,7 @@
notes in your document.  The default settings are indicated in the
margins.

-\mylittlespace This \colmarginpar{legalnotes=true} option prevents the
+\mylittlespace This \mymarginpar{legalnotes=true} option prevents the
printing of legal citations in a bibliography or reference list, as
the \emph{Bluebook} recommends.  You can change this to \texttt{false}
in the preamble of your document, but you should be aware that the
@@ -11846,7 +15298,7 @@
reference printed in the bibliography will be a clone of the long-note
form, as the \emph{Bluebook} doesn't provide an alternative version.

-\mylittlespace This \colmarginpar{noneshort=false} option controls the
+\mylittlespace This \mymarginpar{noneshort=false} option controls the
availability of the short form of the note, intended for use in
subsequent citations of entries already presented in full notes.  By
default, \textsf{biblatex-chicago} attempts to provide
@@ -11855,7 +15307,7 @@
partially designed to cope with the complexities of the specification.
The \emph{Manual}, for its part, suggests that \enquote{works that
cite only a few legal documents may be better off using the full
-  form for each citation} (14.287).  In the author-date styles, you
+  form for each citation} (14.275).  In the author-date styles, you
can set this option to \texttt{true} either in the preamble or in
individual .bib entries to accomplish this.  Assuming you've only used
the \cmd{fullcite} commands for the \emph{Bluebook} entry types, the
@@ -11870,7 +15322,7 @@
results in the presence of \textsf{shorthand} fields and/or the
\texttt{shorthandfirst} and \texttt{short} options.

-\mylittlespace I \colmarginpar{short=false} have ported this option,
+\mylittlespace I \mymarginpar{short=false} have ported this option,
already present in the notes \&\ bibliography style, to the
author-date styles to allow users to present short notes from the very
first citation.  I'm not certain what the use case might be for this,
@@ -11878,7 +15330,7 @@
point to references in a full bibliography.  Still, if for any reason
you need this you can set the option to \texttt{true} in the preamble.

-\mylittlespace This \colmarginpar{supranotes=\\true} is a
+\mylittlespace This \mymarginpar{supranotes=\\true} is a
\emph{Bluebook}-specific option, and it produces, for some entry types
and subtypes, a back reference to the first, long note at the end of
subsequent, short citations.  It takes the form \enquote{\emph{supra}
@@ -11898,14 +15350,14 @@
for producing a Chicago-like style in other languages.  I have
supplied three lbx files, \textsf{cms-german.lbx}, its clone
\textsf{cms-ngerman.lbx}, and \textsf{cms-french.lbx}, in at least
-partial fulfillment of this request.  For this release, Gustavo Barros
-has very kindly provided \textsf{cms-brazilian.lbx} for speakers of
-that language, thereby adding to the generous contributions of Stefan
+partial fulfillment of this request.  For this release Wouter Lancee
+has provided \textsf{cms-dutch.lbx}, thereby adding to the generous
+contributions of Gustavo Barros (\textsf{cms-brazilian.lbx}), Stefan
Bj\xF6rk (\textsf{cms-swedish.lbx}), Antti-Juhani Kaijahano
(\textsf{cms-finnish.lbx}), Baldur Kristinsson
(\textsf{cms-icelandic.lbx}), and H\xE5kon Malmedal
-(\textsf{cms-norsk.lbx}, \textsf{cms-norwe\-gian.lbx}, and
-\textsf{cms-nynorsk.lbx}).  I include \textsf{cms-british.lbx} in
+(\textsf{cms-norsk.lbx}, \textsf{cms-norwegian.lbx}, and
+\textsf{cms-ny\-norsk.lbx}).  I include \textsf{cms-british.lbx} in
order to simplify and to improve the package's handling of
non-American typographical conventions in English.  This means that
all --- or at least most --- of the Chicago-specific bibstrings are
@@ -11931,7 +15383,7 @@
\item Do not load \textsf{babel} at all.
\end{enumerate}
(This last is a change from the \textsf{biblatex} defaults --- cp.\
-\xA7~3.10.1 in \textsf{biblatex.pdf} --- but it seems to me reasonable,
+\xA7~3.12.2 in \textsf{biblatex.pdf} --- but it seems to me reasonable,
in an American citation style, to expect this arrangement to work well
for the majority of users.)

@@ -11943,25 +15395,24 @@
the \texttt{british} option.

-\mylittlespace If you want to use Brazilian Portuguese, Finnish,
-French, German, Icelandic, Norwegian, or Swedish strings in the
-reference apparatus, then you can load \textsf{babel} with
-\texttt{brazilian}, \texttt{finnish}, \texttt{french},
+\mylittlespace If you want to use Brazilian Portuguese, Dutch,
+Finnish, French, German, Icelandic, Norwegian, or Swedish strings in
+the reference apparatus, then you can load \textsf{babel} with
+\texttt{brazilian}, \texttt{dutch}, \texttt{finnish}, \texttt{french},
\texttt{german}, \texttt{icelandic}, \texttt{ngerman}, \texttt{norsk},
\texttt{nynorsk}, or \texttt{swedish} as the main document language.
You no longer need any calls to \cmd{DeclareLanguageMapping} in your
-document preamble, since \textsf{bib\-latex-chicago.sty} automatically
+document preamble, since \textsf{biblatex-chicago.sty} automatically
provides these if you load the package in the standard way.

\mylittlespace You can also define which bibstrings to use on an
entry-by-entry basis by using the \textsf{hyphenation} field in your
-bib file, but you will have to make sure that the Chicago-specific
-strings for the given language are loaded using a
-\cmd{DeclareLanguageMapping} call in the preamble.  Indeed, if
-need \cmd{DeclareLanguageMapping\break\{american\}\{cms-american\}} in
+bib file, but you will have to make sure that all the languages you
+want to use in this way are included in the call to load
+\textsf{babel} in your preamble, even if not as the main text
+language.  The \cmd{DeclareLanguageMapping} calls in
+\textsf{biblatex-chicago.sty} should do the rest, assuming you've

\mylittlespace Three other hints may be in order here.  Please note,
first, that I haven't altered the standard punctuation procedures used
@@ -11972,10 +15423,10 @@
quotation marks, then you'll need a declaration of this sort in your
preamble:

-\begin{quote}
-  \cmd{DefineBibliographyExtras\{german\}\{\%}\\
-  \hspace*{2em}\cmd{DeclareQuotePunctuation\{.,\}\}}
-\end{quote}
+\begin{verbatim}
+  \DefineBibliographyExtras{german}{%
+    \DeclareQuotePunctuation{.,}}
+\end{verbatim}

Second, depending on the nature of your bibliography database, it will
only rarely be possible to process the same bib file in different
@@ -11999,10 +15450,10 @@
provided may well break with established bibliographical traditions in
those languages, but my main concern when choosing them was to remain
as close as possible to the quirks of the Chicago specification.  I
-have entirely relied on the judgment of the creators of the Finnish,
-Icelandic, Norwegian, and Swedish localizations in those instances.
-If you have strong objections to any of the strings, or indeed to any
-of my formatting decisions, please let me know.
+have entirely relied on the judgment of the creators of the Brazilian,
+Dutch, Finnish, Icelandic, Norwegian, and Swedish localizations in
+those instances.  If you have strong objections to any of the strings,
+or indeed to any of my formatting decisions, please let me know.

\section{One\,.bib Database, Two Chicago Styles}
\label{sec:twostyles}
@@ -12010,7 +15461,7 @@
I have, when designing this package, attempted to keep at least half
an eye on the possibility that users might want to re-use a .bib
database in documents using the two different Chicago styles.  The
-extensive unification of the two styles in the 16th edition of the
+extensive unification of the two styles in recent editions of the
\emph{Manual} has simplified things, and though I have no idea whether
this will even be a common concern, I still thought I might gather in
this section the issues that a hypothetical user might face.  The two
@@ -12071,7 +15522,7 @@
in section~\ref{sec:formatting:authdate} above may help.
\item You also need to be more careful about the use of abbreviations,
e.g., in journal names, where the author-date style is more liberal
-  in their use than the notes \&\ bibliography style.  (Cf.\ 14.179.)
+  in their use than the notes \&\ bibliography style.  (Cf.\ 14.170.)
The bibstrings mechanism and package options sort much of this out
automatically, but not all.
\item The \textsf{shorttitle} field is used extensively in notes \&\
@@ -12100,10 +15551,13 @@
\label{sec:otherpacks}

For \mymarginpar{\textbf{endnotes}} users of the \textsf{endnotes}
-package --- or of \textsf{pagenote} --- \textsf{biblatex} 0.9 offers
-RELEASE file and the documentation of the \texttt{notetype} option in
-\textsf{biblatex.pdf} \xA7~3.1.2.1.
+package --- or of \textsf{pagenote} --- \textsf{biblatex} offers
+\texttt{notetype} option in \textsf{biblatex.pdf} \xA7~3.1.2.1.  If you
+are using the \mycolor{\texttt{noteref}} option with the notes \&\
+documentation in section~\ref{sec:endnoterefs} for your options, which
+include the \mycolor{\textsf{cmsendnotes.sty}} package.

\mylittlespace Another \mymarginpar{\textbf{memoir}} problem I have
found occurs because the \textsf{memoir} class provides its own
@@ -12114,45 +15568,28 @@
package may well have their own ideas about such formatting.

\mylittlespace The \mymarginpar{\textbf{ragged2e}} footnote mark code
-I've just mentioned also causes problems for the \textsf{rag\-ged2e}
+I've just mentioned also causes problems for the \textsf{ragged2e}
package, but in this case a simple workaround is to load
\textsf{biblatex} \emph{after} you've loaded \textsf{ragged2e} in your
-document preamble.
+document preamble.  The URL line-breaking code activated by
+\mycolor{\texttt{cmsbreakurl}} doesn't play well with

-%\enlargethispage{\baselineskip}
-
-me to problems that appeared when he used the Xe\LaTeX\ engine to
-process his files.  These included spurious punctuation after
-quotation marks in some situations, and also failures in the automatic
-capitalization routines.  Some of these problems disappeared when I
-switched to using \textsf{biblatex's} punctuation-tracking code for
-\enquote{American} styles, but some remained.  A bug report from
-J.~P.~E.~Harper-Scott suggested a new way of addressing the issue, and
-newer versions of Lehman's \textsf{csquotes} package incorporate a
-full fix.  This, thankfully, doesn't require turning off any of
-Xe\LaTeX 's features, and indeed merely involves upgrading to the
-case.  Compatibility with the EU1 encoding is now standard in that
-package.
-
\section{TODO \&\ Known Bugs}
\label{sec:bugs}

-This release implements the 16th edition of the \emph{Chicago Manual
-  of Style}.  It also contains a version of the author-date style
+This release implements the 17th edition of the \emph{Chicago Manual
+  of Style}.  It contains a version of the author-date style
alongside the \textsf{authordate} code which unifies the treatment of
titles between itself and the notes \&\ bibliography style.  I
strongly encourage users to migrate to one of the styles implementing
the most recent specification, as I am focusing all of my development
-and testing time there.  With the current release I am removing the
-15th-edition styles, long obsolete, in preparation for the move to the
-17th edition in the next feature release.
+and testing time there.

\mylittlespace Regardless of which edition you are considering, there
-remain things I haven't implemented.  The solution in brown:bre\-mer
-to multi-part journal articles obviously isn't optimal, and I should
+remain things I haven't implemented.  The solution in brown:bremer to
+multi-part journal articles obviously isn't optimal, and I should
investigate a way of making it simpler.  If the kludge presented there
doesn't appeal, you can always, for the time being, refer separately
to the various parts.  If you have other issues with particular sorts
@@ -12162,12 +15599,6 @@
address the vast majority of them.  If this optimism proves misguided,

-\mylittlespace I haven't yet explored the possible uses in
-\textsf{biblatex-chicago} for the \textsf{biblatex}
-\textsf{datelabelsource} field, new in \textsf{biblatex} 2.8, nor have
-I implemented automatic compression of date ranges to go along with
-that provided for page ranges.
-
\mylittlespace Kenneth L. Pearce has reported a bug that appears when
using multiple citation commands inside the \textsf{annotation} field
of annotated bibliographies.  If you run into this problem, he
@@ -12184,8 +15615,6 @@
set of curly braces \{\}\ at the start of the field, but I shall look
into this further.

-%\enlargethispage{-4\baselineskip}
-
\mylittlespace This release fixes the formatting errors of which I am
aware.  There remain the larger issues I've discussed throughout this
documentation, which mainly represent my inability to make all of
@@ -12199,10 +15628,361 @@
\section{Revision History}
\label{sec:history}

-\textbf{1.0rc5: Released \today}
+\textbf{2.0: Released \today}

-\mylittlespace Obsolete and Deprecated Features:\label{deprec:obsol}
+\mylittlespace Converting from the 16th to the 17th edition in your
+.bib files and \LaTeX\ documents:\label{deprec:obsol}
\begin{itemize}
+\item The 17th edition of the \emph{Manual} no longer encourages use
+  of \emph{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 \emph{ibid.}\ in that style, you need to set the new
+  \textsf{biblatex} and the \texttt{style=} option instead of with
+  \textsf{biblatex-chicago}, please be aware that there are two
+  standard packages required by \textsf{biblatex-chicago} that aren't
+  \mycolor{\textsf{xstring}} and \mycolor{\textsf{refname}}.  You'll
+\item If you've been using the \textsf{year} field to present decades
+  like \texttt{1950s}, this will no longer work accurately in
+  author-date citations.  The correct way to do so now is to use one
+  of \textsf{biblatex's} \textsc{iso}8601-2 date specifications in the
+  \textsf{date} field instead, to wit, \texttt{195X}.  Generally, I've
+  tried to make \textsf{year} fields like \texttt{[1957?]} or
+  \texttt{[ca.\ 1850]} continue to work properly, but here too the
+  best thing to do is to use the new \textsf{date} features and
+  present them like \texttt{1957?} or \texttt{1850\textasciitilde},
+  respectively.  This will ensure that both sorting and punctuation
+  work out properly.  See table~\ref{ad:date:extras}, and the
+  \textsf{date} docs in sections~\ref{sec:entryfields} and
+\item If you have been using the \textsf{nameaddon} field to hold time
+  stamps for online comments, then you should put the time stamp into
+  the \textsf{date} or possibly \textsf{eventdate} field, instead,
+  using the \textsc{iso}8601-2 format implemented by
+  \textsf{biblatex}.  See the \textsf{date} and \textsf{nameaddon}
+  field docs in sections~\ref{sec:entryfields} and
+  \ref{sec:fields:authdate}, along with tables~\ref{tab:online:types},
+\item Following on from the previous item, the 17th edition of the
+  \emph{Manual} includes more plentiful and more detailed instructions
+  for presenting online materials than were available in previous
+  editions.  For users of \textsf{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.
+  the new specifications for the notes \&\ bibliography and
+  author-date styles, respectively.  Cf.\ in particular the new
+  \mycolor{\texttt{commenton}} \textsf{relatedtype} in
+  sections~\ref{sec:related} and \ref{sec:authrelated}.  Also, the
+  \textbf{online} entry type now prints both \textsf{author} and
+  \textsf{editor} (or other editorial role) if they exist, and I've
+  moved the \textsf{addendum} field \emph{before} the \textsf{url},
+  which fits better with indications in the \emph{Manual}.  If you've
+  been using the \textsf{addendum} field to present citations of other
+  entries (as in older versions of \textsf{biblatex-chicago}), please
+  switch to the \textsf{related} mechanism, which works better anyway.
+\item On the same subject, if you are using the notes \&\ bibliography
+  style and are retaining the \textsf{crossref} field (instead of
+  using the \mycolor{\texttt{commenton}} \textsf{relatedtype}) in
+  \textsf{review} entries as a means of presenting comments on blogs,
+  such entries are now subject to the settings of the
+  \texttt{longcrossref} option and will appear in abbreviated form in
+  some full notes and in the bibliography, as has always occurred in
+  \textsf{incollection} entries, for example.  You can set
+  \texttt{longcrossref} to \texttt{true} to get back the old behavior.
+\item The 17th edition generally encourages more strongly than the
+  16th the use of only one publisher in the \textsf{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
+  \enquote{and} in the field.  Please see the documentation of the
+  field in sections~\ref{sec:entryfields} and
+  \ref{sec:fields:authdate}, above, for the rather minor (and rare)
+  changes this might mandate for your\ .bib files.
+\item The 17th-edition presentation of \textbf{music} entries has
+  added a few pieces of information it seems to find desirable ---
+  track number in \textsf{chapter} and specification of a lead
+  performer's role in, e.g., \textsf{editortype} --- though the basic
+  structure of a 16th-edition\ .bib entry remains unchanged.  Please
+  see the documentation of that entry type in
+  sections~\ref{sec:entrytypes} and \ref{sec:types:authdate}, above.
+\item The 17th edition has added a couple of wrinkles to the
+  \textbf{video} type specifications.  You can now put the broadcast
+  network of a TV show in the \textsf{usera} field, and you can also
+  supply the new \textsf{entrysubtype} \mycolor{\texttt{tvepisode}} to
+  print the series title (\textsf{booktitle}) \emph{before} the
+  episode title (\textsf{title}).  Please see the documentation of the
+  entry type in sections~\ref{sec:entrytypes} and
+  \ref{sec:types:authdate}, above.
+\item Both Chicago styles now sentence case the \textsf{title} field
+  in \textbf{patent} entries, so you may need to put curly braces
+  around words that shouldn't appear in lowercase.
+\item The \textsf{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 \textsf{addendum}
+  field might be of service.  The documentation in
+  sections~\ref{sec:entryfields} and \ref{sec:fields:authdate} should
+  help.
+\item \textsf{Biber} is now the \emph{required} backend for all
+  Chicago styles, including the 16th-edition files still included in
+  the package.  If you have somehow been using some variant of
+  \textsc{Bib}\TeX\ in the notes \&\ bibliography style up to now, I'm
+  fairly confident it will no longer work.  Please switch to
+  \textsf{biber}.
+\end{itemize}
+
+Other new features common to the notes \&\ bibliography and
+author-date styles:
+\begin{itemize}
+\item Wouter Lancee has very generously provided a Dutch localization
+  for \textsf{biblatex-chicago}, called
+  \mycolor{\textsf{cms-dutch.lbx}}.  You can use it by including
+  Barros has also very kindly provided a much-revised version of his
+  \textsf{cms-brazilian.lbx}.
+\item As mentioned above, this release for the first time implements
+  \textsf{biblatex's} elegant and long-standing support for the
+  \textsc{iso}8601-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~\ref{ad:date:extras} summarizes the implementation for all
+  sections~\ref{sec:entryfields} and \ref{sec:fields:authdate}, along
+  with the new package options \mycolor{\texttt{alwaysrange}},
+  \mycolor{\texttt{nodatebrackets}}, and
+  \mycolor{\texttt{noyearbrackets}}.
+\item I have also implemented year-range compression in all styles,
+  governed by the new \mycolor{\texttt{compressyears}} option, set to
+  \texttt{true} by default.
+\item 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 \emph{Manual} concedes that some publishers prefer
+  this style.  Some of \textsf{biblatex's} standard styles have a
+  \mycolor{\texttt{dashed}} option, so for compatibility purposes I've
+  provided the same.  By default, I have set it to \texttt{true} to
+  print the name dash, but you can set \mycolor{\texttt{dashed=false}}
+\item Jan David Hauck suggested I extend the field-exclusion
+  functionality beyond the package options already provided
+  (sections~\ref{sec:chicpreset} and \ref{sec:authpreset}) by
+  \textsf{biblatex-chicago}.  First, I made sure that all of those
+  options could be set globally, per type, and per entry.  Second, I
+  added the command \mycolor{\cmd{suppressbibfield}}, designed to
+  appear in the preamble, and which will look something like:
+\begin{verbatim}
+  \suppressbibfield[entrytype,entrytype,...]{field,field,field,...}
+\end{verbatim}
+  \ref{sec:formatting:authdate} for the details.
+\item After a request by user BenVB, I have added support for the
+  \textsf{biblatex} \mycolor{\textbf{shortseries}} field, which allows
+  you to present abbreviated \textsf{series} in book-like entries in
+  all the styles.  You can use the \mycolor{\texttt{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:
+  \mycolor{\textsf{shortseries}} in sections~\ref{sec:entryfields} and
+  \ref{sec:fields:authdate}.
+\item I have added a new preamble option,
+  \mycolor{\texttt{cmsbreakurl}}, which attempts to follow the
+  \emph{Manual's} instructions for line-breaking inside URLs.  It
+  doesn't work 100\%\ accurately, and it doesn't play well with the
+  \textsf{ragged2e} package, but in most circumstances it is at least
+  closer to the Chicago ideal than the \textsf{biblatex} defaults.
+  See sections~\ref{sec:useropts} and \ref{sec:authuseropts}.
+\item The \emph{Manual} now specifies how to present \textsf{articles}
+  with a unique numeric or alphanumeric ID, which you can place in the
+  \textsf{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.
+\item In \textsf{jurisdiction} entries, the presentation of the
+  \textsf{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 \mycolor{\cmd{runcite}} command, in both Chicago
+  styles, for \textsf{jurisdiction} citations that appear in running
+  text.
+\item N.\ Andrew Walsh suggested that I allow editorial roles that
+  aren't pre-defined \cmd{bibstrings} to appear as-is in entries, just
+  as the standard \textsf{biblatex} styles do.  I have followed this
+  advice for the \textsf{editortype}, \textsf{editoratype},
+  \textsf{editorbtype}, \textsf{editorctype}, and \textsf{nameatype}
+  fields, making sure to capitalize the string according to its
+  context.
+\item I have added the \textsf{venue} field to \textbf{misc} entries,
+  both with and without an \textsf{entrysubtype}. It also appears in
+  the new \mycolor{\textbf{performance}} type.
+\item I have added the \textsf{version} and \textsf{type} fields to
+  \textbf{book} entries to help with multimedia app content (14.268).
+  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 \textsf{type} field to
+  \textbf{article}, \textbf{review}, and \textbf{online} entries for
+  presenting medium information for online multimedia (14.267).
+\item I have added a new entry type, \mycolor{\textbf{dataset}}, to
+  allow the citation of scientific databases.  Cf.\
+  sections~\ref{sec:entrytypes} and \ref{sec:types:authdate}.
+\item I have added the \textsf{number} field to \textbf{misc} entries
+  with an \textsf{entrysubtype} to help cope with the varieties of
+  location information in different archives.
+\item The new entry type \mycolor{\textbf{standard}} is now available
+  organizations.  If you have been using the \textsf{book} type for
+  such material it might be worth switching to make sure your entries
+  are more in line with the \emph{Manual's} specifications.  See the
+  docs in sections~\ref{sec:entrytypes} and \ref{sec:types:authdate}
+  for the details.
+\item The new entry type \mycolor{\textbf{performance}} is now
+  available for citing live performances.  You can sometimes also use
+  a \textbf{misc} entry without an \textsf{entrysubtype}.
+\item I have added the \textsf{eventdate} field to the \textbf{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~\ref{sec:entrytypes} and
+  \ref{sec:types:authdate}, above.
+\item I have added the \textsf{origdate}, \textsf{eventdate},
+  \textsf{userd}, and \textsf{howpublished} fields to the
+  \textbf{artwork} and \textbf{image} entry types, in response to
+  additional information given in some of the \emph{Manual's}
+  examples.  Please see the documentation of \textbf{artwork} in
+  sections~\ref{sec:entrytypes} and \ref{sec:types:authdate}, above.
+\item I have added the \textsf{maintitle}, \textsf{mainsubtitle}, and
+  \textsf{maintitleaddon} fields to the \textbf{article},
+  \textbf{periodical}, and \textbf{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
+  \textsf{biblatex} usage, but the need for two italicized titles
+  demanded something like it.
+\item I have added a new field-exclusion option,
+  \mycolor{\texttt{urlstamp}}, set to \texttt{true} by default, which
+  means that any time stamp associated with the \textsf{urldate} will
+  always be printed.  You can set it to \texttt{false} in the preamble
+  either for the whole document or for specific entry types, or in the
+  \textsf{options} field of individual entries.  See the docs in
+  sections~\ref{sec:chicpreset} and \ref{sec:authpreset}, above.
+\item The \textsf{howpublished} field has accumulated a series of new
+  functions in various entry types, bringing it far from its origins
+  in \textsf{booklet}, \textsf{misc}, and \textsf{unpublished}
+  entries.  Please see its documentation in
+  sections~\ref{sec:entryfields} and \ref{sec:fields:authdate}.
+\item In \textsf{inreference}, \textsf{mvreference}, and
+  \textsf{reference} entries \textsf{biblatex-chicago} no longer
+  considers any of the name fields (\textsf{author}, \textsf{editor},
+  etc.) for sorting purposes in the bibliography or reference list,
+  thus leaving the \textsf{title} as the first field to be considered.
+  This may simplify the creation of .bib database entries.
+\end{itemize}
+
+New notes \&\ bibliography features:
+\begin{itemize}
+\item In keeping with indications in the 17th edition of the
+  \emph{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 (\textsf{maintitle}) \emph{before} the title of
+  individual volumes of that series (\textsf{title} or
+  \textsf{booktitle}).  This involves the use of the new
+  \textsf{relatedtypes} \mycolor{\texttt{maintitle}} and
+  \mycolor{\texttt{maintitlenc}}, which may be used in
+  \textsf{bookinbook}, \textsf{inbook}, \textsf{incollection},
+  \textsf{inproceedings}, \textsf{letter}, \textsf{mvbook},
+  \textsf{mvcollection}, \textsf{mvproceedings}, and
+  \textsf{mvreference} entries.  Please see the detailed documentation
+  of this feature in section~\ref{sec:related}, s.v.\
+  \textsf{relatedtype} \mycolor{\texttt{maintitle}}.
+\item 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
+  \textsf{Manual}.  The feature is enabled with the
+  \mycolor{\texttt{noteref}} option, and there are several sub-options
+  to control where and what is printed:
+  \mycolor{\texttt{fullnoterefs}}, \mycolor{\texttt{noterefinterval}},
+  \mycolor{\texttt{noterefintro}}, \mycolor{\texttt{pagezeros}},
+  \mycolor{\texttt{hidezeros}}, and \mycolor{\texttt{endnotesplit}}.
+  The dependent package \mycolor{\textsf{cmsendnotes.sty}} can assist
+  if you use endnotes instead of footnotes in this context.  It too
+  has numerous options: \mycolor{\texttt{hyper}},
+  \mycolor{\texttt{blocknotes}}, \mycolor{\texttt{split}},
+  alongside the new commands \mycolor{\cmd{theendnotesbypart}} and
+  \mycolor{\cmd{cmsintrosection}}.  Four new citation commands
+  complete the provisions: \mycolor{\cmd{shortrefcite}},
+  \mycolor{\cmd{shorthandrefcite}}, \mycolor{\cmd{shortcite*}}, and
+  section~\ref{sec:noteref} for all the details, and also
+  \href{file:cms-noteref-demo.pdf}{\textsf{cms-noteref-demo.pdf}} for
+  a brief example and explanation of some of the functionality.
+\item I have ported, with modifications, the author-date package
+  option \mycolor{\texttt{nodates}} to the notes \&\ bibliography
+  style.  It is set to \texttt{true} by default.  In conjunction with
+  the \mycolor{\texttt{nodatebrackets}} and
+  \mycolor{\texttt{noyearbrackets}} options it provides an alternative
+  presentation of uncertain dates.  See section~\ref{sec:chicpreset}.
+\item Pursuant to a bug report by David Purton, I have recoded the
+  various \cmd{headlesscite} commands and included a new one,
+  \mycolor{\cmd{Headlesscite}}, which is the actually functional way
+  to enforce capitalization at the start of such a citation, should
+  you need to do so.
+\end{itemize}
+
+New author-date features:
+\begin{itemize}
+\item The \mycolor{\textbf{verbc}} field, which is standard but unused
+  in the styles included in \textsf{biblatex}, allows the user
+  fine-grained control over if and when an \textsf{extradate} letter
+  (1976\textbf{a}) will appear after the year in citations and the
+  list of references.  See its documentation in
+  section~\ref{sec:fields:authdate}.
+\item The new \mycolor{\texttt{authortitle}} type and entry option
+  allows you to provide author-title citations in the text instead of
+  author-date.  The \textsf{entrysubtype} value \texttt{classical}
+  does the same, but there may be cases where using such an
+  \textsf{entrysubtype} is impossible.  This is set to \texttt{true}
+  by default for \mycolor{\textbf{dataset}} entries.
+\item On the same subject, you can also use the new citation commands
+  \mycolor{\cmd{atcite}} and \mycolor{\cmd{atpcite}} to achieve the
+  same end.  The former prints a plain citation, the latter places it
+  in parentheses.
+\item In the default configuration, when you use a \textsf{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
+  \texttt{cmslos=false} in your preamble then this no longer applies,
+  as the \textsf{shorthand} no longer appears in the reference list.
+\end{itemize}
+
+Note on the 16th-edition files:
+\begin{itemize}
+\item These have been updated for compatibility with the latest
+  \textsf{biblatex} and \textsf{biber}, and there are also a number of
+  bug fixes included, many of them already mentioned in changelog
+  items above.  The \mycolor{\texttt{compressyears}} option is
+  available and turned on by default, and so is the
+  \mycolor{\texttt{dashed}} option.  Most of the new
+  \textsc{iso}8601-2 Extended Format date specifications are
+  available, also, though time stamps won't be printed, as that
+  edition of the \emph{Manual} is mostly silent about them.
+\end{itemize}
+
+\textbf{1.0rc5: Released January 16, 2018}
+
+\begin{itemize}
\item As Nikola Le\v{c}i\'c spotted, recent releases of
\textsf{biblatex} have introduced some compatibility problems for
\textsf{biblatex-chicago}, particularly with regard to the handling
@@ -12288,7 +16068,7 @@
there's a \textsf{date} or not.  Cf.\
section~\ref{sec:authuseropts}, above.
\item Bertold Schweitzer requested that the styles allow using the
-  string \texttt{forth\-coming} in the \textsf{pubstate} field to
+  string \texttt{forthcoming} in the \textsf{pubstate} field to
present sources that are yet to be published.  This is now supported
in all styles, and has the additional benefit of rendering recourse
to the \cmd{autocap} command unnecessary, as the styles print
@@ -12300,7 +16080,7 @@
\texttt{magazine} in the \textsf{entrysubtype} field of
\textsf{article}, \textsf{review}, \textsf{periodical}, and
\textsf{suppperiodical} entries.  I have provided this in all
-  styles, and whereever you see \texttt{magazine} in this
+  styles, and wherever you see \texttt{magazine} in this
documentation then \texttt{newspaper} will work in exactly the same
way.
\item Bertold also suggested that, following the example of Philip
@@ -12352,7 +16132,7 @@
bug when presenting a \textsf{subtitle} after a \textsf{title} that
ends in an exclamation point or question mark.  This bug has existed
since the first release of the 16th-edition styles, and I think I've
-  finally solved it now after the release of the \emph{Manual's }17th
+  finally solved it now after the release of the \emph{Manual's} 17th
edition.  (Cf.\ batson.)
\end{itemize}

@@ -12808,7 +16588,6 @@
of your document to redefine the new \mycolor{\cmd{foottextcite}}
and \mycolor{\cmd{foottextcites}} commands to change this
formatting.  See section~\ref{sec:formatcommands}, above.
-%\enlargethispage{\baselineskip}
\item This release includes support, in all styles, for
\textsf{biblatex's} multi-volume entry types: \textbf{mvbook},
\textbf{mvcollection}, \textbf{mvproceedings}, and
@@ -13036,8 +16815,6 @@
\textsf{postnote} field, then only that will appear.
\end{itemize}

-%%\enlargethispage{-2\baselineskip}
-
\textbf{0.9.9a: Released July 30, 2012}
\begin{itemize}
\item I have made a few changes to \textsf{biblatex-chicago.sty} to
@@ -13290,7 +17067,7 @@
you want to cite a comment to a blog or to other online material,
the \textbf{review} entry type, \textsf{entrysubtype}
\texttt{magazine} will serve.  The \textbf{eventdate} dates the
-  comment, and any timestamp that is required can go in
+  comment, and any time stamp that is required can go in
\textsf{nameaddon}.  These instructions work in both specifications.
\item Photographs are no longer presented differently from other sorts
of artworks so, in effect, in both styles, the \textbf{image} type
@@ -13587,8 +17364,6 @@
me know if I'm wrong.
\end{itemize}

-%\vspace{2\baselineskip}
-
Other New Features:
\begin{itemize}
\item The Chicago author-date style is now implemented in the
@@ -13803,8 +17578,6 @@
field if you would like to test this functionality.
\end{itemize}

-%%\enlargethispage{-3\baselineskip}
-
\textbf{0.8.9a: Released July 5, 2009}
\begin{itemize}
\item Slight changes for compatibility with \textsf{biblatex} 0.8e.

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-intro.pdf
===================================================================
(Binary files differ)

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-intro.tex
===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-intro.tex	2020-04-19 23:48:48 UTC (rev 54808)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-intro.tex	2020-04-20 21:05:08 UTC (rev 54809)
@@ -8,7 +8,7 @@
%\usepackage[document]{ragged2e}
\usepackage[authordate,backend=biber,autolang=none,booklongxref=false,%
bibencoding=latin1,postnotepunct,compresspages,strict,%
-annotation]{biblatex-chicago}
+annotation,cmsbreakurl]{biblatex-chicago}
% \usepackage[style=chicago-authordate,backend=biber,usecompiler=true,%
% babel=hyphen,bibencoding=auto,sorting=nyt,cmslos,autocite=inline]{biblatex}
\usepackage{lmodern}
@@ -18,25 +18,37 @@
\usepackage{setspace}
\usepackage{vmargin} \setpapersize{A4}
\setmarginsrb{1in}{20pt}{1in}{.5in}{1pt}{2pt}{0pt}{13pt}
-\usepackage{url}
-\urlstyle{rm}
+% \usepackage{url}
+% \urlstyle{rm}
+\usepackage{multicol}
\appto\bibsetup{\sloppy}
\hyphenation{evans-ton clem-ens mc-hugh}
\setlength{\dimen\footins}{9.5in}
\setlength{\parindent}{0pt}
\setlength{\parskip}{5pt}
+\setcounter{secnumdepth}{-1}
\providecommand{\theendnote}{}
-\protected\def\onethird{{\scriptsize\raisebox{.7ex}{1}%
+\protected\def\onethird{\mbox{\scriptsize\raisebox{.7ex}{1}%
\hspace{-0.1em}\raisebox{.2ex}{/}\hspace{-0.03em}3}}
\newcommand{\cmd}[1]{\texttt{\textbackslash #1}}
\newcommand{\mycolor}{}%[1]{\textcolor[HTML]{228B22}{#1}}
\usepackage{xr-hyper}
-\externaldocument[cms-]{../../Docs/biblatex-chicago}%
+\externaldocument[cms-]{biblatex-chicago}%
\usepackage[pdftex,hyperref,svgnames]{xcolor}
baseurl=biblatex-chicago.pdf\#]{hyperref}
+\makeatletter
+\renewcommand{\section}{\@startsection{section}{1}{\z@}%
+                                     {-3.25ex\@plus -1ex \@minus -.2ex}%
+                                     {1.5ex \@plus .2ex}%
+                                     {\normalfont\large\bfseries}}
+\renewcommand{\subsection}{\@startsection{subsection}{2}{\z@}%
+                                     {-3.25ex\@plus -1ex \@minus -.2ex}%
+                                     {1.5ex \@plus .2ex}%
+                                     {\normalfont\normalsize\bfseries}}
+\makeatother
\usepackage{cmsdocs}
\bibliography{dates-test}
%%\onehalfspacing
@@ -43,11 +55,15 @@
%\tracingstats=2
\begin{document}

-\section*{The Chicago Author-Date Specification}
-\label{sec:spec}
-
+{\Large\bfseries The Chicago Author-Date Specification}
+\vspace*{1.5ex}
+\begin{multicols}{2}
+  \renewcommand{\contentsname}{\textcolor{darkgray}{Contents}}
+  \footnotesize
+  \tableofcontents
+\end{multicols}
This file is intended as a brief introduction to the Chicago
-author-date specification (16th ed.) \autocite{chicago:manual} as
+author-date specification (17th ed.) \autocite{chicago:manual} as
implemented by \textsf{biblatex-chicago}, and falls somewhere in
between the \enquote{Quickstart} section of
\textsf{biblatex-chicago.pdf} and the full documentation as presented
@@ -65,43 +81,44 @@
\textsf{biblatex-chicago.pdf}.

-\subsection*{Important Note}
+\section{Important note: \textsf{biber}}
\label{bibernote}

Starting with \textsf{biblatex} version 1.5, in order to adhere to the
-author-date specification you will need to use \textsf{Biber} to
+author-date specification you will need to use \textsf{biber} to
process your .bib files, as \textsc{Bib}\TeX\ (and its more recent
variants) will no longer provide all the features the style requires.
For this release, you really need the current versions of
-\textsf{Biber} (2.10) and \textsf{biblatex} (3.10), which contain
+\textsf{biber} (2.14) and \textsf{biblatex} (3.14), which contain
features and bug-fixes on which my own code relies.  The advice that
-follows in this document assumes that you are using \textsf{Biber}; if
+follows in this document assumes that you are using \textsf{biber}; if
you wish to continue using \textsc{Bib}\TeX\ then you need
\textsf{biblatex} version 1.4c and \textsf{biblatex-chicago} 0.9.7a.

-\subsection*{Editions}
+\section{Editions}
\label{editions}

-The 16th edition of \emph{The Chicago Manual of Style} implements
-significant changes to what the author-date specification has,
-historically, recommended, and there are certain to be users who
-prefer the older format with titles capitalized sentence-style and
-not, in the case of most un-book-like entries, enclosed in quotation
-marks.  For such users, the \textsf{authordate-trad} style, as
-envisaged by the \textcite[15.45]{chicago:manual}, grafts the
-traditional Chicago author-date title formatting onto the current
-recommendations for the remainder of the reference apparatus.  Please
-consult
+The 17th edition of \emph{The Chicago Manual of Style} makes fairly
+numerous changes to the author-date specification, but many of them
+required changes to package code rather than to current .bib
+databases.  I have \cmssecref{cms-deprec:obsol} listed elsewhere those
+changes that might require attention to your databases, but much of
+what follows will involve additions rather than alterations.  This is
+true no matter which of the two author-date styles you are using,
+\textsf{authordate} or \textsf{authordate-trad}, the latter of which
+differs only in the treatment of titles, maintaining the formatting
+that was traditional in the \emph{CMS} up to the 15th edition where
+many were capitalized sentence-style and those in most un-book-like
+entries appeared without quotation marks
notes on the few .bib entries from this introduction that would
require modification for the \texttt{trad} style; for the remainder,
you'll notice a few extra sets of curly braces in various
\textsf{title} fields to make the entry usable in both author-date
-styles.  I have removed the 15th-edition styles from the package to
-prepare for the appearance of the new 17th-edition styles, which will
-be the focus of my attention, after this last 16th-edition release.
+styles.

-\subsection*{Usage}
+\section{Basic usage: the \cmd{autocite} command}
\label{usage}

As a general rule, you'll probably want to use the \cmd{autocite}
@@ -112,7 +129,7 @@
should also appear as you expect: \autocite[338]{batson};
\autocite[79]{beattie:crime}; \autocite[36]{boxer:china}.

-\subsection*{Repeated citations}
+\section{Repeated citations}
\label{sec:ibidem}

Repeated citations are somewhat complicated.  The Chicago author-date
@@ -121,7 +138,7 @@
\autocite{browning:aurora}; \autocite[45]{browning:aurora}.
Technically, this should only occur when a source is cited
\enquote{more than once in one paragraph}
-\autocite[15.26]{chicago:manual}, so you can use the \cmd{citereset}
+\autocite[15.27]{chicago:manual}, so you can use the \cmd{citereset}
command from \textsf{biblatex} to achieve the greatest compliance, as
the package only offers automatic resetting on part, chapter, section,
and subsection boundaries, while \textsf{biblatex-chicago}
@@ -136,7 +153,7 @@
at least more concise, only to use one citation command rather than
two.

-\subsection*{Other citation commands}
+\section{Other citation commands}
\label{sec:other}

The other \cmssecref{cms-sec:cite:authordate} citation commands from
@@ -157,40 +174,38 @@
\cmd{textcites} by the same author with postnotes:
\textcites[37]{pirumova}{pirumova:russian}.

-\textsf{Biblatex-chicago} now also provides a \cmd{gentextcite}
-command, which prints an \gentextcite{author:forthcoming} name in the
-genitive case in what is otherwise a standard \cmd{textcite}.  If you
-want to change the default -- \textbf{'s} -- printed there you can
-specify whatever text you wish like so:
+\textsf{Biblatex-chicago} also provides a \cmd{gentextcite} command,
+which prints an \gentextcite{author:forthcoming} name in the genitive
+case in what is otherwise a standard \cmd{textcite}.  If you want to
+change the default -- \textbf{'s} -- printed there you can specify
+whatever text you wish like so:
\cmd{gentextcite[<ending>][][]\{entry:key\}}.  There is also a
\cmd{gentextcites} command, modified thus:
\cmd{gentextcites[<ending>]()()[][]\{key1\}\{key2\}}.

-\subsection*{Shorthands}
+\section{Shorthands}
\label{sec:shorthands}

Chicago's author-date style
the use of shorthands as abbreviations for long authors' names,
-particularly institutional names \autocite[15.36]{chicago:manual}.  By
+particularly institutional names \autocite[15.37]{chicago:manual}.  By
default, I have followed this recommendation: \cmd{autocites}:
\autocites{bsi:abbreviation}{iso:electrodoc}; \cmd{textcites}:
\textcites{bsi:abbreviation}{iso:electrodoc}.  This \textsf{shorthand}
will by default appear at the head of the entry in the list of
references, followed by the parenthesized expansion of the shorthand,
-taken from the \textsf{author} field.  (This is a change from the 15th
-edition.)  You will usually also need a \textsf{sortkey} field to make
-sure that the entry is alphabetized by the \textsf{shorthand} rather
-than by the \textsf{title}.  If you use a
-\cmd{printbiblist\{shorthand\}} command, the list of shorthands will
-still be printed, so you now have a variety of options available for
-presenting the expansions depending on your specific requirements.
-Please note, also, that you can get back something approaching the
-\enquote{standard} behavior of shorthands if you give the
-\texttt{cmslos=false} option to \textsf{biblatex-chicago} in your
+taken from the \textsf{author} (or possibly the \textsf{organization})
+field.  The entry will be alphabetized by the \textsf{shorthand}.  If
+you use a \cmd{printbiblist\{shorthand\}} command, the list of
+shorthands will still be printed, so you now have a variety of options
+available for presenting the expansions depending on your specific
+requirements.  Please note, also, that you can get back something
+approaching the \enquote{standard} behavior of shorthands if you give
+the \texttt{cmslos=false} option to \textsf{biblatex-chicago} in your
document preamble.

-\subsection*{Mildly problematic entries}
+\section{Mildly problematic entries: authors and dates}
\label{sec:problematic}

In most \cmssecref[author]{cms-sec:ad:author} entries, the absence of
@@ -200,56 +215,65 @@
\autocite{horsley:prosodies}; \autocite{cook:sotweed}.  Alternatively,
in some cases the \textsf{title} may appear in place of the
\textsf{author}: \autocite{anon:stanze};
-\autocite{virginia:plantation}.  The 16th edition is less than
-enthusiastic about the use of \enquote{\texttt{Anon.}}\ as author.
+\autocite{virginia:plantation}.  Recent editions are less than
+enthusiastic about the use of \enquote{\texttt{Anon.}}\ as author,
+unless the title page of the work explicitly so attributes it.

By default, in most \cmssecref[date]{cms-sec:ad:date} entry types, an
-absent \textsf{date} will automatically provoke \textsf{Biber} into
+absent \textsf{date} will automatically provoke \textsf{biber} into
searching for other sorts of dates in the entry, in the order
-\textsf{year, eventyear, origyear, urlyear}: e.g.,
-\autocite{evanston:library}, which only has a \textsf{urlyear}.  In
-three entry types --- \textsf{Music}, \textsf{Review}, and
-\textsf{Video} --- this search order is \textsf{eventyear, origyear,
-  year, urlyear}, as in these types the earliest year should take
-precedence (cf.\ page~\pageref{sec:audiovisual}, below).  You can also
-change the default search order, for all but the three types just
-mentioned, by using the \texttt{cmsdate} option in the preamble of
-\textsf{options} field of individual entries.  Setting that option in
-the preamble either to \enquote{\texttt{both}} or
-\enquote{\texttt{on}} makes the document-wide search order:
-\textsf{origyear, year, eventyear, urlyear}.  This may be useful for
-documents that contain many entries with multiple dates, and where you
-want \emph{always} to present the earlier (i.e., \textsf{orig}) dates
-at the head of reference list entries and in citations.  You can
-eliminate some of these dates from the running, or change the search
-order, using the \cmd{DeclareLabeldate} command in your preamble, but
-please be aware that I have hard-coded the possibilities above into
-the author-date style in order to cope with some tricky corners of the
-specification.  If you reorder these dates, and your references enter
-these tricky corners, the results might be surprising.  (Cf.\
-section~4.5.8 in \textsf{biblatex.pdf}.)
+\textsf{date, eventdate, origdate, urldate}: e.g.,
+\autocite{wikiped:bibtex}, which only has a \textsf{urldate}.  In
+five entry types --- \textsf{Music}, \textsf{Review},
+\textsf{Standard}, \textsf{SuppPeriodical}, and \textsf{Video} ---
+this search order is \textsf{eventdate, origdate, date, urldate}, as
+in these types the earliest date should take precedence (cf.\
+page~\pageref{sec:audiovisual}, below).  You can also change the
+default search order, for all but the three types just mentioned, by
+using the \texttt{cmsdate} option in the preamble of your document,
+instead of (or in addition to) using it in the \textsf{options} field
+of individual entries.  Setting that option in the preamble either to
+\enquote{\texttt{both}} or \enquote{\texttt{on}} makes the
+document-wide search order: \textsf{origyear, year, eventyear,
+  urlyear}.  This may be useful for documents that contain many
+entries with multiple dates, and where you want \emph{always} to
+present the earlier (i.e., \textsf{orig}) dates at the head of
+reference list entries and in citations.  You can eliminate some of
+these dates from the running, or change the search order, using the
+that I have hard-coded the possibilities above into the author-date
+style in order to cope with some tricky corners of the specification.
+If you reorder these dates, and your references enter these tricky
+corners, the results might be surprising.  (Cf.\ section~4.5.8 in
+\textsf{biblatex.pdf}.)

-In most entry types, the absence of all four possible dates will
-automatically produce \mbox{\enquote{\texttt{n.d.}\hspace{-2pt}}}
-instead: \autocite{bernstein:shostakovich}.  You can also give it
-yourself in the form \cmd{bibstring\{nodate\}}:
-\autocite{ross:thesis}.  A date that can be guessed should appear
-within square brackets: \autocite{clark:mesopot}.  You can handle
-forthcoming works in one of two ways: either by using the
-\cmd{autocap} macro and the \textsf{year} (instead of the
-\textsf{date}) field, or by placing the exact string
-\texttt{forthcoming} in the \textsf{pubstate} field.  Either way the
-word will appear, correctly capitalized, in both citations and the
-list of references: \autocite{author:forthcoming};
+In all entry types except for \textsf{Misc}, the absence of all four
+possible dates will automatically produce
+\autocite{bernstein:shostakovich}.  You will see this same string in
+entries that only contain a \textsf{urldate}, where that date is an
+access date as opposed to, e.g., a revision date provided by the URL
+itself, that is, where no \textsf{userd} field has been provided to
+change the default string before the date:
+\autocite{evanston:library}.  You can also provide
+\cmd{bibstring\{nodate\}} yourself in a \textsf{year} field:
+\autocite{ross:thesis}.  Uncertain dates or date ranges like decades
+and centuries can now be presented using \textsf{biblatex's}
+specification: \autocite{clark:mesopot}.  You can handle forthcoming
+works in one of two ways: either by using the \cmd{autocap} macro and
+the \textsf{year} (instead of the \textsf{date}) field, or by placing
+the exact string \texttt{forthcoming} in the \textsf{pubstate} field.
+Either way the word will appear, correctly capitalized, in both
+citations and the list of references: \autocite{author:forthcoming};
\autocite{contrib:contrib}.

-The 16th edition of the \emph{Manual} has changed the rules for
-entries with more than one date \autocite[15.38]{chicago:manual}.
-First, \textsf{Music}, \textsf{Review}, and \textsf{Video} entries
-have their own rules, which are applied automatically.  (Once again,
-see page~\pageref{sec:audiovisual}, below.)  For other entry types,
-there are two options, corresponding to two different states of the
+The rules for entries with more than one date remain unchanged from
+the previous edition \autocite[15.40]{chicago:manual}.  First,
+\textsf{Music}, \textsf{Review}, and \textsf{Video} entries have their
+own rules, which are applied automatically.  (Once again, see
+page~\pageref{sec:audiovisual}, below.)  For other entry types, there
+are two options, corresponding to two different states of the
\texttt{cmsdate} entry (or preamble) option.  The default is
\texttt{cmsdate=off}: \autocite{maitland:equity}.  Here, setting the
\textsf{pubstate} field to \texttt{reprint} ensures that a notice of
@@ -265,29 +289,34 @@
the following entries in \textsf{dates-test.bib}:
\autocites{schweitzer:bach}{white:russ}{white:ross:memo}.

-\subsection*{Corners of the specification}
+\section{Corners of the specification}
\label{sec:corners}

-In some cases, the \emph{Manual} isn't altogether clear about how to
-present entries in the author-date style.  By following up on
-suggestions from the notes \&\ bibliography style, one can be
-reasonably certain about most of what follows, but if you interpret
-the specification differently please let me know.
+The \emph{Manual} has clarified many parts of the author-date
+specification, and by following up on suggestions from the notes \&\
+bibliography style one can be reasonably certain about many other
+details, but if you interpret the specification differently please let
+me know.

-\subsubsection*{InReference entries}
+\subsection{InReference entries}
\label{sec:inref}

peculiarities: the title of the work should always take the place of
-any author, no \enquote{\texttt{n.d.}\hspace{-2pt}} will automatically
-be provided, and any postnote field will be enclosed in quotation
+any author, citations of non-online sources should include a
+publication date, and any postnote field will be enclosed in quotation
marks preceded by \enquote{\texttt{s.v.}\hspace{-2pt}} for
\enquote{\emph{sub verbo}.}  This allows you to refer to alphabetized
articles in well-known reference works: \autocite[Hume,
David]{ency:britannica}; \autocite[Sibelius, Jean]{grove:sibelius};
-\autocite[BibTeX]{wikiped:bibtex}.
+\autocite[BibTeX]{wikiped:bibtex}.  As this last example shows, you
+can also put anything at all into the \textsf{entrysubtype} field to
+present, at your discretion, an online reference work more like an
+\textsf{Online} entry, that is, with a \textsf{title} in roman rather
+than italics.

-\subsubsection*{Author-less Article, Review, and Manual entries}
+\subsection{Author-less Article, Review, Manual and Standard
+  entries}
\label{sec:authless:art}

In \textsf{Article} and \textsf{Review} entries
@@ -298,35 +327,34 @@
(Without the entrysubtype, you'll get the \textsf{title} at the head
rather than the \textsf{journaltitle}.)  You can cite newspaper and
magazine articles entirely within the text, i.e., without them
-appearing in the reference list \autocite[15.47]{chicago:manual}, if
+appearing in the reference list \autocite[15.49]{chicago:manual}, if
you set the \texttt{cmsdate=full} entry option:
\autocite{lakeforester:pushcarts}; \autocite{nyt:trevorobit}.  In
-\textsf{Manual} entries, the \textsf{organization} field does the
-same: \autocite{dyna:browser}.  If you wish to present an abbreviated
-form of the organization name in citations only, then the
-\textsf{shortauthor} field --- or in other cases the
-\textsf{shorthand} field --- is the place for it:
-\autocite{bsi:abbreviation}.  For abbreviated \textsf{journaltitles},
-you can use \textsf{shortjournal}, which also allows you, should you
-wish, to provide a list of abbreviated journal names with their
-expansions using \cmd{printbiblist\{shortjournal\}}:
-\autocite{unsigned:ranke}.
+\textsf{Manual} and \textsf{Standard} entries, the
+\textsf{organization} field does the same: \autocite{dyna:browser}.
+If you wish to present an abbreviated form of the organization name in
+citations only, then the \textsf{shortauthor} field --- or in other
+cases the \textsf{shorthand} field --- is the place for it:
+\autocite{niso:bibref}.  For abbreviated \textsf{journaltitles}, you
+can use \textsf{shortjournal}, which also allows you, should you wish,
+to provide a list of abbreviated journal names with their expansions
+using \cmd{printbiblist\{shortjournal\}}: \autocite{unsigned:ranke}.

-\subsubsection*{Misc entries with an entrysubtype}
+% \enlargethispage{-\baselineskip}
+
+\subsection{Misc entries with an entrysubtype}
\label{sec:misc}

-pieces from an unpublished archive where only an \textsf{origdate} is
-present, you no longer need to set the \texttt{cmsdate} option in your
-.bib entry, as \textsf{Biber} and \textsf{biblatex-chicago} now handle
-this automatically: \autocite{creel:house}.  Non-letters, e.g.,
-interviews, use the \textsf{date} field, so you don't need
-\texttt{cmsdate} there, either: \autocite{spock:interview}.  For
-undated pieces you can put \cmd{bibstring\{nodate\}} in the
-\textsf{year} field: \autocite{dinkel:agassiz}.  For citing whole
-collections, see the next section.
+When citing individual pieces from unpublished archives,
+only have an \textsf{origdate} \autocite{creel:house}, while
+non-letters, e.g., interviews, use the \textsf{date} field:
+\autocite{spock:interview}.  For undated pieces you can put
+\cmd{bibstring\{nodate\}} in the \textsf{year} field:
+\autocite{dinkel:agassiz}.  For citing whole collections, see the next
+section.

-\subsubsection*{entrysubtype = \{classical\}}
+\subsection{entrysubtype = \{classical\}}
\label{sec:classical}

@@ -334,14 +362,13 @@
in the author-date style especially it can be put to use in several
other contexts.  In a nutshell, any entry with such an
\textsf{entrysubtype} will be treated, in citations only, not as
-author-date but as author-title.  (Entries in the list of references,
-e.g., a particular edition of Aristotle, will still appear in standard
-author-date format.)  A \cmd{cite*} or \cmd{autocite*} command will,
-in such a case, produce the title rather than the year.  Some examples
-should make this clearer:
+author-date but as author-title, and will also have modified
+punctuation before \textsf{postnote} fields.  (Entries in the list of
+references, e.g., a particular edition of Aristotle, will still appear
+in standard author-date format.)  A \cmd{cite*} or \cmd{autocite*}
+command will, in such a case, produce the title rather than the year.
+Some examples should make this clearer:

-%\enlargethispage{-\baselineskip}
-
Classical works: without abbreviation:
\autocite{aristotle:metaphy:trans}; with abbreviation:
\autocite{aristotle:metaphy:gr}; \autocite{plato:republic:gr}; using
@@ -355,14 +382,50 @@

An unpublished archive, from which more than one work has been cited:
\autocite[file 12]{house:papers}.  (Both this and the previous example
-use a Misc entry with \texttt{classical} \textsf{entrysubtype}.)
+use a \textsf{Misc} entry with \texttt{classical}
+\textsf{entrysubtype}.)

+Similarly, scientific \cmssecref[dataset]{cms-sec:types:authdate}
+databases use the specialized \textsf{Dataset} entry type, and will
+generally only have an online access date (\textsf{urldate}), so by
+default I set \texttt{authortitle=true} for this type, instead of
+using an \textsf{entrysubtype}, to provide author-title citations:
+\autocite{nasa:db}.
+
+\subsection{Online sources}
+\label{sec:online}
+
+The 17th edition of the \emph{CMS} has greatly enhanced its treatment
+of online materials, including blogs, social media, podcasts, and
+scientific databases.  Table~2 in \textsf{biblatex-chicago.pdf}
+you, and there are examples scattered throughout this introduction.
+The presentation of online comments (on blogs or social media posts)
+warrants extra attention.  As a rule, such material need be presented
+only in the text, rather than in the reference list.  You could simply
+provide it there by hand, or perhaps as a comment to a citation of the
+main blog or post, using the techniques described in the next section.
+The \texttt{commenton} \textsf{relatedtype}
+\cmssecref{cms-sec:authrelated} allows you to gather all such
+references in your .bib file, and attempts to automate as far as
+possible the presentation of those references in your document.  In
+short, the comment \cmslink{ac:comment} with the \texttt{commenton}
+\textsf{relatedtype} can be cited as part of a multicite command like
+so: \verb+\autocites{ac:comment}{ellis:blog-customc}+, yielding
+\autocites{ac:comment}{ellis:blog-customc}.  The second key given to
+the \cmd{autocites} command is a virtual entry, created by
+\textsf{biber} in the document .bbl file, and reachable by combining
+the key in the \textsf{related} field with the suffix
+\texttt{-customc}.  You can, of course, arrange for comments to appear
+in the reference list, either using \texttt{commenton} or a more
+handcrafted solution, e.g., \autocite{viv:amlen}.
+

If you wish to include a comment inside the parentheses of a citation,
it will need to be separated by a semicolon
-\autocite[15.23]{chicago:manual}.  If you have a \textsf{postnote},
+\autocite[15.24]{chicago:manual}.  If you have a \textsf{postnote},
then you can manually provide the punctuation and comment in that
field, e.g., \autocite[4; the unrevised trans.]{stendhal:parma}.
Without a \textsf{postnote}, you have two choices.  You can enable the
@@ -376,7 +439,7 @@
text and the comment will then do the trick, e.g.,
\autocites{chicago:manual}{chicago:comment}.

-\subsubsection*{Multiple authors}
+\subsection{Multiple authors}
\label{sec:multiple}

The default settings in \textsf{biblatex-chicago} are
@@ -391,8 +454,8 @@
list includes another work \emph{of the same date} that would also
be abbreviated as [\enquote{Hlatky et al.}] but whose coauthors are
different persons or listed in a different order, the text citations
-  must distinguish between them} \autocite[15.28]{chicago:manual}.
-The (\textsf{Biber}-only) \textsf{biblatex} option
+  must distinguish between them} \autocite[15.29]{chicago:manual}.
+The (\textsf{biber}-only) \textsf{biblatex} option
\texttt{uniquelist}, set for you in \textsf{biblatex-chicago.sty},
will automatically handle many of these situations for you, but it is
as well to understand that it does so by temporarily suspending the
@@ -418,35 +481,32 @@
2002), as the spec recommends.  There is, unfortunately, no simpler
way that I know of to deal with this situation.

-\subsubsection*{Audiovisual entries}
+\subsection{Audiovisual entries}
\label{sec:audiovisual}

-\enquote{Chicago recommends a more comprehensive approach to dating
-  audiovisual materials than in previous editions.}  This means, for
-instance, that, even when consulting a digital copy, \enquote{it is
-  generally useful to give information about the original source.}
-Also, \enquote{the date of the original recording should be privileged
-  in the citation} \autocite[15.53]{chicago:manual}.  The rather more
-book-like entries are generally unaffected by these changes, so
-published (\textsf{Audio}) and unpublished (\textsf{Misc}) scores are
-no problem at all: \autocite{schubert:muellerin};
-\autocite{verdi:corsaro}; \autocite{shapey:partita}.  The dating of
-online materials has been enhanced: \autocite{coolidge:speech};
-significant changes, however, appear in \textsf{Music} and
-\textsf{Video} entries, where every effort should be made to find
-\autocite{friends:leia}; \autocite{handel:messiah};
-\autocite{holiday:fool}; \autocite{nytrumpet:art}.  Others perhaps
-require further information in the entry or genuinely are better
-suited to presentation in running text: \autocite{beethoven:sonata29}.
-The standard \textsf{biblatex} tools for subdividing reference lists
-are all available if you want to follow the \emph{Manual's}
-recommendations on presenting this kind of material separately from
-other sources.
+The \emph{Manual} \cmssecref{cms-sec:ad:avdate} acknowledges that most
+audio-visual material will be cited via a digital copy, but suggests
+that \enquote{it is generally useful to give information about the
+  original source,} and also that \enquote{the date of the original
+  recording should be privileged in the citation}
+\autocite[15.57]{chicago:manual}.  The more book-like entries, like
+published (\textsf{Audio}) and unpublished (\textsf{Misc}) scores, are
+straightforward: \autocite{schubert:muellerin};
+\autocite{verdi:corsaro}; \autocite{shapey:partita}.  Efforts should
+be made to provide a date beyond the access date for online materials:
+\autocite{pollan:plant}.  So too for \textsf{Music} and \textsf{Video}
+entries, where recording or broadcast dates are generally preferred;
+\autocite{handel:messiah}; \autocite{holiday:fool};
+\autocite{nytrumpet:art}.  Others perhaps require further information
+in the entry or genuinely are better suited to presentation in running
+text: \autocite{beethoven:sonata29}.  The standard \textsf{biblatex}
+tools for subdividing reference lists are all available if you want to
+follow the \emph{Manual's} recommendations on presenting this kind of
+material separately from other sources.

-\subsubsection*{Related entries}
+\subsection{Related entries}
\label{sec:related}

\textsf{Biblatex} provides \cmssecref{cms-sec:authrelated} a powerful
@@ -456,11 +516,11 @@
some Chicago-specific variants which employ different means.  You can
find a full discussion of this in \textsf{biblatex-chicago.pdf}, but a
few of the entries already cited in this introduction show some of the
-possibilities: \autocite{aristotle:metaphy:trans};
-\autocite{coolidge:speech}; \autocite{emerson:nature};
-\autocite{schweitzer:bach}.
+possibilities: \autocites{ac:comment}{ellis:blog-customc};
+\autocite{aristotle:metaphy:trans}; \autocite{coolidge:speech};
+\autocite{emerson:nature}; \autocite{schweitzer:bach}.

-\subsection*{In conclusion}
+\section*{In conclusion}
\label{sec:conclude}

Allow me, finally, to emphasize just how multifarious are the sources
@@ -472,7 +532,7 @@
\textsf{biblatex-chicago} that looks wrong to you, or if the
documentation has left you perplexed, please let me know.

-
+\nocite{amlen:hoot}
\printbibliography[title=References]
\setlength{\textheight}{10.5in}
\twocolumn[\Large \texttt{The Database File}]
@@ -500,6 +560,16 @@
@String{uchp = {University of Chicago Press}}
@String{oup = {Oxford University Press}}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=ac:comment]
+  entrysubtype = {magazine},
+  author = 	 {AC},
+  eventdate = 	 {2008-07-01T10:18:00},
+{ellis:blog}{anchor}{}}{\{\colorbox{Gainsboro}{ellis:blog}\}}*},
+  relatedtype =  {commenton}
+}
+\end{lstlisting}
title = 	 {The Complete Correspondence, 1928--1940},
@@ -508,9 +578,23 @@
author = 	 {Adorno, Theodor~W. and Benjamin, Walter},
editor = 	 {Lonitz, Henri},
translator = 	 {Nicholas Walker},
-  location =  {Cambridge, MA}
+  location =     {Cambridge, MA}
}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=amlen:hoot]
+  author = 	 {Amlen, Deb},
+  title = 	 {One Who Gives a Hoot},
+  journaltitle = {Wordplay},
+  entrysubtype = {magazine},
+  maintitle = 	 {New York Times},
+  location = 	 {blog},
+  date = 	 {2015-01-26},
+  url = 	 {http://wordplay.blogs
+      .nytimes.com/2015/01/26
+      /one-who-gives-a-hoot/}
+}
+\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=anon:stanze]
title = 	 {Stanze in lode della donna brutta},
@@ -526,13 +610,13 @@
options = 	 {skipbib},
entrysubtype = {classical},
origdate = 	 1924,
-  date = 1997,
+  date =         1997,
author = 	 {Aristotle},
editor = 	 {Ross, W.~D.},
-  publisher = {Oxford Univ.\ Press and Sandpiper Books},
+  publisher =    {Oxford Univ.\ Press and Sandpiper Books},
pubstate = 	 {reprint},
volumes = 	 2,
-  location =  {Oxford}
+  location =     {Oxford}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=aristotle:metaphy:trans]
@@ -549,9 +633,9 @@
{aristotle:metaphy:gr}{anchor}{}}%
{\{\colorbox{Gainsboro}{aristotle:metaphy:gr}\}}*},
maintitle = 	 {The Works of {Aristotle}, Translated into {English}},
-  publisher = {Clarendon Press},
+  publisher =    {Clarendon Press},
edition = 	 2,
-  location =  {Oxford}
+  location =     {Oxford}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=ashbrook:brain]
@@ -559,11 +643,10 @@
author = 	 {Ashbrook, James~B. and Albright, Carol Rausch},
title = 	 {The Frontal Lobes, Intending, and a Purposeful God},
booktitle = 	 {The Humanizing Brain},
-  publisher = {Pilgrim Press},
+  publisher =    {Pilgrim Press},
year = 	 1997,
chapter = 	 7,
-  location =  {Cleveland, OH},
-  shorttitle = {The Frontal Lobes}
+  location =     {Cleveland, OH}
}
\end{lstlisting}
@@ -592,9 +675,9 @@
subtitle = 	 {The Political Economy of Marketwomen in {Peru}},
year = 	 1989,
author = 	 {Babb, Florence},
-  publisher = {University of Texas Press},
+  publisher =    {University of Texas Press},
edition = 	 {\bibstring{revisededition}},
-  location =  {Austin}
+  location =     {Austin}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=barcott:review]
@@ -678,7 +761,6 @@
title = 	 {Specification for Abbreviation of Title Words and Titles of Publications},
date = 	 1985,
organization = {British Standards Institute},
-  sortname = 	 {BSI},
address = 	 {Linford Woods, Milton Keynes, UK},
shorthand = 	 {BSI}
}
@@ -705,12 +787,12 @@
\begin{lstlisting}[language=BibTeX,label=chicago:manual]
title = 	 {The {Chicago} Manual of Style},
-  year = 	 2010,
+  year = 	 2017,
author = 	 {{University of Chicago Press}},
shortauthor =  {\mkbibemph{CMS}},
-  publisher = uchp,
-  edition = 	 16,
-  location =  {Chicago}
+  publisher =    uchp,
+  edition = 	 17,
+  location =     {Chicago}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=clark:mesopot]
@@ -719,8 +801,8 @@
subtitle = 	 {Between Two Rivers},
author = 	 {Hazel V. Clark},
howpublished = {End of the Commons General Store},
-  year = 	 {\mkbibbrackets{1957?}},
-  location =  {Mesopotamia, OH}
+  date = 	 {1957?},
+  location =     {Mesopotamia, OH}
}
\end{lstlisting}
@@ -783,13 +865,13 @@
author = 	 {Coolidge, Calvin},
title = 	 {Equal Rights},
-  note = 	 {copy of an undated 78 rpm disc},
+  note = 	 {copy of an undated 78 rpm disc, 3:45},
-  year = 	 {[1920?]},
-  relatedstring = {from}
+  date = 	 {1920~},
+  relatedstring = {in}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=creel:house]
@@ -820,8 +902,8 @@
year = 	 {\bibstring{nodate}},
entrysubtype = {yes},
note = 	 {Agassiz Papers},
-  location =  {Harvard University},
-  organization =  {Houghton Library}
+  location =     {Harvard University},
+  organization = {Houghton Library}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=donne:var]
@@ -858,14 +940,26 @@
\begin{lstlisting}[language=BibTeX,label=eliot:pound]
title = 	 {Literary Essays},
-  options = {useauthor=false},
+  options =      {useauthor=false},
year = 	 1953,
author = 	 {Pound, Ezra},
-  editor =  {Eliot, T.~S.},
-  publisher = {New Directions},
-  location =  {New York}
+  editor =       {Eliot, T.~S.},
+  publisher =    {New Directions},
+  location =     {New York}
}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=ellis:blog]
+  author = 	 {Ellis, Rhian},
+  title = 	 {Squatters' Rights},
+  journaltitle = {Ward Six},
+  location = 	 {blog},
+  date = 	 {2008-06-30},
+  url = 	 {http://wardsix.blogspot.com
+      /2008/06/squatters-rights.html},
+  entrysubtype = {magazine}
+}
+\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=emerson:nature]
title =	 {Nature},
@@ -881,6 +975,7 @@
\begin{lstlisting}[language=BibTeX,label=ency:britannica]
title =        {Encyclopaedia Britannica},
+  date =         {1980},
edition =      {15},
shorttitle = 	 {Ency. {Brit}., \mkbibemph{15th ed}\adddot},
options =      {hypertitle}
@@ -896,9 +991,9 @@
volume = 	 4,
author = 	 {Euripides},
editor = 	 {Grene, David and Lattimore, Richmond},
-  publisher = uchp,
+  publisher =    uchp,
pages = 	 {185--288},
-  location =  {Chicago},
+  location =     {Chicago}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=evanston:library]
@@ -908,7 +1003,7 @@
title = 	 {Evanston Public Library Strategic Plan, 2000--2010},
subtitle = 	 {A Decade of Outreach},
organization = {Evanston Public Library},
-  url = 	 {http://www.epl.org/library/ strategic-plan-00.html},
+  url = 	 {http://www.epl.org/library /strategic-plan-00.html},
urldate = 	 {2002-07-18}
}
\end{lstlisting}
@@ -917,12 +1012,12 @@
title = 	 {The One with the {Princess Leia} Fantasy},
date = 	 2003,
booktitle = 	 {Friends},
author = 	 {Curtis, Michael and Malins, Gregory~S.},
eventdate = 	 {1996-09-19},
editor = 	 {Mancuso, Gail},
editortype = 	 {director},
-  publisher = {Warner Home Video},
+  publisher =    {Warner Home Video},
type = 	 {DVD},
}
@@ -932,7 +1027,7 @@
entrysubtype = {classical},
keywords = 	 {nosample},
-  title = 	 {Genesis},
+  title = 	 {Genesis}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=gourmet:052006]
@@ -948,7 +1043,7 @@
title = 	 {The New {Grove} Dictionary of Music and Musicians},
author = 	 {Hepokoski, James},
-  lista = {Sibelius, Jean},
+  lista =        {Sibelius, Jean},
url = 	 {http://www.grovemusic.com/},
urldate = 	 {2002-01-03},
sortkey = 	 {New Grove}
@@ -966,7 +1061,7 @@
editora = 	 {Shaw, Robert},
editoratype =  {none},
author = 	 {Handel, George Frederic},
-  publisher = {Video Artists International},
+  publisher =    {Video Artists International},
}
\end{lstlisting}
@@ -979,7 +1074,7 @@
date = 	 {2002-02-06},
volume =	 287,
number =	 5,
-  url =   {http://jama.ama-assn.org/issues/ v287n5/rfull/joc10108.html#aainfo},
+  url =   {http://jama.ama-assn.org/issues /v287n5/rfull/joc10108.html#aainfo},
urldate =	 {2002-01-07}
}
\end{lstlisting}
@@ -991,9 +1086,9 @@
author = 	 {Herron, Joel and Sinatra, Frank and Wolf, Jack},
editor = 	 {Holiday, Billie},
-  editortype = 	 {none},
+  editortype = 	 {vocalist},
number = 	 {CL 1157},
-  publisher = {Columbia},
+  publisher =    {Columbia},
type = 	 {33\onethird\ rpm},
note = 	 {with Ray Ellis},
options = 	 {useauthor=false}
@@ -1003,13 +1098,12 @@
title = 	 {{HOROWITZ AT CARNEGIE HALL} 2-{Chopin Nocturne} in Fm Op.55},
-  sortkey = 	 {Horowitz},
urldate = 	 {2009-01-09},
userd = 	 {posted by \mkbibquote{hubanj,}},
note = 	 {from a performance televised by CBS on\nopunct},
date = 	 {1968-09-22},
-  shorttitle = {HOROWITZ}
+  shorttitle =   {HOROWITZ}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=horsley:prosodies]
@@ -1029,18 +1123,16 @@
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=iso:electrodoc]
-  title = 	 {Electronic Documents or Parts thereof. {Excerpts} from {International Standard ISO} 690-2},
-  part = 	 {part 2},
-  date = 	 2001,
-  maintitle = 	 {Information and Documentation},
-  mainsubtitle = {Bibliographic References},
+  title = 	 {Information and Documentation---Rules for the
+        Abbreviation of Title Words and Titles of Publications},
+  date = 	 1997,
author = 	 {{International Organization for Standardization}},
-  shorthand =  {ISO},
-  publisher = {National Library of Canada},
-  sortname = 	 {ISO},
-  url = 	 {http://www.nlc-bnc.ca/iso/ tc46sc9/standard/690-2e.htm}
+  shorthand =    {ISO},
+  series =       {ISO},
+  number =       {4:1997},
+  publisher =  	 {ISO},
}
\end{lstlisting}
@@ -1050,10 +1142,11 @@
origdate = 	 1909,
options = 	 {cmsdate=on},
author = 	 {James, Henry},
-  publisher = {Project Gutenberg},
-  url = 	 {ftp://ibiblio.org/pub/docs/ books/gutenberg/etext96/ambas10.txt}
+  publisher =    {Project Gutenberg},
+  url = 	 {ftp://ibiblio.org/pub/docs
+     /books/gutenberg/etext96/ambas10.txt}
}
-\end{lstlisting}\clearpage
+\end{lstlisting}%\clearpage
\begin{lstlisting}[language=BibTeX,label=lakeforester:pushcarts]
journaltitle = {Lake Forester},
@@ -1061,15 +1154,15 @@
entrysubtype = {magazine},
title = 	 {Pushcarts Evolve to Trendy Kiosks},
options = 	 {cmsdate=full},
-  location =  {Lake Forest, IL}
+  location =     {Lake Forest, IL}
}
\end{lstlisting}
-  author = 	 {Library of Congress},
+  organization = {Library of Congress},
subtitle = 	 {Recordings from {World War I} and the 1920 Election, 1918--1920},
-  url = 	 {http://memory.loc.gov/ammem/ nfhtml/nforSpeakers01.html},
+  url = 	 {http://memory.loc.gov/ammem /nfhtml/},
note = 	 {RealAudio and WAV formats}
}
\end{lstlisting}
@@ -1093,23 +1186,45 @@
origdate = 	 1909,
author = 	 {Maitland, Frederic W.},
editor = 	 {Chaytor, A.~H. and others},
-  publisher = cup,
+  publisher =    cup,
pubstate = 	 {reprint},
sortyear = 	 {2010}
}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=nasa:db]
+  author = 	 {{NASA/IPAC Extragalactic Database}},
+  title = 	 {object name IRAS F00400+4059},
+  url = 	 {http://ned.ipac.caltech.edu},
+  urldate = 	 {2016-04-06}
+}
+\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=niso:bibref]
+  title = 	 {Bibliographic References},
+  organization = {National Information Standards Organization},
+  userd = 	 {approved},
+  howpublished = {reaffirmed},
+  eventdate =    {2010-05-13},
+  date = 	 {2005-06-09},
+  series = 	 {ANSI/NISO},
+  number =       {Z39.29-2005},
+  publisher =    {NISO},
+  shorthand =    {NISO},
+  location =     {Bethesda, MD}
+}
+\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=nytrumpet:art]
title = 	 {Art of the Trumpet},
date = 	 1982,
origdate = 	 {1981-06-01/1981-06-02},
-  author = 	 {{The New York Trumpet Ensemble, with Edward Carroll (trumpet) and Edward Brewer (organ)}},
+  author = 	 {{New York Trumpet Ensemble, with Edward Carroll (trumpet) and Edward Brewer (organ)}},
shortauthor =  {{New York Trumpet Ensemble}},
number = 	 {PVT 7183},
userd = 	 {recorded at the Madeira Festival,},
-  sortkey = 	 {New York Trumpet},
type = 	 {compact disc}
}
\end{lstlisting}
@@ -1118,7 +1233,7 @@
journaltitle = {New York Times},
entrysubtype = {magazine},
date = 	 {2000-04-10},
-  title = {obituary of {Claire Trevor}},
+  title =        {obituary of {Claire Trevor}},
options = 	 {cmsdate=full},
pages = 	 {national edition}
}
@@ -1142,7 +1257,7 @@
usere = 	 {The zemstvo liberal movement: Its social roots and evolution to the beginning of the twentieth century},
langid =       {russian},
author = 	 {Pirumova, N.~M.},
-  publisher = {Izdatel'stvo \mkbibquote{Nauka}},
+  publisher =    {Izdatel'stvo \mkbibquote{Nauka}},
}
\end{lstlisting}
@@ -1158,10 +1273,10 @@
booktitle = 	 {{Clitophon, Republic, Timaeus, Critias}},
maintitle = 	 {Opera},
-  publisher = {Clarendon Press},
-  series = {Oxford Classical Texts},
+  publisher =    {Clarendon Press},
+  series =       {Oxford Classical Texts},
pages = 	 {327--621},
-  location =  {Oxford}
+  location =     {Oxford}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=pollan:plant]
@@ -1169,7 +1284,9 @@
author = 	 {Pollan, Michael},
title = 	 {Michael {Pollan} Gives a Plant's-Eye View},
organization = {TED video, 17:31},
-  url = 	 {http://www.ted.com/index.php/ talks/michael_pollan_gives_a_ plant_s_eye_view.html},
+  url = 	 {http://www.ted.com/index.php
+      /talks/michael_pollan_gives_a _plant_s_eye_view.html},
+  note =         {filmed in\nopunct},
urldate = 	 {2008-02},
date = 	 {2007-03},
userd = 	 {posted}
@@ -1193,7 +1310,7 @@
maintitle = 	 {First Vocal Album},
author = 	 {Schubert, Franz},
-  publisher = {G.~Schirmer},
+  publisher =    {G.~Schirmer},
}
\end{lstlisting}
@@ -1208,9 +1325,9 @@
addendum = 	 {Citations refer to the Dover edition},
options = 	 {cmsdate=both},
translator = 	 {Newman, Ernest},
-  publisher = {Dover},
+  publisher =    {Dover},
pubstate = 	 {reprint},
-  location =  {New York}
+  location =     {New York}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=shapey:partita]
@@ -1231,7 +1348,7 @@
publisher = 	 uchp,
year = 	 1974,
translator = 	 {Silverstein, Theodore},
-  location =  {Chicago}
+  location =     {Chicago}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=spock:interview]
@@ -1243,7 +1360,7 @@
note = 	 {interview 67A, transcript},
organization = {Senn Oral History Collection},
institution =  {National Library of Medicine},
-  location =  {Bethesda, MD}
+  location =     {Bethesda, MD}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=stendhal:parma]
@@ -1252,7 +1369,7 @@
date = 	 1925,
author = 	 {Stendhal},
-  publisher = {Boni \& Liveright},
+  publisher =    {Boni \& Liveright},
translator = 	 {Scott-Moncrieff, C.~K.}
}
@@ -1264,24 +1381,24 @@
date = 	 {1828-02},
title =	 {unsigned review of \mkbibemph{Geschichten der romanischen und germanischen V\xF6lker}, by {Leopold von Ranke}},
number =	 {23--24},
-  sortkey = 	 {Erg},
-  shortjournal =  {Erg\"anzungsbl\"atter z. Allg. Lit.-Ztg.}
+  shortjournal = {Erg\"anzungsbl\"atter z. Allg. Lit.-Ztg.}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=verdi:corsaro]
title = 	 {Il corsaro (melodramma tragico \mkbibemph{in three acts})},
-  titleaddon = 	 {libretto by Francesco Maria Piave},
+  editortype = 	 {libretto by},
+  editor =       {Piave, Francesco Maria},
date = 	 1998,
author = 	 {Verdi, Giuseppe},
editor = 	 {Hudson, Elizabeth},
number = 	 {\bibstring{jourser} 1, Operas},
series = 	 {The Works of Giuseppe Verdi},
-  publisher = {University of Chicago Press; Milan: G.\ Ricordi},
+  publisher =    {University of Chicago Press; Milan: G.\ Ricordi},
volumes = 	 2,
}
-\end{lstlisting}\clearpage
+\end{lstlisting}%\clearpage
\begin{lstlisting}[language=BibTeX,label=virginia:plantation]
title =	 {A True and Sincere Declaration of the Purpose and Ends of the Plantation Begun in {Virginia}, of the Degrees Which It Hath Received, and Means by Which It Hath Been Advanced},
@@ -1291,6 +1408,16 @@
year = 	 1610
}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=viv:amlen]
+  author = 	 {Viv},
+  entrysubtype = {magazine},
+  title = 	 {comment on Amlen, \mkbibquote{Hoot}},
+  crossref = 	 {amlen:hoot},
+  eventdate = 	 {2015-01-27}
+}
+\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=white:ross:memo]
author = 	 {White, E.~B.},
@@ -1326,9 +1453,10 @@
title = 	 {Wikipedia},
lista =        {BibTeX},
-  url = 	 {http://en.wikipedia.org/wiki/ BibTeX},
-  urldate = 	 {2012-05-18}
+  userd = 	 {last edited},
+  entrysubtype = {online},
+  url = 	 {http://en.wikipedia.org/wiki /BibTeX},
+  urldate = 	 {2019-11-15T20:59:00}
}
\end{lstlisting}
\end{document}

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-sample.pdf
===================================================================
(Binary files differ)

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-sample.tex
===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-sample.tex	2020-04-19 23:48:48 UTC (rev 54808)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-dates-sample.tex	2020-04-20 21:05:08 UTC (rev 54809)
@@ -7,7 +7,8 @@
\usepackage[autostyle]{csquotes}
%\usepackage[document]{ragged2e}
\usepackage[authordate,backend=biber,autolang=none,booklongxref=false,%
-bibencoding=latin1,postnotepunct,compresspages,strict]{biblatex-chicago}
+bibencoding=latin1,postnotepunct,compresspages,strict,%
+cmsbreakurl]{biblatex-chicago}
% \usepackage[style=chicago-authordate,backend=biber,usecompiler=true,%
% babel=hyphen,bibencoding=auto,sorting=nyt,cmslos,autocite=inline]{biblatex}
\usepackage{lmodern}
@@ -25,7 +26,7 @@
\setlength{\dimen\footins}{9.5in}
\setlength{\parindent}{0pt}
\setlength{\parskip}{5pt}
-\protected\def\onethird{{\scriptsize\raisebox{.7ex}{1}%
+\protected\def\onethird{\mbox{\scriptsize\raisebox{.7ex}{1}%
\hspace{-0.1em}\raisebox{.2ex}{/}\hspace{-0.03em}3}}
\newcommand{\cmd}[1]{\texttt{\textbackslash #1}}
@@ -37,23 +38,9 @@
\section*{The Chicago Author-Date Specification: Testing Only}
\label{sec:spec}

\label{bibernote}

-Starting with \textsf{biblatex} version 1.5, in order to adhere to the
-author-date specification you will need to use \textsf{Biber} to
-process your .bib files, as \textsc{Bib}\TeX\ (and its more recent
-variants) will no longer provide all the features the style requires.
-For this release, you really need the current versions of
-\textsf{Biber} (2.10) and \textsf{biblatex} (3.10), which contain
-features and bug-fixes on which my own code relies.  The advice that
-follows in this document assumes that you are using \textsf{Biber}; if
-you wish to continue using \textsc{Bib}\TeX\ then you need
-\textsf{biblatex} version 1.4c and \textsf{biblatex-chicago} 0.9.7a.
-\textsf{biblatex-chicago.pdf} if you have any difficulty obtaining a
-copy of this earlier release.)
-
\subsection*{Editions}
\label{editions}

@@ -432,7 +419,8 @@

-Audio: \autocite{greek:filmstrip}; \autocite{weed:flatiron}.
+Audio: \autocite{greek:filmstrip}; \autocite{twain:audio};
+\autocite{weed:flatiron}.

\autocite{cohen:schiff}; \autocite{cotton:manufacture};
@@ -505,7 +493,41 @@

Video: \autocite{cleese:holygrail}; \autocite{hitchcock:nbynw}.

+\subsubsection*{Additions and changes for the 17th edition}
+\label{ed17}

+Article: \autocite{amlen:hoot}; \autocite{black:infectious};
+\autocite{kessler:nyt}; \autocite{saberhagen:beluga};
+\autocite{stoffle:ghost}.
+
+Artwork: \autocite{mccurry:afghangirl}.
+
+Audio: \autocite{danforth:podcast}; \autocite{strayed:audiobook}.
+
+\autocite{gems:print}.
+
+Dataset: \autocite{genbank:db}; \autocite{nasa:db}.
+
+Music: \autocite{naraya}; \autocite{rihanna:umbrella}.
+
+Online: \autocite{diaz:surprise}; \autocite{obrien:recycle};
+\autocites{licis:diazcomment}{diaz:surprise-customc}.
+
+Performance: \autocite{hamilton:miranda}.
+
+Periodical: \autocite{amlen:wordplay}.
+
+Review: blog comment without \texttt{commenton}: \autocite{viv:amlen};
+blog comment with \texttt{commenton}:
+\autocites{ac:comment}{ellis:blog-customc}.
+
+Standard: \autocite{niso:bibref}; \autocite{w3c:xml}.
+
+
% \printshorthands % No longer necessary in author-date.
% \nocite{*}
\printbibliography[notkeyword=nosample,title=References]

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-legal-sample.pdf
===================================================================
(Binary files differ)

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-legal-sample.tex
===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-legal-sample.tex	2020-04-19 23:48:48 UTC (rev 54808)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-legal-sample.tex	2020-04-20 21:05:08 UTC (rev 54809)
@@ -14,9 +14,6 @@
\usepackage{setspace}
\usepackage{vmargin} \setpapersize{A4}
\setmarginsrb{1in}{20pt}{1in}{.5in}{1pt}{2pt}{0pt}{2mm}
-\usepackage{url}
-\urlstyle{rm}
-\appto\bibsetup{\sloppy}
\protected\def\onethird{{\scriptsize\raisebox{.7ex}{1}%
\hspace{-0.1em}\raisebox{.2ex}{/}\hspace{-0.03em}3}}
@@ -37,7 +34,12 @@
\subsection*{Long note forms}
\label{sec:long}
\begin{enumerate}\setlength{\parskip}{-4pt}
-\item Federal case\autocite[145]{federal:case}
+\item Federal case, with a Supreme Court case in running text in the
+  footnote using \verb+\runcite+\footnote{\cite[145]{federal:case}.
+    The court also noted that under
+    \runcite[7]{scotus:case:runningtext}, police may briefly detain a
+    person without probable cause if the officer believes criminal
+    activity \enquote{may be afoot.}  \cite[143]{federal:case}.}
\item Database case\autocite{database:case}
\item Lower federal-court case (with Supreme Court
action)\autocite{federal:lower:related}

===================================================================
(Binary files differ)

Index: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.pdf
===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.pdf	2020-04-19 23:48:48 UTC (rev 54808)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.pdf	2020-04-20 21:05:08 UTC (rev 54809)

Property changes on: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.pdf
___________________________________________________________________
## -0,0 +1 ##
+application/pdf
\ No newline at end of property
===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.tex	                        (rev 0)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.tex	2020-04-20 21:05:08 UTC (rev 54809)
@@ -0,0 +1,272 @@
+\documentclass[a4paper,12pt]{article}
+\usepackage[T1]{fontenc}
+\usepackage{textcomp}
+\usepackage[latin1]{inputenc}
+\usepackage[american]{babel}
+\usepackage[autostyle]{csquotes}
+%\usepackage[document]{ragged2e}
+\usepackage[notes,strict,backend=biber,autolang=other,cmsbreakurl,%
+bibencoding=latin1,booklongxref=false,compresspages,%
+noteref=section,noterefintro=introduction]{biblatex-chicago}
+\usepackage{lmodern}
+\usepackage{gentium}
+%\renewcommand*{\rmdefault}{fgn}% The font (gentium) used for pdf
+\usepackage{ifthen}
+\usepackage{setspace}
+\usepackage{vmargin} \setpapersize{A4}
+\setmarginsrb{1in}{20pt}{1in}{.5in}{1pt}{2pt}{0pt}{6mm}
+\usepackage[split=section]{cmsendnotes}
+% \renewcommand{\footnote}{\endnote}
+\usepackage{multicol}
+\hyphenation{tech-re-port Ap-ril}
+\protected\def\onethird{{\mbox{\scriptsize\raisebox{.7ex}{1}%
+    \hspace{-0.1em}\raisebox{.2ex}{/}\hspace{-0.03em}3}}}
+\setlength{\parindent}{0pt}
+\setlength{\dimen\footins}{9.5in}
+\newcommand{\mycolor}{}%[1]{\textcolor[HTML]{228B22}{#1}}
+\usepackage{xr-hyper}
+\externaldocument[cms-]{biblatex-chicago}%
+\usepackage[pdftex,hyperref,svgnames]{xcolor}
+\makeatletter
+\renewcommand{\section}{\@startsection{section}{1}{\z@}%
+                                     {-3.25ex\@plus -1ex \@minus -.2ex}%
+                                     {1.5ex \@plus .2ex}%
+                                     {\normalfont\large\bfseries}}
+\newrobustcmd*{\cmssecref}[2][]{\marginpar{\href{\@baseurl%
+      \getrefbykeydefault{#2}{anchor}{}}{\small \xA7\,\getrefnumber{#2}}%
+      \ifblank{#1}{}{\scriptsize,\, s.v.\\[1pt]\enquote{#1}}}}%
+\makeatother
+\newcommand{\cmd}[1]{\texttt{\textbackslash #1}}
+\newcommand{\mylittlespace}{\vspace{5pt}}%.5\baselineskip}}
+\bibliography{notes-test}
+%%\onehalfspacing
+%\tracingmacros=1
+\begin{document}
+
+{\Large\bfseries The \texttt{noteref} Option to the Notes \&\
+  Bibliography Style}\label{cms:top}
+\vspace*{1.5ex}
+
+Recent editions of the \emph{Chicago Manual of
+  Style}\autocite[14.31]{chicago:manual} have suggested that, in short
+notes, it may sometimes be helpful to provide a cross-reference to the
+work's initial presentation in a long note, \enquote{especially in the
+  absence of a full bibliography.}  With this release, I have provided
+for this purpose the \texttt{noteref} package option, which
+additionally involves many sub-options and even a new dependent
+\LaTeX\ package \textsf{cmsendnotes.sty} (with its own options) to
+help those users who need the same functionality in endnotes instead
+of footnotes (see page~\pageref{cms:endnotes}).  The full
+documentation in \cmssecref{cms-sec:noteref}
+\textsf{biblatex-chicago.pdf} contains all of the murky details, but
+in this document I wanted to provide straightforward examples so that
+users could get a quick glimpse of the features provided.
+
+\textsf{biblatex-chicago}:
+\begin{verbatim}
+noteref=section,noterefintro=introduction
+\end{verbatim}
+you'll get the following results, in what is obviously a rather
+artificial setting.
+
+\section{Long notes}
+\label{sec:one}
+
+with\autocite{schubert:muellerin} a\autocite{mchugh:wake}
+series\autocite{euripides:orestes} of\autocite{clark:mesopot}
+footnotes\autocite{ashbrook:brain} chosen\autocite{contrib:contrib}
+randomly.\autocite{frede:inproc}
+
+\section{Short notes on the same page}
+\label{sec:two}
+
+New\autocite{chicago:manual} text\autocite{garaud:gatine}
+a\autocite{mchugh:wake}
+series\footnote{\shortrefcite{euripides:orestes}.
+  \textcolor{DarkSlateBlue}{<--- \cmd{shortrefcite} produced this
+    \texttt{noteref} where by default one wouldn't have appeared.}}
+of\autocite{clark:mesopot} footnotes\autocite{ashbrook:brain}
+chosen\autocite{contrib:contrib} randomly.\autocite{frede:inproc}
+
+\mylittlespace Short notes on the same page, or in the same double-page
+spread when in \texttt{twoside} mode, won't by default have a
+\texttt{noteref} printed, though you can in fact alter this on a
+note-by-note basis by using \cmd{shortrefcite} or
+done with the Euripides example below.
+
+\clearpage
+
+\section{Short notes on a new page}
+\label{sec:three}
+
+New\autocite{chicago:manual} text\autocite{garaud:gatine}
+a\autocite{mchugh:wake}
+series\footnote{\shortcite*{euripides:orestes}.
+  \textcolor{DarkSlateBlue}{<--- \cmd{shortcite*} suppressed the
+    \texttt{noteref} where by default one would have appeared.}}
+of\autocite{clark:mesopot} footnotes\autocite{ashbrook:brain}
+chosen\autocite{contrib:contrib} randomly.\autocite{frede:inproc}
+
+\mylittlespace Here \cmssecref[Zero Sections]{cms-sec:zero} all of the
+short notes will, by default, have a \texttt{noteref}.  The first note
+on this page refers back to a long note that occurred \emph{before}
+section~1, technically therefore in section~0, which is what would
+appear without further intervention.  The intervention I have made is
+the option \verb+noterefintro=introduction+, which tells
+\textsf{biblatex-chicago} to print \cmd{bibstring\{introduc\-tion\}}
+instead of \verb+\bibstring{section}+.  The problem of section numbers
+containing zero can be complicated, so once again the murky details
+are in \textsf{biblatex-chicago.pdf}.
+
+\mylittlespace The main \texttt{noteref} option has six possible
+values, four of which are, I would guess, those most likely to prove
+useful: \texttt{none} (the default), \texttt{page}, \texttt{chapter},
+and \texttt{section}, with \texttt{subsection} and \texttt{part} as
+additional possibilities.  The names of the options correspond to the
+\LaTeX\ counter tracked by that option in addition to the note number
+itself, so that \texttt{none} produces a \texttt{noteref} that just
+provides the note number, while \texttt{page} provides page and note
+number, \texttt{chapter} gives chapter and note number, and so on.
+Here, with \texttt{section} being the top-level division in the
+\texttt{article} class, I've used that option.
+
+\mylittlespace You can suppress the appearance of a \texttt{noteref}
+by using the \cmd{shortcite*} or \cmd{shorthandcite*} commands, as
+I've shown with the Euripides citation below.  You can also set the
+\texttt{noterefin\-terval} option to a number greater than zero if you
+want to make sure that a certain number of references have intervened
+before printing a \texttt{noteref}, even if the short note is on a new
+page.  Because this mechanism tracks the \texttt{instcount} counter,
+which is incremented by more things than just new citations, you may
+have to experiment to find a value that suits your document.
+
+\section{A few extra subtleties}
+\label{sec:four}
+
+Another\autocite{jackson:paulina:letter} new\autocite{holiday:fool}
+with\autocite{schubert:muellerin} a\autocite{mchugh:wake}
+series\footnote{\cite{euripides:orestes}.
+  \textcolor{DarkSlateBlue}{<--- The \texttt{noteref} does appear
+    here, following its suppression above.}}
+of\autocite{clark:mesopot} footnotes\autocite{ashbrook:brain}
+chosen\autocite{contrib:contrib} randomly.\autocite{frede:inproc}
+
+\mylittlespace When a \texttt{noteref} for a particular source has
+won't be printed after subsequent citations of the same source that
+appear on that same page.  With the second Euripides note below, the
+\texttt{noteref} \emph{does} appear because it was suppressed after
+the first reference.
+
+\clearpage
+
+Another\footnote{\cite{jackson:paulina:letter}.
+  \textcolor{DarkSlateBlue}{<--- The form of this \texttt{noteref} and
+    the next indicates that the short notes are in the same section as
+    the long notes to which they refer. Set \texttt{fullnoterefs=true}
+    to get the long form everywhere.}} new\autocite{holiday:fool}
+with\autocite{schubert:muellerin} a\autocite{mchugh:wake}
+series\autocite{euripides:orestes} of\autocite{clark:mesopot}
+footnotes\autocite{ashbrook:brain} chosen\autocite{contrib:contrib}
+randomly.\autocite{frede:inproc}
+
+\mylittlespace Once again, after a page break, the \texttt{noterefs}
+appear after all of these short notes.  Because the section number
+hasn't changed, however, the first two footnotes on the page, which
+refer back to long footnotes in the same section, have
+\texttt{noterefs} containing only the note number.  This more
+compact form is the default, but you can set \texttt{fullnoterefs} to
+form everywhere.
+% and should be unambiguous unless you restart footnote
+% numbering inside the section rather than at section boundaries.
+
+\section{Endnotes}
+\label{cms:endnotes}\citereset
+
+Things are \cmssecref[Endnotes]{cms-sec:endnoterefs}
+slightly more complicated when you are using endnotes instead of
+footnotes, but in standard cases it's still fairly straightforward.
+In this document I have added the line:
+\begin{verbatim}
+\usepackage[split=section]{cmsendnotes}
+\end{verbatim}
+the options shown on page~\pageref{cms:top}), then printed the
+endnotes below with \textsf{cmsendnotes'}
+\begin{verbatim}
+\theendnotesbypart
+\end{verbatim}
+command.  As this shows you can, as usual with \textsf{biblatex}, mix
+foot- and endnotes in the same document, but if \texttt{noterefs} are
+going to appear in both sorts of note --- surely this situation is
+highly unlikely --- then you need to be careful that they refer back
+\emph{only} to long references in the \emph{same} sort of note.  A
+\texttt{noteref} from an endnote to a long citation in a footnote will
+be inaccurate, so careful use of the \cmd{citereset} command (as here)
+or perhaps of the \textsf{biblatex} \texttt{citereset} option should
+allow you to keep the two sorts of note distinct.
+
+\mylittlespace Text\endnote{\autocite{garaud:gatine}.}
+with\endnote{\autocite{schubert:muellerin}.}
+a\endnote{\autocite{mchugh:wake}.}
+series\endnote{\autocite{euripides:orestes}.}
+of\endnote{\autocite{clark:mesopot}.}
+endnotes\endnote{\autocite{ashbrook:brain}.}
+chosen\endnote{\autocite{contrib:contrib}.}
+randomly.\endnote{\autocite{frede:inproc}.}
+
+\section{More endnotes}
+\label{sec:moreen}
+
+Text\endnote{\global\toggletrue{cms at forcenoteref}\autocite{garaud:gatine}.
+  \textcolor{DarkSlateBlue}{<--- Page \enquote{break} before this note.}}
+with\endnote{\autocite{schubert:muellerin}.}
+a\endnote{\autocite{mchugh:wake}.}
+series\endnote{\autocite{euripides:orestes}.}
+of\endnote{\autocite{clark:mesopot}.}
+endnotes\endnote{\autocite{ashbrook:brain}.}
+chosen\endnote{\autocite{contrib:contrib}.}
+randomly.\endnote{\autocite{frede:inproc}.}
+
+\mylittlespace When you peruse the endnotes on the next page, please
+remember that I've simulated a page change in between the two
+sections, thus allowing all the \texttt{noterefs} to appear as they
+do.  The rules about them appearing (or not) on the same page as the
+long reference to which they point are the same as for footnotes, so
+long as you keep in mind that the pages under consideration here are
+those in the endnotes section itself, \emph{not} in the main text.
+Also, in this case the standard \cmd{notesname} command provides
+alternative text for the general header, but \textsf{cmsendnotes.sty}
+organizes the subheaders and facilitates the \texttt{noterefs}, all
+without further intervention from you beyond the single option already
+given to that package.
+
+\mylittlespace I hope that this short demonstration is enough to get
+you started using the \texttt{noteref} functionality.  I admit that
+the processing time for documents using it is somewhat increased, so
+if you have a long document it may require some extra patience.  If
+something doesn't work properly for you, and the main documentation
+doesn't clear up the issue, please let me know.
+
+\def\notesname{Endnotes to \S\S~5--6}
+\theendnotesbypart
+
+\end{document}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:

Property changes on: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-noteref-demo.tex
___________________________________________________________________
## -0,0 +1 ##
+native
\ No newline at end of property
Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-notes-intro.pdf
===================================================================
(Binary files differ)

Modified: trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-notes-intro.tex
===================================================================
--- trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-notes-intro.tex	2020-04-19 23:48:48 UTC (rev 54808)
+++ trunk/Master/texmf-dist/doc/latex/biblatex-chicago/cms-notes-intro.tex	2020-04-20 21:05:08 UTC (rev 54809)
@@ -6,8 +6,9 @@
\usepackage[american]{babel}
\usepackage[autostyle]{csquotes}
%\usepackage[document]{ragged2e}
-\usepackage[notes,strict,backend=biber,autolang=other,%
-bibencoding=latin1,booklongxref=false,annotation]{biblatex-chicago}
+\usepackage[notes,strict,backend=biber,autolang=other,cmsbreakurl,%
+bibencoding=latin1,booklongxref=false,annotation,%
+compresspages]{biblatex-chicago}
\usepackage{lmodern}
\usepackage{gentium}
%\renewcommand*{\rmdefault}{fgn}% The font (gentium) used for pdf
@@ -15,25 +16,31 @@
\usepackage{setspace}
\usepackage{vmargin} \setpapersize{A4}
\setmarginsrb{1in}{20pt}{1in}{.5in}{1pt}{2pt}{0pt}{6mm}
-\makeatletter
-\renewcommand{\@makeenmark}{\textcolor{DarkSlateGrey}{\textsf{\@theenmark}}}
-\makeatother
-\usepackage{url}
-\urlstyle{rm}
-\appto\bibsetup{\sloppy}
-\hyphenation{tech-re-port}
+% \usepackage{url}
+% \urlstyle{rm}
+% \appto\bibsetup{\sloppy}
+\usepackage{multicol}
+\hyphenation{tech-re-port Ap-ril}
\protected\def\onethird{{\mbox{\scriptsize\raisebox{.7ex}{1}%
\hspace{-0.1em}\raisebox{.2ex}{/}\hspace{-0.03em}3}}}
\setlength{\parindent}{0pt}
%\setlength{\parskip}{5pt}
\setlength{\dimen\footins}{9.5in}
+\setcounter{secnumdepth}{-1}
\newcommand{\mycolor}{}%[1]{\textcolor[HTML]{228B22}{#1}}
\usepackage{xr-hyper}
-\externaldocument[cms-]{../../Docs/biblatex-chicago}%
+\externaldocument[cms-]{biblatex-chicago}%
\usepackage[pdftex,hyperref,svgnames]{xcolor}
+\makeatletter
+\renewcommand{\@makeenmark}{\textcolor{DarkSlateGrey}{\textsf{\@theenmark}}}
+\renewcommand{\section}{\@startsection{section}{1}{\z@}%
+                                     {-3.25ex\@plus -1ex \@minus -.2ex}%
+                                     {1.5ex \@plus .2ex}%
+                                     {\normalfont\large\bfseries}}
+\makeatother
\usepackage{cmsdocs}
\newcommand{\cmd}[1]{\texttt{\textbackslash #1}}
\newcommand{\mylittlespace}{\vspace{5pt}}%.5\baselineskip}}
@@ -42,29 +49,36 @@
%\tracingstats=2
\begin{document}

-\section*{The Chicago Notes \&\ Bibliography Specification}
-\label{sec:spec}
+{\Large\bfseries The Chicago Notes \&\ Bibliography Specification}
+\vspace*{1.5ex}
+\begin{multicols}{2}
+  \renewcommand{\contentsname}{\textcolor{darkgray}{Contents}}
+  \footnotesize
+  \tableofcontents
+\end{multicols}

This file is intended as a brief introduction to the Chicago notes \&\
-bibliography specification (16th ed.)\autocite{chicago:manual}\ as
+bibliography specification (17th ed.)\autocite{chicago:manual}\ as
implemented by \textsf{biblatex-chicago}, and falls somewhere in
between the \enquote{Quickstart} section of
\textsf{biblatex-chicago.pdf} and the full documentation as presented
-in section~4 \cmssecref{cms-sec:Spec} of that same document.  I've
-attempted to design this introduction for ease of cross-reference, so
-clicking on long-note citations should bring you to the bibliography
-entry, whence clicking on the entry key in the annotation should
-present you with the entry as it appears in the .bib file, where
-clicking on the entry type should return you to the long note.  If you
-have questions beyond the scope of this introduction, then the full
-documentation is the place to look next --- marginal notes here refer
-to section or page numbers there, and if you've installed the package
-using the standard \TeX\ Live method then clicking on these marginal
-notes should take you to the other document.  If you can't find
-\textsf{biblatex-chicago.pdf}.
+in section~4 \cmssecref{cms-sec:Spec} of that same document.  Please
+note that the package functionality as described here depends on using
+\textsf{biber} as your backend; if you use a different backend the
+results will inevitably be disappointing.  I've attempted to design this
+introduction for ease of cross-reference, so clicking on long-note
+citations should bring you to the bibliography entry, whence clicking
+on the entry key in the annotation should present you with the entry
+as it appears in the .bib file, where clicking on the entry type
+should return you to the long note.  If you have questions beyond the
+scope of this introduction, then the full documentation is the place
+to look next --- marginal notes here refer to section or page numbers
+there, and if you've installed the package using the standard \TeX\
+Live method then clicking on these marginal notes should take you to
+the other document.  If you can't find answers there, please write to
+me at the email address in \textsf{biblatex-chicago.pdf}.

-\subsection*{Standard entry types}
+\section{Standard entry types}
\label{sec:standard}

\begin{refsection}
@@ -88,7 +102,7 @@
annotations)]
\end{refsection}

-\subsection*{Other entry types}
+\section{Other entry types}
\label{sec:other}

\begin{refsection}
@@ -101,10 +115,13 @@
\endnote[\value{Audio}]{\cite{schubert:muellerin}.},
\endnote[\value{BookInBook}]{\cite{euripides:orestes}.},
+  \endnote[\value{Dataset}]{\cite{genbank:db}.},
\endnote[\value{InReference}]{\cite{wikiped:bibtex}.},
\endnote[\value{Letter}]{\cite{jackson:paulina:letter}.},
\endnote[\value{Music}]{\cite{holiday:fool}.},
+  \endnote[\value{Performance}]{\cite{hamilton:miranda}.},
\endnote[\value{Review}]{\cite{ratliff:review}.},
+  \endnote[\value{Standard}]{\cite{niso:bibref}.},
\endnote[\value{SuppBook}]{\cite{polakow:afterw}.}, and
\endnote[\value{Video}]{\cite{friends:leia}.}.

@@ -112,7 +129,7 @@
\printbibliography[title=\normalsize Bibliography Style]
\end{refsection}

-\subsection*{Short notes}
+\section{Short notes}
\label{sec:short}

\begin{refsection}
@@ -126,8 +143,13 @@
you load \textsf{biblatex-chicago} and you'll get the short form
from the start, something only recommended by the \emph{CMS} when
you have a full bibliography to clarify all the abbreviated
-  references.  The following are the short forms of all the works
-  cited in long notes in previous sections:
+  references.  (In the absence of a full bibliography, you can also
+  use the \texttt{noteref} option \cmssecref{cms-sec:noteref} to
+  provide cross-references from short notes to long ones.  Please
+  consult
+  \href{file:cms-noteref-demo.pdf}{\textsf{cms-noteref-demo.pdf}}.)
+  The following are the short forms of all the works cited in long
+  notes in previous sections:
\endnote[\value{Article}]{\shortcite{garaud:gatine}.},
\endnote[\value{Audio}]{\shortcite{schubert:muellerin}.},
@@ -134,6 +156,7 @@
\endnote[\value{Book}]{\shortcite{mchugh:wake}.},
\endnote[\value{BookInBook}]{\shortcite{euripides:orestes}.},
\endnote[\value{Booklet}]{\shortcite{clark:mesopot}.},
+  \endnote[\value{Dataset}]{\shortcite{genbank:db}.},
\endnote[\value{InBook}]{\shortcite{ashbrook:brain}.},
\endnote[\value{InCollection}]{\shortcite{contrib:contrib}.},
\endnote[\value{InProceedings}]{\shortcite{frede:inproc}.},
@@ -142,7 +165,9 @@
\endnote[\value{Manual}]{\shortcite{dyna:browser}.},
\endnote[\value{MastersThesis}]{\shortcite{ross:thesis}.},
\endnote[\value{Music}]{\shortcite{holiday:fool}.},
+  \endnote[\value{Performance}]{\shortcite{hamilton:miranda}.},
\endnote[\value{Review}]{\shortcite{ratliff:review}.},
+  \endnote[\value{Standard}]{\shortcite{niso:bibref}.},
\endnote[\value{SuppBook}]{\shortcite{polakow:afterw}.},
\endnote[\value{TechReport}]{\shortcite{herwign:office}.},
@@ -151,7 +176,7 @@
{\renewcommand{\notesname}{\normalsize Short-Note Style} \theendnotes}
\end{refsection}

-\subsection*{The \textsf{entrysubtype} field}
+\section{The \textsf{entrysubtype} field}
\label{sec:subtype}

\begin{refsection}
@@ -170,17 +195,17 @@
\endnote[\value{Article}]{\cite{lakeforester:pushcarts}.} and
\endnote[\value{Review}]{\cite{bundy:macneil}.}.

-  \mylittlespace The \textsf{Misc} type provides a second
-  differentiating function for the \textsf{entrysubtype} field.
-  Without such a field, \textsf{Misc} entries function as they do in
-  standard \textsf{biblatex} and in \textsc{Bib}\TeX, that is, as
-  hold-alls for sources that won't easily fit into other categories.
-  (Ideally, such entries will be very rare when using
-  \textsf{biblatex-chicago}.)  With an \textsf{entrysubtype},
-  \textsf{Misc} entries will present their source as part of an
-  unpublished archive, to be distinguished from \textsf{Unpublished}
-  entries, which usually will have a specific title and won't come
-  from a named archive:
+  \mylittlespace The \textsf{Misc} type likewise uses the
+  \textsf{entrysubtype} field as a toggle to alter the general
+  presentation of a source.  Without such a field, \textsf{Misc}
+  entries function as they do in standard \textsf{biblatex} and in
+  \textsc{Bib}\TeX, that is, as hold-alls for sources that won't
+  easily fit into other categories.  (Ideally, such entries will be
+  very rare when using \textsf{biblatex-chicago}.)  With an
+  \textsf{entrysubtype} \textsf{Misc} entries will present their
+  source as part of an unpublished archive, to be distinguished from
+  \textsf{Unpublished} entries, which usually will have a specific
+  title and won't come from a named archive:

\mylittlespace The \textsf{entrysubtype} field is, finally, also
@@ -199,7 +224,7 @@
\printbibliography[title=\normalsize Bibliography Style]
\end{refsection}

-\subsection*{Abbreviated references }
+\section{Abbreviated references }
\label{sec:abbrev}

\begin{refsection}
@@ -248,38 +273,49 @@
\printbibliography[title=\normalsize Bibliography Style]
\end{refsection}

-\subsection*{Online materials}
+\section{Online materials}
\label{sec:online}

\begin{refsection}

-  With \cmssecref[online]{cms-sec:online} online sources, the
-  \emph{CMS} emphasizes the nature of the source rather more than the
-  place where that source is found.  This means, for example, that an
-  online edition of a book calls for a
-  intrinsically online source, if it is structured more or less like a
-  conventional printed periodical, may demand an
-  \endnote[\value{Article}]{\cite{stenger:privacy}.} or
-  \textsf{Review} entry rather than an \textsf{Online} one.  Blogs
-  lend themselves well to the
+  The \cmssecref[online]{cms-sec:online} 17th edition of the
+  \emph{CMS} has extended its treatment of online sources, and has
+  also somewhat altered the principles of that treatment.  Earlier
+  editions emphasized the nature of the source (book-like,
+  journal-like, etc.), rather more than how that source was accessed
+  (printed volume, online, etc.), whereas the current specification
+  places somewhat greater --- though not total --- emphasis on where
+  it was accessed, which can in many cases determine what sort of
+  entry type you need.  I have provided a quick guide to the
+  correspondences between online materials and
+  \textsf{biblatex-chicago} entry types in table~1
+  \cmstabref{cms-tab:online:types} of \textsf{biblatex-chicago.pdf},
+  and include a few examples here.  An online edition of a printed
+  book still calls for a
+  rules are similar for a printed journal that has an online portal.
+  For intrinsically online sources, even if they are structured more
+  or less like a conventional printed periodical, you may (at your
+  discretion) choose to present them in an
+  \endnote[\value{Online}]{\cite{stenger:privacy}.}  entry rather than
+  an \textsf{Article} one.  Blogs lend themselves well to the
\endnote[\value{Article}]{\cite{ellis:blog}.} type, while a comment
-  on a blog becomes a
-  \endnote[\value{Review}]{\cite{ac:comment}.}.  For things like
-  mailing lists or less journalistic web pages, the
+  on a blog becomes a \endnote[\value{Review}]{\cite{ac:comment}.},
+  here using the \texttt{commenton} \textsf{relatedtype}.  Social
+  media posts, by contrast, even of photographs, for example, need an
+  \endnote[\value{Online}]{\cite{souza:obama}.} entry.  For things
+  like mailing lists or less journalistic web pages, the
\endnote[\value{Online}]{\cite{powell:email}.} type works well, as
it does for short online videos
(\endnote[\value{Online}]{\cite{pollan:plant}.}) and for short
online audio pieces, too:
-  \endnote[\value{Online}]{\cite{coolidge:speech}.}.  (Some of these
-  latter also work well in a \textsf{Misc} entry with an
-  \textsf{entrysubtype}.)
+  \endnote[\value{Online}]{\cite{coolidge:speech}.}.

{\renewcommand{\notesname}{\normalsize Note Style} \theendnotes}
\printbibliography[title=\normalsize Bibliography Style]
\end{refsection}

-\subsection*{Related entries}
+\section{Related entries}
\label{sec:related}

\begin{refsection}
@@ -290,17 +326,24 @@
long notes, while \textsf{biblatex-chicago} offers both this
functionality and some Chicago-specific variants which employ
different means.  You can find a full discussion of this in
-  \textsf{biblatex-chicago.pdf}, but one of the entries already cited
-  in the previous section (\cmslink{coolidge:speech}) presents the two
-  entries together in both notes and bibliography, whereas a second
-  example places a text and its translation together, but only in the
-  bibliography: \endnote[\value{Book}]{\cite{furet:related}.}.
+  \textsf{biblatex-chicago.pdf}, but two of the entries already cited
+  in the previous section (\cmslink{coolidge:speech} \&\
+  \cmslink{ac:comment}) present the two related entries together in
+  both notes and bibliography, whereas a third example places a text
+  and its translation together, but only in the bibliography:
+  \endnote[\value{Book}]{\cite{furet:related}.}.  Another example
+  shows how to present multi-volume works with the \textsf{maintitle}
+  \emph{before} the \textsf{booktitle} using the \texttt{maintitle}
+  \textsf{relatedtype}, as is sometimes recommended by the \emph{CMS}:
+  \endnote[\value{BookInBook}]{\cite{plato:timaeus:gr}.}.  (The
+  shows the more traditional presentation syntax.)

{\renewcommand{\notesname}{\normalsize Note Style} \theendnotes}
\printbibliography[title=\normalsize Bibliography Style]
\end{refsection}

-\subsection*{Citation commands}
+\section{Citation commands}
\label{sec:citation}

\begin{refsection}
@@ -333,7 +376,7 @@
%  \printbibliography[title=\large Bibliography Style]
\end{refsection}

-\subsection*{In conclusion}
+\section{In conclusion}
\label{sec:conclude}

Allow me, finally, to emphasize just how multifarious are the sources
@@ -367,12 +410,13 @@
\begin{lstlisting}[language=BiBTeX,label=ac:comment]
*\lnbackref{Review}{6}*{ac:comment,
entrysubtype = {magazine},
-  date = 	 {2008-06-30},
author = 	 {AC},
-  eventdate = 	 {2008-07-01},
-  title = 	 {comment on Rhian Ellis, \mkbibquote{Squatters' Rights}}
+  eventdate = 	 {2008-07-01T10:18:00},
+    {ellis:blog}{anchor}{}}{\colorbox{Gainsboro}{ellis:blog}}*},
+  relatedtype =  {commenton},
+  url =          {http://wardsix.blogspot.com/2008
+    /06/squatters-rights.html}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=ashbrook:brain]
@@ -401,10 +445,10 @@
\begin{lstlisting}[language=BibTeX,label=chicago:manual]
title = 	 {The Chicago Manual of Style},
-  year = 	 2010,
+  year = 	 2017,
author = 	 {{University of Chicago Press}},
publisher = uchp,
-  edition = 	 16,
+  edition = 	 17,
location =  {Chicago}
}
\end{lstlisting}
@@ -414,7 +458,7 @@
subtitle = 	 {Between Two Rivers},
author = 	 {Hazel V. Clark},
howpublished = {End of the Commons General Store},
-  year = 	 {\mkbibbrackets{1957?}},
+  date = 	 {1957?},
location =     {Mesopotamia, OH}
}
\end{lstlisting}
@@ -438,8 +482,9 @@
-  year = 	 {ca.\,1920}
+    nodates=false},
+  date = 	 {1920~}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=creel:house]
@@ -467,7 +512,7 @@
title = 	 {By Rail and Stage to Galena},
{anchor}{}}{\{\colorbox{Gainsboro}{prairie:state}\}}*,
-  pages = 	 {271--79}
+  pages = 	 {271--279}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=ellis:blog]
@@ -561,6 +606,32 @@
shorttitle =	 {Recherches sur les d\xE9frichements}
}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=genbank:db]
+*\lnbackref{Dataset}{2}*{genbank:db,
+  author = 	 {GenBank},
+  title = 	 {for RP11-322N14 BAC},
+  number = 	 {AC087526.3},
+  type = 	 {accession number},
+  url = 	 {http://www.ncbi.nlm.nih
+      .gov/nuccore/19683167},
+  urldate = 	 {2016-04-06}
+}
+\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=hamilton:miranda]
+*\lnbackref{Performance}{2}*{hamilton:miranda,
+  editor = 	 {Miranda, Lin-Manuel},
+  editortype = 	 {music and lyrics by},
+  editoratype =  {director},
+  editorbtype =  {choreographer},
+  editora = 	 {Kail, Thomas},
+  editorb = 	 {Blakenbuehler, Andy},
+  venue = 	 {Richard Rodgers Theatre},
+  title = 	 {Hamilton},
+  date = 	 {2016-02-02},
+  options = 	 {useeditor=false},
+  location =     {New York, NY}
+}
+\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=harley:ancient:cart]
*\lnbackref{Collection}{5}*{harley:ancient:cart,
title = 	 {Cartography in Prehistoric, Ancient, and Medieval Europe and the Mediterranean},
@@ -597,10 +668,9 @@
author = 	 {{van} Herwijnen, Eric},
title = 	 {Future Office Systems Requirements},
institution =  {CERN DD internal note},
-  year = 	 1988,
-  month = 	 11
+  date = 	 {1988-11}
}
-\end{lstlisting}\enlargethispage{-\baselineskip}
+\end{lstlisting}%\enlargethispage{-\baselineskip}
\begin{lstlisting}[language=BibTeX,label=holiday:fool]
*\lnbackref{Music}{2}*{holiday:fool,
title = 	 {I'm a Fool to Want You},
@@ -609,7 +679,8 @@
author = 	 {Herron, Joel and Sinatra, Frank and Wolf, Jack},
editor = 	 {Holiday, Billie},
-  editortype = 	 {none},
+  editortype = 	 {vocalist},
+  chapter =      1,
number = 	 {CL 1157},
publisher = {Columbia},
type = 	 {33\onethird~rpm},
@@ -667,7 +738,7 @@
title = 	 {Madonna of the Rocks},
type = 	 {oil on canvas},
institution =  {Louvre},
-  year = 	 {1480s},
+  date = 	 {148X},
note = 	 {78 x 48.5 in\adddot},
location =  {Paris}
}
@@ -695,11 +766,26 @@
author = 	 {Nass, Clifford},
title = 	 {Why Researchers Treat On-Line Journals Like Real People},
-  note =  {keynote address, annual meeting of the Council of Science Editors},
+  eventtitle =   {annual meeting of the Council of Science Editors},
location = 	 {San Antonio, TX},
-  date = 	 {2000-05-06/2000-05-09}
+  eventdate = 	 {2000-05-06/2000-05-09}
}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=niso:bibref]
+*\lnbackref{Standard}{2}*{niso:bibref,
+  title = 	 {Bibliographic References},
+  organization = {National Information Standards Organization},
+  userd = 	 {approved},
+  howpublished = {reaffirmed},
+  eventdate =    {2010-05-13},
+  date = 	 {2005-06-09},
+  series = 	 {ANSI/NISO},
+  number =       {Z39.29-2005},
+  publisher =    {NISO},
+  location =     {Bethesda, MD}
+}
+\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=plato:republic:gr]
*\lnbackref{BookInBook}{4}*{plato:republic:gr,
title = 	 {Republic},
@@ -716,6 +802,46 @@
location =  {Oxford}
}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=plato:timaeus:gr]
+*\lnbackref{BookInBook}{7}*{plato:timaeus:gr,
+  title = 	 {Timaeus},
+  date = 	 1902,
+{plato:total}{anchor}{}}{\colorbox{Gainsboro}{plato:total}}*},
+  relatedtype =  {maintitle},
+  pages = 	 {17--105},
+  author = 	 {Plato},
+  entrysubtype = {classical}
+}
+\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=plato:tomeiv]
+  title = 	 {Clitopho, Res Publica, Timaeus, Critias},
+  date = 	 1902,
+  maintitle = 	 {Opera},
+  volume = 	 4,
+  author = 	 {Plato},
+  editor = 	 {Burnet, J.},
+  publisher =    {Clarendon Press},
+  location =     {Oxford}
+}
+\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=plato:total]
+  author = 	 {Plato},
+  title = 	 {Opera},
+  year = 	 1902,
+{plato:tomeiv}{anchor}{}}{\colorbox{Gainsboro}{plato:tomeiv}}*},
+  editor = 	 {Burnet, J.},
+  relatedtype =  {maintitle},
+  volumes = 	 5,
+  options = 	 {hidevolumes=false},
+  series = 	 {Oxford Classical Texts},
+  publisher =    {Clarendon Press},
+  location =     {Oxford}
+}
+\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=polakow:afterw]
*\lnbackref{SuppBook}{2}*{polakow:afterw,
author =	 {Polakow, Valerie},
@@ -733,11 +859,11 @@
author = 	 {Pollan, Michael},
title = {Michael Pollan Gives a Plant's-Eye View},
organization = {TED video, 17:31},
-  url = 	 {http://www.ted.com/index.php/
-        talks/michael_pollan_gives_a_
-        plant_s_eye_view.html},
+  titleaddon =   {filmed March 2007},
+  url = 	 {http://www.ted.com/index.php
+        /talks/michael_pollan_gives_a
+        _plant_s_eye_view.html},
urldate = 	 {2008-02},
-  date = 	 {2007-03},
userd = 	 {posted}
}
\end{lstlisting}
@@ -745,9 +871,12 @@
*\lnbackref{Online}{6}*{powell:email,
author = 	 {Powell, John},
date = 	 {1998-04-23},
-  titleaddon = {e-mail to Grapevine mailing list},
-  url =        {http://www.electriceditors.net/ grapevine/issues/83.txt},
-  shorttitle =  {\autocap{e}-mail to Grapevine mailing list}
+  titleaddon =   {Grapevine digest mailing list archives},
+  organization = {Electric Editors},
+  title =        {Pattern Matching},
+  url =          {http://www.electriceditors.net
+       /grapevine/archives.php},
+  shorttitle =   {\autocap{e}-mail to Grapevine mailing list}
}
\end{lstlisting}
\begin{lstlisting}[language=BibTeX,label=prairie:state]
@@ -791,16 +920,32 @@
date = 	 1895,
shorttitle = 	 {Das Wandern},
booktitle = 	 {Die sch\"one M\"ullerin (The Maid of the Mill)},
-  maintitle = 	 {First Vocal Album \mkbibemph{(for high voice)}},
+  maintitle = 	 {First Vocal Album},
+  maintitleaddon = {(for high voice)},
author = 	 {Schubert, Franz},
publisher = {G.~Schirmer},
}
\end{lstlisting}
+\begin{lstlisting}[language=BibTeX,label=souza:obama]
+*\lnbackref{Online}{6}*{souza:obama,
+  author = 	 {Souza, Pete},
+  title = 	 {President Obama bids farewell
+         to President Xi of China at the
+         conclusion of the Nuclear
+         Security Summit},
+  date = 	 {2016-04-01},
+  shorttitle = 	 {President Obama},
\begin{l