Checklist to verify the project configurations via XTM Workbench prior to starting the project
Verify that the number of segments and the source text match what is expected in the file. This is done by scrolling to the bottom of the page in Workbench and looking at the value in the No column (far left).
Tip
Troubleshooting: Verify that the correct file was uploaded to the project by opening the project editor with the Files option in XTM Cloud
If migrating from another system, verify that the translations appear in the target column. If they do not appear there, use this checklist as a troubleshooting guide.
If terminologies exist for the customer in this project, click on a segment containing text that should have a matching term (all segments with a matching term have a blue font color).
Check to see that the term is there on the bottom right, If it is not then reanalyze the project. If that doesn't work contact the terminologist to add the terms.
Important
Reanalyzing a project should be done with caution after a project has started as it changes metrics and statistics.
If machine translation is used, and the translations have not been applied, or inline tags have not been copied over to the translations then, use this checklist as a troubleshooting guide.
Troubleshooting translation memory issues using Workbench as a project manager
From the top right-hand side, select Filter->Choose Filter->Match. From there check the 100% or ICE MATCH box. Click on Apply. If many results are found using this filter then:
Contact the administrator to enable TM autofill for ICE and leveraged Matches. The translations will then appear.
From the top right-hand side, select Filter->Choose Filter->Match. From there un-check the previous selection and check Fuzzy Matches and Fuzzy Repeats. click on Apply. If many results are found using this filter then:
There are three options:
Contact the Administrator to have all of the segments translated via autofill with these matches as a starting point for the translators (Please tell the Administrator the fuzzy match range to AutoFill).
Have the translators manually copy these matches one by one and change them.
If the match percentage is very high for all, but not quite 100% it might be a white space setting. Contact the TM Expert, to import the TM again with different settings.
Where TM matches are shown in Workbench
Once in Workbench (CAT), select a segment.
Scroll to the bottom and see if any TM matches exist.
Tip
Use the following reference in order to better understand the matching widget.
If no TM matches exist and this is a new system that has been migrated from another TMS or CAT solution then contact your TM manager to import the translations (TM) from the other software package.
Machine translation troubleshooting guide for project managers
Tip
Use this guide if segments have not been automatically machine translated in Workbench.
Important
For all items in this checklist, configurations need to be verified at the project and customer level by a project manager or at a global level by an administrator.
To determine which level configurations for MT need to be applied, consult this guide.
Important
Machine translation settings at the project level override machine translation settings at the customer level which override machine translation settings at the global level.
Verify if MT matches exist: Click on each segment and on the bottom left and see if a match with metadata of MT:<enginename> will appear in the matches tab.
If a match appears, then autofilling has not been enabled for the MT vendor.
If a match does not appear, contact the administrator to check the subscription information or to verify that the proper MT engine has been selected.
Note
Typically if this is subscription-related, an error will appear once Workbench is opened and will then disappear. Contact the vendor of the MT engine for help as well.
Note
If your department has a unique MT subscription then a project manager can check the subscription information at the customer level.
If inline tags have not been copied over to the translations properly then check the configuration using these instructions.