Translation match failure (capitalised vs all caps)

Hi,

I wonder if anyone can explain this behaviour in Studio.

I have a one-word translation segment that I have translated like this:

In fact, that translation was a 96% match with an earlier one,

So far so good.

Then, a few segments later, I have to translate virtually the same one-word segment, only the source is all caps, but this time I get no match at all:

The odd thing is that I haven't experienced this behavior in any other segments with more or less the same conditions (different word, translation match is all caps, minus the full stop).

Anyone have a clue what could cause this?

Thanks in advance.

Generated Image Alt-Text
[edited by: Trados AI at 1:44 PM (GMT 0) on 28 Feb 2024]

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Translation match failure (capitalised vs all caps) Hi, I wonder if anyone can explain this behaviour in Studio. I have a one-word translation segment that I have translated like this: https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/Screenshot-2018_2D00_06_2D00_20-20.31.11.JPG In fact, that translation was a 96% match with an earlier one, https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/Screenshot-2018_2D00_06_2D00_20-20.31.18.JPG So far so good. Then, a few segments later, I have to translate virtually the same one-word segment, only the source is all caps, but this time I get no match at all: https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/Screenshot-2018_2D00_06_2D00_20-20.34.02.JPG https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/Screenshot-2018_2D00_06_2D00_20-20.34.16.JPG The odd thing is that I haven't experienced this behavior in any other segments with more or less the same conditions (different word, translation match is all caps, minus the full stop). Anyone have a clue what could cause this? Thanks in advance.
Get AI Suggestion

AI Reply

Accept answer Reject Answer

0 Alison Field over 7 years ago

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

Generated Image Alt-Text
[edited by: Trados AI at 1:45 PM (GMT 0) on 28 Feb 2024]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 7 years ago in reply to Alison Field

Hi Alison Field , Robert Eric Carter ,

I can't see any differences either and also don't know what might effect this... unless the minimum match value is above 91% (or similar)?

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 7 years ago in reply to Paul

Acronym recognition... It spoils in such situation, as words written in CAPITALS are treated by Studio as acronyms.
This can be quite dangerous, as when you translate CAUTION to UWAGA and then use BWM with its translation "BMW", it can autopropagate all CAPS words to your target by copying them from source - treating as acronyms. Of course this happens only, it autopropagation is set to overwrite existing translations, confirm them and not ask. But sometimes exactly this setting is necessary - for example when translating an Excel table with 200,000 words and 90% of repetitions there, paid at less then 10%...

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 7 years ago in reply to Jerzy Czopik

I don't follow you Jerzy Czopik ? How does that affect whether you even get a match or not?

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 7 years ago in reply to Paul

It does. Just try to switch the acronym recognition both in project and TM settings and test again. In my case I have the same behavior as described above. 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.

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 7 years ago in reply to Jerzy Czopik

Nope... I can't reproduce this. If I start with a new TM, disable or enable acronym recognition then I still get fuzzies from the previous lowercase match.

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 7 years ago in reply to Paul

In the past I have been posting pictures of similar behavior. I cannot find them now, we're overloaded, but I will try to reproduce.

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Alison Field over 7 years ago in reply to Jerzy Czopik

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

Generated Image Alt-Text
[edited by: Trados AI at 1:45 PM (GMT 0) on 28 Feb 2024]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Alison Field over 7 years ago in reply to Jerzy Czopik

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 7 years ago in reply to Jerzy Czopik

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.

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

Generated Image Alt-Text
[edited by: Trados AI at 1:45 PM (GMT 0) on 28 Feb 2024]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

Translation match failure (capitalised vs all caps)