Hi Yves

Thank you for your feedback.

Could you confirm, please if you have the WS Xliff  Filter enabled in Studio from Add-ins tab - Plug -ins?

Thank you

Regards,

Sorina

QA Engineer

Yes, it is enabled.

-ys

Thank you for your reply.

We started investigate what you reported, but we need the following details if possible:

1. The version of WS you use

2. How you export the packages from WS?

3. What filters you use or if you use legacy filters?

4. If you can send us a sample package to scuibus@sdl.com

5. What API you tried to use?

Thank you

Regards,

Sorina

Sorina Cuibus

We went through opening a ticket with Support and the answer was:

The Worldserver packages are now processed only via the WorldServer Component plugin: https://gateway.sdl.com/apex/communityknowledge?articleName=000013233

For API question please address it to the forum address from this article: https://gateway.sdl.com/apex/communityknowledge?articleName=000004568

Not very helpful I'm afraid. So I'm back in the community forum.

And my questions are still the same:

How can we create a project from a WSXZ package using the Trados Studio 2021 API?

And if the answer is "It's not possible" then the question is: How can we access the WsXliff file type from Trados Studio 2021 API?

Thanks for any pointer.
-yves

Hello Yves,

For one of our clients who uses WorldServer, we get directly the xlf files from him and prepare them with the xliff filter since Trados 2021. I got the information too, that the wsxliff filetype is not available to be used like a standard filetype in the preparation task.

The settings for the xliff filter are the standard settings + "Add segmentation information to the translated file" activated. We haven't seen differences with the wsxliff filetype after testing a couple of files.

Maybe you can adapt your existing program with this.

Kind regards

Sébastien

Hello Yves,

For one of our clients who uses WorldServer, we get directly the xlf files from him and prepare them with the xliff filter since Trados 2021. I got the information too, that the wsxliff filetype is not available to be used like a standard filetype in the preparation task.

The settings for the xliff filter are the standard settings + "Add segmentation information to the translated file" activated. We haven't seen differences with the wsxliff filetype after testing a couple of files.

Maybe you can adapt your existing program with this.

Kind regards

Sébastien