Glossary Term Audit checks glossary terms in translated note pairs

Name: Glossary Term Audit
Author: theluckystrike

Check translation paragraphs for term errors.

Install in Obsidian

Directory page Source on GitHub

MIT · no telemetry · core features free

The audit lists a missing approved term and a forbidden target term with buttons to open the notes. — Open larger

version: 1.1.0
released: 2026-10-21
downloads: 22
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

The directory takes these platforms from the plugin manifest. The automated tests run in the desktop app only.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Glossary Term Audit

Translators who keep source and target prose in Markdown notes and need to review client terminology.

Choose your source note, its translation and a glossary CSV. Glossary Term Audit compares prose blocks by position and points you to literal term findings.

A zero-finding result is a starting point for review. It doesn't certify meaning, grammar or translation quality.

Check a pair and open the target paragraph

Free features

Choose a source and a target

Search Markdown paths with the note pickers, or enter paths yourself. A completed pair check saves your selected paths and current glossary.

Load a glossary CSV

Load a local CSV or paste its text using source,approved,forbidden headers. Skipped rows appear with their starting row numbers.

The glossary input shows a skipped row warning above the pair results. — Open larger

Check literal terms in prose

The check pairs consecutive nonblank prose blocks by position. Whole terms and Ignore case start enabled; change them in settings for substring or case-sensitive checks.

Review paragraph findings

A matched source term requires its approved term in the paired target block. Forbidden target terms produce findings independently of source matches. Unequal prose counts stop the pair report.

Open a note at a result

Select Open source or Open target to move to the block start in editing view. Rerun the check after edits because saved positions describe the previous run.

The target note opens in editing view at the affected paragraph. — Open larger

The single pair workflow is free; folder checks and saved client glossary profiles need Pro.

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Folder checks Pro

Supply one folder and a CSV with source,target paths relative to it. The plugin checks declared pairs rather than guessing from filenames. A missing note stops the operation.

The folder check displays separate results for two declared translation pairs. — Open larger

Client glossary profiles Pro

Save your glossary under a client name and load it for another check. Reusing the name replaces that profile. Profiles hold glossary text, without note paths or matching options.

Open larger

See how Pro works

Set up Glossary Term Audit

needs

Obsidian 1.13.4 or later

steps

Run Check a translated note pair from the command palette.
Choose your source and target notes, then load or paste the glossary CSV.
Select Check pair and resolve skipped rows or alignment errors.
Open affected paragraphs, review the wording and rerun after edits.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to check translation glossary terms in Obsidian

Known limits of Glossary Term Audit

Equal prose block counts do not prove correct paragraph alignment.
The audit compares literal surface forms and does not recognize inflections or assess translation meaning.
Headings, code blocks, outer-pipe table lines, list marker lines and block quote lines are excluded from the prose check.
A missing note stops a folder check.
Result positions describe the previous run; rerun after editing your notes.
Physical mobile devices, Linux and Windows interaction, live GitHub sign-in and real payment were not tested for this release.

Questions about Glossary Term Audit

Will it rewrite my translation?

No. The check reads the notes and stores its own settings. You make edits in the affected note yourself.

Can it recognize inflected terms?

It compares literal surface forms. Add separate glossary rows for the forms you need to check.

Does matching paragraph count prove alignment?

No. Blocks with equal counts can still appear in a different order. Compare their contents before relying on the findings.

Network use

No requests occur before you select Sign in with GitHub; sign-in sends a client ID, scope and device codes to github.com. After sign-in, api.github.com receives token-authenticated sponsorship queries for tier and payment totals; successful checks cache seven days, failures retry after six hours. Refresh requests an earlier check; notes, paths and vault data stay local, with no telemetry.

Read the full network disclosure