Hello Ian Keith Jones Williams

This is definitely something to look into to have a proper solution for the future, but as a workaround in the meantime please try to unzip the package (as you would a normal zipped package) to a folder so you can extract the translatable file this way.

Please let me know if you could access the file.

Best wishes,
Greta

Hi Greta

Thanks but that doesn't work either. This is not the only problem I had this week with Studio. I generally have at least one on a daily basis. Will Trados ever produce a bug-free application?

Regards

Ian

Hi Ian,

As for the bugs I cannot tell you much, but I when you say that unzipping and extracting did not work, could you please elaborate? The file was extracted but even as a standalone SDXLIFF if could not be opened in Studio? Have you received a warning message, maybe the same?

Thank you,
Greta

-- Hi Ian, I have exactly the same problem. Were you able to resolve the issue?

-- Hi Ian,

just to let you know that I am now able to open client packages without any problems

I contacted SDL support and they said that it was a bug in the latest version (SR2) of Studio which I had installed when I bought a new license.

The root cause and one of the phenomenai s described in the following KB:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0029890

I do JA=>EN translations and many of the file names in the packages that I receive are a mishmash of Roman and Japanese characters.

To fix the problem I uninstalled SR2, then deleted various hidden files as described in

https://community.sdl.com/product-groups/translationproductivity/f/studio/20028/how-to-reinstall-studio-19-from-scratch

After rebooting my iMac, Parallels and Windows to be safe, I downloaded the old version (SR1) from the SDL download site (button on left to download archived versions) and then did a clean install of the SR1 version.

I can now open client packages without problems.

I hope that helps.

-- Graham