| SDL misrepresents data safety of Trados database | Aug 12, 2007 |
SDL Professional Services. SDL Access Customer Portal. Partner Groups. SDL Community Internal Group. Language Products - GCS Internal Community. Customer Enablement Leadership Team. Web Upgrade Program. Roadshow Workshop. Windows 10 and Trados 2007. SDL Trados Studio 2019 is built on the same open platform as SDL Trados Studio 2017 and uses the same bilingual file, translation memory and termbase formats. SDL Trados Studio 2017 Freelance/Professional Single license owners only. Only through SDLX provided as part of SDL Trados 2007 Suite: No, only through SDL Trados 2007 Suite.
David Turner wrote:
Sounds like a good point to switch to another CAT program...
Sounds like a good point to switch to another CAT program...
Yes it is, except that I would like to be sure that the 'other CAT program' is more reliable when it comes to the integrity and repairability of my databases.
I hold Trados/SDL responsible for selling me a product that has not implemented basis safety provisions against data loss AND is irrepairable, at the same time fraudulently misrepresenting the product as completely safe ('Never translate the same sentence again').Sdl Trados 2007 Suite Professional Property Management
Could anyone tell me from when on Trados TM's could not be edited in a simple editor anymore? Was it Trados 6 that had that change of file format?
By the way, this is the last segment in the exported TM after which Workbench gets stuck:
'
Office 2007 Suite Download
18022007, 08:50:26WIN2000
27052007, 20:34:24
MARINUS
0
{nosupersub m}{super 2}
{nosupersub m}{super 2}
'
I suppose that it's the next segment, the one that does not show in the exported TM, that is the real culprit.
Thanks for your help thus far.
- Marinus
[Bearbeitet am 2007-08-12 04:41]