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.

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.

Hi Paul,

Thanks for your answer.

Yes, I have preserved the whitespace like this.

Spaces are missing all overt the nine files, mostly between two segments.

Here is an example of the differences the customer sees when opening in Poedit and an example of missing spaces.

  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.

I don't undestand what you want to say by this. What setting may I have used and not turned off?

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?

Janet Klünder 

It is by design... spaces between the attributes are not something which have any functional value and XML parsers should ignore them.  So it would be much better to see an example of your specific file.  You should be able to create a sample and anonymise the text as necessary.

Paul 

Maybe Janet meant this missing space:

Jesús Prieto 

Maybe... although I cannot reproduce tha at all using my test file:

I think we definitely need a better explanation of the problem and details to test with... if she wants sensible help.  It's always tricky when we have to guess.

Hi Paul, hola Jesús,

First of all, thanks for trying to help.

Yes, I was referring to the space Jesús pointed at. Spaces are missing throughout all the files I delivered, especially between two segments.

But before I go on explaining: my version of 2017 is

I will see right now if I can run updates.

Could the problems be caused by using an old version of Studio 2017?

Janet Klünder 

Janet Klünder said:

Could the problems be caused by using an old version of Studio 2017?

Definitely!  The latest versions you should be running are:

Trados Studio 2017 SR1 - 14.1.10018.54792
MultiTerm 2017 SR1 - 14.2.8.55461

If there is still a problem for you with that then the solution may have to be an upgrade.  2017 is pretty old now. Engineering and technical support for Trados Studio 2017 and MultiTerm Desktop 2017 ended on January 31, 2021. Since that date, services covered under standard maintenance agreements - including technical support, updates and new patches - have not been available.

Ok, thank you.

One more question: After running the updates, will the files I have translated before change as well? I mean, will problems due to the use of an older version diasappear in those files?

Janet Klünder 

Janet Klünder said:

After running the updates, will the files I have translated before change as well?

If there are filetype fixes for your problem in the update then no.  You would have to recreate your project from the original source so that the sdlxliff used the new filetype.

Hi Paul,

I have run the update of SDL Studio but I can't manage to download the Multiterm update.

After pressing "FTP site", I can select the application to use for opening the site but no matter if I try with edge or firefox... nothing happens. I don't get to the site. Is there any other way to run the update?

Best,

Janet