Will Trados Workbench accept the returned RTF?

Yes. Verified against Workbench 7.x and Wordfast Classic bilingual exports.

Does Fily preserve the formatting tags inside cells?

Yes. RTF control words are never sent to translation.

What about TM metadata in hidden text?

Pass-through. Match scores and segment IDs preserved.

Can I send the same file in both directions (.rtf and .sdlxliff)?

Yes. Each follows its own pipeline. The RTF pipeline is specifically for bilingual table format.

Is this format still in use?

Yes — legacy LSP workflows, agencies on older Trados or Wordfast Classic, and quick review tasks still use bilingual RTF.

RTF · AI translation

Translate RTF bilingual files. Trados / Wordfast tables intact.

Drop your bilingual .rtf — Trados Workbench export, Wordfast bilingual review file, or generic two-column RTF. Fily fills the target column and returns it with formatting tags intact.

See how it works

0RTF jobs0words processed

What is RTF (Trados bilingual)?

Bilingual RTF is the table-based exchange format used by older Trados Workbench, Wordfast Classic, and many translator review workflows. The file is a Word-compatible table with source segments on the left and target segments on the right, plus formatting tags around inline elements.

Why RTF (Trados bilingual) is tricky for AI translation

RTF tags are character sequences (\b, \i, \fs24, etc.) that look like text but break formatting if translated.

Bilingual tables are not detected by generic AI translators — they may translate the source column or both columns, corrupting the file.

Hidden text with TM metadata (match scores, segment IDs) must be preserved untouched.

Inline formatting (bold, italic, underline) appears as control words that must survive translation.

Multi-segment cells exist in some Trados exports — translating them naively loses the segment boundaries.

How Fily handles RTF (Trados bilingual)

RTF-aware parser: target column detected, source column passed through.

Control word preservation: \b, \i, \fs and friends never sent to the model.

TM metadata pass-through: match scores and segment IDs stay in hidden text fields.

Inline formatting reinserted: bold/italic/underline boundaries respected in the target.

Multi-segment cells: each segment translated independently, then reassembled with original boundaries.

Pipeline: rtf_trados@1.0.0

The RTF (Trados bilingual) workflow with Fily

Upload

Drop your .rtf (single or batch ZIP). Optional: glossary, TM, style guide.

Process

Fily runs the RTF (Trados bilingual) pipeline + 12 QA steps. Typical job: 10–20 minutes.

Download

Same format, ready to deliver. QA report HTML attached.

Common upload: a Trados Workbench bilingual RTF received from a client running legacy tooling. Fily fills the target column with translations, preserves formatting tags, and returns the RTF for direct cleanup in Workbench or Word.