Translation Validator
Catch translation errors before they ship
Start new thread

Translation Validator - Catch translation errors before they ship

by•
A translation file linter that checks XLIFF, Qt Linguist, and Gettext files. Find broken placeholders, mismatched brackets, duplicate translations, suspicious lengths, and 25+ other potential issues in seconds.

Add a comment

Replies

Best
Maker
📌
Translation mistakes are easy to overlook during human review, especially when placeholders, brackets, URLs, numbers, or inline markup are involved. i18nlint checks every translation against its source text and highlights structural or formatting differences that may cause broken interfaces, confusing copy, or runtime problems. It supports XLIFF 1.2 and 2.x, Qt Linguist files, and Gettext files, including plural forms and inline markup. With more than 25 configurable checks, i18nlint can detect: - Missing, additional, or malformed placeholders - Mismatched brackets and punctuation - Changed URLs, email addresses, currencies, and numbers - Suspiciously short or long translations - Duplicate and inconsistent translations - Whitespace and formatting problems - Untranslated entries Upload one or more files, choose the checks you need, and receive a clear HTML, CSV, or SARIF report. Uploaded files are deleted immediately after processing and are never retained. You can start for free, with no credit card required.

The Qt ts file support caught my eye since that format is a pain to audit manually. One thing that would help a lot is a CI-friendly mode that exits with a non-zero code when issues are found, and ideally a flag to filter by severity so I can block merges only on errors but still see warnings in the logs.

Maker

 Thanks! That's already supported. If the tool finds at least one issue with error severity, it exits with a non-zero exit code, making it suitable for CI pipelines.