Hello,

Annemieke Jennissen already reported this issue more than a year ago (see question https://community.sdl.com/product-groups/translationproductivity/f/90/t/7001#pi6614=2, posted on the 8th of April 2016), but as she stated herself last month on that very issue report, this problem has still not been resolved in latest (nor previous) version of Studio and apparently there are no news so far about it.

I am sorry if this might be a duplicated issue, but I think that a +1-year period exceeds by far the reasonably acceptable timeframe that can be expected for a solution (or at least an answer) to be received when there is software functionality not working as it should.

I understand that perhaps this is not an issue in the top of the list of SDL developers' priorities and that it might have get misplaced/forgotten in the meantime, but the fact is that there are many clients sending WSXZ packages for translation and it would be great to leverage in such packages the same features SDL Studio offers for any other package.

Could anyone have a look at it and ideally provide a solution for this issue? (Or temporarily, an explanation about why does this happen?).

Thank you in advance for your help.

Best regards,