When you upgrade
an existing system to WorldServer 10.0 and enable live translation
memory (TM) mode, you must be aware of a number of considerations.
Note: Live TM mode was introduced in WorldServer version 9.0.
When you upgrade to WorldServer 10.0, the status of all of your TM
entries is set to
Reviewed. Also, in non-live mode, whenever an entry is written to the translation
memory it is given a reviewed status. This holds for all places that
the translation memory is updated, including the Browser Workbench,
import, and automatic actions such as
Save. This helps you learn
that entries added to translation memory the old way are considered
“Reviewed” and also ensures that leverage works correctly when you
first enable live mode.
Note: There is no need
to specifically change leverage behavior, scoring, or concordance
search for non-live mode, since every entry in the translation memory
has a status of Reviewed. Any penalty or special behavior based on TM entries with non-Reviewed
statuses therefore never occurs.
Because you might have workflow customizations that make explicit
calls to update the TM from a segment cache, WorldServer checks for
such explicit calls when live mode is enabled. If it detects a call
to update the translation memory, it logs a warning indicating that
the approach is deprecated. This is intended to help you find parts
of your configuration that are not taking advantage of or are incompatible
with live mode. As an example, you might have a Save automatic action with Update TM enabled.
Consider the following:
- In the old model, your translation memory was only updated when you
specifically indicated to update the TM or if you put certain automatic
actions such as "save” in your workflow. Your main concern was making
sure that everything got into TM by the end of your projects. In the
new model any segment with a translation status other than none will go into the translation
memory. Your main concern is making sure that by the end of your workflow
all segments are set to Reviewed. Look at the instructions you give your users
and your workflows with this in mind, to figure out what you need
to change.
- If you are currently using Save with Update
TM at the end of your workflows to ensure that the TM is
updated, consider adding a Set Translation Status auto action step just prior to Save, to set all segment
translation statuses to Reviewed.
- If you are using TRADOS or some other tool, on import all translated
segments will be set to Pending Review. If you consider the work your LSP does
to be “Reviewed”, then put a Set Translation Status auto action in the workflow after
the LSP to set all segments to Reviewed.
- Do not be concerned if you realize you have made a mistake and a
project finishes but some or all of the segments were never set to Reviewed. Use the translation
memory management page to find the appropriate entries in TM and set
them to Reviewed. Unlike the old model, you rarely need to worry about completely
losing translation memory.
- Monitor your log files for warnings. If you are using steps in your
workflow that are explicitly updating translation memory, you will
receive a warning. You can use these warnings to improve your process.