There are 4 possible root causes for the project
%Translated column to display
Not segmented in combination with
the
Total Words column to display a question mark and the
Translated Words column to display
0 words
:1- All the project's tasks have not been segmented due to a segmentation error (Autoerror) or because the Task(s) have not yet reached the
Segment Asset workflow step.
2- In a project with more than one task, at least one task has not been segmented due to a segmentation error or because the Task has not yet reached OR completed the
Segment Asset workflow step, as displayed in the screenshot above. If at least one Task has not been segmented, the project's
% Translated status will display as
Not translated.
3- In a project with more than one task, at least one task has been segmented, but no translatable word count has been found therefore, the total word count is
0. Basically, if at least one Task has
0 words, the project's
% Translated status will display as
Not translated.
4- The project is affected by a defect where the scoping report of the project wrongly displays
0 word count. This defect happens in
WorldServer 11.3.x. More details and a reference to a Hotfix can be found in this article:
Ad-hoc scoping in WorldServer 11.3. leads to inconsistent Total wordcount and error 'Word counts of some assets are inconsistent:' and 'Errors were found in the scoping information'
