I’ve run a test on a short MS Word file I created from a Wikipedia article (I have it available, if anybody wants to repeat my test):Īs you can see, a translator who used to be paid based on a Trados 2007 word count would concede to the translation agency a 5.1% discount just by using 2014 SP2 instead. But why should translators consider this as an improvement? I can see why certain translation agencies would consider this as an “improved” algorithm, and welcome such a misfeature (just another way to pay those pesky translators less). This means that Studio counts elements like “it’s” or “splash-proof” as one single word. Studio no longer treats apostrophes and dashes as word separators, but as punctuation marks that link words together. Studio 2014 SP2 uses an improved algorithm for processing words that contain dashes (-) or apostrophes (‘).
Improved word count and search logic for words containing apostrophes and dashes If you read through the release notes of SP2, however, in addition to various improvements, there is also a major new issue:ġ1. So, thank you to SDL for finally fixing the Java problem.
#Que es xbench upgrade#
This upgrade no longer relies on Java, and should therefore fix all Java-related issues that have plagued the use of MultiTerm in Studio.
0 kommentar(er)
