Under Community Review

Update file function in Trados Live

Update file function (available in Trados Sudio 2021) is essential when the content of a source file was changed but not its name. 

Viktoria Nestrachuk
Parents

  • This is a feature request - to add a function to replace/update  files in Trados Live projects.

    As it stands, there is no option to delete or replace files in existing projects (which is a weird limitation considering that there are no limits to delete entire projects). This means that any new files loaded to the project have to have different names. It's a problem because, the updated files get 100% TM matches on all segments which were translated in the old file (regardless of origin - new translation, modified fuzzy, etc.). This is equivalent to deleting the project and recreating the project - segment statuses get lost.

    The need to replace files may arise from source file updates (work in progress) or due to incorrect preparation (same file but some text may be hidden or formatted differently). 

    The update of the file should replace the original file with the same name.

    For this function to have any real purpose and use it should work so that the new file should receive the same translations and segment statuses in matching segments (those that were not changed between files). Otherwise if the new file is pretraslated from TM disregarding the statuses of the previous file version, the segment origin would be lost and it would be impossible to tell what segments were newly translated, which were fuzzy matches - all segments from TM would get 100% match  status, which makes it impossible for the editor to check what is new translation and it would defeat the whole purpose of the function as it would be equivalent to deleting the project and creating a new one with updated files. 
     

Comment

  • This is a feature request - to add a function to replace/update  files in Trados Live projects.

    As it stands, there is no option to delete or replace files in existing projects (which is a weird limitation considering that there are no limits to delete entire projects). This means that any new files loaded to the project have to have different names. It's a problem because, the updated files get 100% TM matches on all segments which were translated in the old file (regardless of origin - new translation, modified fuzzy, etc.). This is equivalent to deleting the project and recreating the project - segment statuses get lost.

    The need to replace files may arise from source file updates (work in progress) or due to incorrect preparation (same file but some text may be hidden or formatted differently). 

    The update of the file should replace the original file with the same name.

    For this function to have any real purpose and use it should work so that the new file should receive the same translations and segment statuses in matching segments (those that were not changed between files). Otherwise if the new file is pretraslated from TM disregarding the statuses of the previous file version, the segment origin would be lost and it would be impossible to tell what segments were newly translated, which were fuzzy matches - all segments from TM would get 100% match  status, which makes it impossible for the editor to check what is new translation and it would defeat the whole purpose of the function as it would be equivalent to deleting the project and creating a new one with updated files. 
     

Children
No Data