Dear Paul,

Thank you for your message. The idea Jerzy suggested was indeed not an option since we need to merge the files. I ended up making a new project and pretranslated the original file based on a new TM. The new TM was based on the split documents.

I will send the merged file to your mailbox as well so you can have a look at it. Maybe you know how to solve this in future situations. We are using this functionality for one particular client and it would be great to prevent problems like this in the future.

We use Studio 2015, version 12.0.4837.1

Thank you for having a look at this.

Kind regards,

Joey, Iris' colleague

Dear Joey,

Thank you.  I just wanted to close this off with a quick explanation of the problem here so it's useful for others perhaps.

The merged file that was being opened was a file created after merging the split SDLXLIFF files created with the Split n Merge App.  So this thread is not about merging files in Studio.

This is a difficult one to find the source of the problem for the following reasons at least:

1. The Split n Merge app is old and depending on the original source filetype there could have been changes in the filetype settings that have now introduced a problem where there wasn't one before.
2. The split files could have been handled in tools other than Studio and possibly making small changes to the translated SDLXLIFF which the Split n Merge app is not expecting, so it merges them incorrectly.
3. The split files might contain comments, tracked changes, merged segments... and possibly other things that have changed since the app was developed so these might also cause a problem
4. One, or more, of the SDLXLIFF files might have become corrupted in transit

There are probably other changes too, but this is quite a tricky problem to nail down.  The solution Joey Veldkamp mentioned is probably the best one, to pretranslate the original source from a TM.  I did the same thing to resolve this, but I converted the merged SDLXIFF to TMX using the Sdlxliff2Tmx app on the OpenExchange as this isn't so fussy as tools using the underlying Studio api.

So I don't have a good anwer for this, only a suggest approach which is to always make sure you have the TM for the translations and then you can pretranslate the original file.

Regards

Dear Joey,

Thank you.  I just wanted to close this off with a quick explanation of the problem here so it's useful for others perhaps.

The merged file that was being opened was a file created after merging the split SDLXLIFF files created with the Split n Merge App.  So this thread is not about merging files in Studio.

This is a difficult one to find the source of the problem for the following reasons at least:

1. The Split n Merge app is old and depending on the original source filetype there could have been changes in the filetype settings that have now introduced a problem where there wasn't one before.
2. The split files could have been handled in tools other than Studio and possibly making small changes to the translated SDLXLIFF which the Split n Merge app is not expecting, so it merges them incorrectly.
3. The split files might contain comments, tracked changes, merged segments... and possibly other things that have changed since the app was developed so these might also cause a problem
4. One, or more, of the SDLXLIFF files might have become corrupted in transit

There are probably other changes too, but this is quite a tricky problem to nail down.  The solution Joey Veldkamp mentioned is probably the best one, to pretranslate the original source from a TM.  I did the same thing to resolve this, but I converted the merged SDLXIFF to TMX using the Sdlxliff2Tmx app on the OpenExchange as this isn't so fussy as tools using the underlying Studio api.

So I don't have a good anwer for this, only a suggest approach which is to always make sure you have the TM for the translations and then you can pretranslate the original file.

Regards