Salesforce

WorldServer - Length verification from QA Checker Profile does not work in Online Editor when set to 'Check if target segments are within file-specific limits'

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Symptoms/Context
We have created a project using a QA Checker Profile. See also article: How to add a QA Checker Profile to a Project Type in WorldServer

The Length verification setting of the QA Checker Profile is set to Check if target segments are within file-specific limits:

User-added image

This means that the character length is set in the source XLSX file and in the Length limitation column set in the Bilingual Excel file type configuration that we use to segment the file.
Source XLSX file (example):

User-added image

File Type configuration:

User-added image

After segmentation, when opening the file in Online Edito and running the verification, the errors related to Length Verification are partially wrong and confusing The issue seems to be that the value set in row 1, column C of the source xlsx file is not taken into consideration so the max length values are not aligned with the actual segment, but with the below. Moreover, the last segment is not verified at all. See this small video:

User-added image

When exported to a WSXZ package, the Length verification in Trados Studio is correct, reporting the right errors:

User-added image

The issue is not reproducible in Online Editor in Trados Enterprise (August 2023).


 
Resolution
This issue has been filed as defect CRQ-34047.  It is reproducible in WorldServer versions 11.7.3, 11.8.0 and 11.8.1. (Online Editor versions up to 1.36.2).
The current disposition is version 11.9. We will update this article when the issue is fixed.

As a workaround, work in Trados Studio instead, or work in Browser Workbench after implementing some Automatic Actions as described in this article:

WorldServer - How to set the maximum character length of target segments for translation in Browser Workbench
Root Cause
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by