| Table of Contents |
|---|
| Page Properties | ||
|---|---|---|
| ||
|
Introduction
XTM Workbench segments the source document into sentences and phrases. Below are the most common problems clients report in tickets concerning the XTM Workbench application.
...
| Info |
|---|
In XTM Workbench, you can work on more than one file/document at the same time. When the user has logged out from the PM GUI (from the current user account), the session opened in a separate tab should expire soon (after approximately 3-7 minutes). |
...
The XTM International Support team may ask you to send them the so-called HAR file, to further troubleshoot the issue.
Follow the steps below:
Open Google Chrome and go to the page where the issue is occurring.
Look for the ⋮ button and select More Tools → Developer Tools.
From the panel that appears, select the Network tab. You must keep the menu open while you reproduce the issue; select the WS option in the Network tab.
Reload your browser to see the traffic over WebSocket (which is for XTM Workbench issues only).
...
Look for a round record button in the upper left corner of the tab, and make sure it is red. If it is grey, click the button once to start recording.
If it is not, check the Preserve log box.
Click the crossed-circle button to clear any existing logs from the Network tab.
Reproduce the issue while the network requests are being recorded.
Click the download button, Export HAR, to download, and save the file to your computer: Save as HAR with Content.
...
After you open XTM Workbench for the affected project, you see the "INITIALIZATION_ERROR" message
...
Solution: Ensure that you have only one XTM Workbench tab open at a time by closing the rest. If you still experience the issue, perform the basic troubleshooting steps specified in the first issue above.
Segments locked up in XTM Workbench due to no editing rights
...
This issue occurs when you open XTM Workbench in <em>“Read-only</em> mode, for a particular file.
Solution: Ensure that the Read-only option is not selected when accessing XTM Workbench.
...
XTM Workbench
...
Our editing tool only permits one user to operate on a particular part of the document at a particular time. If, for example, you have your file opened in the 1-100 segment range, the second user who attempts to access that part of the file will find that they are locked because the previous user's session is still active.
What is more, if another user enters the next workflow step right after the preceding step is finished, the segments will also be locked.
As in the case of the previous issue, this, is yet another security measure. It prevents two linguists from modifying the same part of a file at the same time.
Solution: This behavior can be modified by using different workflows, but as a rule of thumb, you should just close the XTM Workbench window, wait patiently for around 10 minutes and then start the editor again.
In some rare cases, if a user closes XTM Cloud incorrectly, with the XTM Workbench opened, that user's session (still open in XTM Workbench) can linger for a while, blocking your access to segments as though the user was still working. In such cases, waiting around 5 minutes before accessing the file again should help.
If the lock is only on one file and does not time out after some fixed time interval, moving your workflow back or forth solves the issue.
XTM Workbench cannot be opened for subcontracted projects
...
When you open XTM Workbench and see that target segments are pre-populated with such TM match types as ICE Match, Leveraged Match, Fuzzy Match, or Fuzzy Repeat, it means that some of them have been enabled to populate the target automatically, in the global settings of your XTM instance [Configuration → Settings → Translation → TM → (ICE matches | Leveraged matches | Fuzzy matches | Fuzzy repeats) → Populate target with match]:
...
. Therefore, consult the settings with your XTM administrators.
...
If you are switching between segments in XTM Workbench in the Edit mode and see that a TM match is inserted as you go, this behavior is caused by XTM Workbench shortcuts, specifically the one mapped to the Enter key. In XTM Workbench, go to Settings → Shortcuts → Matches:
...
As has been shown in the screenshot above, by pressing enter XTM will complete the segment, go to the next segment and select the best TM match. If you would like to avoid this behavior, it would be best to re-map the enter key to a different shortcut, that has not yet been used in your mapping.
| Info |
|---|
The XTM Workbench shortcuts are set per user. |
The message: New window cannot be opened due to browser settings pop-ups and redirects are not allowed. Please change the relevant browser settings and then refresh Workbench. displays when trying to open an XTM Workbench session in a separate tab/window in a browser.
Sometimes you might want to open up an XTM Workbench session in a separate window/tab but you see the following message in the editor:
...
As the message suggests, the issue is related to the setup of pop-ups and redirects in your browser. You cannot open XTM Workbench in a new tab/window since your browser does not allow sending pop-ups and using redirects.
Solution: To resolve the problem, depending on the browser you are using, you need to find relevant browser-specific instructions for how to change proper settings – specifically, unblock pop-ups.
For example, here are the instructions with regard to Google Chrome: Block or allow pop-ups in Chrome.
Unsupported browser impacts XTM Workbench
You might sometimes experience that issue that relates to XTM Workbench kicking your linguists out after translating every single segment where the application becomes unresponsive after a particular segment is confirmed, and the only solution is to close the file and open it again.
Solution: The problem stems from unsupported internet browsers.
To ensure all the features of XTM Workbench are working correctly, XTM Cloud version 13.10 requires the latest version of modern internet browsers. Unfortunately, older operating systems such as Windows 8 do not support the installation of these newer browser versions, which may result in compatibility issues.
Unfortunately, it is not technically feasible for us to support outdated browser versions without compromising the platform's performance, security, and the ability to deliver future improvements.
To continue using XTM Workbench without disruption, we recommend upgrading your operating system to a version that supports the latest browsers.