Hi Paul,

Thanks for your fast reply.

I have attached a sample file.

We are working with build 14.1.6278.

The file type we used is Excel 2007-2016.

Actually I just noticed that the problem only occurs with Studio packages that have been translated with Transit and then returned to us as sdlrpx.

However, when I look at the translation in Studio, it does not seem to differ structurally from other identical translations in other languages. Überarbeitung QDL-cs-CZ.xlsx

Hi Lutz M. 

Unknown said:

Actually I just noticed that the problem only occurs with Studio packages that have been translated with Transit and then returned to us as sdlrpx.

However, when I look at the translation in Studio, it does not seem to differ structurally from other identical translations in other languages.

Can we get a copy of the sdlxliff for your problem file after it was returned from Transit?  We'd need a sample of the one from Transit and the matching source excel file so we can compare the results properly to see what happened.  Certainly if Transit is making changes to the SDLXLIFF that cause this then there is nothing we can do to help with it other than to try and identify the problem so you can report it to Star.

Hi Paul,

Here is the Excel file we used to create the sdlppx and the sdlxliff after importing the sdlrpx.

Thanks for looking into this.

Downloads.zip

Hi Lutz M. 

In the meantime I just segmented the file with my own rules and can match your output.  There is an interesting difference because the process through Transit seems to replace line feeds with paragraph breaks, which Studio will not allow.  So I have this in Studio:

When the file that is returned after handling in Transit has this:

You should go back to Star and ask them to look at this because paragraph breaks are not allowed in the SDLXLIFF within a paragraph unit like this.