First steps with ApSIC XBench

ApSIC Xbench is a powerful Quality Assurance and Terminology Management tool.
Follow this quick tutorial and get a feel of it.

Download and install Xbench
First thing first, go to the XBench website to download and install the software on your computer. You can either go for the XBench 3.0 30 days trial or start with the free (yes free!) XBench 2.9. Here is the download page.

Download this sample .sdlxliff file (Trados file)
We have prepared a sample file just for the sake of this demo. You can download the sample file from here. The file type is .sdlxliff (Trados file). If you don’t have Trados, that is still okay you will not need it in this demo. (But as a professional translator it is highly recommended you do have Trados…)

Load the file to check in ApSIC XBench
Open XBench then select “New” in the “Project Menu” (shortcut: ctrl + n)

Drag and drop the sample file (First_Steps_with_Xbench.doc_en-US_fr-FR.sdlxliff) in the “Project Properties” window (or select it from “Add…” button).
In the next window, make sure to check the box for “Key Terms” as it is used for keyterms consistency check.


Click on the “OK” button.


In the next window, also click on the “OK” button.

Check the file using ApSIC XBench
Go to the QA tab, click on the “Check Ongoing Translation” button.


The result is pretty much straight forward.


As you can see XBench will list up all the errors it found in the file. The errors are listed by Error Description with the source and target segments next to it so that you can check what is the actual issue.
In this example the errors are of 5 types:
– Untranslated Segment
– Inconsistency in Target
– Inconsistency in Source
– Numeric Mismatch
– Key Term Mismatch

One neat feature is that by clicking and selecting an error segment XBench actually highlights what could be wrong there.Xbench_demo6

Let’s go through each one of them:
– Untranslated Segment: obviously the segment has no translation, i.e. the target segment is empty.
– Inconsistency in Target: same source segment has been translated differently.
– Inconsistency in Source: different source segments have been translated the same.
– Numeric Mismatch: numbers in source and target do not match.
– Key Term Mismatch: because we have selected the “Key Terms” feature XBench picks up keywords and make sure the translation is consistent across the document.


See how XBench picked up the word “keyterm” (which doesn’t exists actually, yes 🙂 ) as a Key Term? XBench has spotted that keyterm should be translated sa “mot-clé” but it can’t find it in the target segment as it was replaced by “mot-clef”.
Important to note also that the first line shows in which file and at what segment the error is (the number after the file name in parenthesis is the corresponding segment number).

How to add a dictionary in XBench for spell-checking?
It is very simple to add dictionaries in XBench. This will be necessary if you want to perform a spell-check on the bilingual file.
Here is how:
In the “Tools” menu select “Spell-Checking Dictionaries”, select the right language then click on the “Install” button. That’s it!
You can run again the QA, but this time with the spell-check on.


Here you go!
You have performed your first XBench translation check. This is a powerful tool and should always be use as final check before delivery.  But never forget, this is just a mechanical check and cannot judge the overall quality of the translation, it only informs on consistency etc. and helps “debugging” your work.

Are you interested in joining Coreido’s expert translation team?
Register as a translator now:

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s