• State Verified Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 3590 views
  • Users 0 members are here
Options
Related

Updating a TM

Pascal De Cubber

I've created a project and attached directly to that project a file based TM provided by the customer (= TM 1). After having created that project, I've opened the same TM under the Translation Memories button of that particular project (= TM 2).

When looking into Settings of the TM added after creating the project (TM 2), I see that the number of segments in that TM (445 segments) remains unchanged, though the 'update TM' box was ticked.

Apparently, only the TM attached to that particular project (TM 1) is being updated and not the 'main' TM I've added afterwards to the list (TM 2).

If that is the case, that would mean that any TM added to the TM list is not being updated (hope I'm being clear).

Does anyone have an idea what I've done wrong or forgotten?

Many Thanks !
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi.
    A Main TM is (normally) your TM, on your PC, in the folder where you keep your TMs.

    A Project TM (if selected when creating the project) contains a SUB-SET of the 'Main TM' added to the project. During file analysis when Studio creates the project according to your selected settings, the files analysed are compared with the Main TM; all segments that are CM/100% matches or that exceed your threshold fuzzy match setting are extracted from the Main TM and put into the Project TM (so far as I understand it).

    In the Translation Memories list I your Project Settings, a Main TM appears as a single line item. A Project TM appears as a two-line item, the first line is the name of the originating Main TM and the second line is the derived name of the Project TM (normally 'Main TM name' + 'Project name', or something similar). It will be the Project TM that is selected as Enabled and Update. From what I have seen, the Main TM is not enabled in the project.

    The Project TM (again, so far as I understand it), is a device designed by SDL for Studio for 2 reasons. Firstly, so that translation agencies can provide a translator with useful TUs relevant to the files to be translated from their TM without providing the entire TM. This gives the end-client a degree of confidentiality, gives the agency proprietorial control of its TM and can significantly reduce the size of a file or package sent to the translator. The second reason for using a Project TM is that it provides the benefit of a TM storing work done without putting unreviewed and unverified segments directly into the Main TM, so protecting the 'purity' of the Main TM.

    Incidentally, you can look at the Settings for a TM from the TM list window in Project Settings, without opening the TM in Translation Memories view.

    Simon
  • 0 in reply to Simon Cole
    Hi Paul,
    Hi Simon,

    Thanks for your answers and comments.
    I've finally found a roundabout by copying the Project TM to another folder, giving it another name, creating a new project and adding the "new" TM I had just created (but not as a project TM this time). The translated TU's were in the new TM, but not the imported .tmx file I had received from the customer. After importing that .tmx file, everything seems to work now and the number of TUs mentioned under Settings adds up as I move forward with my translation. Anyhow, it remains a very strange situation to me.
    I think the problem may have been caused by a problem with the language variants when creating the project. I remember vaguely that, when creating the project and adding the file to be translated and the TM, there was an error message about the language and that I opted then for "Any TM" (or something).
    This all seems very complicated, but I wanted to do this simply because I wanted a new project under another name and I didn't want to take the risk of simply changing the file and project names and maybe making them corrupt or useless by such action.
    Well, doing that, I've discovered something new and learned something about the dark side of Studio.
  • 0 in reply to Pascal De Cubber
    It seems very complicated indeed and unnecessary... hopefully you won't come across this again but if you do try and write down the steps you went though and perhaps we'll be able to explain why it happened.

    Glad you found a workaround anyway.

    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

Reply Children
No Data