Suggestions on debugging Translation Memory (filters?)
Thread poster: Pablo Mayen
Pablo Mayen
Pablo Mayen  Identity Verified
Mexico
Local time: 22:37
English to Spanish
+ ...
Jun 11, 2013

Dear community,

Hopefully someone can shed some light on suggestions to debug my translation memory.

As of this moment my EN(US)-ES(MX) patent TM reaches 609,000 TUs. And the time has come to fine-tune the same. But nothing comes to my mind that would help me set up a special filter (or what criterion to use) to delete unnecessary units. I was thinking some titles/subtitles to start with and then some ambiguous terms but I'm afraid it will be kind of a titanic task. Per
... See more
Dear community,

Hopefully someone can shed some light on suggestions to debug my translation memory.

As of this moment my EN(US)-ES(MX) patent TM reaches 609,000 TUs. And the time has come to fine-tune the same. But nothing comes to my mind that would help me set up a special filter (or what criterion to use) to delete unnecessary units. I was thinking some titles/subtitles to start with and then some ambiguous terms but I'm afraid it will be kind of a titanic task. Perhaps an age-related filter (i.e. the first TUs when I knew next to nothing of SDL Trados :S)?

I'm not sure where to start. Any suggestions are greatly appreciated.

Regards

Pablo
Collapse


 
Bernard Lieber
Bernard Lieber  Identity Verified
Local time: 06:37
English to French
+ ...
Olifant Jun 11, 2013

Hi Pablo,

I think this issue has been discussed often enough, one of the easiest options is probably to export your TM as tmx and download Okapi Olifant, do your maintenance and reimport it into Studio.

HTH,

Bernard


 
RWS Community
RWS Community
United Kingdom
Local time: 06:37
English
In my opinion... if you are using SDL Trados Studio... Jun 11, 2013

... then I would upgrade the TM into Studio first. This will provide some sensible clean up heuristics as part of the built in process and then you can QA the TM if you like. You could indeed take the suggestion from Bernhard and export to TMX after upgrading in Studio and then use Olifant.

But my preference (as I have had problems with Olifant in the past) would be to convert the SDLTM to XLIFF and then use the QA tools in Studio as part of a translation project to tidy it up. T
... See more
... then I would upgrade the TM into Studio first. This will provide some sensible clean up heuristics as part of the built in process and then you can QA the TM if you like. You could indeed take the suggestion from Bernhard and export to TMX after upgrading in Studio and then use Olifant.

But my preference (as I have had problems with Olifant in the past) would be to convert the SDLTM to XLIFF and then use the QA tools in Studio as part of a translation project to tidy it up. There is an article on this process here that might be helpful : http://wp.me/p2xDjK-mq

Regards

Paul
Collapse


 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Suggestions on debugging Translation Memory (filters?)







CafeTran Espresso
You've never met a CAT tool this clever!

Translate faster & easier, using a sophisticated CAT tool built by a translator / developer. Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools. Download and start using CafeTran Espresso -- for free

Buy now! »
Trados Business Manager Lite
Create customer quotes and invoices from within Trados Studio

Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.

More info »