biblatex-unified (26may20)

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

14 files changed, 2695 insertions, 1 deletions

diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/JournalUnifiedStyleSheet2007.pdf b/Master/texmf-dist/doc/latex/biblatex-unified/JournalUnifiedStyleSheet2007.pdf
new file mode 100644
index 00000000000..d84027cce8b
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/JournalUnifiedStyleSheet2007.pdf
diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/LICENSE b/Master/texmf-dist/doc/latex/biblatex-unified/LICENSE
new file mode 100644
index 00000000000..f8b699e6eb5
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/LICENSE
@@ -0,0 +1,415 @@
+The LaTeX Project Public License
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+
+LPPL Version 1.3c  2008-05-04
+
+Copyright 1999 2002-2008 LaTeX3 Project
+    Everyone is allowed to distribute verbatim copies of this
+    license document, but modification of it is not allowed.
+
+
+PREAMBLE
+========
+
+The LaTeX Project Public License (LPPL) is the primary license under
+which the LaTeX kernel and the base LaTeX packages are distributed.
+
+You may use this license for any work of which you hold the copyright
+and which you wish to distribute.  This license may be particularly
+suitable if your work is TeX-related (such as a LaTeX package), but
+it is written in such a way that you can use it even if your work is
+unrelated to TeX.
+
+The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+below, gives instructions, examples, and recommendations for authors
+who are considering distributing their works under this license.
+
+This license gives conditions under which a work may be distributed
+and modified, as well as conditions under which modified versions of
+that work may be distributed.
+
+We, the LaTeX3 Project, believe that the conditions below give you
+the freedom to make and distribute modified versions of your work
+that conform with whatever technical specifications you wish while
+maintaining the availability, integrity, and reliability of
+that work.  If you do not see how to achieve your goal while
+meeting these conditions, then read the document `cfgguide.tex'
+and `modguide.tex' in the base LaTeX distribution for suggestions.
+
+
+DEFINITIONS
+===========
+
+In this license document the following terms are used:
+
+   `Work'
+    Any work being distributed under this License.
+
+   `Derived Work'
+    Any work that under any applicable law is derived from the Work.
+
+   `Modification'
+    Any procedure that produces a Derived Work under any applicable
+    law -- for example, the production of a file containing an
+    original file associated with the Work or a significant portion of
+    such a file, either verbatim or with modifications and/or
+    translated into another language.
+
+   `Modify'
+    To apply any procedure that produces a Derived Work under any
+    applicable law.
+
+   `Distribution'
+    Making copies of the Work available from one person to another, in
+    whole or in part.  Distribution includes (but is not limited to)
+    making any electronic components of the Work accessible by
+    file transfer protocols such as FTP or HTTP or by shared file
+    systems such as Sun's Network File System (NFS).
+
+   `Compiled Work'
+    A version of the Work that has been processed into a form where it
+    is directly usable on a computer system.  This processing may
+    include using installation facilities provided by the Work,
+    transformations of the Work, copying of components of the Work, or
+    other activities.  Note that modification of any installation
+    facilities provided by the Work constitutes modification of the Work.
+
+   `Current Maintainer'
+    A person or persons nominated as such within the Work.  If there is
+    no such explicit nomination then it is the `Copyright Holder' under
+    any applicable law.
+
+   `Base Interpreter'
+    A program or process that is normally needed for running or
+    interpreting a part or the whole of the Work.
+
+    A Base Interpreter may depend on external components but these
+    are not considered part of the Base Interpreter provided that each
+    external component clearly identifies itself whenever it is used
+    interactively.  Unless explicitly specified when applying the
+    license to the Work, the only applicable Base Interpreter is a
+    `LaTeX-Format' or in the case of files belonging to the
+    `LaTeX-format' a program implementing the `TeX language'.
+
+
+
+CONDITIONS ON DISTRIBUTION AND MODIFICATION
+===========================================
+
+1.  Activities other than distribution and/or modification of the Work
+are not covered by this license; they are outside its scope.  In
+particular, the act of running the Work is not restricted and no
+requirements are made concerning any offers of support for the Work.
+
+2.  You may distribute a complete, unmodified copy of the Work as you
+received it.  Distribution of only part of the Work is considered
+modification of the Work, and no right to distribute such a Derived
+Work may be assumed under the terms of this clause.
+
+3.  You may distribute a Compiled Work that has been generated from a
+complete, unmodified copy of the Work as distributed under Clause 2
+above, as long as that Compiled Work is distributed in such a way that
+the recipients may install the Compiled Work on their system exactly
+as it would have been installed if they generated a Compiled Work
+directly from the Work.
+
+4.  If you are the Current Maintainer of the Work, you may, without
+restriction, modify the Work, thus creating a Derived Work.  You may
+also distribute the Derived Work without restriction, including
+Compiled Works generated from the Derived Work.  Derived Works
+distributed in this manner by the Current Maintainer are considered to
+be updated versions of the Work.
+
+5.  If you are not the Current Maintainer of the Work, you may modify
+your copy of the Work, thus creating a Derived Work based on the Work,
+and compile this Derived Work, thus creating a Compiled Work based on
+the Derived Work.
+
+6.  If you are not the Current Maintainer of the Work, you may
+distribute a Derived Work provided the following conditions are met
+for every component of the Work unless that component clearly states
+in the copyright notice that it is exempt from that condition.  Only
+the Current Maintainer is allowed to add such statements of exemption
+to a component of the Work.
+
+  a. If a component of this Derived Work can be a direct replacement
+     for a component of the Work when that component is used with the
+     Base Interpreter, then, wherever this component of the Work
+     identifies itself to the user when used interactively with that
+     Base Interpreter, the replacement component of this Derived Work
+     clearly and unambiguously identifies itself as a modified version
+     of this component to the user when used interactively with that
+     Base Interpreter.
+
+  b. Every component of the Derived Work contains prominent notices
+     detailing the nature of the changes to that component, or a
+     prominent reference to another file that is distributed as part
+     of the Derived Work and that contains a complete and accurate log
+     of the changes.
+
+  c. No information in the Derived Work implies that any persons,
+     including (but not limited to) the authors of the original version
+     of the Work, provide any support, including (but not limited to)
+     the reporting and handling of errors, to recipients of the
+     Derived Work unless those persons have stated explicitly that
+     they do provide such support for the Derived Work.
+
+  d. You distribute at least one of the following with the Derived Work:
+
+       1. A complete, unmodified copy of the Work;
+          if your distribution of a modified component is made by
+          offering access to copy the modified component from a
+          designated place, then offering equivalent access to copy
+          the Work from the same or some similar place meets this
+          condition, even though third parties are not compelled to
+          copy the Work along with the modified component;
+
+       2. Information that is sufficient to obtain a complete,
+          unmodified copy of the Work.
+
+7.  If you are not the Current Maintainer of the Work, you may
+distribute a Compiled Work generated from a Derived Work, as long as
+the Derived Work is distributed to all recipients of the Compiled
+Work, and as long as the conditions of Clause 6, above, are met with
+regard to the Derived Work.
+
+8.  The conditions above are not intended to prohibit, and hence do not
+apply to, the modification, by any method, of any component so that it
+becomes identical to an updated version of that component of the Work as
+it is distributed by the Current Maintainer under Clause 4, above.
+
+9.  Distribution of the Work or any Derived Work in an alternative
+format, where the Work or that Derived Work (in whole or in part) is
+then produced by applying some process to that format, does not relax or
+nullify any sections of this license as they pertain to the results of
+applying that process.
+
+10. a. A Derived Work may be distributed under a different license
+       provided that license itself honors the conditions listed in
+       Clause 6 above, in regard to the Work, though it does not have
+       to honor the rest of the conditions in this license.
+
+    b. If a Derived Work is distributed under a different license, that
+       Derived Work must provide sufficient documentation as part of
+       itself to allow each recipient of that Derived Work to honor the
+       restrictions in Clause 6 above, concerning changes from the Work.
+
+11. This license places no restrictions on works that are unrelated to
+the Work, nor does this license place any restrictions on aggregating
+such works with the Work by any means.
+
+12.  Nothing in this license is intended to, or may be used to, prevent
+complete compliance by all parties with all applicable laws.
+
+
+NO WARRANTY
+===========
+
+There is no warranty for the Work.  Except when otherwise stated in
+writing, the Copyright Holder provides the Work `as is', without
+warranty of any kind, either expressed or implied, including, but not
+limited to, the implied warranties of merchantability and fitness for a
+particular purpose.  The entire risk as to the quality and performance
+of the Work is with you.  Should the Work prove defective, you assume
+the cost of all necessary servicing, repair, or correction.
+
+In no event unless required by applicable law or agreed to in writing
+will The Copyright Holder, or any author named in the components of the
+Work, or any other party who may distribute and/or modify the Work as
+permitted above, be liable to you for damages, including any general,
+special, incidental or consequential damages arising out of any use of
+the Work or out of inability to use the Work (including, but not limited
+to, loss of data, data being rendered inaccurate, or losses sustained by
+anyone as a result of any failure of the Work to operate with any other
+programs), even if the Copyright Holder or said author or said other
+party has been advised of the possibility of such damages.
+
+
+MAINTENANCE OF THE WORK
+=======================
+
+The Work has the status `author-maintained' if the Copyright Holder
+explicitly and prominently states near the primary copyright notice in
+the Work that the Work can only be maintained by the Copyright Holder
+or simply that it is `author-maintained'.
+
+The Work has the status `maintained' if there is a Current Maintainer
+who has indicated in the Work that they are willing to receive error
+reports for the Work (for example, by supplying a valid e-mail
+address). It is not required for the Current Maintainer to acknowledge
+or act upon these error reports.
+
+The Work changes from status `maintained' to `unmaintained' if there
+is no Current Maintainer, or the person stated to be Current
+Maintainer of the work cannot be reached through the indicated means
+of communication for a period of six months, and there are no other
+significant signs of active maintenance.
+
+You can become the Current Maintainer of the Work by agreement with
+any existing Current Maintainer to take over this role.
+
+If the Work is unmaintained, you can become the Current Maintainer of
+the Work through the following steps:
+
+ 1.  Make a reasonable attempt to trace the Current Maintainer (and
+     the Copyright Holder, if the two differ) through the means of
+     an Internet or similar search.
+
+ 2.  If this search is successful, then enquire whether the Work
+     is still maintained.
+
+  a. If it is being maintained, then ask the Current Maintainer
+     to update their communication data within one month.
+
+  b. If the search is unsuccessful or no action to resume active
+     maintenance is taken by the Current Maintainer, then announce
+     within the pertinent community your intention to take over
+     maintenance.  (If the Work is a LaTeX work, this could be
+     done, for example, by posting to comp.text.tex.)
+
+ 3a. If the Current Maintainer is reachable and agrees to pass
+     maintenance of the Work to you, then this takes effect
+     immediately upon announcement.
+
+  b. If the Current Maintainer is not reachable and the Copyright
+     Holder agrees that maintenance of the Work be passed to you,
+     then this takes effect immediately upon announcement.
+
+ 4.  If you make an `intention announcement' as described in 2b. above
+     and after three months your intention is challenged neither by
+     the Current Maintainer nor by the Copyright Holder nor by other
+     people, then you may arrange for the Work to be changed so as
+     to name you as the (new) Current Maintainer.
+
+ 5.  If the previously unreachable Current Maintainer becomes
+     reachable once more within three months of a change completed
+     under the terms of 3b) or 4), then that Current Maintainer must
+     become or remain the Current Maintainer upon request provided
+     they then update their communication data within one month.
+
+A change in the Current Maintainer does not, of itself, alter the fact
+that the Work is distributed under the LPPL license.
+
+If you become the Current Maintainer of the Work, you should
+immediately provide, within the Work, a prominent and unambiguous
+statement of your status as Current Maintainer.  You should also
+announce your new status to the same pertinent community as
+in 2b) above.
+
+
+WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+======================================================
+
+This section contains important instructions, examples, and
+recommendations for authors who are considering distributing their
+works under this license.  These authors are addressed as `you' in
+this section.
+
+Choosing This License or Another License
+----------------------------------------
+
+If for any part of your work you want or need to use *distribution*
+conditions that differ significantly from those in this license, then
+do not refer to this license anywhere in your work but, instead,
+distribute your work under a different license.  You may use the text
+of this license as a model for your own license, but your license
+should not refer to the LPPL or otherwise give the impression that
+your work is distributed under the LPPL.
+
+The document `modguide.tex' in the base LaTeX distribution explains
+the motivation behind the conditions of this license.  It explains,
+for example, why distributing LaTeX under the GNU General Public
+License (GPL) was considered inappropriate.  Even if your work is
+unrelated to LaTeX, the discussion in `modguide.tex' may still be
+relevant, and authors intending to distribute their works under any
+license are encouraged to read it.
+
+A Recommendation on Modification Without Distribution
+-----------------------------------------------------
+
+It is wise never to modify a component of the Work, even for your own
+personal use, without also meeting the above conditions for
+distributing the modified component.  While you might intend that such
+modifications will never be distributed, often this will happen by
+accident -- you may forget that you have modified that component; or
+it may not occur to you when allowing others to access the modified
+version that you are thus distributing it and violating the conditions
+of this license in ways that could have legal implications and, worse,
+cause problems for the community.  It is therefore usually in your
+best interest to keep your copy of the Work identical with the public
+one.  Many works provide ways to control the behavior of that work
+without altering any of its licensed components.
+
+How to Use This License
+-----------------------
+
+To use this license, place in each of the components of your work both
+an explicit copyright notice including your name and the year the work
+was authored and/or last substantially modified.  Include also a
+statement that the distribution and/or modification of that
+component is constrained by the conditions in this license.
+
+Here is an example of such a notice and statement:
+
+  %% pig.dtx
+  %% Copyright 2005 M. Y. Name
+  %
+  % This work may be 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 version.
+  % The latest version of this license is in
+  %   http://www.latex-project.org/lppl.txt
+  % and version 1.3 or later is part of all distributions of LaTeX
+  % version 2005/12/01 or later.
+  %
+  % This work has the LPPL maintenance status `maintained'.
+  %
+  % The Current Maintainer of this work is M. Y. Name.
+  %
+  % This work consists of the files pig.dtx and pig.ins
+  % and the derived file pig.sty.
+
+Given such a notice and statement in a file, the conditions
+given in this license document would apply, with the `Work' referring
+to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+referring to any `LaTeX-Format', and both `Copyright Holder' and
+`Current Maintainer' referring to the person `M. Y. Name'.
+
+If you do not want the Maintenance section of LPPL to apply to your
+Work, change `maintained' above into `author-maintained'.
+However, we recommend that you use `maintained', as the Maintenance
+section was added in order to ensure that your Work remains useful to
+the community even when you can no longer maintain and support it
+yourself.
+
+Derived Works That Are Not Replacements
+---------------------------------------
+
+Several clauses of the LPPL specify means to provide reliability and
+stability for the user community. They therefore concern themselves
+with the case that a Derived Work is intended to be used as a
+(compatible or incompatible) replacement of the original Work. If
+this is not the case (e.g., if a few lines of code are reused for a
+completely different task), then clauses 6b and 6d shall not apply.
+
+
+Important Recommendations
+-------------------------
+
+ Defining What Constitutes the Work
+
+   The LPPL requires that distributions of the Work contain all the
+   files of the Work.  It is therefore important that you provide a
+   way for the licensee to determine which files constitute the Work.
+   This could, for example, be achieved by explicitly listing all the
+   files of the Work near the copyright notice of each file or by
+   using a line such as:
+
+    % This work consists of all files listed in manifest.txt.
+
+   in that place.  In the absence of an unequivocal list it might be
+   impossible for the licensee to determine what is considered by you
+   to comprise the Work and, in such a case, the licensee would be
+   entitled to make reasonable conjectures as to which files comprise
+   the Work.
diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/README.md b/Master/texmf-dist/doc/latex/biblatex-unified/README.md
new file mode 100644
index 00000000000..b4398c09633
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/README.md
@@ -0,0 +1,79 @@
+biblatex-unified
+================
+
+`biblatex-unified` is an opinionated biblatex implementation of the [Unified Stylesheet for Linguistics Journal](https://www.linguisticsociety.org/resource/unified-style-sheet). The stylesheet was developed by [CELxJ, the Committee of Editors of Linguistics Journals](https://www.linguisticsociety.org/about/who-we-are/committees/editors-linguistics-journals-celxj). 
+
+The first implementation of the stylesheet for LaTeX was [`sp.bst`](https://raw.githubusercontent.com/semprag/tex/master/sp.cls), developed for the house-style of the journal [*Semantics and Pragmatics*](http://semprag.org) (*S&P*). Bridget Samuels produced a revised version `unified.bst`, which has largely disappeared from the internet.
+
+The current project is a ground-up re-implementation of the unified stylesheet in modern biblatex. It has been used by *S&P* in production for several years.
+
+Please [file an issue at github](https://github.com/semprag/biblatex-sp-unified/issues/new) to let us know of any problems you encounter and any recommendations for improvement.
+
+
+## Sources
+
+The `biblatex-unified` style consists of two files:
+
+* [`unified.bbx`](unified.bbx) -- for formatting the bibliography.
+* [`unified.cbx`](unified.cbx) -- for formatting in-text citations in the style of *S&P*.
+  - Since the Unified Stylesheet does not give any guidelines for in-text citations, this file is optional and users can choose other citation styles, such as the `authoryear-comp` citation style that comes with biblatex.
+
+
+## Requirements and backward compatibility
+
+Compiling LaTeX documents with this style depends on a fairly recent TeX installation that includes biblatex 2.0+. It is tested only with the `biber` backend. TexLive 2019 or later would be ideal.
+
+
+## Installation
+
+Manual installation involves putting the two files `unified.bbx` and `unified.cbx` somewhere where your TeX system can find them. This could be local in the same directory as your tex source file, or in your `TEXMF` "home" directory, or in the system `TEXMF` directories. 
+
+
+## Configuring your `.tex` document to use the style
+
+To use the style in conjunction with *S&P*'s [`sp.cls`](https://raw.githubusercontent.com/semprag/tex/master/sp.cls),
+simply add the `biblatex` class option when importing `sp.cls`:
+
+```latex
+    \documentclass[biblatex]{sp}
+```
+
+If you are not using the *S&P* document class, you can still use this style by adding the following to your preamble (after `\documentclass{...}` but before `\begin{document}`):
+
+```latex
+    \usepackage[backend=biber,
+                style=unified,
+                maxcitenames=3,
+                maxbibnames=99]{biblatex}
+```
+
+If you were previously using `natbib`, remove `\usepackage{natbib}` and any accompanying `\bibliographystyle{...}` and `\bibpunct{...}` settings.
+You might also find it helpful to add `natbib` to the list of options (`\usepackage[..., natbib]{biblatex}`), to load biblatex's `natbib` compatibility module, which implements common `natbib` commands like `\citet`, `\citep`, `\citealt`, `\citealp`, etc.
+
+Whether you're using `sp.cls` or a different document class, you'll need to change the usual BibTeX commands to biblatex, in two places:
+
+1. Replace the `\bibliography{your-bibfile}` line in the backmatter with `\printbibliography`.
+2. Add the following command to your preamble:  
+   `\addbibresource{your-bibfile.bib}`
+   - NB: the `.bib` extension must be included (unlike BibTeX)
+
+## Documentation
+
+The full documentation and implementation notes can be found in [`biblatex-unified.pdf`](biblatex-unified.pdf). The PDF can be regenerated by typesetting the `tex` source file with `xelatex`. The `tex` is actually itself generated from the underlying `md` markdown file via `pandoc` with the following incantation:
+
+```zsh
+pandoc -f markdown -t latex biblatex-unified.md -s\ 
+-o biblatex-unified.tex --highlight-style=kate
+```
+
+## License and copyright
+
+Copyright ©2020 Kai von Fintel. 
+
+This package is author-maintained. Permission is granted to copy, distribute
+and/or modify this software under the terms of the LaTeX Project Public License,
+version 1.3c. 
+
+This software is provided “as is,” without warranty of any kind, either
+expressed or implied, including, but not limited to, the implied warranties of
+merchantability and fitness for a particular purpose.
diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.md b/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.md
new file mode 100644
index 00000000000..e9bdf190817
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.md
@@ -0,0 +1,266 @@
+---
+title: biblatex-unified
+author: Kai von Fintel (fintel@mit.edu)
+date: 2020-05-25
+colorlinks: true
+numbersections: true
+...
+
+# Introduction and Usage
+
+`biblatex-unified` is an opinionated biblatex implementation of the [Unified Stylesheet for Linguistics Journal](https://www.linguisticsociety.org/resource/unified-style-sheet). The stylesheet was developed by [CELxJ, the Committee of Editors of Linguistics Journals](https://www.linguisticsociety.org/about/who-we-are/committees/editors-linguistics-journals-celxj). 
+
+The first implementation of the stylesheet for LaTeX was [`sp.bst`](https://raw.githubusercontent.com/semprag/tex/master/sp.cls), developed for the house-style of the journal [*Semantics and Pragmatics*](http://semprag.org) (*S&P*). Bridget Samuels produced a revised version `unified.bst`, which has largely disappeared from the internet.
+
+The current project is a ground-up re-implementation of the unified stylesheet in modern biblatex. It has been used by *S&P* in production for several years.
+
+Please [file an issue at github](https://github.com/semprag/biblatex-sp-unified/issues/new) to let us know of any problems you encounter and any recommendations for improvement.
+
+
+## Sources
+
+The `biblatex-unified` style consists of two files:
+
+* [`unified.bbx`{.latex}](unified.bbx) -- for formatting the bibliography.
+* [`unified.cbx`{.latex}](unified.cbx) -- for formatting in-text citations in the style of *S&P*.
+  - Since the Unified Stylesheet does not give any guidelines for in-text citations, this file is optional and users can choose other citation styles, such as the `authoryear-comp` citation style that comes with biblatex.
+
+
+## Requirements and backward compatibility
+
+Compiling LaTeX documents with this style depends on a fairly recent TeX installation that includes biblatex 2.0+. It is tested only with the `biber` backend. TexLive 2019 or later would be ideal.
+
+
+## Installation
+
+Manual installation involves putting the two files `unified.bbx` and `unified.cbx` somewhere where your TeX system can find them. This could be local in the same directory as your tex source file, or in your `TEXMF` "home" directory, or in the system `TEXMF` directories. 
+
+
+## Configuring your `.tex` document to use the style
+
+To use the style in conjunction with *S&P*'s [`sp.cls`{.latex}](https://raw.githubusercontent.com/semprag/tex/master/sp.cls),
+simply add the `biblatex` class option when importing `sp.cls`{.latex}:
+
+```latex
+    \documentclass[biblatex]{sp}
+```
+
+If you are not using the *S&P* document class, you can still use this style by adding the following to your preamble (after `\documentclass{...}`{.latex} but before `\begin{document}`{.latex}):
+
+```latex
+    \usepackage[backend=biber,
+                style=unified,
+                maxcitenames=3,
+                maxbibnames=99]{biblatex}
+```
+
+If you were previously using `natbib`{.latex}, remove `\usepackage{natbib}`{.latex} and any accompanying `\bibliographystyle{...}`{.latex} and `\bibpunct{...}`{.latex} settings.
+You might also find it helpful to add `natbib`{.latex} to the list of options (`\usepackage[..., natbib]{biblatex}`{.latex}), to load biblatex's `natbib`{.latex} compatibility module, which implements common `natbib`{.latex} commands like `\citet`{.latex}, `\citep`{.latex}, `\citealt`{.latex}, `\citealp`{.latex}, etc.
+
+Whether you're using `sp.cls` or a different document class, you'll need to change the usual BibTeX commands to biblatex, in two places:
+
+1. Replace the `\bibliography{your-bibfile}`{.latex} line in the backmatter with `\printbibliography`{.latex}.
+2. Add the following command to your preamble:  
+   `\addbibresource{your-bibfile.bib}`{.latex}
+   - NB: the `.bib`{.latex} extension must be included (unlike BibTeX)
+
+
+## Testing
+
+Testing consists of rendering `unified-test.tex`{.latex} (and `unified-test.bib`{.latex}) into a PDF, comparing the result to the sample bibliography in the Unified Stylesheet guidelines.
+
+
+## Producing the documentation
+
+The documentation consists of the `README.md`{.zsh} file and this PDF. The PDF can be regenerated by typesetting the `tex`{.zsh} source file with `xelatex`{.zsh}. The `tex`{.zsh} is actually itself generated from the underlying `md`{.zsh} markdown file via `pandoc`{.zsh} with the following incantation:
+
+```zsh
+pandoc -f markdown -t latex biblatex-unified.md -s\ 
+-o biblatex-unified.tex --highlight-style=kate
+```
+
+# Implementation notes
+
+`biblatex-unified` is meant to implement as fully as possible the [Unified Style Sheet for Linguistics Journals](http://celxj.org/downloads/UnifiedStyleSheet.pdf), which consists of a number of guidelines and thoughts on the formatting of bibliographies, a sample bibliography and some comments on that sample. 
+
+The `biblatex-unified` distribution includes a copy of the Unified Style Sheet and a bib-file that corresponds to the references typeset in the Style Sheet specifications. So, this bib-file can be used to test the implementation of the Style Sheet. We include the source code of the test LaTeX file and the resulting pdf to demonstrate that we have faithfully implemented the Style Sheet, with some minor differences.
+
+When it comes to implementing the guidelines in a LaTeX typesetting environment, most of the guidelines can be implemented in the bibliography style (a bst file for BibTex or a bbx file for biblatex), but there are some points that need to be taken into account earlier in the preparation of the bib file containing the bibliographic details for the references to be listed.
+
+Here is a point by point copy of the Unified Style Sheet guidelines, followed by commentary on our implementation.
+
+>1\. **Superfluous font-styles should be omitted.** Do not use small caps for author/editor names, since they do not help to distinguish these from any other bits of information in the citation. In contrast, italics are worthwhile for distinguishing volume (book, journal, dissertation) titles [+ital] from article and chapter titles [-ital].
+
+>2\. **Superfluous punctuation should be left out.** Once italic is adopted to distinguish volumes from articles/chapters (as above), then single or double quotations around article titles are superfluous and only add visual clutter.
+
+`biblatex-unified`: Article and chapter titles are set in roman font, while titles of books, dissertations, and journals are set in italics. There are no quotation marks around titles.
+
+>3\. **Differing capitalization styles should be used to make category distinctions.** Use capitalization of all lexical words for journal titles and capitalize only the first word (plus proper names and the first word after a colon) for book/dissertation titles and article/chapter titles. This is a useful diagnostic for discriminating between titles that are recurring and those that are not. The journal style for capitalization should also be applied to the title of book series. Thus, the citation of a SNLLT volume would be punctuated: *Objects and other subjects: Grammatical functions, functional categories, and configurationality* (Studies in Natural Language and Linguistic Theory 52).
+
+`biblatex-unified`: Recurring titles (i.e. titles of journals and book series) are set in title case (capitalization of all lexical words), while non-recurring titles (articles, chapters, books, dissertations) are set in sentence case (capitalize only the first word, plus proper names and the first word after a colon).
+
+NB: It is fairly easy to convert a title given in title case into sentence case. But the other way round is quite difficult. `biblatex-unified.bbx` depends on the bib file containing title case for those elements that should be set in title case. For those elements that will be set in sentence case, the bbx file will do the conversion to sentence case. Proper names (and the first word after a colon) need to be protected against that lower casing, so the bib-file should have `{...}` braces around those words. Please note that just putting `{}` around the first letter in words that should be capitalized is bad practice since it prevents proper kerning of the space between the first and second letter. Even worse practice is to "double wrap" a whole title in braces, which prevents any style file from setting the title in the style specified by its formatting philosophy.
+
+NB: It is to be encouraged that titles and subtitles be entered into separate fields in the bib entry. In that case, the bbx file will properly capitalize the first letter of the subtitle. So, the first of the following formats is preferred for use with the unified bbx style (but it has the disadvantage of not necessarily being compatible with other bibliography styles):
+
+Option 1
+
+    title = {Government and Binding Theory and the Minimalist Program},
+    subtitle = {Principles and Parameters in Syntactic Theory},
+
+Option 2
+
+    title = {Government and Binding Theory and the Minimalist Program:  
+            {Principles} and Parameters in Syntactic Theory},
+
+>4\. **All author/editor first names should be spelled out.** Not doing so only serves to make the citation less informative. Without full first names, the 20th century index for Language alone would conflate five different people as ‘J. Smith’, four as ‘J. Harris’, three each under ‘A. Cohen’ and ‘P. Lee’, two each under ‘R. Kent’, ‘J. Anderson’, ‘H. Klein’ and ‘J. Klein’.
+
+`biblatex-unified`: The style does not abbreviate first names. Compliance with the Unified Style depends on the bib-file containing full names for everyone.
+
+>5\. **The ampersand is useful.** Use ampersand to distinguish higher and lower order conjuncts, i.e. [W & X] and [Y & Z], as in Culicover & Wilkins and Koster & May. It is relatively easy to see that reference is made here to two pairs of authors here (cf. Culicover and Wilkins and Koster and May).
+
+`biblatex-unified`: The style uses the ampersand rather than a final "and" in author and editor lists. This is taken care of by `biblatex-unified`.
+
+>6\. **Name repetitions are good.** While using a line ____ may save a little space, or a few characters, it also makes each such citation referentially dependent on an antecedent, and the effort of calculating such antecedents is more than what it saved typographically. Each citation should be internally complete.
+
+`biblatex-unified`: The style does not use a dashed line for repeated authors in the reference list.
+
+>7\. **Four digit year plus period only.** Extra parentheses are visual clutter and superfluous.
+
+`biblatex-unified`: The style complies with the Unified Style Sheet.
+
+>8\. **Commas and periods and other punctuation.** Separate citation components with periods (e.g., Author. Year. Title.) and subcomponents with commas (e.g., Author1, Author2 & Author3). Please note the ampersand (&), rather than the word “and” before the name of the last author, and no comma before the “&”. The use of the colon between title and subtitle and between place and publisher is traditional, but we do not use it between journal volumenumber and pagenumbers.
+
+`biblatex-unified`: The style complies with the Unified Style Sheet.
+
+>9\. **Parentheses around ed. makes sense.** Commas and periods should be used exclusively to separate citation components (e.g., "Author. Year."), or subcomponents (e.g. "author1, author2 & author3). Since "ed." is neither a component nor a subcomponent, but a modifier of a component, it should not be separated from the name by a comma:
+
+>    surname, firstname = author
+>    surname, firstname (ed.). = editor (NOT surname, firstname, ed.)
+>    surname, firstname & firstname surname (eds.) = editors
+
+`biblatex-unified`: The style complies with the Unified Style Sheet.
+
+>10\. **For conference proceedings, working papers, etc.** For conference proceedings published with an ISSN, treat the proceedings as a journal: Include both the full conference name and any commonly used acronym for the conference (BLS, WCCFL, etc.) in the journal title position. For proceedings not published with an ISSN, treat the proceedings as any other book, using the full title as listed on the front cover or title page. If the title (and subtitle if there is one) only includes an acronym for the conference name, expand the acronym in square brackets or parentheses following the acronym. If the title does not include an acronym which is commonly used for the conference name, include the acronym in square brackets or parentheses following the conference name. The advantage of including the acronym after the society title is that it makes the entry much more identifiable in a list of references.
+
+[From the comments by Joseph Salmons:]
+
+>Do not include “proceedings of the” or “papers from the”.
+
+NB: The examples included with the Unified Style Sheet do not include the editors of the CLS proceedings volume. We agree with this practice, since the names of editors of such proceedings are often hard to get hold of.
+
+`biblatex-unified`: These guidelines need to be satisfied in the construction of the bib-file. There are two approaches, one more of a hack than the other:
+
+*Option 1*: Use the `@inproceedings` entry type and include the ISSN of the proceedings when available. Example:
+
+    @inproceedings{casali:1998a,
+        Author = {Casali, Roderic F.},
+        Booktitle = {Chicago Linguistic Society (CLS)},
+        ISSN = {0577-7240},
+        Number = {1},
+        Pages = {55-68},
+        Title = {Predicting {ATR} Activity},
+        Volume = {34},
+        Year = {1998}}
+
+Comment: Following the Unified Style Sheet, we can let the presence of an ISSN control whether an article in conference proceedings is set like a journal article or like a book chapter. To do this, the bib-file needs to contain the ISSN of proceedings where possible. When the ISSN is in the bib-file, `biblatex-unified` will not print it with the entry but it will trigger setting as an article. If there's no ISSN in the entry, `biblatex-unified` will set it as a book chapter. The ISSN can be found through [WorldCat](http://www.worldcat.org) fairly easily. Here's a list of common conference proceedings with their ISSN:
+
+* BLS: 0363-2946
+* CLS: 0577-7240
+* NELS: 0883-5500
+* SALT: 2163-5951
+* WCCFL: 1042-1068
+
+*Option 2*: Another option, less portable and definitely a hack, is to use the `@article` entry type, putting the conference name (and the acronym in parentheses; no need to case protect the acronym, since journal titles are set as is) in the `journal` field, and do not list the editors. Example:
+
+    @article{casali:1998b,
+        Author = {Casali, Roderic F.},
+        Journal = {Chicago Linguistic Society (CLS)},
+        Number = {1},
+        Pages = {55-68},
+        Title = {Predicting {ATR} Activity},
+        Volume = {34},
+        Year = {1998}}
+
+>11\. **Use “edn.” as an abbreviation for “edition”, thus “2nd edn.”.** This avoids ambiguity and confusion with “ed.” (editor).
+
+`biblatex-unified`: The style complies with the Unified Style Sheet.
+
+>12\. **Names with “von”, “van”, “de”, etc.** If the "van" (or the "de" or other patronymic) is lower case and separated from the rest by a space (e.g. Elly van Gelderen), then alphabetize by the first upper-case element:
+
+>    `Gelderen, Elly van`
+
+>The addition of "see ..." in comprehensive indices and lists might be helpful for clarification:
+
+>    `van Gelderen, Elly (see Gelderen)`
+
+`biblatex-unified`: This is a point where we depart from the Unified Style Sheet. If the "van" (or the "de" or other patronymic) is lower case and separated from the rest by a space (e.g. Elly van Gelderen), then alphabetize by the first upper-case element **but display the particle as part of the last name in its usual position**:
+
+    `van Gelderen, Elly [alphabetized under "G"]`
+
+NB: biblatex-unified is the only biblatex style that we know of that implements this practice (it took some hacking to make this possible). There is no need to do anything in the bib-file to ensure proper treatment of "von" etc.
+
+>13\. **Names with “Jr.”, “IV.”, etc.** Following library practice, list elements such as “Jr.” as a subelement after names, separated by a comma.
+
+`biblatex-unified`: The style complies with the Unified Style Sheet.
+
+>14\. **Use “In” to designate chapters in collections.** This makes the book's format maximally similar to the standard citation format. This, in turn, would be time-saving when the author or the editor notice that more than one article is cited from a given collection and hence that that book’s details should be set out as a separate entry in the references (and the full details deleted from the articles’ entries).
+    author. year. chaptertitle. In editorname (ed.), collectiontitle, pagenumbers. publisher.
+
+`biblatex-unified`: The style complies with the Unified Style Sheet.
+
+>15\. **Journal volume numbers.** We favor: volumenumber(volumeissue). startingpage--endingpage. Thus: 22(1). 135-169. Note the space between volume number/issue and page numbers. Special formatting (e.g., bold for volume number) is superfluous. Issue numbers are a parenthetical modifier (cf. "ed." above) of the volume number. While it is not NECESSARY information for identifying the article, it is extremely USEFUL information.
+
+`biblatex-unified`: The style complies with the Unified Style Sheet. Providing issue numbers is a guideline for the preparation of the bib-file.
+
+>16\. **Dissertations/theses.** These conform to the already-widespread Place: Publisher format and fit readily into the rest of the standard: Cambridge, MA: MIT dissertation. Instead of archaic state abbreviations, use the official two-letter postal abbreviations. Note that national and other traditions vary in exactly what is labeled ‘thesis’ versus ‘dissertation’ and in distinguishing ‘PhD’ from ‘doctoral’ dissertations.
+    Cambridge, MA: MIT dissertation.
+    Chapel Hill: UNC MA thesis.
+
+`biblatex-unified`: The style complies with the Unified Style Sheet. Using the two-letter postal abbreviations is something that needs to be taken care of during the preparation of the bib-file.
+
+>17\. **On-line materials.** The basic information here -- author, date, title -- remains the same, and the URL where the resource was found takes the place of publisher or journal. We urge authors to include the date the material was accessed, in parentheses after the URL, since new versions often replace old ones. For a .pdf file, this would be the date of downloading, but for a resource like an on-line dictionary consulted repeatedly, a range of dates may be needed. For additional discussion of handling online citations, authors may want to consult this guide:
+
+>    Walker, Janice R. & Todd Taylor. 1998. The Columbia Guide to Online Style. New York: Columbia University Press.
+
+`biblatex-unified`: We take it that this does not refer to material that has officially been published online, in which case permanent document identifiers such as DOIs and the like will take care of the linking requirements. Rather, we are assuming this refers to "unpublished" material available online (on author's homepages or repositories such as the Semantics Archive or LingBuzz). In this case, just use the `@unpublished` entry-type, give the URL in the `url = {}` field, and if deemed necessary include the date the material was accessed by adding an `urldate = {}` field. The date should be given in YYYY-MM-DD format, e.g. `urldate = {2013-08-11}`. The style will then add the date in parentheses, formatted to the style sheet's rather odd format.
+
+
+# Departures from the Unified Style Sheet
+
+We already mentioned our one major disagreement with the Unified Style Sheet: the incorrect treatment of the "von" part of names.
+
+We depart from the style sheet only in a few other places. These are actually only departures from the example formatting given and do not pertain to any explicit guidelines.
+
+1. The acronym "CLS" given in parentheses after "Chicago Linguistic Society" in the Casali 1986 entry is not given in italics in the example. Since it is part of the "journal title" field, `biblatex-unified` will typeset it in italics.
+2. The example URLs have a period inside the parentheses around the URL access date. We have relocated this period to outside the parentheses.
+3. In the one case of an online journal article, the Pedersen 2005 entry, the example has a comma between the journal + volume and the URL. We think that this is analogous to the break between journal + volume(issue) and page numbers, and so it should be a period instead of a comma. That is what `biblatex-unified` does.
+4. There is a period between the URL and the URL access date (which is in parentheses). We do not think that this period should be there. `biblatex-unified` has a space.
+
+
+# Guidelines for the preparation of bib files
+
+For convenience, we repeat the best practices for preparing your bib file for use with `biblatex-unified`.
+
+1. Any words in the titles of articles, books, dissertations that should not be lowercased (other than the first word) have to be protected by {} brackets around that word (not just around the first letter of the word and never double wrap the entire title!). This includes the first word after a subtitle colon (unless the subtitle field is used instead).
+2. Give full first names for all authors and editors (all persons listed in the bib file).
+3. For conference proceedings, working papers, etc. For conference proceedings published with an ISSN, treat the proceedings as a journal: Include both the full conference name and any commonly used acronym for the conference (BLS, WCCFL, etc.) in the journal title position. Do not include the editors in the bib-file. For proceedings not published with an ISSN, treat the proceedings as any other book, using the full title as listed on the front cover or title page. If the title (and subtitle if there is one) only includes an acronym for the conference name, expand the acronym in square brackets or parentheses following the acronym. If the title does not include an acronym which is commonly used for the conference name, include the acronym in square brackets or parentheses following the conference name. The advantage of including the acronym after the society title is that it makes the entry much more identifiable in a list of references. Do not include “proceedings of the” or “papers from the”.
+4. For on-line materials, you can give the date the resource was accessed. Use the `urldate` field for this purpose and give the date in the YYYY-MM-DD format, e.g. `2013-08-11`.
+5. Use two-letter postal abbreviations for all US cities.
+
+
+# License and copyright
+
+Copyright ©2020 Kai von Fintel. 
+
+This package is author-maintained. Permission is granted to copy, distribute
+and/or modify this software under the terms of the LaTeX Project Public License,
+version 1.3c. 
+
+This software is provided “as is,” without warranty of any kind, either
+expressed or implied, including, but not limited to, the implied warranties of
+merchantability and fitness for a particular purpose.
+
+# Changelog and release notes
+
+**v1.00 (2020-05-25)** Initial CTAN release.
diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.pdf b/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.pdf
new file mode 100644
index 00000000000..f068ad0fc15
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.pdf
diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.tex b/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.tex
new file mode 100644
index 00000000000..815f1462675
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/biblatex-unified.tex
@@ -0,0 +1,752 @@
+% Options for packages loaded elsewhere
+\PassOptionsToPackage{unicode}{hyperref}
+\PassOptionsToPackage{hyphens}{url}
+\PassOptionsToPackage{dvipsnames,svgnames*,x11names*}{xcolor}
+%
+\documentclass[
+]{article}
+\usepackage{lmodern}
+\usepackage{amssymb,amsmath}
+\usepackage{ifxetex,ifluatex}
+\ifnum 0\ifxetex 1\fi\ifluatex 1\fi=0 % if pdftex
+  \usepackage[T1]{fontenc}
+  \usepackage[utf8]{inputenc}
+  \usepackage{textcomp} % provide euro and other symbols
+\else % if luatex or xetex
+  \usepackage{unicode-math}
+  \defaultfontfeatures{Scale=MatchLowercase}
+  \defaultfontfeatures[\rmfamily]{Ligatures=TeX,Scale=1}
+\fi
+% Use upquote if available, for straight quotes in verbatim environments
+\IfFileExists{upquote.sty}{\usepackage{upquote}}{}
+\IfFileExists{microtype.sty}{% use microtype if available
+  \usepackage[]{microtype}
+  \UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts
+}{}
+\makeatletter
+\@ifundefined{KOMAClassName}{% if non-KOMA class
+  \IfFileExists{parskip.sty}{%
+    \usepackage{parskip}
+  }{% else
+    \setlength{\parindent}{0pt}
+    \setlength{\parskip}{6pt plus 2pt minus 1pt}}
+}{% if KOMA class
+  \KOMAoptions{parskip=half}}
+\makeatother
+\usepackage{xcolor}
+\IfFileExists{xurl.sty}{\usepackage{xurl}}{} % add URL line breaks if available
+\IfFileExists{bookmark.sty}{\usepackage{bookmark}}{\usepackage{hyperref}}
+\hypersetup{
+  pdftitle={biblatex-unified},
+  pdfauthor={Kai von Fintel (fintel@mit.edu)},
+  colorlinks=true,
+  linkcolor=Maroon,
+  filecolor=Maroon,
+  citecolor=Blue,
+  urlcolor=Blue,
+  pdfcreator={LaTeX via pandoc}}
+\urlstyle{same} % disable monospaced font for URLs
+\usepackage{color}
+\usepackage{fancyvrb}
+\newcommand{\VerbBar}{|}
+\newcommand{\VERB}{\Verb[commandchars=\\\{\}]}
+\DefineVerbatimEnvironment{Highlighting}{Verbatim}{commandchars=\\\{\}}
+% Add ',fontsize=\small' for more characters per line
+\usepackage{framed}
+\definecolor{shadecolor}{RGB}{255,255,255}
+\newenvironment{Shaded}{\begin{snugshade}}{\end{snugshade}}
+\newcommand{\AlertTok}[1]{\textcolor[rgb]{0.75,0.01,0.01}{\textbf{\colorbox[rgb]{0.97,0.90,0.90}{#1}}}}
+\newcommand{\AnnotationTok}[1]{\textcolor[rgb]{0.79,0.38,0.79}{#1}}
+\newcommand{\AttributeTok}[1]{\textcolor[rgb]{0.00,0.34,0.68}{#1}}
+\newcommand{\BaseNTok}[1]{\textcolor[rgb]{0.69,0.50,0.00}{#1}}
+\newcommand{\BuiltInTok}[1]{\textcolor[rgb]{0.39,0.29,0.61}{\textbf{#1}}}
+\newcommand{\CharTok}[1]{\textcolor[rgb]{0.57,0.30,0.62}{#1}}
+\newcommand{\CommentTok}[1]{\textcolor[rgb]{0.54,0.53,0.53}{#1}}
+\newcommand{\CommentVarTok}[1]{\textcolor[rgb]{0.00,0.58,1.00}{#1}}
+\newcommand{\ConstantTok}[1]{\textcolor[rgb]{0.67,0.33,0.00}{#1}}
+\newcommand{\ControlFlowTok}[1]{\textcolor[rgb]{0.12,0.11,0.11}{\textbf{#1}}}
+\newcommand{\DataTypeTok}[1]{\textcolor[rgb]{0.00,0.34,0.68}{#1}}
+\newcommand{\DecValTok}[1]{\textcolor[rgb]{0.69,0.50,0.00}{#1}}
+\newcommand{\DocumentationTok}[1]{\textcolor[rgb]{0.38,0.47,0.50}{#1}}
+\newcommand{\ErrorTok}[1]{\textcolor[rgb]{0.75,0.01,0.01}{\underline{#1}}}
+\newcommand{\ExtensionTok}[1]{\textcolor[rgb]{0.00,0.58,1.00}{\textbf{#1}}}
+\newcommand{\FloatTok}[1]{\textcolor[rgb]{0.69,0.50,0.00}{#1}}
+\newcommand{\FunctionTok}[1]{\textcolor[rgb]{0.39,0.29,0.61}{#1}}
+\newcommand{\ImportTok}[1]{\textcolor[rgb]{1.00,0.33,0.00}{#1}}
+\newcommand{\InformationTok}[1]{\textcolor[rgb]{0.69,0.50,0.00}{#1}}
+\newcommand{\KeywordTok}[1]{\textcolor[rgb]{0.12,0.11,0.11}{\textbf{#1}}}
+\newcommand{\NormalTok}[1]{\textcolor[rgb]{0.12,0.11,0.11}{#1}}
+\newcommand{\OperatorTok}[1]{\textcolor[rgb]{0.12,0.11,0.11}{#1}}
+\newcommand{\OtherTok}[1]{\textcolor[rgb]{0.00,0.43,0.16}{#1}}
+\newcommand{\PreprocessorTok}[1]{\textcolor[rgb]{0.00,0.43,0.16}{#1}}
+\newcommand{\RegionMarkerTok}[1]{\textcolor[rgb]{0.00,0.34,0.68}{\colorbox[rgb]{0.88,0.91,0.97}{#1}}}
+\newcommand{\SpecialCharTok}[1]{\textcolor[rgb]{0.24,0.68,0.91}{#1}}
+\newcommand{\SpecialStringTok}[1]{\textcolor[rgb]{1.00,0.33,0.00}{#1}}
+\newcommand{\StringTok}[1]{\textcolor[rgb]{0.75,0.01,0.01}{#1}}
+\newcommand{\VariableTok}[1]{\textcolor[rgb]{0.00,0.34,0.68}{#1}}
+\newcommand{\VerbatimStringTok}[1]{\textcolor[rgb]{0.75,0.01,0.01}{#1}}
+\newcommand{\WarningTok}[1]{\textcolor[rgb]{0.75,0.01,0.01}{#1}}
+\setlength{\emergencystretch}{3em} % prevent overfull lines
+\providecommand{\tightlist}{%
+  \setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
+\setcounter{secnumdepth}{5}
+
+\title{biblatex-unified}
+\author{Kai von Fintel (fintel@mit.edu)}
+\date{2020-05-25}
+
+\begin{document}
+\maketitle
+
+\hypertarget{introduction-and-usage}{%
+\section{Introduction and Usage}\label{introduction-and-usage}}
+
+\texttt{biblatex-unified} is an opinionated biblatex implementation of
+the
+\href{https://www.linguisticsociety.org/resource/unified-style-sheet}{Unified
+Stylesheet for Linguistics Journal}. The stylesheet was developed by
+\href{https://www.linguisticsociety.org/about/who-we-are/committees/editors-linguistics-journals-celxj}{CELxJ,
+the Committee of Editors of Linguistics Journals}.
+
+The first implementation of the stylesheet for LaTeX was
+\href{https://raw.githubusercontent.com/semprag/tex/master/sp.cls}{\texttt{sp.bst}},
+developed for the house-style of the journal
+\href{http://semprag.org}{\emph{Semantics and Pragmatics}}
+(\emph{S\&P}). Bridget Samuels produced a revised version
+\texttt{unified.bst}, which has largely disappeared from the internet.
+
+The current project is a ground-up re-implementation of the unified
+stylesheet in modern biblatex. It has been used by \emph{S\&P} in
+production for several years.
+
+Please
+\href{https://github.com/semprag/biblatex-sp-unified/issues/new}{file an
+issue at github} to let us know of any problems you encounter and any
+recommendations for improvement.
+
+\hypertarget{sources}{%
+\subsection{Sources}\label{sources}}
+
+The \texttt{biblatex-unified} style consists of two files:
+
+\begin{itemize}
+\tightlist
+\item
+  \href{unified.bbx}{\VERB|\NormalTok{unified.bbx}|} -- for formatting
+  the bibliography.
+\item
+  \href{unified.cbx}{\VERB|\NormalTok{unified.cbx}|} -- for formatting
+  in-text citations in the style of \emph{S\&P}.
+
+  \begin{itemize}
+  \tightlist
+  \item
+    Since the Unified Stylesheet does not give any guidelines for
+    in-text citations, this file is optional and users can choose other
+    citation styles, such as the \texttt{authoryear-comp} citation style
+    that comes with biblatex.
+  \end{itemize}
+\end{itemize}
+
+\hypertarget{requirements-and-backward-compatibility}{%
+\subsection{Requirements and backward
+compatibility}\label{requirements-and-backward-compatibility}}
+
+Compiling LaTeX documents with this style depends on a fairly recent TeX
+installation that includes biblatex 2.0+. It is tested only with the
+\texttt{biber} backend. TexLive 2019 or later would be ideal.
+
+\hypertarget{installation}{%
+\subsection{Installation}\label{installation}}
+
+Manual installation involves putting the two files \texttt{unified.bbx}
+and \texttt{unified.cbx} somewhere where your TeX system can find them.
+This could be local in the same directory as your tex source file, or in
+your \texttt{TEXMF} ``home'' directory, or in the system \texttt{TEXMF}
+directories.
+
+\hypertarget{configuring-your-.tex-document-to-use-the-style}{%
+\subsection{\texorpdfstring{Configuring your \texttt{.tex} document to
+use the
+style}{Configuring your .tex document to use the style}}\label{configuring-your-.tex-document-to-use-the-style}}
+
+To use the style in conjunction with \emph{S\&P}'s
+\href{https://raw.githubusercontent.com/semprag/tex/master/sp.cls}{\VERB|\NormalTok{sp.cls}|},
+simply add the \texttt{biblatex} class option when importing
+\VERB|\NormalTok{sp.cls}|:
+
+\begin{Shaded}
+\begin{Highlighting}[]
+    \BuiltInTok{\textbackslash{}documentclass}\NormalTok{[biblatex]\{}\ExtensionTok{sp}\NormalTok{\}}
+\end{Highlighting}
+\end{Shaded}
+
+If you are not using the \emph{S\&P} document class, you can still use
+this style by adding the following to your preamble (after
+\VERB|\BuiltInTok{\textbackslash{}documentclass}\NormalTok{\{}\ExtensionTok{...}\NormalTok{\}}|
+but before
+\VERB|\KeywordTok{\textbackslash{}begin}\NormalTok{\{}\ExtensionTok{document}\NormalTok{\}}|):
+
+\begin{Shaded}
+\begin{Highlighting}[]
+    \BuiltInTok{\textbackslash{}usepackage}\NormalTok{[backend=biber,}
+\NormalTok{                style=unified,}
+\NormalTok{                maxcitenames=3,}
+\NormalTok{                maxbibnames=99]\{}\ExtensionTok{biblatex}\NormalTok{\}}
+\end{Highlighting}
+\end{Shaded}
+
+If you were previously using \VERB|\NormalTok{natbib}|, remove
+\VERB|\BuiltInTok{\textbackslash{}usepackage}\NormalTok{\{}\ExtensionTok{natbib}\NormalTok{\}}|
+and any accompanying
+\VERB|\BuiltInTok{\textbackslash{}bibliographystyle}\NormalTok{\{}\ExtensionTok{...}\NormalTok{\}}|
+and \VERB|\FunctionTok{\textbackslash{}bibpunct}\NormalTok{\{...\}}|
+settings. You might also find it helpful to add
+\VERB|\NormalTok{natbib}| to the list of options
+(\VERB|\BuiltInTok{\textbackslash{}usepackage}\NormalTok{[..., natbib]\{}\ExtensionTok{biblatex}\NormalTok{\}}|),
+to load biblatex's \VERB|\NormalTok{natbib}| compatibility module, which
+implements common \VERB|\NormalTok{natbib}| commands like
+\VERB|\KeywordTok{\textbackslash{}citet}|,
+\VERB|\KeywordTok{\textbackslash{}citep}|,
+\VERB|\FunctionTok{\textbackslash{}citealt}|,
+\VERB|\FunctionTok{\textbackslash{}citealp}|, etc.
+
+Whether you're using \texttt{sp.cls} or a different document class,
+you'll need to change the usual BibTeX commands to biblatex, in two
+places:
+
+\begin{enumerate}
+\def\labelenumi{\arabic{enumi}.}
+\tightlist
+\item
+  Replace the
+  \VERB|\BuiltInTok{\textbackslash{}bibliography}\NormalTok{\{}\ExtensionTok{your{-}bibfile}\NormalTok{\}}|
+  line in the backmatter with
+  \VERB|\FunctionTok{\textbackslash{}printbibliography}|.
+\item
+  Add the following command to your preamble:\\
+  \VERB|\FunctionTok{\textbackslash{}addbibresource}\NormalTok{\{your{-}bibfile.bib\}}|
+
+  \begin{itemize}
+  \tightlist
+  \item
+    NB: the \VERB|\NormalTok{.bib}| extension must be included (unlike
+    BibTeX)
+  \end{itemize}
+\end{enumerate}
+
+\hypertarget{testing}{%
+\subsection{Testing}\label{testing}}
+
+Testing consists of rendering \VERB|\NormalTok{unified{-}test.tex}| (and
+\VERB|\NormalTok{unified{-}test.bib}|) into a PDF, comparing the result
+to the sample bibliography in the Unified Stylesheet guidelines.
+
+\hypertarget{producing-the-documentation}{%
+\subsection{Producing the
+documentation}\label{producing-the-documentation}}
+
+The documentation consists of the \VERB|\NormalTok{README.md}| file and
+this PDF. The PDF can be regenerated by typesetting the
+\VERB|\NormalTok{tex}| source file with \VERB|\NormalTok{xelatex}|. The
+\VERB|\NormalTok{tex}| is actually itself generated from the underlying
+\VERB|\NormalTok{md}| markdown file via \VERB|\NormalTok{pandoc}| with
+the following incantation:
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\NormalTok{pandoc {-}f markdown {-}t latex biblatex{-}unified.md {-}s}\DataTypeTok{\textbackslash{} }
+\NormalTok{{-}o biblatex{-}unified.tex {-}{-}highlight{-}style=kate}
+\end{Highlighting}
+\end{Shaded}
+
+\hypertarget{implementation-notes}{%
+\section{Implementation notes}\label{implementation-notes}}
+
+\texttt{biblatex-unified} is meant to implement as fully as possible the
+\href{http://celxj.org/downloads/UnifiedStyleSheet.pdf}{Unified Style
+Sheet for Linguistics Journals}, which consists of a number of
+guidelines and thoughts on the formatting of bibliographies, a sample
+bibliography and some comments on that sample.
+
+The \texttt{biblatex-unified} distribution includes a copy of the
+Unified Style Sheet and a bib-file that corresponds to the references
+typeset in the Style Sheet specifications. So, this bib-file can be used
+to test the implementation of the Style Sheet. We include the source
+code of the test LaTeX file and the resulting pdf to demonstrate that we
+have faithfully implemented the Style Sheet, with some minor
+differences.
+
+When it comes to implementing the guidelines in a LaTeX typesetting
+environment, most of the guidelines can be implemented in the
+bibliography style (a bst file for BibTex or a bbx file for biblatex),
+but there are some points that need to be taken into account earlier in
+the preparation of the bib file containing the bibliographic details for
+the references to be listed.
+
+Here is a point by point copy of the Unified Style Sheet guidelines,
+followed by commentary on our implementation.
+
+\begin{quote}
+1. \textbf{Superfluous font-styles should be omitted.} Do not use small
+caps for author/editor names, since they do not help to distinguish
+these from any other bits of information in the citation. In contrast,
+italics are worthwhile for distinguishing volume (book, journal,
+dissertation) titles {[}+ital{]} from article and chapter titles
+{[}-ital{]}.
+\end{quote}
+
+\begin{quote}
+2. \textbf{Superfluous punctuation should be left out.} Once italic is
+adopted to distinguish volumes from articles/chapters (as above), then
+single or double quotations around article titles are superfluous and
+only add visual clutter.
+\end{quote}
+
+\texttt{biblatex-unified}: Article and chapter titles are set in roman
+font, while titles of books, dissertations, and journals are set in
+italics. There are no quotation marks around titles.
+
+\begin{quote}
+3. \textbf{Differing capitalization styles should be used to make
+category distinctions.} Use capitalization of all lexical words for
+journal titles and capitalize only the first word (plus proper names and
+the first word after a colon) for book/dissertation titles and
+article/chapter titles. This is a useful diagnostic for discriminating
+between titles that are recurring and those that are not. The journal
+style for capitalization should also be applied to the title of book
+series. Thus, the citation of a SNLLT volume would be punctuated:
+\emph{Objects and other subjects: Grammatical functions, functional
+categories, and configurationality} (Studies in Natural Language and
+Linguistic Theory 52).
+\end{quote}
+
+\texttt{biblatex-unified}: Recurring titles (i.e.~titles of journals and
+book series) are set in title case (capitalization of all lexical
+words), while non-recurring titles (articles, chapters, books,
+dissertations) are set in sentence case (capitalize only the first word,
+plus proper names and the first word after a colon).
+
+NB: It is fairly easy to convert a title given in title case into
+sentence case. But the other way round is quite difficult.
+\texttt{biblatex-unified.bbx} depends on the bib file containing title
+case for those elements that should be set in title case. For those
+elements that will be set in sentence case, the bbx file will do the
+conversion to sentence case. Proper names (and the first word after a
+colon) need to be protected against that lower casing, so the bib-file
+should have \texttt{\{...\}} braces around those words. Please note that
+just putting \texttt{\{\}} around the first letter in words that should
+be capitalized is bad practice since it prevents proper kerning of the
+space between the first and second letter. Even worse practice is to
+``double wrap'' a whole title in braces, which prevents any style file
+from setting the title in the style specified by its formatting
+philosophy.
+
+NB: It is to be encouraged that titles and subtitles be entered into
+separate fields in the bib entry. In that case, the bbx file will
+properly capitalize the first letter of the subtitle. So, the first of
+the following formats is preferred for use with the unified bbx style
+(but it has the disadvantage of not necessarily being compatible with
+other bibliography styles):
+
+Option 1
+
+\begin{verbatim}
+title = {Government and Binding Theory and the Minimalist Program},
+subtitle = {Principles and Parameters in Syntactic Theory},
+\end{verbatim}
+
+Option 2
+
+\begin{verbatim}
+title = {Government and Binding Theory and the Minimalist Program:  
+        {Principles} and Parameters in Syntactic Theory},
+\end{verbatim}
+
+\begin{quote}
+4. \textbf{All author/editor first names should be spelled out.} Not
+doing so only serves to make the citation less informative. Without full
+first names, the 20th century index for Language alone would conflate
+five different people as `J. Smith', four as `J. Harris', three each
+under `A. Cohen' and `P. Lee', two each under `R. Kent', `J. Anderson',
+`H. Klein' and `J. Klein'.
+\end{quote}
+
+\texttt{biblatex-unified}: The style does not abbreviate first names.
+Compliance with the Unified Style depends on the bib-file containing
+full names for everyone.
+
+\begin{quote}
+5. \textbf{The ampersand is useful.} Use ampersand to distinguish higher
+and lower order conjuncts, i.e.~{[}W \& X{]} and {[}Y \& Z{]}, as in
+Culicover \& Wilkins and Koster \& May. It is relatively easy to see
+that reference is made here to two pairs of authors here (cf.~Culicover
+and Wilkins and Koster and May).
+\end{quote}
+
+\texttt{biblatex-unified}: The style uses the ampersand rather than a
+final ``and'' in author and editor lists. This is taken care of by
+\texttt{biblatex-unified}.
+
+\begin{quote}
+6. \textbf{Name repetitions are good.} While using a line \_\_\_\_ may
+save a little space, or a few characters, it also makes each such
+citation referentially dependent on an antecedent, and the effort of
+calculating such antecedents is more than what it saved typographically.
+Each citation should be internally complete.
+\end{quote}
+
+\texttt{biblatex-unified}: The style does not use a dashed line for
+repeated authors in the reference list.
+
+\begin{quote}
+7. \textbf{Four digit year plus period only.} Extra parentheses are
+visual clutter and superfluous.
+\end{quote}
+
+\texttt{biblatex-unified}: The style complies with the Unified Style
+Sheet.
+
+\begin{quote}
+8. \textbf{Commas and periods and other punctuation.} Separate citation
+components with periods (e.g., Author. Year. Title.) and subcomponents
+with commas (e.g., Author1, Author2 \& Author3). Please note the
+ampersand (\&), rather than the word ``and'' before the name of the last
+author, and no comma before the ``\&''. The use of the colon between
+title and subtitle and between place and publisher is traditional, but
+we do not use it between journal volumenumber and pagenumbers.
+\end{quote}
+
+\texttt{biblatex-unified}: The style complies with the Unified Style
+Sheet.
+
+\begin{quote}
+9. \textbf{Parentheses around ed.~makes sense.} Commas and periods
+should be used exclusively to separate citation components (e.g.,
+``Author. Year.''), or subcomponents (e.g.~``author1, author2 \&
+author3). Since''ed." is neither a component nor a subcomponent, but a
+modifier of a component, it should not be separated from the name by a
+comma:
+\end{quote}
+
+\begin{quote}
+surname, firstname = author surname, firstname (ed.). = editor (NOT
+surname, firstname, ed.) surname, firstname \& firstname surname (eds.)
+= editors
+\end{quote}
+
+\texttt{biblatex-unified}: The style complies with the Unified Style
+Sheet.
+
+\begin{quote}
+10. \textbf{For conference proceedings, working papers, etc.} For
+conference proceedings published with an ISSN, treat the proceedings as
+a journal: Include both the full conference name and any commonly used
+acronym for the conference (BLS, WCCFL, etc.) in the journal title
+position. For proceedings not published with an ISSN, treat the
+proceedings as any other book, using the full title as listed on the
+front cover or title page. If the title (and subtitle if there is one)
+only includes an acronym for the conference name, expand the acronym in
+square brackets or parentheses following the acronym. If the title does
+not include an acronym which is commonly used for the conference name,
+include the acronym in square brackets or parentheses following the
+conference name. The advantage of including the acronym after the
+society title is that it makes the entry much more identifiable in a
+list of references.
+\end{quote}
+
+{[}From the comments by Joseph Salmons:{]}
+
+\begin{quote}
+Do not include ``proceedings of the'' or ``papers from the''.
+\end{quote}
+
+NB: The examples included with the Unified Style Sheet do not include
+the editors of the CLS proceedings volume. We agree with this practice,
+since the names of editors of such proceedings are often hard to get
+hold of.
+
+\texttt{biblatex-unified}: These guidelines need to be satisfied in the
+construction of the bib-file. There are two approaches, one more of a
+hack than the other:
+
+\emph{Option 1}: Use the \texttt{@inproceedings} entry type and include
+the ISSN of the proceedings when available. Example:
+
+\begin{verbatim}
+@inproceedings{casali:1998a,
+    Author = {Casali, Roderic F.},
+    Booktitle = {Chicago Linguistic Society (CLS)},
+    ISSN = {0577-7240},
+    Number = {1},
+    Pages = {55-68},
+    Title = {Predicting {ATR} Activity},
+    Volume = {34},
+    Year = {1998}}
+\end{verbatim}
+
+Comment: Following the Unified Style Sheet, we can let the presence of
+an ISSN control whether an article in conference proceedings is set like
+a journal article or like a book chapter. To do this, the bib-file needs
+to contain the ISSN of proceedings where possible. When the ISSN is in
+the bib-file, \texttt{biblatex-unified} will not print it with the entry
+but it will trigger setting as an article. If there's no ISSN in the
+entry, \texttt{biblatex-unified} will set it as a book chapter. The ISSN
+can be found through \href{http://www.worldcat.org}{WorldCat} fairly
+easily. Here's a list of common conference proceedings with their ISSN:
+
+\begin{itemize}
+\tightlist
+\item
+  BLS: 0363-2946
+\item
+  CLS: 0577-7240
+\item
+  NELS: 0883-5500
+\item
+  SALT: 2163-5951
+\item
+  WCCFL: 1042-1068
+\end{itemize}
+
+\emph{Option 2}: Another option, less portable and definitely a hack, is
+to use the \texttt{@article} entry type, putting the conference name
+(and the acronym in parentheses; no need to case protect the acronym,
+since journal titles are set as is) in the \texttt{journal} field, and
+do not list the editors. Example:
+
+\begin{verbatim}
+@article{casali:1998b,
+    Author = {Casali, Roderic F.},
+    Journal = {Chicago Linguistic Society (CLS)},
+    Number = {1},
+    Pages = {55-68},
+    Title = {Predicting {ATR} Activity},
+    Volume = {34},
+    Year = {1998}}
+\end{verbatim}
+
+\begin{quote}
+11. \textbf{Use ``edn.'' as an abbreviation for ``edition'', thus ``2nd
+edn.''.} This avoids ambiguity and confusion with ``ed.'' (editor).
+\end{quote}
+
+\texttt{biblatex-unified}: The style complies with the Unified Style
+Sheet.
+
+\begin{quote}
+12. \textbf{Names with ``von'', ``van'', ``de'', etc.} If the ``van''
+(or the ``de'' or other patronymic) is lower case and separated from the
+rest by a space (e.g.~Elly van Gelderen), then alphabetize by the first
+upper-case element:
+\end{quote}
+
+\begin{quote}
+\texttt{Gelderen,\ Elly\ van}
+\end{quote}
+
+\begin{quote}
+The addition of ``see \ldots{}'' in comprehensive indices and lists
+might be helpful for clarification:
+\end{quote}
+
+\begin{quote}
+\texttt{van\ Gelderen,\ Elly\ (see\ Gelderen)}
+\end{quote}
+
+\texttt{biblatex-unified}: This is a point where we depart from the
+Unified Style Sheet. If the ``van'' (or the ``de'' or other patronymic)
+is lower case and separated from the rest by a space (e.g.~Elly van
+Gelderen), then alphabetize by the first upper-case element \textbf{but
+display the particle as part of the last name in its usual position}:
+
+\begin{verbatim}
+`van Gelderen, Elly [alphabetized under "G"]`
+\end{verbatim}
+
+NB: biblatex-unified is the only biblatex style that we know of that
+implements this practice (it took some hacking to make this possible).
+There is no need to do anything in the bib-file to ensure proper
+treatment of ``von'' etc.
+
+\begin{quote}
+13. \textbf{Names with ``Jr.'', ``IV.'', etc.} Following library
+practice, list elements such as ``Jr.'' as a subelement after names,
+separated by a comma.
+\end{quote}
+
+\texttt{biblatex-unified}: The style complies with the Unified Style
+Sheet.
+
+\begin{quote}
+14. \textbf{Use ``In'' to designate chapters in collections.} This makes
+the book's format maximally similar to the standard citation format.
+This, in turn, would be time-saving when the author or the editor notice
+that more than one article is cited from a given collection and hence
+that that book's details should be set out as a separate entry in the
+references (and the full details deleted from the articles' entries).
+author. year. chaptertitle. In editorname (ed.), collectiontitle,
+pagenumbers. publisher.
+\end{quote}
+
+\texttt{biblatex-unified}: The style complies with the Unified Style
+Sheet.
+
+\begin{quote}
+15. \textbf{Journal volume numbers.} We favor:
+volumenumber(volumeissue). startingpage--endingpage. Thus: 22(1).
+135-169. Note the space between volume number/issue and page numbers.
+Special formatting (e.g., bold for volume number) is superfluous. Issue
+numbers are a parenthetical modifier (cf.~``ed.'' above) of the volume
+number. While it is not NECESSARY information for identifying the
+article, it is extremely USEFUL information.
+\end{quote}
+
+\texttt{biblatex-unified}: The style complies with the Unified Style
+Sheet. Providing issue numbers is a guideline for the preparation of the
+bib-file.
+
+\begin{quote}
+16. \textbf{Dissertations/theses.} These conform to the
+already-widespread Place: Publisher format and fit readily into the rest
+of the standard: Cambridge, MA: MIT dissertation. Instead of archaic
+state abbreviations, use the official two-letter postal abbreviations.
+Note that national and other traditions vary in exactly what is labeled
+`thesis' versus `dissertation' and in distinguishing `PhD' from
+`doctoral' dissertations. Cambridge, MA: MIT dissertation. Chapel Hill:
+UNC MA thesis.
+\end{quote}
+
+\texttt{biblatex-unified}: The style complies with the Unified Style
+Sheet. Using the two-letter postal abbreviations is something that needs
+to be taken care of during the preparation of the bib-file.
+
+\begin{quote}
+17. \textbf{On-line materials.} The basic information here -- author,
+date, title -- remains the same, and the URL where the resource was
+found takes the place of publisher or journal. We urge authors to
+include the date the material was accessed, in parentheses after the
+URL, since new versions often replace old ones. For a .pdf file, this
+would be the date of downloading, but for a resource like an on-line
+dictionary consulted repeatedly, a range of dates may be needed. For
+additional discussion of handling online citations, authors may want to
+consult this guide:
+\end{quote}
+
+\begin{quote}
+Walker, Janice R. \& Todd Taylor. 1998. The Columbia Guide to Online
+Style. New York: Columbia University Press.
+\end{quote}
+
+\texttt{biblatex-unified}: We take it that this does not refer to
+material that has officially been published online, in which case
+permanent document identifiers such as DOIs and the like will take care
+of the linking requirements. Rather, we are assuming this refers to
+``unpublished'' material available online (on author's homepages or
+repositories such as the Semantics Archive or LingBuzz). In this case,
+just use the \texttt{@unpublished} entry-type, give the URL in the
+\texttt{url\ =\ \{\}} field, and if deemed necessary include the date
+the material was accessed by adding an \texttt{urldate\ =\ \{\}} field.
+The date should be given in YYYY-MM-DD format,
+e.g.~\texttt{urldate\ =\ \{2013-08-11\}}. The style will then add the
+date in parentheses, formatted to the style sheet's rather odd format.
+
+\hypertarget{departures-from-the-unified-style-sheet}{%
+\section{Departures from the Unified Style
+Sheet}\label{departures-from-the-unified-style-sheet}}
+
+We already mentioned our one major disagreement with the Unified Style
+Sheet: the incorrect treatment of the ``von'' part of names.
+
+We depart from the style sheet only in a few other places. These are
+actually only departures from the example formatting given and do not
+pertain to any explicit guidelines.
+
+\begin{enumerate}
+\def\labelenumi{\arabic{enumi}.}
+\tightlist
+\item
+  The acronym ``CLS'' given in parentheses after ``Chicago Linguistic
+  Society'' in the Casali 1986 entry is not given in italics in the
+  example. Since it is part of the ``journal title'' field,
+  \texttt{biblatex-unified} will typeset it in italics.
+\item
+  The example URLs have a period inside the parentheses around the URL
+  access date. We have relocated this period to outside the parentheses.
+\item
+  In the one case of an online journal article, the Pedersen 2005 entry,
+  the example has a comma between the journal + volume and the URL. We
+  think that this is analogous to the break between journal +
+  volume(issue) and page numbers, and so it should be a period instead
+  of a comma. That is what \texttt{biblatex-unified} does.
+\item
+  There is a period between the URL and the URL access date (which is in
+  parentheses). We do not think that this period should be there.
+  \texttt{biblatex-unified} has a space.
+\end{enumerate}
+
+\hypertarget{guidelines-for-the-preparation-of-bib-files}{%
+\section{Guidelines for the preparation of bib
+files}\label{guidelines-for-the-preparation-of-bib-files}}
+
+For convenience, we repeat the best practices for preparing your bib
+file for use with \texttt{biblatex-unified}.
+
+\begin{enumerate}
+\def\labelenumi{\arabic{enumi}.}
+\tightlist
+\item
+  Any words in the titles of articles, books, dissertations that should
+  not be lowercased (other than the first word) have to be protected by
+  \{\} brackets around that word (not just around the first letter of
+  the word and never double wrap the entire title!). This includes the
+  first word after a subtitle colon (unless the subtitle field is used
+  instead).
+\item
+  Give full first names for all authors and editors (all persons listed
+  in the bib file).
+\item
+  For conference proceedings, working papers, etc. For conference
+  proceedings published with an ISSN, treat the proceedings as a
+  journal: Include both the full conference name and any commonly used
+  acronym for the conference (BLS, WCCFL, etc.) in the journal title
+  position. Do not include the editors in the bib-file. For proceedings
+  not published with an ISSN, treat the proceedings as any other book,
+  using the full title as listed on the front cover or title page. If
+  the title (and subtitle if there is one) only includes an acronym for
+  the conference name, expand the acronym in square brackets or
+  parentheses following the acronym. If the title does not include an
+  acronym which is commonly used for the conference name, include the
+  acronym in square brackets or parentheses following the conference
+  name. The advantage of including the acronym after the society title
+  is that it makes the entry much more identifiable in a list of
+  references. Do not include ``proceedings of the'' or ``papers from
+  the''.
+\item
+  For on-line materials, you can give the date the resource was
+  accessed. Use the \texttt{urldate} field for this purpose and give the
+  date in the YYYY-MM-DD format, e.g.~\texttt{2013-08-11}.
+\item
+  Use two-letter postal abbreviations for all US cities.
+\end{enumerate}
+
+\hypertarget{license-and-copyright}{%
+\section{License and copyright}\label{license-and-copyright}}
+
+Copyright ©2020 Kai von Fintel.
+
+This package is author-maintained. Permission is granted to copy,
+distribute and/or modify this software under the terms of the LaTeX
+Project Public License, version 1.3c.
+
+This software is provided ``as is,'' without warranty of any kind,
+either expressed or implied, including, but not limited to, the implied
+warranties of merchantability and fitness for a particular purpose.
+
+\hypertarget{changelog-and-release-notes}{%
+\section{Changelog and release
+notes}\label{changelog-and-release-notes}}
+
+\textbf{v1.00 (2020-05-25)} Initial CTAN release.
+
+\end{document}
diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.bib b/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.bib
new file mode 100644
index 00000000000..588723c75a7
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.bib
@@ -0,0 +1,146 @@
+@book{blevins:2004,
+	Address = {Cambridge},
+	Author = {Blevins, Juliette},
+	Publisher = {Cambridge University Press},
+	Title = {Evolutionary Phonology},
+	Year = {2004}}
+
+@inproceedings{casali:1998,
+	Author = {Casali, Roderic F.},
+	Booktitle = {Chicago Linguistic Society (CLS)},
+	Number = {1},
+	Pages = {55-68},
+	Title = {Predicting {ATR} Activity},
+	Volume = {34},
+	Year = {1998},
+  ISSN = {0577-7240}}
+
+@book{chomsky:1986,
+	Address = {New York},
+	Author = {Chomsky, Noam},
+	Publisher = {Praeger},
+	Title = {Knowledge of Language},
+	Year = {1986}}
+
+@book{chomsky:1969,
+  Title = {Aspects of the Theory of Syntax},
+  Author = {Chomsky, Noam},
+  ISBN = {9780262327800},
+  Year = {1969},
+  Publisher = {MIT Press}}
+
+@book{coetsem:2000,
+	Address = {Heidelberg},
+	Author = {van Coetsem, Frans},
+	Publisher = {Winter},
+	Title = {A General and Unified Theory of the Transmission Process in Language Contact},
+	Year = {2000}}
+
+@unpublished{franks:2005,
+	Author = {Franks, Steven},
+	Title = {Bulgarian Clitics are Positioned in the Syntax},
+	Url = {http://www.cogs.indiana.edu/people/homepages/franks/Bg_clitics_remark_dense.pdf},
+	Urldate = {2006-05-17},
+	Year = {2005}}
+
+@article{iverson:1983,
+	Author = {Iverson, Gregory K.},
+	Journal = {Journal of Phonetics},
+	Pages = {191-200},
+	Title = {Korean /s/},
+	Volume = {11},
+	Year = {1983}}
+
+@article{iverson:1989,
+	Author = {Iverson, Gregory K.},
+	Journal = {Phonology},
+	Pages = {285-303},
+	Title = {On the Category Supralaryngeal},
+	Volume = {6},
+	Year = {1989}}
+
+@article{johnson:1989,
+	Author = {Johnson, Kyle and Baker, Mark and Roberts, Ian},
+	Journal = {Linguistic Inquiry},
+	Pages = {219-251},
+	Title = {Passive Arguments Raised},
+	Volume = {20},
+	Year = {1989}}
+
+@book{lahiri:2000,
+	Address = {Berlin},
+	Editor = {Lahiri, Aditi},
+	Number = {127},
+	Publisher = {Mouton de Gruyter},
+	Series = {Trends in Linguistics},
+	Title = {Analogy, Leveling, Markedness: {Principles} of Change in Phonology and Morphology},
+	Year = {2000}}
+
+@incollection{mccarthy:1999,
+	Address = {Malden, MA and Oxford},
+	Author = {McCarthy, John J. and Prince, Alan S.},
+	Booktitle = {Phonological Theory: {The} Essential Readings},
+	Editor = {Goldsmith, John A.},
+	Pages = {238-288},
+	Publisher = {Blackwell},
+	Title = {Prosodic morphology},
+	Year = {1999}}
+
+@article{murray:1983,
+	Author = {Murray, Robert W. and Vennemann, Theo},
+	Journal = {Language},
+	Number = {3},
+	Pages = {514-528},
+	Title = {Sound Change and Syllable Structure in {Germanic} Phonology},
+	Volume = {59},
+	Year = {1983}}
+
+@book{oed:1989,
+	Address = {Oxford},
+	Edition = {2},
+	Publisher = {Oxford University Press},
+	Title = {Oxford {English} Dictionary},
+	Year = {1989}}
+
+@article{pedersen:2005,
+	Author = {Pedersen, Johan},
+	Journal = {Constructions},
+	Title = {The {Spanish} impersonal \emph{se}-construction: {Constructional} variation and change},
+	Url = {http://www.constructions-online.de},
+	Urldate = {2007-04-03},
+	Volume = {1},
+	Year = {2005}}
+
+@incollection{rissanen:1999,
+	Address = {Cambridge and New York},
+	Author = {Rissanen, Matti},
+	Booktitle = {Cambridge History of the {English} Language},
+	Editor = {Lass, Roger},
+	Pages = {187-331},
+	Publisher = {Cambridge University Press},
+	Title = {Syntax},
+	Volume = {3},
+	Year = {1999}}
+
+@phdthesis{stewart:2000,
+	Address = {Columbus, OH},
+	Author = {Stewart, Jr., Thomas W.},
+	School = {The Ohio State University},
+	Title = {Mutation as Morphology: {Bases}, Stems, and Shapes in {Scottish Gaelic}},
+	Type = {phdthesis},
+	Year = {2000}}
+
+@book{webelhuth:1995,
+	Address = {Oxford},
+	Editor = {Webelhuth, Gert},
+	Publisher = {Blackwell},
+	Title = {Government and Binding Theory and the Minimalist Program: {Principles} and Parameters in Syntactic Theory},
+	Year = {1995}}
+
+@phdthesis{yu:2003,
+	Address = {Berkeley, CA},
+	Author = {Yu, Alan C. L.},
+	School = {University of California},
+	Title = {The Morphology and Phonology of Infixation},
+	Type = {phdthesis},
+	Year = {2003}}
diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.pdf b/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.pdf
new file mode 100644
index 00000000000..a67ba7a4476
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.pdf
diff --git a/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.tex b/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.tex
new file mode 100644
index 00000000000..06226986d5b
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/biblatex-unified/unified-test.tex
@@ -0,0 +1,22 @@
+\documentclass{article}
+
+\usepackage[utf8]{inputenc}
+\usepackage{lmodern}
+\usepackage[english]{babel}
+\usepackage{csquotes}
+\usepackage[backend=biber,style=unified]{biblatex}
+\usepackage{hyperref}
+\urlstyle{same}
+\pagestyle{empty}
+
+\addbibresource{unified-test.bib}
+
+\begin{document}
+
+\section*{Unified biblatex style sheet for linguistics}
+
+\nocite{*}
+
+\printbibliography[heading=none]
+
+\end{document}
diff --git a/Master/texmf-dist/tex/latex/biblatex-unified/unified.bbx b/Master/texmf-dist/tex/latex/biblatex-unified/unified.bbx
new file mode 100644
index 00000000000..bb278b4a1cb
--- /dev/null
+++ b/Master/texmf-dist/tex/latex/biblatex-unified/unified.bbx
@@ -0,0 +1,733 @@
+%% ---------------------------------------------------------------
+%% biblatex-unified --- A biblatex implementation of the Unified Style
+%%   Sheet for Linguistics Journals. This is the house style of the
+%%   journal "Semantics & Pragmatics" (A journal of the Linguistic
+%%   Society of America).
+%% Maintained by Kai von Fintel (fintel@mit.edu)
+%% Released under the LaTeX Project Public License v1.3c or later
+%% See http://www.latex-project.org/lppl.txt
+%% ---------------------------------------------------------------
+%%
+
+\ProvidesFile{unified.bbx}[2020/06/25 v1.00 biblatex bibliography style]
+
+% biblatex by default calls biblatex.def, we add to this authoryear.bbx, which
+% in turn loads standard.bbx. So, unified.bbx is built on top of those styles;
+% once authoryear.bbx is loaded, we tell it not to put in dashes for repeated
+% authors (in accordance with the Unified Stylesheet)
+
+\RequireBibliographyStyle{authoryear}
+\ExecuteBibliographyOptions{dashed=false,isbn=false,eprint=false}
+
+% NB: The Unified Style Sheet wants abbreviated "ed(s)", "edn". But using the
+% abbreviate option also abbreviates the names of months. But then
+% dateabbrev=false restores the long names of months
+
+% biblatex has a "useprefix" option, which makes "von" count for
+% alphabetization; the Unified Stylesheet does not want that, so it is important
+% that this option be disabled (even if an author tries to set it to true)
+
+\ExecuteBibliographyOptions{%
+  sorting=nyt,abbreviate,dateabbrev=false,useprefix=false}
+
+% For backward compatibility: choose labeldate or labeldateparts
+% depending on the biblatex version
+\@ifpackagelater{biblatex}{2016/09/09} {%
+  \ExecuteBibliographyOptions{labeldateparts}} {%
+  \ExecuteBibliographyOptions{labeldate}
+  \def\printlabeldateextra{\printdateextralabel} }%
+
+% If an @article entry contains Issuetitle and Editor information, we
+% might not want to print it. The Unified Style Sheet does not offer
+% explicit guidelines on this, but they don't have any examples where
+% either of these pieces of information are actually printed.
+% Therefore, we can offer an option for the user to decide whether to
+% print it. The default will be not to print it since the Unified
+% Style Sheet does not have examples where this information is
+% printed. The user can print it by setting `issueandeditor=true` as a
+% package option when biblatex is called.
+
+\newtoggle{issueandeditor}
+\DeclareBibliographyOption{issueandeditor}[false]{%
+  \settoggle{issueandeditor}{#1}}
+
+% Formatting directives for name lists
+% ------------------------------------------------------------------
+%
+% In biblatex.def, there are name formats defined: first-last, last-first,
+% last-first/first-last. They could be simplified (we don't need provisions for
+% using initials only, since the Unified Style doesn't do that), but since
+% biblatex.def is loaded automatically, there's no point. The name formats call
+% bibmacros that figure out how to order the internal of name components. These
+% are re-defined here to make sure that "von" is treated as part of the last
+% name (it still doesn't count for sorting -- which is controlled by the
+% \useprefix package option) name:last is used to produce citation labels
+% name:last-first is used to produce the first author's name listing in the
+% alphabetical bibliography
+
+% Also moved the Jr part to after the first name and inserted another comma,
+% because the Unified Stylesheet disagrees with standard.bbx: it wants "Jr." not
+% to be treated as part of the last name.
+
+% The macros here get 4 arguments passed to them. They are: #1 last name, #2
+% first name, #3 von, #4 Jr.
+
+% In biblatex v3.3 and onwards, the name formatting has changed in a big way.
+% See for example:
+% http://tex.stackexchange.com/questions/299036/biblatex-3-3-name-formatting,
+% https://github.com/plk/biblatex/issues/372, and
+% http://www.texdev.net/2016/03/13/biblatex-a-new-syntax-for-declarenameformat/.
+% The name formats in biblatex.def are not called first-last etc. anymore but
+% given-family etc. And while there are safeguard legacy aliases
+% (\DeclareNameAlias{first-last}{given-family}, for example), the new formats
+% then use macros like \usebibmacro{name:family-given}, which of course our old
+% redefinitions didn't adjust. So, for newer biblatex, we need to do new
+% versions of \renewbibmacro{name:...}.
+
+%% Redefinitions of name:last and name:last-first for biblatex versions before
+%% v3.3
+
+\renewbibmacro*{name:last}[4]{%
+     \usebibmacro{name:delim}{#3#1}%
+     \usebibmacro{name:hook}{#3#1}%
+     \ifblank{#3}
+       {}
+       {\ifcapital
+          {\mkbibnameprefix{\MakeCapital{#3}}\isdot}
+          {\mkbibnameprefix{#3}\isdot}%
+        \ifpunctmark{'}{}{\bibnamedelimc}}%
+  \mkbibnamelast{#1}}%
+
+\renewbibmacro*{name:last-first}[4]{%
+     \usebibmacro{name:delim}{#3#1}%
+     \usebibmacro{name:hook}{#3#1}%
+     \ifblank{#3}{}{%
+       \mkbibnameprefix{#3}\isdot%
+       \ifpunctmark{'}{}{\bibnamedelimc}}%
+     \mkbibnamelast{#1}\isdot
+     \ifblank{#2}{}{\addcomma\bibnamedelimd\mkbibnamefirst{#2}\isdot}%
+     \ifblank{#4}{}{\addcomma\bibnamedelimd\mkbibnameaffix{#4}\isdot}}
+
+%% Redefinitions of name:family and name:family-given for biblatex ever since
+%% v3.3
+
+\renewbibmacro*{name:family}[4]{%
+     \usebibmacro{name:delim}{#3#1}%
+     \usebibmacro{name:hook}{#3#1}%
+     \ifdefvoid{#3}
+       {}
+       {\ifcapital
+          {\mkbibnameprefix{\MakeCapital{#3}}\isdot}
+          {\mkbibnameprefix{#3}\isdot}%
+        \ifprefchar{}{\bibnamedelimc}}%
+     \mkbibnamefamily{#1}\isdot}%
+
+\renewbibmacro*{name:family-given}[4]{%
+  \usebibmacro{name:delim}{#3#1}%
+  \usebibmacro{name:hook}{#3#1}%
+  \ifdefvoid{#3}
+    {}
+    {\mkbibnameprefix{#3}\isdot%
+     \ifprefchar{}{\bibnamedelimc}}%
+  \mkbibnamefamily{#1}\isdot
+  \ifdefvoid{#2}
+    {}
+    {\revsdnamepunct\bibnamedelimd\mkbibnamegiven{#2}\isdot}%
+  \ifdefvoid{#4}
+    {}
+    {\addcomma\bibnamedelimd\mkbibnamesuffix{#4}\isdot}}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% Various bibmacros used in producing the bibliography
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+% We use `date+extradate` but biblatex versions before 3.8 didn't have that
+% macro. Older versions were smart enough to complain about `\renewmacro` and
+% use `\newmacro` instead. But the following construction works for both cases
+
+\providebibmacro{date+extradate}{}
+\renewbibmacro*{date+extradate}{%
+     \iffieldundef{labelyear} {}
+     {\printtext{\printlabeldateextra}}}% Took out parentheses around the year
+
+\renewbibmacro*{author}{%
+  \ifboolexpr{
+    test \ifuseauthor
+    and
+    not test {\ifnameundef{author}}
+  }
+    {\usebibmacro{bbx:dashcheck}
+       {\bibnamedash}
+       {\usebibmacro{bbx:savehash}%
+        \printnames{author}%
+  \iffieldundef{authortype}
+    {\newunit}%                               period instead of space
+    {\setunit{\addcomma\space}}}%
+     \iffieldundef{authortype}
+       {}
+       {\usebibmacro{authorstrg}%
+  \newunit}}%                                 period instead of space
+    {\global\undef\bbx@lasthash
+     \usebibmacro{labeltitle}%
+     \newunit}%                               period instead of space
+  \usebibmacro{date+extradate}}
+
+\renewbibmacro*{editor}{%
+  \usebibmacro{bbx:editor}{editorstrg}}
+\renewbibmacro*{editor+others}{%
+  \usebibmacro{bbx:editor}{editor+othersstrg}}
+\renewbibmacro*{bbx:editor}[1]{%
+  \ifboolexpr{
+    test \ifuseeditor
+    and
+    not test {\ifnameundef{editor}}
+  }
+    {\usebibmacro{bbx:dashcheck}
+       {\bibnamedash}
+       {\printnames{editor}%
+  \setunit{\addspace}%
+  \usebibmacro{bbx:savehash}}%
+     \printtext[parens]{\usebibmacro{#1}}%
+     \clearname{editor}%
+     \newunit}%                                         period instead of space
+    {\global\undef\bbx@lasthash
+     \usebibmacro{labeltitle}%
+     \newunit}%                                         period instead of space
+  \usebibmacro{date+extradate}}
+
+\renewbibmacro*{translator}{%
+  \usebibmacro{bbx:translator}{translatorstrg}}
+\renewbibmacro*{translator+others}{%
+  \usebibmacro{bbx:translator}{translator+othersstrg}}
+\renewbibmacro*{bbx:translator}[1]{%
+  \ifboolexpr{
+    test \ifusetranslator
+    and
+    not test {\ifnameundef{translator}}
+  }
+    {\usebibmacro{bbx:dashcheck}
+       {\bibnamedash}
+       {\printnames{translator}%
+  \setunit{\addcomma\space}%
+  \usebibmacro{bbx:savehash}}%
+     \usebibmacro{translator+othersstrg}%
+     \clearname{translator}%
+     \newunit}%                                     period instead of space
+    {\global\undef\bbx@lasthash
+     \usebibmacro{labeltitle}%
+     \newunit}%                                     period instead of space
+  \usebibmacro{date+extradate}}
+
+\renewbibmacro*{journal}{%
+  \iffieldundef{journaltitle}
+    {}
+    {\printtext{%
+       \printfield{journaltitle}%
+       \setunit{\subtitlepunct}%
+       \printfield{journalsubtitle}}}}
+
+\newbibmacro*{journal+issuetitle+editor}{%
+  \usebibmacro{journal}%
+  \setunit*{\addspace}%
+  \iffieldundef{series}
+    {}
+    {\newunit
+     \printfield{series}%
+     \setunit{\addspace}}%
+  \usebibmacro{volume+number+eid}%
+  \iftoggle{issueandeditor}
+    {\setunit{\addspace}%
+     \usebibmacro{issue+date}%
+     \setunit{\addcolon\space}%
+     \usebibmacro{issue}
+     % The following three lines were originally not included inside of
+     % the journal+issuetitle bibmacro. They have been moved inside of
+     % this macro in order to allow them to be controlled by the toggle
+     % `issuetitle` that is defined at the top of this style file.
+     \newunit
+     \usebibmacro{byeditor+others}%
+     \newunit}
+    {}%
+  \newunit}
+
+% The next three bib macros are for printing the maintitle and
+% booktitle fields of an @inproceedings entry with an ISSN as an
+% article in accordance with the unified style sheet guidelines.
+
+% 1. maintitle
+
+\newbibmacro*{unified:proc-as-article:maintitle}{%
+  \ifboolexpr{
+    test {\iffieldundef{maintitle}}
+    and
+    test {\iffieldundef{mainsubtitle}}
+  }
+    {}
+    {\printtext{%
+       \printfield[maintitle]{maintitle}%
+       \setunit{\subtitlepunct}%
+       \printfield[maintitle]{mainsubtitle}}%
+     \newunit}%
+  \printfield{maintitleaddon}}
+
+% 2. booktitle
+
+\newbibmacro*{unified:proc-as-article:booktitle}{%
+  \ifboolexpr{
+    test {\iffieldundef{booktitle}}
+    and
+    test {\iffieldundef{booksubtitle}}
+  }
+    {}
+    {\printtext{%
+       \printfield[booktitle]{booktitle}%
+       \setunit{\subtitlepunct}%
+       \printfield[booktitle]{booksubtitle}}%
+     \newunit}%
+  \printfield{booktitleaddon}}
+
+% 3. maintitle+booktitle
+
+\newbibmacro*{unified:proc-as-article:maintitle+booktitle}{%
+  \iffieldundef{maintitle}
+    {}
+    {\usebibmacro{unified:proc-as-article:maintitle}%
+     \newunit\newblock}
+  \usebibmacro{unified:proc-as-article:booktitle}%
+  \setunit{\addspace}}
+
+\renewbibmacro*{volume+number+eid}{%
+  \printfield{volume}%
+%  \setunit*{\adddot}%
+  \printfield[parens]{number}%  parentheses instead of dot before issue number
+  \setunit{\addcomma\space}%
+  \printfield{eid}}
+
+% This is for printing the volume field of a proceedings with an ISSN
+% as an article in accordance with the unified style sheet guidelines.
+% It depends on the declared field format below.
+
+\newbibmacro*{unified:proc-as-article:volume+number+eid}{%
+  \printfield[volume:unified:proc-as-article]{volume}%
+  \printfield[parens]{number}%
+  \setunit{\addcomma\space}%
+  \printfield{eid}}
+
+% Because of the weird format "3 May, 2007" specified in the Unified
+% Stylesheet for URL access dates, we need a special way to format the
+% urldate
+
+\newcommand{\mkbibdateunified}[3]{% Year-Month-Day as input --> xx Month, Year
+  \iffieldundef{#3}
+    {}
+    {\stripzeros{\thefield{#3}}%
+     \nobreakspace}%
+  \iffieldundef{#2}
+    {\iffieldundef{#1}%
+      {}%
+      {\stripzeros{\thefield{#1}}}}%
+    {\mkbibmonth{\thefield{#2}}%
+     \iffieldundef{#1}%
+      {}%
+      {\iffieldundef{#3}%
+           {}%
+           {,}%
+         \space\stripzeros{\thefield{#1}}}%
+    }%
+  }%
+
+\renewbibmacro*{url+urldate}{%
+  \printfield{url}%
+  \iffieldundef{urlyear}%
+    {}%
+    {\setunit*{\addspace}%
+     \printtext[parens]{\mkbibdateunified{urlyear}{urlmonth}{urlday}}}%
+  }
+
+\renewbibmacro*{series+number}{%
+  \iffieldundef{series}
+    {}
+    {\printtext[parens]{%
+      \printfield{series}%
+      \setunit*{\addspace}%
+      \printfield{number}}%
+    }}
+
+\renewbibmacro*{byeditor+others}{%
+  \ifnameundef{editor}
+    {}
+    {\printnames[byeditor]{editor}%
+     \setunit{\addspace}%
+     \printtext[parens]{\usebibmacro{editor+othersstrg}}%
+     \clearname{editor}%
+     \newunit}%
+  \usebibmacro{byeditorx}%
+  \usebibmacro{bytranslator+others}}
+
+\renewbibmacro*{chapter+pages}{%
+  \iffieldundef{chapter}%
+  {}%
+  {\printfield{chapter}%
+  \setunit{\addcomma\space}}%
+  \printfield{pages}%
+  \newunit}
+
+\renewbibmacro*{note+pages}{%
+  \iffieldundef{note}%
+  {}%
+  {\printfield{note}%
+  \setunit{\addcomma\space}}%
+  \printfield{pages}%
+  \newunit}
+
+\newbibmacro*{institution+location+type+date}{%
+  \printlist{location}%
+  \iflistundef{institution}
+    {}
+    {\setunit*{\addcolon\space}}%
+  \printlist{institution}%
+  \setunit{\addspace}%
+  \printfield{type}%
+  \setunit*{\addcomma\space}%
+  \usebibmacro{date}%
+  \newunit}
+
+% The following is a hack to satisfy the Unified Stylesheet's decision
+% to give the edition right after the OED as used as a sortlabel.
+
+\renewbibmacro*{labeltitle}{%
+  \iffieldundef{label}
+    {\iffieldundef{shorttitle}
+       {\printfield{title}%
+        \setunit{\addcomma\space}%     Here it comes, preparing for the edition
+        \printfield{edition}%          Here's the edition
+        \clearfield{title}%
+        \clearfield{edition}}%         Clearing the edition field
+       {\printfield[title]{shorttitle}}}
+    {\printfield{label}}}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% Punctuation & formatting
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+% This gets rid of the Oxford comma in name lists and uses the
+% ampersand rather than "and":
+
+\renewcommand*{\finalnamedelim}{\addspace\&\addspace}
+\renewcommand*{\finallistdelim}{\addspace\&\addspace}
+
+% no colon after "In" in incollection entries (overriding
+% biblatex.def):
+
+\renewcommand{\intitlepunct}{\addspace}
+
+\renewcommand{\subtitlepunct}{\addcolon\space}
+
+% No comma before pages, just the usual new unit period
+
+\renewcommand*{\bibpagespunct}{\newunitpunct}
+
+\DefineBibliographyStrings{english}{%
+  edition = {edn\adddot},
+  phdthesis = {dissertation},
+}
+
+% basically everything is in sentence case, other than journals and
+% book series (recurring titles)
+
+\DeclareFieldFormat[%
+  article,book,collection,incollection,inproceedings,thesis,unpublished]%
+  {titlecase}{\MakeSentenceCase*{#1}}%
+
+% No quotes around titles
+
+\DeclareFieldFormat[%
+  article,inbook,incollection,inproceedings,patent,thesis,unpublished]%
+  {title}{#1}
+
+% Just like book titles, thesis titles are in italics
+
+\DeclareFieldFormat[thesis]{title}{\mkbibemph{#1}}
+
+\DeclareFieldFormat{pages}{#1}     % no pp. prefix, took \mkpageprefix out [kvf]
+\DeclareFieldFormat{doi}{%
+  \ifhyperref
+    {\href{https://doi.org/#1}{\nolinkurl{https://doi.org/#1}}}
+    {\nolinkurl{https://doi.org/#1}}}
+\DeclareFieldFormat{url}{\url{#1}}
+
+% This is for printing the volume field of a proceedings with an ISSN
+% as an article in accordance with the unified style sheet guidelines
+
+\DeclareFieldFormat{volume:unified:proc-as-article}{#1}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% The bibliography drivers, specifying the formats of each type of
+% entry in the bibliography
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+%%% First, the entry types used in the Unified Test Bibliography.
+%%% Could rely on standard.bbx for all others as a fallback.
+
+% For the article type, the only departure from standard.bbx is that
+% we don't use a literal "In: " before the journal title; other
+% formatting departures are done in the format specs and bibmacros
+
+\DeclareBibliographyDriver{article}{%
+  \usebibmacro{bibindex}%
+  \usebibmacro{begentry}%
+  \usebibmacro{author/translator+others}%
+  \setunit{\labelnamepunct}\newblock
+  \usebibmacro{title}%
+  \newunit
+  \printlist{language}%
+  \newunit\newblock
+  \usebibmacro{byauthor}%
+  \newunit\newblock
+  \usebibmacro{bytranslator+others}%
+  \newunit\newblock
+  \printfield{version}%
+  \newunit\newblock
+  \usebibmacro{journal+issuetitle+editor}%
+  \newblock%                          \newblock ensures period before pages
+  \usebibmacro{note+pages}%
+  \newunit\newblock
+  \iftoggle{bbx:isbn}
+    {\printfield{issn}}
+    {}%
+  \newunit\newblock
+  \usebibmacro{doi+eprint+url}%
+  \newunit\newblock
+  \usebibmacro{addendum+pubstate}%
+  \setunit{\bibpagerefpunct}\newblock
+  \usebibmacro{pageref}%
+  \newunit\newblock
+  \iftoggle{bbx:related}
+    {\usebibmacro{related:init}%
+     \usebibmacro{related}}
+    {}%
+  \usebibmacro{finentry}}
+
+\DeclareBibliographyDriver{book}{%
+  \usebibmacro{bibindex}%
+  \usebibmacro{begentry}%
+  \usebibmacro{author/editor+others/translator+others}%
+  \setunit{\labelnamepunct}\newblock
+  \usebibmacro{maintitle+title}%
+  \newunit
+  \printlist{language}%
+  \newunit\newblock
+  \usebibmacro{byauthor}%
+  \newunit\newblock
+  \usebibmacro{byeditor+others}%
+  \newunit\newblock
+  \printfield{edition}%
+  \newunit
+  \iffieldundef{maintitle}
+    {\printfield{volume}%
+     \printfield{part}}
+    {}%
+  \newunit
+  \printfield{volumes}%
+  \setunit{\addspace}% 
+  \usebibmacro{series+number}%
+  \newunit\newblock
+  \printfield{note}%
+  \newunit\newblock
+  \usebibmacro{publisher+location+date}%
+  \newunit\newblock
+  \usebibmacro{chapter+pages}%
+  \newunit
+  \printfield{pagetotal}%
+  \newunit\newblock
+  \iftoggle{bbx:isbn}
+    {\printfield{isbn}}
+    {}%
+  \newunit\newblock
+  \usebibmacro{doi+eprint+url}%
+  \newunit\newblock
+  \usebibmacro{addendum+pubstate}%
+  \setunit{\bibpagerefpunct}\newblock
+  \usebibmacro{pageref}%
+  \newunit\newblock
+  \iftoggle{bbx:related}
+    {\usebibmacro{related:init}%
+     \usebibmacro{related}}
+    {}%
+  \usebibmacro{finentry}}
+
+% Aliased to ensure no period between the title and the series.
+
+\DeclareBibliographyAlias{collection}{book}
+
+% @inbook entries look terrible as-is, and have fields very similar to
+% @incollection anyway
+
+\DeclareBibliographyAlias{inbook}{incollection}
+
+\DeclareBibliographyAlias{incollection}{inproceedings}
+
+% Given the guidelines in the unified style sheet, we should print
+% conference proceedings and working papers as @article's just in case
+% the publication has an ISSN. So, rather than have users handle this
+% in the database by changing the entry type, we can implement this by
+% checking if the inproceedings entry has an ISSN. If the field is
+% undefined, the driver will do what driver did for @inproceedings
+% entries as of 512f11657199a6044f7663da454f3eac338bdbd5 except that
+% \printlist{organization} and \newunit have been removed. On the
+% other hand, if the ISSN field is not undefined, then we will do
+% largely the exact same thing that we do in the @article driver,
+% except that we use the two macros
+% \usebibmacro{unified:proc-as-article:maintitle+booktitle} and
+% \usebibmacro{unified:proc-as-article:volume+number+eid} instead of
+% \usebibmacro{journal+issuetitle} and except that
+% \usebibmacro{byeditor+others} has been removed so as to ensure that
+% the editors are not listed even if they are present in the database.
+
+\DeclareBibliographyDriver{inproceedings}{%
+  \usebibmacro{bibindex}%
+  \usebibmacro{begentry}%
+  \iffieldundef{issn}
+    {\usebibmacro{author/translator+others}%
+     \setunit{\labelnamepunct}\newblock
+     \usebibmacro{title}%
+     \newunit
+     \printlist{language}%
+     \newunit\newblock
+     \usebibmacro{byauthor}%
+     \newunit\newblock
+     \usebibmacro{in:}%
+     \ifnameundef{editor}
+       {\setunit{\addspace}}
+       {\usebibmacro{byeditor+others}\setunit{\addcomma\space}}
+     \usebibmacro{maintitle+booktitle}%
+     \setunit{\addcomma\space}
+     \printfield{edition}%
+     \setunit{\addcomma\space}
+     \iffieldundef{maintitle}
+       {\printfield{volume}%
+        \printfield{part}}
+       {}%
+     \setunit{\addcomma\space}
+     \printfield{volumes}%
+     \setunit{\addspace}%
+     \usebibmacro{series+number}%
+     \setunit{\addcomma\space}
+     \usebibmacro{chapter+pages}%
+     \newunit\newblock
+     \printfield{note}%
+     \newunit\newblock
+     \usebibmacro{publisher+location+date}%
+     \newunit\newblock
+     \iftoggle{bbx:isbn}
+       {\printfield{isbn}}
+       {}%
+     \newunit\newblock
+     \usebibmacro{doi+eprint+url}%
+     \newunit\newblock
+     \usebibmacro{addendum+pubstate}%
+     \setunit{\bibpagerefpunct}\newblock
+     \usebibmacro{pageref}%
+     \newunit\newblock
+     \iftoggle{bbx:related}
+       {\usebibmacro{related:init}%
+        \usebibmacro{related}}
+       {}}
+    {\usebibmacro{author/translator+others}%
+     \setunit{\labelnamepunct}\newblock
+     \usebibmacro{title}%
+     \newunit
+     \printlist{language}%
+     \newunit\newblock
+     \usebibmacro{byauthor}%
+     \newunit\newblock
+     \usebibmacro{bytranslator+others}%
+     \newunit\newblock
+     \printfield{version}%
+     \newunit\newblock
+     \usebibmacro{unified:proc-as-article:maintitle+booktitle}%
+     \usebibmacro{unified:proc-as-article:volume+number+eid}
+     \newunit\newblock%
+     \usebibmacro{note+pages}%
+     \newunit\newblock
+     \iftoggle{bbx:isbn}
+       {\printfield{issn}}
+       {}%
+     \newunit\newblock
+     \usebibmacro{doi+eprint+url}%
+     \newunit\newblock
+     \usebibmacro{addendum+pubstate}%
+     \setunit{\bibpagerefpunct}\newblock
+     \usebibmacro{pageref}%
+     \newunit\newblock
+     \iftoggle{bbx:related}
+       {\usebibmacro{related:init}%
+        \usebibmacro{related}}
+       {}}
+  \usebibmacro{finentry}}
+
+\DeclareBibliographyDriver{thesis}{%
+  \usebibmacro{bibindex}%
+  \usebibmacro{begentry}%
+  \usebibmacro{author}%
+  \setunit{\labelnamepunct}\newblock
+  \usebibmacro{title}%
+  \newunit
+  \printlist{language}%
+  \newunit\newblock
+  \usebibmacro{byauthor}%
+  \newunit\newblock
+  \printfield{note}%
+  \newunit\newblock
+  \usebibmacro{institution+location+type+date}%
+  \newunit\newblock
+  \usebibmacro{chapter+pages}%
+  \newunit
+  \printfield{pagetotal}%
+  \newunit\newblock
+  \iftoggle{bbx:isbn}
+    {\printfield{isbn}}
+    {}%
+  \newunit\newblock
+  \usebibmacro{doi+eprint+url}%
+  \newunit\newblock
+  \usebibmacro{addendum+pubstate}%
+  \setunit{\bibpagerefpunct}\newblock
+  \usebibmacro{pageref}%
+  \newunit\newblock
+  \iftoggle{bbx:related}
+    {\usebibmacro{related:init}%
+     \usebibmacro{related}}
+    {}%
+  \usebibmacro{finentry}}
+
+\DeclareBibliographyDriver{unpublished}{%
+  \usebibmacro{bibindex}%
+  \usebibmacro{begentry}%
+  \usebibmacro{author}%
+  \setunit{\labelnamepunct}\newblock
+  \usebibmacro{title}%
+  \newunit
+  \printlist{language}%
+  \newunit\newblock
+  \usebibmacro{byauthor}%
+  \newunit\newblock
+  \printfield{howpublished}%
+  \newunit\newblock
+  \printfield{note}%
+  \newunit\newblock
+  \usebibmacro{location+date}%
+  \newunit\newblock
+  \iftoggle{bbx:url}
+    {\usebibmacro{url+urldate}}
+    {}%
+  \newunit\newblock
+  \usebibmacro{addendum+pubstate}%
+  \setunit{\bibpagerefpunct}\newblock
+  \usebibmacro{pageref}%
+  \newunit\newblock
+  \iftoggle{bbx:related}
+    {\usebibmacro{related:init}%
+     \usebibmacro{related}}
+    {}%
+  \usebibmacro{finentry}}
diff --git a/Master/texmf-dist/tex/latex/biblatex-unified/unified.cbx b/Master/texmf-dist/tex/latex/biblatex-unified/unified.cbx
new file mode 100644
index 00000000000..95fe0d99e07
--- /dev/null
+++ b/Master/texmf-dist/tex/latex/biblatex-unified/unified.cbx
@@ -0,0 +1,280 @@
+%% ---------------------------------------------------------------
+%% biblatex-unified --- A biblatex implementation of the Unified Style
+%%   Sheet for Linguistics Journals. This is the house style of the
+%%   journal "Semantics & Pragmatics" (A journal of the Linguistic
+%%   Society of America).
+%% Maintained by Kai von Fintel (fintel@mit.edu)
+%% Released under the LaTeX Project Public License v1.3c or later
+%% See http://www.latex-project.org/lppl.txt
+%% ---------------------------------------------------------------
+%%
+
+\ProvidesFile{unified.cbx}[2020/05/25 v1.00 biblatex citation style]
+
+\RequireCitationStyle{authoryear-comp}
+
+\ExecuteBibliographyOptions{%
+  labeldateparts,%
+  uniquename=minfull,%
+  uniquelist=minyear,%
+  autocite=inline,%
+  sortcites=false}
+
+% disabled sortcites option, since it was sorting by name, instead of
+% year, and we often want to keep citations in the order chosen by the
+% author
+
+% Setting the delimiters the way we want them:
+
+\renewcommand*{\nameyeardelim}{\addspace}
+\renewcommand*{\postnotedelim}{\addcolon\space}
+\renewcommand*{\multicitedelim}{\addcomma\space}
+
+% Apart from setting some options, the main change from
+% authoryear-comp is that we extend what parts of a citation label are
+% hyperlinked (to match what natbib did in the old days). The solution
+% used to be a very ugly homegrown rewrite of the entirety of
+% `authoryear-comp.cbx`, which meant that we were left behind when
+% that style was updated. The new solution, still a hack, is to apply
+% patches to the base style. These patches were first proposed in
+% https://tex.stackexchange.com/a/27615/70432.
+
+% It would be nice if biblatex simply offered more expansive
+% hyperlinks as an option and then we wouldn't have to patch things.
+% But this seems not to be in the cards:
+% https://github.com/plk/biblatex/issues/428
+
+\usepackage{xpatch}
+
+% Patches for biblatex > v3.8 2017-11-04, when labeldate+extradate
+% were introduced
+
+% Combine label and labelyear links
+\xpatchbibmacro{cite}
+  {\usebibmacro{cite:label}%
+   \setunit{\printdelim{nonameyeardelim}}%
+   \usebibmacro{cite:labeldate+extradate}}
+  {\printtext[bibhyperref]{%
+     \DeclareFieldAlias{bibhyperref}{default}%
+     \usebibmacro{cite:label}%
+     \setunit{\printdelim{nonameyeardelim}}%
+     \usebibmacro{cite:labeldate+extradate}}}{}{}
+
+% Include labelname in labelyear link
+\xpatchbibmacro{cite}
+  {\printnames{labelname}%
+   \setunit{\printdelim{nameyeardelim}}%
+   \usebibmacro{cite:labeldate+extradate}}
+  {\printtext[bibhyperref]{%
+     \DeclareFieldAlias{bibhyperref}{default}%
+     \printnames{labelname}%
+     \setunit{\printdelim{nameyeardelim}}%
+     \usebibmacro{cite:labeldate+extradate}}}{}{}
+
+% Patches for biblatex 3.7
+
+% Combine label and labelyear links
+\xpatchbibmacro{cite}
+ {\usebibmacro{cite:label}%
+   \setunit{\printdelim{nonameyeardelim}}%
+   \usebibmacro{cite:labelyear+extrayear}}
+ {\printtext[bibhyperref]{%
+     \DeclareFieldAlias{bibhyperref}{default}%
+     \usebibmacro{cite:label}%
+     \setunit{\addspace}%
+     \usebibmacro{cite:labelyear+extrayear}}}{}{}
+
+% Include labelname in labelyear link
+\xpatchbibmacro{cite}
+ {\printnames{labelname}%
+   \setunit{\printdelim{nameyeardelim}}%
+   \usebibmacro{cite:labelyear+extrayear}}
+ {\printtext[bibhyperref]{%
+     \DeclareFieldAlias{bibhyperref}{default}%
+     \printnames{labelname}%
+     \setunit{\nameyeardelim}%
+     \usebibmacro{cite:labelyear+extrayear}}}{}{} 
+
+% Patches for biblatex before 3.7
+
+% Combine label and labelyear links
+\xpatchbibmacro{cite}
+  {\usebibmacro{cite:label}%
+   \setunit{\addspace}%
+   \usebibmacro{cite:labelyear+extrayear}}
+  {\printtext[bibhyperref]{%
+     \DeclareFieldAlias{bibhyperref}{default}%
+     \usebibmacro{cite:label}%
+     \setunit{\addspace}%
+     \usebibmacro{cite:labelyear+extrayear}}}{}{}
+
+% Include labelname in labelyear link
+\xpatchbibmacro{cite}
+  {\printnames{labelname}%
+   \setunit{\nameyeardelim}%
+   \usebibmacro{cite:labelyear+extrayear}}
+  {\printtext[bibhyperref]{%
+     \DeclareFieldAlias{bibhyperref}{default}%
+     \printnames{labelname}%
+     \setunit{\nameyeardelim}%
+     \usebibmacro{cite:labelyear+extrayear}}}{}{} 
+
+% Access hyperref's citation link start/end commands
+\protected\def\blx@imc@biblinkstart{%
+  \@ifnextchar[%]
+    {\blx@biblinkstart}
+    {\blx@biblinkstart[\abx@field@entrykey]}}
+\def\blx@biblinkstart[#1]{%
+  \blx@sfsave\hyper@natlinkstart{\the\c@refsection @#1}\blx@sfrest}
+\protected\def\blx@imc@biblinkend{%
+  \blx@sfsave\hyper@natlinkend\blx@sfrest}
+\blx@regimcs{\biblinkstart \biblinkend}
+
+\newbool{cbx:link}
+
+% Include parentheses around labelyear in \textcite only in
+% single citations without pre- and postnotes
+\def\iflinkparens{%
+  \ifboolexpr{ test {\ifnumequal{\value{multicitetotal}}{0}} and
+               test {\ifnumequal{\value{citetotal}}{1}} and
+               test {\iffieldundef{prenote}} and
+               test {\iffieldundef{postnote}} }}
+
+\xpatchbibmacro{textcite}
+  {\printnames{labelname}}
+  {\iflinkparens
+     {\DeclareFieldAlias{bibhyperref}{default}%
+      \global\booltrue{cbx:link}\biblinkstart%
+      \printnames{labelname}}
+     {\printtext[bibhyperref]{\printnames{labelname}}}}{}{}
+
+\xpatchbibmacro{textcite}
+  {\usebibmacro{cite:label}}
+  {\iflinkparens
+     {\DeclareFieldAlias{bibhyperref}{default}%
+      \global\booltrue{cbx:link}\biblinkstart%
+      \usebibmacro{cite:label}}
+     {\usebibmacro{cite:label}}}{}{}
+
+\xpretobibmacro{textcite:postnote}
+  {\ifbool{cbx:link}% patch 2.7+
+     {\ifbool{cbx:parens}
+        {\bibcloseparen\global\boolfalse{cbx:parens}}
+        {}%
+         \biblinkend\global\boolfalse{cbx:link}}
+        {}}
+  {}
+  {\xpatchbibmacro{textcite}% patch earlier releases
+     {\setunit{%
+        \ifbool{cbx:parens}
+          {\bibcloseparen\global\boolfalse{cbx:parens}}
+          {}%
+        \multicitedelim}}
+     {\ifbool{cbx:link}
+        {\ifbool{cbx:parens}
+           {\bibcloseparen\global\boolfalse{cbx:parens}}
+           {}%
+         \biblinkend\global\boolfalse{cbx:link}}
+        {}%
+      \setunit{%
+        \ifbool{cbx:parens}
+          {\bibcloseparen\global\boolfalse{cbx:parens}}
+          {}%
+        \multicitedelim}}
+    {}{}}
+
+% Making the old code in \posscite work with new biblatex
+\@ifpackagelater{biblatex}{2016/12/06}%
+{\letbibmacro{cite:labelyear+extrayear}{cite:labeldate+extradate}}
+{}
+
+% What follows is ugly and meh. These cite commands have been part of
+% S&P's author convenience macros since the beginning. We shouldn't
+% advertise them anymore, but here they are. We should add warnings
+% that people shouldn't use them, because they are deprecated and will
+% go away at some point.
+
+\newcommand{\pgcitep}[2]{(\cite{#1}:~#2)}
+\newcommand{\pgcitealt}[2]{\cite{#1}:~#2}
+\newcommand{\pgcitet}[2]{\citeauthor{#1} (\citeyear{#1}:~#2)}
+\newcommand{\pgposscitet}[2]{\citeauthor{#1}'s (\citeyear{#1}:~#2)}
+\newcommand{\seccitealt}[2]{\cite{#1}:~$\S$#2}
+\newcommand{\seccitep}[2]{(\cite{#1}:~$\S$#2)}
+\newcommand{\seccitet}[2]{\citeauthor{#1} (\citeyear{#1}:~$\S$#2)}
+\newcommand{\secposscitet}[2]{\citeauthor{#1}'s (\citeyear{#1}:~$\S$#2)}
+
+\newbibmacro*{posscite}{% Based on textcite
+  \iffieldequals{namehash}{\cbx@lasthash}
+    {\iffieldundef{shorthand}
+       {\usebibmacro{labelyearrepeat}}
+       {\setunit{\compcitedelim}%
+        \usebibmacro{cite:shorthand}%
+        \global\undef\cbx@lastyear}}
+    {\ifnameundef{labelname}
+       {\printtext[bibhyperref]{% Include labelname in hyperlink
+          \DeclareFieldAlias{bibhyperref}{default}% Prevent nested hyperlinks
+          \iffieldundef{shorthand}
+            {\usebibmacro{cite:label}%
+             \setunit{%
+               \global\booltrue{cbx:parens}%
+               \addspace\bibopenparen}%
+             \ifnumequal{\value{citecount}}{1}
+               {\usebibmacro{prenote}}
+               {}%
+             \usebibmacro{cite:labelyear+extrayear}}
+            {\usebibmacro{cite:shorthand}}%
+          \ifthenelse{\iffieldundef{postnote}\AND
+                      \(\value{multicitetotal}=0\AND\value{citetotal}=1\)}
+            {\bibcloseparen% Include closing parenthesis in hyperlink
+             \global\boolfalse{cbx:parens}}
+            {}}}
+       {\printtext[bibhyperref]{% Include labelname in hyperlink
+          \DeclareFieldAlias{bibhyperref}{default}% Prevent nested hyperlinks
+          \printnames{labelname}'s%
+          \setunit{%
+            \global\booltrue{cbx:parens}%
+            \addspace\bibopenparen}%
+          \ifnumequal{\value{citecount}}{1}
+            {\usebibmacro{prenote}}
+            {}%
+          \iffieldundef{shorthand}
+            {\iffieldundef{labelyear}
+               {\usebibmacro{cite:label}}
+               {\usebibmacro{cite:labelyear+extrayear}}%
+             \savefield{labelyear}{\cbx@lastyear}}
+            {\usebibmacro{cite:shorthand}%
+             \global\undef\cbx@lastyear}%
+          \ifthenelse{\iffieldundef{postnote}\AND
+                      \(\value{multicitetotal}=0\AND\value{citetotal}=1\)}
+            {\bibcloseparen% Include closing parenthesis in hyperlink
+             \global\boolfalse{cbx:parens}}
+            {}}%
+          \savefield{namehash}{\cbx@lasthash}}}%
+  \setunit{%
+    \ifbool{cbx:parens}
+      {\bibcloseparen\global\boolfalse{cbx:parens}}
+      {}%
+    \multicitedelim}}
+\DeclareCiteCommand{\posscitet}
+  {\usebibmacro{cite:init}}
+  {\usebibmacro{citeindex}%
+   \usebibmacro{posscite}}
+  {}
+  {\usebibmacro{textcite:postnote}}
+
+\DeclareCiteCommand{\posscitealt}
+  {\boolfalse{citetracker}%
+   \boolfalse{pagetracker}}
+  {\printtext[bibhyperref]{\printnames{labelname}'s \iffieldundef{year}{\printfield{labelyear}}{\printfield{year}}\printfield{extradate}}}
+  {}
+  {}
+
+\DeclareCiteCommand{\possciteauthor}
+  {\boolfalse{citetracker}%
+   \boolfalse{pagetracker}}
+  {\printtext[bibhyperref]{\printnames{labelname}'s}}
+  {}
+  {}
+
+  
+\endinput
diff --git a/Master/tlpkg/bin/tlpkg-ctan-check b/Master/tlpkg/bin/tlpkg-ctan-check
index 7e8d069ab55..4665f0a38eb 100755
--- a/Master/tlpkg/bin/tlpkg-ctan-check
+++ b/Master/tlpkg/bin/tlpkg-ctan-check
@@ -118,7 +118,7 @@ my @TLP_working = qw(
     biblatex-realauthor biblatex-sbl biblatex-science biblatex-shortfields
     biblatex-socialscienceshuberlin biblatex-software
     biblatex-source-division biblatex-subseries biblatex-swiss-legal
-    biblatex-trad biblatex-true-citepages-omit
+    biblatex-trad biblatex-true-citepages-omit biblatex-unified
     biblatex2bibitem
     bibleref bibleref-french bibleref-german bibleref-lds bibleref-mouth
     bibleref-parse bibletext
diff --git a/Master/tlpkg/tlpsrc/biblatex-unified.tlpsrc b/Master/tlpkg/tlpsrc/biblatex-unified.tlpsrc
new file mode 100644
index 00000000000..e69de29bb2d
--- /dev/null
+++ b/Master/tlpkg/tlpsrc/biblatex-unified.tlpsrc
diff --git a/Master/tlpkg/tlpsrc/collection-bibtexextra.tlpsrc b/Master/tlpkg/tlpsrc/collection-bibtexextra.tlpsrc
index 4f1b32acf0c..682529ee3d2 100644
--- a/Master/tlpkg/tlpsrc/collection-bibtexextra.tlpsrc
+++ b/Master/tlpkg/tlpsrc/collection-bibtexextra.tlpsrc
@@ -77,6 +77,7 @@ depend biblatex-subseries
 depend biblatex-swiss-legal
 depend biblatex-trad
 depend biblatex-true-citepages-omit
+depend biblatex-unified
 depend biblatex2bibitem
 depend biblist
 depend bibtexperllibs