• State Suggested Answer
  • Replies 23 replies
  • Answers 3 answers
  • Subscribers 353 subscribers
  • Views 21836 views
  • Users 0 members are here
Options

SDK and documentation for Trados 2007

Jesus Mañogil

Hi all,


I'd like to automate some tasks using the old Trados version, I mean 2007.

I've seen there are plenty of documentation from 2009 on, but I don't find anything related to the previous version and its SDK. Anybody with the same problem?


Thanks in advance.
Rate translation
×
Suggest better translation
×
Parents
  • 0

    You get Trados 2007 SDK documentation in the installer included, you just need to explicitly select it for installation, it's not installed by default.

    If you don't HAVE to, no need to upgrade at all.
  • 0 in reply to Evzen Polenka
    Thanks Evzen,
    The point is, our license doesn't include this documentation. I've tried to install it again and I don't see any option showing this Documentation. It's just a pity, I'd like to automate a couple of things and upgrading only because of that doesn't make sense at all.
    Anyhow, thanks again.
  • 0 in reply to Jesus Mañogil

    It's worth noting that the SDK documentation is not complete - the "Jobfiles.chm" file, describing structure of the job files used for Analyze, Translate and Cleanup actions is missing.
    You can get this file from "Trados 6.5 LSP" package, which is also downloadable from the FTP (it's in the root).

    EDIT: Actually, the jobfiles documentation is there, under Programming Guides... but references to the jobfiles from the Programming Reference (e.g. TW4Win.TranslationMemory.AnalyseFiles method) still link to the original external CHM file, i.e. are broken.

    As far as I can tell, no special license is necessary to USE the SDK... (at least not with 'higher' licenses than Freelance).
    That special developer license was necessary to GET ACCESS to the SDK back in the ancient days when it was not included in the installer.
  • 0 in reply to Evzen Polenka
    Thanks again,
    I've found that file.
  • 0 in reply to Jesus Mañogil
    Check out this page for a good head start on scripting for the SDK:
    http://www.openlingua.de/ol/software/tmexports.html
    It's a Word macro but you can also access the COM interface with PowerShell.
  • 0 in reply to jmyerscough
    I have been using the Trados 2007 API via COM interface with AutoHotkey for automating certain tasks and establishing connections between the Workbench and other tools; it is quite straight-forward.
  • 0 in reply to Raphaël Toussaint
    ...unlike that weird .NET sh*t needed for the new versions :(
    Someone at SDL should finally realize that not everybody on this planet is a developer with Visual Studio, but still would like to get some Trados Studio stuff automated.
    Duh, that is driving me so nuts, that I simply couldn't resist...
  • 0 in reply to Evzen Polenka

    Unknown said:
    Someone at SDL should finally realize that not everybody on this planet is a developer with Visual Studio, but still would like to get some Trados Studio stuff automated.

    Might be true, but I'm pretty sure the current situation is more powerful and more widely used already. You can always use Windows Powershell, this is pretty simple for automation.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    You can download a free version of Visual Studio, which is enough for most Trados related tasks.
  • 0 in reply to Paul

    Paul, the point is that
    1) The users I'm talking about do NOT need the power you guys are so excited about... they do NOT want customize/redesign the interface, nor they have ambitions to create plugins, etc... All they want is some EASY(!)-to-create automation of pretranslate, cleanup, etc.
    2) The power of the API has NOTHING to do with the way it's accessible (COM/.NET/etc.). Just look at the Microsoft Office - even the latest version can still be automated using simple JScript/VBScript file written in Notepad, using all of the latest features and API enhancements!

    Regarding PowerShell - have YOU personally tried to write some simple T2007 automation in VBScript and compare it with TS201x effort needed for the same automation using PowerShell?! I seriously doubt that, it looks rather like you just repeat someone else's (most probably a developer's) words.
    Have you tried to get the 'glorious' PowerShell Toolkit and actually _USE_ it with TS2014/2015 installed on Win7 or Win8? It's NOT possible 'out-of-the-box'! One gets some weird god-knows-what-it-means errors (and it's NOT about the paths, of course!) and it simply does not work.
    And then what? If you are not developer (and remember, we are talking about NON-developers!), you are screwed.

    So I strongly suggest everybody to get realistic and get out of their offices and talk to real common users...
  • 0 in reply to Remy Blaettler
    Looks like you did not get what I'm talking about.
    It's NOT about tools. It's about necessary additional knowledge and experience... and most importantly about the .NET chaos (versions, dependencies, references and god-knows-what-other-sh*t one needs to understand... ooops, additional necessary knowledge/experience!) to be able to cope with it.

    I can take my few-lines JavaScript file (written in Notepad) and use it to automate T2007 installed on _ANY_ system (WinXPSP3/Vista/7/8.x/10) without ANY pre-requisities and without checking if this-or-that version of this-or-that is installed or not.

    And what do I need to do the same with Studio and that 'glorious' PowerShell (Toolkit)?!
    How many things I need to check and/or install on each of these systems to make it work?
Reply
  • 0 in reply to Remy Blaettler
    Looks like you did not get what I'm talking about.
    It's NOT about tools. It's about necessary additional knowledge and experience... and most importantly about the .NET chaos (versions, dependencies, references and god-knows-what-other-sh*t one needs to understand... ooops, additional necessary knowledge/experience!) to be able to cope with it.

    I can take my few-lines JavaScript file (written in Notepad) and use it to automate T2007 installed on _ANY_ system (WinXPSP3/Vista/7/8.x/10) without ANY pre-requisities and without checking if this-or-that version of this-or-that is installed or not.

    And what do I need to do the same with Studio and that 'glorious' PowerShell (Toolkit)?!
    How many things I need to check and/or install on each of these systems to make it work?
Children