CAT tool access
We provide licenses to our vendors to work with our CAT tool. CAT stands for Computer Assisted Translation, so don't confuse it with the living kind. There is no need to acquire any software to work with us. When you accept a job, you can enter the CAT tool through the Works platform & you will get a license for the duration of that job. Once you have finished and completed the job, your license will expire. This means that you will not be able to log into the CAT tool directly, you can only access the CAT tool by clicking on the 'Go to CAT tool' link in your dashboard.
Use the 'Go to CAT tool' button to access the job you are working on.
Which will bring you to the landing page of the CAT tool:
You can accept several jobs at the same time, by selecting them and clicking on "Change Status" button! This way you'll be able to change the status to "accepted" :
You can also accept jobs one by one, just by clicking on the pencil icon on the right-side of the job check-box:
Note: You'll only see the pencil icon once you hover the mouse on it.
Working with our CAT tool
The ins and outs of the CAT tool
Using our CAT tool is quite intuitive & straightforward, but if it's your first time working with it, checking out this comprehensive guide for linguists can and will save you time in the long run.
These are the most important things you will encounter in the strings & how to deal with them
If you find a lot of tags in the strings, you are probably working on a translation for a website, app or other technical application. Also, tags may sometimes be used for content that should not be translated. If you're unsure what you're dealing with, consult the Memsource guide above to find out how to show what is behind a tag.
If a segment has been translated and reviewed before, it may be at 101% or 101% and be locked. You can't touch locked segments & you can ignore them. If you should however see a mistake in one of these, please do contact us at email@example.com with the project number, file name and segment number so that it can be corrected.
Why we have the QA tool enabled
Before you can complete a job in the CAT tool, you have to run the QA.
The purpose of the QA check is to:
Assure that you do a final check of the work they are delivering. Unfortunately, very often we receive jobs with basic mistakes such as double spacing, double periods, typos and others that may put us in a very compromising position in front of our clients. It is not always true that the REV step captures these things.
It is not possible to differentiate types of QA checks per project or per linguist or per language pair. The QA checks are setup at the system's level, so all projects are subject to the exact same QA checks.
In addition, it is not possible to "ignore all" warnings at once. That would defeat the purpose of the QA tool. We want you to review every QA warning and confirm that the warning is not an issue or give you the opportunity to fix something that you might have missed.
On QA warnings regarding fuzzy matches, whenever the TM proposes a translation that is not a 100% match and you accept it without making any edits, the QA Tool will point that out. We want you to review the proposed translation and be sure that this is what you intended it to be.
How to successfully use the QA tool
Here's how to manage the QA warnings:
- On the right side, at the bottom, you'll see four tabs. To run the QA, click on the QA tab (1).
- Click on the "Run" button to see all the warnings in the file (2).
- Each warning has to be fixed or ignored.
- To fix it, change the translation.
- To ignore it, click on the empty box on the right side. Column "i". By clicking on it, the warning will be ignored (3)
If you ran the QA tool and you still can't complete the job, try looking at only unsolved warnings, to do this click on "hide ignored".
After you have successfully completed the job in in the CAT tool, don't forget to deliver the job in Works as well. If you don't deliver both, the system can't calculate your work & you can't get paid.
If you can't find the answer to your questions in the articles on Zendesk, please contact us at firstname.lastname@example.org