Multimodal TM vs Legacy Translation Memory

Quick answer — A legacy translation memory holds sentence pairs from one file format in one language direction and matches on characters. A multimodal memory spans every format, matches on meaning as well, and works in any language direction.

Vitra.ai Universe runs multi-tenant, in a dedicated region, or fully air-gapped.

What legacy memory was built for

Documents. Specifically, translating a document from one language into another and reusing the sentences next time a similar document arrives.

Inside that scope it works well, and it is why the technology has lasted.

Outside it, three assumptions start to cost money.

The three assumptions

Character matching is the expensive one day to day. Edit a sentence lightly and a legacy memory scores it as new work, so you pay again for wording that was already approved. Semantic matching survives the edit.

Directionality is the one people discover late. A match earned translating English into Tamil is unavailable when a Tamil source needs Hindi, because it was stored as a pair rather than as a row per language. Coverage stops compounding exactly when the language set gets interesting.

The format assumption is the expensive one

Most organizations do not have one memory. They have several, one per tool, because the subtitling tool and the document tool and the web connector each keep their own. So a claim approved by legal for the website is retranslated for the app, retranslated again for the PDF, and voiced differently again in the dubbed video. Four surfaces, four wordings, one approval that only ever reached one of them.

A memory every modality reads and writes removes that by construction rather than by process.

What stays the same

Import and export. Existing memories move in over TMX and should move out the same way — a memory you cannot export is a lock-in dressed as a feature.

Glossaries still pin the terms that must not vary, and they still outrank a general match. Reviewer corrections still write back, which is what makes the next job start further ahead than the last.

The mechanics are familiar. The scope is what moved, and consistency across formats is what it buys.

FAQ

What is the difference between multimodal and legacy translation memory? Legacy memory holds sentence pairs from one file format in one language direction and matches on character overlap. Multimodal memory spans video, audio, images, documents, web and app, and matches on meaning too.

Why does character-based matching cost more? Because a lightly edited sentence scores as new work. You pay again for wording that was already approved and reviewed, where meaning-based matching recognises it as a match and reuses it.

What does row-per-language storage change? Coverage compounds across the whole language set. A match earned translating English into Tamil is available when Tamil content needs Hindi, instead of being locked to the direction it was created in.

Can existing translation memories be migrated? Yes, through TMX import, and they should be exportable the same way. A memory that cannot be exported in a portable format is a lock-in rather than an asset you own.