How to use Studio APIs from good old JScript / VBScript / etc.?

Hi,

sorry if this is a weird question, but I'm NOT a developer, I'm a batch scripting guy...

The old Trados 2007 SDK documentation was perfectly comprehensive and I used it for creating some nice automation scripts, e.g. in JScript

var wb = new ActiveXObject("TW4Win.Application");
wb.TranslationMemory.Open (tm, tmuserid);
wb.TranslationMemory.AnalyseFiles (jobfile);
wb.TranslationMemory.Close();
wb.Quit();

Now, how do I do such trivial thing with Studio 2014 API?

(yes, I know that jobfiles are not supported, that's not what I'm talking about... I'm talking about knowing clearly from the SDK documentation the name of the object to create, the methods and their parameters to use...)

All this Visual Studio stuff looks totally Chinese to me... classes, namespaces... OMG, where is the KISS principle gone? Or am I missing something?

I do NOT want to create EXEs... I NEED to create "open source" scripts, which any localization engineer in the company can simply modify according their needs and run immediately, without compiling anything and similar stuff...

Oh, and no PowerShell either...

Parents
  • Hi Evzen,

    What you are asking for is not available.

    Your example is using COM underneath and Trados does not have a COM interface. (although it has been requested before to SDL)

    You could check out the powershell toolkit if you have a professional license, but you already stated "and no Powershell" (which I don't understand)

    https://github.com/sdl/Sdl-studio-powershell-toolkit

    Powershell is becoming the standard scripting/shell environment on Windows. VBScript and JScript are now legacy so I recommend switching.

Reply
  • Hi Evzen,

    What you are asking for is not available.

    Your example is using COM underneath and Trados does not have a COM interface. (although it has been requested before to SDL)

    You could check out the powershell toolkit if you have a professional license, but you already stated "and no Powershell" (which I don't understand)

    https://github.com/sdl/Sdl-studio-powershell-toolkit

    Powershell is becoming the standard scripting/shell environment on Windows. VBScript and JScript are now legacy so I recommend switching.

Children
No Data