RWS Community
RWS Community
  • Site

Trados Studio

Trados Enterprise

Trados Team

Trados GroupShare

Trados Business Manager

Passolo

MultiTerm

RWS AppStore

Connectors

Beta Groups

Managed Translation

MultiTrans

TMS

Trados Enterprise

WorldServer

Language Weaver

Language Weaver Edge

Language Weaver Connectors

Language Weaver in Trados Studio

 

 

Tridion Docs

Tridion Sites

LiveContent S1000D

XPP

Language Developers

Tridion Docs Developers

Community Help

RWS User Experience

AURORA

Internal Trados Ideas

Mercury

RWS Community Internal Group

XPP Cloud

Language Combinations by Language Services

RWS Training & Certification

Style Guides

RWS Campus

Trados Approved Trainers

ETUG (European Trados User Group) Public Information

Nordic Tridion Docs User Group

Tridion West Coast User Group

Trados Studio Ideas

Trados GroupShare Ideas

Trados Team Ideas

Trados Team Terminology Ideas

Trados Enterprise Ideas

Trados Business Manager Ideas

MultiTerm Ideas

Passolo Ideas

RWS Appstore Ideas

Tridion Docs Ideas

Tridion Sites Ideas

Language Weaver Ideas

Language Weaver Edge Ideas

Managed Translation - Enterprise Ideas

TMS Ideas

WorldServer Ideas

Trados Enterprise Ideas

LiveContent S1000D Ideas

Contenta S1000D

XPP Ideas

Events & Webinars

RWS Training & Certification

To RWS Support

  • Search
  • Translate

    Detecting language please wait for.......


    Powered by
  • User
  • Site
  • Search
  • User
  • Product Groups
  • Trados Portfolio
  • RWS AppStore
  • More
  • Cancel
RWS AppStore

RWS AppStore > Wiki

Trados Transcreate
  • Home
  • Forums
  • Wiki
  • More
  • Cancel
  • New
Show Translation Options

Detecting language please wait for.......


Powered by
RWS AppStore requires membership for participation - click to join
  • -RWS AppStore
    • +AdaptiveMT Trainer
    • +Amazon Translate MT provider
    • +Antidote Verifier
    • +Apply Studio Project Template
    • +ApplyTM template
    • +AppNotifications
    • +AutoHotKey Manager (AHK)
    • +CleanUp Tasks
    • +Community Advanced Display Filter
    • +DeepL Translation Provider
    • +DSI Viewer
    • +Excel Terminology Provider / TermExcelerator
    • +Excel4GroupShare
    • +Trados Studio – Export Analysis Reports
    • +Export To Excel
    • +Fail Safe Task
    • +Google API Validator
    • GroupShare Kit
    • +GroupShare Version Fetch - Authentication options
    • +Hunspell Dictionary Manager
    • +IATE Real-Time Terminology
    • +IRIS PDF OCR Support for Studio
    • +Lingotek TMS plugin for Trados Studio
    • +MEMSOURCE CloudTM Provider
    • +MT Comparison
    • +MT Enhanced Plugin for Trados Studio
    • +MXLIFF File Type Support
    • +PA Admin
    • +Post-Edit Compare
    • +projectTermExtract
    • +Qualitivity
    • +Rapid Add Term
    • +RecordSource TU
    • +Reports Viewer Plus
    • +Trados Data Protection Suite
    • +Trados Freshstart
    • +Trados LegIt!
    • +Language Weaver
    • +Language Weaver Edge
    • SDL MultiTerm Extract
    • +MultiTrans Plug-in for Trados Studio
    • +Trados Studio InQuote
    • +Trados T-Window for Clipboard
    • +Trados TMBackup
    • +Trados Studio Word Cloud
    • +Trados TTS
    • +SDLTM Import Plus
    • +SDLXLIFF Convertor for MS Office
    • +SDLXLIFF Split / Merge
    • +SDLXLIFF to Legacy Converter
    • +SDLXLIFF Toolkit
    • +Signoff Verify Settings
    • +Star Transit (TransitPackage Handler)
    • +Studio Migration Utility
    • +Studio Subtitling
    • +studioViews
    • +Stylesheet Verifier
    • +Target Renamer
    • +Trados Copy Tags
    • +Target Word Count
    • +TM Lifting (ReIndex Translation Memories)
    • +TM Optimizer
    • +Trados Analyse
    • +Trados Batch Anonymizer
    • +Trados InSource!
    • +Trados Number Verifier
    • -Trados Transcreate
      • ChangeLog: Trados Transcreate
    • +Wordlight
    • +WorldServer Compatibility Pack for Trados Studio
    • +XLIFF Manager for SDL Trados Studio
    • +XML Reader
    • +#YourProductivity
    • +File type definition for TMX
    • +File Type Definition for Wordfast TXML
    • +Google Cloud Translation Provider
    • +Jobs
    • +Microsoft Translator Provider
    • +MSWord Grammar Checker
    • +Multilingual Excel Filetype
    • +Multilingual XML FileType
    • +OpenX Hash Generator
    • +PDF Assistant for Trados
    • +RWS Community Inside
    • +SDLTM Repair
    • +SDLXLIFF Compare
    • +Segment Status Switcher
    • +Studio Time Tracker
    • +TermInjector
    • +TMX Translation Provider
    • +Trados 2007 Translation Memory Plug-in
    • +Trados Compatibility and Migration Power Pack
    • +Trados QuickInfo
    • +Trados Translation Memory Management Utility
    • +TuToTm
    • +Variables Manager for Trados Studio

Trados Transcreate

This wiki will continue to evolve with full details of how to use the application.  In the meantime you may find this video useful, from the Trados Spring 2021 virtual conference, as it runs through the overall process:

Play this video

Definitions

What is Transcreation:

WIKI describes Transcreation as a concept used in the field of translation studies to describe the process of adapting a message from one language to another, while maintaining its intent, style, tone, and context

Often this includes Back-Translations

What are Back-Translations

 WIKI: Back translation is defined as: a procedure whereby a translator (or team of translators) interpret or re-translate a document that was previously translated into another language, back to the original language.

Overview

What does the Trados Transcreation App do? 

The app allows for users to convert their existing Trados Studio Projects into a Trados Transcreation Project. Transcreated Projects are unique in that they cater for numerus alternative translations as well as back translations, which are often required when adapting this type of material from one language to another.

Prerequisites

In order for the Transcreate application to work correctly you must also install the Reports Viewer Plus application from the appstore. This requirement will be removed in the future once Trados Studio has been updated to accommodate the improved Reporting API that has been developed to support the Transcreate application.

Supported Workflows 

Workflows supported are both Internal and done within Trados Studio, and/or External, meaning MS Word is the users preferred environment for completing their Transcreated task.

   

Workflow Phases

General steps required include:

  1. Bilingual Excel file(s) used to create a Trados Studio project
  2. Trados Studio project is converted into a transcreation project
  3. Files are then Transcreated & Reviewed
  4. Back Translations can be managed either as part of:
    1. the initial/external transcreation workflow
    2. or as a second focused back translation project

  

Summary points: 

  • A Trados Transcreate project is based on a standard Trados Studio project
  • Only bilingual excel files are supported as the source file
  • 2 workflows are supported based on the users preference:
    • Internal: Trados Studio
    • External: MS Word
  • Back translations can be addressed as a second step in the transcreation process if preferred

Getting Started

Questions to review before you start: 

  1. Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
  2. How many alternative Transcreations do you require?
  3. What do you want to do with any historic translations which may be leveraged during your convert process?
  4. Will the same person perform the transcreation AND the back translation, as part of the same task?

Creating your Trados Transcreation Project

Using Bilingual Excel files, follow these steps: 

  1. Select "Create local Project"

 

  1. Review File Type Settings (in practice it may be more convenient to do this in advance)

 

Ensure the source file columns are configured appropriately, paying specific attention to: 

  • Source column
  • Traslation column
  • Context information

 

  1. Complete the Project wizard to create your Trados Studio project
  2. Also note that by using the “Customer” field when you create your project the transcreation projects will be neatly grouped by customer.
  3. Select the project in the Projects View, right click and select "Convert to Transcreate Project"

    

  1. Complete the Trados Transcreate Convert Project Wizard, paying careful attention to:
    1. the number of alternative Translations required
    2. specifying whether or not you wish to retain the original Trados Project listed within the Project view

    

  1. Once complete, go back to the Trados Studio Projects view and note your converted Project is now in the list. It’s clearly identifiable by:
  • a Trados Transcreate icon
  • the project name use a “-T” as a suffix
  • the “Type” column uses “Transcreate Project” as the identifier

   

  1. A Trados Transcreated project can be managed directly from within the Trados Transcreate View, depending on the preferred workflow (Internal / External)

  

Internal Workflow

It’s expected that the content in the Editor view will show duplicate segments, which are part of the alternative Transcreations specified during the initial convert process

This is further supported, as seen in the File Tree View through the alternative listings

Take Note: Only the first occurrence of the alternative segments are translated, where possible. All other instances and the translations thereof remain empty. This is as designed in order to ensure each alternative translation is unique and appropriately differentiated as part of the Transcreate process.

  

External Workflow

As briefly explained above, the External Workflow would consist of both an export to MS Word as well as an import back into Trados Studio for reflect any Transcreated updates to your Project files.

Exporting to MS Word

Export options that are managed as part of the export to MS Word include:

  • Include Translation:
    If any translations exist within the Trados Transcreate Project, do they get exported to the MS Word document?
  • Exclude Segments:
    Management over current translations from within the Trados Transcreate Project to MS Word, can be specified via the exclusions of segments. Locked segments are not exported to MS Word by default
  • Copy Source To Target:
    Where no translations exist within the Trados Transcreate Project, should the export copy source text to target columns?
  • Include Back-Translation:
    Does this export to MS Word, include the task of Back-Translation
    * It’s our recommendation that files first get Transcreated & Reviewed. However if you want a user to perform both tasks simultaneously, then you can do so accordingly.

 To run an export follow these steps:

  1. Right click on file(s) and select export to proceed to export wizard


  2. Once exported, take note the file(s) show the blue export icon

Based on export file(s) selections, users can then complete their Transcreated task directly in MS Word.

Take Note: This export did not include the Back Translation

 

MS Word support includes:
Tracked Changes
Tag Management

Import updates from MS Word

File(s) can be imported as required, in order to:

  • Update Trados Transcrated Project *.xliff files
  • Revert files back to previous versions

Import options that are managed as part of the export workflow from MS Word include:

  • Overwrite existing translation:
    Regardless of what translations currently exists in the Trados Transcreate Project, should it be over written from the pending MS Word import?
  • Exclude Segments:
    In order to Project any current translations within the Trados Transcreated Project and regardless of which segments were originally excluded (if any), by excluding segments based on segment status we can ignore any changes made within the pending MS Word import.
  • Origin system:
    Otherwise known as Provider. Meaning what name should reflect against the translation segments and potentially under the TU meta data once the Translation Memory has been updated
  • Segment Status Assignment:
    Adjusting segment status accordingly is beneficial to aid users navigation, once reviewing the updated *.sdlxliff files in Trados Studio

 To run an import follow these steps:

  1. Select the file(s) and select import


  2. Specify which file(s) need updating
  3. Add the updated MS Word File

Take Note: Once completed the green import icon is seen against the files

 

 File Management

The Trados Transcreate Project is created in the same location path as your original Studio Project.

After the successful completion of the conversation between your original Studio Project and the Trados Transcreated Project, you can use the short cut to explore the folders

Or access the “Open Project Folder” directly from within the Project View in Trados Studio

   

Included in the standard folder structure, you now have a folder called workflow. And in the even you created a Back Translation, you will also see an additional folder called “Back Projects”cccccctjnevgtljfddjtnvvfuntdgrcdngvtvihehicf

  

During your numerus exports/imports you can track progressive files and versions by looking through the sub folders which follows a date/time naming convention   

   

It is worthy to note the following: 

  • It is not possible to mix files from different Trados Transcreate Projects

    

  • If an Internal workflow was carried out, a folder will be created with a file extension that isn’t strictly recognised outside of Trados Studio.

 

However as the local report confirms as the Workflow, this file was managed from within Trados Studio as an Internal Workflow

  

  • If an External workflow was implemented nestled in the folder structure you will find a MS Word as a result of the export process. This is in addition to a local report and a detailed*.txt file with information related to that particular task (for reference)

 

If unsure, a user can review the Project File Activity Audit View for a full understanding of the files export/import history

Take Note: To prevent valuable work from being lost due to ongoing imports and exports while having a mixed Internal / External workflow, the following warning may show

In addition, a warning icon will indicate if a file has already been exported and/or imported and therefore work may be lost if not managed appropriately

Back Translations

When to accommodate Back Translation

The command to create a Back Translation can only take place from within the Trados Transcreate View. Regardless if you included Back Translation as part of the external export to MS Word or not. 

Back Translation Workflow Options


How to create a Focused Back Translation Project

 

  1. Select your Trados Transcreate Project file(s) and use the ribbon to complete the request for a Back Translation to be created

   

You will now see a Back Translation listed under the original Trados Transcreated Project

  

Take Note: Also within Project View in Trados Studio you will find a dedicated Back Translation Project

   

  1. Complete the Back Transation either as an Internal or External workflow based on preference.

 Take Note: It’s expected that the source and target translation changes direction, to fulfil the Back Translation requirement

   

Included as part of Transcreate

While it is recommended different users perform the actual Transcreation from the Back Translation, it maybe your requirement that during the External workflow you want to include the Back-Translation.

 

 Back Translation Workflow Phases

   

General steps required include:

  1. Include Back Translation as part of exported MS Document
  2. Transcreate target column as well as complete Back Translation Column
  3. Import update back into Trados Translation Project
  4. Review Transcreation updates in Trados Studio
    1. Including Review and Sign off (optional)
  5. Create Back Translation Project from within Trados Transcreate View
  6. Assess Back Translations originating from step 3
    1. Ongoing assessment, review and Sign off can be performed either by following the Internal (within Trados Studio) or External (export/Import MS Word) Workflow steps

In summary the following results are expected:

  • Initially no dedicated Back Translation Project is created
  • A MS Word file with an additional column for Back Translations is provided
  • Initial import will only show Target Segment in Trados Studio
  • Back Translations will be accessed only once Back Translation Project has been created

   

 

Tips:

TU Meta Data

To maintain reference of the Transcreation origin, Trados Studio users can update Translation Memories using the *.sdlxliff meta data. During Batch Translation Memory Update it is known as “Use information from bilingual file to update TU system fields”

As defined during the import wizard the Provider of this Transcreation in this case has been noted as Lyds and will be saved in the TU accordingly

   

Changing Default

Trados Transcreate App default settings for convert, export and import can be changed by going to the app view’s settings

 Removing referenced files

During an import, you have added a file accidently. You can remove it by right clicking and select “Clear XLIFF File”

  

Missing Project

If in the Trados Transcreate view you cant see your Project listed, its likely because its missing from within the Trados Studio Project View. In which case, simply select “Open Project” to relocate your missing Project from within your windows explorer.

Advanced Display Filter

In the event you have several alternative translations to manage, you can easily navigate within Trados Studio by using the Advanced Display Filter

Context

If working as part of the Internal Workflow, your Translation Memory and Termbase maybe great assets to integrated as supporting tools to reference as part of your Transcreate process

Deleting a Back Transcreate project
If you need to delete a Back Transcreate project, simply right click on the Trados Transcreate project and select “Remove Back-Translation projects”

Known issues:

List descriptions of CRQ logged but not yet closed

Tags:

Backtranslate
  • Share
  • History
  • More
  • Cancel
Related
Recommended
  • Our Terms of Use
  • Copyright
  • Privacy
  • Security
  • Anti-slavery Statement
  • Cookie Notice
  • YouTube