After adding variables to a TM, when do they take effect in TM leverage?

I added some variables to a TM in an ongoing project. I closed and re-opened the project, and then upgraded the TM in the "Project settings" view. But the variables still don't have an effect on TM leverage.

At which point are they supposed to be effective?

Thanks,

Daniel

emoji
  • "Probability score": 0.8

    "Question improvement suggestion": Please provide the version of Trados Studio you are using and the steps you followed to add the variables to the TM. This will help in providing a more accurate solution.

    In the meantime, based on the information you have provided, here is a suggested answer to your question:

    Hello Daniel,

    When you add variables to a Translation Memory (TM) in Trados Studio, they should take effect immediately. However, for them to impact the TM leverage, you need to ensure a few things:

    Step 1: Make sure that the variables you added are correctly defined and saved in the TM settings.

    Step 2: After adding the variables, you need to reprocess the files in your project for the changes to take effect. This means you should re-translate the files using the updated TM.

    Step 3: If you have already translated some segments before adding the variables, you might need to confirm these segments again for the variables to have an effect on TM leverage.

    Remember, the TM leverage is calculated based on the match value of the segments, and the variables are part of this calculation. Therefore, any changes to the variables should be reflected in the TM leverage once the files are reprocessed.

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

    RWS Community AI

    emoji
  • Wow, that was it! (3) Re-confiming segments. Brilliant answer!

    emoji
  •  

    Do you have project TM in your setting? In this case the variables are NOT in there before you recreate the TM. And if not, I would recreate the project, should the variables not work at once. However, I would be with you, that your actions done should have triggered the new variables to work.

    _________________________________________________________

    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
  • Thanks  

    In this case, the (quite amazing) Community AI hit the nail on the head. Re-creating the project would be terrible, it's big and complex.

    Daniel

    emoji
  •   

    This is an old bug in Trados Studio. I don’t know if it’s fixed in Trados Studio 2024.

    The workaround is cumbersome, but it works (until I add more variables Tired face), In the Translation Memory view:

    - Remove all variables (Reset to Deafults button).

    - Upgrade the TM (Upgrade button).

    - Add the new variables (previously exported to a TXT file) then edited somehow (with a text editor or, as I do it mysefl, with an AutoHotkey script to append the selected text to the TXT file with variables).

    - Import the new TXT file (Import button).

    - Upgrade again the TM (Upgrade button)

    As you can imagine, it really takes a long time to do it, so I follow the above procedure just once a month and just for a small number of TMs.

    EDIT: I’ll test this bug in Trados Studio 2024 and if re-creating the project actually works…

    emoji
  •  

    I usually do the following:

    Using the “Variables Manager” app, I export all variables, then copy all new variables into the same text file in EditPad Pro. Then I remove leading and trailing spaces and de-dupe the list (“Delete duplicate lines”). Then I paste the de-duped list into the text window in the Variables Manager.

    But it somehow makes sense that a segment that was committed to the Project TM before the “mother TM” had the variables added does not update right away. Once I re-confirm a segment, it has taken in the new variables, or so it seemed  to be the other day.

    emoji