Translation Tools

Translation Memory (TM)

Nowadays, a TM that makes existing translations accessible and therefore makes the translation quicker and cheaper is a must-have. It should be developed as a server-based solution so that all translators can simultaneously access the same database. This optimizes usage and ensures consistency.

Examples: Across, Trados, DéjàVu, Transit

File Transfer

For larger and/or continuing projects in particular, a lot of effort is required for the transfer and management of files. By automating this process, we can save a lot of time and money. Some TMs also deliver workflow components but customer-specific solutions are often required for this (see right).

Machine Translation

MT makes sense for large projects. However, its use should be carefully considered and planned. If applied properly, MT will deliver savings and service extensions.

Editors/DTP

Of course, translation and localization companies also require editors and layout programs in order to prepare the source materials and to give the finishing touches to the translated material.

Examples: MS Word, Open Office, FrameMaker, InDesign, QuarkXPress

You are here: Home Next FAQ Next Translation Tools

Near or Far

Do I need a GMS?

Customers who have a large amount of text often use a CMS (Content Management System) to manage this and they ask themselves, rightly so, whether they can extend the workflow that they already use in the CMS to include translation, using either the GMS (Global Management System) or using the TM servers that are directly connected to the CMS.

The theory is impressive, but it has serious disadvantages:

As the customer, can I (and do I want to) manage and monitor the translation process chain the whole way to the translator in China?
What happens during an update of the CMS or its counterpart (GMS/TM server)? Does the link continue to work?
Can I switch providers (either for the translation or the technology)? Can I easily transfer my solution?

Does it make more sense to use a defined interface to link the customer environment and the translation environment with each other? In this case, other providers, other CMS systems (for example, subsidiaries) and so on can be integrated and updates or software changes can be implemented a lot more easily.