Translation review is the final stage of the translation workflow, by no means less important than any of the steps before. After all the job is done, you still need to make sure that the translation is accurate and your product or service is really ready to conquer the global market. It sounds easy, but every stage has its challenges. What are the challenges of the translation review and how to overcome them? We’ll discuss it in this blog, by using the example of your business website.
Challenge #1: Context
Let’s imagine having to localize your website into 10 languages. You agree on the prices with the language services provider, send over the website exported in a handy format (e.g. XML), and the projects are kicked-off. The translators working on the localization are hand-picked native speakers of the target languages, and they work tirelessly on providing the translation within the given deadline.
What happens then? The moment a translator hits a string which reads “Deliver to <placeholder>”, they will hit a bump in the road. This goes beyond the quality of the translator. Translators are good at localizing content which they can read and understand. In cases like this, however, they lack context.
The next logical step for the translator would be to reach out to the project manager. Assuming that the PM knows what the placeholder stands for, and where the string is actually located on the website, this could be quickly resolved. The thing is, the PM will also need to contact the client and ask for help, then wait for the client’s feedback, and then notify the translator.
Challenge #2: Translation quality control
A second issue which will quickly arise is terminology questions. Even if the client and the PM prepared a list of terms for translators, they did not prepare a list of all the terms which could potentially come up as problematic. This again means that the PM will have to act as a liaison between the translator and the client. Mind you, this is still the traditional translation phase of the project.
Things will get very interesting after the delivery of the translated XML files. Once the client imports the translations back into their system, it will become obvious that certain parts are too long, breaking the layout of the page.
The client will then have to do another translation review and prepare feedback for the translators, who will then implement the changes. This whole cycle can take days, if not weeks, depending on the scope of the project, not counting the second phase of the review, when the corrected files are again received.
Challenge #3: Central collaboration space
Now, the people + technology part. While looking at the challenges above, you’ll probably have a few questions coming to your mind. Why does everything have to be done via email? Can’t we somehow provide context to the translators?
Could the terminology be online and adjustable? Can the review be done in the same tool as the translation to save time? Do reviewers need to wait for the translation to be finished? The list can go on for some time.
How to overcome translation review challenges?
All the issues caused by the challenges mentioned above can easily be resolved with an online Translation Management System, such as Text United.
Using the same example, this is what would happen with a website translation project set up using our system:
- The website would be crawled using the URL, eliminating the need for files
- Translators and client’s reviewers would be allocated to the project within our platform
- Translators can start working on within our Overlay Editor, which enables them to translate within the actual website, eliminating context issues
- A glossary of all the most important terms would be generated automatically by our system
- Translators and reviewers would both have access to the glossary and could work on the terminology together, accepting, rejecting, and commenting on terms
- Our built-in comment function would enable translators and reviewers to talk about the individual strings, as if it was a chat within our system, eliminating the need to emails
- Reviewers could access the cloud-based editor from any browser, at any time, and review the project as it moves along, eliminating the need to wait for a final version of the translation
- Built-in QA tools can check automatically if the terminology has been properly used, if all the numbers in the source and target match, if placeholders have been tampered with, etc., eliminating the need for manual checks of all string and terms
- Once the translation is finalized, it can be placed online almost with the press of a button, without the need to import back the files and check everything from the beginning
Which of these two approaches sounds better?
If you want to try the second approach yourself, you can! Register here and get a 14-day free trial of the Text United TMS. You can invite your own team, set up your website translation project, and check all the above-listed things yourself.
As always, there are no strings attached. If you do need guidance, or want to ask some questions, let us know and we will gladly help!