Wrong (old) 'TM User ID' added to TU when adding translation as new translation

When using the option to add a translation as a new translation (Home > Segment Actions > Add as New Tranation), Studio only uses the 'TM User ID' stored under File > Setup > Users as user information (created by etc.) for the first translation that is saved in the TM by confiming the segment manually in Editor (provided you have "Update translation memory" activated under "After Confirming Segments Manually"). When you then go back to the segment and write your second translation in the target field and now use the function "Add as New Translation", you will see that Studio has now not used the current ’TM User ID’ from the User settings, but old data that has previously been used in the Studio environment. This behaviour has been replicated in several Studio instances.

Parents Reply Children
  • Hi

    I didn't respond to you yet because it looked like too much confusion for me to get my head around quickly... needed some time to look at this carefully.  First of all I don't think Studio should be using File Setup -> Users for the TM updates when you are translating at all.  I have now been playing with this a little and to be honest I would not of ewxpected it to behave this way at all for two reasons:

    1. The description says this:
      Screenshot of Trados Studio's 'Users' dialog box with a description about managing users for sending and receiving packages.
      This is all about the users you work with and not your own user ID
    2. This may be even more important... Projects are supposed to be unique to themselves.  So once a project has been created any changes in the global settings anywhere should not reflect on unique settings for the project.

    But here, I can see that by adding myself as a user (which is the odd approach I would not of thought of) actually causes all my projects to use whatever ID I put in there.  In fact changing it in a project even changes all the other projects too.

    This, in my opinion is a bug and should be addressed.  I'll report this to the appropriate teams and let you know what the feedback is.  Could be they won't agree with me, but it certainly seems like unwanted behaviour to me.  I think it would make sense to have a separate option for your own TM User ID so you can control it as needed, and with the ability to use a different ID on each project.

    Paul Filkin | RWS

    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 4:25 PM (GMT 0) on 28 Feb 2024]
  • Hi ,

    Thanks a lot for looking into this and getting back to me. Blush And thanks for reporting this bug to the relevant teams in order to have it fixed.

    It this connection, it would really be great, if the developer team could take into consideration to create a separate option that would allow you as a user to you easily select between different TM User IDs (pre-defined by yourself) and to select the specific TM User ID that you wanted to use for updating TUs in a specific project (BOTH when running the batch task ’Update Main Translation Memories’ AND in connection with interactive translation).

    Could you also have a look at ’Scenario 2’ above?

    Scenario 2:

    If you use TM1 to pre-translate a file, and you then enable a different TM (TM2) in the Project Settings, go to a given segment and press Ctrl + Alt + Enter in order to confirm the translation in the target field, the user info from TM1 is mysteriously used to update the user info fields of the newly stored segment in TM2. The user info is in this case NOT your own TM User ID.