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

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

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.

Make sure you save the target file as UTF-8. If the client is trying to import the XLF in DejaVu, you MUST modify the header. The header produced by Studio is:

<?xml version="1.0" standalone="no" encoding="utf-8"?>

But DejaVu accepts only this header:

<?xml version="1.0" standalone="no"?>

And the file MUST be UTF-8.