Hi Iris,

Currently, one possible approach is to prepare the projects in Trados Studio using the PerfectMatch capability there. You could prepare them as local projects and then save them to the cloud using the Save To Cloud functionality in Trados Studio. Trados Enterprise will then fully honour the PerfectMatch status on the segments, include the correct numbers in any analysis reports, both Online Editor and Studio will work with the files as you know it from Studio. Having said all that, we are also working on a cloud-native version of PerfectMatch as part of our future roadmap. I can't give you an exact date at this point but it's high on our priority list. Once it's available in the cloud also, we will announce it as part of our regular product announcements.

Thanks, Daniel     

Hi Daniel,

that's what we are doing as a workaround. But since the translations are ordered via Customer Portal, I have to do it in the Cloud projects created by Trados Enterprise using the "BIlingual Engineering" task. Unfortunately according to the documentation Trados Enterprise doesn't allow a Bilingual Engineering task in the workflow before Translation Memory Matching. But that's when I have to do it. It doesn't make sense to do Perfect Match AFTER Translation Memory Matching. Do you have a suggestion how to integrate the Bilingual Engineering task to use it for Perfect Match before Translation Memory Matching?

Hi Daniel,

instead of trying to integrate Bilingual Engineering before Translation Memory Matching, PS suggested the following as a workaround: Use the Bilingual Engineering Task and do the following in Studio:

Clear Target Segments, then do Perfect Match, then do pretranslation and if needed do another pretranslation with our customised Language Weaver. Unfortunately the Pretranslation with the Translation Engine from the cloud doesn't work. I logged this as a case (no. 00812761) and was told that this is a bug and they don't know exactly when this will be fixed. Now we are running out of options. Add Bilingual Engineering before Translation Memory Matching is not allowed according to the documentation. Using Bilingual Engineering after Translation Memory Matching is not working. And the workaround you suggested doesn't work for us, as we receive our projects via customer portal from our clients. 

Do you have any further suggestions for us?

Hi Iris Düwel  - I do think we should look at why the bilingual engineering task should not be allowed before Translation Memory Matching. Trados Enterprise workflows are customizable using the workflow editor, and I am wondering why there should not be a custom task "optimize files using Trados Studio" (or similar) of type "translation" where you would be able to check out the files in Studio, apply PerfectMatch to them, check them back in before they then go on to the next stage. But I might be missing something here. I have also asked Luis Lopes  for advice on this. Thanks, Daniel

Hi Daniel Brockmann 

Is there any update on when PerfectMatch could be available in Trados Enterprise? This is something we use all the time in Studio for our product documentation and UI strings to extract only new or modified files compared to the previously translated files. We want our project managers to create projects from Trados Enterprise and not Studio to maintain consistency with our set up in the tenant.

Thanks,

Sara

Thanks Sara - tagging Luis Lopes  for an update around this.

Hi Sara, 

We're hopeful to be able to deliver this in H1 2024, no promises, but that is the plan.

Thanks,
Luis

Thanks, Luis Lopes . I'll share this update with our team and look forward to the release!

Hi Luis Lopes any update on the timeline for releasing Perfect Match in Trados Enterprise? 

Hi Sara, still the plan as above

Hi Sara, still the plan as above

Hi Luis,

I'm following this feature. Do you have any news?