...
Below are the most common problems clients put forward report in tickets with regard to the concerning translation memory (TM).
Before consulting reading the article below article, you may want to familiarize yourself with a we recommend that you read the step-by-step guideline on how to import importing your TM: How to import a translation memory (TM) into XTM. |
|---|
...
This is one of the most common issues a user who is importing a TM can encounter in XTM . On every server, a file upload limit of 150MBs is established, and if Cloud. The largest file size you can upload to any server is 150MB. If your file exceeds this limit, the import will fail with and an error will be generated.
Solution: There are a couple of solutions you can implement to work resolve this around:
Divide your file into smaller chunks;,
Zip your files and upload the zip archive;,
Delete unnecessary parts of the file, mainly especially duplicates, to make it 'slimmer'.
...
Solution: When uploading a TM file, please, make sure that entities that are not supported by XML standards are properly escaped.
For example, characters like & (ampersand)has to must be inputted entered as &.
If such characters of this type are not correctly escaped, the file will error out, fail to import and the process will fail, either partially or fully fail. Online completely. You might find online syntax checkers can be helpful when determining you check if your file holds complies with character standards. Please, see See an example of such this kind of site: https://www.xmlvalidation.com/. Validate XML files.
TM import cannot be performed because
...
a file format is unsupported
A third major contributor to issues with TM is the wrong an unsupported file format or faulty structure.
Solution: The currently supported TM file formats are as follows: TMX, XLIFF, XLS.
Please, see See attached a zipped file containing each sample file for its respective specific format:
| View file | ||
|---|---|---|
|
"&" or other special characters being displayed in the TM
...
source
This can happen after uploading the a TM alignment file where in which source segments display & marks,
whereas the desired required format would be that of &.
Solution: Please, follow Follow the steps below:
Export affected TM (please, click here for help);
Delete affected TM;
Perform the "Search and Replace" option in the exported TM document and replace &into with &;
Import back Reimport the corrected TM (please, click here for help).
Can the deleted TM be restored?
Solution: If you have deleted a TM by an accidentmistake, the XTM International Support team can only restore it only if the following option was enabled on your account prior to this incident (administrative privileges required!): Configuration → Settings → Translation → TM → Matches - general → Save TM in segment history.
...
If this is the case, please, raise create a support ticket to for the XTM International Support team and provide the details.
| Info |
|---|
If the deleted TM pertains is only to for one or two projects, keep in mind that you can always retrieve it directly from the XTM Project. Please, go Go to Project editor → Files → TMX, and generate the file in question. You can then seamlessly use it for re-importing reimporting the TM from this very project. The file is generated live from whatever is found in XTM Workbench at a given particular time. |
Batch change of TM status
If you find that your TM having has Approved or Not approved status in the TM basedatabase, contrary to your expectations, the XTM International Support team can perform a batch database change for such that TM.
Solution: Please, create Create a support ticket to for the XTM International Support team and provide the following information:
Customer that the TM is connected to;,
Language combination;,
Specify if the change has only needs to be performed only for the TM related to a specific project or projects (s) (provide its name or ID(s) - please, click provide their names or IDs. Click here for help.) or all of the projects under with this particular customer and language combination.
What
...
is SYSTEM:USER: AUTO-STEP that appeared in the place of user details?
...
Solution: "SYSTEM:USER: AUTO-STEP"; if this occurs anywhere in the TM-related part of XTM Cloud, this means that a given particular match was created due to by an automated step or process. Typically, it is the Approve TM or action or a bulk action such as Rollback that are as a Rollback that is marked this way. In the cases above cases , this is the expected behavior.
Records cannot be found in the TM tab
...
, even if they do exist in XTM Cloud and are displayed as a match in the editor
Sometimes, you may might not be able to search for records for single or multiple languages in the TM Manager tab.
Solution: In this case, we recommend that you contact the XTM International Support team as soon as possible in order to find the cause of this problem. This is usually related to damaged translation memory indexes, which may might have broken down been damaged during a sudden or unexpected downtime or if the XTM Cloud services restart. In such a case, a reindex of the TM needs to be performedreindexed.
Before raising creating a ticket, however, please, make sure you are well familiarized with have a good understanding of what TM reindexing actually is and what details to include in on the ticket form from . You will find this information in the relevant article: Reindex Reindexing of translation memory.