Hi Corinna Schnermann

I have not tested that setup myself, but from my experience I would say you should be okay for the most part. However, engineering and technical support for Trados Studio 2015 ended in February 28, 2019. What this means is you run a higher risk of running into a corner case which may give you problems. I cannot give an exact estimate, but I would say 90% of the time you should be fine, however just like the lottery you might be the "lucky" person to hit one of those issues in the 10%...

Hi Corinna Schnermann

I have not tested that setup myself, but from my experience I would say you should be okay for the most part. However, engineering and technical support for Trados Studio 2015 ended in February 28, 2019. What this means is you run a higher risk of running into a corner case which may give you problems. I cannot give an exact estimate, but I would say 90% of the time you should be fine, however just like the lottery you might be the "lucky" person to hit one of those issues in the 10%...

Thanks Jesse. I didn't know that the technical support for 2015 ended... Well. I will probably upgrade. Thanks again and best regards, Corinna

Hello Corinna Schnermann ,

Im not sure if this applies to you or not- but further to Jesse Good comment and that we no longer support Studio 2015- as MS have dropped support for Windows 7- we can no longer offer full technical support for users on Windows7

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/5126/windows7-and-sdl-trados-studio-support

Hi Steven,

thanks for the info. My computer has Windows 10 :-) But I have two more questions:

1. If I upgrade my SDL Studio 2015 Freelance Plus license to Studio 2019, can I still use Studio 2015?

2. If not, is SDL Studio 2019 backward compatible? Because it does not make sense to upgrade if I cannot work for my old clients anymore.

Thanks

Corinna

Corinna Schnermann

Corinna Schnermann said:

1. If I upgrade my SDL Studio 2015 Freelance Plus license to Studio 2019, can I still use Studio 2015?

Technically no.  If you upgrade you are effectively replacing the 2015 with the 2019.  You'd need to purchase a new licence (as opposed to upgrade) so you owned both if you wanted to keep them both.

Having said this if you don't return the 2015 licence in the product when you upgrade, and you don't uninstall 2015, then you can continue to use it for as long as you have it running on your computer.  It will not be possible to activate it on a new computer, or to reactivate it if you return the licence.

So don't deactivate the licence in the product.

Corinna Schnermann said:

2. If not, is SDL Studio 2019 backward compatible? Because it does not make sense to upgrade if I cannot work for my old clients anymore.

What in particular do you want backwards compatibility for?  In general you should be able to handle everything you need with 2019.  But if, for example, you are expected to send back an SDLXLIFF that you created from the source so that your client can save the target in 2015 then this "may" not work for them.  If they created the SDLXLIFF and you translated it that would be fine, but you "may" not be able to save the target file, only the SDLXLIFF.  It depends on the filetype.

Hi Paul,

thanks for your answer. Maybe I used the wrong word. I just want to make sure that I can handle projects and packages which were created in older SDL Trados Studio versions than 2019 so I can continue working for my clients. Because otherwise the upgrade does not make sense for me.

Best regards,

Corinna

Corinna Schnermann said:

I just want to make sure that I can handle projects and packages which were created in older SDL Trados Studio versions than 2019

Yes you can.  But even here you should be aware that if the package contained SDLXLIFF files that were based on older versions of the filetypes that are not available in 2019 anymore you might not be able to save target files.  You can translate the files and create a return package, but if your customer asked you to create the target files too you might not be able to.  It depends on the filetype as most filetypes have been updated at least once since Studio 2015.