summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE')
-rw-r--r--Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE146
1 files changed, 145 insertions, 1 deletions
diff --git a/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE b/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE
index 9282231bf85..6c2ad051b20 100644
--- a/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE
+++ b/Master/texmf-dist/doc/latex/biblatex-chicago/RELEASE
@@ -1,3 +1,147 @@
+Release notes for version 1.0rc5 [2018-01-16]:
+
+ - Recent releases of biblatex have introduced some compatibility
+ problems for biblatex-chicago, particularly with regard to the
+ handling of the "origlanguage" field (now a list), but also through
+ the renaming of several other fields and declarations, e.g.,
+ \DeclareSortingTemplate. I have improved the handling of the
+ "origlanguage" list by including many new bibstrings in the
+ package's localization files, but other changes to formatting
+ macros have made backward compatibility with older releases of
+ biblatex difficult or impossible. Please upgrade to version 3.10
+ -- which has received the most testing -- to use these styles.
+
+ - As I mentioned in the initial Notice of biblatex-chicago.pdf, the
+ 17th edition of the Manual has now appeared, and my development
+ energies from this point will be devoted to upgrading all styles to
+ conform to it. You can still file bug reports against the 16th
+ edition, but the next major feature release will be based on the
+ 17th. In preparation for these changes, I have removed all the
+ 15th-edition files from the package.
+
+Other New Features:
+
+ - After fielding multiple requests over the years, I have added three
+ new entry types -- Jurisdiction, Legal, and Legislation -- to allow
+ the presentation of court cases, laws, treaties, congressional
+ (parliamentary) debates and hearings, constitutions, and executive
+ documents. The first ("round" and "square") and last ("canada",
+ "constitution", "hansard", "hearing", "uk", and "un") introduce a
+ number of new "entrysubtypes" to help with formatting quirks,
+ including the presentation of Canadian and UK materials for
+ inclusion in an otherwise US context. There are also several new
+ options ("legalnotes", "noneshort", "short", and "supranotes") for
+ controlling the output. I have documented all of this in section 6
+ of biblatex-chicago.pdf, a separate section both because the
+ specification really comes from the Bluebook rather than the
+ Manual, and also because they are the only entry types treated
+ identically by the notes & bibliography style and the author-date
+ styles (itself a formatting quirk). You can also look at the
+ sample files legal-test.bib and cms-legal-sample.pdf to see how you
+ might construct your database entries. Support for Bluebook
+ citations is in its infancy, so if you have ideas for sorting out
+ its complexities more elegantly or spot any inaccuracies then I
+ would be happy to hear about it. The implementation is intended
+ mainly for American documents, but there is some rudimentary
+ localization for the other languages supported by biblatex-chicago.
+ The actual citations in such contexts would, let it be noted, fall
+ outside of the Bluebook spec.
+
+ - I am grateful to Gustavo Barros for providing a Brazilian
+ Portuguese localization for biblatex-chicago, contained in the
+ cms-brazilian.lbx file.
+
+ - Gustavo also pointed out a couple of instances where the package's
+ \bibstrings couldn't accommodate the needs of his localization, so
+ with his help I've split the "recorded" string into "discrecorded"
+ and "songrecorded", then added it to all the .lbx files. I've also
+ added two new \bibstrings for the "lista" field format: "subverbo"
+ and "subverbis". I've added them to all the .lbx files, but only
+ cms-brazilian.lbx differs from the default. If other languages
+ need this change please let me know.
+
+ - The same user also suggested a fix to Patent entries: removing the
+ comma from between the dates when the language doesn't use a comma
+ in lists.
+
+ - Timo Thoms pointed out some annoying inconsistencies when using the
+ hyperref package with the author-date styles, and I have attempted
+ to rectify them. In citations, only the "date" portion should act
+ as a link, if there is a "date", otherwise a "title" or perhaps a
+ "shorthand" will link to the entry in the list of references. If
+ you have entries that you believe should present hyperlinks but
+ don't, you can try setting the new "hypertitle" option in their
+ "options" fields. Alternately, you can set the option to "true"
+ globally in the preamble and then "titles" and "shorthands" will
+ serve as links whether there's a "date" or not. Cf. section 5.4.3
+ in biblatex-chicago.pdf.
+
+ - Bertold Schweitzer requested that the styles allow using the string
+ "forthcoming" in the "pubstate" field to present sources that are
+ yet to be published. This is now supported in all styles, and has
+ the additional benefit of rendering recourse to the \autocap
+ command unnecessary, as the styles print \bibstring{forthcoming}
+ where the "year" would normally appear. Using the "year" field
+ itself is, of course, still supported too.
+
+ - The same user requested that I allow "newspaper" as an exact
+ synonym of "magazine" in the "entrysubtype" field of Article,
+ Review, Periodical, and Suppperiodical entries. I have provided
+ this in all styles, and whereever you see "magazine" in the
+ documentation then "newspaper" will work in exactly the same way.
+
+ - Bertold also suggested that, following the example of Philip Kime's
+ biblatex-apa package, I support the use of "related" functionality
+ when presenting reviews, so that you can, for example, easily
+ present multiple reviews of the same item. I have provided this
+ functionality in all styles. To enable it you'll need to set the
+ "relatedtype" field to "reviewof" in Article, Review, or
+ Suppperiodical types. You should also read the documentation in
+ section 4.2.1 or 5.2.1 in biblatex-chicago.pdf, as this
+ "relatedtype" works somewhat differently from the others. The
+ standard, manual way of citing such works remains, of course,
+ available.
+
+ - Jan David Hauck suggested that there was a need for an
+ "unpublished" "entrysubtype" to the Report type, which would
+ present the "title" in quotation marks (or plain roman in
+ authordate-trad) instead of italics. I can't quite tell if the
+ Manual agrees, but I have fulfilled this request in all styles.
+
+ - The same user pointed out that standard biblatex and the discussion
+ in the Manual both suggest providing "venue", "eventdate",
+ "eventtitle", and "eventtitleaddon" fields for the Unpublished
+ type, thereby allowing for the further specification of unpublished
+ conference papers and the like. I have added these fields in all
+ styles.
+
+ - At the request of N. Andrew Walsh, the notes & bibliography style
+ now offers a way to disambiguate references to different sources
+ which would ordinarily produce identical short notes, that is,
+ where the "author" and "labeltitle" are the same. Biblatex's
+ "uniquework" option is now active by default, and biblatex-chicago
+ provides three new user options, one for choosing a disambiguating
+ field, one for setting the punctuation between that field and the
+ rest of the short note, and one for formatting the field using
+ parentheses or square brackets -- "shortextrafield",
+ "shortextrapunct", and "shortextraformat", respectively. Please
+ see section 4.4.3 in biblatex-chicago.pdf for the details, and note
+ that "shortextrafield" has to be set for the mechanism to print
+ anything at all.
+
+ - User Pétùr spotted two long-standing bugs: first, that the
+ "url=false" option didn't stop the printing of the "urldate", and
+ second that empty parentheses would appear in some circumstances
+ around non-existent "dates" in the author-date styles. I have
+ fixed both.
+
+ - Philipp Immel wondered whether I could address a long-standing bug
+ when presenting a "subtitle" after a "title" that ends in an
+ exclamation point or question mark. This bug has existed since the
+ first release of the 16th-edition styles, and I think I've finally
+ solved it now (after the release of the Manual's 17th edition).
+
+
Release notes for version 1.0rc4 [2017-05-02]:
Another bug-fix release.
@@ -1577,7 +1721,7 @@ Changelog for version 0.7 [2008-08-18]:
- First public release
-Copyright (c) 2008-2016 David Fussner. This package is
+Copyright (c) 2008-2018 David Fussner. This package is
author-maintained. This work may be copied, distributed and/or
modified under the conditions of the LaTeX Project Public License,
either version 1.3 of this license or (at your option) any later