After trying out both Studio and DVX, I have now decided about which tool to choose: It will be Studio.
And I will now also sign a maintenance contract for Studio; it will probably not be able to run without constant support. I will also take a webinar for Studio upgraders on 8 January, and take the certification exam.
The main reasons for my choice:
Studio +:
+ Handling of "rouge codes" does not cause any extra work
+ AutoSuggest, that is so superior to DVX AutoAssemble
+ SDL Automatic Translation Server, which actually boost productivity
+ Dual editor has a better user interface
+ TW_users list is a good free source for support
Studio -:
- Multiple translations problem
- Instability and error messages
- Bad concordance search compared with Workbench
- Numbers and codes "localization" cannot be turned off
DVX +:
+ Intuitive and fast on the fly editing in all databases
+ The AutoAssemble and Lexicon function is very good in some cases
DVX -:
- Multiple translations problem
- Tags handling can become overwhelming in some Word documents
- Déjà vu users lists is only for DVX fanatics
It is difficult to compare the two systems function by function, as they are working so differently. Actually, you could have use of both AutoSuggest/AutoAssemble in the same system, and that also goes for the AutoSuggest dictionary/Lexicon as they could complement each other.
Subscribe to:
Post Comments (Atom)
Based on my own (limited) experience with Trados, I can confirm that the "TW_users list is a good free source for support".
ReplyDeleteHowever, based on my extensive experience with Déjà vu and its user group, I certainly can't confirm the statement "Déjà vu users lists is only for DVX fanatics".
Anyone who is prepared to spend a little time looking at the message archive at http://groups.yahoo.com/group/dejavu-l/ (no subscription necessary) will surely be able to establish quite quickly that the statement could be described as somewhat subjective, to put it mildly.
More generally, it is interesting to note that the blog author bought a Déjà Vu licence back in 2001" but in all these years appears to have been unable to discover and utilise the power of what is affectionately known as the Ferrari among CAT tools in Déjà Vu circles.
The "multiple translation problem" is (more precisely) the capacity to store more than one translation for a single segment and allow the user to choose which one to use. This is essential for those languages where there isn't a one-to-one correspondence (for instance, the English "light" has a number of translations in Italian, and this very morning I had to translate the segment "display lights" in two different ways in a single document.
ReplyDeleteBelow is a link to some comments by an SDL representative about "multiple translations" which incidentally imply that this capacity exists also in Studio and is not a problem, but a useful linguistic function.
Trados List Post
Lorenzo
Italian Translator
www.italianwords.it
Does "Numbers and codes "localization" cannot be turned off" (Trados) mean that DVX, by implication, enables using a TM for translating from/into a language different from that stated in the TM. To give an example, as I translate from German into Russian (DE-DE to RU-RU), I would like to also use an English to Russian TM (EN-US ti RU-RU) for reference. In Trados, I used to replace the EN-US tags with DE-DE tags after I have exported the memory. Your comparison implies that I could use an "alien" memory with DVX? Or did I get it wrong?
ReplyDeleteThanks.
Valerij Tomarenko
Translator and interpreter for Russian - English - German
www.tomarenko.de