Hi Mala Trivedi 

If you source Word file is monolingual then there are three options I am aware of (and probably a number of workarounds...).

Export for Bilingual Review

This is a feature in Studio that allows you to export the translation as a bilingual file in Word, normally used for review.  You access this by going to the Review tab when you file is open in Studio and select "Export for Bilingual Review".

You can make changes to the target text in Word and import the file back in to update your target translation in Studio with this method.

Export to a legacy Bilingual DOC/DOCX

This can be achieved by using an app from the SDL AppStore:

https://appstore.sdl.com/language/app/sdlxliff-to-legacy-converter/134/

Using this you can export a Word file that contains the source and target text formatted in the same way the old BilingualDOC used to be.  You can find some more information on this method here:

https://multifarious.filkin.com/2013/07/01/legacy_converter/

Export as the target format but with the source and target in it

This is also achieved using an app from the SDL AppStore:

https://appstore.sdl.com/language/app/rys-enhanced-target-document-generator/805/

This application supports exporting a target document with source and target grouped at either sentence or paragraph level.  You can find some more information on this method here:

https://multifarious.filkin.com/2017/11/24/double-vision/

Hopefully one of these is what you were after?

Condition 1: I do not want to spend money
Condition 2: I do not need old style

then you have only one choice "Export for Bilingual Review"
Now, I'm adding

Condition 3: I do want simple result.

Now, you got nothing, unless you have excellent MS Word VBA skills.

Let me make it clearer with screenshots.

regards

(there is a typo while counting par counts)

And the point you are trying to make is...?

Excuse me Martin... Do you really need to have brilliant VBA skills to convert table to text? I thought it was a standard feature in MS Word (Layout > Convert to Text). And what do you do at [what you refer to as] "sentence level" when segmentation is not that right and obvious? For example, ending with : or . that is not a full stop but just a dot? Not to mention formatting.

Unknown said:

I think the point is that you are once again sharing solutions that you have created for yourself and don't want to make them available through any recognised distribution network.

Do I understand this right that Martin Jornan is yet another reincarnation of Kelly Edward and Hoon Kim?
That would explain everything...

for 1st question.

I'm attaching two docx for you
one is just exported from SDL Trados Studio
the other is processed through "brilliant VBA skills" of mine
try if you can, through standard features, make the same result.

of course, you could do it
but how many clicks ? how long did you take ? and most importantly, do you really want to it again and again for 100 of them ?

Need_excellent_VBA_skills.zip

for 2nd question.

Mr. Filkin has the answer, not me.
That's the default segmentation topic. I'm just one of the ordinary users.

[In reply to Stepan Konev]

VBA codes ? it's 90 lines of them
if you have proper skills and really want to see it
i'll show you, all of them, free of charge.

-ah, last comment. My tool have nothing to do with VBA.  It is totally executed within SDL Trados Studio Plug Ins. The skills named "OpenXml".

regards