Problem with .xlf files in Trados 2017.

The client is complaining that the translated files he received back is mostly one big block of text rather than a more formatted version that he is getting from other translator. Is there some setting for .xlf files I am not aware of? I received the job from the client as .xlf files and simply translated them in Trados 2017 the usual way (creating a project). finalized when I was done and returned the completed package of files to the client. But the client thinks the format of the .xlf files is off. He also doesn't know why I send him the .sdlxliff files. Has anyone run into this problem before?

Parents
  • Hello Torben,

    There seems to be two things in here:

    Unknown said:
    the translated files he received back is mostly one big block of text rather than a more formatted version that he is getting from other translator

    I'm not sure I've come across this before, the more common issue is the target XLF containing additional segmentation information.  This is resolved by making sure you check this setting which is not checked by default:

    Perhaps this is really what the problem is?

    Unknown said:
    He also doesn't know why I send him the .sdlxliff files

    Neither do I.  If he sent you XLF files why don't you send him XLF files back?  You need to save the target file to convert the SDLXLIFF back to XLF.

    If none of this helps perhaps you can share a file or show some screenshots to explain the problem in more detail?

    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 Paul,

    Thank you for your answer. I tried setting the "Do not store segmentation information in the translated file" but it didn't solve the problem.

    Here is an example of how the file looks like after Trados is done with it:

     

    And here is how it should look:

    the file looked like the second example when I got it, but after translating it in Trados it looks like the first example. I have done the quality checks and I am not missing any tags that I can see.

     

    Hope you have an idea about what might be wrong.

     

    Best,

    Torben

  • Hmm, the first look you show is a normal look of any xml based file, while the second one is a "pretty print" look, which does not necessarily fit all tools.

    Does your customer have any problems with importing the translated file in his system? This should not be the case. As from what I know the tool goes by tags, not by what it does see...

    Of course I may be wrong.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • Hello Torben,

    Is this just a readability thing or having it like this actually causes a problem? It all looks correct, it's just missing returns at the end of the elements. So not really a block of text as I'd imagined it.

    Can I see a source file so I can test the process myself?

    Thanks

    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

Reply Children