Version 1.0

As the styles are now in use without serious complaint, I am finally taking them out of beta and declaring this version 1.0.

• A new convenience field, casenumber, has been introduced to simplify use of number and oscola's userb fields for European cases.

• Internally the styles now treat the oscola fields parreporter, parseries, parvolume and parpages as fully defined fields in their own right, instead of as aliases for userb, userc, etc.

• The routine for compressing years (e.g. 2018-9) has been improved.

• Internals have been updated for biblatex 3.12.

• Fixed an edge case that would trigger the printing of empty parentheses in reports.

• Fixed bug where redundant disambiguation markers would be printed in oxalph references if using non-default date merging options.

• Fixed small bugs that biblatex was working around dynamically.

Version 0.12

The 0.12.x releases are intended as the final set of experimental releases before freezing the behaviour of the styles for version 1.0.

• Breaking change: titles of suppbook entries are now in quotation marks by default; the inverted commas must be removed by using the descriptor annotation or field, in common with other entry types.

• Breaking change: the punctuation before a ‘by Author’ statement is now configurable, and defaults to a space instead of a comma.

• Explicit handling has been added for entry types suppperiodical, suppcollection, booklet, patent, standard, artwork, performance, and letter, and examples for these have been added to the documentation. The image entry type uses the new artwork/performance driver instead of online.

• The altthesis option has been deprecated in favour of new option thesis, which takes values in (altthesis = true), out (altthesis = false) and plain (no parentheses at all).

• The varissuedate option has been renamed issuedate-plain, to match court-plain.

• There is a new bookseries option which takes values in and out with the same logic as the thesis option.

• The mergedate option can now be set on a per-type basis. Some bugs in the maximum and compact variants have been fixed.

• There is a new nonodate option for suppressing ‘n.d.’ when an entry in oxalph/oxyear has no suitable date label. It is automatically activated on a per-entry basis if a sortyear is given.

• It is now possible to annotate a date as inferred to enclose it in square brackets.

• Various edge-case formatting bugs have been fixed.

Version 0.11.3

• Fixed bug introduced in v0.11.2 into oxyear/oxalph, where the year would be printed twice if given in year field instead of date.

Version 0.11.2

• Fixed bug in oxyear where parenthetical citations would be wrongly punctuated if year given in year field instead of date.
• Fixed bug where the test for abbreviated journal names would cause errors when OT1 encoding was used.

Version 0.11.1

• Fixed bug where the option giveninits=false would cause a stream of errors for oxyear and oxalph.

Version 0.11

• Internals were updated in step with biblatex 3.8.
• New style variants oxalph (alphabetic) and oxnum (numeric) were added.
• The code underlying the mergedate option was further refined.
• Bugs in the name:family-title-given macro were fixed.
• Some issues only noticeable in the logs were fixed.

Version 0.10

This is the first version of the class to be submitted to CTAN.

• Inheritance rules for the inaudio driver were added.
• Some outstanding issues with the mergedate option were fixed.
• Compatibility with the oscola style was updated to match version 1.5.

Version 0.9

This release of biblatex-oxref is intended for testing prior to a formal release on CTAN.

The styles should be fully usable, but at this point they are still experimental in the sense that

• option names and instructions for handling certain unusual entries may change;
• I am open to adjusting the intended output of the examples (especially for oxyear).

Therefore if you have any suggestions for improvements, or think I have not interpreted the OGS/NHR correctly, there is still a chance to make a difference to the style. Please leave any feedback you may have on the issue tracker.

My hope is to make the styles fully stable from the version 1.0 release.