Forum: SDL Trados support
Topic: Studio 2014, duplicates when updating TM
Poster: Andreas Wettergren
Post title: Same issue in 2011
Just FYI, this is a standing issue we have with Studio 2011 as well.
I'm just now researching under which circumstances the duplicates are created.
So far it seems that there is a difference if the update is made in a package and then imported, or if the update is made directly in the project managers version of the project. In the latter case the last version of the segment gets updated (but not any previous duplicates).
Any type of package import i have tried leads to duplicates.
(updated return package from same translator project, new project package created and opened as separate project at translator, then returned the usual way. All using different user as "translator" of course)
Right now I'm comparing sdlxliff/project files to see what triggers the different behavior when doing an update as project manager.
This has been creeping in to our TMs for a long while without notice (possibly since we started using Studio?), and is now starting to cause lots of grief. Our customers wonder why their previously corrected segments are regressing to the previous version, and the analyses (spelling?) shows 99%-ers where there should only be 100% matches.
We've tried getting help from support before (I think while we still had a contract), but they dismissed it or didn't understand the question. I think the gist of it was that or workflow was non-standard in some way, but i fail to understand how that can be (I didn't contact them personally, so I may have got it wrong). Everyone needs to update a segment now and then.
I understand the issue may be a different one in 2014 compared to 2011, but the symptoms are very very similar. If anyone could reproduce the behavior (making the update as "project manager") above on 2014 please update the thread. I don't have access to 2014 personally.
Paul, let me know if you want a step by step on how to reproduce this in 2011 (assuming it's the same issue).
I've tested extensively and can give you our project template to ensure we have the same settings.
I feel this is a serious issue that potentially is costing your clients money. In our situation at least, where we have automation external to Studio, we have to sidestep our normal workflow to get correct updates with no duplicates.
/Andreas