What a round trip does to a gettext file.
On our comparison pages we say what two command-line translation tools did to a real gettext file. This is how we know. We read two catalogs through each tool's own file code, wrote them back with nothing translated, and compared the result with the original. A file that goes in untouched should come back identical. Everything is here, so you can run it yourself and check our work.
Tools tested
| Tool | Version | Code under test |
|---|---|---|
| lingo.dev | 0.138.9, its legacy command-line tool (v0, which Lingo.dev now marks deprecated; the npx lingo.dev flow) | Its PO loader, called the way its command-line tool calls it |
| languine | 3.1.4, the version npx languine@latest installs | Its PO parser, called the way its command-line tool calls it |
| gettext-parser | 8.0.0, the library lingo.dev builds on | Called directly, as the baseline |
Neither tool offers its file code as a library, so the script cuts each one byte for byte out of the package published on npm and records a SHA-256 hash of every slice, which you'll find below. We ran lingo.dev 0.138.4 and languine 4.0.1 as well: their gettext code is byte-identical to the versions above, and so was every file they wrote. The run was on 6 October 2026.
The two catalogs
The French catalog is 104 lines for a made-up Phoenix shop, written the way mix gettext.mergeand a couple of years of translators leave one: a header with twelve fields, translators' notes, extracted comments, references and flags, a fuzzy entry with its previous text, two entries that share the English “Order” but not their meaning, plurals, a wrapped paragraph, escaped quotes and two obsolete entries.
The Polish catalog is its 48-line sibling. Polish has three plural forms, which shows whether a tool can hold more than two. Both catalogs pass msgfmt --check.
Results
| The French catalog | Original | lingo.dev | languine |
|---|---|---|---|
| Lines | 104 | 95 | 23 |
| Header fields | 12 | 12 | None |
| Comment, reference and flag lines | 40 | 40 | None |
| Plural forms | 4 | 4 | None |
| “Order” button and heading | Apart | Merged, and a translation changed | Merged |
| The wrapped paragraph | Wrapped | On one line | Gone |
| Obsolete entries | 2 | None | None |
| Valid gettext (msgfmt --check) | Yes | Yes | No |
lingo.dev kept more than most, and its output is valid gettext. It lost the obsolete entries and put the wrapped paragraph on one line. It also keys each entry by its English alone, so the checkout button and the order-history heading, which share “Order”, took one slot, and the heading's “Commande” replaced the button's “Commander”.
On the Polish catalog, an update leaves the third form behind. The script changed every string lingo.dev read, as a translator would, and wrote it back. The first two plural forms changed. The third, the one Polish uses for five or more, kept its old text, and nothing said so.
languine wrote back 23 lines of the 104, without the header, the comments, the plurals or the wrapped paragraph, and with its quotes unescaped, so msgfmt no longer reads it as gettext.
Dialecto isn't in the table because it never writes a file from what it parsed. It changes the lines you edited and leaves the rest of the file as it was.
Untested tools
Lingo.dev's newer command-line tool, @lingo.dev/cli 1.16.0, has no gettext code in its package. It uploads each file to Lingo.dev's servers, which parse it, and writes back what comes down. Testing it would mean an account and sending these files to a third party, so we haven't, and we claim nothing about it either way. If you run it, we'd like to see the diff.
Tolgee keeps your strings in its database and writes files from it when you export. We didn't run a Tolgee server, so Tolgee isn't in the table. We read its exporter's source instead, at version 3.226.0.
Reproduction steps
Download the files into one folder, keeping fixture/ and out/ besiderun.mjs, then run:
npm ci --ignore-scripts
node run.mjsIt needs Node 20 or later, and GNU gettext's msgfmt for the validity check.--ignore-scripts keeps the packages' install scripts from running, and the script runs nothing of theirs but the slices it cuts out.
- fixture/messages.fr.pothe French catalog, 104 lines
- fixture/messages.pl.pothe Polish catalog, 48 lines
- run.mjsthe script
- package.jsonthe exact versions
- package-lock.jsonthe full dependency tree
- out/summary.mdevery count, the hashes and the msgfmt verdicts
- out/lingo.dev@0.138.9.fr.diffthe French, through lingo.dev
- out/lingo.dev@0.138.9.update.pl.diffthe Polish update, through lingo.dev
- out/languine@3.1.4.fr.diffthe French, through languine
- out/gettext-parser.fr.diffthe French, through gettext-parser
The slices' SHA-256 hashes, as the script printed them:
- lingo.dev 0.138.9, src/cli/loaders/po/index.ts
- 64979dd8df5882691fca4b4f0f94d0046d471984d88325da04ea89fb1281c345
- lingo.dev 0.138.9, src/cli/loaders/_utils.ts
- ef3a3adce82ea10bbae257a4ab8826b7b25bb4e1c81b40a8530cd6fa259b7072
- languine 3.1.4, src/parsers/formats/po.ts
- 03b8c7173e7f178355969d5302bb92c47ade665a9e4c26886eec25cf7e94d069
- languine 3.1.4, src/parsers/core/base-parser.ts
- 4c00e87aeadfcfd65fc08ddc0acf8594bc6251b15fe03c9087369a9ca6e6468c
Corrections
Tell us at info@dialecto.eu. We'll run it again, and correct this page and every page that cites it.