Comments on: The case for and against direct update of TM’s by translators http://www.translatemyworld.com/LocalizationBestPractices/2009/05/the-case-for-and-against-direct-update-of-tms-by-translators/ global-scale localization. thought leadership, news and information Tue, 19 Oct 2010 13:07:14 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: mtpostediting http://www.translatemyworld.com/LocalizationBestPractices/2009/05/the-case-for-and-against-direct-update-of-tms-by-translators/comment-page-1/#comment-12 mtpostediting Sat, 30 May 2009 15:18:08 +0000 http://www.translatemyworld.com/LocalizationBestPractices/?p=59#comment-12 The method of automatically updating the TM, and reusing instantly afterward, doesn't fit well with those who clearly promote the traditional TEP cycle. Yet, for those who want to embrace a non-sequential crowdsourcing approach, the translators' scrum as I call it, it has its place. The type of content, and the requirement for review and proofing or not, can influence this. Much depends if the central TM with online updating is done in 1 stage, or in a 2-stage cycle by filling the main pool of TM segments, and then migrating them to a core after they have been reviewed. There is a benefit in getting reusable segments throughout the translation cycle, rather than waiting until completing a milestone for updating and then propagation. Harmonization and standardization can happen early, however, as you also point out, at the expense of missing valuable QA checks. This can lead to standardization backfire. Jeff The method of automatically updating the TM, and reusing instantly afterward, doesn’t fit well with those who clearly promote the traditional TEP cycle. Yet, for those who want to embrace a non-sequential crowdsourcing approach, the translators’ scrum as I call it, it has its place. The type of content, and the requirement for review and proofing or not, can influence this.

Much depends if the central TM with online updating is done in 1 stage, or in a 2-stage cycle by filling the main pool of TM segments, and then migrating them to a core after they have been reviewed.

There is a benefit in getting reusable segments throughout the translation cycle, rather than waiting until completing a milestone for updating and then propagation. Harmonization and standardization can happen early, however, as you also point out, at the expense of missing valuable QA checks. This can lead to standardization backfire.

Jeff

]]>