Problem with automatic population of target segments from TM

SDL Trados Studio 2017.

I have a project with a Project TM that uses paragraph segmentation, which I'm beginning to regret (it's good in that I can always split segments into the right units, but I have to do a lot of it to make the project TM useful; if I'd gone with the default segmentation rules, there are always useful segments that are so split that I CAN'T join them. But it is a lot less work...)

Anyway, some of the project is translation, some is editing. I want the edits to reach the TM, so I've started aligning them. To make that useful, I did a lot of segment splitting.

Which creates a new problem: to use those edits, I open the original source document for translation. But here the problems arise:

1.) I have to do the same splits; which takes a long time, but otherwise the segments don't populate.

2.) I get suggestions in the Translation Results window, but they don't get entered, and they don't come up in the same order as they do in the paragraph, and the paragraphs are long enough that it's a pain to find them all to enter them.

2.) When the splits are done, I have a document identical to a previously translated document, from the TM's point of view. It ought to just run down through TUs, populating the target segments. But it doesn't. First of all, it takes a LONG time to search for each TM match. Which is ridiculous, because I have a power user computer and a pretty darn small project TM...

In short, can anyone suggest a better way of doing this? And a reason why the TM search is so slow?

Thanks in advance

Parents
  • Note that TM searches were fast, and the population rapid, in Studio 2015.
  • If you use Project TM, the default search setting is "Search both PTM and main TM" afair. This of course slows the searches down.
    As for not entering hits from TM: go to File -> Options -> Editor -> Automation and select "Apply better match if found in TM after merging segments". Also bear in mind, that in case of draft status no TM hits will be entered anymore.
    Place the TM locally in your PC, the best option here would be using SSD. Studio is extremely sensitive in that respect. I have a i7 6700k PC with 2 TB spinning Seagate hard drive, where my TMs were placed as I started to use it last year. After I've got Studio 2017 I have had to move the TMs to a new SSD, which I bought and installed only for that purpose. This made searches significantly faster, but still searches in S2017 are slower as in S2015. This is because of fragment matching. And if you use TMs from 2015, which have NOT been upgraded to the new fragment match function, the searches are even slower, damn slow TBH. So check also, if you upgraded your TM. In running projects with Project TM you would either need to upgrade the PTMs too or create them anew after upgrading the main TM.
    And on the final note: why don't simply you change the segmentation rule?

    _________________________________________________________

    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.

Reply
  • If you use Project TM, the default search setting is "Search both PTM and main TM" afair. This of course slows the searches down.
    As for not entering hits from TM: go to File -> Options -> Editor -> Automation and select "Apply better match if found in TM after merging segments". Also bear in mind, that in case of draft status no TM hits will be entered anymore.
    Place the TM locally in your PC, the best option here would be using SSD. Studio is extremely sensitive in that respect. I have a i7 6700k PC with 2 TB spinning Seagate hard drive, where my TMs were placed as I started to use it last year. After I've got Studio 2017 I have had to move the TMs to a new SSD, which I bought and installed only for that purpose. This made searches significantly faster, but still searches in S2017 are slower as in S2015. This is because of fragment matching. And if you use TMs from 2015, which have NOT been upgraded to the new fragment match function, the searches are even slower, damn slow TBH. So check also, if you upgraded your TM. In running projects with Project TM you would either need to upgrade the PTMs too or create them anew after upgrading the main TM.
    And on the final note: why don't simply you change the segmentation rule?

    _________________________________________________________

    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.

Children