Hi Edward Carandang,

This is not a feature that is enabled out of the box for TM providers.  We will review this internally and identify the requirements in enabling this feature for Third-party TM providers.

Internal tracking ID: SDLCOM-3660

Patrick Andrew Hartnett

Hi Patrick, thank you for your response. When you said "This is not a feature that is enabled out of the box for TM providers", did you mean we cannot accomplish it even through custom code? Or we can accomplish it albeit we need additional work outside the box?

Hi Edward Carandang, this will require a more conclusive investigation which we will pick up once we have more capacity in our team. My initial impression is that it should be possible, but requires the TU's to include tokentization of the segments in the search results.  Features related to tokenization of the segments are derived from language processing which is not publicly available, from what I see now.

We will need to review this fully of course and identify if we can provide you with sufficient information (including an example where necessary) of the requirements in accomplishing this and/or if we need to add an API change proposal request with the Studio team etc...

Hi Patrick Andrew Hartnett, thanks for the info. Will wait for the outcome of your review.

Hi Edward Carandang ,

As I've said in another thread as well,

We've found a way to show differences between TUs in third party TM providers. It involves a bit of reflection, but we've hidden that away.
Long story short:
- we've created a sample project that shows just how simple it is to use in your own project - github.com/.../SimpleTranslationProvider
- the key class is "ComputeSearchResults" that pretty much abstracts away all the complexity
- to see how to use it, please check out MyTranslationProviderLanguageDirection.SearchSegments
- obviously, we've made the code public, so you can extend/tweak it to your liking

The core idea is you have an original text (in the source language), and a resulting text (what actually got translated). The code we've provided properly computes the differences between them, so that the differences are shown in the UI.

To quickly see everything in action, just run the sample project:
- Open the sample project from Trados Studio 2022
- go to Project Settings >> ... Translation Memory and create a Translation Provider, and Automated Translation, select "Use", and select "smtiti".
- Open the SecondSample.docx.sdlxliff file
- Select with the 1st, 2nd, and 4th segments
- Do note that in our simple sample, you should ignore the translation itself. Please focus on what needs to be done on the source segments

Finally, I'd love to hear your thoughts! Please let me know if this works for you.

Best,
John