SDL Trados Studio – Hiding automated translation (AT) origin

If you use the MyMemory plug-in for SDL Trados Studio, your translated segments will often be assigned the AT (Automated Translation) origin. This also includes the MT (machine translated) segments. While AT origin does not necessarily mean that such segment was machine translated, some clients may get a bad impression seeing this in their translated files. Use the following procedure to get rid of the AT origin in translated file.

Prerequisites: SDL Trados Studio, Unicode text editor, such as PS Pad or Notepad+

  1. Start Unicode editor of your choice.
  2. Open appropriate SDLXLIFF file in the text editor.
  3. Search for origin-system=”MyMemory Plugin” (include double quotes) string and replace all instances with the following one: origin-system=”XXX”, where XXX is a name of your translation memory (without file extension). This can usually be done easily using CTRL+H.
  4. Search for origin=”mt” (include double quotes) string and replace all instances with the following one: origin=”cm”
  5. Save the SDLXLIFF and open it in Studio to check whether all segments were updated.

Under the line: This is a technical article. Each of you has to consider its ethic aspect.

This entry was posted in Computer-aided Translation, Software-related. Bookmark the permalink.

7 Responses to SDL Trados Studio – Hiding automated translation (AT) origin

  1. Chau Nguyen says:

    Thank you for the solution. This does take care of the problem to it root. I just want to contribute another solution for those non-technical guys out there. Let’s presume that you are at an AT Translation Unit:

    1. Edit the automatically translated text.
    2. Ctrl + A: to select all the text.
    3. Ctrl + X: to Cut it.
    4. Ctrl + Insert: to insert text from source. This step will overwrite the AT origin with From source origin and removes the AT label. ^_^
    5. Ctrl + V: to Paste the edited text back to the Translation Unit.
    6. Enjoy

  2. Great tip from Chau above! It can be a bit tedious if your whole file needs to be edited, but it takes away the risks of touching the file directly in a text editor.

    Personnally, when I have issues with segment statuses, I use Notepad++, which offers tons of useful options (including “Replace in files”).

    • Huw says:

      Totally agree that the ‘Replace All in All files’ in Notepad++ is exceptionally useful. Does the whole process in the matter of a second over several sdlxliff files at once, whereas Chau’s method could potentially take hours.

      I also agree with Ciniala’s appraisal of the ethical side of things. More than anything, it is just useful for assuring agencies and clients that the AT is just the starting point in the process, not the polished, human-standard end product.

  3. Yom says:

    The technique suggested by Chau is good to remove the AT label in the Editor view, but NOT the references in the xliff file itself (at least, not in my case). The solution in the article is the most effective.

    I’ll probably whip up an Autohokey script to automate the process.

    BTW, I’ve already done so for Chau’s technique. Here’s the code to assign the whole thing to CTRL+Q when you’re inside an AT translation unit.

    ; ————————————————————–
    ; Clean TM origin in Trados : control + q
    ; ————————————————————–

    Send, ^a
    Send, ^x
    Send, ^{Insert}
    Send, ^a
    Send, ^v

  4. B Rhoton says:

    Isn’t there a step missing in the script, the copy command after the select all command : Send, ^c

  5. Vaclav says:

    Ofteh happens that AT fills the segment but I will not use it and overwrite it. However, the AT mark stays there as if used the AT. So I simply copy my translation into the clipboard, then copy source into target and paste my translation into the target too. AT mark is gone.
    Its not exactly user friendly but it gets me rid of the AT thing.

  6. Code says:

    Hi all,

    I’ve written a program that takes in source files and automatically translates them into sdlxliff target files, using provided TMs.

    If anyone is interested, we can discuss possible customised solutions, or even sale of source code.

    Just drop me a message at Thanks!


    Code Seller

Leave a Reply

Your email address will not be published. Required fields are marked *