Hi Romulus,

my offline documentation says pretty clearly this:

And that's actually the ONLY thing which makes sense - that if I select the "Trados" profile during the first run after installation, this (and only this) template will be used as default... just as Studio does "at the UI level".
Any other behavior does not make any sense since it would be inconsistent with the "UI level behavior" and different than documented.

Hello,

I just wanted to try this toolkit on my pc but I could not do it right. I get below error.

Can you tell me what is wrong?

As Jesse says, the toolkit was created for older Studio version which uses only 4 parameters for creation of filebased TM.

I changed my toolkit modules to accept $StudioVersion as parameter (which is simply the variable part of Studio program files path)

param([String]$StudioVersion = "Studio4")

if ("${Env:ProgramFiles(x86)}")
{
    $ProgramFilesDir = "${Env:ProgramFiles(x86)}"
}
else
{
    $ProgramFilesDir = "${Env:ProgramFiles}"
}

Add-Type -Path "$ProgramFilesDir\SDL\SDL Trados Studio\$StudioVersion\Sdl.LanguagePlatform.TranslationMemoryApi.dll"
Add-Type -Path "$ProgramFilesDir\SDL\SDL Trados Studio\$StudioVersion\Sdl.LanguagePlatform.TranslationMemory.dll"

and then use it to differentiate the TM creation calls

    if ($StudioVersion -le "Studio3")
    {
        $TM = New-Object Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemory ($TMPath, $Description, $TMSourceLanguage, $TMTargetLanguage, $FuzzyIndexes, $Recognizers)
    }
    else
    {
        $TM = New-Object Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemory ($TMPath, $Description, $TMSourceLanguage, $TMTargetLanguage, $FuzzyIndexes, $Recognizers, $TokenizerFlags, $WordCountFlags)
    }

In other words, newer Studio versions need 6 parameters when creating filebased TM (that's why the error message states the number 6 ;-) ).

I may eventually publish my heavily changed toolkit on GitHub, but it's still lacking some TM-related updates... and I don't have much time to finish that :-\.

Oh, but the second error may be a showstopper - you need Professional license in order to be able to use the Project Automation API.

So if you don't have that, don't even bother digging deeper into PowerShell Toolkit...

Hi,

Just an update to let you know that there is an updated version of the PowerShell Toolkit here:

No major changes, but support for Studio4/5 and couple of things here and there:

• The paths to the .dll files are now identified regardless of the operating system(32-bit of 64-bit)
• The user can select which version of Studio is in use (Studio4 or Studio5)
• The script now creates in "SampleRoundtrip.ps1" a sample text file with custom content
• The "Get-Project" function only requires as parameter the path to the .sdlproj file
• The "New-Project" function automatically creates the source file directory
• Updated the "New-FileBasedTM" function from TMHelper module to use the new implemention from Studio
• Updated the "New-Project" function from "SampleRoundtrip.ps1” to use the new implementation from Studio

Thanks to  for updating it and to Evzen Polenka for his advice during the process.  I know this doesn't solve all the problems raised as some of the things require changes in Studio but this is an improvement which I hope will be useful.

Regards

Paul

To give back something to the community, here is my modification of the Powershell Toolkit.
I dare to say that after all the modifications and enhancements it has hardly something to do with the original toolkit anymore...

https://github.com/EvzenP/STraSAK/

I have also a GUI launcher created as Powershell script, but since it's somehow contradicting the main purpose of scriptable automation (i.e. avoiding clicking in GUI), I'm probably not going to release it anyway ;-)

The point is that the "consumers" don't need to know anything about Powershell.
It's just that the scripts are written in Powershell... but that doesn't say anything about the environment they can be used in!

I really don't understand where this weird asumption comes from... it's like if people would assume that they need to know C# if they want to use Trados Studio or Microsoft Office... :-\