Thread: How to QA files in Memsource

Hi everyone

Here Im trying to help with another simple explanation. I hope this helps!

Once we are done with our translation or editing task, we need to run the Memsource QA to make sure everything is OK before changing the project status to “Complete”. Sometimes, when files are short, this can be done really easy and fast. Some other times, especially when files are too long or formatting is too complex, the QA might take a few more minutes.
Here´s a step by step guide so that you can run the QA efficiently and set the status to “Complete” without simply ignoring all the QA results.

1. If you translated more than one file, it’s better if you download a “joined” file to run the QA and apply the corrections. This is due to the fact that you may spot something to be fixed in one segment and then you will be able to:
   
   1. Auto-propagate that correction if it is a repetition.
   2. Use the “Find & Replace” feature (similar to MS Word) to make all corrections at once.
   
   
2. Go to the tab “QA” and then click “Run”:

3. You will see the message "Processing". Once it has been done, you ́ll get a list with the potential issues to solve (The longer the file, the longer the processing will take). Some of the issues reported will need to be corrected (typos, double spaces, missing tags, etc.), and some of them will be correct as they are and you ́ll just have to ignore them (numbers for letters, tags in a different position because of word order changes, etc.)

4. Memsource will only show you about 25 issues per round of QA, so you might have to run the QA more than once, depending on the size of the file and the QA settings. If entries are too many, the message “Show me more” will display at the bottom of the list. Just click there and the QA log will be refreshed.

5. Hiding “ignored” entries: Read the text box of the above screenshot to do so. This will narrow down the list to the last/new entries to be evaluated and corrected if necessary. Once you ́ve done this a few times (especially in long files or joined files), you ́ll see the message “Done”. Remember that if you decide to make any fixes, you always need to rerun the QA for it to show as “completed” for the PM.


6. When done, you can now change the status to “Complete”. Make sure to always save changes and upload latest versions to the cloud to apply the corrections to the actual bilingual files and TM.

Bonus Track! : To run an efficient spell check, you can also go to Documents > Export to Bilingual DOCX and then you will be able to run the MS Word spell check through the target column.