Hi, Kelly.

Sure!
It goes like this:

1.1 Title goes here

The table continues for several hundred pages with slide summaries in between.

The client want the delivery file to be in this exact format.
So, yes, to translate it I can just extract the entire source column to import it into Trados, but I would need to copy and paste every single target segment into the original file.
That is why I am looking for a solution that lets me import (more or less) directly the file into the 2017 ver.

Do you have any idea how?

As the time is pressing, right now I am manually extracting the source to paste the target back, but still a better solution would be nice.

Thank you!

Hi, Kelly.

Sure!
It goes like this:

1.1 Title goes here

The table continues for several hundred pages with slide summaries in between.

The client want the delivery file to be in this exact format.
So, yes, to translate it I can just extract the entire source column to import it into Trados, but I would need to copy and paste every single target segment into the original file.
That is why I am looking for a solution that lets me import (more or less) directly the file into the 2017 ver.

Do you have any idea how?

As the time is pressing, right now I am manually extracting the source to paste the target back, but still a better solution would be nice.

Thank you!

What would happen, if you copy this table to Excel and use Excel Bilingual or—in Studio 2022—the Multilingual Excel file type, which would fit excellent for your task.

Before copying to Excel make sure, there are no soft line breaks in Word. To do so, run a search for ^l
Should you find any, replace by something not present in Word, like # or @ sign. In Excel, run a replacement for this sign and replace by ALT+010 (typed on numeric keyboard with ALT key pressed and released after entering the code). You will see nothing in the replacement box, but the replacement should work and replace all signs by a soft line break in Excel. This is because Excel treats soft line breaks from Word as cell breaks and this would destroy your table. When copying the table back to Word, Word will treat Excel soft line breaks properly.
Other solution could be to use the sign like # or @ as a segmentation rule in your TM. Then you would need to replace these signs in Word after translation, which is typically easier.

Thank you for another idea.

I have just tried it.
Luckily there was no soft line break.

Copying it to Excel worked fine.
However, Trados ignore completely the Source and Target columns, instead it treats the first two columns from the left (e.g. "ID" and "Type" / "gawregjj" and "Text Box 13") as Source and Target.
In result, the actual Source and Target, being the two right columns, do not appear at all in Trados.

If I can tell Trados to ignore the first two columns, it might work.
(Copy and Pasting only the right columns to Excel is not ideal either because there are a lot of reference tables in-between that prevents me from selecting the entire relevant columns. I would have done so if the volume had had been much less).

Use the Multilingual Excel file type https://appstore.rws.com/language/app/multilingual-excel-filetype/1307/ and configure as described here: community.rws.com/.../multilingual-excel-filetype

In hindsight, now that they are in Excel, I can simply delete the first two of four columns because luckily all the relevant columns are the two on the right.
I am going to need anyway to insert the translation back manually, but for now it might be the best solution I have without upgrading the software.

I will take a look at Multilingual Excel file type and the instructions.
I might try it.

Thank you!

nop

the sample means "somethingSimple.docx" which will be used by others to make a testing project.

I wanted to put a file here but it does not let me do it directly, so I opted in to paste an example table.

I'm sorry to say like this But..
I promise.
No file, No solution.

Good Luck To You.