One-time downloads · $0.99 USD. No subscription.

Perunlight

Step-by-step guide

KvasirQA

Check bilingual XLIFF 1.2, 2.0, 2.1 and TMX 1.4 files offline in desktop Chrome and save a CSV, HTML or JSON QA report.

Offline browser app for desktop Google Chrome, tested in Chrome 152 on Linux only. Test fixtures are synthetic: files written to the XLIFF 1.2, 2.0, 2.1 and TMX 1.4 specifications. Real Trados, memoQ and Phrase exports have not been independently verified, and vendor-specific files or packages may not work. KvasirQA flags candidate issues for a reviewer; it does not certify translation quality, edit your files or replace your CAT tool.

Get KvasirQA · $0.99Try a one-minute review

See it in use

Review translation findings in kettle manuals

A screenshot walkthrough with fictional practice data. Select a step to explore.

1. Start with

Review translation findings in kettle manuals

The Brightfern practice files contain fictional manuals and one skipped no-translate unit.

Sample files and contents

The practice files in examples/ of the paid download and the free guide ZIP: brightfern-kettle-manual.en-de.xlf (segmented XLIFF 1.2, en-US → de-DE), brightfern-app.en-fr.xlf (XLIFF 2.1, en → fr-FR), brightfern-memory.en-de.tmx (TMX 1.4, en-US → de-DE) and brightfern-glossary.csv (3 terms). All text is fictional and every mistake is planted.

Practice files and guides are free. The complete app is included only where the product page says so.

2. In the app

KvasirQA 1.0.1 first start: the practice-run button, Add bilingual files panel and Review findings panel with zero counts.
Open KvasirQA.html in desktop Chrome. The Start here box walks you through the practice run: click Load practice files. Enlarge image ↗

Try it in three steps

  1. Load the four practice files and inspect the scope summary.
  2. Review number and same-source translation findings.
  3. Filter errors and open the saved HTML report.
Show every click and setting
  1. Open KvasirQA.html in desktop Chrome and click Load practice files, or add the four files from examples/ yourself.
  2. Check the summary: 3 files checked, 29 segments checked, 7 errors and 6 warnings. The Scope: line reports 1 unit skipped because it is marked translate="no".
  3. Click Numbers: segment 3 of the German manual turns “Never fill above 1.7 litres.” into “Nie über 1,5 Liter füllen.”; source number 1.7, target number 1,5.
  4. Click Same source, different translations: “Press the power button.” is “Drücken Sie die Ein-/Aus-Taste.” in segment 4 and TMX unit m1, but “Betätigen Sie den Netzschalter.” in segment 6. The Glossary check also flags segment 6, because the glossary requires “Ein-/Aus-Taste”.
  5. Choose Errors to review seven likely mistakes, then Full HTML. The saved report still includes all 13 findings: seven errors and six warnings. Open it from your downloads folder to see the complete scope.

3. The result

Inspect the result

The report lists 13 findings across 29 checked segments in three files. Seven are errors and six are warnings; the skipped unit is disclosed.

Saved KvasirQA translation QA report opened in Chrome: generated by KvasirQA 1.0.1, 29 segments in 3 files, 7 errors, 6 warnings, glossary brightfern-glossary.csv with 3 terms; tables of files checked with format, languages, segments and skipped units, findings by check, and the first finding, Numbers 1.7 versus 1,5.
The saved HTML report: files checked, counts per check and every finding, ready to reopen, print or save as PDF. Enlarge image ↗
What to check in the practice result

13 findings (7 errors and 6 warnings) in 29 segments of 3 files, with the skipped translate="no" unit disclosed, and a standalone HTML report you can reopen, print or save as PDF. The CSV and JSON reports contain the same findings. The practice files are not changed.

This fictional example is shown in the working interface and in the supplied result. Review the guide before using your own files.

See the workflow at a glance

Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.

The source says 1.7 litres. What does the translation say?

A tiny numeric change can be easy to miss in a bilingual file. KvasirQA's fictional Brightfern kettle example flags 1.7 litres becoming 1,5 litres, then shows inconsistent translations of the power-button instruction. Inspect 13 planted findings across 29 segments and export a standalone report. The supported inputs are XLIFF 1.2, 2.0, 2.1 and TMX 1.4. Findings need human review; this is not spelling, grammar or quality certification. Linux Chrome was tested with synthetic files, while real CAT-vendor exports remain unverified.

View the illustrated card
The source says 1.7 litres. What does the translation say? — the same explanation written above, with a labelled illustrative panel.
Download the full-size PNG card

Free guided exercise · about a minute

Spot a translation issue.

Read each example, then reveal the finding. These are three moments from the fictional Brightfern practice check, with mistakes planted on purpose.

This page shows fixed examples and explanations. It does not check files. The downloadable app runs the checks on your computer.

01 · Compare the numbers

Does the quantity still match?

Source · English

Never fill above 1.7 litres.

Translation · German

Nie über 1,5 Liter füllen.

German manual · segment 3

Reveal the number finding

Error · Numbers

The value changed from 1.7 to 1.5. This is more than a decimal comma: the last digit differs.

Review the intended quantity in the source, correct the translation in your translation tool, then export and check again. KvasirQA reports the location; it does not edit the file.

02 · Compare repeated wording

Same source. Two translations.

Source: “Press the power button.”

Segment 4 & memory m1

Drücken Sie die Ein-/Aus-Taste.

Segment 6

Betätigen Sie den Netzschalter.

The practice glossary specifies “power button” → “Ein-/Aus-Taste”.

Reveal the wording findings

Warning · Same source, different translations

The English sentence has different German translations across the manual and translation memory. A variation can be intentional: review the context before changing it.

Error · Glossary

Segment 6 also lacks the term required by this glossary. Decide whether that terminology rule applies, then correct the translation or the glossary in your own tools.

03 · Read the coverage

What did this check actually cover?

Files checked
3
Segments checked
29
Findings
13

Scope: 1 unit skipped because it is marked translate="no".

Reveal what the totals mean

Review · Scope

The full practice run has 7 errors and 6 warnings. A finding is a check result, not a count of distinct bad segments: one segment can trigger more than one check.

The skipped unit is disclosed and was not checked. Read coverage and omissions before relying on a report. Even a report with no findings does not prove that a translation is correct; meaning, grammar and style still need human review.

See the complete practice run and actual app screenshots
Download the free illustrated guide and these practice files

The free ZIP contains the guide and examples; the app is sold separately. The app has been tested in desktop Chrome 152 on Linux with synthetic files. Real CAT-tool exports and other platforms remain unverified.

Before you start

  • Desktop Google Chrome; tested with Chrome 152 on Linux (x86-64). Windows, macOS, phones and other browsers have not been tested.
  • The whole kvasir-qa-1.0.1.zip extracted, with KvasirQA.html kept next to its app folder. No account, licence key, internet connection or installation.
  • Bilingual files up to 50 MB each: XLIFF 1.2 (including segmented files), XLIFF 2.0 or XLIFF 2.1 (.xlf, .xliff), or TMX 1.4 (.tmx, the TMX 1.4b format). The version and namespace are checked; other versions are refused with a message.
  • Optional glossary: a UTF-8 CSV or TSV with source,target,language columns.

Your first result

  1. Extract and open

    Extract the whole kvasir-qa-1.0.1.zip into a folder you can find again. Open KvasirQA.html in desktop Chrome: drag it into a Chrome window, or right-click it and choose Open with › Google Chrome. You should see Check translations before you deliver them and a green-edged Start here box.

  2. Run the practice check

    Click Load practice files. Expect 3 files, 29 segments checked, 7 errors and 6 warnings. The mistakes in the fictional Brightfern files are planted on purpose.

  3. Review the findings

    Read the Scope: line first: it states the files and segments checked and any units skipped. Choose All, Errors or Warnings, then a check chip or search term to focus the list. Each finding gives Where and What to fix. Summary totals remain the totals for the selected checks; warnings can be intentional.

  4. Save and reopen the report

    Choose Full CSV, Full HTML or Full JSON. Every report includes all findings from the selected checks, including those hidden by severity, chip or search filters. Chrome saves kvasirqa-report-<date>-<time> files in your downloads folder. Reopen the HTML in your browser or the CSV in a spreadsheet.

  5. Check your own files

    Click Clear all, then drop your exported XLIFF or TMX files on Drop files here or choose files. Add a glossary with Choose glossary… if you have one. Fix the findings in your translation tool, export again and add the new files: a file with the same name replaces the earlier one. KvasirQA never changes your files. Open Adjust checks to select checks; its summary shows how many are enabled.

  6. Privacy and uninstall

    Files are read by Chrome on your computer; the app page blocks network requests and nothing is uploaded. KvasirQA keeps no project: to check again later, add the files again. It stores one browser setting, whether the guide is hidden. To uninstall, delete the extracted folder; saved reports stay in your downloads folder.

A worked example

Check the fictional Brightfern kettle files

Input: The practice files in examples/ of the paid download and the free guide ZIP: brightfern-kettle-manual.en-de.xlf (segmented XLIFF 1.2, en-US → de-DE), brightfern-app.en-fr.xlf (XLIFF 2.1, en → fr-FR), brightfern-memory.en-de.tmx (TMX 1.4, en-US → de-DE) and brightfern-glossary.csv (3 terms). All text is fictional and every mistake is planted.

  1. Open KvasirQA.html in desktop Chrome and click Load practice files, or add the four files from examples/ yourself.
  2. Check the summary: 3 files checked, 29 segments checked, 7 errors and 6 warnings. The Scope: line reports 1 unit skipped because it is marked translate="no".
  3. Click Numbers: segment 3 of the German manual turns “Never fill above 1.7 litres.” into “Nie über 1,5 Liter füllen.”; source number 1.7, target number 1,5.
  4. Click Same source, different translations: “Press the power button.” is “Drücken Sie die Ein-/Aus-Taste.” in segment 4 and TMX unit m1, but “Betätigen Sie den Netzschalter.” in segment 6. The Glossary check also flags segment 6, because the glossary requires “Ein-/Aus-Taste”.
  5. Choose Errors to review seven likely mistakes, then Full HTML. The saved report still includes all 13 findings: seven errors and six warnings. Open it from your downloads folder to see the complete scope.

Expected result: 13 findings (7 errors and 6 warnings) in 29 segments of 3 files, with the skipped translate="no" unit disclosed, and a standalone HTML report you can reopen, print or save as PDF. The CSV and JSON reports contain the same findings. The practice files are not changed.

Troubleshooting

The report contains more findings than the screen

This is expected: severity, chip and search filters focus your review; Full CSV, Full HTML and Full JSON include all findings from the selected checks. To change the checks themselves, open Adjust checks.

Buttons do nothing or the page has no colours

KvasirQA.html was opened from inside the ZIP or away from its app folder. Extract the whole ZIP again and open KvasirQA.html from the extracted folder. It worked when the green Start here box appears.

A file card turns red and says Not checked

Read the message, for example “not well-formed XML (line …, column …)”, “Not a bilingual file”, “No checkable segments were found”, “Unsupported XLIFF version” or “not valid UTF-8”. The other files are still checked. Re-export that file from your translation tool as UTF-8 XLIFF 1.2, 2.0, 2.1 or TMX 1.4 and add it again: a file with the same name replaces the earlier one. Use Remove on a card to drop a file from the run.

An amber Partial result line appears

Some files were not checked, or some units could not be checked: TMX units without a defined source language and units with <sub> text inside an inline code. Counts and every report cover only what was checked and list what was left out. Fix or re-export the listed files and add them again; review skipped units in your translation tool. When every file and unit was checked, the line starts with Scope: instead.

The glossary shows a red message

Use a CSV or TSV (comma, semicolon or tab; UTF-8) with one term per row in source,target,language order. Separate allowed translations with |. It worked when “… · N terms” appears next to Choose glossary….

A file is refused as larger than 50 MB

Split the project or check fewer files at a time. Exports with an embedded original document can be very large.

No findings are shown, or no report arrives

If “No findings match this filter” appears, click All or clear the search box. If a download seems missing, check Chrome’s download bar or chrome://downloads.

Changing work while files open

Clear all and Load practice example cancel pending file and glossary reads. Clear glossary cancels a pending glossary replacement. When the same filename is selected twice, only the latest selection can replace that file. A slow read cannot restore files or glossary entries after these actions.

Compatibility & limits

  • Flags candidate issues for a human reviewer. It does not certify translation quality; judge meaning, grammar, style or spelling; write changes back to your files or CAT tool; or read CAT statuses, comments or locks. A clean report does not prove a translation is right.
  • The test fixtures are synthetic files written to the XLIFF 1.2, 2.0, 2.1 and TMX 1.4 specifications. Real Trados, memoQ, Phrase and other CAT-tool exports have not been independently verified; vendor-specific files, dialects and packages may not work.
  • Tested only in desktop Chrome 152 on Linux (x86-64). Windows, macOS, phones, tablets and other browsers have not been tested.
  • Accepts exactly XLIFF 1.2, 2.0, 2.1 and TMX 1.4; other versions are refused with a message. PO, TS, TTX, bilingual DOCX/RTF and compressed project packages are not supported.
  • TMX units without a defined source language and units with <sub> text inside an inline code are skipped, counted and the result is marked partial. Units marked translate="no" are skipped and counted. The Tags check compares inline codes, not highlight markers such as TMX hi or XLIFF mrk; the text inside them is checked.
  • Consistency compares exact language pairs (de and de-DE differ). Numbers compare digits, so 3.5 and 3,50 are reported.
  • Up to 50 MB per file; performance near that limit is untested. The on-screen table shows the first 500 findings; the CSV, HTML and JSON reports contain all of them.
  • Okapi CheckMate is a capable free alternative for offline bilingual QA, and Xbench offers broader CAT-format and terminology features. KvasirQA offers a smaller browser workflow.

Need a hand?

Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.