Hi Jesus

after having carefully read your post, I noticed that, probably, you have not correctly understood what a bilingual review MS word document is.

In fact, when exporting a bilingual review MS Word document, it is supposed that target column should contain some text which, when modified and since the export bilingual review MS Word file has the “Track changes” activated by default, report pertinent “track changes” formatted text (say, strikethrough or different colours, according to your personal settings).

Before exporting your SDL file to an External Review MS Word file, try to copy all source segments to the pertinent target Studio Editor column selecting all segments and running the command “Copy source to Target” (or CTRL+INS) to populate target column segments and you will get identical content for source and target columns and save the project.

Now export your Studio file to MS Word review document, open it, and, without deactivating the “Track changes” feature, select the “fake” translated text, copy your external “real” translated text and paste it in the proper row to replace the “fake” target text. The old “fake” target text will assume the formatting of a deleted text while the pasted one the formatting of inserted/changed text. Repeat this process until the last segment, and save the file, without deactivating “Track changes”.

When you subsequently import the reviewed MS Word file in your Studio Editor view, the target column will be populated with your deleted and newly inserted text (formatted in a way similar to the MS Word file).

At this point, run the command “Review > Accept > Accept all changes in Document” to clean up the target translated column and save the project.

But pay attention to possible tags (if present).

Game over.

I do not think that this procedure will work if you start it with empty target column.

I hope this may help.

Claudio

Hi Jesus

after having carefully read your post, I noticed that, probably, you have not correctly understood what a bilingual review MS word document is.

In fact, when exporting a bilingual review MS Word document, it is supposed that target column should contain some text which, when modified and since the export bilingual review MS Word file has the “Track changes” activated by default, report pertinent “track changes” formatted text (say, strikethrough or different colours, according to your personal settings).

Before exporting your SDL file to an External Review MS Word file, try to copy all source segments to the pertinent target Studio Editor column selecting all segments and running the command “Copy source to Target” (or CTRL+INS) to populate target column segments and you will get identical content for source and target columns and save the project.

Now export your Studio file to MS Word review document, open it, and, without deactivating the “Track changes” feature, select the “fake” translated text, copy your external “real” translated text and paste it in the proper row to replace the “fake” target text. The old “fake” target text will assume the formatting of a deleted text while the pasted one the formatting of inserted/changed text. Repeat this process until the last segment, and save the file, without deactivating “Track changes”.

When you subsequently import the reviewed MS Word file in your Studio Editor view, the target column will be populated with your deleted and newly inserted text (formatted in a way similar to the MS Word file).

At this point, run the command “Review > Accept > Accept all changes in Document” to clean up the target translated column and save the project.

But pay attention to possible tags (if present).

Game over.

I do not think that this procedure will work if you start it with empty target column.

I hope this may help.

Claudio

Claudio, please, read this well.

YOU ARE A GENIOUS ! You have found the solution !

Yes, that is what I really needed and you found the solution. These days I am very busy, but I promise you I will create a video showing step by step how to do what you said. I will try to post the video here, so people can find an easy way to do this process without having to read all the explanations given.

The solution worked fantastic. You found a way to trick the system and you deserve an ovation, an applause and all my respect and consideration.

Great job. Well done.

Hi Jesus,

happy that you found my suggestion useful and working.

I’m not a genius, but just a common user trying to manage texts, graphics and to make the most of IT resources, machines, software and applications.

Computers, software, hardware and other IT resources are nothing “magical”, instead they are “logical” resources. It’s up to us understanding, exploit and apply this logic.

The basic principle when dealing with IT resources is to understand and to recognize that they are not, and won’t be, “intelligent” (compared to human brain) but just “logical” (“Yes-No”, “0-1”, “True-False”…. i.e., no "grey zones" between them), therefore they work following instructions, programming code and features guiding their behaviour. When you run away from their logic (no matter if simple or complex) you won’t be able to obtain the outcome you are expecting to get.

Claudio

Hi back!

As I promised, here is the videotutorial. In the meantime, the videotutorial is bilingual (English / Spanish) but the audio is in Spanish. I want to create a different version with the audio in English, anyway, for the moment this video is enough because you have the english subtitles along with the Spanish subtitles.

I hope you like it, and it may help many people having the same problem.

How to "inject" a pre-translation inside Trados

To watch this video in Youtube (full screen) just hover the mouse pointer over it, and when you see the Youtube logo, click on it.

Cheers

Unknown said:

If you can upload a video with the same quality, explaining step by step how to pre-translate inside Trados without having to pay anything I will be waiting for it.

Hi JESUS SANCHEZ 

Perhaps another way to do this if you are trying to avoid paying for Machine Translation (which is what you must be referring to since pre-translation in Trados itself is free) is this:

1. Export to Excel (no need to copy source to target first) using one of several apps available for this and you can also do all your files in one go and insert into a single Excel file for the translation process if you like
2. Copy the source column into the webpage of your preferred MT engine
3. Get the translation and copy it into the target column of your excel file
4. Use the Glossary Converter to convert the Excel to a TMX
5. Upgrade the TMX in Studio and pretranslate your project

This may be more reliable as the process you are using is not designed to be used like this, it is for light editing.  It can work, and you have demonstrated this, but it's a bit unreliable for heavy editing.

Incidentally, you can copy all the source to target in your video using a keyboard shortcut, the default is Alt+Shift+Insert.

Hi

Pre-translation in Trados itself is free? Really?

I would like, please, to see a video in which you show how to use the pre-translation for free inside Trados.

I guess you need to be registered in a SDL website?

A whole video showing the registration process and the way to configure Trados for pre-translation would be nice.

I tried also the bilingual excel, but I am sorry, I prefer the method I have described because that way I maintain the format in the source column, if I carry data to Excel I start to lose format

Cheers