Hence, I have decided to explore Xbench, a QA tool for translation that allows translators and project managers to check the accuracy and consistency of translations.

Therefore, I decided to watch the tutorials in order to understand the purpose and basic features of this tool.

These are the videos that I watched:

For instance, I looked up the word "mountain":

At this point, I can select the chosen translation (let's take the glossary entry) and simply click Enter. This copies the term to the clipboard, and I can paste it directly in the target segment in OmegaT.

In this instance, I did not try to make mistakes on purpose for it to give me results, but as it turned out, I had made a typo, which Xbench promptly addressed: I wrote rOkres in Polish, which should have been Okres.

They are referenced accordingly in superscript in the portfolio, whenever they are used. Superscript numbers match the files as follows:

1. glossary.txt — Glossary used in Xbench

2. mountains 2-level1.tmx — Legacy TM used in Xbench

3. Mountains_ST.docx — Source text

4. Mountains_TT.docx — Target text

5. Mountains.xbp — Xbench project file

6. QA check.mp4 — Screen recording of a QA check

While it is already possible to verify the quality of a translation through proofreading, I recognise that in bigger projects, QA tools are a must-have, as they allow for the verification of terminological consistency, as well as checking for linguistic accuracy.

1. I have understood the need for QA tools within the translation industry.

2. I have learnt how to upload files on Xbench, assign priorities to files, and use the basic functionalities of Xbench alongside OmegaT.

3. I know how to perform a term search and how to analyse its results.

4. I have learnt how to perform a basic QA check effectively to find inconsistencies and errors in a translated text.

1. Creating custom RegEx rules to check for specific inconsistencies;

2. Discovering project templates available on Xbench;

3. Using plugins and automation.

Moreover, given that Xbench is not fully compatible with OmegaT, as I have noticed in this portfolio, I will come back to it and explore its potential with MemoQ and Trados later on, potentially as part of next year's portfolio.