NoteMods

How to check translation tokens in Obsidian

As of October 2026, Obsidian Search can find tokens with exact phrases or regular expressions. You must compare the source and target tokens yourself. Translation Token Audit compares supported tokens between the same line numbers in two notes.

Updated · 2 ways compared · 2 sources

Background

A token with a changed name or a missing repeated token can pass a language review. The plugin README shows these differences as missing and added tokens.

2 ways to do it

  1. Search for a token and inspect it manually

    Search for a token such as "{name}" to find that text. Obsidian also supports regular expressions between forward slashes.

    limits
    Search locates matching text. You still need to compare the source and translated occurrences yourself.

  2. Translation Token Audit from this site

    Put one translation unit per physical line in each note and run Check translated line pairs. Review missing tokens, added tokens, unsupported syntax and unnumbered printf order.

    limits
    Different line counts stop comparison. The grammar excludes ICU messages, Apple formats and full printf syntax.
    The dialog shows two Markdown notes and the core token grammar.
    Open larger
    Install in Obsidian
    Directory pageSource on GitHub

    MIT · no telemetry · core features free

    All features of Translation Token Audit

Try it with your notes

  1. Create two plain Markdown notes with corresponding translation units on matching physical lines.

  2. Run Check translated line pairs and choose the source and target notes.

  3. Select Core, then Check tokens.

  4. Review mismatch and unsupported rows, then select Open target line for a result.

  5. Edit the target text yourself and rerun the check.

Common questions

Do blank lines change the comparison?

Blank lines inside a note count as translation units. One terminal newline counts as a file terminator, and CRLF or CR line endings become LF.

Can named tokens move within a translation?

Named and numbered tokens can move within a unit. Unnumbered %s and %d tokens must keep their type sequence.

How should I handle an unsupported result?

Inspect the expression with a tool that supports its format. Matching unsupported expressions do not make a line pass this audit.

Sources

Photo of Michael LipYou can now check translation tokens in Obsidian.

Obsidian rewards people who share. NoteMods is just me and a lot of coffee. If this guide saved you a fight with the syntax, buy me a cup.

Buy me a coffee · $5 via PayPalCard, any amount or monthlySponsor on GitHub monthly or one-time; $5 a month or $15 once also turns on Pro

The plugin in this guide