Hi Roberta Bogni 

Unknown said:

1) The client sends a .WSXZ format packet, which is never an issue.
2) The translator works on it, and sends back to us a return package, as usual. The difference now is that the translator changed from 2015 to 2017 Studio version, and the format of his return packages seems to now be .sdlrpx.wsxz (and not any more simply .sdlrpx), which creates problems to us when uploading it to our platform.

The format of a return package from Studio 2015 and earlier has always been this way.  I just tested a package in Studio 2015 and see this:

I recall there being a bug in a much older version that actually named the package *.SDLRPX and didn't add the correct extension and this caused problems for WorldServer users because WorldServer expects to see WSXZ at the end.

Please double check that you are not doing anything different.  If you send a package from Studio it then it will always come back with the SDLRPX extension.  But if you send a package from WorldServer, and not through Studio first, then it will always have a WSXZ extension.

This article might be helpful:

https://multifarious.filkin.com/2012/12/17/working-with-packages/

If you don't agree with any of this then perhaps we can set up a quick call and you can show me?

Hi Roberta Bogni 

Unknown said:

1) The client sends a .WSXZ format packet, which is never an issue.
2) The translator works on it, and sends back to us a return package, as usual. The difference now is that the translator changed from 2015 to 2017 Studio version, and the format of his return packages seems to now be .sdlrpx.wsxz (and not any more simply .sdlrpx), which creates problems to us when uploading it to our platform.

The format of a return package from Studio 2015 and earlier has always been this way.  I just tested a package in Studio 2015 and see this:

I recall there being a bug in a much older version that actually named the package *.SDLRPX and didn't add the correct extension and this caused problems for WorldServer users because WorldServer expects to see WSXZ at the end.

Please double check that you are not doing anything different.  If you send a package from Studio it then it will always come back with the SDLRPX extension.  But if you send a package from WorldServer, and not through Studio first, then it will always have a WSXZ extension.

This article might be helpful:

https://multifarious.filkin.com/2012/12/17/working-with-packages/

If you don't agree with any of this then perhaps we can set up a quick call and you can show me?

Unknown said:

Aha, I see... if Studio 2015 creates these "double extensions", then I bet the "problem" is the damned Windows 'hide extensions for known file types' feature :(
People have no clue that they are not seeing the real extension, but actually a part of filename...

That's a very good point Evzen... many users work without showing the extensions so this could easily be a project manager just not seeing the real extension.

Unknown said:

Inventor of this "feature" should burn in hell forever...

Perhaps a little harsh ;-)