Hi,
I am translating some data sheets using the TM in the packages created by the client. But for some reason, the TM is not being updated as I go along.
I have tried everything (meaning each and every solution described that I can find!) including importing the finished translations into the TM - still nothing happens.
I really don't know what to try next, so suggestions will be highly appreciated.
Thanks in advance.
Lena
Hi there,
I have a similar if not identical issue. I've just starting using service release 1 with Studio 2017 and I'm having lots of problems with TM matches. It seems that the memory refers back to old matches and ignores newer and better matches created in the current document. I've been upgrading my TMs where necessary but this is still happening. The settings in the project require newest matches to be prioritised and the TM is the only project TM.
All the best,
Julia
Hi Julia,
Maybe this will help...
Have you recomputed your fuzzy index statistics for the TM/s affected or reindexed it/them lately? In case you don't know, here's where it's done via TM settings:
(e.g. Right click on the TM in the list on the left of the TM View, or click on Settings with the TM hightlighted in the Project Settings).
This would help particularly if it's a big old TM... The first option updates statistics to the memory, the second variables.
All the best,
Ali
Hi again Julia,
Oh how frustrating for you!
Is/are the TM/s on your local machine?
Have you tried exporting the TM to tmx and importing it into a newly-created, differently-named TM (based on the previous TM if it had customised settings)?
If you close the project and Studio then re-open the file/s in the project, does the TM now display the recent matches created in the actual project?
It is possible that there is some sort of delay in displaying them when they are actually there. Especially if the TM is on another drive/server...
As Paul Filkin says, more info is needed to define what could be happening here.
Though, if this is a direct result of installing SR1 and it's stopping you working effectively, you have the right to raise it with installation and licensing support, here:
Fill in all the asterisked details, with your most frequently used email address so they can get back to you.
It's helpful to contact them if they can find something useful from this to pass to the developers.
All the best,
Ali
Hi Julia,
I was wondering if you had managed to resolve this problem?
I am having the same issue since upgrading to SDL 2017 and then to 2019. The only difference is that if I delete the TU, then the new match appears - I don't have to make any changes to the project settings.
If you have any suggestions I'd be grateful.
Katie
Translate
