Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Customizing your workflow lets you invest resources to translate high value content (and fewer resources to translate low value content). In this article, we outline four common workflows, their primary purposes, and how to set them up.
 

Panel
titleFor specific instructions on building a workflow, click a link below.

Table of Contents



Tip
titleCommon Workflows


  • Machine Translation
    When speed is important and you’re ok with less-than-perfect results, machine translation can be a cost effective option. 

    Use
    : Low value content. 
    Example: Comments on social media.

  • Post Edit-Machine Translation (PEMT)
    When you need a professional translation, but aren't concerned with professional review, you may wish to use a Post Edit-Machine Translation workflow.

    Use: Medium grade content. 
    Example: Product descriptions, web pages.

  • Standard Professional
    When you need a professional translation, and it needs several rounds of review, you may wish to build a Standard Professional workflow.

    Use: High value content. 
    Example: Marketing materials, legal agreements, customer communications.

  • Community Translation
    When you are on a tight budget, or have a large amount of content needing translation (e.g. a community forum), you may wish to build a Community Translation Workflow.

    Use: Medium value, high volume content. 
    Example: Help files and knowledge bases.


Once a workflow is built, it can be applied to any translation project. In other words, every document added to the project using the workflow will pass through its required steps.


Anchor
mt
mt
Machine Translation

When speed is important, and you’re ok with less-than-perfect results, you may wish to create a machine translation workflow.

To build a workflow with only machine translation,

  1. Go to Templates in the side bar, then select Workflow Templates.

  2. Click New Workflow. Type a workflow title (e.g. Machine Translation, Post Edit) and click Save.

  3. In the new screen, click to choose the phases for the workflow.
    On the next screen, click to add the following phases. (Drag and drop to rearrange; rename as needed). Typical phases could include:
    1. Machine Translation

  4. Click Save.

  5. Go into the workflow and ensure a machine translation engine has been selected. (MT workflows will not run until a machine translation engine has been selected).

The machine translation workflow is ready to be used and can be applied to any translation project

Anchor
pemt
pemt
Post Edit (PEMT)

When you need a professional translation, but aren't concerned with professional review, you may wish to use a Machine Translation, Post Edit (PEMT) workflow.

To build a Machine Translation, Post Edit workflow,

  1. Click New Workflow. Type a workflow title (e.g. Machine Translation, Post Edit) and click Save.

  2. In the new screen, click to choose the phases for the workflow.
    On the next screen, click to add the following phases. (Drag and drop to rearrange; rename as needed). Typical phases could include:

    1. TM Leverage
    2. Machine Translation
    3. Translation (Post-Edit) - During this step, a professional translator makes corrections (as needed) to the machine translation.
      Optional:
    4. Custom (Validation & Verification) - Staff members check completed translations (in their final format) to ensure layout looks OK.
    5. Custom (Client Review)
       
  3. Click Save.

  4. For best results, Configure each workflow phase. (Note, a workflow will not run properly if it is not completely configured).

  5. The PEMT workflow is ready to be used and can be applied to any translation project.

Anchor
pro
pro
Standard Professional Workflow

When you need a professional translation, and it needs several rounds of review, you may wish to build a Standard Professional workflow.

To build a Standard Professional workflow,


  1. Go to Templates in the side bar, then select Workflow Templates.

  2. Click New Workflow. Type a workflow title (e.g. Standard Professional Translation) and click Save.

  3. Next, choose the phases for the workflow.
    On the next screen, click to add the following phases. (Drag and drop to rearrange; rename as needed). Typical phases could include:
    1. TM Leverage
    2. Translate - During this step, a professional translator translates the source text.
    3. Review - During this phase, as many reviewers as needed review and correct the translation.
    4. Custom (Validation & Verification) - Staff members check completed translations (in their final format) to ensure layout looks OK.
    5. Custom (Client Review).
       
  4. Click Save.

  5. Configure each workflow phase.

  6. The MT workflow is ready to be used and can be applied to any translation project.

Anchor
cmty
cmty
Community Translation Workflow

When you are on a tight budget, or have a large amount of content needing translation (e.g. a community forum), you may wish to build a Community Translation Workflow.

To build a Community Translation workflow,

  1. Go to Templates in the side bar, then select Workflow Templates.

  2. Click New Workflow. Type a workflow title (e.g. Community Translation) and click Save.

  3. Next, choose the phases for the workflow.
    On the next screen, click to add the following phases. (Drag and drop to rearrange; rename as needed). Typical phases could include:
    1. TM Leverage
    2. Machine Translation
    3. Post-edit (by the Community) - During this step, members of the community submit translations.
      Optional:
    4. Custom (Validation & Verification) - Staff members check completed translations (in their final format) to ensure layout looks OK.
    5. Custom (Client Review).
       
  4. Click Save.

  5. Configure each workflow phase.

  6. The workflow is ready to be used and can be applied to any translation project.

Live Search
spaceKeyPDOC
additionalpage excerpt
placeholderSearch Documentation

 


On this page:

Table of Contents


Need Support?

Visit the RAY Enterprise Support Center.



Style
#children-section {        display:none !important;    }
#comments-section {        display:none !important;    }
#likes-and-labels-container {        display:none !important;    }
.page-metadata	{display:none;}