Before I come to tell you my – very personal – opinion about this tool, I tell you its story, how I got to it.
One of my friends and colleagues posted about this tool on facebook, so I downloaded it, without thinking that I will ever need a tool like this.
After the download it, I installed it and when I opened it, there was a very unfriendly window wanting a licence key.
Nothing else opened, just this text bar….well…ok, I went to their website and learned that you can apply for a trial licence key by compiling their form.
It is just the same QA check, what you can find built-in in the CAT tools. So, there is a very good chance, that if you are a professional translator, you are using at least one CAT tool. If you do, you have your Verifika-like checks inside, already compatible with all the formats, which your CAT-tool produces, and you don’t need this tool.
Anyhow, since another friend of mine chased me to start blogging about all the tools, I am using, I thought, it is good to keep myself updated.
What is Verifika?
Verifika is an external tool, with which can cross-check your translations’ spelling, consistency and terminology.
Why is it useful to use any tool like this?
Well, you all know, that it is not only important, what you say, but also, how you say it. Translating is not only about choosing the right words, but also presenting your translation in a form, so that the agency/client will be satisfied.
And then, one day – like in a story – an agency has sent me a translation package, in which translation memory and term-base should have been included.
Unfortunately the term-base was only visible, but the QA check didn’t “see” it somehow…(yes, there should be another question mark here, why did this happened. Well, since I don’t pay for the costly support of SDL, which usually just comes back with the “solution” of “works-for-me”, “update-upgrade”, “buy another computer”, I rest in the position of just telling you, that there can be a situation, where an external tool is more than useful).
Well, since you can’t deliver a project without checking the terminology consistency, I thought, I will give a try to Verifika.
Verifika is very easy to use, if you are handy with how to use a software (you know, what you can usually find under the menu-point “File” and know, that to use an external file, you have to search for an “Upload“, “Import” or “Add” button somewhere, etc.)
Verifika also handles multiple formats, like in my case .sdlxliff format, which I just selected from the folder, where SDL put it.
You can add multiple files, so you can keep your terminology consistent over a long period in different projects, packages, even with different CAT tools, which is very important in our era, where all the companies want to have their legacy formats (drives me crazy).
After you upload the translation, you can add the terminology to it.
I needed some conversion here.
Verifika only accepts the tab-delimited and .xls/.xlsx formats. Well, I had to export it from Multiterm and save it in a two-column xls file, since Verifika only gets the first two columns of a sheet. (Another downside for a translator, who is not working easily with computer programs, but maybe translators, who are still working with Microsoft word and keep their terminology consistent with help of an Excel file, can benefit from this tool very well).
After I set up my first Verifika project, it was sooo fast and so easy to do the terminology check, that I really started to think about even to buy it!
After you click on the “check button”, there is a list appearing with different columns, where you see the term, its translation and its occurances in the text, where Verifika didn’t find the desired translation.
I performed a check on a 17000 word heavy translation with a term-base containing over 1000 terms in about an hour (the translation was made without using the term-base, there was plenty to do on it, but still.)
I have to say, even I told you about the built-in tools and how useless this another tool is for CAT-tool owners…I feel tempted to buy it…