Idea Delivered Partially

As per comments, this idea has been delivered partially:

- SDLXLIFF Toolkit app: RWS AppStore

- Working with a language variant to copy all source to target, then do replace all in target

- Working with cloud projects and Online Editor - same source/target language projects are supported when working with Trados cloud offerings

'Replace all' function in the source column of the Editor view

I don't know if I'm the only Trados user who has used / has been able to use the 'Replace all' function in the source column of the Editor view, but with the last version update to 2022 I lost this function and I really miss it. Now I only have the normal 'Replace' function which can be used to make changes in one segment only. It's basically useless, as the source segments can be edited by using the 'Edit source' function as well. I've been told that neither the 'Replace' nor the 'Replace all' function is intended behavior in the source column.

Please consider adding this feature to your future upgrades of the software, I'd really appreciate it! It would make the editing of the source file(s) directly in the Editor against the translation memories a whole lot easier and faster, as I use the 'Save source as' function to save the changes and then I return the proofread/corrected source files together with the target translations, without the need to open the source files for editing in other software. In large projects some places to change can only be spotted against the memories, so if editing cannot be done in the Editor, the source files may need to be opened and saved in other programs dozens of times - a bit clumsy in the end. I know all companies and translators have their own working methods, but this feature could be helpful for other users as well. Please consider it.

Best Regards,

Kati

JAR Kaantajat
Parents

  •  

    You probably are!  This has never been possible unless you use an app such as the SDLXLIFF Toolkit.  If you happen to have had a version of Studio at some point that did support this it was most likely not intended.  Furthermore editing the source to get a better TM match seems somewhat counter productive as you would have to edit the source every time you received a document with such non-matching segments from a customer.  The process is surely to add these different segments to your TM so that now you will get a match in future and won't have to touch the source.

    For the vast majority of customers editing the source is not something they would ever be expected to do.  Such tasks when necessary, especially in a regulated project, should be managed through change control and an updated source document should be provided.

  • in reply to Paul

    Hi Paul! I don't have the SDLXLIFF Toolkit myself. The thing about editing the source text is that I work as a translator and language professional for a company where I have to go through and correct the source texts before saving them in the translation memory. I have to keep up the high level of the original text, as the writers of them are non-native and/or non-linguistic engineers with plenty of typos and other grammatical issues, for example. Furthermore, I have to check the used terminology and correct it to correspond the recommended, perfectly written term forms. The 'Replace all' function really helped me a lot before, as the text masses handled this way can be dozens or sometimes even thousands of words in a tight schedule. If I proofread the text alone without the translation memory in the background, I cannot see all non-recommended terms or phrases that only slightly differ from each other. We try to avoid making unnecessary doubles, triples, etc. in the memories of texts that vary very little. In Finnish, the words can be written and conjugated in so many different forms, so we try to keep the source texts as coherent as possible and the translation memories are a good tool for this. Maybe my case is more special due to this background.

Comment
  • in reply to Paul

    Hi Paul! I don't have the SDLXLIFF Toolkit myself. The thing about editing the source text is that I work as a translator and language professional for a company where I have to go through and correct the source texts before saving them in the translation memory. I have to keep up the high level of the original text, as the writers of them are non-native and/or non-linguistic engineers with plenty of typos and other grammatical issues, for example. Furthermore, I have to check the used terminology and correct it to correspond the recommended, perfectly written term forms. The 'Replace all' function really helped me a lot before, as the text masses handled this way can be dozens or sometimes even thousands of words in a tight schedule. If I proofread the text alone without the translation memory in the background, I cannot see all non-recommended terms or phrases that only slightly differ from each other. We try to avoid making unnecessary doubles, triples, etc. in the memories of texts that vary very little. In Finnish, the words can be written and conjugated in so many different forms, so we try to keep the source texts as coherent as possible and the translation memories are a good tool for this. Maybe my case is more special due to this background.

Children
  • in reply to JAR Kaantajat

     

    Completely understand your usecase, but I personally don't think enabling a CAT tool is the right way to address this problem.  Getting quality source material has always been an objective for any localization workflow and is indeed very important.  But the way to manage this should be through a proper source text workflow.

    I think if you want to use a CAT tool for this the best way to manage this would be if we supported same source/target language projects.  So you work through the original source and correct it into the same language as a first step in your workflow and then use the target files from this for the source files in your multilingual projects.  You can do this now in Language Cloud, but it's not yet supported in Trados Studio (unfortunately).  So you could use Language Cloud for your preparation, download the target, corrected, files and use these as the source in Trados Studio.

    Bizarrely there is an English (Finland) variant so maybe you could use that as either the source or target language in Studio for a correction project so that at least you can do everything in Studio if you prefer that.

    I think that the way you do this now may work for you if you only have one target language from Finnish, but is surely unworkable as the number of target languages increases unless you fix the source before you start.