Export Verification (Word-Count Check)

Whenever you export a translated document, Supervertaler runs an automatic safeguard that checks whether any text was lost on the way out. It is a safety net against the rare case where the round-trip drops content that is present and confirmed in the grid. It started with Word files and, since v1.10.372, covers every format the Okapi merge writes back: DOCX, PPTX, XLSX, IDML, HTML, XLIFF and PO.

What it does

After writing the file, Supervertaler:

Counts the words it expected to write – the target text of every segment, falling back to the source text for any untranslated segment.
Counts the words actually present in the exported file – in a DOCX, for example, the document body, headers, footers, and foot/endnotes.
Compares the two. If the exported file contains noticeably fewer words than expected, it shows a warning.

Tags, numbers, and punctuation are counted the same way on both sides, so a genuine loss of text shows up as a clear shortfall while incidental formatting differences stay within tolerance.

Each format is counted generously, so that a clean export is never flagged:

In HTML, text in alt and title attributes (and similar attributes that get translated) counts.
An untranslated XLIFF or PO unit counts its source text, just as an untranslated segment does on the expected side.

When it runs

Automatically, after Project → Export → Export Translated Document… for DOCX, PowerPoint (PPTX), Excel (XLSX), InDesign (IDML), HTML, XLIFF and gettext PO files – whether the file is built through the Okapi merge or the standard DOCX exporter.
On multi-file DOCX exports too. These produce a single combined warning listing each affected file, rather than one dialog per file.
Other exports, such as plain text and the CAT-tool bilingual formats, aren’t checked: a format Supervertaler can’t count is skipped rather than guessed at.

The warning

If a file falls short, you’ll see a Possible Missing Text in Export dialog naming the file(s) and roughly how many words appear to be missing. The same result is written to the log, for example:

🔢 Export word-count check [Manual.docx]: 4065/4060 words (100%; threshold 95%)

or, when text looks lost:

⚠️ Possible dropped text in export: Manual.docx has only 85% of the expected words – review before delivery.

When you see the warning, open the file and check it before delivering.

Adjusting or turning it off

The check is configured in your settings.json file, under an "export" section:

Key	Default	Meaning
`word_count_check_enabled`	`true`	Set to `false` to turn the check off entirely.
`word_count_check_threshold`	`0.95`	Warn when the exported file has fewer than this fraction of the expected words. Raise it (e.g. `0.99`) for more sensitivity, lower it to tolerate larger differences.

{
  "export": {
    "word_count_check_enabled": true,
    "word_count_check_threshold": 0.95
  }
}

If your documents legitimately differ a lot from the segment word count – for example they contain many numbers, or comments that aren’t part of the translation – you may prefer to lower the threshold slightly to avoid false alarms.

🤖 These docs are AI-readable: llms.txt · full · Workbench only