• State Verified Answer
  • Replies 15 replies
  • Answers 4 answers
  • Subscribers 432 subscribers
  • Views 4829 views
  • Users 0 members are here
Options
Related

Translation match failure (capitalised vs all caps)

Robert Eric Carter

Hi,

I wonder if anyone can explain this behaviour in Studio.

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

Trados Studio screenshot showing a translation segment 'Importante.' with a 96% match 'Important.' highlighted in green.

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

Trados Studio screenshot displaying the Project Settings with a translation match 'Importante.' to 'Important.' highlighted in green and orange.

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:

Trados Studio screenshot showing a translation segment 'IMPORTANTE' with no match found, highlighted in blue.

Trados Studio screenshot displaying the Project Settings with a message 'No match found' in a white box.

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]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Jerzy Czopik

    Situation on my PC with acronym recognition off:

    Screenshot of Trados Studio interface showing a translation project with acronym recognition off. The segment 'ACHTUNG' is not translated to 'UWAGA'.

     

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

    Screenshot of Trados Studio interface showing the same translation project with acronym recognition on. The segment 'ACHTUNG' is correctly translated to 'UWAGA'.

     

    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.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 1:45 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Jerzy Czopik
    We happened to come across the exact same issue before.

    In order to address this behavior, you need to go to the “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
    - Re-select the same TM and go to the “Performance and Tuning” submenu
    - Click on the “Re-index Translation Memory” button, wait for the TM to be re-indexed and press OK

    You can now go back to the same segment you point out in your screenshot and you’ll see that the 100% match is there.

    Thanks,
    Naoko
  • 0 in reply to Naoko Jones
    Thanks ,

    I could not repro this because I had a clean TM and reindexing wasn't really necessary... although even with the clean TM I did it automatically when I changed the setting without even thinking this could be the reason.

    @
    I'd still be surprised if this is your issue because you are talking about no matches at all, but perhaps try reindexing your TM anyway in case it is causing your problem.

    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

  • 0 in reply to Paul

    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"

    Trados Studio Translation Memory Settings dialog box with the Acronyms option disabled under the Fields and Settings submenu.

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

    Close-up of text in Trados Studio showing a mismatch in capitalization, with 'IMPORTANT' on the left and 'IMPORTANT' on the right.

    Trados Studio Project Settings showing a 91% match for the term 'IMPORTANT' with correct all caps formatting applied.

    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.)
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 1:45 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Robert Eric Carter
    Hi Robert,

    So glad that between them, Jerzy and Naoko found the solution to your problem!

    Replying to the last post is fine because you were speaking to all who have posted in this thread :)

    All the best,
    Ali :)
  • 0 in reply to Robert Eric Carter

    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  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.

    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