Help with missing tags in target file

I am working on a multilingual project, English – Croatian.
Per instructions, I've used SDL Legit to make the source bilingual, and opened in Trados to translate.
Here's how the interface looks:
The square brackets (e.g. FIREHAWK FX) are Internal tags, i.e., brand names etc. that are to appear untouched in the source and target.
But when I save target, all the original Terms that were supposed to appear untouched in both source and target do not appear, and I get a big mess.
Those internal tags are all gone. In their place are empty spaces, and red formatting, hinting that something should have gone before.
I have to do a massive amount of manual cleanup.
Any help would be much appreciated.
Thanks in advance,
SG
  • Hi Sanda,

    That looks very strange, what file type filter did you use to process the file?

    Nora Díaz
  • Hi Nora,


    Here's the process I used:

    PART I
    1. Open SDL Legit .
    2. Mark "Convert to bilingual Doc"
    3. Choose the file
    4. Choose English as source
    5. Choose Croatian as target
    6. Click convert, wait.

    PART II
    1. Open the coverted file
    2. Click "Style" (bottom right-hand corner arrow)
    3. Look for "TwinMark"
    4. Delete it
    5. Save file

    Part III

    1. Open the file in Trados Studio 2015 (translate single file, load related TM)
    2. Translate the file
    3. Save target as

    Part IV

    1. Open the file in Word
    2. Scream

    Any help you could suggest would be really appreciated. If it helps, I could send you the files in question offline to an email address you provide.

    Thanks again,

    Sanda

    P.S.

    I hope this answers your question... if not, can you please clarify what you mean by what filter I"m using.

  • Hi Sanda,

    A few questions:

    1. Why are you converting to bilingual DOC first? Has your client asked for a bilingual DOC?
    2. Why did you delete the tw4win style? This is used with the Bilingual DOC format to protect non-translatables.

    You can see from your screenshot that you have opened this file as a monolingual file in Studio and if you really wanted to have a bilingual DOC this is obviously wrong. So when Nora asked about the filetype she wondered whether you used the Bilingual DOC filetype or a monolingual DOC for this?

    I think it might be easier to help you over Skype perhaps because there seems to be some fundamental problems here it will be easier to address if we talk it through. If you are around tomorrow I'd be happy to do this?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hi Sanda,

    Studio is capable of processing bilingual Word files without the extra steps, and as Paul has explained, the tw4win style is needed to create the structure of the bilingual file, so you shouldn't delete it.

    If you really need a bilingual DOC file, try this:

    PART I - SDL Legit

    1. Open SDL Legit

    2. Mark "Convert to bilingual Doc"

    3. Choose the file

    4. Choose English as source

    5. Choose Croatian as target

    6. Click convert, wait.

    PART II - SDL Trados Studio

    First, check if you have the Bilingual Workbench file type (also called a filter) enabled. Do this by going either to Options (for a single file) or Project Settings (if your file is to be part of a project), then File Types and check that you have a file type called SDL Trados Translator's Workbench installed and active. If you don't, you can install it easily by clicking the blue link on the right:

    The SDL Trados Translator Workbench file type is the correct filter for files prepared with SDL Legit. If you don't have it installed, Studio will try to open the file with one of the regular Word filters (most likely the Microsoft Word 2000-2003 filter), which will lead to some problems. In other words, SDL Legit files are useless in Studio unless you have the SDL Trados Translator Workbench file type.

    In your case I'm going to venture a guess and say that the file type is probably already installed and active, but since you removed the tw4win style that is used for identifying this type of file, the filter simply didn't recognize the file as bilingual, and therefore it was passed on to the Word filter for processing.

    So now that you've made sure you have the right filter in Studio, open the converted file without any intermediate steps. Simply open it via the Translate Single Document option or add it to a project (but make sure the project has the correct file type active).

    So, to borrow your steps:

    1. Open the file in Trados Studio 2015 (translate single file, load related TM). If the correct file type has been used, you will see the below icon and the file type identifier in the Files View:

    2. Translate the file. When you open the file for translation, it will be clean of all the Trados codes. That's one of the advantages of using Studio to work on bilingual DOC files:

    Note that the 0% matches are populated with the source text. This is the default setting, but if you'd rather have clean segments for 0% matches like I actually do, there's a checkbox in the file type settings called "Clear 0% match segments" that you must check before adding the file to Studio. Click the little arrow next to the file type name to expand the settings.

    Translate as usual.

    3. Save target. Note that this will produce a bilingual DOC file, with all the Trados codes.

    And that's it. So it's really just two steps: prepare the file in SDL LegIt, and open the file for translation in Studio, making sure you have the correct filter installed and enabled.

  • Rereading your original question about the missing tags, I should add that the file you have now (for which you posted screenshots) is unfortunately unusable and you will need to repopulate the translation in a fresh file following the correct procedure for bilingual DOC files. Hopefully you'll be able to rescue most of your translation from your TM and place it in the new file, although of course you'll need to remove the extra Trados codes. Once you do this and produce your target, your tags should be there. : )
  • Nora and Paul - Thank you so much!
    You figured it out.
    Your instructions, Nora, were perfect.
    I can't thank you enough.

    The instructions that were handed to me were to remove the tw4win tags prior to opening the file in Trados Studio.
    This was most likely an answer to someone else's issue that wasn't mine, but was handed down as gospel.
    This was clearly the issue; not doing so made the file completely workable (I had the right filters installed, but they were being bypassed because of the tag deletion).

    OK - back to work, without pulling my hair out!

    Thanks again!

    Sanda