Trados Transcreate

Oana Nagy — Fri, 12 Jan 2024 17:06:55 GMT

Current Revision posted to Wiki by Oana Nagy on 1/12/2024 5:06:55 PM

The RWS AppStore > Wiki is no longer being maintained. For the latest updates and changes being published, please visit the official RWS AppStore, where you will find supporting information such as documentation & change log details that is associated to each app.

Alternatively if you are using Trados Studio 2022 SR2, you will find the same information within the Integrated AppStore.

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:

uat.community.rws.com/.../6862.05_5F00_tinact.mp4

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

Trados Transcreate

Oana Nagy — Tue, 13 Jul 2021 10:44:09 GMT

Revision 9 posted to Wiki by Oana Nagy on 7/13/2021 10:44:09 AM

uat.community.rws.com/.../05_5F00_tinact.mp4

Definitions

What is Transcreation:

Often this includes Back-Translations

What are Back-Translations

Overview

What does the Trados Transcreation App do?

Prerequisites

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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

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

Back Translation Workflow Phases

General steps required include:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

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

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

Trados Transcreate

Oana Nagy — Tue, 13 Jul 2021 10:44:09 GMT

Revision 10 posted to Wiki by Oana Nagy on 7/13/2021 10:44:09 AM

uat.community.rws.com/.../05_5F00_tinact.mp4

Definitions

What is Transcreation:

Often this includes Back-Translations

What are Back-Translations

Overview

What does the Trados Transcreation App do?

Prerequisites

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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

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

Back Translation Workflow Phases

General steps required include:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

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

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

Trados Transcreate

Oana Nagy — Tue, 13 Jul 2021 10:44:09 GMT

Revision 11 posted to Wiki by Oana Nagy on 7/13/2021 10:44:09 AM

uat.community.rws.com/.../6862.05_5F00_tinact.mp4

Definitions

What is Transcreation:

Often this includes Back-Translations

What are Back-Translations

Overview

What does the Trados Transcreation App do?

Prerequisites

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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

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

Back Translation Workflow Phases

General steps required include:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

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

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

Trados Transcreate

Oana Nagy — Tue, 13 Jul 2021 10:44:09 GMT

Revision 12 posted to Wiki by Oana Nagy on 7/13/2021 10:44:09 AM

uat.community.rws.com/.../6862.05_5F00_tinact.mp4

Definitions

What is Transcreation:

Often this includes Back-Translations

What are Back-Translations

Overview

What does the Trados Transcreation App do?

Prerequisites

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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

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

Back Translation Workflow Phases

General steps required include:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

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

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

Trados Transcreate

Paul Filkin — Tue, 25 May 2021 13:14:15 GMT

Revision 8 posted to Wiki by Paul Filkin on 5/25/2021 1:14:15 PM

uat.community.rws.com/.../05_5F00_tinact.mp4

Definitions

What is Transcreation:

Often this includes Back-Translations

What are Back-Translations

Overview

What does the Trados Transcreation App do?

Prerequisites

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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

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

Back Translation Workflow Phases

General steps required include:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

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

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

Trados Transcreate

Paul Filkin — Thu, 22 Apr 2021 07:15:02 GMT

Revision 7 posted to Wiki by Paul Filkin on 4/22/2021 7:15:02 AM

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

uat.community.rws.com/.../SDL-Transcreate.mp4

Definitions

What is Transcreation:

Often this includes Back-Translations

What are Back-Translations

Overview

What does the Trados Transcreation App do?

Prerequisites

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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

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

Back Translation Workflow Phases

General steps required include:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

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

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

Trados Transcreate

Paul Filkin — Mon, 22 Mar 2021 16:58:17 GMT

Revision 6 posted to Wiki by Paul Filkin on 3/22/2021 4:58:17 PM

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

uat.community.rws.com/.../SDL-Transcreate.mp4

Definitions

What is Transcreation:

Often this includes Back-Translations

What are Back-Translations

Overview

What does the Trados Transcreation App do?

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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

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

Back Translation Workflow Phases

General steps required include:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

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

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

Trados Transcreate

Paul Filkin — Mon, 22 Mar 2021 16:50:30 GMT

Revision 5 posted to Wiki by Paul Filkin on 3/22/2021 4:50:30 PM

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

uat.community.rws.com/.../SDL-Transcreate.mp4

Definitions

What is Transcreation:

Often this includes Back-Translations

What are Back-Translations

Overview

What does the Trados Transcreation App do?

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:

Bilingual Excel file(s) used to create a Trados Studio project
Trados Studio project is converted into a transcreation project
Files are then Transcreated & Reviewed
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:

Do you want to keep the original Trados Studio Project displayed within the Trados Studio Projects view?
How many alternative Transcreations do you require?
What do you want to do with any historic translations which may be leveraged during your convert process?
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:

Select "Create local Project"

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

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

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

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

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

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:

Right click on file(s) and select export to proceed to export wizard
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:

Select the file(s) and select import
Specify which file(s) need updating
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

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

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

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

Back Translation Workflow Phases

General steps required include:

Include Back Translation as part of exported MS Document
Transcreate target column as well as complete Back Translation Column
Import update back into Trados Translation Project
Review Transcreation updates in Trados Studio
1. Including Review and Sign off (optional)
Create Back Translation Project from within Trados Transcreate View
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

How to install:

Prerequisites:
Download:

Download:

Supported versions:

Locate via “Downloads” and click to install

Confirm your version of Trados Studio

Installation can be deemed successful, once you see the Transcreate and Reports Viewer Plus view within Trados Studio

Tips:

TU Meta Data

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

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

Trados Transcreate

Paul Filkin — Fri, 12 Mar 2021 18:11:19 GMT

Revision 4 posted to Wiki by Paul Filkin on 3/12/2021 6:11:19 PM

This wiki will be extended over time with full details of how to use the application. For the time being you may find this video useful which provides an indication of the overall process:

uat.community.rws.com/.../SDL-Transcreate.mp4

Tags: Backtranslate

Trados Transcreate

Paul Filkin — Fri, 12 Mar 2021 18:05:22 GMT

Revision 3 posted to Wiki by Paul Filkin on 3/12/2021 6:05:22 PM

This wiki will be extended over time with full details of how to use the application. For the time being you may find this video useful which provides an indication of the overall process:

Tags: Backtranslate

Trados Transcreate

Paul Filkin — Tue, 09 Mar 2021 22:50:11 GMT

Revision 2 posted to Wiki by Paul Filkin on 3/9/2021 10:50:11 PM

Tags: Backtranslate

Trados Transcreate

Oana Nagy — Mon, 08 Mar 2021 14:00:06 GMT

Revision 1 posted to Wiki by Oana Nagy on 3/8/2021 2:00:06 PM

TBC

Tags: Backtranslate