Skip to content

Releases

1.14.2

Choose a tag to compare

@github-actions github-actions released this 20 Nov 09:07

Fix: the right suggestions after Ibid.

After "Ibid", the inline hint suggested "Article title", because "Ibid" was also read as the author of a journal article. Now, once you have typed something that identifies the kind of citation (such as "Ibid", or the "(n" of a later reference), only that kind is suggested:

Typed Suggestions
Ibid nothing required; optionally a pinpoint or judge, or end the footnote
Ibid 45 optionally a judge, or end the footnote
Ibid. nothing: the footnote is finished

A footnote that ends in its full stop is treated as finished, so no suggestions appear after it.

1.14.1

Choose a tag to compare

@github-actions github-actions released this 20 Nov 07:00

Fix: the page preview shows every line when it first opens.

When the page preview was opened, it could show only the headings and one line of each paragraph until you pressed Refresh. This happened because it measured the text before Obsidian had laid out its pane (while the pane was still opening, or in a tab not yet shown), so every paragraph measured as one line. Now the preview waits until the pane is laid out, showing "Preparing pages…" in the meantime. It also loads the font before measuring, so the first layout matches a refresh.

1.14.0

Choose a tag to compare

@github-actions github-actions released this 20 Nov 02:21

Fix: no large gap at the bottom of a page before a heading.

A heading has to stay on the same page as the start of its paragraph. Before, the heading needed two lines of its paragraph under it at the bottom of a page. When they didn't fit, the heading moved to the next page and left up to four lines empty. Now a heading needs only the first line of its paragraph, so it stays at the bottom of the page. On a test essay, the gaps fell from 28–61 pt to 2–20 pt (at most one line).

This uses Word's own setting. The first paragraph after each heading has Widow/Orphan control off (Paragraph → Line and Page Breaks), so Word lays out the export the same way, and you can see or change the setting in Word. The page preview follows the same rule.

New: a fuller example essay. Create example essay now adds a five-page critical analysis essay, Native Title after Mabo: Recognition, Extinguishment and the Limits of the Common Law. It shows:

  • Headings: all four AGLC4 heading levels.
  • Sources: about 30 real sources:
    • cases (authorised reports and medium neutral citations);
    • Commonwealth and state legislation, and the Constitution;
    • a parliamentary debate;
    • a treaty and a UN declaration;
    • books, a chapter in an edited book, a journal article and law reform reports.
  • Referencing: signals, short titles, Ibid and (n X).
  • Also included:
    • a long quotation;
    • a bibliography on export;
    • paragraph guides for a critical essay;
    • a practice part of citations with mistakes to fix.

1.13.2

Choose a tag to compare

@github-actions github-actions released this 20 Nov 01:31

New donation link. The plugin's Donate button in Obsidian (Settings → Community plugins) now offers Buy me a coffee as well as Patreon. If AGLC4 Citations saves you some footnote pain, a coffee is appreciated...or don't, no presh.

The plugin's code is unchanged since 1.13.1.

1.13.1

Choose a tag to compare

@github-actions github-actions released this 19 Nov 23:20

Fix: the paragraph guide carries on when a paragraph does.

When a paragraph had more sentences than its guide, the guide stopped and said the structure was complete. That happened, for example, after the thesis in an introduction written as one paragraph. Now the guide carries on into the section's next guide, in the same paragraph:

  • Introduction: the thesis is followed by the roadmap.
  • An essay part: its opening is followed by a PEEL body paragraph.
  • Rule: the principle, then how the courts apply it, then exceptions.
  • Application: one element, then the next, then the other side.
  • An issue written without sub-headings: Issue, Rule, Application, then Conclusion.

"The structure is complete" now appears only after the section's last guide.

Also fixed:

  • The next paragraph gets the guide after the one the previous paragraph ended in. A roadmap written in the first paragraph is not suggested again in the second.
  • A guide chosen with ‹ › in the middle of a paragraph now starts at its first sentence.

1.13.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 22:48

New: change the paragraph guide when a paragraph needs something else.

The guide expects the usual order, but a paragraph often needs a step skipped or repeated, a sentence the guide doesn't list, or a different kind of paragraph altogether. You can now change the guide for the paragraph you are writing:

  • Write another sentence of the guide next. Click or tap a sentence in the guide. The guide keeps counting from there: jump to Reasoning, finish it, and Mini-conclusion is next.
  • Write a different kind of sentence. Click ⟳ on the highlighted sentence to see another kind of sentence in its place, and again for the next. After the last, it comes back to the guide's own sentence. When a paragraph runs past the guide's last sentence, ⟳ offers these for the next one.
    • In problem answers:
      • a second authority;
      • a qualification;
      • statutory interpretation;
      • distinguishing a case;
      • an alternative argument;
      • a missing fact;
      • evidence and burden;
      • policy;
      • a transition.
    • In essays:
      • an example;
      • a second authority;
      • a contrast;
      • a concession;
      • a qualification;
      • a definition;
      • policy;
      • reform;
      • a transition.
  • Switch to another paragraph guide. Click ‹ › next to the guide's title to see the section's other paragraph guides. For example, use them when you're writing the other side's argument rather than the next element.

These choices last while you write the paragraph, and are never saved.

Each action also has a command, so you can give it a hotkey:

  • Paragraph guide: next sentence and previous sentence;
  • Paragraph guide: another kind of sentence;
  • Paragraph guide: next paragraph guide and previous paragraph guide.

Your own prompt sets can list their own kinds of sentence under ## Alternatives.

1.12.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 22:40

Paragraph prompts are now a guide that stays while you write, sentence by sentence.

Above the paragraph you are writing, a small guide shows what the paragraph should do and how to build it, sentence by sentence. The sentence you are writing is highlighted. When you finish a sentence, the next is highlighted, and when you start a new paragraph, the guide moves to it. Before, the prompt was a single line at an empty paragraph, and it disappeared as you typed.

Every prompt has been rewritten with its sentence structure. For example, the first paragraph of an Application:

  1. Topic sentence: the element ("The first question is whether …").
  2. Facts ("Here, …").
  3. Comparison with the closest case ("As in …" / "Unlike …").
  4. Reasoning.
  5. Mini-conclusion ("It is therefore likely that …").

The guides cover each part of an answer or essay:

  • Rule:
    • the principle, its source and its elements;
    • how the courts apply it;
    • exceptions and defences.
  • Application: each element, then the other side's best argument and how strong it is.
  • Essay body paragraphs: PEEL (Point, Evidence, Explanation, Link). Each part of an essay opens with its claim and a signpost.
  • Introductions: the issue and your thesis, then a roadmap with scope and definitions.
  • Also covered:
    • counter-arguments, evaluation and conclusions;
    • the overview and overall advice;
    • MIRAT's material facts and arguments;
    • HIRAC's issue headings.

New setting: Guide shows. Choose every sentence (the default) or only the current sentence, for a smaller guide.

Your own prompt sets can now give each paragraph its sentences, as list items indented under it. Sets made with 1.11.0 still work.

The guide is drawn by the editor and never written into your note, so it can't reach an export or the word count. It works offline, with no AI.

1.11.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 21:27

New: paragraph prompts for legal essays and problem answers.

Turn on prompts for a note, and a faint reminder of what that part of your answer should do appears at each empty paragraph. It disappears as you type. Prompts are never written into the note, so they can't end up in your submission, an export or the word count. Notes without prompts are unchanged.

Problem questions:

  • IRAC
  • ILAC
  • HIRAC
  • MIRAT

Essays:

  • Critical analysis: thesis, supported points, counter-arguments, conclusion.
  • "Discuss": both sides, evaluation, and a conclusion that answers the question as asked.

The prompt follows where you are:

  • Each section has its own prompts. For example, under Rule: state the rule as a general principle, with its source cited in AGLC4. Under Application: apply each element to the facts, then follow or distinguish the cases, then deal with the other side's best argument.
  • Essay body paragraphs follow PEEL: Point, Evidence, Explanation, Link.

The prompts follow the advice of Australian law schools' writing guides: Southern Cross University, Monash University Library, ANU and UTS Law. The guide lists them. Your lecturer's instructions always come first.

New commands:

  • Choose paragraph prompts for this note: sets the note's property aglc-prompts.
  • New legal essay or problem answer: creates a note with the outline for the kind you choose, and its prompts.
  • Copy a prompt set to edit as your own: lets you write your own set (for IPAC, CLEO, or your subject's structure) as an ordinary note. Each heading is a section and its list items are its prompts.

Show paragraph prompts in settings hides them in every note.

As always, everything works offline, with no AI: the prompts are fixed text.

1.10.2

Choose a tag to compare

@github-actions github-actions released this 19 Nov 12:44

Fix: no large gaps at the bottom of pages.

Keep footnotes on one page (on by default) now keeps only short footnotes whole: those up to two lines, such as a citation with a long web address. When one does not fit at the bottom of a page, the line citing it moves to the next page with it, as before.

Longer footnotes now continue at the bottom of the next page, as Word does. Before, they pushed their line, and the text after it, onto the next page, sometimes leaving most of a page empty.

Measured with the page preview (which matches Word's page breaks):

Document Before Now
The example essay 106 pt (about five lines) 3 pt
A document with long footnotes 307 pt (about fifteen lines) 8 pt

The Word export and the page preview use the same rule, so they still agree. Your settings are unchanged.

1.10.1

Choose a tag to compare

@github-actions github-actions released this 19 Nov 10:59

AGLC4 Citations returns to the code of 1.9.3. It is now a fully separate project, as part of a suite of plugins for students.

Removed:

  • The optional sharing of citations with Legal Core (Australia), added in 1.10.0. Legal Core is now developed separately, as the foundation for plugins for legal professionals. Legal Core was never in the community directory, so nothing you use changes.

Unchanged:

  • Everything else works exactly as in 1.9.3 and 1.10.0: checking, footnotes, export, import, version history and the example essay. The released main.js is identical to 1.9.3's.
  • Your settings load as before. The setting 1.10.0 added for sharing is simply ignored.
  • The plugin remains fully offline and AI-free. Verify the build with gh attestation verify main.js -R blursedperf/obsidian-aglc4.