biblatex-chicago (7jun16)

git-svn-id: svn://tug.org/texlive/trunk@41351 c570f23f-e606-0410-a88d-b1316a301751

1 files changed, 3128 insertions, 2187 deletions

diff --git a/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.tex b/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.tex
index 8f8916cb6b5..30aa780e2e2 100644
--- a/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.tex
+++ b/Master/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.tex
@@ -14,6 +14,7 @@
 \setmarginsrb{1.65in}{.9in}{1.75in}{.6in}{0pt}{0pt}{12pt}{24pt}
 \setlength{\marginparwidth}{1in}
 \usepackage[colorlinks,urlcolor=blue,linkcolor=blue]{hyperref}
+\usepackage{lmodern}
 \usepackage[osf]{mathpazo}
 \usepackage[scaled]{helvet}
 \usepackage[pdftex]{xcolor}
@@ -63,7 +64,7 @@
   Style files for biblatex
 
 \vspace{.3\baselineskip}
-\sffamily\normalsize\bfseries David Fussner\qquad Version 0.9.9i (beta) \\
+\sffamily\normalsize\bfseries David Fussner\qquad Version 1.0rc1 (beta) \\
 \href{mailto:djf027@googlemail.com}{djf027@googlemail.com}\\ \today
 
 \end{center} 
@@ -77,29 +78,32 @@
 \section{Notice}
 \label{sec:Notice}
 
-\textbf{Please be advised that this package is beta software.  Philipp
-  Lehman's \textsf{biblatex} package has now reached a stable state,
-  and is unlikely to require wholesale changes to styles written for
-  it.  The \textsf{biblatex-chicago} package has, for the last few
-  releases, implemented the 16th edition of the \emph{Chicago Manual
-    of Style}.  I am, at the moment, barely maintaining the
-  15th-edition files for those who need or want them.  I have marked
-  them as \enquote{strongly deprecated,} and I encourage all users to
-  switch to the newer specification, which is receiving just about all
-  of my development time.  If the title-formatting changes in the
-  author-date style have been an obstacle, please note that the
-  \textsf{authordate-trad} style keeps the traditional title
-  formatting but switches everything else to the 16th-edition spec.  I
-  have summarized the changes between the two editions in
-  section~\ref{sec:history} below, especially the ones that may
-  require alterations to your .bib files.  (The 15th-edition
+\textbf{Please be advised that this package is beta software.  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}.  I am, with this release,
+  marking the 15th-edition files as \enquote{obsolete,} and I have
+  ceased providing them with any bug fixes or upgrades.  I have
+  included them in the} \texttt{obsolete} \textbf{subdirectory of the
+  package, but I very strongly encourage all users to switch to the
+  newer specification, which is receiving all of my development time.
+  If the title-formatting changes in the author-date style have been
+  an obstacle, please note that the \textsf{authordate-trad} style
+  keeps the traditional title formatting but switches everything else
+  to the 16th-edition spec.  I have summarized the changes between the
+  two editions in section~\ref{sec:history} below, especially the ones
+  that may require alterations to your .bib files.  (The 15th-edition
   documentation is still available, also, in
   \textsf{biblatex-chicago15.pdf}.)  I also 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\\
-  I have tried to implement as much of the \emph{Manual's}
+  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.  One
   user has recently argued that I should attempt to include legal
   citations, so in the long term it may be that I return to this
@@ -117,6 +121,7 @@ properly with this release.  If you are new to these styles, please
 read on.
 
 \section{Quickstart}
+\label{quickstart}
 \reversemarginpar
 
 The \textsf{biblatex-chicago} package is designed for writers who wish
@@ -135,19 +140,25 @@ author-date styles produce a short, in-text citation inside
 parentheses --- (Author Year) --- keyed to a list of references where
 entries start with the same name and year.
 
-\enlargethispage{-\baselineskip}
+%\enlargethispage{-\baselineskip}
 
 \mylittlespace The documentation you are reading covers all three of
-these Chicago styles and their variants.  Much of what follows is
-relevant to all users, but I have decided, after some experimentation,
-to keep the instructions for the two author-date styles separate from
-those pertaining to the notes \&\ bibliography style, at least in
-sections~\ref{sec:Spec} and \ref{sec:authdate}.  Information provided
-under one style will often duplicate that found under the other, but
-efficiency's loss should, I hope, be clarity's gain, and much of what
-you learn using one style will be applicable without alteration to the
-other.  Within the author-date section, the \textsf{authordate-trad}
-information really only appears separately in
+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,
+\mycolor{\textsf{cms-notes-intro.pdf}} or
+\mycolor{\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 decided, after some
+experimentation, to keep the instructions for the two author-date
+styles separate from those pertaining to the notes \&\ bibliography
+style, at least in sections~\ref{sec:Spec} and \ref{sec:authdate}.
+Information provided under one style will often duplicate that found
+under the other, but efficiency's loss should, I hope, be clarity's
+gain, and much of what you learn using one style will be applicable
+without alteration to the other.  Within the author-date section, the
+\textsf{authordate-trad} information really 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
@@ -157,13 +168,11 @@ release.
 \textsf{biblatex-chicago}:
 
 \begin{itemize}{}{}
-\item Philipp Lehman's \textsf{biblatex} package, of course!  The
-  current version(s) --- 1.7 or 3.4 at the time of writing --- work
-  well, but the older 2.9a has been somewhat more extensively tested,
-  so please try it if you have any issues with the latest
-  \textsf{biblatex}.  Both of these versions contain features and bug
-  fixes upon which my code relies.  Lehman's tools require several
-  packages, and he strongly recommends several more:
+\item The \textsf{biblatex} package, of course!  The current version
+  --- 3.4 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:
   \begin{itemize}{}{}
   \item e-\TeX\ (required)
   \item \textsf{etoolbox} --- available from CTAN (required)
@@ -185,12 +194,12 @@ release.
     in particular its enhanced handling of cross references, you must
     use the following:
   \item \textsf{Biber} --- the next-generation \textsc{Bib}\TeX\
-    replacement, which is available from SourceForge.  You should use
-    the latest version, 2.5, to work with \textsf{biblatex} 3.4 and
-    \textsf{biblatex-chicago} (or \textsf{Biber} 1.9 with
-    \textsf{biblatex} 2.9a), 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-sample.pdf} and, for example, the
+    replacement by Philip Kime and François Charette, available from
+    SourceForge.  You should use the latest version, 2.5, to work with
+    \textsf{biblatex} 3.4 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
+    \mycolor{\textsf{cms-dates-intro.pdf}} and, for example, the
     \textsf{crossref} documentation in section~\ref{sec:entryfields},
     below, for more details.
   \end{itemize}
@@ -209,20 +218,18 @@ release.
       backend=biber]\{biblatex-chicago\}}
   \end{quote}
 
-  to load the traditional variant of the author-date style.  (You can
-  use \texttt{notes15} or \texttt{authordate15} to load the
-  15th-edition styles.  Please see \textsf{bibla\-tex-chicago15.pdf}
-  for the details.)  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 number of other parameters
-  automatically.  You can also load the package via the usual
-  \cmd{usepackage\{biblatex\}}, adding either
-  \texttt{style=chicago\-notes} or \texttt{style=chicago-authordate},
-  but this is mainly for those, probably experienced users, who wish
-  to set much of the low-level formatting of their documents
-  themselves.  Please see sections~\ref{sec:loading} and
-  \ref{sec:loading:auth} below for a fuller discussion of the issues
-  involved here.
+  to load the traditional variant of the author-date style.  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 \cmd{usepackage\{bibla\-tex\}},
+  adding either \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 themselves.  Please see
+  sections~\ref{sec:loading} and \ref{sec:loading:auth} below for a
+  fuller discussion of the issues involved here.
 \item You can use \cmd{usepackage[notes,short]\{biblatex-chicago\}} to
   get the short note format even in the first reference of a notes \&\
   bibliography document, letting the bibliography provide the full
@@ -240,11 +247,13 @@ release.
   should work, too, but I haven't tested it.)  As before,
   \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 now provides (at least partial)
-  support for British, Finnish, French, German, Icelandic, and
-  Norwegian.  Please see below (section~\ref{sec:international}) for a
-  fuller explanation of all the options.
-\item \textsf{chicago-auth\-ordate.cbx},
+  \textsf{Biblatex-chicago} also provides (at least partial) support
+  for British, Finnish, French, German, Icelandic, Norwegian, and
+  \mycolor{Swedish}.  Please see below
+  (section~\ref{sec:international}) for a fuller explanation of all
+  the options.
+\item \mycolor{\textsf{chicago-dates-common.cbx}},
+  \textsf{chicago-auth\-ordate.cbx},
   \textsf{chi\-cago-authordate.bbx},
   \textsf{chi\-cago-authordate-trad.cbx},
   \textsf{chicago-auth\-ordate-trad.bbx}, \textsf{chicago-notes.bbx},
@@ -253,19 +262,16 @@ release.
   \textsf{cms-french.lbx}, \textsf{cms-ger\-man.lbx},
   \textsf{cms-icelandic.lbx}, \textsf{cms-ngerman.lbx},
   \textsf{cms-norsk.lbx}, \textsf{cms-norwe\-gian.lbx},
-  \textsf{cms-nynorsk.lbx}, and \textsf{biblatex-chicago.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.  (To use the 15th-edition styles, you'll also require
-  \textsf{chicago-notes15.bbx}, \textsf{chicago-notes15.cbx},
-  \textsf{chicago-authordate15.bbx}, and
-  \textsf{chicago-authordate15.cbx}.)  The .zip file from CTAN
+  \textsf{cms-nynorsk.lbx}, \mycolor{\textsf{cms-swedish.lbx}},and
+  \textsf{biblatex-chica\-go.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 using the standard
-  layout and creating
+  you install in a system-wide directory, I suggest a standard layout
+  using
   \texttt{<TEXMFLOCAL>/tex/latex/biblatex-contrib/biblatex-chicago},
   where\ \texttt{<TEXMFLOCAL>} is the root of your local \TeX\
   installation --- for example, and depending on your system and
@@ -278,14 +284,32 @@ release.
   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.
-\item Philipp Lehman's very clear and detailed documentation of the
-  \textsf{biblatex} system, available in his package as
-  \textsf{biblatex.pdf}.  Here he explains why you might want to use
-  the system, the rules for constructing .bib files for it, and the
-  (numerous) methods at your disposal for modifying the formatted
+\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
+  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 \mycolor{\textsf{cms-notes-intro.pdf}},
+  \mycolor{\textsf{cms-dates-intro.pdf}}, and
+  \mycolor{\textsf{cms-trad-appendix.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 \texttt{trad} style.  All
+  three are fully hyperlinked, 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 these
+  three are in the \texttt{examples} directory just below this one,
+  marginal links there will take you to further discussions here.  The
+  file \mycolor{\textsf{cmsdocs.sty}} contains code and kludges
+  designed specifically for compiling
+  \mycolor{\textsf{cms-dates-intro.tex}},
+  \mycolor{\textsf{cms-notes-intro.tex}} and
+  \mycolor{\textsf{cms-trad-appendix.tex}}, so 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}, which will acquaint you with most of the
+  \textsf{dates-test.bib}, 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},
@@ -295,7 +319,8 @@ release.
   the second and third are the result of processing
   \textsf{dates-test.bib} with \textsf{cms-dates-sample.tex} or
   \textsf{cms-trad-sample.tex}.  All of these files are in
-  \texttt{doc/examples/}.
+  \texttt{doc/examples/}, and the \textsf{sample} files in particular
+  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
@@ -309,8 +334,8 @@ release.
   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 seven previous files
-  in the \texttt{doc/} subdirectory once you've extracted
+  page~\pageref{deprec:obsol}.  You will find the sixteen 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},
@@ -324,6 +349,14 @@ release.
   which naturally contains incomparably more information than I can
   hope to present here.  It should always be your first port of call
   when any doubts arise as to exactly what the specification requires.
+\item If you really still need the 15th-edition style files, you'll
+  find chicago-notes15.cbx, chicago-notes15.bbx,
+  chicago-authordate15.cbx, and chicago-auth\-ordate15.bbx, along with 
+  cms15-notes-sample.tex, cms15-dates-sam\-ple.tex,
+  cms15-notes-sample.pdf, and cms15-dates-sample.pdf all in the
+  \mycolor{\texttt{obsolete}} subdirectory of the package.  Please
+  remember that they won't compile with the current \textsf{biblatex},
+  so you'll need to downgrade, perhaps to version 2.9a.
 \end{itemize}
 
 \subsection{License}
@@ -345,36 +378,37 @@ purpose.
 \label{sec:acknowl}
 
 Even a cursory glance at the cbx and bbx files in the package will
-demonstrate how much of Lehman's code from \textsf{biblatex} I've
-adapted and re-used, and I've also followed some of the advice he gave
-to others in the \texttt{comp.text.tex} newsgroup.  He has been
-instrumental in improving the contextual capitalization procedures of
-which the style makes such frequent use, and his advice on
-constructing \textsf{biblatex-chicago.sty} was invaluable.  The code
-for formatting the footnote marks, and that for printing the
-separating rule only after a run-on note, I've adapted from the
-\textsf{footmisc} package by Robin Fairbairns, and I've borrowed ideas
-for the \texttt{shorthandibid} option from Dominik Waßenhoven's
-\textsf{biblatex-dw} package.  I've adapted Audrey Boruvka's
-\cmd{textcite} code from
+demonstrate how much of \textsf{biblatex's} code I've adapted and
+re-used, and I've also followed some of the advice the authors have
+given to others in the \texttt{comp.text.tex} newsgroup and on
+\href{http://tex.stackexchange.com}{Stackexchange}.  In particular,
+Philipp Lehman's advice on constructing \textsf{biblatex-chicago.sty}
+was invaluable.  The code for formatting the footnote marks, and that
+for printing the separating rule only after a run-on note, I've
+adapted from the \textsf{footmisc} package by Robin Fairbairns, and
+I've borrowed ideas for the \texttt{shorthandibid} option from Dominik
+Waßenhoven's \textsf{biblatex-dw} package.  I've adapted Audrey
+Boruvka's \cmd{textcite} code from
 \href{http://tex.stackexchange.com/questions/67837/citations-as-nouns-in-biblatex-chicago}{Stackexchange}
 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 Antti-Juhani Kaijahano for the Finnish
-localization, to Baldur Kristinsson for providing the Icelandic
-localization, and to Håkon Malmedal for the Norwegian localizations.
-Kazuo Teramoto and Gildas Hamel both sent patches to improve the
-package, and 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}.  I am very grateful to Stefan Björk for the new Swedish
+localization, to Antti-Juhani Kaijahano for the Finnish localization,
+to Baldur Kristinsson for providing the Icelandic localization, and to
+Håkon Malmedal for the Norwegian localizations.  Kazuo Teramoto and
+Gildas Hamel both sent patches to improve the package, and Arne
+Skjærholt 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.
 
 \section{Detailed Introduction}
 \label{sec:Intro}
@@ -464,18 +498,11 @@ original \LaTeX\ .sty file and \textsc{Bib}\TeX\ .bst file.  As you
 proceed, you will no doubt encounter some of the consequences of this
 decision, with certain fields and entry types in the .bib file having
 less-than-memorable names because I chose to use the supplementary
-ones provided by \textsf{biblatex.bst} rather than alter that file.  I
-intended then, if it turned out that anyone besides myself actually
-used \textsf{biblatex-chicago}, to ask Mr.\ Lehman to include more
-descriptive names for these few entry types and fields in
-biblatex.bst, if he were willing.  As luck would have it, several new
-types appeared in \textsf{biblatex} 0.8, many of which I have
-incorporated as replacements for the custom entry types I defined
-before.  If a consensus emerges about how best to assign the data to
-various fields in such entries, then I shall adopt it.  In the
-meantime, as you will see below, I have made two of the old custom
-types obsolete, and recycled the third for an entirely new purpose.
-Needless to say, I'm open to advice and suggestions on this score.
+ones provided by \textsf{biblatex} rather than alter that package's
+files.  With additions to the standard data model now possible, this
+will be one of the directions for future development, particularly if
+other styles are adopting certain broad conventions.  Needless to say,
+I'm open to advice and suggestions on this score.
 
 \section{The Specification:\ Notes\,\&\,Bibliography}
 \label{sec:Spec}
@@ -505,19 +532,17 @@ from the latter file below in parentheses.
 
 The complete list of entry types currently available in
 \textsf{biblatex-chicago-notes}, minus the odd \textsf{biblatex}
-alias, is as follows: \textbf{article}, \textbf{artwork},
-\textbf{audio}, \mycolor{\textbf{book}},
-\mycolor{\textbf{bookinbook}}, \textbf{booklet},
-\mycolor{\textbf{collection}}, \textbf{customc}, \textbf{image},
-\mycolor{\textbf{inbook}}, \textbf{incollection},
-\textbf{inproceedings}, \textbf{inreference}, \textbf{letter},
-\textbf{manual},\textbf{misc}, \textbf{music},
-\mycolor{\textbf{mvbook}}, \mycolor{\textbf{mvcollection}},
-\mycolor{\textbf{mvproceedings}}, \mycolor{\textbf{mvreference}},
-\textbf{online} (with its alias \textbf{www}), \textbf{patent},
-\textbf{periodical}, \mycolor{\textbf{proceedings}},
+alias, is as follows: \mycolor{\textbf{article}}, \textbf{artwork},
+\textbf{audio}, \textbf{book}, \textbf{bookinbook}, \textbf{booklet},
+\textbf{collection}, \textbf{customc}, \textbf{image},
+\textbf{inbook}, \textbf{incollection}, \textbf{inproceedings},
+\textbf{inreference}, \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{periodical}}, \textbf{proceedings},
 \textbf{reference}, \textbf{report} (with its alias
-\textbf{techreport}), \textbf{review}, \textbf{suppbook},
+\textbf{techreport}), \mycolor{\textbf{review}}, \textbf{suppbook},
 \textbf{supp\-collection}, \textbf{suppperiodical}, \textbf{thesis}
 (with its aliases \textbf{mastersthesis} and \textbf{phdthesis}),
 \textbf{unpublished}, and \textbf{video}.
@@ -533,7 +558,9 @@ very few fields when you use \textsf{biblatex-chicago-notes}, so it
 seemed to me better to gather information pertaining to fields in the
 next section.
 
-\mybigspace The \mymarginpar{\textbf{article}} \emph{Chicago Manual of
+\enlargethispage{\baselineskip}
+
+\mybigspace The \colmarginpar{\textbf{article}} \emph{Chicago Manual of
   Style} (14.170) recognizes three different sorts of periodical
 publication, \enquote{journals,} \enquote{magazines,} and
 \enquote{newspapers.} The first (14.172) includes \enquote{scholarly
@@ -587,8 +614,6 @@ 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.)
 
-%%\enlargethispage{-\baselineskip}
-
 \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
 latter in the \textsf{titleaddon} field.  Standard \textsf{biblatex}
@@ -602,7 +627,7 @@ 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 No less than eight more things need explication here.
+\mylittlespace No less than nine 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,
@@ -647,7 +672,7 @@ bibliography entry is alphabetized correctly.  (See
 lakeforester:pushcarts and, for the sorting issue,
 \cmd{DeclareSortingScheme} in section~\ref{sec:formatopts} below.)
 
-\enlargethispage{-\baselineskip}
+%\enlargethispage{-\baselineskip}
 
 \mylittlespace Fourth, Bertold Schweitzer has pointed out, following
 the \emph{Manual} (14.192), that while an \textsf{issuetitle} often
@@ -672,8 +697,8 @@ 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 now
-obsolete, replaced by Lehman's macro \cmd{autocap}, which itself only
+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
@@ -712,10 +737,11 @@ 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 into \textsf{misc} entries with an
-\textsf{entrysubtype} [coolidge:speech, roosevelt:speech].)
+archives fit best either into \textsf{online} or into \textsf{misc}
+entries with an \textsf{entrysubtype} [coolidge:speech,
+roosevelt:speech].)
 
-\mylittlespace Finally, the 16th edition of the \emph{Manual}
+\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
@@ -729,6 +755,15 @@ 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 Finally, \colmarginpar{New} the special
+\textsf{biblatex} field \mycolor{\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
+\mycolor{\textbf{shortjournal}} in section~\ref{sec:entryfields} for
+all the details on how this works.
+
 % %\enlargethispage{-\baselineskip}
 
 \mylittlespace If you're still with me, allow me to recommend that you
@@ -819,9 +854,11 @@ such favorite educational formats as the slideshow and the filmstrip
 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 best be presented in a \textbf{misc}
-entry with an \textsf{entrysubtype} (coolidge:speech,
-roosevelt:speech).
+of an archive, online or no, may be presented either in an
+\textsf{online} or in a \textsf{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).
 
 %\enlargethispage{\baselineskip}
 
@@ -842,19 +879,18 @@ from a cycle.  If the medium in question needs specifying, the
 \textsf{biblatex-chicago} provides no automated handling, e.g., a
 librettist (verdi:corsaro).
 
-\mybigspace This \colmarginpar{\textbf{book}} is the standard
-\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but with this
-release the package can now provide automatically 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 enable it in the preamble or in the
-\textsf{options} field using the new \mycolor{\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.
-
-\mybigspace This \colmarginpar{\textbf{bookinbook}} type provides the
+\mybigspace This \mymarginpar{\textbf{book}} is the standard
+\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but 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
+enable it in the preamble or in the \textsf{options} field using the
+\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.
+
+\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
@@ -862,10 +898,10 @@ articles.  Such an entry can have a \textsf{title} and a
 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 now enable automatically
+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 \mycolor{\texttt{booklongxref}} 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
@@ -889,26 +925,25 @@ uses the \textsf{howpublished} field instead of a standard
 \textsf{howpublished} field should instead go in \textsf{publisher}.
 (See clark:mesopot.)
 
-\mybigspace This \colmarginpar{\textbf{collection}} is the standard
-\textsf{biblatex} entry type, but with this release the package can
-now provide automatically 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
-enable it in the preamble or in the \textsf{options} field using the
-new \mycolor{\texttt{booklongxref}} option.  Please see
-\textbf{crossref} in section~\ref{sec:entryfields} and
+\mybigspace This \mymarginpar{\textbf{collection}} is the standard
+\textsf{biblatex} entry type, but 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 enable it in the preamble or in
+the \textsf{options} field using the new \texttt{booklongxref} option.
+Please see \textbf{crossref} in section~\ref{sec:entryfields} and
 \texttt{booklongxref} in section~\ref{sec:chicpreset}, below.  See
 harley:ancient:cart, harley:cartography, and harley:hoc for how this
 might look.
 
-\mybigspace This \mymarginpar{\textbf{customa}} entry type is now
+\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
 instead.
 
 %\enlargethispage{\baselineskip}
 
-\mybigspace This \mymarginpar{\textbf{customb}} entry type is now
+\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}
 type instead.
@@ -916,20 +951,20 @@ type instead.
 \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
-recommended by the \emph{Manual}.  (This is different from the usual
-\textsf{crossref}, \textsf{xref}, and \textsf{userf} mechanisms, all
-primarily designed to include cross-references to other works.  Cf.\
-14.84,86).  The lecarre:cornwell entry, for example, would allow your
-readers to find the more-commonly-used pseudonym \enquote{John Le
-  Carré} even if they were, for some reason, looking under his real
-name \enquote{David John Moore Cornwell.}\ As I read the
-specification, these cross-references are particularly encouraged,
-bordering on required, when \enquote{a bibliography 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.
+recommended by the \emph{Manual}.  (This is different from the
+\textsf{crossref}, \textsf{xref}, \textsf{userf} and
+\mycolor{\textsf{related}} mechanisms, all primarily designed to
+include cross-references to other works.  Cf.\ 14.84,86).  The
+lecarre:cornwell entry, for example, would allow your readers to find
+the more-commonly-used pseudonym \enquote{John Le Carré} even if they
+were, for some reason, looking under his real name \enquote{David John
+  Moore Cornwell.}\ As I read the specification, these
+cross-references are particularly encouraged, bordering on required,
+when \enquote{a bibliography 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.
 
 \mylittlespace In these latter cases, you would need merely to place
 the pseudonym in the \textsf{author} field, and the author's real
@@ -960,30 +995,27 @@ media.  This means that this entry type is now a clone of the
 for users migrating from the old to the new specification.  (See 3.22,
 8.193; bedford:photo.)
 
-\mybigspace These
-\mymarginpar{\mycolor{\textbf{inbook}}\\\textbf{incollection}} two
-standard \textsf{biblatex} types have very nearly identical formatting
-requirements as far as the Chicago specification is concerned, but I
-have retained both of them for compatibility.  \textsf{Biblatex.pdf}
-(§~2.1.1) intends the first for \enquote{a part of a book which forms
-  a self-contained unit with its own title,} while the second would
-hold \enquote{a contribution to a collection 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 notes and
-bibliography when you cite multiple pieces from the same
-\textsf{collection}.  These abbreviations are now activated by default
-when you use the \textsf{crossref} or \textsf{xref} field in
-\textsf{incollection} entries \emph{and} in \textsf{inbook} entries,
+\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
+concerned, but I have retained both of them for compatibility.
+\textsf{Biblatex.pdf} (§~2.1.1) intends the first for \enquote{a part
+  of a book which forms a self-contained unit with its own title,}
+while the second would hold \enquote{a contribution to a collection
+  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.  I have, in both types,
+implemented the \emph{Manual's} recommendations for space-saving
+abbreviations in notes and bibliography 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 and in \textsf{inbook} entries,
 because although the \emph{Manual} (14.113) 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},
-below, and the new option \mycolor{\texttt{longcrossref}} in
+below, and the new option \texttt{longcrossref} in
 section~\ref{sec:chicpreset}.  Please note 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
@@ -1018,9 +1050,9 @@ 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
 \textsf{incollection} and \textsf{inbook} entries.  See
-\textbf{crossref} in section~\ref{sec:entryfields} and the new option
-\mycolor{\texttt{longcrossref}} in section~\ref{sec:chicpreset} for
-more details.
+\textbf{crossref} in section~\ref{sec:entryfields} and the option
+\texttt{longcrossref} in section~\ref{sec:chicpreset} for more
+details.
 
 \mybigspace This \mymarginpar{\textbf{inreference}} entry type is
 aliased to \textsf{incollection} in the standard styles, but the
@@ -1057,7 +1089,7 @@ 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 previous releases of
+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
@@ -1068,12 +1100,12 @@ 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 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{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.
 
-\enlargethispage{-\baselineskip}
+%\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
@@ -1135,10 +1167,10 @@ type with a comma, like so: \texttt{memorandum, London}.
 Alternatively, you can put the place of writing into the
 \textsf{origlocation} field.  Most importantly, the date of the letter
 itself goes in the \textsf{origdate} field (\texttt{year-month-day}),
-which now allows a full date specification, while the publishing date
-of the whole collection goes in the \textsf{date} field, instead of in
+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 now has its ordinary meaning of \enquote{date of
+\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
@@ -1161,8 +1193,8 @@ 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 now correctly inherit fields from
-\textsf{book} and \textsf{collection} entries, and also from the new
+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
@@ -1176,8 +1208,8 @@ bibliography if more than one piece from a single collection is cited.
 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 new \mycolor{\texttt{longcrossref=true}} option, on which
-see section~\ref{sec:chicpreset}, below.  To stop individual letters
+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.
 
@@ -1233,7 +1265,7 @@ take no parentheses in full footnotes.  (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.\
-coolidge:speech, roosevelt:speech, shapey:partita.)
+roosevelt:speech, shapey:partita.)
 
 \mylittlespace If you are wondering what to put in
 \textsf{entrysubtype}, the answer is, currently, anything at all.  You
@@ -1242,16 +1274,16 @@ 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 now understand the specification, it draws a
+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 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., and into the
-\textsf{date} field for the others.
+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 In effect, whether it's a \textsf{letter} entry or a
 \enquote{letter-like} \textsf{misc} entry (with
@@ -1266,9 +1298,9 @@ 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}
-below.  (See 14.219-220, 14.231, 14.232-242; creel:house,
-dinkel:agassiz, spock:interview.)
+\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 Recipient}, and
@@ -1290,7 +1322,7 @@ date of a letter in a short note, I have provided the
 the citation command.  (The standard \textsf{biblatex} command
 \cmd{printdate} will work if you need to do the same for interviews.)
 
-\enlargethispage{\baselineskip}
+%\enlargethispage{\baselineskip}
 
 \mylittlespace As with \textsf{letter} entries, the \emph{Manual}
 (14.233) suggests that bibliography entries contain only the name of
@@ -1317,10 +1349,11 @@ should pursue.  I hope that \textsf{biblatex-chicago-notes} proves
 helpful in this regard.
 
 \mybigspace The \mymarginpar{\textbf{music}} 16th edition of the
-\emph{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
+\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
@@ -1382,14 +1415,14 @@ equivalences.
   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 now 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.
+  \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}
@@ -1409,12 +1442,11 @@ equivalences.
   \texttt{recorded} to the \textsf{eventdate} or, in the absence of
   this \textsf{pubstate} mechanism, to the \textsf{origdate}, or even
   to both, but you can modify what is printed there using the
-  \mycolor{\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 the \textsf{date}.  (See floyd:atom,
-  nytrumpet:art.)
+  \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 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.
@@ -1433,21 +1465,20 @@ course, be entertained.  (Cf. 14.276--77; \textsf{eventdate},
 bernstein:shostakovich, floyd:atom, holiday:fool, nytrumpet:art,
 rubinstein:chopin.)
 
-\mybigspace All \colmarginpar{\textbf{mvbook}\\\textbf{mvcollection}%
+\mybigspace All \mymarginpar{\textbf{mvbook}\\\textbf{mvcollection}%
   \\\textbf{mvproceedings}\\\textbf{mvreference}} four of these entry
-types are new to \textsf{biblatex-chicago}, and all 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
+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
+\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.)
@@ -1497,10 +1528,12 @@ 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
-best as \textsf{misc} entries with an \textsf{entrysubtype}:
-coolidge:speech, roosevelt:speech.)  Some online materials will, no
+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.
@@ -1517,7 +1550,7 @@ 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.
 
-%%\enlargethispage{\baselineskip}
+\enlargethispage{\baselineskip}
 
 \mybigspace The \mymarginpar{\textbf{patent}} \emph{Manual} is very
 brief on this subject (14.230), but very clear about which information
@@ -1547,7 +1580,7 @@ the \textsf{title} field to provide the lowercase letters manually.
 See petroff:impurity.
 
 
-\mybigspace This \mymarginpar{\textbf{periodical}} is the standard
+\mybigspace This \colmarginpar{\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
 function in \textsf{biblatex-chicago-notes}, and in the main uses the
@@ -1560,15 +1593,27 @@ 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.)
 
-\mybigspace This \colmarginpar{\textbf{proceedings}} is the standard
-\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but with this
-release the package can now provide automatically 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 enable it in the preamble or in the
-\textsf{options} field using the new \mycolor{\texttt{booklongxref}}
-option.  Please see \textbf{crossref} in section~\ref{sec:entryfields}
-and \texttt{booklongxref} in section~\ref{sec:chicpreset}, below.
+\mylittlespace It is worth \colmarginpar{New} noting that the special
+\textsf{biblatex} field \mycolor{\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 \mycolor{\textbf{shortjournal}} in
+section~\ref{sec:entryfields} for all the details on how this works.
+
+\mybigspace This \mymarginpar{\textbf{proceedings}} is the standard
+\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but 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
+enable it in the preamble or in the \textsf{options} field using the
+\texttt{booklongxref} option.  Please see \textbf{crossref} in
+section~\ref{sec:entryfields} and \texttt{booklongxref} in
+section~\ref{sec:chicpreset}, below.
 
 \mybigspace This \mymarginpar{\textbf{reference}} entry type is
 aliased to \textsf{collection} by the standard \textsf{biblatex}
@@ -1604,7 +1649,7 @@ report type in \textsf{note} and the \textsf{institution} in
 
 %%\enlargethispage{\baselineskip}
 
-\mybigspace The \mymarginpar{\textbf{review}} \textsf{review} entry
+\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
@@ -1669,9 +1714,9 @@ itself if you start the \textsf{title} field with a 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 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
+\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
@@ -1697,6 +1742,15 @@ 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, \colmarginpar{New} the special
+\textsf{biblatex} field \mycolor{\textsf{shortjournal}} allows you to
+present shortened \textsf{journaltitles} in \textsf{review} entries,
+as well as in \textsf{article} and \textsf{periodical} entries, and it
+facilitates the creation of lists of journal abbreviations in the
+manner of a \textsf{shorthand} list.  Please see the documentation of
+\mycolor{\textbf{shortjournal}} in section~\ref{sec:entryfields} for
+all the details on how this works.
+
 \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,
@@ -1722,7 +1776,7 @@ depending on the context.  Examples might be \enquote{\texttt{preface
 that unless you use a \cmd{bibstring} command in the \textsf{type}
 field, the resultant entry will not be portable across languages.)
 
-\enlargethispage{-\baselineskip}
+%\enlargethispage{-\baselineskip}
 
 \mylittlespace There are a few other rules for constructing your .bib
 entry.  The \textsf{author} field refers to the author of the
@@ -1759,7 +1813,7 @@ this purpose, and now you can use either of these, as I've added
 above under \textbf{review} for the full instructions on how to
 construct a .bib entry for such a reference.
 
-%%\enlargethispage{-\baselineskip}
+\enlargethispage{\baselineskip}
 
 \mybigspace The \mymarginpar{\textbf{unpublished}}
 \textsf{unpublished} entry type works largely as it does in standard
@@ -1768,8 +1822,8 @@ lowercase letter at the start of your \textsf{note} field (or perhaps
 an\ \cmd{autocap} command in the somewhat contradictory
 \textsf{howpublished}, if you have one) for material that wouldn't
 ordinarily be capitalized except at the beginning of a sentence.
-Thanks to a bug report by Henry D. Hollithron, such entries will now
-print information about any \textsf{editor}, \textsf{translator},
+Thanks to a bug report by Henry D. Hollithron, such entries will print
+information about any \textsf{editor}, \textsf{translator},
 \textsf{compiler}, etc., that you include in the .bib file (14.228;
 nass:address).
 
@@ -1826,9 +1880,9 @@ by \textsf{biblatex}.  Here are the main correspondences:
   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 \mycolor{\textsf{userd}} field
-  to change the string printed there.  (Absent an \textsf{eventdate},
-  the \textsf{userd} field in \textsf{video} entries will modify the
+  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
@@ -1902,9 +1956,9 @@ undefined, and \textsf{biblatex-chicago-notes} will do the rest. Cf.\
 \paragraph*{\protect\mymarginpar{\textbf{annotation}}}
 \label{sec:annote}
 
-At the request of Emil Salim, \textsf{biblatex-chicago-notes} has, as
-of version 0.9, added a package option (see \texttt{annotation} below,
-section \ref{sec:useropts}) to allow you to produce annotated
+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
@@ -1927,74 +1981,58 @@ be useful for some purposes.  Cf.\ \textsf{commentator}.
 
 %%\enlargethispage{\baselineskip}
 
-\mybigspace For \mymarginpar{\textbf{author}} the most part, I have
+\mybigspace For \colmarginpar{\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:manual).  If there is no \textsf{author}, then
-\textsf{biblatex-chicago-notes} will look, in sequence, for an
-\textsf{editor}, \textsf{translator}, or \textsf{compiler} (actually
-\textsf{namec}, currently) 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:bremer,
-harley:cartography, schellinger:novel, sechzer:women, silver:ga\-wain,
-soltes:georgia).  Please note that when a \textsf{namec} appears at
-the head of an entry, and you're not using \textsf{Biber}, you'll need
-to assist \textsf{biblatex}'s sorting algorithms by providing a
-\textsf{sortkey} field to ensure correct alphabetization in the
+\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:bremer, harley:cartography,
+schellinger:novel, sechzer:women, silver:ga\-wain, soltes:georgia).
+\textsf{Biblatex's} sorting algorithms will use the first of those
+names found, which should ensure correct alphabetization in the
 bibliography.  (See \cmd{DeclareSortingScheme} in
-section~\ref{sec:formatopts}, below.)  A \textsf{shortauthor} entry is
-no longer necessary to provide a \textsf{namec} at the head of the
-short note form --- \textsf{biblatex-chicago} now takes care of this
-automatically.
+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 two options: either you can
+isn't appropriate, you have (at least) two options: either you can
 (chaucer:liferecords) put all the information into a \textsf{note}
 field rather than individual fields, or you can use the
 \textsf{biblatex} options \texttt{useauthor=false},
-\texttt{useeditor=false}, \texttt{usetranslator=false}, and
-\texttt{usecompiler=\\false} in the \textsf{options} field
-(chaucer:alt).  If you look at the chaucer:alt entry in
-\textsf{notes-test.bib}, you'll notice a peculiarity of this system of
-toggles.  In order to ensure that the \textsf{title} of the book
-appears at the head of the entry, you need to use \emph{all four} of
-the toggles, even though the entry contains no \textsf{translator}.
-Internally, \textsf{biblatex-chicago} is either searching for an
-author-substitute, or it is skipping over elements of the ordered,
-unidirectional chain \textsf{author -> editor -> translator ->
-  compiler -> title}.  If you don't include
-\texttt{usetranslator=false} in the \textsf{options} field, then the
-package begins its search at \textsf{translator} and continues on to
-\textsf{namec}, even though you have \texttt{usecompiler=false} in
-\textsf{options}.  The result will be that the compilers' names will
-appear at the head of the entry.  If you want to skip over parts of
-the chain, you must turn off \emph{all} of the parts up to the one you
-wish printed.  (Another peculiarity of the system, if you're using
-\textsf{Biber}, is that setting the Chicago-specific
-\texttt{usecompiler} option to \texttt{false} doesn't remove
-\textsf{namec} from the sorting list, whereas the other standard
-\textsf{biblatex} toggles \emph{do} remove their names from the
-sorting list, so in the chaucer:alt case you need the \textsf{sortkey}
-field.  See \cmd{DeclareSortingScheme} in
-section~\ref{sec:formatopts}, below.)
-
-\mylittlespace This system of toggles, then, can turn off
+\mycolor{\texttt{usenamea=false}}, \texttt{useeditor=false},
+\mycolor{\texttt{usenameb=false}}, \texttt{usetranslator=false}, and
+\mycolor{\texttt{usenamec=false}} in the \textsf{options} field
+(chaucer:alt).  If you \colmarginpar{New} look at the chaucer:alt
+entry in \textsf{notes-test.bib}, you'll notice that you only need to
+turn off the fields that are present in the entry, but please remember
+to use the new option \mycolor{\texttt{usenamec}} instead of the old
+\texttt{usecompiler}, as the latter doesn't work as smoothly and
+completely as \textsf{biblatex's} own name toggles.
+
+\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
 wasn't possible before.  For full details of how this works, see the
 \textsf{editortype} documentation below.  (Of course, in
-\textsf{collection} and \textsf{proceedings} entry types, an
-\textsf{author} isn't expected, so there the \textsf{editor} is
-required, as in standard \textsf{biblatex}.  Also, in \textsf{article}
-or \textsf{review} entries with \textsf{entrysubtype}
-\texttt{magazine}, the absence of an \textsf{author} triggers the use
-of the \textsf{journaltitle} in its stead.  See those entry types for
-further details.)
+\textsf{collection}, \textsf{periodical} and \textsf{proceedings}
+entries, an \textsf{author} isn't expected, so there the chain of
+substitutions starts with \textsf{namea} and \textsf{editor}.  Also,
+in \textsf{article} or \textsf{review} entries with
+\textsf{entrysubtype} \texttt{magazine}, the absence of an
+\textsf{author} triggers the use of the \textsf{journaltitle} in its
+stead.  See those entry types for further details.)
 
 \mylittlespace \textbf{NB}: The \emph{Manual} provides specific
 instructions for formatting the names of both anonymous and
@@ -2017,10 +2055,10 @@ mark indicating doubt.  As long as you have the right string in the
 \textsf{authortype} field, \textsf{biblatex-chicago-notes} will also
 do the right thing automatically in the short note form.
 
-\mylittlespace In \textsf{nameaddon} most entry types (except
-\textsf{customc} and \textsf{review}, which see), this field furnishes
+\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
+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
@@ -2111,12 +2149,16 @@ invariably be providing information for the traditional
 (\textbf{crossref}).  This provision is unnecessary if you are using
 \textsf{Biber}.
 
-\mybigspace An \mymarginpar{\textbf{booktitleaddon}} annex to the
+\mybigspace An \colmarginpar{\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
 ordinarily only be capitalized at the beginning of a sentence, then
 simply ensure that that word is in lowercase, and
 \textsf{biblatex-chicago-notes} will automatically do the right thing.
+The package and entry options \colmarginpar{New}
+\mycolor{\texttt{ptitleaddon}} and \mycolor{\texttt{ctitleaddon}}
+(section~\ref{sec:chicpreset}) allow you to customize the punctuation
+that appears before the \textsf{booktitleaddon} field.
 
 \mybigspace This \mymarginpar{\textbf{chapter}} field holds the
 chapter number, mainly useful only in an \textsf{inbook} or an
@@ -2130,7 +2172,7 @@ be useful for some purposes.  Cf.\ \textsf{annotator}.
 
 %\enlargethispage{\baselineskip}
 
-\paragraph*{\protect\colmarginpar{\textbf{crossref}}}
+\paragraph*{\protect\mymarginpar{\mycolor{\textbf{crossref}}}}
 \label{sec:crossref}
 
 This field is the standard \textsc{Bib}\TeX\ cross-referencing
@@ -2143,11 +2185,11 @@ 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.  New functionality, discussed below, for
+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 new \mycolor{\textsf{mv*}} entry types to do so, will prove
-extremely difficult with the older backends, so if you plan on lots of
+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}.
 
@@ -2184,29 +2226,28 @@ form is appropriate for all the child entries.  The
 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).  With this release, I \colmarginpar{New!} have
-considerably extended this functionality.
-
-\mylittlespace First, I have added five new entry types ---
-\mycolor{\textbf{book}}, \mycolor{\textbf{bookinbook}},
-\mycolor{\textbf{collection}}, \mycolor{\textbf{inbook}}, and
-\mycolor{\textbf{proceedings}} --- to the list of those which use
-shortened cross references, and I have added two new options ---
-\mycolor{\texttt{longcrossref}} and \mycolor{\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.)
+see just below).  Recent releases have considerably extended this
+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.)
 
 \mylittlespace The inclusion of \textbf{book}, \textbf{bookinbook},
 \textbf{collection}, and \textbf{proceedings} entries fulfills a
@@ -2263,13 +2304,17 @@ such entry types, I thought it might help in these abbreviated
 book-like entries to provide a date for the \textsf{title} when it's
 part of a \textsf{maintitle}, though not when it's only part of a
 \textsf{booktitle}.  If dates appear in shortened references where
-you'd rather not have them, I have provided the new
-\mycolor{\texttt{omitxrefdate}} option
-\colmarginpar{\texttt{omitxrefdate}} to turn them off, either in the
-preamble for the document as a whole or in the \textsf{options} field
-of individual entries.  See \textbf{mvbook} in
-section~\ref{sec:entrytypes} and \texttt{omitxrefdate} in
-section~\ref{sec:useropts}.
+you'd rather not have them, I have provided the \texttt{omitxrefdate}
+option to turn them off, either in the preamble for the document as a
+whole or in the \textsf{options} field of individual entries.  There
+is also \colmarginpar{New} an \mycolor{\texttt{xrefurl}} option
+available to control the printing of \textsf{url}, \textsf{doi}, and
+\textsf{eprint} fields in abbreviated references where such
+information might otherwise never appear.  See \textbf{mvbook} in
+section~\ref{sec:entrytypes}, and both \texttt{omitxrefdate} and
+\mycolor{\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
@@ -2300,19 +2345,19 @@ 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 all previous releases of \textsf{biblatex-chicago}, so if your
-documents have come 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 will no longer work 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 now dependent on the settings of
-two new preamble and entry options.
-
-\mylittlespace Those \colmarginpar{\texttt{longcrossref}} options
-function asymmetrically.  The first, \mycolor{\texttt{longcrossref}},
-generally controls the settings for the entry types more-or-less
-authorized by the \emph{Manual}: \textsf{inbook},
+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 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}
@@ -2333,10 +2378,10 @@ authorized by the \emph{Manual}: \textsf{inbook},
   and in the bibliography.
 \end{description}
 
-The \colmarginpar{\texttt{booklongxref}} second option,
-\mycolor{\texttt{booklongxref}}, controls the settings for
-\textsf{book}, \textsf{bookinbook}, \textsf{collection}, and
-\textsf{proceedings} entries:
+The \mymarginpar{\texttt{booklongxref}} second option,
+\texttt{booklongxref}, controls the settings for \textsf{book},
+\textsf{bookinbook}, \textsf{collection}, and \textsf{proceedings}
+entries:
 
 \begin{description}
 \item[\qquad true:] This is the default.  If you use \textsf{crossref}
@@ -2355,30 +2400,30 @@ Please note that you can set both of these options either in the
 preamble or in the \textsf{options} field of individual entries,
 allowing you to change the settings on an entry-by-entry basis.
 
-\mylittlespace Please \colmarginpar{New!} further note that in
-previous releases of \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 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.  The \textsf{userf} and
-\textsf{reprinttitle} fields should now just work automatically in
-such circumstances, but \colmarginpar{\texttt{inheritshort\-hand}} the
-\textsf{shorthand} field in parent entries needs to be enabled by
-setting the \mycolor{\texttt{inheritshorthand}} package option to
-\texttt{true}.  There are, in addition, several other steps required
-to make this function smoothly --- please see the documentation of the
-\textbf{shorthand} field, below, for a full explanation.  (In case it
-isn't clear, the combination of \textsf{userf}, \textsf{shorthand},
-and \textsf{crossref} functionality in a single entry is now possible.
-If you come across any problems or inaccuracies, please report them.)
-
-\mybigspace This \colmarginpar{\textbf{date}} field may be used to
+\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
+in combination with this abbreviated cross-referencing mechanism.  I
+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.  The \textsf{userf} and \textsf{reprinttitle} fields should
+just work automatically in such circumstances, but
+\mymarginpar{\texttt{inheritshort\-hand}} the \textsf{shorthand} field
+in parent entries needs to be enabled by setting the
+\texttt{inheritshorthand} package option to \texttt{true}.  There are,
+in addition, several other steps required to make this function
+smoothly --- please see the documentation of the \textbf{shorthand}
+field, below, for a full explanation.  (In case it isn't clear, the
+combination of \textsf{userf}, \textsf{shorthand}, and
+\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 Lehman's instructions in §~2.3.8 of
+date range, according to the instructions in §~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
@@ -2392,23 +2437,22 @@ in section~\ref{sec:entrytypes} above for how to use this field to
 distinguish between two classes of archival material.  See also
 \textsf{origdate} and \textsf{urldate}.
 
-\mylittlespace With \colmarginpar{New!} this release, you can now 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 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 (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, in this release, the latter
-style includes compatibility code for the \texttt{cmsdate} (silently
-ignored) and \texttt{switchdates} options, along with the mechanism
-for reversing \textsf{date} and \textsf{origdate}.  This means that
-you can, in theory, leave all of this alone in your .bib file when
-making the conversion, though I'm retaining the right to revoke this
-if the code in question demonstrably interferes with the functioning
-of the notes \&\ bibliography style.)
+bibliography style should be aware that the latter style includes
+compatibility code for the \texttt{cmsdate} (silently ignored) and
+\texttt{switchdates} options, along with the mechanism for reversing
+\textsf{date} and \textsf{origdate}.  This means that you can, in
+theory, leave all of this alone in your .bib file when making the
+conversion, though I'm retaining the right to revoke this if the code
+in question demonstrably interferes with the functioning of the notes
+\&\ bibliography style.)
 
 \enlargethispage{\baselineskip}
 
@@ -2446,8 +2490,8 @@ 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
-complications that need explaining.  Lehman points out in his
-documentation that the \textsf{editor} field will be associated with a
+complications that need explaining.  \textsf{Biblatex.pdf} points out
+that the \textsf{editor} field will be associated with a
 \textsf{title}, a \textsf{booktitle}, or a \textsf{maintitle},
 depending on the sort of entry.  More specifically,
 \textsf{biblatex-chicago} associates the \textsf{editor} with the most
@@ -2477,7 +2521,10 @@ or in one of the \textsf{titleaddon} fields (chaucer:liferecords).
 (Because the strings identifying an editor differ in notes and
 bibliography, one can't simply write them out in such a field, hence
 the need for a macro, which I discuss further in the commands section
-below [\ref{sec:formatcommands}].)  Cf.\ \textsf{namea},
+below [\ref{sec:formatcommands}].)  Please note that, when attempting
+to find a name for the head of a note or a bibliography entry,
+\textsf{namea} takes precedence over \textsf{editor}, and
+\textsf{nameb} over \textsf{translator}.  Cf.\ \textsf{namea},
 \textsf{nameb}, \textsf{namec}, and \textsf{translator}.
 
 \mybigspace The \mymarginpar{\textbf{editora\\editorb\\editorc}} newer
@@ -2492,18 +2539,18 @@ bernstein:shostakovich, handel:messiah.)
 
 %\enlargethispage{\baselineskip}
 
-\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
-proceeding in order through \textsf{editor}, \textsf{translator}, and
-\textsf{namec} (the compiler).  If all four are missing, then the
-\textsf{title} will be placed at the head.  (In \textsf{article} and
-\textsf{review} entries with a \texttt{magazine}
-\textsf{entrysubtype}, a missing author immediately prompts the use of
-\textsf{journaltitle} at the head of an entry.  See above under
-\textsf{article} for details.)  The \textsf{editortype} field, added
-in \textsf{biblatex 0.7}, provides even greater flexibility, giving
+proceeding in order through \textsf{namea}, \textsf{editor},
+\textsf{nameb}, \textsf{translator}, and \textsf{namec} (the
+compiler).  If all six are missing, then the \textsf{title} will be
+placed at the head.  (In \textsf{article} and \textsf{review} entries
+with a \texttt{magazine} \textsf{entrysubtype}, a missing author
+immediately prompts the use of \textsf{journaltitle} at the head of an
+entry.  See above under \textsf{article} for details.)  The
+\textsf{editortype} field provides even greater flexibility, giving
 you the ability to indicate any number of roles at the head of an
 entry.  You can do this even though an author is named (eliot:pound
 shows this mechanism in action for a standard editor, rather than for
@@ -2520,42 +2567,44 @@ name in both the bibliography and in the long note form.
 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 \textsf{editortype} mechanism 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 it will go ahead and look
-for an \textsf{editor}.  When the \textsf{editor} field is used,
-\textsf{biblatex}'s sorting algorithms will work properly, and also
-its \textsf{labelname} mechanism, meaning that a shortened form of the
-\textsf{editor} will be used in the short note form.  If, however, the
-\textsf{namea} field provides the name, and you are not using
-\textsf{Biber}, then your .bib entry will need to have a
-\textsf{sortkey} field to aid in alphabetizing, and it will also need
-a \textsf{shorteditor} defined to help with the short note form, not a
-\textsf{shortauthor}, ruled out because \texttt{useauthor=false}.
+\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
+\mycolor{\texttt{usenamea=false}}, the algorithm will go ahead and
+look for an \textsf{editor}.  The \textsf{editortype} field applies
+only to the \textsf{editor}, but you can use
+\mycolor{\textsf{nameatype}} to modify \textsf{namea}.  Either of
+these names should be sorted properly in the bibliography, but please
+be aware that if you want a shortened form to appear in short notes
+then there's only the \textsf{shorteditor}, which you should ensure
+presents whichever of the two editors' names appears at the head of
+long notes or bibliography entries.
 
 \mylittlespace In \textsf{biblatex} 0.9 Lehman reworked the string
 concatenation mechanism, for reasons he outlined in his RELEASE file,
 and I have followed his lead.  In short, if you define the
 \textsf{editortype} field, then concatenation is turned off, even if
 the name of the \textsf{editor} matches, for example, that of the
-\textsf{translator}.  In the absence of an \textsf{editortype}, the
-usual mechanisms remain in place, that is, if 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)
-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
+\textsf{translator}.  In the absence of an \textsf{editortype} (or
+\mycolor{\textsf{nameatype}}), the usual mechanisms remain in place,
+that is, if 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) 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
 manually in the \textsf{shorteditor} field, or perhaps, in a different
 sort of entry, in a \textsf{shortauthor} field.
 
 \mylittlespace It may also be worth noting that because of certain
 requirements in the specification -- absence of an \textsf{author},
-for example -- the \texttt{useauthor} mechanism won't work properly in
-the following entry types: \textsf{collection}, \textsf{letter},
-\textsf{patent}, \textsf{periodical}, \textsf{proceedings},
-\textsf{review}, \textsf{suppbook}, \textsf{suppcollection}, and
+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{review},
+\textsf{suppbook}, \textsf{suppcollection}, and
 \textsf{suppperiodical}.
 
 \mybigspace These
@@ -2624,18 +2673,18 @@ section~\ref{sec:entrytypes} above under \textbf{misc} for all the
 details on how these citations work.
 
 \mylittlespace Fourth, and finally, the field can be defined in the
-new \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.
+\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.
 
 \mybigspace Kazuo
 \mymarginpar{\textbf{eprint}\\\textbf{eprintclass}\\\textbf{eprinttype}}
 Teramoto suggested adding \textsf{biblatex's} excellent
 \textsf{eprint} handling to \textsf{biblatex-chicago}, and he sent me
-a patch implementing it.  With minor alterations, I have applied it to
-this release, so these three fields now work more or less as they do
-in standard \textsf{biblatex}.  They may prove helpful in providing
-more abbreviated references to online content than conventional URLs,
+a patch implementing it.  I have applied it, with minor alterations,
+so these three fields now work more or less as they do in standard
+\textsf{biblatex}.  They may prove helpful in providing more
+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
@@ -2748,7 +2797,11 @@ where a piece in an \textsf{article} or \textsf{review}
 the author.  See above (section~\ref{sec:entrytypes}) under
 \textbf{article} for details.  The lakeforester:pushcarts and
 nyt:trevorobit entries in \textsf{notes-test.bib} will give you some
-idea of how this works.
+idea of how this works.  Please note there is a
+\mycolor{\textsf{shortjournal}} field which you can use to abbreviate
+the \textsf{journaltitle} in notes and/or in the bibliography, and you
+can also use it to print a list of journal abbreviations.  Cf.\ the
+\mycolor{\textbf{shortjournal}} documentation below.
 
 \mybigspace This \mymarginpar{\textbf{keywords}} field is
 \textsf{biblatex}'s extremely powerful and flexible technique for
@@ -2763,18 +2816,18 @@ 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},
-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.
+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.
 
 \mybigspace A \mymarginpar{\textbf{language}} standard
 \textsf{biblatex} field, designed to allow you to specify the
@@ -2854,10 +2907,10 @@ macro \cmd{reprint}, followed by a comma, 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 below.)  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).
+\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).
 
 \mybigspace The \mymarginpar{\textbf{mainsubtitle}} subtitle for a
 \textsf{maintitle} --- see next entry.
@@ -2872,39 +2925,48 @@ child entry.
 
 %%\enlargethispage{\baselineskip}
 
-\mybigspace An \mymarginpar{\textbf{maintitleaddon}} annex to the
+\mybigspace An \colmarginpar{\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
 that would ordinarily only be capitalized at the beginning of a
 sentence, then simply ensure that that word is in lowercase, and
 \textsf{biblatex-chicago-notes} will automatically do the right thing.
+The package and entry options \colmarginpar{New}
+\mycolor{\texttt{ptitleaddon}} and \mycolor{\texttt{ctitleaddon}}
+(section~\ref{sec:chicpreset}) allow you to customize the punctuation
+that appears before the \textsf{maintitleaddon} field
+(schubert:muellerin).
 
 \mybigspace Standard \mymarginpar{\textbf{month}} \textsf{biblatex}
 field, containing the month of publication.  This should be an
 integer, i.e., \texttt{month=\{3\}} not \texttt{month=\{March\}}.  See
 \textsf{date} for more information.
 
-\mybigspace This \mymarginpar{\textbf{namea}} is one of the fields
+\mybigspace This \colmarginpar{\textbf{namea}} is one of the fields
 \textsf{biblatex} provides for style writers to use, but which it
 leaves undefined itself.  In \textsf{biblatex-chicago} it contains the
 name(s) of the editor(s) of a \textsf{title}, if the entry has a
-\textsf{booktitle} or \textsf{maintitle}, or both, in which situation
-the \textsf{editor} would be associated with one of these latter
-fields (donne:var).  (In \textsf{article} and \textsf{review} entries,
+\textsf{booktitle} and/or a \textsf{maintitle}, in which situation the
+\textsf{editor} would be associated with one of these latter fields
+(donne:var).  (In \textsf{article} and \textsf{review} entries,
 \textsf{namea} applies to the \textsf{title} instead of the
 \textsf{issuetitle}, should the latter be present.)  You should
 present names in the field exactly as you would those in an
 \textsf{author} or \textsf{editor} field, and the package will
-concatenate this field with \textsf{nameb} if they are identical.  See
-under \textbf{editor} above for the full details.  Please note that,
-as the field is highly single-entry specific, if you are using
-\textsf{Biber} \textsf{namea} isn't inherited from a
-\textsf{crossref}'ed parent entry.  Cf.\ also \textsf{nameb},
-\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
-section~\ref{sec:formatcommands}.
+concatenate this field with \textsf{nameb} if they are identical.
+When choosing a name to head a note or a bibliography entry,
+\textsf{biblatex-chicago} gives precedence to \textsf{namea} over
+\textsf{editor}.  See under \textbf{editor} above for the full
+details.  Please note that, as the field is highly single-entry
+specific, if you are using \textsf{Biber} \textsf{namea} isn't
+inherited from a \textsf{crossref}'ed parent entry.  Please note,
+also, that you can use the \mycolor{\textsf{nameatype}} field to
+redefine this 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{parteditandcomp},
+\cmd{parttransandcomp}, and \cmd{partedittransand\-comp}, for which
+see section~\ref{sec:formatcommands}.
 
 \mybigspace This \mymarginpar{\textbf{nameaddon}} field is provided
 by \textsf{biblatex}, though not used by the standard styles.  In
@@ -2935,6 +2997,13 @@ string linking the two parts of the cross-reference.  The code
 automatically tests for a known bibstring, which it will italicize.
 Otherwise, it prints the string as is.
 
+\mybigspace You \colmarginpar{\textbf{nameatype}} can use this field
+to change the role of a \textsf{namea} just as you can use
+\textsf{editortype} to change the role of an \textsf{editor}.  As with
+the \textsf{editortype}, using this field prevents string
+concatenation with identical \textsf{nameb} or \textsf{namec} fields.
+Please see \textbf{editortype}, above, for the details.
+
 \mybigspace Like \mymarginpar{\textbf{nameb}} \textsf{namea}, above,
 this is a field left undefined by the standard \textsf{biblatex}
 styles.  In \textsf{biblatex-chicago}, it contains the name(s) of the
@@ -2950,14 +3019,16 @@ concatenate this field with \textsf{namea} if they are identical.  See
 under the \textbf{translator} field below for the full details.
 Please note that, as the field is highly single-entry specific, if you
 are using \textsf{Biber} \textsf{nameb} isn't inherited from a
-\textsf{crossref}'ed parent entry.  Cf.\ also \textsf{namea},
-\textsf{namec}, \textsf{origlanguage}, \textsf{translator},
-\textsf{userf} and the macros \cmd{partedit}, \cmd{parttrans},
-\cmd{parteditandtrans}, \cmd{partcomp}, \cmd{parteditandcomp},
-\cmd{parttransandcomp}, and \cmd{partedittransandcomp} in
-section~\ref{sec:formatcommands}.
+\textsf{crossref}'ed parent entry.  Please note, also, that in
+\textsf{biblatex-chicago's} name-finding algorithms \textsf{nameb}
+takes precedence over \textsf{translator}.  Cf.\ \textsf{namea},
+\textsf{namec}, \textsf{origlanguage} (section~\ref{sec:related}),
+\textsf{translator}, \textsf{userf} (section~\ref{sec:related}), and
+the macros \cmd{partedit}, \cmd{parttrans}, \cmd{parteditandtrans},
+\cmd{partcomp}, \cmd{parteditandcomp}, \cmd{parttransandcomp}, and
+\cmd{partedittransand\-comp} in section~\ref{sec:formatcommands}.
 
-\mybigspace The \mymarginpar{\textbf{namec}} \emph{Manual} (14.87)
+\mybigspace The \colmarginpar{\textbf{namec}} \emph{Manual} (14.87)
 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
@@ -2982,14 +3053,10 @@ please note that I've arranged the concatenation algorithms to include
 so in this particular circumstance you can, if needed, make
 \textsf{namec} analogous to these two latter, \textsf{title}-only
 fields.  (See above under \textbf{editortype} for details of how you
-may, in certain circumstances, use that field to identify a compiler.
-This method will be particularly useful if you don't need to
-concatenate the \textsf{namec} with any other role, because if you use
-the \textsf{editor} field \textsf{biblatex} will automatically attend
-to alphabetization and name-replacement in the bibliography, and will
-also provide a name for short notes.)
+may, in certain circumstances, use that field, or the
+\mycolor{\textsf{nameatype}} field, to identify a compiler.)
 
-\enlargethispage{\baselineskip}
+%\enlargethispage{\baselineskip}
 
 \mylittlespace It might conceivably be necessary at some point to
 identify the compiler(s) of a \textsf{title} separate from the
@@ -3000,23 +3067,16 @@ to fall back on the \cmd{partcomp} macro or the related
 \cmd{partedittransandcomp}, on which see Commands
 (section~\ref{sec:formatcommands}) below.  (Future releases may be
 able to remedy this.)  It may be as well to mention here too that of
-the three names that can be substituted for the missing
-\textsf{author} at the head of an entry,
-\textsf{biblatex-chicago-notes} will choose an \textsf{editor} if
-present, then a \textsf{translator} if present, falling back to
-\textsf{namec} only in the absence of the other two, and assuming that
-the fields aren't identical, and therefore to be concatenated.  In a
-change from the previous behavior, these algorithms also now test for
-\textsf{namea} or \textsf{nameb}, which will be used instead of
-\textsf{editor} and \textsf{translator}, respectively, giving the
-package the greatest likelihood of finding a name to place at the head
-of an entry.  Please remember, however, that if this name is supplied
-by any of the non-standard fields \textsf{name[a-c]}, and you're not
-using \textsf{Biber}, then you will need to provide a \textsf{sortkey}
-to assist with alphabetization in the bibliography (cf.\
-\cmd{DeclareSortingScheme} in section~\ref{sec:formatopts}, below.)  A
-\textsf{shortauthor} is no longer necessary for the short note form,
-as the style will provide it automatically.
+the names that can be substituted for the missing \textsf{author} at
+the head of an entry, \textsf{biblatex-chicago-notes} will choose a
+\textsf{namea} if present, then an \textsf{editor}, a \textsf{nameb},
+or a \textsf{translator}, with \textsf{namec} coming last, assuming
+that the fields aren't identical, and therefore to be concatenated.
+The alphabetization routines should work properly for any of these
+names, but do please remember that if you want the package to skip
+over any names you can employ the \texttt{use<name>=false} options.
+Indeed, \textsf{biblatex's} \mycolor{\texttt{usenamec}} has replaced
+the old Chicago-specific \texttt{usecompiler}, which is deprecated.
 
 \mybigspace As \mymarginpar{\textbf{note}} in standard
 \textsf{biblatex}, this field allows you to provide bibliographic data
@@ -3122,86 +3182,17 @@ 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.
+\textsf{location} field.  (The \textsf{origyear} field usually works,
+too.)
 
-%%\enlargethispage{\baselineskip}
+\mybigspace See
+\vspace{-14.2pt}
+\colmarginpar{\textbf{origlanguage}\\
+\textbf{origlocation}\\\textbf{origpublisher}}
+section~\ref{sec:related}, below.
+\vspace{18pt}
 
-\mybigspace In \mymarginpar{\textbf{origlanguage}} keeping with the
-\emph{Manual}'s specifications, I have fairly thoroughly redefined
-\textsf{biblatex}'s facilities for treating translations.  The
-\textsf{origtitle} field isn't used, while the \textsf{language} and
-\textsf{origdate} fields have been press-ganged for other duties.  The
-\textsf{origlanguage} field, for its part, retains a dual role in
-presenting translations in a bibliography.  The details of the
-\emph{Manual}'s suggested treatment when both a translation and an
-original are cited may be found below under \textbf{userf}.  Here,
-however, I simply note that the introductory string used to connect
-the translation's citation with the original's is \enquote{Originally
-  published as,} which I suggest may well be inaccurate in a great
-many cases, as for instance when citing a work from classical
-antiquity, which will most certainly not \enquote{originally} have
-been published in the Loeb Classical Library.  Although not, strictly
-speaking, authorized by the \emph{Manual}, I have provided another way
-to introduce the original text, using the \textsf{origlanguage} field,
-which must be provided \emph{in the entry for the translation, not the
-  original text} (aristotle:metaphy:trans).  If you put one of the
-standard \textsf{biblatex} bibstrings there (enumerated below), then
-the entry will work properly across multiple languages.  Otherwise,
-just put the name of the language there, localized as necessary, and
-\textsf{biblatex-chicago} will eschew \enquote{Originally published
-  as} in favor of, e.g., \enquote{Greek edition:} or \enquote{French
-  edition:}.  This has no effect in notes, where only the work cited
---- original or translation --- will be printed, but it may help to
-make the \emph{Manual}'s suggestions for the bibliography more
-palatable.
-
-\mylittlespace That was the first usage, in keeping at least with the
-spirit of the \emph{Manual}.  I have also, perhaps less in keeping
-with that specification, retained some of \textsf{biblatex}'s
-functionality for this field.  If an entry doesn't have a
-\textsf{userf} field, and therefore won't be combining a text and its
-translation in the bibliography, you can also use
-\textsf{origlanguage} as Lehman intended it, so that instead of
-saying, e.g., \enquote{translated by X,} the entry will read
-\enquote{translated from the German by X.}  The \emph{Manual} doesn't
-mention this, but it may conceivably help avoid certain ambiguities in
-some citations.  As in \textsf{biblatex}, if you wish to use this
-functionality, you have to provide \emph{not} the name of the
-language, but rather a bibliography string, which may, at the time of
-writing, be one of \texttt{american}, \texttt{brazilian},
-\texttt{danish}, \texttt{dutch}, \texttt{english}, \texttt{french},
-\texttt{german}, \texttt{greek}, \texttt{italian}, \texttt{latin},
-\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).  Starting with this release of \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 now 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 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 achieve.  Cf.\
-\textsf{origdate}, \textsf{origpublisher} and \textsf{pubstate};
-schweitzer:bach.)
-
-\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 now 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}, and
-\textsf{pubstate}; schweitzer:bach.)
-
-\mybigspace This \colmarginpar{\textbf{pages}} is the standard
+\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
@@ -3218,8 +3209,8 @@ 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 has recently brought to my attention a
-discussion that took place a couple of years ago on
+\mylittlespace David Gohlke brought to my attention a discussion that
+took place a couple of years ago on
 \href{http://tex.stackexchange.com/questions/44492/biblatex-chicago-style-page-ranges}{Stackexchange}
 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
@@ -3229,10 +3220,9 @@ 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,
 and in their \textsf{postnote} fields, I have made the activation of
-this code a package option, so setting
-\mycolor{\texttt{compresspages=true}} when loading
-\textsf{biblatex-chicago} should automatically give you the
-Chicago-recommended page ranges.
+this code a package option, so setting \texttt{compresspages=true}
+when loading \textsf{biblatex-chicago} should automatically give you
+the Chicago-recommended page ranges.
 
 \mybigspace This, \mymarginpar{\textbf{pagination}} a standard
 \textsf{biblatex} field, allows you automatically to prefix the
@@ -3243,7 +3233,7 @@ appropriate identifying string to information you provide in the
 all the details on this functionality, as aside from the difference
 just mentioned the two fields are equivalent.
 
-\mybigspace Standard \colmarginpar{\textbf{part}} \textsf{biblatex}
+\mybigspace Standard \mymarginpar{\textbf{part}} \textsf{biblatex}
 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
@@ -3257,13 +3247,13 @@ capitalizing it if necessary, rather than supplying the usual
 bibstring, so this provides a mechanism for altering the string to
 your liking.  The field will be printed in the same place in any entry
 as would a \textsf{volume} number, and although it will most usually
-be associated with such a number, it can also, as of this release,
-function independently, allowing you to identify parts of works that
-don't fit into the standard scheme.  If you need to identify
-\enquote{parts} or \enquote{books} that are part of a published
-\textsf{series}, for example, then you'll need to use a different
-field, (which in this case would be \textsf{number}
-[palmatary:pottery]).  Cf.\ \textsf{volume}.
+be associated with such a number, it can also function independently,
+allowing you to identify parts of works that don't fit into the
+standard scheme.  If you need to identify \enquote{parts} or
+\enquote{books} that are part of a published \textsf{series}, for
+example, then you'll need to use a different field, (which in this
+case would be \textsf{number} [palmatary:pottery]).  Cf.\
+\textsf{volume}.
 
 \mybigspace Standard \mymarginpar{\textbf{publisher}}
 \textsf{biblatex} field.  Remember that \enquote{\texttt{and}} is a
@@ -3293,71 +3283,16 @@ 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.
 
-\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.
-
-%\enlargethispage{\baselineskip}
-
-\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.)
-Please remember that, currently, if you put anything besides
-\texttt{reprint} in the \textsf{pubstate} field it will silently be
-ignored, but this may change in future releases.
+\mybigspace See \colmarginpar{\textbf{pubstate}}
+section~\ref{sec:related}, below.
 
 \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
 purposes.  Cf.\ \textsf{annotator} and \textsf{commentator}.
 
-\mybigspace \textbf{NB:} \mymarginpar{\textbf{reprinttitle}}
-\textbf{Please note that this feature is in an alpha state, and that
-  I'm contemplating using a different field in the future for this
-  functionality.  I include it here in the hope that it might receive
-  some testing in the meantime.}  At the request of Will Small, I have
-included a means of providing the 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.
+\mybigspace See \colmarginpar{\textbf{reprinttitle}}
+section~\ref{sec:related}, below.
 
 \mybigspace A \mymarginpar{\textbf{series}} standard \textsf{biblatex}
 field, usually just a number in an \textsf{article},
@@ -3388,7 +3323,7 @@ preferences regarding the formatting of numerals.
 
 %\enlargethispage{\baselineskip}
 
-\paragraph*{\protect\mymarginpar{\textbf{shortauthor}}}
+\paragraph*{\protect\colmarginpar{\textbf{shortauthor}}}
 \label{sec:shortauthor}
 
 This is a standard \textsf{biblatex} field, but
@@ -3400,19 +3335,18 @@ the \textsf{biblatex} system selects the author's last name from the
 \textsf{author} field and uses it in such a reference, and if there is
 no \textsf{author} it will search \textsf{namea}, \textsf{editor},
 \textsf{nameb}, \textsf{translator}, and \textsf{namec}, in that
-order.  (In the case of the non-standard names \textsf{name[a-c]}, you
-will need to provide a \textsf{sortkey} if you aren't using
-\textsf{Biber}.  Cf.\ \cmd{DeclareSortingScheme} and
-\cmd{DeclareLabelname} in section~\ref{sec:formatopts}, below.)  In an
-author-less \textsf{article} or \textsf{review} entry
+order.  In an author-less \textsf{article} or \textsf{review} entry
 (\textsf{entrysubtype} \texttt{magazine}), where
 \textsf{biblatex-chicago-notes} will use the \textsf{journaltitle} as
-the author, or in author-less \textsf{manual} entries, where the
-\textsf{organization} will be so used, the style automatically
-provides the same substitution in the short note form, though you'll
-still need to help the alphabetization routines by providing a
-\textsf{sortkey} field in such cases (dyna:browser, gourmet:052006,
-lakeforester:pushcarts, nyt:trevorobit).
+the author, you can use the \colmarginpar{New}
+\mycolor{\textsf{shortjournal}} field instead, but you'll need to set
+up the \mycolor{\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,
+gourmet:052006, lakeforester:pushcarts, nyt:trevorobit).
 
 \mylittlespace As mentioned under \textsf{editortype}, the
 \emph{Manual} (14.87) recommends against providing the identifying
@@ -3428,22 +3362,28 @@ in this case for, e.g., a \textsf{collection} entry that typically
 lacks an author.  The \textsf{shortauthor} field works just as well in
 most situations, but if you have set \texttt{useauthor=false} (and not
 \texttt{useeditor=false}) in an entry's \textsf{options} field, then
-only \textsf{shorteditor} will be recognized.  Cf.\
-\textsf{editortype}, above.
+only \textsf{shorteditor} will be recognized.  It may be worth
+pointing out that, because \textsf{biblatex-chicago} also provides a
+\textsf{namea} field for the editor of a \textsf{title} as opposed to
+a \textsf{main-} or \textsf{booktitle}, and because in standard use
+the \textsf{namea}, if present, will be chosen to head a bibliography
+entry before the \textsf{editor}, you should present the shortened
+\textsf{namea} here instead of a shortened \textsf{editor} in such
+cases.  Cf.\ \textsf{editortype}, above.
 
-\mybigspace This \colmarginpar{\textbf{shorthand}} is
+\mybigspace This \mymarginpar{\textbf{shorthand}} is
 \textsf{biblatex}'s mechanism for using abbreviations in place of the
 usual short note form, and in previous releases I left it effectively
 unmodified in \textsf{biblatex-chicago-notes}, apart from a few
-formatting tweaks.  For this release, at the request of Kenneth Pearce
-and following some hints in the \emph{Manual}, I have made the system
-considerably more flexible, which I hope might be useful for those
-with specialized formatting needs.  In the default configuration, any
-entry which contains a \textsf{shorthand} field will produce a normal
-first note, either long or short according to your package options,
-informing the 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
+formatting tweaks.  At the request of Kenneth Pearce, and following
+some hints in the \emph{Manual}, I have made the system considerably
+more flexible, which I hope might be useful for those with specialized
+formatting needs.  In the default configuration, any entry which
+contains a \textsf{shorthand} field will produce a normal first note,
+either long or short according to your package options, informing the
+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
 abbreviations for reference purposes, a list which the \emph{Manual}
 suggests should be placed either in the front matter (when using
@@ -3470,22 +3410,22 @@ 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
 information.)
 
-\mylittlespace Alexandre \colmarginpar{New!} Roberts has suggested a
-further refinement to \textsf{shorthand} behavior, which allows for it
-to appear in the place of the usual abbreviated citation of parent
-entries cross-referenced by several different child entries.  In such
-a case, instead of the usual \enquote{\ldots\,in Author, \emph{Title},
+\mylittlespace Alexandre Roberts suggested a further refinement to
+\textsf{shorthand} behavior, which allows for it to appear in the
+place of the usual abbreviated citation of parent entries
+cross-referenced by several different child entries.  In such a case,
+instead of the usual \enquote{\ldots\,in Author, \emph{Title},
   24--38,} you would see instead \enquote{\ldots\,in \emph{ShrtHd},
   24--38.}  There are several steps required for enabling this
-behavior.  First, you need to set the new package option
-\mycolor{\texttt{inheritshorthand}} to \texttt{true}, which allows
-child entries to inherit the necessary fields from their
-cross-referenced parents.  Second, you'll probably want to use the
-\textsf{shorthandintro} field somehow to clarify that the
-\textsf{shorthand} applies to the \emph{parent} rather than to the
-\emph{child}, as otherwise the reference will be ambiguous.  Third,
-you'll need to put \texttt{skipbiblist}, formerly \texttt{skiplos}, in
-the \textsf{options} field of the child entries so that the
+behavior.  First, you need to set the package option
+\texttt{inheritshorthand} to \texttt{true}, which allows child entries
+to inherit the necessary fields from their cross-referenced parents.
+Second, you'll probably want to use the \textsf{shorthandintro} field
+somehow to clarify that the \textsf{shorthand} applies to the
+\emph{parent} rather than to the \emph{child}, as otherwise the
+reference will be ambiguous.  Third, you'll need to put
+\texttt{skipbiblist}, formerly \texttt{skiplos}, in the
+\textsf{options} field of the child entries so that the
 \textsf{shorthand} itself appears in the list of shorthands
 \emph{only} next to the parent entry, and not also next to all of its
 children.
@@ -3494,15 +3434,15 @@ children.
 formerly recommended against using shorthands with cross-references,
 but this extension of their use makes sense as an extra space-saving
 measure.  I'm not certain that I've identified all the possible
-drawbacks to enabling the \mycolor{\texttt{inheritshorthand}} option,
-so care is still needed, at least in the current state of
+drawbacks to enabling the \texttt{inheritshorthand} option, so care is
+still needed, at least in the current state of
 \textsf{biblatex-chicago-notes}.  Please report any problems you might
 have with this functionality to the email address at the head of this
 documentation.
 
-\enlargethispage{-\baselineskip}
+%\enlargethispage{-\baselineskip}
 
-\mybigspace When \mymarginpar{\textbf{shorthandintro}} you include a
+\mybigspace When \colmarginpar{\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
 parentheses and prefaced by the phrase \enquote{hereafter cited as.}
@@ -3515,18 +3455,63 @@ shorthand in later citations and in the list of shorthands.  Finally,
 I've tried to allow for as many different styles of notification as
 possible, so by default the only punctuation that will appear between
 the rest of the citation and the \textsf{shorthandintro} is a space.
-If you are not enclosing the whole phrase in parentheses, you may need
-to provide additional punctuation in the field itself, e.g.,
-\texttt{\{\textbackslash addperiod\textbackslash space Cited
-  as\ldots\}}.
-
-\mybigspace A \mymarginpar{\textbf{shorttitle}} standard
+You can \colmarginpar{New} change this punctuation, either in the
+preamble for the whole document or in individual entries, using the
+\mycolor{\texttt{shorthandpunct}} option, documented in
+section~\ref{sec:chicpreset}.  If the available option keys aren't
+adequate, you can use \texttt{none} and then provide custom
+punctuation inside the \textsf{shorthandintro} field itself.
+
+\mybigspace A \colmarginpar{\textbf{shortjournal}} special
+\textsf{biblatex} field, used to provide both 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
+utilize this functionality in your documents, but there are several
+steps to take in order to do so.  First, you'll need to provide both
+\textsf{shortjournal} and \textsf{journaltitle} fields in the entry
+types that use them, i.e., mainly \textsf{article} and \textsf{review}
+entries.  In \textsf{periodical} entries the \textsf{title} field
+presents what would be the \textsf{journaltitle} in the previous two,
+so in such entries you can provide the standard \textsf{shorttitle}
+field to accompany the \textsf{title}, and \textsf{biblatex-chicago}
+will automatically copy the \textsf{shorttitle} into a
+\mycolor{\textsf{shortjournal}}.
+
+\mylittlespace Having done this, you need to set the
+\mycolor{\texttt{journalabbrev}} option either when loading
+\textsf{biblatex-chicago} or in the \textsf{options} field of
+individual .bib entries.  By default, this option is not set, so your
+\textsf{shortjournal} 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 \cmd{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-
+or endnotes (\mycolor{\texttt{sjnotes}} and
+\mycolor{\texttt{sjendnotes}}, 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 (bold italic), you can
+roll your own using \cmd{DeclareFieldFormat\{shortjour\-nalwidth\}} ---
+you can see its default definition at the top of
+\textsf{chicago-notes.bbx}.
+
+\mybigspace A \colmarginpar{\textbf{shorttitle}} standard
 \textsf{biblatex} field, primarily used to provide an abbreviated
-title for short notes.  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;
-jackson:paulina:letter, white:ross:memo, white:russ.)  Some
+title for short notes.  (It is also the way to hook
+\textsf{periodical} entries into the \mycolor{\textsf{shortjournal}}
+mechanism, 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; 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
@@ -3557,11 +3542,11 @@ 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).  Lehman also provides
-\textbf{sortname}, \textbf{sorttitle}, and \textbf{sortyear} for more
-fine-grained control.  Please consult \textsf{biblatex.pdf} and the
-remarks on \cmd{DeclareSortingScheme} in section~\ref{sec:formatopts},
-below.
+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
+\textsf{biblatex.pdf} and the remarks on \cmd{DeclareSortingScheme} in
+section~\ref{sec:formatopts}, below.
 
 \mybigspace The \mymarginpar{\textbf{subtitle}} subtitle for a
 \textsf{title} --- see next entry.
@@ -3661,10 +3646,10 @@ quotation, retains those marks in all title types (kimluu:diethyl).
 \textsf{biblatex-chicago-notes} will automatically capitalize the
 first word of the \textsf{title} after sentence-ending punctuation,
 assuming that such a \textsf{title} begins with a lowercase letter in
-your .bib database.  See \textbf{\textbackslash autocap} below for
-more details.
+your .bib database.  See\,\textbf{\textbackslash autocap} in
+section~\ref{sec:formatcommands} below for more details.
 
-\mybigspace Standard \mymarginpar{\textbf{titleaddon}}
+\mybigspace Standard \colmarginpar{\textbf{titleaddon}}
 \textsf{biblatex} intends this field for use with additions to titles
 that may need to be formatted differently from the titles themselves,
 and \textsf{biblatex-chicago-notes} uses it in just this way, with the
@@ -3679,21 +3664,27 @@ this rule is when your data begins with a word that would ordinarily
 only be capitalized at the beginning of a sentence, in which case you
 need then simply ensure that that word is in lowercase, and
 \textsf{biblatex-chicago-notes} will automatically do the right thing.
-See\ \textbf{\textbackslash autocap}, below.  (Cf.\ brown:bremer,
-osborne:poison, reaves:rosen, and white:ross:memo for examples where
-the field starts with a lowercase letter; morgenson:market provides an
-example where the \textsf{titleaddon} field, holding the name of a
-regular column in a newspaper, is capitalized, a situation that is
-handled as you would expect.)
-
-\enlargethispage{-\baselineskip}
-
-\mybigspace As \mymarginpar{\textbf{translator}} far as possible, I
+See\,\textbf{\textbackslash autocap} in
+section~\ref{sec:formatcommands}, below.  The package and entry
+options \colmarginpar{New} \mycolor{\texttt{ptitleaddon}} and
+\mycolor{\texttt{ctitleaddon}} (section~\ref{sec:chicpreset}) allow
+you to customize the punctuation that appears before the
+\textsf{titleaddon} field.  (Cf.\ brown:bremer, osborne:poison,
+reaves:rosen, and white:ross:memo for examples where the field starts
+with a lowercase letter; morgenson:market provides an example where
+the \textsf{titleaddon} field, holding the name of a regular column in
+a newspaper, is capitalized, a situation that is handled as you would
+expect; coolidge:speech shows both entry options for controlling the
+punctuation.)
+
+%\enlargethispage{-\baselineskip}
+
+\mybigspace As \colmarginpar{\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
-complications that need explaining.  Lehman points out in his
-documentation that the \textsf{translator} field will be associated
-with a \textsf{title}, a \textsf{booktitle}, or a \textsf{maintitle},
+complications that need explaining.  \textsf{Biblatex.pdf} points out
+that the \textsf{translator} field will be associated with a
+\textsf{title}, a \textsf{booktitle}, or a \textsf{maintitle},
 depending on the sort of entry.  More specifically,
 \textsf{biblatex-chicago} associates the \textsf{translator} with the
 most comprehensive of those titles, that is, \textsf{maintitle} if
@@ -3706,7 +3697,9 @@ one part of a collection or for one volume of a multi-volume work.
 For these cases I have provided the \textsf{nameb} field.  You should
 format names for this field as you would for \textsf{author} or
 \textsf{editor}, and these names will always be associated with the
-\textsf{title} (euripides:orestes).
+\textsf{title} (euripides:orestes) In the algorithm for finding a name
+for the head of notes and bibliography entries, \textsf{nameb} takes
+precedence over \textsf{translator}.
 
 \mylittlespace I have also provided a \textsf{namea} field, which
 holds the editor of a given \textsf{title} (euripides:orestes).  If
@@ -3725,11 +3718,11 @@ macro, which I discuss further in the commands section below
 [\ref{sec:formatcommands}].)
 
 \mylittlespace Finally, as I detailed above under \textbf{author}, in
-the absence of an \textsf{author} or an \textsf{editor}, the
-\textsf{translator} will be used at the head of an entry
-(silver:gawain), and the bibliography entry alphabetized by the
-translator's name, behavior that can be controlled with the
-\texttt{{usetranslator}} switch in the \textsf{options} field.  Cf.\
+the absence of an \textsf{author}, \textsf{namea}, \textsf{editor},
+and \textsf{nameb}, the \textsf{translator} will be used at the head
+of an entry (silver:gawain), and the bibliography entry alphabetized
+by the translator's name, behavior that can be controlled with the
+\texttt{use<name>} switches in the \textsf{options} field.  Cf.\
 \textsf{author}, \textsf{editor}, \textsf{namea}, \textsf{nameb}, and
 \textsf{namec}.
 
@@ -3765,7 +3758,7 @@ do the right thing in citations.  Cf.\ \textsf{artwork},
 above, for all the details.  (See auden:reading, bedford:photo,
 cleese:holygrail, leo:madonna, nytrumpet:art.)
 
-%%\enlargethispage{-\baselineskip}
+\enlargethispage{\baselineskip}
 
 \mybigspace A standard \mymarginpar{\textbf{url}} \textsf{biblatex}
 field, it holds the url of an online publication, though you can
@@ -3774,7 +3767,11 @@ provide one for all entry types.  The 16th edition of the
 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.
+properly, in the text and in the reference apparatus.  It
+\colmarginpar{New} 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 A standard \mymarginpar{\textbf{urldate}}
 \textsf{biblatex} field, it identifies exactly when you accessed a
@@ -3798,7 +3795,7 @@ field will be placed, unformatted and between commas, after the
 identifying the broadcast network when you cite a radio or television
 program (14.221; bundy:macneil).
 
-\mybigspace I \mymarginpar{\textbf{userc}} have now implemented this
+\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
 mnemonic for this function, though it's perfectly possible to use the
@@ -3816,19 +3813,18 @@ entry in the bibliography to which the cross-reference will point.
 (See 14.84, 14.86; creasey:ashe:blast, creasey:morton:hide,
 creasey:york:death, lecarre:quest.)
 
-\mybigspace The \colmarginpar{\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}
 the \textsf{urldate}, so phrases like \enquote{\texttt{last modified}}
 or \enquote{\texttt{last revised}} are what the field will typically
-contain (14.7--8; wikiped:bibtex).  In \colmarginpar{New!} the absence
-of a \textsf{urldate}, you can now, in most entry types, include a
+contain (14.7--8; 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}.
 
@@ -3865,40 +3861,10 @@ 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.)
 
-%%\enlargethispage{\baselineskip}
-
-\mybigspace This \mymarginpar{\textbf{userf}} is the last 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)
-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
-provided a third cross-referencing system (the others being
-\textsf{crossref} and \textsf{xref}), and have chosen the name
-\textsf{userf} because it might act as a mnemonic for its function.
+\mybigspace See \colmarginpar{\textbf{userf}}
+section~\ref{sec:related}, below.
 
-\mylittlespace In order to use this system, you should start by
-entering both the original and its translation into your .bib file,
-just as you normally would.  The mechanism works for any entry type,
-and the two entries need not be of the same type.  In the entry for
-the \emph{translation}, you put the cite key of the original into the
-\textsf{userf} field.  In the \emph{original's} entry, you need to
-include something that will prevent the entry from being printed
-separately in the bibliography --- \texttt{skipbib} in the
-\textsf{options} field will work, as would something in the
-\textsf{keywords} field in conjunction with a \texttt{notkeyword=}
-switch in the \cmd{printbibliography} command.  In this standard case,
-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: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
-language in \textsf{origlanguage}, and instead of \texttt{originally
-  published as}, you'll get \texttt{French edition:} or \texttt{Latin
-  edition:}, etc.\ (aristotle:metaphy:gr, aristotle:metaphy:trans).
+%%\enlargethispage{\baselineskip}
 
 \mybigspace Standard \mymarginpar{\textbf{venue}} \textsf{biblatex}
 offers this field for use in \textsf{proceedings} and
@@ -3911,7 +3877,7 @@ instead.  Anything in a \textsf{venue} field will be ignored.
 field, currently only available in \textsf{misc} and \textsf{patent}
 entries in \textsf{biblatex-chicago-notes}.
 
-\mybigspace Standard \colmarginpar{\textbf{volume}} \textsf{biblatex}
+\mybigspace Standard \mymarginpar{\textbf{volume}} \textsf{biblatex}
 field.  It holds the volume of a \textsf{journaltitle} in
 \textsf{article} (and some \textsf{review}) entries, and also the
 volume of a multi-volume work in many other sorts of entry.  The
@@ -3924,11 +3890,11 @@ possibility of this information appearing \emph{after} the publication
 data, just before page numbers.  In the past, if you wanted the volume
 information to appear here, you had to leave that information out of
 your .bib entry and give it in the \textsf{pages} or \textsf{postnote}
-field.  Now, you can use the new \textsf{biblatex-chicago} option
-\mycolor{\texttt{delayvolume}} \colmarginpar{\texttt{delayvolume}} in
-your preamble or in the \textsf{options} field of an entry to ensure
-that any \textsf{volume} information that would normally have appeared
-just before the publication data in a long note appears after it.
+field.  Now, you can use the \textsf{biblatex-chicago} option
+\texttt{delayvolume} \mymarginpar{\texttt{delayvolume}} in your
+preamble or in the \textsf{options} field of an entry to ensure that
+any \textsf{volume} information that would normally have appeared just
+before the publication data in a long note appears after it.
 
 \mylittlespace The \textsf{volume} information in both books and
 periodicals, and in both the bibliography and long notes, can appear
@@ -3937,16 +3903,16 @@ periodicals, and in both the bibliography and long notes, can appear
 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 new command \mycolor{\cmd{postvolpunct}}
-\colmarginpar{\cmd{postvolpunct}}.  By default it prints
-\cmd{addcolon}, but you can use \cmd{renewcommand\{\textbackslash
+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}.
 
 %%\enlargethispage{\baselineskip}
 
-\mybigspace Standard \colmarginpar{\textbf{volumes}} \textsf{biblatex}
+\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;
@@ -3955,14 +3921,13 @@ 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 new
-option \mycolor{\texttt{hidevolumes}},
-\colmarginpar{\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.
+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.
 
 \mybigspace A \mymarginpar{\textbf{xref}} modified \textsf{crossref}
 field provided by \textsf{biblatex}, which prevents inheritance of any
@@ -3978,6 +3943,325 @@ can include that guess in square brackets instead of, or after, the
 \enquote{n.d.}\ abbreviation.  Cf.\ bedford:photo, clark:mesopot,
 leo:madonna, ross:thesis.
 
+\subsubsection{\mycolor{Fields for Related Entries}}
+\label{sec:related}
+
+As \textsf{biblatex.pdf} puts it (§~3.4), \enquote{Almost all
+  bibliography styles require authors to specify certain types of
+  relationship between entries such as \enquote{Reprint of},
+  \enquote{Reprinted in,} etc. It is impossible to provide data fields
+  to cover all of these relationships and so \textsf{biblatex}
+  provides a general mechanism for this using the entry fields
+  \textsf{related}, \textsf{relatedtype} and \textsf{relatedstring}.}
+Before this mechanism was available \textsf{biblatex-chicago}
+attempted to provide a similar but much more limited set of
+inter-entry relationships using the \textsf{biblatex} fields
+\textsf{origlanguage}, \textsf{origlocation}, \textsf{origpublisher},
+\textsf{pubstate}, \textsf{reprinttitle}, and \textsf{userf}.  All of
+these still work just as they always have or, I hope, somewhat better
+than they always have after many recent bug fixes, but the more
+general and more powerful \textsf{biblatex} \mycolor{\texttt{related}}
+mechanism is also available.  It can provide much of what the older
+system provided and a great deal that it couldn't.  What follows is a
+field-by-field discussion of the options now available.
+
+\mybigspace In \mymarginpar{\textbf{origlanguage}} keeping with the
+\emph{Manual}'s specifications, I have fairly thoroughly redefined
+\textsf{biblatex}'s facilities for treating translations.  The
+\textsf{origtitle} field isn't used, while the \textsf{language} and
+\textsf{origdate} fields have been press-ganged for other duties.  The
+\textsf{origlanguage} field, for its part, retains a dual role in
+presenting translations in a bibliography.  The details of the
+\emph{Manual}'s suggested treatment when both a translation and an
+original are cited may be found below under \textbf{userf}.  Here,
+however, I simply note that the introductory string used to connect
+the translation's citation with the original's is \enquote{Originally
+  published as,} which I suggest may well be inaccurate in a great
+many cases, as for instance when citing a work from classical
+antiquity, which will most certainly not \enquote{originally} have
+been published in the Loeb Classical Library.  Although not, strictly
+speaking, authorized by the \emph{Manual}, I have provided another way
+to introduce the original text, using the \textsf{origlanguage} field,
+which must be provided \emph{in the entry for the translation, not the
+  original text} (aristotle:metaphy:trans).  If you put one of the
+standard \textsf{biblatex} bibstrings there (enumerated below), then
+the entry will work properly across multiple languages.  Otherwise,
+just put the name of the language there, localized as necessary, and
+\textsf{biblatex-chicago} will eschew \enquote{Originally published
+  as} in favor of, e.g., \enquote{Greek edition:} or \enquote{French
+  edition:}.  This has no effect in notes, where only the work cited
+--- original or translation --- will be printed, but it may help to
+make the \emph{Manual}'s suggestions for the bibliography more
+palatable.  \textbf{NB:} You can use the \mycolor{\textsf{relatedtype}
+  \texttt{origpubas}} with a customized
+\mycolor{\textsf{relatedstring}} field to achieve the same ends.
+
+\mylittlespace That was the first usage, in keeping at least with the
+spirit of the \emph{Manual}.  I have also, perhaps less in keeping
+with that specification, retained some of \textsf{biblatex}'s
+functionality for this field.  If an entry doesn't have a
+\textsf{userf} field, and therefore won't be combining a text and its
+translation in the bibliography, you can also use
+\textsf{origlanguage} as the standard styles use it, so that instead
+of saying, e.g., \enquote{translated by X,} the entry will read
+\enquote{translated from the German by X.}  The \emph{Manual} doesn't
+mention this, but it may conceivably help avoid certain ambiguities in
+some citations.  As in \textsf{biblatex}, if you wish to use this
+functionality, you have to provide \emph{not} the name of the
+language, but rather a bibliography string, which may, at the time of
+writing, be one of \texttt{american}, \texttt{brazilian},
+\texttt{danish}, \texttt{dutch}, \texttt{english}, \texttt{french},
+\texttt{german}, \texttt{greek}, \texttt{italian}, \texttt{latin},
+\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
+\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 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
+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 \mycolor{\texttt{related}}
+field, though the \mycolor{\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 \mycolor{\texttt{related}} field, though the
+\mycolor{\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.
+
+\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.)
+Please remember that, currently, if you put anything besides
+\texttt{reprint} in the \textsf{pubstate} field it will silently be
+ignored, but this may change in future releases.  \textbf{NB:} The
+\textsf{pubstate} functionality currently has no equivalent using the
+\mycolor{\textsf{related}} field.
+
+\mybigspace This \colmarginpar{\textbf{related}} field is required to
+use \textsf{biblatex's} \mycolor{\textsf{related}} functionality, and
+it should contain the entry key or keys from which \textsf{biblatex}
+should extract data for presentation not on its own, but rather in the
+bibliography entry (or long note) which contains the \textsf{related}
+field itself.  Indeed, unless you change the defaults using the
+\mycolor{\textsf{relatedoptions}} field this data will only appear in
+such entries, never on its own.  Without a
+\mycolor{\textsf{relatedtype}} field, this will print the default
+type, equivalent to a long note citation \emph{immediately after} the
+bibliography entry containing the \textsf{related} field, with no
+intervening string.  You can specify a string using the
+\mycolor{\textsf{relatedstring}} field, so in effect this presents a
+powerful mechanism for presenting full references to related material
+of any sort whatsoever.
+
+\mylittlespace By \colmarginpar{\texttt{related=bib}} default, the
+package option \mycolor{\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.)
+
+\mybigspace This \colmarginpar{\textbf{relatedoptions}} field will, I
+should expect, only be needed very rarely.  If you want to set
+entry-level options for a \mycolor{\textsf{related}} entry this is
+where you can do it, though please remember one important detail.  By
+default, \textsf{Biber} sets this option to \texttt{dataonly}, which
+among other things prevents the \mycolor{\textsf{related}} entry from
+appearing separately in the bibliography.  If you use the field
+yourself, then you'll need to include \texttt{dataonly} as one of the
+options therein to maintain this effect.  Of course, it may be you
+don't want all the effects of \texttt{dataonly}, so you can tailor it
+however you wish.  See \textsf{biblatex.pdf} §~3.4.
+
+\mybigspace The \colmarginpar{\textbf{relatedstring}} procedure for
+choosing a string to connect the main entry with its related entry/ies
+is straightforward, the default being a \texttt{bibstring}, if any,
+with the same name as the \mycolor{\textsf{relatedtype}}, or
+alternately a string or strings defined within the driver for that
+\mycolor{\textsf{relatedtype}}, as happens with the types
+\mycolor{\texttt{origpubin}} and \mycolor{\texttt{bytranslator}}.
+Failing these, you can supply your own in the
+\mycolor{\textsf{relatedstring}} field, either in the form of the name
+of a pre-defined \texttt{bibstring} or as any text you choose, and
+anything in this field always takes precedence over the automatic
+choices.  If your non-\texttt{bibstring} starts with a lowercase
+letter then \textsf{biblatex-chicago} will capitalize it automatically
+for you depending on context (weed:flatiron).  I have not altered the
+standard \textsf{relatedtype} strings, and have indeed changed the
+\textsf{reprinttitle} mechanism to use the
+\mycolor{\texttt{reprintfrom}} string, which works better
+syntactically in this context.
+
+\mybigspace The \colmarginpar{\textbf{relatedtype}} standard
+\textsf{biblatex} styles define six \mycolor{\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:
+
+\begin{description}
+\item[\qquad \mycolor{bytranslator:}] This prints a full citation of a
+  translation, starting with the (localized) string
+  \enquote{Translated by \textsf{translator} as \textsf{Title},
+    \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}
+  mechanism provides the other, as does the
+  \mycolor{\texttt{origpubas} \textsf{relatedtype}} (see below).
+\item[\qquad \mycolor{default:}] This is the macro used when no
+  \mycolor{\textsf{relatedtype}} is defined.  It prints, as in the
+  standard styles, and with no intervening string, a full citation of
+  the \mycolor{\textsf{related}} entries.  In
+  \textsf{biblatex-chicago-notes}, the citation is in long note form,
+  rather than bibliography form, as this is the usual practice in the
+  \emph{Manual}.
+\item[\qquad \mycolor{multivolume:}] This briefly lists the individual
+  volumes in a multi-volume work, and works much as in the standard
+  styles.  The \emph{Manual}, as far as I can see, has little to say
+  on the matter.
+\item[\qquad \mycolor{origpubas:}] This type can, if you want, replace
+  the old \textsf{userf} mechanism, described below, for presenting an
+  original with its translation.  It's quite similar to the
+  \mycolor{\texttt{default}} type, but with a \texttt{bibstring}
+  automatically connecting the entry with its \textsf{related}
+  entries.  You can identify other sorts of relationships if you
+  change the introductory string using \textsf{relatedstring}.
+\item[\qquad \mycolor{origpubin:}] I haven't altered this from the
+  \textsf{biblatex} default at all, and it presents reprint
+  information \emph{after} the main entry rather than within it.  The
+  \emph{Manual} seems to prefer the latter for the notes \&
+  bibliography style and, in some circumstances, the former for
+  author-date.
+\item[\qquad \mycolor{reprintfrom:}] This type provides a replacement
+  for the old \textsf{reprinttitle} mechanism described below.  As in
+  the standard styles, it presents a fuller reference to the reprinted
+  material than does \mycolor{\texttt{origpubin}}, and is designed
+  particularly for presenting pieces formerly printed in other
+  collections or perhaps essays collected from various periodicals.
+  (In \textsf{biblatex-chicago} it contains some kludges to cope with
+  possible \textsf{babel} language environments, so if you find it
+  behaving oddly please let me know, including whether you are using
+  \textsf{babel} [which I've tested] or \textsf{polyglossia} [which I
+  haven't].)
+\end{description}
+
+\mybigspace \textbf{NB:} \mymarginpar{\textbf{reprinttitle}}
+\textbf{If you have been using this feature, you may want to have a
+  look at the} \mycolor{\textsf{relatedtype} \texttt{reprintfrom}},
+\textbf{documented above, for a better solution to this problem, one
+  that also allows you to change the introductory string using the}
+\mycolor{\textsf{relatedstring}} \textbf{field.  The}
+\textsf{reprinttitle} \textbf{field will continue to work as before,
+  however.}  At the request of Will Small, I have included a means of
+providing the 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{Reprinted
+  from.}  Please see the documentation on \textsf{userf} below for all
+the details on how to create .bib entries for presenting your data.
+
+\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)
+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
+provided a third cross-referencing system (the others being
+\textsf{crossref} and \textsf{xref}), and have chosen the name
+\textsf{userf} because it might act as a mnemonic for its function.
+
+\mylittlespace In order to use this system, you should start by
+entering both the original and its translation into your .bib file,
+just as you normally would.  The mechanism works for any entry type,
+and the two entries need not be of the same type.  In the entry for
+the \emph{translation}, you put the cite key of the original into the
+\textsf{userf} field.  In the \emph{original's} entry, you need to
+include something that will prevent the entry from being printed
+separately in the bibliography --- \texttt{skipbib} in the
+\textsf{options} field will work, as would something in the
+\textsf{keywords} field in conjunction with a \texttt{notkeyword=}
+switch in the \cmd{printbibliography} command.  In this standard case,
+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: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
+language in \textsf{origlanguage}, and instead of \texttt{originally
+  published as}, you'll get \texttt{French edition:} or \texttt{Latin
+  edition:}, etc.\ (aristotle:metaphy:gr, aristotle:metaphy:trans).
+\textbf{NB:} You can use the \mycolor{\textsf{relatedtype}
+  \texttt{origpubas}} to replicate the \textsf{userf} functionality,
+and you can also customize the \mycolor{\textsf{relatedstring}} field
+to achieve the same result as with \textsf{origlanguage}.
+
+
 \subsection{Commands}
 \label{sec:commands}
 
@@ -3996,7 +4280,7 @@ These commands allow you to fine-tune the presentation of your
 references in both notes and bibliography.  You can find many examples
 of their usage in \textsf{notes-test.bib}, and I shall try to point
 you toward a few such entries in what follows.  \textbf{NB:}
-\textsf{biblatex's} \cmd{mkbibquote} command is now mandatory in some
+\textsf{biblatex's} \cmd{mkbibquote} command is mandatory in some
 situations.  See its entry below.
 
 \mybigspace Version \mymarginpar{\textbf{\textbackslash autocap}} 0.8
@@ -4010,10 +4294,10 @@ than the kludge I designed for a previous version of
 single-letter \cmd{bibstring} commands in your .bib file is obsolete.
 
 \mylittlespace In order somewhat to reduce the burden on users even
-further, I have, following Lehman's example, implemented a new system
-which automatically tracks the capitalization of certain fields in
-your .bib file.  I chose these fields after a non-scientific survey of
-entries in my own databases, so of course if you have ideas for the
+further, I have, following \textsf{biblatex's} example, implemented a
+system which automatically tracks the capitalization of certain fields
+in your .bib file.  I chose these fields after a non-scientific survey
+of entries in my own databases, so of course if you have ideas for the
 extension of this facility I would be most interested to hear them.
 In order to take advantage of this functionality, all you need do is
 begin the data in the appropriate field with a lowercase letter,
@@ -4027,15 +4311,16 @@ mechanism without printing anything itself.  Here, then, is the
 complete list of fields where this functionality is active:
 
 \begin{enumerate}
+\setlength{\parskip}{-4pt}
 \item The \textbf{addendum} field in all entry types.
 \item The \textbf{booktitleaddon} field in all entry types.
 \item The \textbf{edition} field in all entry types.  (Numerals work
   as you expect them to here.)
 \item The \textbf{maintitleaddon} field in all entry types.
 \item The \textbf{note} field in all entry types.
-\item The \mycolor{\textbf{part}} field in entry types that use it.
-\item The \mycolor{\textbf{prenote}} field prefixed to citation
-  commands.
+\item The \textbf{part} field in entry types that use it.
+\item The \textbf{prenote} field prefixed to citation commands.
+\item The \mycolor{\textbf{relatedstring}} field in all entry types.
 \item The \textbf{shorttitle} field in the \textsf{review}
   (\textsf{suppperiodical}) entry type and in the \textsf{misc} type,
   in the latter case, however, only when there is an
@@ -4059,38 +4344,36 @@ accidentally do so in one of the above fields, it 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.
 
-\mybigspace This \mymarginpar{\textbf{\textbackslash bibstring}} is
-Lehman's 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.  This command was designed by Philipp Lehman, and has now
-been included in version 0.8 of \textsf{biblatex}.  For yet greater
-convenience I have implemented, following Lehman'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 new 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.
+\mybigspace This \mymarginpar{\textbf{\textbackslash bibstring}} is a
+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 a new functionality which sometimes allows you simply to
-input, for example, \texttt{newseries} instead of
+introduced functionality which sometimes allows you simply to input,
+for example, \texttt{newseries} instead of
 \cmd{bib\-string\{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
@@ -4099,11 +4382,9 @@ cases either form will work.  This functionality is available in the
 \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.  These are the
-places, as far as I can make out, where \textsf{biblatex's} standard
-styles support this feature, and I have added the last,
-style-specific, one.  If Lehman generalizes it still further in a
-future release, I shall do the same, if possible.
+\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.
 
 \mybigspace In \mymarginpar{\textbf{\textbackslash custpunct} \\
   \textbf{\textbackslash custpunctb}} common with other American
@@ -4136,7 +4417,7 @@ 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 \colmarginpar{\textbf{\textbackslash
+\mybigspace These \mymarginpar{\textbf{\textbackslash
     foottextcite\\\textbackslash foottextcites}} two commands look
 like citation commands, but are in fact wrappers for customizing the
 behavior of the \cmd{textcite} and \cmd{textcites} citation commands
@@ -4149,15 +4430,15 @@ preamble.  The default definitions are: \texttt{\{\textbackslash
   addspace\textbackslash headlessparenshortcite\}} and
 \texttt{\{\textbackslash addspace\textbackslash
   headlessparenshortcites\}}.  If you wanted to return to the default
-behavior of the previous release of \textsf{biblatex-chicago}, for
+behavior of previous releases of \textsf{biblatex-chicago}, for
 example, you could change the first to: \texttt{\{\textbackslash
   newcunit\textbackslash bibstring\{in\}\textbackslash
   addspace\textbackslash headlesscite\}}, and the second similarly,
 only using \cmd{headlesscites}.  (There is also, by the way, a
-\cmd{headlessparencite(s)} command if you want to retain the long
+\cmd{head\-lessparencite(s)} command if you want to retain the long
 citations inside the parentheses.)
 
-\enlargethispage{\baselineskip}
+%\enlargethispage{\baselineskip}
 
 \mybigspace This \mymarginpar{\textbf{\textbackslash isdot}} is a
 standard \textsf{biblatex} macro, which in previous releases of
@@ -4186,7 +4467,7 @@ command \cmd{printorigdate}.)
 
 \mybigspace This \mymarginpar{\textbf{\textbackslash mkbibquote}} is
 the standard \textsf{biblatex} command, which requires attention here
-because it is a crucial part of the mechanism of Lehman's
+because it is a crucial part of the mechanism for the
 \enquote{American} punctuation system.  If you look in
 \textsf{chicago-notes.cbx} you'll see that the quoted fields, e.g., an
 \textsf{article} or \textsf{incollection title}, have this command in
@@ -4235,7 +4516,7 @@ the latter isn't strictly necessary in texts using an American style,
 to which \textsf{biblatex} defaults when \textsf{csquotes} isn't
 loaded.
 
-\mybigspace The \colmarginpar{\textbf{\textbackslash postvolpunct}}
+\mybigspace The \mymarginpar{\textbf{\textbackslash postvolpunct}}
 \emph{Manual} (14.121) unequivocally prescribes that when a
 \textsf{volume} number appears immediately before a page number,
 \enquote{the abbreviation \emph{vol.}\ is omitted and a colon
@@ -4244,7 +4525,7 @@ loaded.
 of a book or of a periodical, and it appears to be a surprising and
 unwelcome feature for many users, conflicting as it may do with
 established typographic traditions in a number of contexts.  Clea~ F.\
-Rees has requested a way to customize this, so I have provided the new
+Rees requested a way to customize this, so I have provided the
 \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,
@@ -4255,7 +4536,7 @@ 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}
+%\enlargethispage{-\baselineskip}
 
 \mybigspace This \mymarginpar{\textbf{\textbackslash reprint}} and the
 following 7 macros all help \textsf{biblatex-chicago-notes} cope with
@@ -4307,7 +4588,7 @@ currently you'll need to add either \texttt{de} or \texttt{d'} after
 this command in your .bib files to make the references come out right.
 I'm working on this.)  See chaucer:liferecords.
 
-\enlargethispage{-\baselineskip}
+%\enlargethispage{-\baselineskip}
 
 \mybigspace As \mymarginpar{\textbf{\textbackslash
     partedit-\\andcomp}} before, but for use when an editor is also a
@@ -4416,7 +4697,7 @@ included this multicite command to enable you to present such a list,
 if the need arises.  Remember that you'll have to put it inside a
 \cmd{footnote} command manually.
 
-%\enlargethispage{\baselineskip}
+\enlargethispage{-\baselineskip}
 
 \mybigspace Another \mymarginpar{\textbf{\textbackslash footfullcite}}
 standard \textsf{biblatex} command, modified to work properly with
@@ -4433,6 +4714,42 @@ is a standard command, and it too provides a full citation, but unlike
 the previous command it doesn't automatically place it in a footnote.
 It may be useful within long textual notes.
 
+\mybigspace Arne \colmarginpar{\textbf{\textbackslash gentextcite}}
+Skjærholt 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.  As a convenience for users, I've also ported this to
+the notes \& bibliography style.  In most respects it behaves exactly
+like \cmd{textcite}, on which see below.  The difference is that I've
+added a new optional field to the front of the command to allow you to
+choose which declensional ending to add to the name.  If you don't
+specify this field, you'll get the standard English \enquote{\,'s\,}.
+If you want something different, then you'll need to present a third
+option to the command, like so:
+\cmd{gentextcite[<ending>][][]\{entry:key\}}.  You must include the
+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 \mycolor{\cmd{gentextcites}} command as
+well, and for it you may need to specify
+\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\}}.
+
+\mylittlespace The syntax of multiple authors' names in running text
+is unpredictable.  There is currently no way to add the genitival
+ending to all the names attached to a single citation key, so it will
+only appear at the end of a group of names in such a case.  (This is
+in keeping with the usual syntax when referring to a multi-author
+work, at least in English.)  When using \mycolor{\cmd{gentextcites}},
+however, you can control whether the ending appears after the name(s)
+attached to each citation key, or whether it only appears after the
+names attached to the last key.  By default, it only appears after the
+last, but the \mycolor{\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 headlesscite}}
 Lundin requested a more generalized \cmd{headlesscite} macro,
 suppressing the author's name in specific contexts while allowing
@@ -4483,8 +4800,8 @@ 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.)
 
-\mybigspace Norman \colmarginpar{\textbf{\textbackslash textcite}}
-Gray started a discussion on
+\mybigspace Norman \mymarginpar{\textbf{\textbackslash textcite}} Gray
+started a discussion on
 \href{http://tex.stackexchange.com/questions/67837/citations-as-nouns-in-biblatex-chicago}{Stackexchange}
 which established both that \textsf{biblatex} had begun including a
 \cmd{textcite} command in its verbose styles and that
@@ -4500,20 +4817,18 @@ request within the package, but there are now at least commands
 functionality is a little complicated.  In the main text, they will
 provide an \textsf{author's} name(s), followed immediately by a foot-
 or endnote which contains the full (or short) reference, following the
-usual rules.  If you use \cmd{textcite} inside \colmarginpar{New!} a
-foot- or endnote, then the default behavior has changed for this
-release, but I've made that behavior configurable, so you can tailor
-it to your needs.  Now, by default, for both \cmd{textcite} and
-\cmd{textcites}, 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 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
+usual rules.  If you use \cmd{textcite} inside a foot- or endnote,
+then the default behavior, for both \cmd{textcite} and
+\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
+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
 syntactically.  If you want to configure this behavior for either
-citation command, please see \mycolor{\cmd{foottextcite}} and
-\mycolor{\cmd{foottextcites}} in section~\ref{sec:formatcommands}.
+citation command, please see \cmd{foottextcite} and
+\cmd{foottextcites} in section~\ref{sec:formatcommands}.
 
 \mylittlespace If you look at \textsf{chicago-notes.cbx}, you'll see a
 number of other citation commands, but those are intended for internal
@@ -4552,9 +4867,11 @@ for the \cmd{ifciteseen} test is enabled globally.
 for the long format when presenting dates, slightly shortened when
 presenting date ranges.
 
+\enlargethispage{-\baselineskip}
+
 \mylittlespace The \mymarginpar{\texttt{dateabbrev=\\false}}
-\emph{Manual} prefers full month names in the notes \&\ bibliography
-style.
+\emph{Manual} prefers to use full month names in the notes \&\
+bibliography style.
 
 \mybigspace This \mymarginpar{\texttt{ibidtracker=\\constrict}}
 enables the use of \enquote{Ibid} in notes, but only in the most
@@ -4565,6 +4882,22 @@ 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.
 
+\mylittlespace Roger \colmarginpar{\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}
+\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.}
+You can turn this on when loading \textsf{biblatex-chicago} by setting
+\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} §~2.3.3.
+
 \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
@@ -4572,12 +4905,12 @@ case, \texttt{Ibid} alone will be printed, without the page reference,
 following the specification (14.29).
 
 \mylittlespace These \mymarginpar{\textsf{\texttt{maxbibnames\\=10\\
-      minbibnames\\=7}}} two options are new, and control the number
-of names printed in the bibliography when that number exceeds 10.
-These numbers follow the recommendations of the \emph{Manual} (14.76),
-and they are different from those for use in notes.  With
+      minbibnames\\=7}}} two options control the number of names
+printed in the bibliography when that number exceeds 10.  These
+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{printbibliography} command at the bottom
+\texttt{minnames} in the \cmd{printbiblio\-graphy} 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.
@@ -4588,6 +4921,16 @@ commands for controlling, among other things, the printing of
 \enquote{Ibid.}  It tracks individual pages if \LaTeX\ is in oneside
 mode, or whole spreads in twoside mode.
 
+\mylittlespace This \colmarginpar{\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 \mycolor{\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{sortcase=\\false}} turns off
 the sorting of uppercase and lowercase letters separately, a practice
 which the \emph{Manual} doesn't appear to recommend.
@@ -4641,66 +4984,60 @@ chosen font.  The default definition is:
 
 \mylittlespace At \mymarginpar{\texttt{losnotes}
   \&\\\texttt{losendnotes}} the request of Kenneth Pearce, I have
-added two new \texttt{bibenvironments} to \textsf{chicago-notes.bbx},
-for use with the \texttt{env} option to the \cmd{printshorthands}
-command.  The first, \texttt{losnotes}, is designed to allow a list of
+added two \texttt{bibenvironments} to \textsf{chicago-notes.bbx}, for
+use with the \texttt{env} option to the \cmd{printshorthands} command.
+The first, \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 latter case to clear up some spurious punctuation and white
 space that I see on my system when using endnotes.  (You'll probably
 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.)  Please see the documentation of
-\textsf{shorthand} in section~\ref{sec:entryfields} above for further
-options available to you for presenting and formatting the list of
-shorthands.
-
-\mylittlespace The \mymarginpar{\cmd{Declare-}\\\texttt{Labelname}}
-next-generation backend \textsf{Biber} offers enhanced functionality
-in many areas, two of which I've implemented in this release.
-\cmd{DeclareLabelname} allows you to add name fields for consideration
-when \textsf{biblatex} is attempting to find a shortened name for
-short notes.  This, for example, allows a compiler (=\textsf{namec})
-to appear at the head of short notes without any other intervention
-from the user, rather than requiring a \textsf{shortauthor} field as
-previous releases of \textsf{biblatex-chicago} did.  In point of fact,
-I have implemented this functionality in such a way as to make it
-available even to users of other backends, but this required reducing
-its flexibility considerably.  When \textsf{biblatex} reaches version
-2.0, \textsf{Biber} will become a requirement, so I recommend getting
-to know it sooner rather than later.
-
-\mylittlespace The
-\mymarginpar{\cmd{Declare-}\\\texttt{SortingScheme}} second
-\textsf{Biber} enhancement I have implemented allows you to include
-almost any field whatsoever in \textsf{biblatex's} sorting algorithms
-for the bibliography, so that a great many more entries will be sorted
-correctly automatically rather than requiring manual intervention in
-the form of a \textsf{sortkey} field or the like.  Code in
-\textsf{biblatex-chicago.sty} detects whether you are using
-\textsf{Biber}, and if and only if this is the case changes the
-sorting scheme to a custom one (\texttt{cms}), a Chicago-specific
-variant of the default \texttt{nty}.  (You can find its definition in
-\textsf{chicago-notes.cbx}.)  Users of all other backends will still
-be using \texttt{nty}.
-
-%%\enlargethispage{\baselineskip}
-
-\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
+\cmd{footnote} command.)  If \colmarginpar{New} you use a command like
+\cmd{printbiblist\{shortjournal\}} to print a list of journal
+abbreviations, you can use the \mycolor{\texttt{sjnotes}} and
+\mycolor{\texttt{sjendnotes}} \texttt{bibenvironments} in exactly the
+same way.  Please see the documentation of \textsf{shorthand} and
+\mycolor{\textsf{shortjournal}} in section~\ref{sec:entryfields} above
+for further options available to you for presenting and formatting
+these two types of \texttt{biblist}.
+
+\mylittlespace Formerly
+\mymarginpar{\cmd{Declare-}\\\texttt{Labelname}} available only to
+those using \textsf{Biber}, but since version 3.0 handled by
+\textsf{biblatex} itself, \cmd{DeclareLabelname} allows you to add
+name fields for consideration when \textsf{biblatex} is attempting to
+find a shortened name for short notes.  This, for example, allows a
+compiler (=\textsf{namec}) to appear at the head of short notes
+without any other intervention from the user, rather than requiring a
+\textsf{shortauthor} field as previous releases of
+\textsf{biblatex-chicago} did.  The default search order for the
+Chicago styles is \textsf{shortauthor}, \textsf{author},
+\textsf{shorteditor}, \textsf{namea}, \textsf{editor}, \textsf{nameb},
+\textsf{translator}, \textsf{namec}.  You can set the option
+\texttt{use<name>=false} in entries or when loading
+\textsf{biblatex-chicago} to exclude individual fields from appearing
+in short notes, or indeed at the head of long notes and bibliography
+entries.  See the documentation of those name types in
+section~\ref{sec:entryfields} for further details.
+
+\mylittlespace I \mymarginpar{\cmd{Declare-}\\\texttt{SortingScheme}}
+have provided, using this declaration, a custom sorting algorithm for
+the bibliography.  The idea is that \textsf{biblatex} can use any
+field whatsoever for sorting, so that a great many more entries will
+be sorted correctly automatically rather than requiring manual
+intervention in the form of a \textsf{sortkey} field or the like.
+Code in \textsf{biblatex-chicago.sty} loads the custom scheme
+\enquote{\texttt{cms},} a Chicago-specific variant of the default
+\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} will no longer need a
-\textsf{sortkey} set.  The main disadvantage should only occur very
-rarely, and appears because the supplemental name fields are treated
-differently from the standard name fields by \textsf{biblatex}.
-Ordinarily, you can set, for example, \texttt{useauthor=false} in the
-\textsf{options} field to remove the \textsf{author's} name from
-consideration for sorting purposes.  The Chicago-specific option
-\textsf{usecompiler=false}, however, doesn't remove \textsf{namec}
-from such consideration, so in an entry like chaucer:alt you \emph{do}
-need a \textsf{sortkey} or else it will be alphabetized by
-\textsf{namec} rather than by \textsf{title}.
+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}
@@ -4717,6 +5054,8 @@ 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
@@ -4732,8 +5071,6 @@ preamble, for the whole document, or on a per-entry basis in the
 field will always be printed, but the \texttt{only} switch will still
 eliminate any \textsf{url}.
 
-% %\enlargethispage{\baselineskip}
-
 \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
@@ -4819,8 +5156,8 @@ you can change it either in the preamble for the whole document or,
 for specific fields, in the \textsf{options} field of individual
 entries.
 
-\mylittlespace At \colmarginpar{\texttt{booklongxref=\\true}} the
-request of Bertold Schweitzer, I have included two new options for
+\mylittlespace At \mymarginpar{\texttt{booklongxref=\\true}} the
+request of Bertold Schweitzer, I have included two options 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.  This option controls whether multiple
@@ -4850,10 +5187,44 @@ This option can be set either in the preamble or in the
 \textsf{options} field of individual entries.  For controlling the
 behavior of \textsf{inbook}, \textsf{incollection},
 \textsf{inproceedings}, and \textsf{letter} entries, please see
-\mycolor{\texttt{longcrossref}}, below, and also the documentation of
+\texttt{longcrossref}, below, and also the documentation of
 \textsf{crossref} in section~\ref{sec:entryfields}.
 
-\mylittlespace If \colmarginpar{\texttt{hidevolumes=\\true}} both a
+\mylittlespace Roger
+\colmarginpar{\texttt{ctitleaddon=\\comma\\ptitleaddon=\\period}} Hart
+requested a way to control the punctuation printed before the
+\textsf{titleaddon}, \textsf{booktitleaddon}, and
+\textsf{maintitleaddon} fields.  By default, this is
+\cmd{addcomma\cmd{add\-space}} (\mycolor{\textsf{ctitleaddon}}) for all
+occurrences in notes and for nearly all \textsf{book-} and
+\textsf{maintitleaddons} in the bibliography, while
+\cmd{addperiod\cmd{addspace}} (\mycolor{\textsf{ptitleaddon}}) is the
+default 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.
+(Cf.\ coolidge:speech and schubert:muellerin.)  The accepted option
+keys are:
+
+\begin{description}
+\setlength{\parskip}{-4pt}
+\item[\qquad none] = no punctuation at all
+\item[\qquad space] = \cmd{addspace}
+\item[\qquad comma] = \cmd{addcomma\cmd{addspace}}
+\item[\qquad period] = \cmd{addperiod\cmd{addspace}}
+\item[\qquad colon] = \cmd{addcolon\cmd{addspace}}
+\item[\qquad semicolon] = \cmd{addsemicolon\cmd{addspace}}
+\end{description}
+
+If you need something a little more exotic, you can directly
+\cmd{renewcommand} either \cmd{ctitleaddonpunct} or
+\cmd{ptitleaddonpunct} (or both) in your preamble, but it's worth
+remembering that the redefinition will hold for all instances, unless
+you use the \textsf{options} field in your other entries with a
+\textsf{titleaddon} field.  A simpler solution might be to set the
+relevant option to \texttt{none} in your entry and then include the
+punctuation in the \textsf{titleaddon} field itself.
+
+\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
 \textsf{biblatex-chicago} will ordinarily suppress the
@@ -4865,7 +5236,7 @@ option, set to \texttt{true} by default, controls whether to print the
 \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 \colmarginpar{\texttt{longcrossref=\\false}} is
+\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
@@ -4900,35 +5271,45 @@ governed by the following options:
 This option can be set either in the preamble or in the
 \textsf{options} field of individual entries.  For controlling the
 behavior of \textsf{book}, \textsf{bookinbook}, \textsf{collection},
-and \textsf{proceedings} entries, please see
-\mycolor{\texttt{booklongxref}}, above, and also the documentation of
-\textsf{crossref} in section~\ref{sec:entryfields}.
+and \textsf{proceedings} entries, please see \texttt{booklongxref},
+above, and also the documentation of \textsf{crossref} in
+section~\ref{sec:entryfields}.
 
-\mylittlespace This \mymarginpar{\texttt{usecompiler=\\true}} option
-enables automatic use of the name of the compiler (in the
-\textsf{namec} field) at the head of an entry, usually in the absence
-of an \textsf{author}, \textsf{editor}, or \textsf{translator}, in
-accordance with the specification (\emph{Manual} 14.87).  It may also,
-like \texttt{useauthor}, \texttt{useeditor}, and
-\texttt{usetranslator}, be disabled on a per-entry basis by setting
-\texttt{usecompiler=false} in the \textsf{options} field.  Please
-remember that, because \textsf{namec} isn't a standard
-\textsf{biblatex} field, it may take a little extra effort to get it
-to work smoothly.  The package should now automatically take care of
-finding a name for short notes, but it will alphabetize by this name
-in the bibliography only if you use \textsf{Biber}, failing which
-you'll need to provide a \textsf{sortkey} for this purpose.  (These
-rules don't apply when you modify the \textsf{editor's} identifying
-string using the \textsf{editortype} field, which is the procedure I
-recommend if the entry-heading compiler is only a compiler, and not
-also, e.g., an editor or a translator.)  Cf.\
-\cmd{DeclareSortingScheme} and \cmd{DeclareLabelname} in
-section~\ref{sec:formatopts}, above; also, chaucer:alt for an entry
-where, because none of the names provided appear at the head of the
-reference, you will need to provide a \textsf{sortkey} to stop
-\textsf{Biber} using the \textsf{namec} --- because it's not a
-standard name field, you can stop it being printed at the head of the
-entry, but you can't stop it turning up in the sorting algorithms.
+\mylittlespace This
+\colmarginpar{\texttt{shorthand\\punct\\=space}}
+option controls the punctuation that appears before the first
+introduction of a \textsf{shorthand} field, including the
+\textsf{shorthandintro}, in long notes.  The default is
+\cmd{addspace}, but if this isn't correct for your needs, especially
+if you change the \textsf{shorthandintro} or don't want the whole
+phrase inside parentheses, then you can change it in the preamble or
+in individual entries.  The accepted option keys are:
+
+\begin{description}
+\setlength{\parskip}{-4pt}
+\item[\qquad none] = no punctuation at all
+\item[\qquad space] = \cmd{addspace}
+\item[\qquad comma] = \cmd{addcomma\cmd{addspace}}
+\item[\qquad period] = \cmd{addperiod\cmd{addspace}}
+\item[\qquad colon] = \cmd{addcolon\cmd{addspace}}
+\item[\qquad semicolon] = \cmd{addsemicolon\cmd{addspace}}
+\item[\qquad emdash] =
+  \cmd{addthinspace\cmd{textemdash}\cmd{addthinspace}}
+\item[\qquad endash] = \cmd{addspace\cmd{textendash}\cmd{addspace}}
+\end{description}
+
+You can, in emergencies, directly
+\cmd{renewcommand\{\cmd{shorthandpunct}\}} in the pre\-amble, but it
+might be easier to use the \texttt{none} option to
+\mycolor{\texttt{shorthandpunct}} and hand-craft solutions inside the
+\textsf{shorthandintro} fields of individual entries.
+
+\mylittlespace As \colmarginpar{\texttt{usecompiler=\\true}}
+\textsf{biblatex} automatically includes a \mycolor{\texttt{usenamec}}
+option as standard, the Chicago-specific option \texttt{usecompiler}
+is now deprecated.  Please replace it your documents and .bib files
+with \mycolor{\texttt{usenamec}}, which works much better across the
+board.
 
 \subsubsection{Style Options -- Preamble}
 \label{sec:useropts}
@@ -4950,7 +5331,7 @@ 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 When \colmarginpar{\texttt{compresspages}} set to
+\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).
@@ -4958,7 +5339,7 @@ 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.
 
-\mylittlespace The \colmarginpar{\texttt{delayvolume}} presentation of
+\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
 on the presence or absence of a \textsf{booktitle} or a
@@ -4975,7 +5356,7 @@ basis, to allow you to move \textsf{volume} data to the end of a long
 note.  Please note that this doesn't affect any \textsf{volume} data
 printed \emph{before} a \textsf{maintitle}, but only data that would,
 without this option, be printed \emph{after} a \textsf{booktitle} or
-\textsf{maintitle}.  Cf.\ also \mycolor{\cmd{postvolpunct}}, below.
+\textsf{maintitle}.  Cf.\ also \cmd{postvolpunct}, below.
 
 \mylittlespace Although \mymarginpar{\texttt{footmarkoff}} the
 \emph{Manual} (14.19) recommends specific formatting for footnote (and
@@ -4993,7 +5374,13 @@ revert to the \LaTeX\ default, but of course you also lose a fair
 amount of other formatting, as well.  See section~\ref{sec:loading},
 below.
 
-\mylittlespace Setting \colmarginpar{\texttt{inheritshort\-hand}} this
+\mylittlespace This \colmarginpar{\texttt{genallnames}} option affects
+the choice of which names to present in the genitive case when using
+the \mycolor{\cmd{gentextcites}} command.  Please see the
+documentation of that command in section~\ref{sec:citecommands},
+above.
+
+\mylittlespace Setting \mymarginpar{\texttt{inheritshort\-hand}} this
 option to \texttt{true} allows child entries to inherit the
 \textsf{shorthand} and \textsf{shorthandintro} fields from
 cross-referenced parent entries.  This in turn allows abbreviated
@@ -5003,6 +5390,20 @@ savings.  There are several other steps required to make this all
 function smoothly, so please see the documentation of the
 \textbf{shorthand} field in section~\ref{sec:entryfields}, above.
 
+\mylittlespace This \colmarginpar{\texttt{journalabbrev}} option
+controls the printing of the \mycolor{\textsf{shortjournal}} field in
+place of the \textsf{journaltitle} field 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 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.  Please 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 \mycolor{\textbf{shortjournal}} in
+section~\ref{sec:entryfields}, above.
+
 \mylittlespace The \mymarginpar{\texttt{juniorcomma}} \emph{Manual}
 (6.47) states that \enquote{commas are not required around \emph{Jr.}\
   and \emph{Sr.},} so by default \textsf{biblatex-chicago} has
@@ -5044,7 +5445,7 @@ form.  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 \colmarginpar{\texttt{omitxrefdate}} part of the new
+\mylittlespace As \mymarginpar{\texttt{omitxrefdate}} part of the
 abbreviated cross-referencing functionality for \textsf{book},
 \textsf{bookinbook}, \textsf{collection}, and \textsf{proceedings}
 entries, I have thought it helpful to include, in the abbreviated
@@ -5057,7 +5458,7 @@ harley:ancient:cart, harley:cartography, and harley:hoc; and
 \textsf{crossref} in section~\ref{sec:entryfields}, above.
 
 \mylittlespace Several
-\colmarginpar{\texttt{postnotepunct}\\(experimental)} users, most
+\mymarginpar{\texttt{postnotepunct}\\(experimental)} users, most
 recently David Gohlke, have requested a way to alter the punctuation
 that appears just before the \textsf{postnote} argument of citation
 commands, usually, but perhaps not always, to allow citations to fit
@@ -5065,15 +5466,14 @@ better into the flow of text.  This punctuation is a complex issue in
 the \emph{Manual}, and I've attempted to make
 \textsf{biblatex-chicago} follow the specifications closely.  Still,
 as a first stab at enabling the greater flexibility in punctuation
-that some have requested, I have introduced the
-\mycolor{\texttt{postnotepunct}} package option.  Set to
-\texttt{true}, it 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 \mycolor{experimental}.  Note
-also that the option only affects the \textsf{postnote} field of
+that some have requested, I have introduced the \texttt{postnotepunct}
+package option.  Set to \texttt{true}, it 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 experimental.
+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}
@@ -5122,6 +5522,17 @@ rule intervenes to emphasize this continuation.  I haven't tested this
 code very thoroughly, and it's possible that frequent use of floats
 might interfere with it.  Let me know if it causes problems.
 
+\mylittlespace Stefan \colmarginpar{\texttt{xrefurl}} Björk pointed
+out that when, using the \texttt{longcrossref} or
+\texttt{booklongxref} options, you turn on the automatic abbreviation
+of multiple entries in the same (e.g.) \textsf{collection} or
+\textsf{mvcollection}, you could entirely lose a \textsf{url} that
+might be helpful for locating a source, as the abbreviated forms in
+notes and in the bibliography wouldn't include this information.
+Setting this option to \textsf{true} either in the preamble or in
+individual entries will allow the \textsf{url}, \textsf{doi}, or
+\textsf{eprint} field to appear even in these abbreviated references.
+
 \subsection{General Usage Hints}
 \label{sec:hints}
 
@@ -5177,7 +5588,7 @@ footnotes.  Also in this file is the code that calls
 Chicago-specific bibstrings I've defined unless you provide, in your
 preamble, a \cmd{DeclareLanguageMapping} command adapted for your
 setup, on which see section~\ref{sec:international} below and also
-§§~4.9.1 and 4.11.8 in Lehman's \textsf{biblatex.pdf}.
+§§~4.9.1 and 4.11.8 in \textsf{biblatex.pdf}.
 
 %%\enlargethispage{-\baselineskip}
 
@@ -5211,15 +5622,15 @@ information you're providing.  I've tried to make
 complex, data-rich citations, but there may be instances where you can
 save yourself some typing by keeping it simple.
 
-\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
-helpfully provide as much information as is available, including
-fields that users may well wish not to have printed (ISBN, URL, DOI,
+\mylittlespace Scot Becker 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 helpfully
+provide as much information as is available, including fields that
+users may well wish not to have printed (ISBN, URL, DOI,
 \textsf{pagetotal}, inter alia).  The standard \textsf{biblatex}
 styles contain a series of options, detailed in \textsf{biblatex.pdf}
-§3.1.2.2, for controlling the printing of some of these fields, and
-with this release I have implemented the ones that are relevant to
+§3.1.2.2, for controlling the printing of some of these fields, and I
+have implemented the ones that are relevant to
 \textsf{biblatex-chicago}, along with a couple that Scot requested and
 that may be of more general usefulness.  There is also a general
 option to excise with one command all the fields under consideration
@@ -5260,34 +5671,34 @@ after the author's initials in a bibliography, usually in a
 \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 Philipp Lehman says
-in \textsf{biblatex.pdf}, 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.  In this release, for example, the new
-\mycolor{\textbf{mv*}} entry types 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 Lehman
-advises using \textsf{bibtex8}, rather than standard \textsc{Bib}\TeX,
+\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.
 
 \section{The Specification: Author-Date}
 \label{sec:authdate}
 
-The \textsf{biblatex-chicago} package now contains \emph{two}
-different author-date styles.  The first,
-\textsf{biblatex-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, \textsf{biblatex-chicago-authordate-trad}, implements that
-same specification but with a markedly different style of title
+The \textsf{biblatex-chicago} package contains two different
+author-date styles.  The first, \textsf{biblatex-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,
+\textsf{biblatex-chicago-authordate-trad}, implements that same
+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}
 or \textsf{incollection} entries, \emph{inter alia}.  The
@@ -5330,18 +5741,17 @@ included the reference keys from the latter file below in parentheses.
 The complete list of entry types currently available in
 \textsf{biblatex-chicago-authordate} and \textsf{authordate-trad},
 minus the odd \textsf{biblatex} alias, is as follows:
-\textbf{article}, \textbf{artwork}, \textbf{audio},
-\mycolor{\textbf{book}}, \mycolor{\textbf{bookinbook}},
-\textbf{booklet}, \mycolor{\textbf{collection}}, \textbf{customc},
-\textbf{image}, \textbf{inbook}, \textbf{incollection},
-\textbf{inproceedings}, \textbf{inreference}, \textbf{letter},
-\textbf{manual}, \textbf{misc}, \textbf{music},
-\mycolor{\textbf{mvbook}}, \mycolor{\textbf{mvcollection}},
-\mycolor{\textbf{mvproceedings}}, \mycolor{\textbf{mvreference}},
-\textbf{online} (with its alias \textbf{www}), \textbf{patent},
-\textbf{periodical}, \mycolor{\textbf{proceedings}},
+\mycolor{\textbf{article}}, \textbf{artwork}, \textbf{audio},
+\textbf{book}, \textbf{bookinbook}, \textbf{booklet},
+\textbf{collection}, \textbf{customc}, \textbf{image},
+\textbf{inbook}, \textbf{incollection}, \textbf{inproceedings},
+\textbf{inreference}, \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{periodical}}, \textbf{proceedings},
 \textbf{reference}, \textbf{report} (with its alias
-\textbf{techreport}), \textbf{review}, \textbf{suppbook},
+\textbf{techreport}), \mycolor{\textbf{review}}, \textbf{suppbook},
 \textbf{suppcollection}, \textbf{suppperiodical}, \textbf{thesis}
 (with its aliases \textbf{mastersthesis} and \textbf{phdthesis}),
 \textbf{unpublished}, and \textbf{video}.
@@ -5357,17 +5767,19 @@ very few fields when you use \textsf{biblatex-chicago-authordate}, so
 it seemed to me better to gather information pertaining to fields in
 the next section.
 
-\mybigspace The \mymarginpar{\textbf{article}} \emph{Chicago Manual of
-  Style} (14.170) 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} 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.
+\paragraph*{\protect\colmarginpar{\textbf{article}}}
+\label{sec:ad:article}
+The \emph{Chicago Manual of Style} (14.170) 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} 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.
 
 \mylittlespace For articles in \enquote{journals} you can simply use
 the traditional \textsc{Bib}\TeX\ --- and indeed \textsf{biblatex} ---
@@ -5408,6 +5820,8 @@ but if it's a fuller entry also containing an \textsf{author} then
 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
@@ -5428,8 +5842,8 @@ need the \textsf{review} entry type, with or without this same
 \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.)
+  0.6}, but the current arrangement is somewhat simpler and therefore,
+I hope, better.)
 
 \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
@@ -5445,9 +5859,7 @@ 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.
 
-%\enlargethispage{\baselineskip}
-
-\mylittlespace No less than eight more things need explication under
+\mylittlespace No less than nine 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
@@ -5480,7 +5892,7 @@ missing \textsf{author} field results in the name of the periodical
 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 new default sorting scheme in
+\emph{Manual} (14.175).  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
@@ -5488,10 +5900,10 @@ retain the definite or indefinite article at the beginning of the
 \textsf{journaltitle} in author-less entries with an
 \textsf{entrysubtype}.  If you want to abbreviate the
 \textsf{journaltitle} for use in citations, but give the full name in
-the list of references, then the \textsf{shortauthor} field, somewhat
-surprisingly, is the place for it.  A shortened \textsf{title} should
-go, as usual, in \textsf{shorttitle}.  (See
-section~\ref{sec:authformopts}, below; lakeforester:pushcarts,
+the list of references, then \colmarginpar{New} the
+\mycolor{\textsf{shortjournal}} field is the place for it.  A
+shortened \textsf{title} should go, as usual, in \textsf{shorttitle}.
+(See section~\ref{sec:authformopts}, below; lakeforester:pushcarts,
 nyt:trevorobit, unsigned:ranke.)
 
 \mylittlespace Fourth, Bertold Schweitzer has pointed out, following
@@ -5509,18 +5921,19 @@ with the \textsf{title} otherwise.  The usual string concatenation
 rules still apply --- cf.\ \textsf{editor} and \textsf{editortype} in
 section~\ref{sec:fields:authdate}, below.
 
-\enlargethispage{\baselineskip}
+%\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} 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 \textsf{article} entries, I thought the problem merited a
-preliminary mention here.
+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
+\textsf{article} entries, I thought the problem merited a preliminary
+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
@@ -5549,10 +5962,11 @@ episode in \textsf{title}.  The network's name goes into the
 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 into \textsf{misc} entries with an
-\textsf{entrysubtype} [coolidge:speech, roosevelt:speech].)
+recordings from archives fit best either into \textsf{online} or into
+\textsf{misc} entries with an \textsf{entrysubtype} [coolidge:speech,
+roosevelt:speech].)
 
-\mylittlespace Finally, the 16th edition of the \emph{Manual}
+\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
@@ -5566,6 +5980,15 @@ 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 Finally, \colmarginpar{New} the special
+\textsf{biblatex} field \mycolor{\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
+\mycolor{\textbf{shortjournal}} in section~\ref{sec:fields:authdate}
+for all the details on how this works.
+
 % %\enlargethispage{-\baselineskip}
 
 \mylittlespace If you're still with me, allow me to recommend that you
@@ -5626,13 +6049,13 @@ sources in accordance with the Chicago specifications.  The
 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 \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} should
-help you maintain consistency.
+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
+obvious, at the very least \textsf{biblatex-chicago} should help you
+maintain consistency.
 
 \mylittlespace For users of the author-date styles, the 16th edition
 of the \emph{Manual} (15.53) \enquote{recommends a more comprehensive
@@ -5669,9 +6092,10 @@ such favorite educational formats as the slideshow and the filmstrip
 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 best be presented in a \textbf{misc}
-entry with an \textsf{entrysubtype} (coolidge:speech,
-roosevelt:speech).
+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).
 
 \mylittlespace Once you've accepted the analogy of composer to
 \textsf{author}, constructing an \textsf{audio} entry should be fairly
@@ -5690,19 +6114,18 @@ from a cycle.  If the medium in question needs specifying, the
 \textsf{biblatex-chicago} provides no automated handling, e.g., a
 librettist (verdi:corsaro).
 
-\mybigspace This \colmarginpar{\textbf{book}} is the standard
-\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but with this
-release the package can now provide automatically 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 new \mycolor{\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.
-
-\mybigspace This \colmarginpar{\textbf{bookinbook}} type provides the
+\mybigspace This \mymarginpar{\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
+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
+\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.
+
+\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
@@ -5710,13 +6133,13 @@ articles.  Such an entry can have a \textsf{title} and a
 three of which will be italicized in the reference matter.  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 now enable
-automatically abbreviated references in the reference list, though
-this isn't the default.  Please see \textbf{crossref} in
-section~\ref{sec:fields:authdate} and \mycolor{\texttt{booklongxref}}
-in section~\ref{sec:preset:authdate}, below.  (Cf.\ \emph{Manual}
-14.114, 14.127, 14.130; bernhard:boris, bernhard:ritter, and
-bernhard:themacher for the new abbreviating functionality; also
+marks.  As with the \textsf{book} type, you can enable automatically
+abbreviated references in the reference list, though this isn't the
+default.  Please see \textbf{crossref} in
+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
+bernhard:themacher for the abbreviating functionality; also
 euripides:orestes, plato:republic:gr.)
 
 \mylittlespace \textbf{NB}: The Euripides play receives slightly
@@ -5737,25 +6160,25 @@ which uses the \textsf{howpublished} field instead of a standard
 \textsf{howpublished} field should instead go in \textsf{publisher}.
 (See clark:mesopot.)
 
-\mybigspace This \colmarginpar{\textbf{collection}} is the standard
-\textsf{biblatex} entry type, but with this release the package can
-now provide automatically 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 new
-\mycolor{\texttt{booklongxref}} option.  Please see \textbf{crossref}
-in section~\ref{sec:fields:authdate} and \texttt{booklongxref} in
-section~\ref{sec:authpreset}, below.  See harley:ancient:cart,
-harley:cartography, and harley:hoc for how this might look.
+\mybigspace This \mymarginpar{\textbf{collection}} is the standard
+\textsf{biblatex} entry type, but the package can provide
+automatically 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 \texttt{booklongxref} option.
+Please see \textbf{crossref} in section~\ref{sec:fields:authdate} and
+\texttt{booklongxref} in section~\ref{sec:authpreset}, below.  See
+harley:ancient:cart, harley:cartography, and harley:hoc for how this
+might look.
 
-\mybigspace This \mymarginpar{\textbf{customa}} entry type is now
+\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
 instead.
 
 %%\enlargethispage{-\baselineskip}
 
-\mybigspace This \mymarginpar{\textbf{customb}} entry type is now
+\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}
 type instead.
@@ -5764,17 +6187,18 @@ type instead.
 to include alphabetized cross-references to other, separate entries in
 the bibliography, particularly to other names or pseudonyms, as
 recommended by the \emph{Manual}.  (This is different from the usual
-\textsf{crossref}, \textsf{xref}, and \textsf{userf} 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 new 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.,
+\textsf{crossref}, \textsf{xref}, \textsf{userf}, and
+\mycolor{\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.)
@@ -5810,18 +6234,17 @@ wish to include a comment inside the parentheses of a citation, as
 specified by the \emph{Manual} (15.23).  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 now
-have two choices.  You can enable the new
-\mycolor{\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.,
+  trans.]\{stendhal:parma\}}.  Without a \textsf{postnote}, you have
+two choices.  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\{chicago:manual\}\{chicago:\\comment\}}.  Cf.\
-\mycolor{\texttt{postnotepunct}} in section~\ref{sec:authuseropts},
-below.
+\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
@@ -5833,23 +6256,23 @@ media.  This means that this entry type is now a clone of the
 for users migrating from the old to the new specification.  (See 3.22,
 8.193; bedford:photo.)
 
-\mybigspace These
-\mymarginpar{\mycolor{\textbf{inbook}}\\\textbf{incollection}} two
-standard \textsf{biblatex} types have very nearly identical formatting
-requirements as far as the Chicago specification is concerned, but I
-have retained both of them for compatibility.  \textsf{Biblatex.pdf}
-(§~2.1.1) intends the first for \enquote{a part of a book which forms
-  a self-contained unit with its own title,} while the second would
-hold \enquote{a contribution to a collection 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 now activated by default when you use the
+\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
+concerned, but I have retained both of them for compatibility.
+\textsf{Biblatex.pdf} (§~2.1.1) intends the first for \enquote{a part
+  of a book which forms a self-contained unit with its own title,}
+while the second would hold \enquote{a contribution to a collection
+  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
@@ -5857,9 +6280,9 @@ 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 new option
-\mycolor{\texttt{longcrossref}} in section~\ref{sec:authpreset}.
-Please note that it is also active by default in \textsf{letter} and
+section~\ref{sec:fields:authdate}, below, and the option
+\texttt{longcrossref} in section~\ref{sec:authpreset}.  Please note
+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,
@@ -5877,7 +6300,7 @@ inclusive page numbers, not both.  In-text citations, of course,
 require any \textsf{postnote} field to specify if it is a whole
 chapter to which you are referring.
 
-\enlargethispage{-\baselineskip}
+%\enlargethispage{-\baselineskip}
 
 \mybigspace This \mymarginpar{\textbf{inproceedings}} entry type works
 pretty much as in standard \textsf{biblatex}.  Indeed, the main
@@ -5889,17 +6312,18 @@ 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
 \textsf{incollection} and \textsf{inbook} entries.  See
-\textbf{crossref} in section~\ref{sec:fields:authdate} and the new
-option \mycolor{\texttt{longcrossref}} in
-section~\ref{sec:authpreset}, below, for more details.
+\textbf{crossref} in section~\ref{sec:fields:authdate} and the option
+\texttt{longcrossref} in section~\ref{sec:authpreset}, below, for more
+details.
 
-\mybigspace This \mymarginpar{\textbf{inreference}} 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).
+\paragraph*{\protect\mymarginpar{\textbf{inreference}}}
+\label{sec:ad: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).
 
 \mylittlespace One thing, at least, seems clear.  If your reference
 work can easily or conveniently be presented like a regular book, that
@@ -5984,8 +6408,8 @@ section~\ref{sec:entrytypes}, s.v.\ \enquote{\textsf{letter,}} should
 get you started.  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 now
-simply use the \textsf{origdate} field in both of them, because in the
+published collection, both written in the same year.  You can simply
+use the \textsf{origdate} field in both of them, because in the
 absence of a \textsf{date} (or an \textsf{eventdate}) \textsf{Biber}
 and \textsf{biblatex} will use the \textsf{origyear} as the
 \textsf{labelyear}, putting it at the head of the entry and in the
@@ -6023,19 +6447,21 @@ entry for such a reference, then you would need to define both
 have put in \textsf{organization}.  (See 14.92; chicago:manual,
 dyna:browser, natrecoff:camera.)
 
-\mybigspace As \mymarginpar{\textbf{misc}} its name suggests, the
-\textsf{misc} entry type was designed as a hold-all for citations that
-didn't quite fit into other categories.  In \textsf{biblatex-chicago},
-I have somewhat extended its applicability, while retaining its
-traditional use.  Put simply, with no \textsf{entrysubtype} field, a
-\textsf{misc} entry will retain backward compatibility with the
-standard styles, so the usual \textsf{howpublished}, \textsf{version},
-and \textsf{type} fields are all available for specifying an otherwise
-unclassifiable text, and the \textsf{title} will be italicized.  (The
-\emph{Manual}, you may wish to note, doesn't give specific
-instructions on how such citations should be formatted, so when using
-the Chicago style I would recommend you have recourse to this
-traditional entry type as sparingly as possible.)
+\paragraph*{\protect\mymarginpar{\textbf{misc}}}
+\label{sec:ad:misc}
+As its name suggests, the \textsf{misc} entry type was designed as a
+hold-all for citations that didn't quite fit into other categories.
+In \textsf{biblatex-chicago}, I have somewhat extended its
+applicability, while retaining its traditional use.  Put simply, with
+no \textsf{entrysubtype} field, a \textsf{misc} entry will retain
+backward compatibility with the standard styles, so the usual
+\textsf{howpublished}, \textsf{version}, and \textsf{type} fields are
+all available for specifying an otherwise unclassifiable text, and the
+\textsf{title} will be italicized.  (The \emph{Manual}, you may wish
+to note, doesn't give specific instructions on how such citations
+should be formatted, so when using the Chicago style I would recommend
+you have recourse to this traditional entry type as sparingly as
+possible.)
 
 \mylittlespace If you do provide an \textsf{entrysubtype} field, the
 \textsf{misc} type provides a means for citing unpublished letters,
@@ -6051,17 +6477,16 @@ 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.\ coolidge:speech,
-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 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, dinkel:agassiz, and spock:interview cite individual
-pieces.)
+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
+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,
+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}
@@ -6075,17 +6500,18 @@ 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).
-Like with the \textsf{letter} type, if the only date present is an
-\textsf{origdate}, you no longer 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 now 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.)
+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.)
+
+\enlargethispage{\baselineskip}
 
 \mylittlespace As in \textsf{letter} entries, the titles of
 unpublished letters are of the form \texttt{Author to Recipient},
@@ -6182,15 +6608,15 @@ equivalences.
   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 now 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.
+  \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
@@ -6216,12 +6642,12 @@ equivalences.
   \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 new \mycolor{\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.)
+  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.
@@ -6242,25 +6668,24 @@ section~\ref{sec:authpreset}; auden:reading, beethoven:sonata29,
 bernstein:shostakovich, floyd:atom, holiday:fool, nytrumpet:art,
 rubinstein:chopin.)
 
-\mybigspace All \colmarginpar{\textbf{mvbook}\\\textbf{mvcollection}%
+\mybigspace All \mymarginpar{\textbf{mvbook}\\\textbf{mvcollection}%
   \\\textbf{mvproceedings}\\\textbf{mvreference}} four of these entry
-types are new to \textsf{biblatex-chicago}, and all 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{\textbf{mv}} from their
-names.  Second, 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:fields:authdate}, below.)
+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{\textbf{mv}} from their names.  Second, 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:fields:authdate}, below.)
 
-\enlargethispage{\baselineskip}
+%\enlargethispage{\baselineskip}
 
 \mylittlespace On the same subject, when multi-volume works are
 presented in the reference apparatus, the \emph{Manual} (14.121--27,
@@ -6304,13 +6729,14 @@ ac:comment).  Otherwise, for online documents not \enquote{formally
 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 best as
-\textsf{misc} entries 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.
+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 Constructing an \textsf{online} .bib file entry is much
 the same as in \textsf{biblatex}.  The \textsf{title} field would
@@ -6353,7 +6779,7 @@ down-casing code from previous editions, you may need manually to
 revise the \textsf{title} field to provide the lowercase letters.  See
 petroff:impurity.
 
-\mybigspace This \mymarginpar{\textbf{periodical}} is the standard
+\mybigspace This \colmarginpar{\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
 function in \textsf{biblatex-chicago}, and in the main uses the same
@@ -6367,15 +6793,28 @@ initial lowercase letter to activate the automatic capitalization
 routines, though this isn't strictly necessary in the author-date
 styles.  (See \emph{Manual} 14.187; good:wholeissue.)
 
-\mybigspace This \colmarginpar{\textbf{proceedings}} is the standard
-\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but with this
-release the package can now provide automatically 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 new \mycolor{\texttt{booklongxref}} option.  Please see
-\textbf{crossref} in section~\ref{sec:fields:authdate} and
-\texttt{booklongxref} in section~\ref{sec:authpreset}, below.
+\mylittlespace It is worth \colmarginpar{New} noting that the special
+\textsf{biblatex} field \mycolor{\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 \mycolor{\textbf{shortjournal}} in
+section~\ref{sec:fields:authdate} for all the details on how this
+works.
+
+\mybigspace This \mymarginpar{\textbf{proceedings}} is the standard
+\textsf{biblatex} and \textsc{Bib}\TeX\ entry type, but the package
+can provide automatically 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
+\texttt{booklongxref} option.  Please see \textbf{crossref} in
+section~\ref{sec:fields:authdate} and \texttt{booklongxref} in
+section~\ref{sec:authpreset}, below.
 
 \mybigspace This \mymarginpar{\textbf{reference}} entry type is
 aliased to \textsf{collection} by the standard \textsf{biblatex}
@@ -6406,10 +6845,10 @@ then the \textsf{type} field automatically defaults to
 report type in \textsf{note} and the \textsf{institution} in
 \textsf{publisher}.  (See herwign:office.)
 
-\mybigspace The \mymarginpar{\textbf{review}} \textsf{review} entry
+\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 now become
+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
@@ -6523,6 +6962,15 @@ 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:fields:authdate}, below.
 
+\mylittlespace Finally, \colmarginpar{New} the special
+\textsf{biblatex} field \mycolor{\textsf{shortjournal}} allows you to
+present shortened \textsf{journaltitles} in \textsf{review} entries,
+as well as in \textsf{article} and \textsf{periodical} entries, and it
+facilitates the creation of lists of journal abbreviations in the
+manner of a \textsf{shorthand} list.  Please see the documentation of
+\mycolor{\textbf{shortjournal}} in section~\ref{sec:fields:authdate}
+for all the details on how this works.
+
 %%\enlargethispage{\baselineskip}
 
 \mybigspace This \mymarginpar{\textbf{suppbook}} is the entry type to
@@ -6643,13 +7091,13 @@ by \textsf{biblatex}.  Here are the main correspondences:
   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
-  \mycolor{\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}.)  Typically, any given
-  \textsf{video} entry will only need an \textsf{eventdate} \emph{or}
-  an \textsf{origdate}, and it is this date that will appear in
-  citations and at the head of the entry in the reference list.  It's
+  \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}.)  Typically, any given \textsf{video}
+  entry will only need an \textsf{eventdate} \emph{or} an
+  \textsf{origdate}, and it is this date that will appear in citations
+  and at the head of the entry in the reference list.  It's
   conceivable that you may need all three dates, in which case you can
   also use the standard \textsf{pubstate} field with \texttt{reprint}
   in it to control the printing of the \textsf{origdate} at the end of
@@ -6715,7 +7163,7 @@ undefined, and \textsf{biblatex-chicago} will do the rest. Cf.\
 \textsf{foreword} and \textsf{introduction}. (See \emph{Manual} 14.91,
 14.116; polakow:afterw.)
 
-% %\enlargethispage{\baselineskip}
+\enlargethispage{\baselineskip}
 
 \mybigspace At \mymarginpar{\textbf{annotation}} the request of Emil
 Salim, \textsf{biblatex-chicago} has, as of version 0.9, added a
@@ -6740,80 +7188,52 @@ serves as an alias for this.)
 do, even though the \emph{Manual} doesn't actually mention it.  It may
 be useful for some purposes.  Cf.\ \textsf{commentator}.
 
-\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, 15.36;
-assocpress:gun, chicago:manual).  If there is no \textsf{author}, then
-\textsf{biblatex-chicago} will look, in sequence, for an
-\textsf{editor}, \textsf{translator}, or \textsf{compiler} (actually
-\textsf{namec}, currently) 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, schellinger:novel, sechzer:women, silver:ga\-wain,
-soltes:georgia).  \textsf{Biber} now takes care of alphabetizing
-entries no matter which name appears at their head, and the package
-also automatically provides a name for citations.
-
-\mylittlespace If you wish to emphasize the activity of an editor or a
-translator, you can use the \textsf{biblatex} and
-\textsf{biblatex-chicago} options \texttt{useauthor=false},
-\texttt{useeditor=false}, \texttt{usetranslator=false}, and
-\texttt{usecompiler=false} in the \textsf{options} field to choose
-which one appears at the head of an entry.  A peculiarity of this
-system of toggles is that in order to ensure that the \textsf{title}
-of a book appears at the head of an entry, you would need to use
-\emph{all four} of the toggles, even though the hypothetical entry
-contains no \textsf{translator}.  Internally,
-\textsf{biblatex-chicago} is either searching for an
-author-substitute, or it is skipping over elements of the ordered,
-unidirectional chain \textsf{author -> editor -> translator ->
-  compiler -> title}.  If you don't include
-\texttt{usetranslator=false} in the \textsf{options} field, then the
-package begins its search at \textsf{translator} and continues on to
-\textsf{namec}, even though you have \texttt{usecompiler=false} in
-\textsf{options}.  The result will be that the compilers' names will
-appear at the head of the entry.  If you want to skip over parts of
-the chain, you must turn off \emph{all} of the parts up to the one you
-wish printed.  Another peculiarity of the system is that setting the
-Chicago-specific \texttt{usecompiler} option to \texttt{false} doesn't
-remove \textsf{namec} from the sorting list, whereas the other
-standard \textsf{biblatex} toggles \emph{do} remove their names from
-the sorting list, so in some corner cases you may need the
-\textsf{sortkey} field.  See \cmd{DeclareSortingScheme} in
-section~\ref{sec:authformopts}, below.
-
-\mylittlespace This system of toggles, then, can turn off
-\textsf{biblatex-chicago}'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 wasn't
-possible before.  For full details of how this works, see the
-\textsf{editortype} documentation below.  (Of course, in
-\textsf{collection} and \textsf{proceedings} entry types, an
-\textsf{author} isn't expected, so there the \textsf{editor} is
-required, as in standard \textsf{biblatex}.  Also, in \textsf{article}
-and \textsf{review} entries with \textsf{entrysubtype}
-\texttt{magazine}, the absence of an \textsf{author} triggers the use
-of the \textsf{journaltitle} in its stead.  Without an
-\textsf{entrysubtype}, the \textsf{title} will be used.  See the next
-paragraph, and those entry types, for further details.)
-
-\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}
-is nothing if not flexible, however, so with unsigned articles or
-encyclopedia entries the \textsf{journaltitle} or \textsf{title} may
-take the place of the \textsf{author} (gourmet:052006,
-lakeforester:pushcarts, nyt:trevorobit, unsigned:ranke,
-wikipedia:bibtex).  Even in such entries, however, it may be
-advantageous to provide either a standard \textsf{shorttitle} or, for
-abbreviating a \textsf{journaltitle}, a (formatted)
-\textsf{shortauthor} field, thereby keeping the in-text citations to a
-reasonable length, though not at the expense of making it hard to find
-the relevant entries in the reference list.
+\paragraph*{\protect\colmarginpar{\textbf{author}}}
+\label{sec:ad: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: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,
+schellinger:novel, sechzer:wo\-men, silver:ga\-wain, soltes:georgia).
+\textsf{Biber} and \textsf{biblatex} take care of alphabetizing
+entries no matter which name appears at their head.  In citations,
+where the \textsf{labelname} is used, the order searched is somewhat
+augmented: \textsf{shortauthor}, \textsf{author},
+\textsf{shorteditor}, \textsf{namea}, \textsf{editor}, \textsf{nameb},
+\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
+\textsf{biblatex} options \texttt{useauthor=false},
+\mycolor{\texttt{usenamea=false}}, \texttt{useeditor=false},
+\mycolor{\texttt{usenameb=false}}, \texttt{usetranslator=false}, and
+\mycolor{\texttt{usenamec=false}} in the \textsf{options} field to
+choose which name appears at the head of an entry and in the citation.
+You \colmarginpar{New} only need to turn off any fields that are
+present in the entry, but please remember to use the new option
+\mycolor{\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\-ingScheme} in section~\ref{sec:authformopts}, and the
+\textsf{editortype} documentation, below.
+
+\mylittlespace Of course, in \textsf{collection} and
+\textsf{proceedings} entry types, an \textsf{author} isn't expected,
+so there the chain of substitutions begins with \textsf{namea} and
+\textsf{editor}.  Also, in \textsf{article} and \textsf{review}
+entries with \textsf{entrysubtype} \texttt{magazine}, the absence of
+an \textsf{author} triggers the use of the \textsf{journaltitle} in
+its stead.  Without an \textsf{entrysubtype}, the \textsf{title} will
+be used.  See the discussion a few paragraphs down, and those entry
+types, for further details.
 
 % %\enlargethispage{\baselineskip}
 
@@ -6859,27 +7279,43 @@ name in the \textsf{author} field, then the pseudonym goes in
 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 now strengthened its policies
+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
 pseudonyms back to the author's name, using the \textsf{customc} entry
 type, which see (ashe:creasey, morton:creasey, york:creasey).
 
-\mylittlespace One final piece of advice.  An institutional author's
-name, or a journal's name being used in place of an author, can be
-rather too long for in-text citations.  In unsigned:ranke I placed an
-abbreviated form of the \textsf{journaltitle} into
-\textsf{shortauthor}, adapting for a periodical the practice
-recommended for books in 15.32.  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 now also appear 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 also still utilize
-the list of shorthands to clarify the abbreviation, if you wish.)
+\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}
+is nothing if not flexible, however, so with unsigned articles or
+encyclopedia entries the \textsf{journaltitle} or \textsf{title} may
+take the place of the \textsf{author} (gourmet:052006,
+lakeforester:pushcarts, nyt:trevorobit, unsigned:ranke,
+wikipedia:bibtex).  Even in such entries, however, it may be
+advantageous to provide either a standard \textsf{shorttitle} or, for
+abbreviating a \textsf{journaltitle}, a
+\mycolor{\textsf{shortjournal}} field, thereby keeping the in-text
+citations to a reasonable length, though not at the expense of making
+it hard to find the relevant entries in the reference list.  An
+institutional author's name can also be rather too long for in-text
+citations.  In unsigned:ranke I placed an abbreviated form of the
+\textsf{journaltitle} into \mycolor{\textsf{shortjournal}}, adapting
+for a periodical the practice recommended for books in 15.32.  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, 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
+\mycolor{\cmd{printbiblist\{shortjournal\}}} command.  Please cf.\ the
+\mycolor{\textbf{shortjournal}} documentation, below, and the
+\mycolor{\texttt{journalabbrev}} option in
+section~\ref{sec:authpreset}.)
 
 \mybigspace In \mymarginpar{\textbf{authortype}}
 \textsf{biblatex-chicago}, this field serves a function very much in
@@ -6961,12 +7397,16 @@ in \textsf{authordate-trad}.
 
 %%\enlargethispage{\baselineskip}
 
-\mybigspace An \mymarginpar{\textbf{booktitleaddon}} annex to the
+\mybigspace An \colmarginpar{\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
 ordinarily only be capitalized at the beginning of a sentence, then
 simply ensure that that word is in lowercase, and
-\textsf{biblatex-chicago} will automatically do the right thing.
+\textsf{biblatex-chicago} will automatically do the right thing.  The
+package and entry options \colmarginpar{New}
+\mycolor{\texttt{ptitleaddon}} and \mycolor{\texttt{ctitleaddon}}
+(section~\ref{sec:authpreset}) allow you to customize the punctuation
+that appears before the \textsf{booktitleaddon} field.
 
 \mybigspace This \mymarginpar{\textbf{chapter}} field holds the
 chapter number, mainly useful only in an \textsf{inbook} or an
@@ -6978,9 +7418,9 @@ of a book (ashbrook:brain).
 do, even though the \emph{Manual} doesn't actually mention it.  It may
 be useful for some purposes.  Cf.\ \textsf{annotator}.
 
-\mybigspace \textsf{Biblatex} \colmarginpar{\textbf{crossref}} uses
-the standard \textsc{Bib}\TeX\ cross-referencing mechanism, and has
-also introduced a modified one of its own (\textsf{xref}).  The latter
+\mybigspace \textsf{Biblatex} \mymarginpar{\textbf{crossref}} uses the
+standard \textsc{Bib}\TeX\ cross-referencing mechanism, and has also
+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}
@@ -6988,15 +7428,15 @@ 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 now inherit from \textsf{book}
-and \textsf{mvbook} just as they do from \textsf{mvcollection}
-entries; \textsf{letter} entries now inherit from \textsf{book},
+here: \textsf{incollection} entries can inherit from \textsf{book} and
+\textsf{mvbook} just as they do from \textsf{mvcollection} entries;
+\textsf{letter} entries inherit from \textsf{book},
 \textsf{collection}, \textsf{mvbook}, and \textsf{mvcollection}
 entries the same way an \textsf{inbook} or an \textsf{incollection}
 entry would; the \textsf{namea}, \textsf{nameb}, \textsf{sortname},
 \textsf{sorttitle}, and \textsf{sortyear} fields, all highly
 single-entry specific, are no longer inheritable; and \textsf{date}
-and \textsf{origdate} fields are not inheritable from any of the new
+and \textsf{origdate} fields are not inheritable from any of the
 \textbf{mv*} entry types.
 
 \mylittlespace Aside from these inheritance questions, the other main
@@ -7014,29 +7454,27 @@ child entries.  The \textsf{biblatex-chicago-authordate} package has
 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).  With this release, I
-\colmarginpar{New!} have considerably extended this functionality.
-
-\mylittlespace First, I have added five new entry types ---
-\mycolor{\textbf{book}}, \mycolor{\textbf{bookinbook}},
-\mycolor{\textbf{collection}}, \mycolor{\textbf{inbook}}, and
-\mycolor{\textbf{proceedings}} --- to the list of those which use
-shortened cross references, and I have added two new options ---
-\mycolor{\texttt{longcrossref}} and \mycolor{\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 the reference list.)
+entries (on the last named, see just below).  More recently, I have
+considerably extended this 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 provided 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 the reference list.)
 
 \mylittlespace The inclusion of \textbf{book}, \textbf{bookinbook},
 \textbf{collection}, and \textbf{proceedings} entries fulfills a
@@ -7065,17 +7503,17 @@ outlined, even though the \emph{Manual} doesn't explicitly require it.
 As with \textsf{book}, \textsf{bookinbook}, \textsf{collection},
 \textsf{inbook}, \textsf{incollection}, \textsf{inproceedings}, and
 \textsf{proceedings} entries, the use of a \textsf{crossref} or
-\textsf{xref} field will activate this mechanism, assuming the new
+\textsf{xref} field will activate this mechanism, assuming the 
 preamble and entry options are set to enable it.  (See
 white:ross:memo, white:russ, and white:total, for examples of the
 \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.)
 
-\mylittlespace These \colmarginpar{\texttt{longcrossref}} new options
-function asymmetrically.  The first, \mycolor{\texttt{longcrossref}},
-generally controls the settings for the entry types more-or-less
-authorized by the \emph{Manual}: \textsf{inbook},
+\mylittlespace These \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}
@@ -7094,10 +7532,10 @@ authorized by the \emph{Manual}: \textsf{inbook},
   \texttt{false} and \textsf{true}, respectively.
 \end{description}
 
-The \colmarginpar{\texttt{booklongxref}} second option,
-\mycolor{\texttt{booklongxref}}, controls the settings for
-\textsf{book}, \textsf{bookinbook}, \textsf{collection}, and
-\textsf{proceedings} entries:
+The \mymarginpar{\texttt{booklongxref}} second option,
+\texttt{booklongxref}, controls the settings for \textsf{book},
+\textsf{bookinbook}, \textsf{collection}, and \textsf{proceedings}
+entries:
 
 \begin{description}
 \item[\qquad true:] This is the default.  If you use \textsf{crossref}
@@ -7114,30 +7552,38 @@ Please note that you can set both of these options either in the
 preamble or in the \textsf{options} field of individual entries,
 allowing you to change the settings on an entry-by-entry basis.
 
-\mylittlespace Please \colmarginpar{New!} further note that in
-previous releases of \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 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 now 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.
-
-\mybigspace Predictably, \colmarginpar{\textbf{date}} 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 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.
+\mylittlespace Please further note that in previous releases of
+\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 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
+inaccuracies, please report them.
+
+\mylittlespace Finally, there is also \colmarginpar{New} an
+\mycolor{\texttt{xrefurl}} option available to control the printing of
+\textsf{url}, \textsf{doi}, and \textsf{eprint} fields in abbreviated
+references where such information might otherwise never appear.  See
+\mycolor{\texttt{xrefurl}} in section~\ref{sec:authuseropts}.
+
+\paragraph*{\protect\mymarginpar{\textbf{date}}}
+\label{sec:ad: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
+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.
 
 \mylittlespace To start, in each entry, \textsf{Biber} attempts to
 find something which it can designate a \textsf{labeldate}, which
@@ -7161,10 +7607,7 @@ types \enquote{\texttt{n.d.}}\ will appear if no date is provided,
 though you can turn this off throughout the document in all entry
 types with the option \texttt{nodates=false} when loading
 \textsf{biblatex-chicago} in your preamble.  (See
-section~\ref{sec:authpreset}, below.  If you wish to provide the
-\enquote{\texttt{n.d.}}\ yourself in the \textsf{year} field, please
-instead put \cmd{bibstring\{nodate\}} there, as otherwise the
-punctuation in citations will come out [subtly] wrong.)
+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
@@ -7199,19 +7642,19 @@ the specification.  If users modified \cmd{DeclareLabeldate}, and
 their references entered these tricky corners, the results could be
 surprising.
 
-\mylittlespace With \colmarginpar{New!} this release, therefore, I
-have included a new means of coping with multiple dates in database
-entries, while retaining the old mechanisms for those for whom they
-work well.  These old 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 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.
+\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
+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.
 
 \mylittlespace For other entry types, the 16th edition of the
 \emph{Manual} (15.38) presents a fairly simple scheme for when a
@@ -7224,11 +7667,11 @@ default \textsf{biblatex-chicago-authordate} will use 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
+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, \colmarginpar{\texttt{cmsdate}\\\emph{in entry}}
+\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}
 toggle in the \textsf{options} field of the entry itself.  This has 3
@@ -7249,7 +7692,7 @@ state (\texttt{full}) which I shall discuss below:
   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
-  \texttt{new} and \texttt{old} now work like \texttt{both}.
+  \texttt{new} and \texttt{old} work like \texttt{both}.
 \end{enumerate}
 
 In the first and third cases, if you put the string \texttt{reprint}
@@ -7295,10 +7738,10 @@ the \textsf{date} --- (Author [1898] 1974a) and (Author [1898] 1974b)
 how to cope with these situations, but
 \textsf{biblatex-chicago-authordate} provides help.  You can't
 manually put the alphabetical suffix on an \textsf{origdate} yourself
-because that field only accepts numerical data.  Instead, we can now
+because that field only accepts numerical data.  Instead, we can
 choose between two solutions.  The old way
-\colmarginpar{\texttt{cmsdate}\\\emph{in entry}
-  \\+ \texttt{switchdates}} is an unusual expedient, which amounts to
+\mymarginpar{\texttt{cmsdate}\\\emph{in entry} \\+
+  \texttt{switchdates}} is an unusual expedient, which amounts to
 switching the two date fields, placing the earlier date in
 \textsf{date} and the later one in \textsf{origdate}.  The style tests
 for this condition using a simple arithmetical comparison between the
@@ -7316,7 +7759,7 @@ follows:
 \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 now synonyms for this.
+  options \texttt{old} and \texttt{new} are synonyms for this.
 \end{enumerate}
 
 If, for some reason, the automatic switching of the dates cannot be
@@ -7328,14 +7771,14 @@ in print (preventing the comparison between a year and the word
 \texttt{switchdates} in the \textsf{options} field to achieve the
 required effects.
 
-\mylittlespace The \mycolor{new}
-\colmarginpar{\texttt{cmsdate}\\\emph{in preamble}} 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 \enquote{correctly} as I can.  The switches
-for this option are the same as for the entry-only option, that is:
+\mylittlespace The more \mymarginpar{\texttt{cmsdate}\\\emph{in
+    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
+\enquote{correctly} as I can.  The switches for this option are the
+same as for the entry-only option, that is:
 
 \begin{enumerate}
 \item \texttt{cmsdate=off} is the default: (Author 1952).
@@ -7350,25 +7793,24 @@ for this option are the same as for the entry-only option, that is:
   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
-  \texttt{new} and \texttt{old} now work like \texttt{both}.
+  \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
 synonyms for the latter, \texttt{new} or \texttt{old}), then
-\textsf{biblatex-chicago-authordate} will now change the default
+\textsf{biblatex-chicago-authordate} will change the default
 \cmd{DeclareLa\-bel\-date} definition so that the \textsf{labelyear}
-search order will be \mycolor{\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} and the
-correct sorting, without having to switch dates around
-counter-intuitively in your .bib file.  A few clarifications may yet
-be in order.
+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} and the correct
+sorting, without having to switch dates around counter-intuitively in
+your .bib file.  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
@@ -7452,12 +7894,11 @@ 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, with \colmarginpar{New!} this release, you can now 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.
+finally, 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 I recommend that you have a look through
 \textsf{dates-test.bib} to see how all these complications will affect
@@ -7502,8 +7943,8 @@ citations (emerson:nature).
 \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
-complications that need explaining.  Lehman points out in his
-documentation that the \textsf{editor} field will be associated with a
+complications that need explaining.  \textsf{Biblatex.pdf} points out
+that the \textsf{editor} field will be associated with a
 \textsf{title}, a \textsf{booktitle}, or a \textsf{maintitle},
 depending on the sort of entry.  More specifically,
 \textsf{biblatex-chicago} associates the \textsf{editor} with the most
@@ -7540,40 +7981,41 @@ languages, but they are otherwise unnecessary.
 Cf. section~\ref{sec:international}, and also \textsf{namea},
 \textsf{nameb}, \textsf{namec}, and \textsf{translator}.)
 
-\mybigspace The \mymarginpar{\textbf{editora\\editorb\\editorc}} newer
-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
+\mybigspace \textsf{Biblatex}
+\mymarginpar{\textbf{editora\\editorb\\editorc}} provides 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},
 \textsf{editorbtype}, and \textsf{editorctype}, which see.  (Cf.\
 bernstein:shostakovich, 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
 put at the head of an entry, starting with an \textsf{author}, and
-proceeding in order through \textsf{editor}, \textsf{translator}, and
-\textsf{namec} (the compiler).  If all four are missing, then the
-\textsf{title} will be placed at the head.  (In \textsf{article} and
-\textsf{review} entries with a \texttt{magazine}
-\textsf{entrysubtype}, a missing author immediately prompts the use of
-\textsf{journaltitle} at the head of an entry.  See above under
-\textsf{article} for details.)  The \textsf{editortype} field provides
-even greater flexibility, allowing you to choose from a variety of
-editorial roles while only using the \textsf{editor} field.  You can
-do this even though an author is named (eliot:pound shows this
-mechanism in action for a standard editor, rather than for some other
-role).  Two things are necessary for this to happen.  First, in the
-\textsf{options} field you need to set \texttt{useauthor=false} (if
-there is an \textsf{author}), then you need to put the name you wish
-to see at the head of your entry into the \textsf{editor} or the
-\textsf{namea} field.  If the \enquote{editor} is in fact, e.g., a
-compiler, then you need to put \texttt{compiler} into the
-\textsf{editortype} field, and \textsf{biblatex} will print the
-correct string after the name in the list of references.
+proceeding in order through \textsf{namea}, \textsf{editor},
+\textsf{nameb}, \textsf{translator}, and \textsf{namec} (the
+compiler).  If all six are missing, then the \textsf{title} will be
+placed at the head.  (In \textsf{article} and \textsf{review} entries
+with a \texttt{magazine} \textsf{entrysubtype}, a missing
+\textsf{author} immediately prompts the use of \textsf{journaltitle}
+at the head of an entry.  See above under \textsf{article} for
+details.)  The \textsf{editortype} field provides even greater
+flexibility, allowing you to choose from a variety of editorial roles
+while only using the \textsf{editor} field.  You can do this even
+though an author is named (eliot:pound shows this mechanism in action
+for a standard editor, rather than for some other role).  Two things
+are necessary for this to happen.  First, in the \textsf{options}
+field you need to set \texttt{useauthor=false} (if there is an
+\textsf{author}), then you need to put the name you wish to see at the
+head of your entry into the \textsf{editor} or the \textsf{namea}
+field.  If the \enquote{\textsf{editor}} is in fact, e.g., a compiler,
+then you need to put \texttt{compiler} into the \textsf{editortype}
+field, and \textsf{biblatex} will print the correct string after the
+name in the list of references.
 
 %\enlargethispage{\baselineskip}
 
@@ -7583,30 +8025,34 @@ 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 \textsf{editortype} mechanism 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 it will go ahead and look
-for an \textsf{editor}.  \textsf{Biblatex}'s sorting algorithms, and
+used at the head of the entry, if it isn't , or if you've set the
+option \mycolor{\texttt{usenamea=false}}, it will go ahead and look
+for an \textsf{editor}.  The \textsf{editortype} field applies only to
+the \textsf{editor}, but you can use \mycolor{\textsf{nameatype}} to
+modify \textsf{namea}.  \textsf{Biblatex}'s sorting algorithms, and
 also its \textsf{labelname} mechanism, should both work properly no
 matter sort of name you provide, thanks to \textsf{Biber} and the
 (default) Chicago-specific definitions of \cmd{DeclareLabelname} and
 \cmd{DeclareSortingScheme}.  (Cf.\ section~\ref{sec:authformopts},
-below).  If, however, the \textsf{namea} field provides the name, and
-that name isn't automatically shortened properly by \textsf{biblatex},
-then your .bib entry will need to have a \textsf{shorteditor} defined
-to help with in-text citations, not a \textsf{shortauthor}, possibly
-ruled out because \texttt{useauthor=false}.
+below).  Please be aware that if you want a shortened form to appear
+in citations then there's only the \textsf{shorteditor}, which you
+should ensure presents whichever of the two editors' names
+(\textsf{namea} or \textsf{editor}) appears at the head of the
+reference-list entry.
 
 \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
 \textsf{editortype} field, then concatenation is turned off, even if
 the name of the \textsf{editor} matches, for example, that of the
-\textsf{translator}.  In the absence of an \textsf{editortype}, the
-usual mechanisms remain in place, that is, if 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 (15.7) recommends
-not using these identifying strings in citations, and
+\textsf{translator}.  In the absence of an \textsf{editortype} (or
+\mycolor{\textsf{nameatype}}), the usual mechanisms remain in place,
+that is, if 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 (15.7) recommends not using these
+identifying strings in citations, and
 \textsf{biblatex-chicago-authordate} follows that recommendation.  If
 you nevertheless need to provide such a string, you'll have to do it
 manually in the \textsf{shorteditor} field, or perhaps, in a different
@@ -7614,20 +8060,20 @@ sort of entry, in a \textsf{shortauthor} field.
 
 \mylittlespace It may also be worth noting that because of certain
 requirements in the specification -- absence of an \textsf{author},
-for example -- the \texttt{useauthor} mechanism 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}.
+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}.
 
 \mybigspace These
 \mymarginpar{\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
 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, and they have found a use particularly in \textsf{music}
+and \textsf{video} entries.  Cf.\ bernstein:shostakovich,
+handel:messiah.
 
 \mybigspace Standard \mymarginpar{\textbf{eid}} \textsf{biblatex}
 field, providing a string or number some journals use uniquely to
@@ -7635,19 +8081,20 @@ identify a particular article.  Only applicable to the
 \textsf{article} entry type.  Not typically required by the
 \emph{Manual}.
 
-\mybigspace Standard \mymarginpar{\textbf{entrysubtype}} 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 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 between scholarly
-\enquote{journals,} on the one hand, and \enquote{magazines} and
-\enquote{newspapers} on the other.  Usage is fairly simple: you need
-to put the exact string \texttt{magazine} into the
-\textsf{entrysubtype} field if you are citing one of the latter two
-types of source, whereas if your source is a \enquote{journal,} then
-you need do nothing.
+\paragraph*{\protect\mymarginpar{\textbf{entrysubtype}}}
+\label{sec:ad: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
+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
+between scholarly \enquote{journals,} on the one hand, and
+\enquote{magazines} and \enquote{newspapers} on the other.  Usage is
+fairly simple: you need to put the exact string \texttt{magazine} into
+the \textsf{entrysubtype} field if you are citing one of the latter
+two types of source, whereas if your source is a \enquote{journal,}
+then you need do nothing.
 
 \mylittlespace The second use involves references to works from
 classical antiquity and, according to the \emph{Manual}, from the
@@ -7703,16 +8150,16 @@ above, and that of \textsf{userd} below.)
 \mymarginpar{\textbf{eprint}\\\textbf{eprintclass}\\\textbf{eprinttype}}
 Teramoto suggested adding \textsf{biblatex's} excellent
 \textsf{eprint} handling to \textsf{biblatex-chicago}, and he sent me
-a patch implementing it.  With minor alterations, I have applied it to
-this release, so these three fields now work more or less as they do
-in standard \textsf{biblatex}.  They may prove helpful in providing
-more abbreviated references to online content than conventional URLs,
+a patch implementing it.  I have applied it, with minor alterations, 
+so these three fields work more or less as they do in standard
+\textsf{biblatex}.  They may prove helpful in providing more
+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 will now play a significant role in \textsf{music},
+\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
@@ -7721,9 +8168,9 @@ 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).
+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 the default configuration of \cmd{DeclareLabeldate},
 dates for citations and for the head of reference list entries are
@@ -7764,7 +8211,7 @@ from the \textsf{author}.  The \emph{Manual} has nothing to say on the
 subject, but \textsf{biblatex-chicago} prints it (them), in
 parentheses, just after the author(s).
 
-%%\enlargethispage{\baselineskip}
+\enlargethispage{\baselineskip}
 
 \mybigspace Standard \mymarginpar{\textbf{howpublished}}
 \textsf{biblatex} field, mainly applicable in the \textsf{booklet}
@@ -7834,7 +8281,11 @@ where a piece in an \textsf{article} or \textsf{review}
 author.  See above (section~\ref{sec:fields:authdate}) under
 \textbf{article} for details.  The lakeforester:pushcarts and
 nyt:trevorobit entries in \textsf{dates-test.bib} will give you some
-idea of how this works.
+idea of how this works.  Please note there is a
+\mycolor{\textsf{shortjournal}} field which you can use to abbreviate
+the \textsf{journaltitle} in citations and/or in the reference list,
+and you can also use it to print a list of journal abbreviations.
+Cf.\ the \mycolor{\textsf{shortjournal}} documentation below.
 
 \mybigspace This \mymarginpar{\textbf{keywords}} field is
 \textsf{biblatex}'s extremely powerful and flexible technique for
@@ -7850,12 +8301,11 @@ 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
-(furet:passing:eng, furet:passing:fr, 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).
+(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).
 
 \mybigspace A \mymarginpar{\textbf{language}} standard
 \textsf{biblatex} field, designed to allow you to specify the
@@ -7946,38 +8396,48 @@ cross references produced using the \textsf{crossref} field, the
 euripides:\-orestes, harley:cartography, lach:asia,
 pelikan:chris\-tian, and plato:re\-public:gr.)
 
-\mybigspace An \mymarginpar{\textbf{maintitleaddon}} annex to the
+\mybigspace An \colmarginpar{\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
 that would ordinarily only be capitalized at the beginning of a
 sentence, then simply ensure that that word is in lowercase, and
-\textsf{biblatex-chicago} will automatically do the right thing.
+\textsf{biblatex-chicago} will automatically do the right thing.  The
+package and entry options \colmarginpar{New}
+\mycolor{\texttt{ptitleaddon}} and \mycolor{\texttt{ctitleaddon}}
+(section~\ref{sec:authpreset}) allow you to customize the punctuation
+that appears before the \textsf{maintitleaddon} field
+(schubert:muellerin).
 
 \mybigspace Standard \mymarginpar{\textbf{month}} \textsf{biblatex}
 field, containing the month of publication.  This should be an
 integer, i.e., \texttt{month=\{3\}} not \texttt{month=\{March\}}.  See
 \textsf{date} for more information.
 
-\mybigspace This \mymarginpar{\textbf{namea}} is one of the fields
+\mybigspace This \colmarginpar{\textbf{namea}} is one of the fields
 \textsf{biblatex} provides for style writers to use, but which it
 leaves undefined itself.  In \textsf{biblatex-chicago} it contains the
 name(s) of the editor(s) of a \textsf{title}, if the entry has a
-\textsf{booktitle} or \textsf{maintitle}, or both, in which situation
-the \textsf{editor} would be associated with one of these latter
-fields (donne:var).  (In \textsf{article} and \textsf{review} entries,
+\textsf{booktitle} and/or a \textsf{maintitle}, in which situation the
+\textsf{editor} would be associated with one of these latter fields
+(donne:var).  (In \textsf{article} and \textsf{review} entries,
 \textsf{namea} applies to the \textsf{title} instead of the
 \textsf{issuetitle}, should the latter be present.)  You should
 present names in this field exactly as you would those in an
 \textsf{author} or \textsf{editor} field, and the package will
-concatenate this field with \textsf{nameb} if they are identical.  See
-under \textbf{editor} and \textbf{editortype} above for the full
-details.  Please note that, as the field is highly single-entry
-specific, \textsf{namea} isn't inherited from a \textsf{crossref}'ed
-parent entry.  Cf.\ also \textsf{nameb}, \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 section~\ref{sec:formatting:authdate}.
+concatenate this field with \textsf{nameb} if they are identical.
+When choosing a name for a citation or to head a reference-list entry,
+\textsf{biblatex-chicago} gives precedence to \textsf{namea} over
+\textsf{editor}.  See under \textbf{editor} and \textbf{editortype}
+above for the full details.  Please note that, as the field is highly
+single-entry specific, \textsf{namea} isn't inherited from a
+\textsf{crossref}'ed parent entry.  Please note, also, that you can
+use the \mycolor{\textsf{nameatype}} field to redefine this 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{parteditandcomp}, \cmd{parttransandcomp}, and
+\cmd{partedittransand\-comp}, for which see
+section~\ref{sec:formatting:authdate}.
 
 \mybigspace This \mymarginpar{\textbf{nameaddon}} field is provided
 by \textsf{biblatex}, though not used by the standard styles.  In
@@ -7996,11 +8456,10 @@ details.
 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.
+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 the \textsf{customc} entry type, finally, which is
 used to create alphabetized cross-references to other entries in the
@@ -8009,6 +8468,13 @@ default string linking the two parts of the cross-reference.  The code
 automatically tests for a known bibstring, which it will italicize.
 Otherwise, it prints the string as is.
 
+\mybigspace You \colmarginpar{\textbf{nameatype}} can use this field
+to change the role of a \textsf{namea} just as you can use
+\textsf{editortype} to change the role of an \textsf{editor}.  As with
+the \textsf{editortype}, using this field prevents string
+concatenation with identical \textsf{nameb} or \textsf{namec} fields.
+Please see \textbf{editortype}, above, for the details.
+
 \mybigspace Like \mymarginpar{\textbf{nameb}} \textsf{namea}, above,
 this is a field left undefined by the standard \textsf{biblatex}
 styles.  In \textsf{biblatex-chicago}, it contains the name(s) of the
@@ -8024,13 +8490,15 @@ concatenate this field with \textsf{namea} if they are identical.  See
 under the \textbf{translator} field below for the full details.
 Please note that, as the field is highly single-entry specific,
 \textsf{nameb} isn't inherited from a \textsf{crossref}'ed parent
-entry.  Cf.\ also \textsf{namea}, \textsf{namec},
+entry.  Please note, also, that in \textsf{biblatex-chicago's}
+name-finding algorithms \textsf{nameb} takes precedence over
+\textsf{translator}.  Cf.\ also \textsf{namea}, \textsf{namec},
 \textsf{origlanguage}, \textsf{translator}, \textsf{userf} and the
 macros \cmd{partedit}, \cmd{parttrans}, \cmd{parteditandtrans},
 \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 \colmarginpar{\textbf{namec}} \emph{Manual} (15.35)
 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
@@ -8040,7 +8508,7 @@ reference, so I have added that possibility to the many that
 \textsf{biblatex} already provides, such as the \textsf{editor},
 \textsf{translator}, \textsf{commentator}, \textsf{annotator}, and
 \textsf{redactor}, along with writers of an \textsf{introduction},
-\textsf{foreword}, or \textsf{afterword}.  Since \textsf{biblatex.bst}
+\textsf{foreword}, or \textsf{afterword}.  Since \textsf{biblatex}
 doesn't offer a \textsf{compiler} field, I have adopted for this
 purpose the otherwise unused field \textsf{namec}.  It is important to
 understand that, despite the analogous name, this field does not
@@ -8055,7 +8523,8 @@ please note that I've arranged the concatenation algorithms to include
 so in this particular circumstance you can, if needed, make
 \textsf{namec} analogous to these two latter, \textsf{title}-only
 fields.  (See above under \textbf{editortype} for details of how you
-can use that field to identify a compiler.)
+can use that field, or the \mycolor{\textsf{nameatype}} field, to
+identify a compiler.)
 
 \mylittlespace It might conceivably be necessary at some point to
 identify the compiler(s) of a \textsf{title} separate from the
@@ -8068,19 +8537,16 @@ to fall back on the \cmd{partcomp} macro or the related
 be able to remedy this.)  It may be as well to mention here too that
 of the three names that can be substituted for the missing
 \textsf{author} at the head of an entry, \textsf{biblatex-chicago}
-will choose an \textsf{editor} if present, then a \textsf{translator}
-if present, falling back to \textsf{namec} only in the absence of the
-other two, and assuming that the fields aren't identical, and
-therefore to be concatenated.  In a change from the previous behavior,
-these algorithms also now test for \textsf{namea} or \textsf{nameb},
-which will be used instead of \textsf{editor} and \textsf{translator},
-respectively, giving the package the greatest likelihood of finding a
-name to place at the head of an entry.  \textsf{Biblatex}'s sorting
-algorithms, and also its \textsf{labelname} mechanism, should both
-work properly no matter sort of name you provide, thanks to
-\textsf{Biber} and the (default) Chicago-specific definitions of
-\cmd{DeclareLabelname} and \cmd{DeclareSortingScheme}.  (Cf.\
-section~\ref{sec:authformopts}, below).
+will choose a \textsf{namea} if present, then an \textsf{editor}, a
+\textsf{nameb}, or a \textsf{translator}, with \textsf{namec} coming
+last, assuming that the fields aren't identical, and therefore to be
+concatenated.  \textsf{Biblatex}'s sorting algorithms, and also its
+\textsf{labelname} mechanism, should both work properly no matter what
+sort of name you provide, but do please remember that if you want the
+package to skip over any names you can employ the
+\texttt{use<name>=false} options.  Indeed, \textsf{biblatex's}
+\mycolor{\texttt{usenamec}} has replaced the old Chicago-specific
+\texttt{usecompiler}, which is deprecated.
 
 \mybigspace As \mymarginpar{\textbf{note}} in standard
 \textsf{biblatex}, this field allows you to provide bibliographic data
@@ -8105,7 +8571,7 @@ 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
 \textsf{review} entry, this will be a plain cardinal number, but in
-such entries \textsf{biblatex-chicago} now does the right thing if you
+such entries \textsf{biblatex-chicago} does the right thing if you
 have a list or range of numbers (unsigned:ranke).  In any
 \textsf{book}-like entry it may well contain considerably more
 information, including even a reference to \enquote{2nd ser.,} for
@@ -8144,7 +8610,7 @@ organization sponsoring a conference in a \textsf{proceedings} or
 \textsf{inproceedings} entry, and I have retained this as a
 possibility, though the \emph{Manual} is silent on the matter.
 
-\mybigspace This \colmarginpar{\textbf{origdate}} is a standard
+\mybigspace This \mymarginpar{\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
@@ -8186,8 +8652,8 @@ 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 new
-\colmarginpar{\texttt{cmsdate}\\\emph{in preamble}} \texttt{cmsdate}
+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
 multiple dates.  In short, setting \texttt{cmsdate} to \texttt{both}
@@ -8238,85 +8704,17 @@ 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.
-
-%\enlargethispage{\baselineskip}
-
-\mybigspace In \mymarginpar{\textbf{origlanguage}} keeping with the
-\emph{Manual}'s specifications, I have fairly thoroughly redefined
-\textsf{biblatex}'s facilities for treating translations.  The
-\textsf{origtitle} field isn't used, while the \textsf{language} and
-\textsf{origdate} fields have been press-ganged for other duties.  The
-\textsf{origlanguage} field, for its part, retains a dual role in
-presenting translations in a list of references.  The details of the
-\emph{Manual}'s suggested treatment when both a translation and an
-original are cited may be found below under \textbf{userf}.  Here,
-however, I simply note that the introductory string used to connect
-the translation's citation with the original's is \enquote{Originally
-  published as,} which I suggest may well be inaccurate in a great
-many cases, as for instance when citing a work from classical
-antiquity, which will most certainly not \enquote{originally} have
-been published in the Loeb Classical Library.  Although not, strictly
-speaking, authorized by the \emph{Manual}, I have provided another way
-to introduce the original text, using the \textsf{origlanguage} field,
-which must be provided \emph{in the entry for the translation, not the
-  original text} (aristotle:metaphy:trans).  If you put one of the
-standard \textsf{biblatex} bibstrings there (enumerated below), then
-the entry will work properly across multiple languages.  Otherwise,
-just put the name of the language there, localized as necessary, and
-\textsf{biblatex-chicago} will eschew \enquote{Originally published
-  as} in favor of, e.g., \enquote{Greek edition:} or \enquote{French
-  edition:}.  This has no effect in citations, where only the work
-cited --- original or translation --- will be printed, but it may help
-to make the \emph{Manual}'s suggestions for the list of references
-more palatable.
+\textsf{location} field.  (The \textsf{origyear} field usually works,
+too.)
 
-\mylittlespace That was the first usage, in keeping at least with the
-spirit of the \emph{Manual}.  I have also, perhaps less in keeping
-with that specification, retained some of \textsf{biblatex}'s
-functionality for this field.  If an entry doesn't have a
-\textsf{userf} field, and therefore won't be combining a text and its
-translation in the list of references, you can also use
-\textsf{origlanguage} as Lehman intended it, so that instead of
-saying, e.g., \enquote{translated by X,} the entry will read
-\enquote{translated from the German by X.}  The \emph{Manual} doesn't
-mention this, but it may conceivably help avoid certain ambiguities in
-some citations.  As in \textsf{biblatex}, if you wish to use this
-functionality, you have to provide \emph{not} the name of the
-language, but rather a bibstring, which may, at the time of writing,
-be one of \texttt{american}, \texttt{brazilian}, \texttt{danish},
-\texttt{dutch}, \texttt{english}, \texttt{french}, \texttt{german},
-\texttt{greek}, \texttt{italian}, \texttt{latin}, \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 now 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 now 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}, \textsf{origpublisher} and
-\textsf{pubstate}; schweitzer:bach.)
+\mybigspace See
+\vspace{-14.2pt}
+\colmarginpar{\textbf{origlanguage}\\
+\textbf{origlocation}\\\textbf{origpublisher}}
+section~\ref{sec:authrelated}, below.
+\vspace{18pt}
 
-\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 now 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}, and
-\textsf{pubstate}; schweitzer:bach.)
-
-\mybigspace This \colmarginpar{\textbf{pages}} is the standard
+\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
@@ -8332,8 +8730,8 @@ 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 has recently brought to my attention a
-discussion that took place a couple of years ago on
+\mylittlespace David Gohlke brought to my attention a discussion that
+took place a couple of years ago on
 \href{http://tex.stackexchange.com/questions/44492/biblatex-chicago-style-page-ranges}{Stackexchange}
 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
@@ -8343,10 +8741,9 @@ 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,
 and in their \textsf{postnote} fields, I have made the activation of
-this code a package option, so setting
-\mycolor{\texttt{compresspages=true}} when loading
-\textsf{biblatex-chicago} should automatically give you the
-Chicago-recommended page ranges.
+this code a package option, so setting \texttt{compresspages=true}
+when loading \textsf{biblatex-chicago} should automatically give you
+the Chicago-recommended page ranges.
 
 \mybigspace This, \mymarginpar{\textbf{pagination}} a standard
 \textsf{biblatex} field, allows you automatically to prefix the
@@ -8357,7 +8754,7 @@ appropriate identifying string to information you provide in the
 all the details on this functionality, as aside from the difference
 just mentioned the two fields are equivalent.
 
-\mybigspace Standard \colmarginpar{\textbf{part}} \textsf{biblatex}
+\mybigspace Standard \mymarginpar{\textbf{part}} \textsf{biblatex}
 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}
@@ -8371,13 +8768,13 @@ necessary, rather than supplying the usual bibstring, so this provides
 a mechanism for altering the string to your liking.  The field will be
 printed in the same place in any entry as would a \textsf{volume}
 number, and although it will most usually be associated with such a
-number, it can also, as of this release, function independently,
-allowing you to identify parts of works that don't fit into the
-standard scheme.  If you need to identify \enquote{parts} or
-\enquote{books} that are part of a published \textsf{series}, for
-example, then you'll need to use a different field, (which in the case
-of a series would be \textsf{number} [palmatary:pottery]).  Cf.\
-\textsf{volume}; iso:electrodoc.
+number, it can also function independently, allowing you to identify
+parts of works that don't fit into the standard scheme.  If you need
+to identify \enquote{parts} or \enquote{books} that are part of a
+published \textsf{series}, for example, then you'll need to use a
+different field, (which in the case of a series would be
+\textsf{number} [palmatary:pottery]).  Cf.\ \textsf{volume};
+iso:electrodoc.
 
 \mybigspace Standard \mymarginpar{\textbf{publisher}}
 \textsf{biblatex} field.  Remember that \enquote{\texttt{and}} is a
@@ -8407,71 +8804,16 @@ 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.
 
-\mybigspace A \mymarginpar{\textbf{pubstate}} standard
-\textsf{biblatex} field, introduced in version 0.9.  Because the
-author-date specification has fairly complicated rules about
-presenting reprinted editions, I have adopted this field as a means of
-simplifying the problem for users.  Instead of hand-formatting in the
-\textsf{location} field, you can now 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
-parenthesized 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.)  If the field contains something
-other than the word \texttt{reprint}, then it will be treated as in
-the standard styles, and printed after the publication information.
-
-\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, the original release date will be printed near
-the end, preceded by the appropriate string.
-
-%\enlargethispage{\baselineskip}
+\mybigspace See \colmarginpar{\textbf{pubstate}}
+section~\ref{sec:authrelated}, below.
 
 \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
 purposes.  Cf.\ \textsf{annotator} and \textsf{commentator}.
 
-\mybigspace \textbf{NB:} \mymarginpar{\textbf{reprinttitle}}
-\textbf{Please note that this feature is in an alpha state, and that
-  I'm contemplating using a different field in the future for this
-  functionality.  I include it here in the hope that it might receive
-  some testing in the meantime.}  At the request of Will Small, I have
-included a means of providing the 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 need be provided
-only if they 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{Orig.\ pub.\ in.}  Please see the documentation on
-\textsf{userf} below for all the details on how to create .bib entries
-for presenting your data.
-
-%%\enlargethispage{\baselineskip}
+\mybigspace See \colmarginpar{\textbf{reprinttitle}}
+section~\ref{sec:authrelated}, below.
 
 \mybigspace A \mymarginpar{\textbf{series}} standard \textsf{biblatex}
 field, usually just a number in an \textsf{article},
@@ -8499,7 +8841,7 @@ garaud:gatine, sewall:letter.)  Cf.\ \textsf{number} for more
 information on the \emph{Manual}'s preferences regarding the
 formatting of numerals.
 
-\mybigspace This \mymarginpar{\textbf{shortauthor}} is a standard
+\mybigspace This \colmarginpar{\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
 purposes of the author-date specification, the field provides the name
@@ -8509,20 +8851,21 @@ the author's last name from the \textsf{author} field and uses it in
 such a reference, and if there is no \textsf{author} it will search
 \textsf{namea}, \textsf{editor}, \textsf{nameb}, \textsf{translator},
 and \textsf{namec}, in that order.  The current versions of
-\textsf{biblatex} and \textsf{Biber} will now automatically
-alphabetize by any of these names if they appear at the head of an
-entry.  If, in an author-less \textsf{article} entry
-(\textsf{entrysubtype} \texttt{magazine}), you allow
-\textsf{biblatex-chicago} to use the title of the periodical as the
-author --- the default behavior --- then your \textsf{shortauthor}
-field can optionally contain an abbreviated form of the periodical
-name, formatted appropriately, which usually means something like
-\enquote{\cmd{mkbibemph\{Abbrev.\ Period.\ Title\}}} (gourmet:052006,
-lakeforester:pushcarts, nyt:trevorobit, unsigned:ranke).  Indeed, with
-long, institutional authors, a shortened version in
-\textsf{shortauthor} may save space in the running text
-(evanston:library).  See just below under \textbf{shorthand} for
-another method of saving space.
+\textsf{biblatex} and \textsf{Biber} will automatically alphabetize by
+any of these names if they appear at the head of an entry.  If, in an
+author-less \textsf{article} entry (\textsf{entrysubtype}
+\texttt{magazine}), you allow \textsf{biblatex-chicago} to use the
+\textsf{journaltitle} as the author --- the default behavior --- and
+you have been accustomed to using the \textsf{shortauthor} field to
+abbreviate it, it may be simpler now to use the
+\mycolor{\textsf{shortjournal}} field instead, which does all of the
+formatting for you, and additionally adds the possibility of printing
+a list of journal abbreviations.  See just below for the details.
+(Cf.\ gourmet:052006, lakeforester:pushcarts, nyt:trevorobit,
+unsigned:ranke).  With long, institutional authors, a shortened
+version in \textsf{shortauthor} may save space in the running text
+(evanston:library), but see under \textbf{shorthand} for another
+method of saving space.
 
 \mylittlespace As mentioned under \textsf{editortype}, the
 \emph{Manual} (15.21) recommends against providing the identifying
@@ -8538,16 +8881,23 @@ in this case for, e.g., a \textsf{collection} entry that typically
 lacks an author.  The \textsf{shortauthor} field works just as well in
 most situations, but if you have set \texttt{useauthor=false} (and not
 \texttt{useeditor=false}) in an entry's \textsf{options} field, then
-only \textsf{shorteditor} will be recognized.  Cf.\
-\textsf{editortype}, above.
+only \textsf{shorteditor} will be recognized.  It may be worth
+pointing out that, because \textsf{biblatex-chicago} also provides a
+\textsf{namea} field for the editor of a \textsf{title} as opposed to
+a \textsf{main-} or \textsf{booktitle}, and because in standard use
+the \textsf{namea}, if present, will be chosen to head a reference
+list entry before the \textsf{editor}, you should present the
+shortened \textsf{namea} here instead of a shortened \textsf{editor}
+in such cases.Cf.\ \textsf{editortype}, above.
 
 % %\enlargethispage{\baselineskip}
+\paragraph*{\protect\mymarginpar{\textbf{shorthand}}}
+\label{sec:ad:shorthand}
 
-\mybigspace This \mymarginpar{\textbf{shorthand}} is
-\textsf{biblatex}'s mechanism for using abbreviations in citations.
-For \textsf{biblatex-chicago-authordate} I have modified it somewhat
-to conform to the needs of the specification, though there is a
-package option to revert the behavior to something closer to the
+This is \textsf{biblatex}'s mechanism for using abbreviations in
+citations.  For \textsf{biblatex-chicago-authordate} I have modified
+it somewhat to conform to the needs of the specification, though there
+is a package option to revert the behavior to something closer to the
 \textsf{biblatex} standard --- see below and under \texttt{cmslos} in
 section~\ref{sec:authpreset}.  The main problem when presenting
 readers with an abbreviation is to ensure that they know how to expand
@@ -8561,30 +8911,33 @@ in themselves already highly-abbreviated keys to the fuller
 information to be found in the list of references.  There are cases,
 however, particularly when institutions or \textsf{journaltitles}
 appear as authors, when you may feel the need to provide a shortened
-version for citations.  I have already discussed one option available
-to you just above (cf.\ \textbf{shortauthor}), but for this to work
-the abbreviation must either be instantly recognizable to your
-readership or at least easily parseable by them.
-
-\mylittlespace The \emph{Manual's} recommendation (15.36), and this
-has changed for the 16th edition, involves using an abbreviation for
-long institutional names, an abbreviation which will appear not only
-in citations but also at the head of the entry in the list of
+version for citations.  I have already discussed two options available
+to you just above (cf.\ \textbf{shortauthor} and
+\mycolor{\textbf{shortjournal}}).  For the former to work the
+abbreviation must either be instantly recognizable to your readership
+or at least easily parseable by them, while with the latter you can
+either rely on the conventions of your field or, alternately, provide
+a list of journal abbreviations using
+\mycolor{\cmd{printbiblist\{shortjournal\}}}.
+
+\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, which will be expanded within the same entry and placed
-(inside parentheses) between the abbreviation and the date.  This new
-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.)
+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.)
 
 \mylittlespace I should clarify here that this automatic placement of
 the \textsf{shorthand} at the head of the entry will \emph{not} occur
@@ -8597,21 +8950,21 @@ itself.  You can place \texttt{skiplos} in the \textsf{options} field
 to exclude a particular entry from the list of shorthands if you do
 decide to print that list, giving maximum flexibility.
 
-\mylittlespace Indeed, I have provided two new options to add to this
-flexibility.  First, I have included two new \texttt{bibenvironments}
-for 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 latter case to clear up some spurious punctuation and white space
-that I see on my system when using endnotes.  (You'll probably 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.)  Second, I have provided a new 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
+\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:
+\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
+latter case to clear up some spurious punctuation and white space that
+I see on my system when using endnotes.  (You'll probably 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.)  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{cmslos=false}, as otherwise the shorthand will be printed
 twice.  (See 15.36, 13.65, 14.54--55, and also \textsf{biblatex.pdf}
 for more information.)
@@ -8619,14 +8972,66 @@ for more information.)
 %%\enlargethispage{-\baselineskip}
 
 \mylittlespace As I mentioned above under \textbf{crossref}, I believe
-it is now safe to use shorthands in parent entries, as this, in the
+it is safe to use shorthands in parent entries, as this, in the
 standard configuration, gives you the shorthand itself in the child
 entry's abbreviated cross-reference, which may well save space in the
 list of references.
 
-\mybigspace A \mymarginpar{\textbf{shorttitle}} standard
+\mybigspace A \colmarginpar{\textbf{shortjournal}} special
+\textsf{biblatex} field, used to provide both an abbreviated form of a
+\textsf{journaltitle} in citations and/or the reference list and to
+facilitate the creation of a list of journal abbreviations, should
+this be needed, rather in the manner of a \textsf{shorthand} list.  As
+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
+\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
+individual publications, but were you to require such a thing, you'd
+have to move the abbreviation from the \textsf{journaltitle} to the
+\mycolor{\textsf{shortjournal}} field, placing the full title in the
+former.  In \textsf{periodical} entries the \textsf{title} field
+presents what would be the \textsf{journaltitle} in the
+\textsf{articles} or \textsf{reviews}, so in such entries you can
+provide the standard \textsf{shorttitle} field to accompany the
+\textsf{title}, and \textsf{biblatex-chicago} will automatically copy
+the \textsf{shorttitle} into a \mycolor{\textsf{shortjournal}}.
+
+\mylittlespace Having done this, you then need to choose where to
+print the \mycolor{\textsf{shortjournal}}, which is controlled by the
+\mycolor{\texttt{journalabbrev}} option either in the preamble or in
+the \textsf{options} field of individual .bib entries.  By default,
+and taking account of the space-saving features of the author-date
+styles, this option is set to \texttt{notes}, so your
+\textsf{shortjournal} fields will be printed only in those citations
+where they appear in place of an \textsf{author}.  There are three
+other settings: \texttt{true} prints the shortened fields both in
+citations and in the 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 \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{sjnotes}} and
+\mycolor{\texttt{sjendnotes}}, 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 (bold italic), you can
+roll your own using \cmd{DeclareFieldFormat\{shortjournalwidth\}} ---
+you can see its default definition at the top of
+\textsf{chicago-authordate.bbx}.
+
+\mybigspace A \colmarginpar{\textbf{shorttitle}} standard
 \textsf{biblatex} field, primarily used to provide an abbreviated
-title for citation styles that need one.  In
+title for citation styles that need one.  (It is also the way to hook
+\textsf{periodical} entries into the \mycolor{\textsf{shortjournal}}
+mechanism, on which see the previous entry.)  In
 \textsf{biblatex-chicago-authordate} such a field will be necessary
 only very rarely (unlike in the notes \&\ bibliography style), and is
 most likely to turn up in \textsf{inreference} or \textsf{reference}
@@ -8642,28 +9047,28 @@ space in your running text this is the field where you can provide it.
 \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 now omit
-the definite or indefinite article, which should help (14.85;
+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{DeclareSortingScheme} now 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.  Lehman also provides \textbf{sortname} and
+\cmd{DeclareSortingScheme} 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 A \mymarginpar{\textbf{sortyear}} standard
-\textsf{biblatex} field, provided by Lehman 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.
+\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.
@@ -8671,23 +9076,22 @@ present several reprinted books by the same author.  See
 %\enlargethispage{\baselineskip}
 
 \mybigspace This \mymarginpar{\textbf{title}} release of
-\textsf{biblatex-chicago} now includes the \textsf{authordate-trad}
-style, 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 related fields, which retain the forms they have
-traditionally had in 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.
+\textsf{biblatex-chicago} includes the \textsf{authordate-trad} style,
+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
+related fields, which retain the forms they have traditionally had in
+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.
 
 \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
@@ -8793,14 +9197,14 @@ quotation, retains those marks in all title types (kimluu:diethyl).
 \textsf{biblatex-chicago-authordate} will automatically capitalize the
 first word of the \textsf{title} after sentence-ending punctuation,
 assuming that such a \textsf{title} begins with a lowercase letter in
-your .bib database.  See \textbf{\textbackslash autocap} below for
-more details.
+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
-new \textsf{authordate-trad} style, your \textsf{title} and related
-fields will need extra care, familiar to users of the 15th-edition
+\textsf{authordate-trad} style, your \textsf{title} and related fields
+will need extra care, familiar to users of the 15th-edition
 author-date style.  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-trad} does just that, capitalizing
@@ -8940,7 +9344,7 @@ determine capitalization.  It works by redefining the command
 latter anywhere in your document please be aware that it will also be
 turned off there.  See section~\ref{sec:authuseropts}, below.
 
-\mybigspace Standard \mymarginpar{\textbf{titleaddon}}
+\mybigspace Standard \colmarginpar{\textbf{titleaddon}}
 \textsf{biblatex} intends this field for use with additions to titles
 that may need to be formatted differently from the titles themselves,
 and \textsf{biblatex-chicago} uses it in just this way, with the
@@ -8954,20 +9358,28 @@ to provide manually yourself.  The single exception to this rule is
 when your data begins with a word that would ordinarily only be
 capitalized at the beginning of a sentence, in which case you need
 then simply ensure that that word is in lowercase, and
-\textsf{biblatex-chicago} will automatically do the right thing.  See\
-\textbf{\textbackslash autocap}, below.  (Cf.\ brown:bremer,
-osborne:poison, reaves:rosen, and white:ross:memo for examples where
-the field starts with a lowercase letter; morgenson:market provides an
-example where the \textsf{titleaddon} field, holding the name of a
-regular column in a newspaper, is capitalized, a situation that is
-handled as you would expect.)
-
-\mybigspace As \mymarginpar{\textbf{translator}} far as possible, I
+\textsf{biblatex-chicago} will automatically do the right thing.
+See\,\textbf{\textbackslash autocap} in
+section~\ref{sec:formatting:authdate} below.  The \colmarginpar{New}
+package and entry options \mycolor{\texttt{ptitleaddon}} and
+\mycolor{\texttt{ctitleaddon}} (section~\ref{sec:authpreset}) can help
+you customize the punctuation that appears before the
+\textsf{titleaddon} field.  (Cf.\ brown:bremer, osborne:poison,
+reaves:rosen, and white:ross:memo for examples where the field starts
+with a lowercase letter; morgenson:market provides an example where
+the \textsf{titleaddon} field, holding the name of a regular column in
+a newspaper, is capitalized, a situation that is handled as you would
+expect; coolidge:speech shows an entry option for controlling the
+punctuation.)
+
+\enlargethispage{\baselineskip}
+
+\mybigspace As \colmarginpar{\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
-complications that need explaining.  Lehman points out in his
-documentation that the \textsf{translator} field will be associated
-with a \textsf{title}, a \textsf{booktitle}, or a \textsf{maintitle},
+complications that need explaining.  \textsf{Biblatex.pdf} points out
+that the \textsf{translator} field will be associated with a
+\textsf{title}, a \textsf{booktitle}, or a \textsf{maintitle},
 depending on the sort of entry.  More specifically,
 \textsf{biblatex-chicago} associates the \textsf{translator} with the
 most comprehensive of those titles, that is, \textsf{maintitle} if
@@ -8980,7 +9392,9 @@ one part of a collection or for one volume of a multi-volume work.
 For these cases I have provided the \textsf{nameb} field.  You should
 format names for this field as you would for \textsf{author} or
 \textsf{editor}, and these names will always be associated with the
-\textsf{title} (euripides:orestes).
+\textsf{title} (euripides:orestes).  In the algorithm for finding a
+name for the head of a reference list entry or for a citation,
+\textsf{nameb} takes precedence over \textsf{translator}.
 
 \mylittlespace I have also provided a \textsf{namea} field, which
 holds the editor of a given \textsf{title} (euripides:orestes).  If
@@ -9002,13 +9416,13 @@ languages, but they are otherwise unnecessary.  [See
 section~\ref{sec:international}].)
 
 \mylittlespace Finally, as I detailed above under \textbf{author}, in
-the absence of an \textsf{author} or an \textsf{editor}, the
-\textsf{translator} will be used at the head of an entry
-(silver:gawain), and the reference list entry alphabetized by the
-translator's name, behavior that can be controlled with the
-\texttt{{usetranslator}} switch in the \textsf{options} field.  Cf.\
-\textsf{author}, \textsf{editor}, \textsf{namea}, \textsf{nameb}, and
-\textsf{namec}.
+the absence of an \textsf{author}, a \textsf{namea}, an
+\textsf{editor}, and a \textsf{nameb}, the \textsf{translator} will be
+used at the head of an entry (silver:gawain), and the reference list
+entry alphabetized by the translator's name, behavior that can be
+controlled with the \texttt{use<name>} switches in the
+\textsf{options} field.  Cf.\ \textsf{author}, \textsf{editor},
+\textsf{namea}, \textsf{nameb}, and \textsf{namec}.
 
 %%\enlargethispage{\baselineskip}
 
@@ -9052,7 +9466,11 @@ provide one for all entry types.  The 16th edition of the
 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.
+properly, in the text and in the reference apparatus.  It
+\colmarginpar{New} 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
@@ -9066,9 +9484,9 @@ 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 now use the
-\textsf{urldate} to find a year for citations and the list of
-references (grove:sibelius, wikiped:bibtex).
+\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).
 
 % %\enlargethispage{\baselineskip}
 
@@ -9082,7 +9500,7 @@ field will be placed, unformatted and between commas, after the
 identifying the broadcast network when you cite a radio or television
 program (14:221; bundy:macneil).
 
-\mybigspace I \mymarginpar{\textbf{userc}} have now implemented this
+\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
@@ -9102,7 +9520,7 @@ 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,
 creasey:morton:hide, creasey:york:death, lecarre:quest.)
 
-\mybigspace The \colmarginpar{\textbf{userd}} \textsf{userd} field,
+\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
@@ -9113,10 +9531,10 @@ been the default in \textsf{biblatex} and in
 way, what you include in \textsf{userd} will be printed \emph{before}
 the \textsf{urldate}, so phrases like \enquote{\texttt{last modified}}
 or \enquote{\texttt{last revised}} are what the field will typically
-contain (14.7--8; wikiped:bibtex).  In \colmarginpar{New!} the absence
-of a \textsf{urldate}, you can now, 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}.
+contain (14.7--8; 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 schema changes for \textsf{music}
@@ -9152,40 +9570,8 @@ can translate the title and use that translation in your
 \textbf{language}, above.  (See 14.108--110, 14.194; kern,
 pirumova:russian, weresz.)
 
-%%\enlargethispage{-\baselineskip}
-
-\mybigspace This \mymarginpar{\textbf{userf}} is the last 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)
-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
-possibility also for a list of references, though in-text citations
-will still only refer to individual works.  In order to follow this
-specification, I have provided a third cross-referencing system (the
-others being \textsf{crossref} and \textsf{xref}), and have chosen the
-name \textsf{userf} because it might act as a mnemonic for its
-function.
-
-\mylittlespace In order to use this system, you should start by
-entering both the original and its translation into your .bib file,
-just as you normally would.  The mechanism works for any entry type,
-and the two entries need not be of the same type.  In the entry for
-the \emph{translation}, you put the cite key of the original into the
-\textsf{userf} field.  In the \emph{original's} entry, you need to
-include some means of preventing it appearing separately in the list
-of references, either a toggle in the \textsf{keywords} field or
-perhaps \texttt{skipbib} in the \textsf{options} field.  In this
-standard case, the data for the translation will be printed first,
-followed by the string \texttt{orig. pub. as}, followed by the
-original, author omitted (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 language in
-\textsf{origlanguage}, and instead of \texttt{originally published
-  as}, you'll get \texttt{French edition:} or \texttt{Latin edition:},
-etc.\ (aristotle:metaphy:gr, aristotle:metaphy:trans).
+\mybigspace See \colmarginpar{\textbf{userf}}
+section~\ref{sec:authrelated}, below.
 
 \mybigspace Standard \mymarginpar{\textbf{venue}} \textsf{biblatex}
 offers this field for use in \textsf{proceedings} and
@@ -9198,7 +9584,7 @@ instead.  Anything in a \textsf{venue} field will be ignored.
 field, currently only available in \textsf{misc} and \textsf{patent}
 entries in \textsf{biblatex-chicago}.
 
-\mybigspace Standard \colmarginpar{\textbf{volume}} \textsf{biblatex}
+\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
@@ -9214,16 +9600,16 @@ In such a case, the \emph{Manual} (14.121) 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 new command
-\mycolor{\cmd{postvolpunct}} \colmarginpar{\cmd{postvolpunct}}.  By
-default it prints \cmd{addcolon}, but you can use
+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:formatting:authdate};
 conway:evolution shows how sometimes this field may hold series
 information, as well.
 
-\mybigspace Standard \colmarginpar{\textbf{volumes}} \textsf{biblatex}
+\mybigspace Standard \mymarginpar{\textbf{volumes}} \textsf{biblatex}
 field.  It holds the total number of volumes of a multi-volume work,
 and in such references you should provide the volume and page numbers
 in the \textsf{postnote} field of the relevant \cmd{cite} command,
@@ -9241,9 +9627,9 @@ 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, except in some cases
 when a \textsf{maintitle} is present.  In this latter case, if the
-\textsf{volume} appears before the \textsf{maintitle}, the new option
-\mycolor{\texttt{hidevolumes}}, \colmarginpar{\texttt{hidevolumes}}
-set to \texttt{true} by default, controls whether to print 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
@@ -9253,6 +9639,8 @@ option's documentation in section~\ref{sec:authpreset}, below.
 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}
 field, especially important for the author-date specification.  Please
 see all the details under \textbf{date} above.  Unlike the
@@ -9263,6 +9651,328 @@ then you can include that guess in square brackets instead of
 \cmd{bibstring\{nodate\}}.  Cf.\ bedford:photo, clark:mesopot,
 leo:madonna, ross:thesis.
 
+\subsubsection{\mycolor{Fields for Related Entries}}
+\label{sec:authrelated}
+
+As \textsf{biblatex.pdf} puts it (§~3.4), \enquote{Almost all
+  bibliography styles require authors to specify certain types of
+  relationship between entries such as \enquote{Reprint of},
+  \enquote{Reprinted in,} etc. It is impossible to provide data fields
+  to cover all of these relationships and so \textsf{biblatex}
+  provides a general mechanism for this using the entry fields
+  \textsf{related}, \textsf{relatedtype} and \textsf{relatedstring}.}
+Before this mechanism was available \textsf{biblatex-chicago}
+attempted to provide a similar but much more limited set of
+inter-entry relationships using the \textsf{biblatex} fields
+\textsf{origlanguage}, \textsf{origlocation}, \textsf{origpublisher},
+\textsf{pubstate}, \textsf{reprinttitle}, and \textsf{userf}.  All of
+these still work just as they always have or, I hope, somewhat better
+than they always have after many recent bug fixes, but the more
+general and more powerful \textsf{biblatex} \mycolor{\texttt{related}}
+mechanism is also available.  It can provide much of what the older
+system provided and a great deal that it couldn't.  What follows is a
+field-by-field discussion of the options now available.
+
+\mybigspace In \mymarginpar{\textbf{origlanguage}} keeping with the
+\emph{Manual}'s specifications, I have fairly thoroughly redefined
+\textsf{biblatex}'s facilities for treating translations.  The
+\textsf{origtitle} field isn't used, while the \textsf{language} and
+\textsf{origdate} fields have been press-ganged for other duties.  The
+\textsf{origlanguage} field, for its part, retains a dual role in
+presenting translations in a list of references.  The details of the
+\emph{Manual}'s suggested treatment when both a translation and an
+original are cited may be found below under \textbf{userf}.  Here,
+however, I simply note that the introductory string used to connect
+the translation's citation with the original's is \enquote{Originally
+  published as,} which I suggest may well be inaccurate in a great
+many cases, as for instance when citing a work from classical
+antiquity, which will most certainly not \enquote{originally} have
+been published in the Loeb Classical Library.  Although not, strictly
+speaking, authorized by the \emph{Manual}, I have provided another way
+to introduce the original text, using the \textsf{origlanguage} field,
+which must be provided \emph{in the entry for the translation, not the
+  original text} (aristotle:metaphy:trans).  If you put one of the
+standard \textsf{biblatex} bibstrings there (enumerated below), then
+the entry will work properly across multiple languages.  Otherwise,
+just put the name of the language there, localized as necessary, and
+\textsf{biblatex-chicago} will eschew \enquote{Originally published
+  as} in favor of, e.g., \enquote{Greek edition:} or \enquote{French
+  edition:}.  This has no effect in citations, where only the work
+cited --- original or translation --- will be printed, but it may help
+to make the \emph{Manual}'s suggestions for the list of references
+more palatable.  \textbf{NB:} You can use the
+\mycolor{\textsf{relatedtype} \texttt{origpubas}} with a customized
+\mycolor{\textsf{relatedstring}} field to achieve the same ends.
+
+\mylittlespace That was the first usage, in keeping at least with the
+spirit of the \emph{Manual}.  I have also, perhaps less in keeping
+with that specification, retained some of \textsf{biblatex}'s
+functionality for this field.  If an entry doesn't have a
+\textsf{userf} field, and therefore won't be combining a text and its
+translation in the list of references, you can also use
+\textsf{origlanguage} as \textsf{biblatex} intended it, so that
+instead of saying, e.g., \enquote{translated by X,} the entry will
+read \enquote{translated from the German by X.}  The \emph{Manual}
+doesn't mention this, but it may conceivably help avoid certain
+ambiguities in some citations.  As in \textsf{biblatex}, if you wish
+to use this functionality, you have to provide \emph{not} the name of
+the language, but rather a bibstring, which may, at the time of
+writing, be one of \texttt{american}, \texttt{brazilian},
+\texttt{danish}, \texttt{dutch}, \texttt{english}, \texttt{french},
+\texttt{german}, \texttt{greek}, \texttt{italian}, \texttt{latin},
+\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}],
+\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 \mycolor{\texttt{related}}
+field, though the \mycolor{\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, 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}
+[section~\ref{sec:fields:authdate}], \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 \mycolor{\texttt{related}} field, though the
+\mycolor{\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.)  If the field contains something other than the word
+\texttt{reprint}, then it will be treated as in the standard styles,
+and printed after the publication information.
+
+\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
+those uses of the \textsf{pubstate} field that print a notice at the
+end of the entry, the \mycolor{\textsf{relatedtype}
+  \texttt{origpubin}} provides much the same information, using data
+extracted from a different entry.  If the information appears inside
+the entry then there is no equivalent \mycolor{\textsf{related}}
+functionality.
+
+\mybigspace This \colmarginpar{\textbf{related}} field is required to
+use \textsf{biblatex's} \mycolor{\textsf{related}} functionality, and
+it should contain the entry key or keys from which \textsf{biblatex}
+should extract data for presentation not on its own, but rather in the
+reference list entry which contains the \textsf{related} field itself.
+Indeed, unless you change the defaults using the
+\mycolor{\textsf{relatedoptions}} field this data will only appear in
+such entries, never on its own and never in citations.  Without a
+\mycolor{\textsf{relatedtype}} field, this will print the default
+type, equivalent to a full reference list entry \emph{immediately
+  after} the entry containing the \textsf{related} field, with no
+intervening string.  You can specify a string using the
+\mycolor{\textsf{relatedstring}} field, so in effect this presents a
+powerful mechanism for presenting full references to related material
+of any sort whatsoever.
+
+\mylittlespace By \colmarginpar{\texttt{related=true}} default, the
+package option \mycolor{\texttt{related}} is set to print
+\textsf{related} 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 \mycolor{\textsf{relatedoptions}} field of
+the relevant entry, to \texttt{false}.
+
+\mybigspace This \colmarginpar{\textbf{relatedoptions}} field will, I
+should expect, only be needed very rarely.  If you want to set
+entry-level options for a \mycolor{\textsf{related}} entry this is
+where you can do it, though please remember one important detail.  By
+default, \textsf{Biber} sets this option to \texttt{dataonly}, which
+among other things prevents the \mycolor{\textsf{related}} entry from
+appearing separately in the list of references, assuming you don't
+specifically cite it elsewhere.  If you use the field yourself, then
+you'll need to include \texttt{dataonly} as one of the options therein
+to maintain this effect.  Of course, it may be you don't want all the
+effects of \texttt{dataonly}, so you can tailor it however you wish.
+See \textsf{biblatex.pdf} §~3.4.
+
+\mybigspace The \colmarginpar{\textbf{relatedstring}} procedure for
+choosing a string to connect the main entry with its related entry/ies
+is straightforward, the default being a \texttt{bibstring}, if any,
+with the same name as the \mycolor{\textsf{relatedtype}}, or
+alternately a string or strings defined within the driver for that
+\mycolor{\textsf{relatedtype}}, as happens with the types
+\mycolor{\texttt{origpubin}} and \mycolor{\texttt{bytranslator}}.
+Failing these, you can supply your own in the
+\mycolor{\textsf{relatedstring}} field, either in the form of the name
+of a pre-defined \texttt{bibstring} or as any text you choose, and
+anything in this field always takes precedence over the automatic
+choices.  If your non-\texttt{bibstring} starts with a lowercase
+letter then \textsf{biblatex-chicago} will capitalize it automatically
+for you depending on context (coolidge:speech, weed:flatiron).  I have
+not altered the standard \textsf{relatedtype} strings, and have in
+fact modified the \textsf{reprinttitle} mechanism to use the
+\mycolor{\texttt{reprintfrom}} string, which works better
+syntactically in this context, and modified the \textsf{pubstate}
+mechanism to use the \mycolor{\texttt{origpubin}} string, which brings
+it into line with the notes \&\ bibliography style.
+
+\mybigspace The \colmarginpar{\textbf{relatedtype}} standard
+\textsf{biblatex} styles define six \mycolor{\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:
+
+\begin{description}
+\item[\qquad \mycolor{bytranslator:}] This prints a full reference to
+  a translation, starting with the (localized) string
+  \enquote{Translated by \textsf{translator} as \textsf{Title},
+    \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}
+  mechanism provides the other, as does the
+  \mycolor{\texttt{origpubas} \textsf{relatedtype}} (see below).
+\item[\qquad \mycolor{default:}] This is the macro used when no
+  \mycolor{\textsf{relatedtype}} is defined.  It prints, as in the
+  standard styles, and with no intervening string, full references to
+  the \mycolor{\textsf{related}} entries.
+\item[\qquad \mycolor{multivolume:}] This briefly lists the individual
+  volumes in a multi-volume work, and works much as in the standard
+  styles.  The \emph{Manual}, as far as I can see, has little to say
+  on the matter.
+\item[\qquad \mycolor{origpubas:}] This type can, if you want, replace
+  the old \textsf{userf} mechanism, described below, for presenting an
+  original with its translation.  It's quite similar to the
+  \mycolor{\texttt{default}} type, but with a \texttt{bibstring}
+  automatically connecting the entry with its \textsf{related}
+  entries.  You can identify other sorts of relationships if you
+  change the introductory string using \textsf{relatedstring}.
+\item[\qquad \mycolor{origpubin:}] I have barely altered this from the
+  \textsf{biblatex} default, and it will present reprint information
+  \emph{after} the main entry rather than within it.  The
+  \emph{Manual} seems to prefer the latter for the notes \&
+  bibliography style and, in some circumstances, the former for
+  author-date.
+\item[\qquad \mycolor{reprintfrom:}] This type provides a replacement
+  for the old \textsf{reprinttitle} mechanism described below.  As in
+  the standard styles, it presents a fuller reference to the reprinted
+  material than does \mycolor{\texttt{origpubin}}, and is designed
+  particularly for presenting pieces formerly printed in other
+  collections or perhaps essays collected from various periodicals.
+  (In \textsf{biblatex-chicago} it contains some kludges to cope with
+  possible \textsf{babel} language environments, so if you find it
+  behaving oddly please let me know, including whether you are using
+  \textsf{babel} [which I've tested] or \textsf{polyglossia} [which I
+  haven't].)
+\end{description}
+
+\mybigspace \textbf{NB:} \mymarginpar{\textbf{reprinttitle}}
+\textbf{If you have been using this feature, you may want to have a
+  look at the} \mycolor{\textsf{relatedtype} \texttt{reprintfrom}},
+\textbf{documented above, for a better solution to this problem, one
+  that also allows you to change the introductory string using the}
+\mycolor{\textsf{relatedstring}} \textbf{field.  The}
+\textsf{reprinttitle} \textbf{field will continue to work as before,
+  however.}  At the request of Will Small, I have included a means of
+providing the 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.
+
+\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)
+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
+possibility also for a list of references, though in-text citations
+will still only refer to individual works.  In order to follow this
+specification, I have provided a third cross-referencing system (the
+others being \textsf{crossref} and \textsf{xref}), and have chosen the
+name \textsf{userf} because it might act as a mnemonic for its
+function.
+
+\mylittlespace In order to use this system, you should start by
+entering both the original and its translation into your .bib file,
+just as you normally would.  The mechanism works for any entry type,
+and the two entries need not be of the same type.  In the entry for
+the \emph{translation}, you put the cite key of the original into the
+\textsf{userf} field.  In the \emph{original's} entry, you need to
+include some means of preventing it appearing separately in the list
+of references, either a toggle in the \textsf{keywords} field or
+perhaps \texttt{skipbib} in the \textsf{options} field.  In this
+standard case, the data for the translation will be printed first,
+followed by the string \texttt{orig. pub. as}, followed by the
+original, author omitted.  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 language in \textsf{origlanguage}, and instead of
+\texttt{originally published as}, you'll get \texttt{French edition:}
+or \texttt{Latin edition:}, etc.\ (aristotle:metaphy:gr,
+aristotle:metaphy:trans).  \textbf{NB:} You can use the
+\mycolor{\textsf{relatedtype} \texttt{origpubas}} to replicate the
+\textsf{userf} functionality, and you can also customize the
+\mycolor{\textsf{relatedstring}} field to achieve the same result as
+with \textsf{origlanguage}.
+
+\enlargethispage{\baselineskip}
+
 \subsection{Commands}
 \label{sec:commands:authdate}
 
@@ -9281,8 +9991,8 @@ These commands allow you to fine-tune the presentation of your
 references in both citations and list of references.  You can find
 many examples of their usage in \textsf{dates-test.bib}, and I shall
 try to point you toward a few such entries in what follows.
-\textbf{NB:} \textsf{biblatex's} \cmd{mkbibquote} command is now
-mandatory in some situations.  See its entry below.
+\textbf{NB:} \textsf{biblatex's} \cmd{mkbibquote} command is mandatory
+in some situations.  See its entry below.
 
 \mybigspace Version \mymarginpar{\textbf{\textbackslash autocap}} 0.8
 of \textsf{biblatex} introduced the \cmd{autocap} command, which
@@ -9298,10 +10008,10 @@ involve the string \texttt{forthcoming} in the \textsf{year} field
 (author:forthcoming, contrib:contrib).
 
 \mylittlespace I have nonetheless retained the system developed,
-following Lehman's example, for the notes \&\ bibliography style,
-which automatically tracks the capitalization of certain fields in
-your .bib file.  I chose these fields after a non-scientific survey of
-entries in my own databases, so of course if you have ideas for the
+following \textsf{biblatex's} example, for the notes \&\ bibliography
+style, which automatically tracks the capitalization of certain fields
+in your .bib file.  I chose these fields after a non-scientific survey
+of entries in my own databases, so of course if you have ideas for the
 extension of this facility I would be most interested to hear them.
 In order to take advantage of this functionality, all you need do is
 begin the data in the appropriate field with a lowercase letter,
@@ -9316,15 +10026,16 @@ purposes, is the complete list of fields where this functionality is
 active:
 
 \begin{enumerate}
+\setlength{\parskip}{-4pt}
 \item The \textbf{addendum} field in all entry types.
 \item The \textbf{booktitleaddon} field in all entry types.
 \item The \textbf{edition} field in all entry types.  (Numerals work
   as you expect them to here.)
 \item The \textbf{maintitleaddon} field in all entry types.
 \item The \textbf{note} field in all entry types.
-\item The \mycolor{\textbf{part}} field in entry types that use it.
-\item The \mycolor{\textbf{prenote}} field prefixed to citation
-  commands.
+\item The \textbf{part} field in entry types that use it.
+\item The \textbf{prenote} field prefixed to citation commands.
+\item The \mycolor{\textbf{relatedstring}} field in all entry types.
 \item The \textbf{shorttitle} field in the \textsf{review}
   (\textsf{suppperiodical}) entry type and in the \textsf{misc} type,
   in the latter case, however, only when there is an
@@ -9346,32 +10057,31 @@ fields, it frankly 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.
 
-\mybigspace This \mymarginpar{\textbf{\textbackslash bibstring}} is
-Lehman's 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.  \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 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.  These are the places, as far as I can make
-out, where \textsf{biblatex's} standard styles support this feature,
-though I have added the last, style-specific, one.  If Lehman
-generalizes it still further in a future release, I shall do the same,
-if possible.
+\mybigspace This \mymarginpar{\textbf{\textbackslash bibstring}} is a
+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.
+\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
+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.  These are the
+places, as far as I can make out, where \textsf{biblatex's} standard
+styles support this feature, though I have added the last,
+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 This \mymarginpar{\textbf{\textbackslash mkbibquote}} is
 the standard \textsf{biblatex} command, which requires attention here
-because it is a crucial part of the mechanism of Lehman's
+because it is a crucial part of the mechanism of that package's
 \enquote{American} punctuation system.  Quotation marks around the
 \textsf{title} field in various entry types are automatically provided
 by \textsf{biblatex-chicago}, but titles-within-titles frequently also
@@ -9424,7 +10134,7 @@ the latter isn't strictly necessary in texts using an American style,
 to which \textsf{biblatex} defaults when \textsf{csquotes} isn't
 loaded.
 
-\mybigspace The \colmarginpar{\textbf{\textbackslash postvolpunct}}
+\mybigspace The \mymarginpar{\textbf{\textbackslash postvolpunct}}
 \emph{Manual} (14.121) unequivocally prescribes that when a
 \textsf{volume} number appears immediately before a page number,
 \enquote{the abbreviation \emph{vol.}\ is omitted and a colon
@@ -9433,7 +10143,7 @@ loaded.
 of a book or of a periodical, and it appears to be a surprising and
 unwelcome feature for many users, conflicting as it may do with
 established typographic traditions in a number of contexts.  Clea~F.\
-Rees has requested a way to customize this, so I have provided the new
+Rees has requested a way to customize this, so I have provided the
 \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,
@@ -9525,13 +10235,56 @@ that \textsf{biblatex-chicago-authordate} sets this command to use
 the most common citation command you will use, and also works fine in
 its multicite form, \textbf{\textbackslash autocites}.
 
+\mybigspace Arne \colmarginpar{\textbf{\textbackslash gentextcite}}
+Skjærholt 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 \mycolor{\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 \cmd{textcite}, on which see below.  The difference is that I've
+added a new optional field to the front of the command to allow you to
+choose which declensional ending to add to the name.  If you don't
+specify this field, you'll get the standard English \enquote{\,'s\,}.
+If you want something different, you'll need to present a third option
+to the command, like so:\
+\cmd{gentextcite[<ending>][][]\{entry:key\}}.  You must include the
+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 \mycolor{\cmd{gentextcites}} command as
+well, though currently you can only specify one genitival ending for
+all keys, like so:\
+\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\}}.
+
+\mylittlespace The syntax of multiple authors' names in running text
+is unpredictable.  There is currently no way to add the genitival
+ending to all the names attached to a single citation key, so it will
+only appear at the end of a group of names in such a case.  (This is
+in keeping with the usual syntax when referring to a multi-author
+work, at least in English.)  When using \mycolor{\cmd{gentextcites}},
+however, you can control whether the ending appears after the name(s)
+attached to each citation key, or whether it only appears after the
+names attached to the last key.  By default, it only appears after the
+last, but the \mycolor{\texttt{genallnames}} preamble and/or entry
+option set to \texttt{true} will attach the ending to each key's
+name(s).  When using one citation command to cite more than one work
+by the same author, it is the \emph{first} occurrence of the name
+which \textsf{biblatex} prints, eliding subsequent ones.  In order to
+get the possessive ending on that name you'll need to set
+\mycolor{\texttt{genallnames}} to \texttt{true}.
+
 \mybigspace In \mymarginpar{\textbf{\textbackslash textcite}} standard
 \textsf{biblatex} this command searches first for a
 \textsf{labelname}, usually taken from the \textsf{author} or
 \textsf{shortauthor} field, then uses the \textsf{shorthand} field if
 the former doesn't exist.  Because of the way the Chicago author-date
 specification recommends handling abbreviations, I have switched this
-around, and the command now searches for a \textsf{shorthand} first.
+around, and the command searches for a \textsf{shorthand} first.
 This holds also for the multicite form \textbf{\textbackslash
   textcites}, though both commands revert to their standard
 \textsf{biblatex} behavior when you give the \texttt{cmslos=false}
@@ -9583,10 +10336,9 @@ ambiguity, \textsf{biblatex} should default to printing a more
 informative reference.
 
 \mylittlespace If you are going to repeat a source, make sure that the
-cite command provides a postnote --- from this release of
-\textsf{biblatex-chicago} you'll no longer get any annoying empty
-parentheses, but you will get another standard citation, which may add
-too much clutter.
+cite command provides a postnote --- you'll no longer get any annoying
+empty parentheses, but you will get another standard citation, which
+may add too much clutter.
 
 %%\enlargethispage{\baselineskip}
 
@@ -9595,18 +10347,17 @@ 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 are new, and 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}
-now 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.
+      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.
 
 \mylittlespace This \mymarginpar{\texttt{pagetracker=\\true}} enables
 page tracking for the \cmd{iffirstonpage} and \cmd{ifsamepage}
@@ -9618,6 +10369,14 @@ or whole spreads in twoside mode.
 minor problem with punctuation in titles, ensuring that the colon
 between a title and a subtitle appears in the correct, matching font.
 
+\mylittlespace This \colmarginpar{\texttt{related=true}} is the
+standard \textsf{biblatex} bibliography option, and it enables the use
+of \mycolor{\textsf{related}} functionality in the list of references.
+I have added an entry option, as well, so if you set this to
+\texttt{false} in your preamble, in the \textsf{options} field, or in
+the \mycolor{\textsf{relatedoptions}} field, you can make the package
+ignore the \mycolor{\textsf{related}} fields.
+
 \mylittlespace This \mymarginpar{\texttt{sortcase=\\false}} turns off
 the sorting of uppercase and lowercase letters separately, a practice
 which the \emph{Manual} doesn't appear to recommend.
@@ -9646,7 +10405,7 @@ surname, using initials in the first instance, and whole names if
 initials aren't enough (15.21).  The option is \textsf{Biber}-only,
 like the previous one.
 
-\enlargethispage{\baselineskip}
+%\enlargethispage{\baselineskip}
 
 \mylittlespace This \mymarginpar{\texttt{usetranslator\\=true}}
 enables automatic use of the \textsf{translator} at the head of
@@ -9689,25 +10448,29 @@ chosen font.  The default definition is:
 
 \mylittlespace At \mymarginpar{\texttt{losnotes}
   \&\\\texttt{losendnotes}} the request of Kenneth Pearce, I have
-added two new \texttt{bibenvironments} to
-\textsf{chicago-authordate.bbx}, for use with the \texttt{env} option
-to the \cmd{printshorthands} command.  The first, \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 latter case to clear up
-some spurious punctuation and white space that I see on my system when
-using endnotes.  (You'll probably 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.)  Please see the
-documentation of \textsf{shorthand} in
-section~\ref{sec:fields:authdate} above for further options available
-to you for presenting and formatting the list of shorthands.
-
-\mylittlespace The next-generation backend \textsf{Biber} offers
-enhanced functionality in many areas, three of which I've implemented
-in this release.  If the default definitions don't work well for you,
-you can redefine all of them in your document preamble --- see
-\textsf{biblatex.pdf} §§4.5.8 and 4.5.5.
+added two \texttt{bibenvironments} to \textsf{chicago-authordate.bbx},
+for use with the \texttt{env} option to the \cmd{printshorthands}
+command.  The first, \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 latter case to clear up some spurious punctuation and white
+space that I see on my system when using endnotes.  (You'll probably
+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 \colmarginpar{New} you use a command like
+\cmd{printbiblist\{shortjournal\}} to print a list of journal
+abbreviations, you can use the \mycolor{\texttt{sjnotes}} and
+\mycolor{\texttt{sjendnotes}} \texttt{bibenvironments} in exactly the
+same way.  Please see the documentation of \textsf{shorthand} and
+\mycolor{\textsf{shortjournal}} in section~\ref{sec:fields:authdate}
+above for further options available to you for presenting and
+formatting these two types of \texttt{biblist}.
+
+\mylittlespace The next-generation backend \textsf{Biber} and
+\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} §§4.5.8 and 4.5.5.
 
 \enlargethispage{\baselineskip}
 
@@ -9722,7 +10485,7 @@ currently is
 \texttt{\{shortauthor,author,\\shorteditor,namea,editor,nameb,%
   translator,namec\}}.
 
-\mylittlespace This \colmarginpar{\cmd{Declare-}\\\texttt{Labeldate}}
+\mylittlespace This \mymarginpar{\cmd{Declare-}\\\texttt{Labeldate}}
 option allows you to alter the order in which \textsf{Biber} and
 \textsf{biblatex} search for the year to use both in citations and at
 the head of entries in the list of references.  This will also be the
@@ -9734,19 +10497,19 @@ configuration, a year will be searched for in the order \textsf{date,
 author-date styles well, except for two situations.  First, when a
 reference apparatus contains many entries with multiple dates, it may
 be simplest to promote the \textsf{origdate} to the head of the list,
-which you can do using the new \mycolor{\texttt{cmsdate} preamble}
-option.  This changes the order to \mycolor{\textsf{origdate, date,
-    eventdate, urldate}}.  Second, in \textsf{music} and
-\textsf{video} entries, and, exceptionally, some \textsf{review}
-entries, the general rule is to emphasize the earliest date.  For
-these three entry types, then, \cmd{DeclareLabeldate} uses the order
-\textsf{eventdate, origdate, date, urldate}.  See \texttt{avdate} in
+which you can do using the \texttt{cmsdate} preamble option.  This
+changes the order to \textsf{origdate, date, eventdate, urldate}.
+Second, in \textsf{music} and \textsf{video} entries, and,
+exceptionally, some \textsf{review} entries, the general rule is to
+emphasize the earliest date.  For these three entry types, then,
+\cmd{DeclareLabeldate} uses the order \textsf{eventdate, origdate,
+  date, urldate}.  See \texttt{avdate} in
 section~\ref{sec:authpreset}, \texttt{cmsdate} in
 section~\ref{sec:authuseropts}, and the \textbf{date} docs in
 section~\ref{sec:fields:authdate}.
 
 \mylittlespace The
-\colmarginpar{\cmd{Declare-}\\\texttt{SortingScheme}} third
+\mymarginpar{\cmd{Declare-}\\\texttt{SortingScheme}} third
 \textsf{Biber} enhancement I have implemented allows you to include
 almost any field whatsoever in \textsf{biblatex's} sorting algorithms
 for the list of references, so that a great many more entries will be
@@ -9756,7 +10519,7 @@ Code in \textsf{biblatex-chicago.sty} sets the \textsf{biblatex}
 option \texttt{sorting=cms}, which is a custom scheme, basically a
 Chicago-specific variant of the default \texttt{nyt}.  You can find
 its definition in \textsf{chicago-authordate.cbx}.  (Please note that
-it now uses the \textsf{labelyear} as its main year component, which
+it uses the \textsf{labelyear} as its main year component, which
 should help improve the automatic sorting of entries by the same
 \textsf{author}.)
 
@@ -9765,20 +10528,15 @@ 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.  The two main
-disadvantages should only occur very rarely.  First, in
-\textsf{author}-less \textsf{article} and \textsf{review} entries
+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
-\textsf{sortkey} for proper alphabetization.  The second occurs
-because the supplemental name fields are treated differently from the
-standard name fields by \textsf{biblatex}.  Ordinarily, you can set,
-for example, \texttt{useauthor=false} in the \textsf{options} field to
-remove the \textsf{author's} name from consideration for sorting
-purposes.  The Chicago-specific option \textsf{usecompiler=false},
-however, doesn't remove \textsf{namec} from such consideration, so in
-some rare corner cases you may need a \textsf{sortkey}.
+\textsf{sortkey} for proper alphabetization.
 
 \subsubsection{{Pre-set \textsf{chicago} Options}}
 \label{sec:authpreset}
@@ -9861,20 +10619,21 @@ 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.
 
-\mylittlespace For \mymarginpar{\texttt{avdate=true}} \textsf{music}
-and \textsf{video} entries, the 16th edition of the \emph{Manual}
-(15.53) strongly recommends both that you provide a recording,
-release, or broadcast date for your references and also 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 types, you can
-use \texttt{avdate=false} in the options when loading
+\paragraph*{\protect\mymarginpar{\texttt{avdate=true}}}
+\label{sec:ad:avdate}\vspace{-.5\baselineskip}
+For \textsf{music} and \textsf{video} entries, the 16th edition of the
+\emph{Manual} (15.53) strongly recommends both that you provide a
+recording, release, or broadcast date for your references and also
+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
+types, you can use \texttt{avdate=false} in the options when loading
 \textsf{biblatex-chicago}.  If, however, you want to tailor the
 algorithm to your own needs, then you can use \cmd{DeclareLabeldate}
 commands in your preamble.  Please be aware, however, that some parts
@@ -9887,8 +10646,8 @@ cases, surprise.  Please see \textsf{music}, \textsf{review}, and
 section~\ref{sec:fields:authdate}; and \cmd{DeclareLabeldate} in
 section~\ref{sec:authformopts}.
 
-\mylittlespace At \colmarginpar{\texttt{booklongxref=\\true}} the
-request of Bertold Schweitzer, I have included two new options for
+\mylittlespace At \mymarginpar{\texttt{booklongxref=\\true}} the
+request of Bertold Schweitzer, I have included two options 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.  This option controls whether multiple
@@ -9916,7 +10675,7 @@ This option can be set either in the preamble or in the
 \textsf{options} field of individual entries.  For controlling the
 behavior of \textsf{inbook}, \textsf{incollection},
 \textsf{inproceedings}, and \textsf{letter} entries, please see
-\mycolor{\texttt{longcrossref}}, below, and also the documentation of
+\texttt{longcrossref}, below, and also the documentation of
 \textsf{crossref} in section~\ref{sec:fields:authdate}.
 
 \mylittlespace This \mymarginpar{\texttt{cmslos=true}} option alters
@@ -9938,19 +10697,67 @@ document preamble.  Cf.\ section~\ref{sec:fields:authdate},
 s.v. \enquote{\textbf{shorthand}} above, and also
 \textsf{cms-dates-sample.pdf}.
 
-\mylittlespace If \colmarginpar{\texttt{hidevolumes=\\true}} both a
+\mylittlespace Roger
+\colmarginpar{\texttt{ctitleaddon=\\comma\\ptitleaddon=\\period}} Hart
+requested a way to control the punctuation printed before the
+\textsf{titleaddon}, \textsf{booktitleaddon}, and
+\textsf{maintitleaddon} fields.  By default, this is
+\cmd{addcomma\cmd{add\-space}} (\mycolor{\textsf{ctitleaddon}}) for
+nearly all \textsf{book-} and \textsf{maintitleaddons} in the list of
+references, while \cmd{addperiod\cmd{addspace}}
+(\mycolor{\textsf{ptitleaddon}}) is the default before most
+\textsf{titleaddons} there.  If the punctuation printed isn't correct
+for your needs, you can set the relevant option either in the preamble
+or in individual entries.  (Cf.\ coolidge:speech and
+schubert:muellerin.) The accepted option keys are:
+
+\begin{description}
+\setlength{\parskip}{-4pt}
+\item[\qquad none] = no punctuation at all
+\item[\qquad space] = \cmd{addspace}
+\item[\qquad comma] = \cmd{addcomma\cmd{addspace}}
+\item[\qquad period] = \cmd{addperiod\cmd{addspace}}
+\item[\qquad colon] = \cmd{addcolon\cmd{addspace}}
+\item[\qquad semicolon] = \cmd{addsemicolon\cmd{addspace}}
+\end{description}
+
+If you need something a little more exotic, you can directly
+\cmd{renewcommand} either \cmd{ctitleaddonpunct} or
+\cmd{ptitleaddonpunct} (or both) in your preamble, but it's worth
+remembering that the redefinition will hold for all instances, unless
+you use the \textsf{options} field in your other entries with a
+\textsf{titleaddon} field.  A simpler solution might be to set the
+relevant option to \texttt{none} in your entry and then include the
+punctuation in the \textsf{titleaddon} field itself.
+
+\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
 \textsf{biblatex-chicago} will ordinarily suppress the
 \textsf{volumes} field.  In some instances, when a \textsf{maintitle}
 is present, this may not be the desired result.  In this latter case,
-if the \textsf{volume} appears before the \textsf{maintitle}, this new
+if the \textsf{volume} appears before the \textsf{maintitle}, this
 option, 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}.
 
-\mylittlespace This \colmarginpar{\texttt{longcrossref=\\false}} is
+\mylittlespace This \colmarginpar{\texttt{journalabbrev\\=notes}}
+option controls the printing of the \mycolor{\textsf{shortjournal}}
+field in place of the \textsf{journaltitle} field in citations and
+reference lists.  It is set to \texttt{notes} by default, so as
+shipped \textsf{biblatex-chicago-authordate} will print such fields
+only in citations, but you can set it, either in the preamble or in
+individual entries, to one of three other values: \texttt{true} prints
+the abbreviated form both in citations and reference lists,
+\texttt{bib} in the reference list only, and \texttt{false} in
+neither.  Please 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
+\mycolor{\textbf{shortjournal}} in section~\ref{sec:entryfields},
+above.
+
+\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
@@ -9983,9 +10790,9 @@ governed by the following options:
 This option can be set either in the preamble or in the
 \textsf{options} field of individual entries.  For controlling the
 behavior of \textsf{book}, \textsf{bookinbook}, \textsf{collection},
-and \textsf{proceedings} entries, please see
-\mycolor{\texttt{booklongxref}}, above, and also the documentation of
-\textsf{crossref} in section~\ref{sec:fields:authdate}.
+and \textsf{proceedings} entries, please see \texttt{booklongxref},
+above, and also the documentation of \textsf{crossref} in
+section~\ref{sec:fields:authdate}.
 
 %\enlargethispage{\baselineskip}
 
@@ -9999,20 +10806,12 @@ preamble, then the package won't perform this substitution in any
 entry type whatsoever.  (The bibstring expands to
 \enquote{\texttt{n.d.}} in English.)
 
-\mylittlespace This \mymarginpar{\texttt{usecompiler=\\true}} option
-enables automatic use of the name of the compiler (in the
-\textsf{namec} field) at the head of an entry, usually in the absence
-of an \textsf{author}, \textsf{editor}, or \textsf{translator}, in
-accordance with the specification (\emph{Manual} 15.35).  It may also,
-like \texttt{useauthor}, \texttt{useeditor}, and
-\texttt{usetranslator}, be disabled on a per-entry basis by setting
-\texttt{usecompiler=false} in the \textsf{options} field.  The only,
-subtle, difference between this switch and those standard
-\textsf{biblatex} switches is that this one won't remove
-\textsf{namec} from the sorting list, whereas \texttt{useauthor=false}
-and \texttt{useeditor=false} do remove the \textsf{author} and
-\textsf{editor}.  You may, therefore, in corner cases, require a
-\textsf{sortkey} in the entry.
+\mylittlespace As \colmarginpar{\texttt{usecompiler=\\true}}
+\textsf{biblatex} automatically includes a \mycolor{\texttt{usenamec}}
+option as standard, the Chicago-specific option \texttt{usecompiler}
+is now deprecated.  Please replace it your documents and .bib files
+with \mycolor{\texttt{usenamec}}, which works much better across the
+board.
 
 \subsubsection{Style Options -- Preamble}
 \label{sec:authuseropts}
@@ -10034,13 +10833,12 @@ 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 With \colmarginpar{\texttt{cmsdate}} this release, I am
-providing a new method for simplifying the creation of databases with
-a great many multi-date entries: 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
-\enquote{correctly} as I can.  The switches for this option are
+\mylittlespace This \mymarginpar{\texttt{cmsdate}} option used
+\emph{in the preamble} provides a method for simplifying the creation
+of databases with a great many multi-date entries.  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 \enquote{correctly} as I can.  The switches for it are
 basically the same as for the entry-only option, that is, assuming an
 entry presents a reprinted edition of a work by Smith, first published
 in 1926 (the \textsf{origdate}) and reprinted in 1985 (the
@@ -10059,18 +10857,18 @@ in 1926 (the \textsf{origdate}) and reprinted in 1985 (the
   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
-  \texttt{new} and \texttt{old} now work like \texttt{both}.
+  \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
-synonyms for the latter, \texttt{new} or \texttt{old}), then
-\textsf{biblatex-chicago-authordate} (and \textsf{authordate-trad})
-will now change the default \cmd{DeclareLabel\-date} definition so
-that the \textsf{labelyear} search order will be
-\mycolor{\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
+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
+\textsf{authordate-trad}) will change the default
+\cmd{DeclareLabel\-date} 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
@@ -10102,18 +10900,17 @@ please see the documentation of the \textbf{date} field in
 section~\ref{sec:fields:authdate} for the fullest discussion of date
 presentation in the \textsf{authordate} styles.
 
-\mylittlespace Although \colmarginpar{\texttt{cmsorigdate}} I can't
+\mylittlespace Although \mymarginpar{\texttt{cmsorigdate}} I can't
 currently think of any reason why anyone would want to use it on its
 own, I should nonetheless mention that the \texttt{cmsorigdate} option
 in your preamble will change the default \cmd{DeclareLabeldate}
-settings to \mycolor{\textsf{origdate, date, eventdate, urldate}}.
-Setting \texttt{cmsdate} to \texttt{on} or \texttt{both} in the
-preamble --- see the previous option --- sets this to true, but if for
-some reason you want to set it to true without any of the other
-effects of the \texttt{cmsdate} option, then you can.  The effects may
-surprise.
-
-\mylittlespace When \colmarginpar{\texttt{compresspages}} set to
+settings to \textsf{origdate, date, eventdate, urldate}.  Setting
+\texttt{cmsdate} to \texttt{on} or \texttt{both} in the preamble ---
+see the previous option --- sets this to true, but if for some reason
+you want to set it to true without any of the other effects of the
+\texttt{cmsdate} option, then you can.  The effects may surprise.
+
+\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).
@@ -10136,6 +10933,12 @@ once again footnote marks will revert to the \LaTeX\ default, but of
 course you also lose a fair amount of other formatting, as well.  See
 section~\ref{sec:loading:auth}, below.
 
+\mylittlespace This \colmarginpar{\texttt{genallnames}} option affects
+the choice of which names to present in the genitive case when using
+the \mycolor{\cmd{gentextcites}} command.  Please see the
+documentation of that command in section~\ref{sec:cite:authordate},
+above.
+
 \mylittlespace Several \mymarginpar{\texttt{headline}\\\texttt{(trad
     only)}} users requested an option that turned off the automatic
 transformations that produce sentence-style capitalization in the
@@ -10196,7 +10999,7 @@ use the \cmd{citereset} command, allied possibly with the
 \textsf{biblatex.pdf} §3.1.2.1.
 
 \mylittlespace Originally
-\colmarginpar{\texttt{postnotepunct}\\(experimental)} designed for the
+\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
 you to alter the punctuation that appears just before the
@@ -10205,15 +11008,15 @@ particular the provision of comments within parenthetical citations.
 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\}}.  Now, with
-this option enabled, \cmd{autocite[; some comment]\{citekey\}} will
-do.  More generally, the \mycolor{\texttt{postnotepunct}} option
+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 \mycolor{experimental}.  Note also that the
+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.
 
@@ -10237,6 +11040,17 @@ rule intervenes to emphasize this continuation.  I haven't tested this
 code very thoroughly, and it's possible that frequent use of floats
 might interfere with it.  Let me know if it causes problems.
 
+\mylittlespace Stefan \colmarginpar{\texttt{xrefurl}} Björk pointed
+out that when, using the \texttt{longcrossref} or
+\texttt{booklongxref} options, you turn on the automatic abbreviation
+of multiple entries in the same (e.g.) \textsf{collection} or
+\textsf{mvcollection}, you could entirely lose a \textsf{url} that
+might be helpful for locating a source, as the abbreviated forms in
+the reference list wouldn't include this information.  Setting this
+option to \textsf{true} either in the preamble or in individual
+entries will allow the \textsf{url}, \textsf{doi}, or \textsf{eprint}
+field to appear even in these abbreviated references.
+
 \subsubsection{Style Options -- Entry}
 \label{sec:authentryopts}
 
@@ -10244,7 +11058,7 @@ 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.
 
-\mylittlespace The \colmarginpar{\texttt{cmsdate}} 16th edition of the
+\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
 \texttt{cmsdate} entry option.  It has 3 possible states relevant to
@@ -10263,7 +11077,7 @@ reprinted edition of a work by Smith, first published in 1926 (the
   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
-  \texttt{old} now work like \texttt{both}.
+  \texttt{old} work like \texttt{both}.
 \end{description}
 
 As I explained in detail above in section~\ref{sec:fields:authdate},
@@ -10283,8 +11097,8 @@ be as follows:
   (Smith 1926a).  This style is no longer recommended by the 16th
   edition of the \emph{Manual}.
 \item[\qquad both:] The citation will look like (Smith [1926a] 1985).
-  The 15th-edition options \texttt{old} and \texttt{new} are now
-  synonyms for this.
+  The 15th-edition 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}.
@@ -10293,13 +11107,13 @@ be as follows:
 If, \mymarginpar{\texttt{switchdates}} for any reason, simply
 switching the \textsf{date} and the \textsf{origdate} isn't possible
 in a given entry, then you can put \texttt{switchdates} in the
-\textsf{options} field to achieve the same result.  Also, now you can
-use the new preamble version \colmarginpar{\texttt{cmsdate}\\\emph{in
-    preamble}} of \mycolor{\texttt{cmsdate}} to change the default
-order of \cmd{DeclareLabeldate}, generally making this date-switching
-in your .bib file unnecessary.  Please take a look at the full
-documentation of the \textbf{date} field to which I referred just
-above, at the preamble \texttt{cmsdate} documentation in
+\textsf{options} field to achieve the same result.  Also, you can use
+the preamble version \mymarginpar{\texttt{cmsdate}\\\emph{in
+    preamble}} of \texttt{cmsdate} to change the default order of
+\cmd{DeclareLabeldate}, generally making this date-switching in your
+.bib file unnecessary.  Please take a look at the full documentation
+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.
@@ -10384,7 +11198,7 @@ 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 §§~4.9.1 and 4.11.8 in Lehman's \textsf{biblatex.pdf}.
+also §§~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
@@ -10420,19 +11234,19 @@ Chicago author-date specification.  However, if \enquote{a reference
   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 new
-(\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 limits,
-listed above, on how many names to print in a citation.  Without
-\texttt{uniquelist}, \textsf{biblatex} would present such a work as,
-e.g., (Hlatky et al. 2002b), while hlatky:hrt would be (Hlatky et
-al. 2002a).  This does distinguish between them, but inaccurately, as
-it suggests that the two different author lists are exactly the same.
-With \texttt{uniquelist}, the two citations might look like (Hlatky,
-Boothroyd et al.\ 2002) and (Hlatky, Smith et al.\ 2002), which is
-what the specification requires.
+  must distinguish between them} (15.28).  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 limits, listed above, on how many names to
+print in a citation.  Without \texttt{uniquelist}, \textsf{biblatex}
+would present such a work as, e.g., (Hlatky et al. 2002b), while
+hlatky:hrt would be (Hlatky et al. 2002a).  This does distinguish
+between them, but inaccurately, as it suggests that the two different
+author lists are exactly the same.  With \texttt{uniquelist}, the two
+citations might look like (Hlatky, Boothroyd et al.\ 2002) and
+(Hlatky, Smith et al.\ 2002), which is what the specification
+requires.
 
 \mylittlespace If, however, the distinguishing name occurs further
 down the author list --- in fourth or fifth position in our examples
@@ -10474,15 +11288,15 @@ helpfully provide as much information as is available, including
 fields that users may well wish not to have printed (ISBN, URL, DOI,
 \textsf{pagetotal}, inter alia).  The standard \textsf{biblatex}
 styles contain a series of options, detailed in \textsf{biblatex.pdf}
-§3.1.2.2, for controlling the printing of some of these fields, and
-with this release I have implemented the ones that are relevant to
+§3.1.2.2, for controlling the printing of some of these fields, and I
+have implemented others that are relevant to
 \textsf{biblatex-chicago}, along with a couple that Scot requested and
 that may be of more general usefulness.  There is also a general
 option to excise with one command all the fields under consideration
 -- please see section~\ref{sec:authpreset} above.
 
-\mylittlespace Finally, allow me to reiterate what Philipp Lehman says
-in \textsf{biblatex.pdf}, to wit, if you aren't going to use
+\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.
@@ -10496,12 +11310,13 @@ in other \enquote{American} \textsf{biblatex} styles (e.g.,
 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, Antti-Juhani
-Kaijahano has very kindly provided \textsf{cms-finnish.lbx} for
+partial fulfillment of this request.  For this release, Stefan Björk
+has very kindly provided \mycolor{\textsf{cms-swedish.lbx}} for
 speakers of that language, thereby adding to the generous
-contributions of Baldur Kristinsson (\textsf{cms-icelandic.lbx}) and
-Håkon Malmedal (\textsf{cms-norsk.lbx}, \textsf{cms-norwegian.lbx},
-and \textsf{cms-nynorsk.lbx}).  I include \textsf{cms-british.lbx} in
+contributions of Antti-Juhani Kaijahano (\textsf{cms-finnish.lbx}),
+Baldur Kristinsson (\textsf{cms-icelandic.lbx}), and Håkon Malmedal
+(\textsf{cms-norsk.lbx}, \textsf{cms-norwegian.lbx}, and
+\textsf{cms-nynorsk.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
@@ -10540,13 +11355,13 @@ complicated rules outlined in previous releases of
 the \texttt{british} option.
 
 \mylittlespace If you want to use Finnish, French, German, Icelandic,
-or Norwegian strings in the reference apparatus, then you can load
-\textsf{babel} with \texttt{finnish}, \texttt{french},
+Norwegian, or Swedish strings in the reference apparatus, then you can
+load \textsf{babel} with \texttt{finnish}, \texttt{french},
 \texttt{german}, \texttt{icelandic}, \texttt{ngerman}, \texttt{norsk},
-or \texttt{nynorsk} 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 provides these if
-you load the package in the standard way.
+\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
+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
@@ -10595,11 +11410,11 @@ 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 and Norwegian 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.
+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}
+\section{One\,.bib Database, Two Chicago Styles}
 \label{sec:twostyles}
 
 I have, when designing this package, attempted to keep at least half
@@ -10645,7 +11460,7 @@ nonetheless:
   \ref{sec:authentryopts} when doing the conversion to author-date.
 \end{enumerate}
 
-\subsection{Author-date -> Notes}
+\subsection{Author-Date -> Notes}
 \label{sec:conv:authnotes}
 
 It is my impression that an author-date .bib database is somewhat
@@ -10696,8 +11511,8 @@ of the things you may need to address:
 
 For \mymarginpar{\textbf{endnotes}} users of the \textsf{endnotes}
 package --- or of \textsf{pagenote} --- \textsf{biblatex} 0.9 offers
-considerably enhanced functionality.  Please read Lehman's RELEASE
-file and the documentation of the \texttt{notetype} option in
+considerably enhanced functionality.  Please read the package's
+RELEASE file and the documentation of the \texttt{notetype} option in
 \textsf{biblatex.pdf} §~3.1.2.1.
 
 \mylittlespace Another \mymarginpar{\textbf{memoir}} problem I have
@@ -10714,14 +11529,14 @@ package, but in this case a simple workaround is to load
 \textsf{biblatex} \emph{after} you've loaded \textsf{ragged2e} in your
 document preamble.
 
-\enlargethispage{\baselineskip}
+%\enlargethispage{\baselineskip}
 
 \mylittlespace Nick \mymarginpar{\textbf{Xe\LaTeX}} Andrewes alerted
 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 Lehman's punctuation-tracking code for
+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
@@ -10735,15 +11550,15 @@ package.
 \label{sec:bugs}
 
 This release implements the 16th edition of the \emph{Chicago Manual
-  of Style}.  It now also contains a version of the author-date style
+  of Style}.  It also contains a version of the author-date style
 (\textsf{authordate-trad}) with traditional title formatting,
 alongside the \textsf{authordate} code which unifies the treatment of
-titles between itself and the notes \&\ bibliography style.  I hope
-that users will migrate to one of these styles implementing the most
-recent specification, as I am focusing my development and testing time
-there.  With the current release, I am calling the 15th-edition styles
-\enquote{strongly deprecated,} but if you still have urgent feature
-requests for them, I'll do what I can.
+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 calling the
+15th-edition styles \enquote{obsolete,} and have moved them into a
+separate directory in the package.
 
 \mylittlespace Regardless of which edition you are considering, there
 are a number of things I haven't implemented.  The solution in
@@ -10760,7 +11575,7 @@ the \emph{Manual} (14.281) even makes it clear that you should be
 using a different reference book if you are presenting work in the
 field, so I've thought it prudent to stay clear of those waters so
 far.  I have received a request for this feature, however, so when I
-have finished the updates for the 16th edition I shall look at it more
+have cleared a few long-standing requests I shall look at it more
 closely.  If you have other issues with particular sorts of citation,
 I'm of course happy to take them on board.  The \emph{Manual} covers
 an enormous range of materials, but if we exclude the legal citations
@@ -10769,48 +11584,17 @@ service to address the vast majority of them.  If this optimism proves
 misguided, please let me know.
 
 \mylittlespace I haven't yet explored the possible uses in
-\textsf{biblatex-chicago} for the new(-ish) \textsf{biblatex} fields
-\textsf{related}, \textsf{relatedtype}, and \textsf{relatedstring}.
-It's possible they will solve some issues more simply and elegantly
-than my own kludges do, so I hope to address this for the next
-release.  The same holds for the \textsf{datelabelsource} field, new
-in \textsf{biblatex} 2.8.
+\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.  As late as I am with the file for the
-16th edition, I shall attempt to address this in a future release.  If
-you run into this problem, he suggests placing all the citations
-together in parentheses at the end of the annotation, though on my
-machine this doesn't always work too well, either.
-
-\mylittlespace Version 1.5 of \textsf{biblatex} revised the way the
-package deals with breaking long URLs and DOIs across lines.  The new
-code is designed to deal as elegantly as possible with as wide a
-variety of cases as possible, but in a few of my test entries it has
-caused some line-breaking issues of its own.  Depending on the nature
-of your cited sources, it may be useful for you to revert to the
-older, pre-1.5 \textsf{biblatex} behavior, something which is easily
-done by copying and pasting the old definition of the
-\cmd{biburlsetup} command into your document preamble.  If you look in
-the preambles of \textsf{cms-notes-sample.tex} or
-\textsf{cms-dates-sample.tex}, you can see the redefinition and copy
-it from there, just to see whether it helps your situation.  If it
-would be generally useful, I could also easily turn it into a package
-option.  Feedback welcome.
-
-\mylittlespace The switch to \textsf{Biber} for the author-date
-specification means that \textsf{biblatex} now provides considerably
-enhanced handling of the various date fields.  I have attempted to
-document the relevant changes in \textsf{cms-dates-sample.pdf} and in
-the \textbf{date} discussion in section~\ref{sec:fields:authdate},
-above, but it's possible the package may need some changes to cope
-with all the permutations.  Please let me know if you find something
-that looks like a bug.
-
-\mylittlespace Speaking of \textsf{dates}, now that there's an option
-for the automatic compression of page ranges, something similar could
-perhaps be provided for year ranges.  I shall be looking into this.
+of annotated bibliographies.  If you run into this problem, he
+suggests placing all the citations together in parentheses at the end
+of the annotation, though on my machine this doesn't always work too
+well, either.
 
 \mylittlespace Roger Hart, Pierric Sans, and a number of other users
 have reported a bug in the formatting of title fields.  This, as far
@@ -10821,14 +11605,6 @@ title, particularly Unicode ones.  If you are using
 set of curly braces \{\}\ at the start of the field, but I shall look
 into this further.
 
-\mylittlespace Roger Hart has requested that I incorporate some means
-of changing the punctuation before \textsf{titleaddon} fields, perhaps
-using a customizable command like \cmd{titleaddonpunct}.  I hope to
-provide this in the next release.  He has also requested, despite the
-\emph{Manual's} objections, the possibility of using both
-\texttt{Idem} and \texttt{Ibid.}\ in notes.  I shall look into this
-for the next major release.
-
 \enlargethispage{-4\baselineskip}
 
 \mylittlespace This release fixes the formatting errors of which I am
@@ -10837,11 +11613,11 @@ the \cmd{partedit} command in section~\ref{sec:formatcommands} above.
 There also remain the larger issues I've discussed throughout this
 documentation, which mainly represent my inability to make all of
 \textsf{biblatex-chicago's} formatting functions transparent for the
-user, but thankfully Lehman's superb punctuation-tracking code has
-preemptively fixed a great many small errors, some of which I hadn't
-even noticed before I began testing that functionality.  That there
-are other micro-bugs seems certain --- if you report them I'll do my
-best to fix them.
+user, but thankfully \textsf{biblatex's} superb punctuation-tracking
+code preemptively fixed a great many small errors, some of which I
+hadn't even noticed before I began testing that functionality.  That
+there are other micro-bugs seems certain --- if you report them I'll
+do my best to fix them.
 
 \mylittlespace I haven't looked closely at the standard
 \textsc{Bib}\TeX\ style by Glenn Paulley, contained in
@@ -10853,7 +11629,172 @@ code for it, let me know, and I'll look into it.
 \section{Revision History}
 \label{sec:history}
 
-\textbf{0.9.9i: Released \today}
+\textbf{1.0rc1: Released \today}
+
+\mylittlespace Obsolete and Deprecated Features:\label{deprec:obsol}
+\begin{itemize}
+\item The 15th-edition styles are now obsolete, and have been moved to
+  a new \mycolor{\texttt{obsolete}} subdirectory.  You can still use
+  them as they stand, but they won't compile against the newest
+  \textsf{biblatex}, so you'll have to make sure that you have an
+  older version (2.9a, perhaps).  If you are still using them, I
+  strongly urge you to consider switching to the the 16th-edition
+  styles, which contain many new features and bug-fixes.
+\item The old Chicago-specific option \texttt{usecompiler} is
+  deprecated, and has been replaced by the standard \textsf{biblatex}
+  \mycolor{\texttt{usenamec}}.  If you have been using the former in
+  your preamble or in your .bib entries, please replace it with the
+  latter, which works better across the board.  \texttt{Usecompiler}
+  still \enquote{works,} just not very well.
+\end{itemize}
+
+Other New Features:
+
+\begin{itemize}
+\item Stefan Björk has very generously provided a Swedish localization
+  file for the package --- \mycolor{\textsf{cms-swedish.lbx}} ---
+  which can be loaded and used with \textsf{babel} just like the other
+  localizations.
+\item I have added support for \mycolor{\textbf{related}}
+  functionality to all the Chicago styles, including all the standard
+  \textsf{biblatex} \mycolor{\textbf{relatedtypes}}.  It is turned on
+  by default in all styles, but you can turn it off, or alter where
+  the information is printed, using the \mycolor{\texttt{related}}
+  option in the preamble or in individual entries.  In the notes \&\
+  bibliography style, \textsf{related} information is printed by
+  default only in the bibliography, but you can change that by setting
+  the option.  In the author-date styles, it will only ever print in
+  the list of references, depending on the option's setting.  Please
+  see sections~\ref{sec:related} and \ref{sec:authrelated} for the
+  details.
+\item I have improved the name-handling code in all styles,
+  regularizing the functioning of the \textsf{namea}, \textsf{nameb},
+  and \textsf{namec} fields with respect to the other, standard
+  \textsf{biblatex} names.  The former two in particular are newly
+  available in the \textsf{collection} and \textsf{periodical} entry
+  types, and \textsf{biblatex-chicago} now recognizes the standard
+  \mycolor{\texttt{usenamea}}, \mycolor{\texttt{usenameb}}, and
+  \mycolor{\texttt{usenamec}} toggles, the last replacing the
+  deprecated \texttt{usecompiler} (as above).  You can also now use
+  the \mycolor{\textbf{nameatype}} field just as you would an
+  \textsf{editortype}, extending the possibilities for identifying
+  certain roles attached specifically to \textsf{titles} as opposed to
+  \textsf{booktitles} or \textsf{maintitles}.
+\item After a request by user BenVB, I have added support for the
+  \textsf{biblatex} \mycolor{\textbf{shortjournal}} field, which
+  allows you to present abbreviated \textsf{journaltitles} in all the
+  styles.  You can use the \mycolor{\texttt{journalabbrev}} option to
+  control where in your document these abbreviated forms will appear.
+  By default, the field is ignored in the notes \&\ bibliography
+  style, and appears only in citations in the author-date styles.  You
+  can also print a list of journal abbreviations, rather in the manner
+  of a list of shorthands, using a command like:
+  \cmd{printbiblist\{shortjournal\}}.  Even though the
+  \textsf{periodical} entry type uses the \textsf{title} and
+  \textsf{shorttitle} fields in place of \textsf{journaltitle} and
+  \textsf{shortjournal}, these entries are included in this
+  functionality, and controlled by the same \texttt{journalabbrev}
+  option.  Please see s.v.\ \enquote{shortjournal} in
+  sections~\ref{sec:entryfields} and \ref{sec:fields:authdate}.
+\item Following a request by Arne Skjærholt, and his generous
+  provision of some code to get me started, I have implemented a new
+  \mycolor{\cmd{gentextcite}} citation command in all styles.  The
+  \enquote{gen} part of the name refers to the genitive case, and it
+  adds a possessive ending --- \textbf{'s} by default --- to the
+  author's name in what is otherwise an ordinary \cmd{textcite}.  You
+  can change the added ending however you want, using a third optional
+  field to the citation command, and you can control to which names
+  the ending is added in a \mycolor{\cmd{gentextcites}} multicite
+  command by using the \mycolor{\texttt{genallnames}} preamble and
+  entry option.  Please see sections~\ref{sec:citecommands} and
+  \ref{sec:cite:authordate} for the details.
+\item Stefan Björk pointed out that \textsf{url}, \textsf{doi}, and
+  \textsf{eprint} information could be totally ignored in some entries
+  when you used the abbreviated cross-referencing functionality
+  accessed through the \textsf{crossref} and \textsf{xref} fields.  At
+  his request, I have provided a new \mycolor{\texttt{xrefurl}} entry
+  and preamble option for all the styles to control the printing of
+  this information in abbreviated notes or bibliography (reference
+  list) entries.  Please see sections~\ref{sec:useropts} and
+  \ref{sec:authuseropts} for the details.
+\item In a related change, I have stopped child entries inheriting
+  \textsf{url}, \textsf{doi}, and \textsf{eprint} fields from their
+  cross-ref'd parents, so if your documents rely on this behavior
+  please note that you'll have to provide such fields manually in the
+  child entries.
+\item Roger Hart long ago requested a way to control the punctuation
+  before \textsf{book-}, \textsf{main-}, or plain \textsf{titleaddon}
+  fields, and I have finally added it in this release in the form of
+  two entry and preamble options, \mycolor{\texttt{ptitleaddon}} and
+  \mycolor{\texttt{ctitleaddon}}, available in all styles.  By
+  default, the former prints \cmd{addperiod}\cmd{addspace}, hence its
+  name, and the latter\,\cmd{addcomma}\cmd{addspace}, but you can
+  change either or both depending on which field you are using and
+  which sort of entry it appears in --- the default output can be your
+  guide to which option(s) to change.  Please see the available valid
+  option keys in sections~\ref{sec:chicpreset} and
+  \ref{sec:authpreset}.
+\item The same user also long ago requested that the notes \&\
+  bibliography style make it possible to use \emph{Idem} when two
+  consecutive notes cite different works by the same author.  You can
+  now use the standard \textsf{biblatex} option
+  \texttt{idemtracker=constrict} in your preamble to activate this in
+  your documents, but please be aware, first, that the \emph{Manual}
+  doesn't exactly approve of this and, second, that you'll only see
+  \emph{Idem} in short notes, never in full ones, which seems to be
+  the standard (\textsf{biblatex}) way of implementing this.
+\item Also only in the notes \& bibliography style, I have added a
+  \mycolor{\texttt{shorthandpunct}} option to control the punctuation
+  that appears before the first appearance of a \textsf{shorthand}
+  and/or a \textsf{shorthandintro} in a long note.  The default is
+  \cmd{addspace}, but you can change it in your preamble or in
+  individual entries.  Please see the available valid option keys in
+  section~\ref{sec:chicpreset}.
+\item After reading a discussion started by Ryo Furue at
+  \href{https://github.com/plk/biblatex/issues/363}{github}, I have
+  added, in the author-date styles only, a test to some spacing
+  commands to prevent line breaks immediately after abbreviation dots.
+  These tests apply only in running text, never in the list of
+  references, where good line breaks are already hard enough to find.
+\item In addition to moving the 15th-edition styles into an
+  \texttt{obsolete} subdirectory, I have also reorganized the
+  author-date style files, adding
+  \mycolor{\textsf{chicago-dates-common.cbx}} which contains the code
+  that is common to the \texttt{trad} and the standard
+  \texttt{authordate} styles.  Nothing has changed in terms of loading
+  the styles, the changes being designed primarily to ease
+  maintenance.
+\item I have created two new documentation files (and an appendix) to
+  provide short introductions to the Chicago styles, introductions
+  which attempt to fill the gap between the Quickstart section
+  (\ref{quickstart}) and the fuller documentation contained in
+  sections~\ref{sec:Spec} and \ref{sec:authdate} of this file.  Both
+  \mycolor{\textsf{cms-notes-intro.pdf}} and
+  \mycolor{\textsf{cms-dates-intro.pdf}} are fully hyperlinked so you
+  can move easily from formatted citations and (annotated) references
+  to .bib entries and back, with marginal references to the fuller
+  discussions here.  There is also a short
+  \mycolor{\textsf{cms-trad-appendix.pdf}} file to discuss a few
+  entries that would need special treatment for the \texttt{trad}
+  style.  The \textsf{sample} files for each style still exist, but I
+  intend them mainly for testing purposes, while many more (annotated)
+  entries are still available for consultation in
+  \textsf{notes-test.bib} and \textsf{dates-test.bib}.
+\item I have made a number of other small enhancements to and fixed
+  numerous bugs in all the styles, including some subtle inaccuracies
+  in author-date citations spotted by Arne Skjærholt and some macros
+  in \textsf{inproceedings} entries that had been missing for years.
+  I have provided some default values for counters in
+  \textsf{biblatex-chicago.sty} that aid in breaking long
+  \textsf{urls} across lines, but I make no pretense that these fully
+  adhere to the \emph{Manual's} specifications.  I have added a few
+  \texttt{bibstrings}, currently missing in standard
+  \textsf{biblatex}, to \textsf{cms-german.lbx} for use with the
+  \mycolor{\textsf{related}} functionality.  Recommendations for
+  better ones would be gratefully received.
+\end{itemize}
+
+\textbf{0.9.9i: Released May 16, 2016}
 \begin{itemize}
 \item This is another interim release, allowing the use of
   \textsf{biblatex} 3.4 for those who want to try it.  I have also
@@ -10896,10 +11837,10 @@ code for it, let me know, and I'll look into it.
 
 \textbf{0.9.9f: Released August 15, 2014}
 \begin{itemize}
-\item I've \label{deprec:obsol} made the alterations needed to bring
-  the styles into line with the latest version of \textsf{biblatex}
-  (2.9a).  This is the version that has been tested most thoroughly
-  with \textsf{biblatex-chicago}, so I strongly recommend using it.
+\item I've made the alterations needed to bring the styles into line
+  with the latest version of \textsf{biblatex} (2.9a).  This is the
+  version that has been tested most thoroughly with
+  \textsf{biblatex-chicago}, so I strongly recommend using it.
 \item I fixed several inaccuracies in the presentation of abbreviated
   cross-referen\-ces in all the Chicago styles, and while I was working
   on that portion of the code it seemed an opportune moment to fulfill