Hello David Wright

Please try to import the files manually.

Every Studio package is essentially a compressed file, and therefore can be extracted like a zip file to access its content in Windows Explorer. If you have 7-Zip, right-click on the package and extract the contents to a folder, or first change the extension (.sdlrpx) to .zip and then extract the file. 
Among the extracted files you will see a subfolder with the target language abbreviation. Take this file and copy+paste it into the Studio project folder, in the target language subfolder of the given project. Then when you open the file in Studio you will see the returned file.
(Feel free to first create a backup version of the original target file before overwriting it.)

Hope this helps.

Looking forward to hearing back from you.

Best wishes,
Greta

Greta Magyar - Customer Success Consultant - SDL

Hi Greta

Thanks for that. Followed your suggestion and it worked perfectly.

But everything was working perfectly up to yesterday when I updated the software after receiving an update alert. Is this a bug in the update that the team is working on resolving or will I have to follow your instructions for all files from now on?

Thanks again Greta.

David

Hi David,

I have experienced this error before in previous Studio versions, so I don't think this is related to this update. It might have been caused on the other side, by the person who created the package, something caused inadvertently by their setup.

I will see of I can recreate this on my computer.

Best wishes,
Greta

Hi Greta

Thanks again for your feedback, but it is something that since this morning is affecting all of the return packages we are receiving from different translators in different parts of the world, so it looks like it's a problem on our end rather than their end.

We very much appreciate your help. Thanks Greta.

David

Hi Greta 

Did you get a chance to check if this is a bug that will be resolved or will we have to work the way you describe from hereon in?

Thanks again Greta.

David

Our company had a problem after we installed the latest Trados Studio 2017 updates (and Trados Studio 2019) when working with returned packages from freelance translators who work in older versions of Trados Studios. Trados Studio issued a warning about the problems in the file names, if the file names contain Cyrillic characters or umlauts. It seems that in the latest updates, developers began to use Unicode when archiving packages when codepage 437 was used in older versions. We had to write a converter for the codepage in the file names in the archives.

Hi,

I have the same problem while opening .sdlppx. It has a termbase with "ü" in the name and it saves differently to temp files. If I use the zip method I'm not sure the return package will work properly. Is there any chance to change saving temporary files setting in Studio?

Hello Lenka Rajnochová, David Wright

Which version of Studio are you using, could you please confirm?

For Studio 2019 the issue has been fixed in Service Release 2, issued last week. If you have Studio 2019, please install this update package.

For Studio 2017 this issue has been logged and our support team is working on it.

Best wishes,
Greta

Dear Greta, I use Studio 2017 SR1. Thank you for replying!