the main one is that it won't be updated, so if (for example) SDL in the future makes a change to the sdxliff format that makes it no longer compatible with Xbench, you'll be out of luck. There are some other limitations in the "free forever" version. 3, so it is not available in the free version. 2.9 for the QA of Studio files, but not, (for example), of memoQ files: that capability was added after the release of v. That's not exactly right: Version 3 (the commercial version) is free for a trial period, then you have to pay, or it stops working - but version 2.9 is free forever. You can use it for free for a while, but then you are asked to pay. You can find a thorough presentation of what Xbench can do for translation QA and terminology management in this presentation of mine: Xbench for Terminology Management and Translation QA ▲ Collapse ![]() I highly recommend it (and not only the free version, which is starting to be a bit outdated: the paid version as well). Xbench is a terrific program, it includes excellent documentation (via the help file), and, if you devote to it the time necessary to learn to use it well, can be very useful for your projects. Just like any other useful non-trivial piece of software, you have to devote the time necessary to learn it. Is it as simple to learn as my client says it is? No, there is a learning curve.two consecutive same words, like the two to's I've just used, inconsistencies in source or target, etc.): it also includes a more practical spell-checker, and can be expanded (via personal checklists) to catch the kind of errors you know you might be particularly prone to. Xbench not only helps to catch the type of errors that is difficult for a human being to to detect (e.g. ![]() Would you recommend it to improve quality of your work? Yes, absolutely.Do you use it with every project? Almost every project: the sole exception are a few small "one-off" projects.Do you like it? Yes, very much: it's wonderful tool, not only for QA, but also for terminology and translation memory management. ![]() I own a licence for Xbench, but have never really warmed to its QA functions. Also, if they are one of those clients that insist I work with SDL Studio projects, even though I have asked them politely and insistently if I can use my own CAT tool, I let them handle all the QA stuff in Studio. I currently us the various QA features in Déjà Vu X3. Having said that, the more my client pays me, the more time and effort I can expend on QA stuff. The party line: Yes, it's great, and I use it, and all manner of other QA tools on my transaltiomn work after finishing it.Ī perhaps more realistic version: I usually don't have much time for that kind of thing once I'm finished, and I am actually quite slow and methodical in my work anyway, so hope for the best I am referring specifically to the free version.ĭo you like it? Do you use it with every project? Would you recommend it to improve quality of your work? Is it as simple to learn as my clients says it is? Now, I generally feel I have had enough of new softwares to get to know and use, so I would like your input, please, if you use Xbench as a quality assurance tool. A client has asked me to get and use Xbench for QA of files translated in Trados Studio.
0 Comments
Leave a Reply. |