Known issues
A list of issues that are known to exist in SDL WorldServer 11.2.
| Component | ID | Issue name | Description or workaround |
|---|---|---|---|
| SDL Trados Studio integration | WSXI-8455 | Entering long segment comments in Studio or long comments in DOCX files leads to WorldServer import failure | If you export a WSXZ translation kit from WorldServer, open it in SDL Trados Studio, add a long comment to a segment (for example, 4000 characters or more), and then import the kit back into WorldServer, the kit is not imported. The same may happen when substituting SDL Online Editor for SDL Trados Studio. Also, if you create projects in WorldServer using DOCX assets with long comments, the assets are not segmented, resulting in an Auto Error step. |
| Microsoft Edge | WSXI-5071 | Java and Silverlight are not supported in Microsoft Edge | Microsoft Edge does not support applets. Therefore, you have to use another supported browser to open pages such as the Workflow Editor or file type configurations. You can still open WorldServer Explorer in Microsoft Edge by using the Java Network Launching Protocol (JNLP). |
| SDL Online Editor | WSXI-8472 | SDL Online Editor cannot be opened in Internet Explorer | You cannot open SDL Online Editor in Internet Explorer. You should only open it in the following browsers:
|
| WSXI-9026 | Locked content added in Studio is duplicated in the SDL Online Editor | If you lock selected parts of segments in SDL Trados Studio, and then import the asset back into WorldServer, the locked selections are duplicated. Locks are also duplicated if an asset imported from SDL Trados Studio contains tags that are marked as non translatable in the configuration of the file type. | |
| WSXI-9389 | Inline locked embedded content is duplicated in the target with the number of SaveToWS actions executed | If an asset that you want to edit in SDL Online Editor contains locked inline content, that content is duplicated in the target each time the SaveToWS workflow step is executed. | |
| WSXI-8979 | Selection comments are not converted properly from BCM to WS | The selection-level comments that you add in SDL Online Editor are displayed in Browser Workbench as segment-level comments. Selection-level comments are also displayed as segment-level comments in SDL Online Editor if users open the asset in another step than the one in which the comment was added. | |
| WSXI-9169 | Error icons for segment are no longer displayed in Browser Workbench after conversion from BCM to WS | Segment errors added in Browser Workbench are displayed as comments in SDL Online Editor. Moreover, if you open an asset in Browser Workbench, then open it in SDL Online Editor in a different step, and then open it again in Browser Workbench (also in a different step), the errors you added in the first step in Browser Workbench are lost. | |
| WSXI-9151 | Differences between task statistics | At the moment, WorldServer and SDL Online Editor use different word counting mechanisms. Therefore, in certain cases, the number of words and the task completion percentage displayed in SDL Online Editor are different than the ones displayed in WorldServer. | |
| WSXI-9139 | MT score is lost in Browser Workbench after saving the online asset | Apply machine translation to an asset, and then open it in SDL Online Editor. After you complete the step (and the Save Online Asset automatic action is performed), open the asset again in Browser Workbench. The segment score is 0 (zero) for all machine-translated segments. |