Project Translation

Project Translation is the main workspace in Transbox: a project is a set of files plus one language setup and one parsing/AI configuration. Every file can be opened in the editor for sentence-level work, or pre-translated, QA'd and exported in bulk.

Projects and Files

• A project has one source language and multiple target languages
• A project can hold many files; each file can override source/target languages (inheriting the project defaults)
• Each file keeps its own translations, stage status, QA and edit history
• Project progress, character counts and QA totals are aggregated from its files

File Modes

A mode must be chosen when adding a file; each mode has its own parser and export rules:

The Multilingual file mode currently supports XLIFF only; for other bilingual formats (TMX, two-column Excel), use the file tools or the memory import first.

Project List

Smart Translation → Project Translation:

• Columns: project name (with notes), language pair, file count, character count, progress bar, QA count, update time
• Search by project name or notes
• Row actions: open / settings / delete (deletes files, translations and related data — irreversible)
• New project asks for name, notes, source language, target languages (targets cannot include the source)

The Four Tabs

Files

• Add file: choose a mode → pick the file → confirm languages
• Project export / Project import translations: bulk transfer across files
• Bulk delete: select several files and delete at once
• Search by file name
• Per-file actions: Translate opens the editor; More offers Agent translate, export, import, re-parse and delete

Statistics

Select files (all or some) and a project language, then click Statistics to get, per file: total segments, duplicate segments, and TM match distribution (100% / 90-99% / 60-90% / below 60% / unmatched). Useful for quoting and effort estimation.

Overview

Totals for files, segments, characters, QA issues, translated, confirmed and overall progress, plus the most recently updated files.

Settings

• Name / notes
• Source / target languages (keep them compatible with the files)
• Parse mode: auto / locale file / document / multilingual. "Auto" infers from the extension
• Lock duplicates: when on, "other duplicate" segments cannot be edited, preventing divergent translations of the same source
• Parse config JSON: advanced parsing options (column mapping, hierarchy rules) for unusual formats
• AI assistant prompt: shared system prompt for every segment and target language in the project; empty means no system prompt

Import and Export

Export

Combine file scope, language scope and key conditions to produce:

• Translated file: original format, original structure
• Excel comparison: two columns
• XLIFF: for other CAT tools or external translators
• JSON: uniform comparison structure

Import

Accepts .json / .xlsx / .xliff / .xlf, with options for auto-confirm, writing to memory, and the target stage.

Working with Corpora and AI

• Memory: matched automatically in the editor; pre-translation can run TM-only at zero translation cost
• Termbase: highlighted and matched in the editor; LLM and Agent translation inject matched terms into the prompt
• Corpus search: the header search runs across all memories and termbases so you can confirm a rendering and return to the editor
• Agent translate: translates a whole file following the project prompt — a good way to get a first draft before human review

Notes

1. Quotas: files per project and characters per file are plan-limited
2. Deletion is irreversible: deleting a project or file also deletes its translations
3. Filter by stage before delivery: export only confirmed or published segments for clients
4. Backup: all project data lives in the local database and ships with Data backup

FAQ

Q: How does project translation relate to locale file translation?

A: Locale file is one of the file modes inside project translation. Projects handle files, progress, statistics and transfer; the locale file mode decides how those files are parsed and written back.

Q: Can one project contain Word files and JSON files?

A: Yes. The mode is chosen per file, so a single project can mix them.

Q: Do existing translations disappear if I change the project languages?

A: No. Translations are stored per language; removing a target language hides its translations but re-adding the language brings them back.

Q: Can several people collaborate on a project?

A: There is no account-level collaboration or task assignment. The practical workflow is exporting XLIFF/Excel to translators and merging their work with Import translations.

Q: What is the difference between project statistics and file analysis?

A: Project statistics targets quoting and effort (repetition rate, TM match distribution, across several files). File analysis targets delivery status for the current file and language (translated / confirmed / MT / QA distribution).

Q: Do I have to add the file again after the source changes?

A: No. Run Re-parse on that file in the file list; keys are re-extracted and existing translations are kept.