This is extremely not finished. The README here is also out of date — there are changes afoot regarding the availability of CSL-M-level features elsewhere, so for now, a CSL-M style is not being actively developed.
Citing legal materials is complicated, but the days of typing out footnotes with fiddly italics, manually managing ibid and footnote numbers and messing up by missing a comma are fading fast. This project includes implementations of AGLC4 in CSL and CSL-M, to be used with Zotero/Mendeley/many others or Juris-M respectively. This documentation aims to cover all the different ways you can use the styles to automatically produce compliant AGLC4 citations.
This documentation is generated from a test suite. Each test in the suite is associated with a particular rule with which it is attempting to check compliance. It should be presumed that an AGLC rule not found here should be entered manually in a footnote. Due to the complexity of the AGLC, it will sometimes be necessary to use the tools in an unintuitive or non-standard way — these cases are documented.
Each of the two documentation sets can be navigated using the same table of contents as the AGLC4 book itself. Many of the test cases are lifted from the book. Each rule can be linked to by clicking the anchor next to the rule title and copying the resulting URL.
This project works with two closely related but different kinds of citation processor. You can pick which documentation set of CSL or CSL-M to browse at the top of the page. They are:
Because of the different feature sets, large swathes of the AGLC can only be covered by the CSL-M variant. If you are a current, happy CSL user (i.e. you only cite Australian reported judgments, legislation, journal articles and books), you can proceed as usual. If you find yourself citing parliamentary committee hearings, foreign domestic or international materials like treaties, reports with institutional authors, the less common unreported case modes, or you’re generally hitting the edge cases in the AGLC, you may wish to switch. A project for a later date is to add a comparison chart based on the test suites.
These styles can’t really be installed through the standard channels yet. When they can be, it will be documented here.
Following is an example rule. You will notice it comprises two test cases, one of which has failed, because the result was not identical to the expected output. Rules might include documentation that explains how to get the style to do what you want, or warnings about what you must or mustn’t do for correct output.
Some notes on using this rule.
Document Type | Book |
Author | {"first":"John","last":"Doe"} |
Title | Miscellaneous Writings |
Date | 2001 |
Document Type | Book |
Author | {"first":"John","last":"Doe"} |
Title | Miscellaneous Writings |
Date | 2001 |
…
Tag | Meaning |
---|---|
passed | The style produces the correct output, down to italics and curly quotation marks. |
failed | The style gets it wrong. A diff will be shown. Be careful using the style in this way. |
stub | There was an empty test defined. |
A cite cluster looks like prefix @citekey locator label locator suffix.
You enter these with the Microsoft Word plugin and its cite entry UI, or in
Pandoc using the [prefix @citekey label locator suffix]
syntax (see the
manual for more).
A semicolon in the cluster means there are multiple cites:
prefix @citekey ; second prefix @key2.
Thanks to the University of Technology Sydney for supporting the development of the CSL-M style.