The following process can be used to work offline when your internet connection is temporarily down, when you are traveling, etc. Otherwise, using the desktop editor online is recommended since an internet connection is necessary in order to use the project's TM, TB or MT, run QA checks, and save the translation to the server. In addition, the Preview feature is only available online.
Step 2: Log in to your Linguist Portal and pre-translate your MXLIFF file through the Memsource pre-translate feature. You can set any pre-translate threshold you want (only available if there is a TM assigned to the project).
Step 3: Download the pre-translated MXLIFF file and start translating in Memsource Editor.
Step 4: Here, you can go offline. You will still be able to translate and have segments with some TM matches already pre-translated (but you will not have TM, TB, or MT matches in the CAT Pane).
Step 5: After you are back online, log in. (When successful, you'll see a green Login Indicator in the bottom right-hand corner of your Memsource Editor.) Click on Document and select Upload to Server. This will ensure that all of your content is uploaded to Memsource. Be sure to check the status in the bottom right-hand corner of the Desktop Editor window.
Note: If the Linguist user is working offline in the desktop editor and uploads the bilingual MXLIFF file in Memsource by clicking on Upload in Tools, the segments are automatically saved to the TM.
Step 6: The translation can be also uploaded in your Linguist Portal (by going to Tools and clicking on Upload) or sent via email to your Project Manager who can then upload it for you.
Step 7: Don't forget to run a QA check and to resolve all problems before setting the job to Completed.
Reasons Why an MXLIFF File Could Not be Uploaded
- The MXLIFF has broken
- This can happen if, for example, it was translated in another CAT tool.
- The MXLIFF belongs to a different project
- Sometimes translators misunderstand the workflow in Memsource. They create their own projects and then try to add their MXLIFF files to their clients' accounts.
- The MXLIFF belongs to a different workflow step.
- The MXLIFF file should always be added to the same workflow step that it was exported from.
- The job has been deleted
- The job into which the MXLIFF file belongs has been deleted, but the translator has continued to translate the deleted MXLIFF file. Because the job was deleted, the connection between the server and the MXLIFF file was lost (you cannot connect to deleted jobs). The translator must have therefore worked offline (the square indicators in the bottom right corner were red).
- The solution for this is on the PM's side. Locate the deleted job in the Recycle Bin by going to Settings on the Memsource page and clicking on Recycle Bin in the Tools section. Undelete the job and ask the translator to upload his/her MXLIFF to update the (previously deleted) job.