Today I learned on Twitter about Massimo Ghislandi’s statements about 2014 and the translation industry, comments which fellow colleagues Jost Zetzsche and Riccardo Schiaffino qualified as interesting. Well, after reading Mr. Ghislandi’s posting, I decided that his words were more than just interesting in a way.
Mr. Ghislandi is VP of Translation Productivity for SDL Language Solutions, a large MLSP with main offices in Great Britain. Some of the news he shared in his posting are very good news indeed, like the removal of Java from MultiTerm. As a SDL Trados Freelancer user, I’m pleased with this development, as well as other minor improvements in the tool. I took issue with some of Mr. Ghislandi’s sunny assertions, particularly those regarding the role of terminology to increase the speed of the translation process and the manufactured need for a faster translation process. The following is my posted reply to Mr. Ghislandi:
After seeing cautiously complimentary Twitter comments on this article, I had to drop by and see for myself. Here are my opinions:
Adjectives in lieu of hard data smell of marketing language, not empirical observation: “huge amounts of content being created.; “it has also been an eventful year for SDL Translation Productivity and the translation industry overall.”
Unsupported statements based on subjective impressions: “The number of full time translators is also not growing at the content’s pace. I have the impression that the number of full time translators might be growing at 5-10%, while content is growing at double or triple digit rates.”
An artificial urgency to make translation faster based on a fallacy: “The gap between source content and translated content is just widening …I think we do need to find ways to translate faster so that we can try and close the gap between created content and translated content.”
Who is to say that all source content should be translated in its entirety? One rule of thumb to follow is to translate just what the customer needs, no more, not less, and not what some localization manager or sales or marketing manager ‘thinks’ the customer needs. I think that’s the more important gap.
As a professional translator myself, I am persuaded that we need to find ways to translate more slowly so that the translated content is useful, readable and actionable. It doesn’t matter what software tools we translators use, as long as we remember to take the requisite time to think before writing, which is an ability in very short supply.
About your statements on terminology: “Or is terminology seen as way to improve the speed of the overall translation process (cutting down on those review cycles!)? I am not sure.” While terminology management software is useful to keep a level of consistency, terminology by itself it not nearly enough to increase the so-called translation quality. I have seen many poorly written translations that include the right industry terminology, for example. I cannot agree with your take that terminology may be a way to speed up the translation process. We need to let go of the need for speed in translation.
Many visible people in the translation field feel the temptation to play prophet and tell us what’s in store in the future: “I guess I do need to look forward! I wish I could tell you what is going to happen next year in the translation world. Predictions are tougher to make in this agile and perhaps more volatile world.”
But not all of my comments are critical. Well done for getting rid of Java in MultiTerm.