Different codes in source and target/missing spaces

Question

Hi, 
 I just delivered 9 files to my client. When they open the XLIFFs in Poedit or iXLIFF and when implementing in Articulate, there are spaces missing - mostly in between two segments. 
 Furthermore, in Poedit the codes in the target text are different from those in the source. 
 Where can that problem come from? What can I do to solve it, because that is what the client is asking me to do. They say it must be a Trados issue. 
 I am working with Trados Studio 2017. 
 I would be greatful for quick advice/help. 
 
 Kind regards, 
 Janet

Paul · Answer

Janet Klünder 
 I don't have 2017 to hand, but the issue sounds like a setting at your end related to normalizing spaces. When you set up your filetype settings did you preserve the whitespace like this? 
 
 Janet Klünder said: Furthermore, in Poedit the codes in the target text are different from those in the source. 
 Can you elaborate on what this means? Share a screenshot showing the differences? Also show the relevant segments in Trados Studio. When you say different are they changed, additional, missing? I'm guessing you may have used the setting for adding segmentation information to the target file as I think was the default in 2017. If you didn't turn it off (because your customer doesn't/can't use them) then you will have added a lot of additional code to every target.

Oana Nagy · Answer

Janet Klünder If I understand you correctly you have a native XLIFF file that got converted to XLIFF.SDLXLIFF for translation purposes. You then proved your client translated XLIFF files back? 
 Its easy to check the spacing between segments, if that is what you suspect by opening the XLIFF.SDLXLIFF and translated XLIFF files in something like Notepad++ Then comparing the two files based on an example string. Happy to try help provided you can safely send the files. 
 
 I trust this helps a bit 
 Lyds

Paul · Answer

Janet Klünder 
 I created a quick video to try and explain. So far I cannot understand what problem you are really having as your screenshots don't tell us anything. You need to be a bit more specific. I can see a problem with white spaces in 2017 as they get removed even if I have the setting checked to preserve... but I'm not sure if this is by design for the example I created. It would be better to see your file. 
 Anyway... check the video and see if it helps? Maybe you can explain better what the problem is after seeing this, or at least provide sample files of the original source and your target XLIFF?

Paul · Answer

Janet Klünder 
 In fact sorry... that was for Studio. Looks like the KB doesn't go that far back for MultiTerm. 
 I suggest you simply log into your account and download it from there.

Trados Studio > 1. Trados Studio

Different codes in source and target/missing spaces