Hi Robert Eric Carter

I can't reproduce this, it works correctly for me in both Studio 2017 and Studio 2019:

Sometimes match values are lower when there are background properties to the segment that are different to those of the TM entry. This doesn't usually mean the match isn't visible at all though.

I've looked through various settings to see if there was anything that could cause these symptoms but found nothing.

Any ideas, anyone?

Ali :)

Hi Jerzy,

so, are you suggesting that a word in all capitals would be treated as an acronym and copied directly from source to target if Robert has autopropagation set to overwrite existing translations then confirm them without asking as here (not how I have it set):

(this setting is only available via File>Options, not in Project settings)

He would also have 'Acronyms' ticked here (or in the same place via File>Options if he's not working with projects):

That could do as you say on confirmation?

There's also this setting I think you're referring to?

However, how would that prevent the TM from displaying the lower-case translation in the TM results window?

All the best,

Ali :)

Hi Jerzy,

so, are you suggesting that a word in all capitals would be treated as an acronym and copied directly from source to target if Robert has autopropagation set to overwrite existing translations then confirm them without asking as here (not how I have it set):

(this setting is only available via File>Options, not in Project settings)

He would also have 'Acronyms' ticked here (or in the same place via File>Options if he's not working with projects):

That could do as you say on confirmation?

There's also this setting I think you're referring to?

However, how would that prevent the TM from displaying the lower-case translation in the TM results window?

All the best,

Ali :)