• State Suggested Answer
  • Replies 4 replies
  • Answers 3 answers
  • Subscribers 432 subscribers
  • Views 4253 views
  • Users 0 members are here
Options
Related

Clean TM functionality in SDL Trados Studio?

Octavio Ramos

Does SDL Trados Studio provide any functionality for fixing/improving TMs similar to a tool like Okapi Checkmate which has built in check for things like Source = Target, possibly corrupted characters, length warnings, et cetera. I am guessing that some of these types of checks can be created with the Serach functions, but the Search help seems to be lacking. Is there more information on this and how people handle this in Studio or do I simply need to export to TMX and work with 3rd party tools like Checkmate? It seems like lots of this functionality is already available in the Editor window while translating, but why has this not been made available for the TMs?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Octavio

    The types of check you mention are not part of the functions built into Studio's TM maintenance. Such functions, which I would qualify as "TM cleaning functions" are best executed using third party tools like the one you mention. Personally, the one I use most for this type of work is Olifant (also from Okapi). I have experimented with a few other tools and found this one to still be the best fit for that purpose.
    You are right when you mention that the functions of the Editor would also be suitable for this kind of task. This leads one to try to export a TM to XLIFF for example (which can be done using the AppStore app "TM Convert") and to do the cleaning in Studio's Editor using powerful functions such as Display filter and others. Unfortunately, the current Studio Editor has problems processing very large files and TMs usually are quite large files. Many other QA tools such as XBench, Error Spy and QA Distiller also have problems processing very large files. The only one I found so far which can handle very large files without problems is Olifant.

    Walter
  • 0
    Hi Octavio,

    This type of functionality in the TM Maintenance View of Studio is quite limited. You are probably better off exporting your TM as XLIFF or TMX (bite sized chunks) and then creating a STudio Project to QA the segments against the original TM. This article might be helpful if you wish to try it:

    multifarious.filkin.com/.../

    Regards

    Paul

    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

  • Former Member
    0 Former Member in reply to Paul
    Hello all,
    I find myself asking this question as well! Thank you, Octavio, for asking it!
    If you were to export the TM as a TMX, wouldn't you lose all of the metadata that makes a CM match a Context Match? Wouldn't it then be only a 100% match?
    Is there a way to export the TM as TMX withOUT losing all of that information?
    Best, Mindy
  • 0 in reply to Former Member
    Hi Mindy,

    A TMX from Studio (without the "export for Trados 2007" checked) will contain this information. So you need to make sure that whatever editor you use will not delete it.

    However, if you use an export to lots of TMX files and open them in Studio as a translation project then you can QA them in there with the original TM attached and edit the TM as needed in the editor view. But this won't help with batch edit tasks so for this using the TMX route and maybe something like Olifant is a better way to go.

    Regards

    Paul

    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