Not Considering

WS shouldn't write unconfirmed segments to the TM

Similar to TMS, WS shouldn't write unconfirmed segments to the TM at all. Linguists leave segments unconfirmed, generally, in order to keep them from the TM for a variety of different reasons including: one-time project specific instructions, one-time ICR or other third party feedback that shouldn't be implemented in the future, etc.

Suggestion: Create a setting to let organizations choose if unconfirmed segments should be written to the TM or not.

Rebecca Herrera
Parents

  • The WorldServer TM is unique in that it support segment statuses. A TU can be 'Pending Review' or 'Reviewed', depending on which step in the workflow the TM was updated in Live TM mode. This means that newly translated segments are available for leverage for new projects while their review is pending or in progress, potentially lowering costs. In this case, TUs with this status should be penalised so that it is clear that are unreviewed.

Comment

  • The WorldServer TM is unique in that it support segment statuses. A TU can be 'Pending Review' or 'Reviewed', depending on which step in the workflow the TM was updated in Live TM mode. This means that newly translated segments are available for leverage for new projects while their review is pending or in progress, potentially lowering costs. In this case, TUs with this status should be penalised so that it is clear that are unreviewed.

Children
No Data