Issues resolved in WorldServer 11.3.7

An overview of the issues that have been resolved in WorldServer 11.3.7.

Deployment notes

If you are upgrading from a WorldServer version earlier than 11.3.3, do one of the following:
  • If you want to deploy this cumulative update through Tomcat, uninstall your current Tomcat version, and then install the Tomcat version included in the cumulative update kit.
  • If you want to deploy it on a WorldServer instance installed with the installer, uninstall your current WorldServer version, and then re-install it using the installer included in the cumulative update kit.
You do not need to do this if you are upgrading from WorldServer 11.3.3 or later to 11.3.7.

Also, to apply the fix for CRQ-12097, upgrade the File Type Support (FTS) Server to the version included in the cumulative update kit (11.3.0.1752).

Resolved issues

Affected area or componentIDDescription
Integration with SDL Trados StudioCRQ-17390Fixed an issue which prevented users from opening WSXZ packages in Studio in a specific scenario (projects created by using Explorer, the project workflow includes the Generate Translation Kit automatic action, and Studio GUID generation is enabled in the Sdl.WorldServer.FileTypeSupport.Server.HostProcess.exe.config file).
CRQ-12097After you apply Language Cloud machine translation to a WorldServer project in Studio and import the return kit back into WorldServer, the segments with the Translation Approved status in Studio now have their correct equivalent in WorldServer.
Third-party componentsCRQ-16486You can now use saxon.jar alongside xalan.jar for XSLT processing.