Editing Translation Files

• Editing Translation Files
  • Permission Required?
  • How Do I Edit Files Using MadTranslations?
  • How Do I Edit Files With a Third-Party Translator?
  • What’s Noteworthy?

[Menu Proxy — Headings — Online — Depth3 ]

Since MadTranslations is a full service provider, they will communicate with you and guide you through the entire translation process—including what to do if editing at any stage in the process is needed.

The following are a few editing scenarios you might encounter:

• Before a quote is approved Once you click the Create button at the end of the wizard, MadTranslations receives the translation package to prepare a quote. If you made a mistake or want to change a setting, you will most likely have to restart the process for a new quote.

• Quote is approved, but edits are needed before completion If you need to make edits to your content after a translation branch is sent to MadTranslations (and before completion), you will most likely need to cancel the existing branch and create a new branch to send.

• Translation is complete but edits are needed After you receive a completed translated project, MadTranslations will retain all of your files. A re-uploaded branch will replace the existing branch. Once you "Approve" the translated project, then no more edits can be made for that branch.

MadTranslations uses a translation memory system. It stores source language content and previously translated content. If rework is needed they will most likely tap into this database.

Communicate with your translator about an editing process that will work for both of you. There are various ways a reviewer and translator can exchange updates. The workflow is up to you, but the following points might get you started.

• The reviewer can build a PDF of the translated branch and make annotations in the PDF regarding any changes. The reviewer will have to deliver those edits to the translator (e.g., via email).

• The reviewer can build a PDF or an online version of the translated branch and make a list of edits in a separate document (e.g., Word, Notepad). The reviewer will have to deliver those edits to the translator (e.g., via email).

• The reviewer has a license seat with Central. The reviewer can review the translated content in the Files editor, make edits or annotations where text needs more work, and save the changes. If the reviewer wants to send the edits to the translator, the reviewer will need to create a new translation branch but base it on the previously translated (or edited) branch.

  Note The current branch uploaded (that the reviewer can view, edit, or annotate) can be overwritten if another upload occurs on that branch.

• The reviewer and translator have a license seat with Central. The reviewer can review the translated content in the Files editor and make annotations where text needs more work. The translator could go in after the review and clean up the files with annotations.

  Note Edits done in the Files page will be disregarded if another upload occurs, and edits will not be retained in the translator’s translation tool or in translation memory.

• The translator could set the reviewer up with access to the translation tool that is used for translation (e.g., memoQ, Trados Studio, Smartcat). If applicable, the reviewer could provide comments in the portal for the translator.

Your translator should retain all your files (i.e., in a translation memory system), so a re-translation of the entire project should not be necessary. Only the files that require editing should be affected.