Is it possible to output bilingual .doc files without using .ttx?

Several times/week I receive .doc files that are filled with codes, highlighted text and other stuff that is not to be translated. I still have to use Workbench because I can't figure out how to translate the file in Studio AND end up with a bi-lingual .doc file.

A bi-lingual .doc file with all the codes, highlighted text, etc. intact is what the customer wants back. They work in Workbench as well because they can't figure out how to work in Studio and keep all this "not-to-be-translated" text.

I played with it today and I am able to open up the .doc file in Studio, translate it and save the target as a .doc file with all the codes, etc. still there. It looks beautiful, except for the fact that it is not a bi-lingual file because the source text is missing!

How can I do this? I receive .doc files and Workbench memory, but I can't keep waiting for the customer to figure things out. I want to work these files in Studio because I know it would save me time. And then I could finally upgrade to Windows 10 and not worry about not being able to use Workbench!!

Any ideas, anyone? Any tiny suggestion would give me a bit of hope!!

TIA

Dorte

Parents Reply
  • Hi Paul,

    I just did a test with two .doc files using SDL Legit! and it almost worked.

    It changed the colour of the font for the "do-not-translate" text which is no big deal. Unfortunately all the hyperlinks were changed from "do-not-translate" text to translatable text when I saved the .sdlxliff file as bilingual .doc file.

    The hyperlinks are not in the translatable text (they are reference links for us, the translators) and did not show in Studio. I don't know what will happen when the customer cleans the bilingual files using Workbench and the hyperlinks all of sudden are translatable (but not segmented).

    Best regards,

    Dorte

Children