Long time ago, Hans Lenting wrote:
When using CafeTran Espresso 2018 as an interesting alternative for SDL Studio 2017, there are occasions where one has to deal with the feature
Tracked Changes of Studio.
The first occasion is where the translator opens a Studio package in CafeTran Espresso 2018 and inserts tracked changes while reviewing her own or someone else's translation. Personally, I don't think that this scenario will be used very frequently.
The second scenario is more likely to happen: a translator creates a translation of a Studio package in CafeTran Espresso and sends the translated package to his client for review. A reviewer adds tracked changes in Studio and returns the reviewed package. The translator will have to process these tracked changes in CafeTran Espresso.
In order to use this second scenario, CafeTran Espresso will need the following enhancements:
- Filter on segments that contain tracked changes
- Accept or ignore individual tracked changes
- Accept or ignore all tracked changes at once
Note that I'm not requesting a feature to create Studio-compatible tracked changes in CafeTran Espresso 2018.
Hello Igor,
I read this enthusiastic reaction of a translator who upgraded from Studio to CafeTran Espresso (https://www.proz.com/forum/sdl_trados_support/350267-will_rws_destroy_trados-page2.html ):
Since then, I've noticed that many of translators have already decided to get rid of it once and for all, in order to switch to another real effective CAT tool, for example CafeTran Expresso, which is the current successful rising state-of-the-art technology in matter of real CAT tools (but not the only one though).
I did the same and I've ultimately adopted CafeTran Expresso as my favorite CAT tool for a few weeks. Not only I do warmly recommand this tool, but I must say I don't regret the gain of time and the really outstanding accurate outcome of this CAT tool.
As a long-time user of CafeTran Espresso I only miss one feature of Studio: Tracking changes.
Is there any chance that CafeTran Espresso will learn how to deal with Studio's Tracked changes, just like it learned to deal with its TMs and termbases?