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 :)

Unknown said:

I think in case an acronym is recognized, there will be no search in TM, because it is "not necessary" - the segment does contain something not needing translation.

Ah, OK, I see what you're saying...

Robert Eric Carter can  you check the settings I included in my last post and see if they're set the way Jerzy is suggesting?

All the best,

Ali

Situation on my PC with acronym recognition off:

Same project, same TMs, same PC, but acronym recognition switched on:

Please note, that the correct translation "UWAGA" has been inserted in the segment previously, and as I realized this is the example I was looking for, I just switched acronym recognition on and returned to this segment.

Thank you all.

Jerzy Czopik was on the right track as far as "acronym recognition" goes, but Naoko Jones has suggested the exact setting that eliminates this behaviour.

I had already unticked the Acronyms box in the Auto-substitution settings, but the behavior persisted. In fact, prior to this, I was getting the results that Jerzy suggests, so I thought that might be the issue, and I unticked the Acronyms setting in Auto-substitution.

However, it was when I changed the settings as Naoko suggested here:

“Project Settings \ Language Pairs \ All Language Pairs \ Translation Memory and Automated Translation”, select the TM and click on settings. Once here:
- Go to the “Fields and Settings” sub-menu
- Disable the “Acronyms” option and press OK"

and, after reorganizing the TM, that Studio behaves normally again, giving me a 91% match that is automatically formatted in all caps.

So, thanks again you to all of you, particularly Naoko, that did the trick!

(I'm not sure of the etiquette on this forum. I posted this as a reply to the last post in the thread, but I don't know whether I should have posted it as a reply to Naoko instead.)

Thank you all.

Jerzy Czopik was on the right track as far as "acronym recognition" goes, but Naoko Jones has suggested the exact setting that eliminates this behaviour.

I had already unticked the Acronyms box in the Auto-substitution settings, but the behavior persisted. In fact, prior to this, I was getting the results that Jerzy suggests, so I thought that might be the issue, and I unticked the Acronyms setting in Auto-substitution.

However, it was when I changed the settings as Naoko suggested here:

“Project Settings \ Language Pairs \ All Language Pairs \ Translation Memory and Automated Translation”, select the TM and click on settings. Once here:
- Go to the “Fields and Settings” sub-menu
- Disable the “Acronyms” option and press OK"

and, after reorganizing the TM, that Studio behaves normally again, giving me a 91% match that is automatically formatted in all caps.

So, thanks again you to all of you, particularly Naoko, that did the trick!

(I'm not sure of the etiquette on this forum. I posted this as a reply to the last post in the thread, but I don't know whether I should have posted it as a reply to Naoko instead.)

Unknown said:

(I'm not sure of the etiquette on this forum. I posted this as a reply to the last post in the thread, but I don't know whether I should have posted it as a reply to Naoko instead.)

Hi Robert Eric Carter the important thing is you marked the correct answer as verified... this way anyone coming across a similar problem will see your question and the answer by default and won't have to scroll through all the discussions unless they want to.