Translation Memory

Scale your translation process using Translation Memory

Translation Memory (TM) is a core technology used across the language services sector and it should play a central role in every organization’s translation strategy. TM is a database that stores all your translations, allowing each translated segment to be re-used in future translation projects. Where content is repeated within a project (for instance in a website translation), the first translation is automatically propagated to all other instances where that content appears.

Translation Memory doesn’t just save you money – up to 50% in many projects – but time as well. In large projects this often allows you to meet tight deadlines for product or market launches that would otherwise be impossible.

TM drives consistency

TM helps to drive consistency by ensuring that previously translated content is re-used rather than translated a second time. A centralized TM ensures consistency even though you are likely to use different translators over time. For urgent projects, we may use two or more translators at the same time. Translation Memory means that the work of Translator 1 is instantly available to Translator 2.

The best TM systems feature something called Concordance Search. This helps translators search the TM and Termbase for individual words or phrases that have been previously translated.

TM drives Machine Translation quality

If you’re considering Machine Translation (MT), TM is critical to training a Machine Translation Engine for your unique brand tone and terminology. We use your TM to train an MTE to get closer to the results you would expect from human translation. TM is the foundation of high-quality MT!

Our TM, Terminology, Machine Translation and Multilingual SEO solutions work together to provide the foundations for a fully optimized translation strategy.

 

Translation memory

TRANSLATION MEMORY SPEEDS UP THE TRANSLATION PROCESS AND CAN SUBSTANTIALLY REDUCE COSTS

OUR LATEST BLOG POSTS

No Results Found

The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.

Ready To Get Started?