Transept
Back to changelog
Platform

Free tools for translators

From the Transept team
The XLIFF ⇄ Excel converter — one of the free tools, all client-side.

Alongside the app, we shipped a small set of free tools for the file formats translation work runs on. They live at /tools, take no sign-up, and run entirely in your browser — your files never leave your device.

Added

  • A free-tools hub. /tools lists the browser-based converters, starting with three and more on the way. Everything runs client-side, so nothing is uploaded and there are no watermarks.
  • XLIFF ⇄ Excel and XLIFF ⇄ CSV. Turn an XLIFF file into an editable spreadsheet — one row per segment with the ID, source, an empty target column, and notes — translate the target column in Excel or any editor, then rebuild the original XLIFF with your translations written back in. Supports XLIFF 1.2 and 2.0.
  • TMX Cleaner & Converter. Strip broken formatting tags and duplicate segments from a translation memory, and convert a TMX file to CSV or Excel.
  • Build a glossary or style guide from a whole document. Point glossary or style-guide auto-generation at an entire document and Transept works through it in passes, refining the terminology or rules as it goes, with an up-front cost estimate and a range.

Changed

  • Per-document translation-memory settings. A document can now override the memory defaults it inherits — what gets searched and whether memory is on — with a team owner able to enforce a policy where needed.
  • Faithful exports from the content API. Markdown and JSON exports now preserve lists, tables, images, and inline formatting instead of flattening to plain text.
  • An honest “Reused” label. The memory chip that marks a block as reused from a past translation is now stricter, so it only claims reuse when the wording really matches.

Fixed

  • Translation memory works on standard runs again. A tiering bug had been silently switching memory off for standard-model batch runs; memory now applies as intended, with quality checks so reused wordings only help.
  • Failed batch runs say so. A run on an unsupported provider now fails visibly and stays re-runnable instead of quietly retrying in the background, and low-quality or empty translations are caught before they land as a block version.
  • Live progress catches up. Opening a running job’s progress a little late now replays the events you missed, so the card reflects where the run actually is.
  • Files import where you’re looking. Dropping files onto the dashboard while a project or team is open now files them there, instead of into your personal space.

Have a request or hit a snag? Ask Literess in the app, or write to [email protected].