Studio Developers Q&A - Recent Threads

RE: How to create multiple translation projects based on Trados APIs by using many licenses at the same time to release concurrent cases

Daniel Brockmann — Mon, 04 May 2026 14:41:34 GMT

Hi Flavio - just chiming in here - for such scenarios it is indeed definitely interesting to look at the Trados Cloud platform rather than desktop. Desktop scenarios are by nature limited as Patrick explained, so for this kind of work you would need to implement your own queueing mechanism or similar to not overload the desktop tool with too many parallel project batch preparation processes or uncontrollable license checkouts. More info on the cloud API is available from Trados Cloud Platform API. Thanks, Daniel

How to create multiple translation projects based on Trados APIs by using many licenses at the same time to release concurrent cases

Flavio Sun — Mon, 27 Apr 2026 07:20:37 GMT

Hi,

I am a Trados user for SDL Trados 2019 and 2024 with licenses. I am writing automation exe based on Trados SDK API to make project automated.

When running the project, I find that in same time only one Trados License can be activated and only one Instance is running, for example, If two users want to create two translation projects at the same time, only one user can launch the Trados API-based exe, and the other user must be waiting for the license released.

So I WANT TO KNOW, How can I realize the cocurrent use? For example, I have 4 licenses, and It is possible for us to run 4 projects at the same time by calling the APIs.

Thansks,

Flavio

RE: How to create multiple translation projects based on Trados APIs by using many licenses at the same time to release concurrent cases

Flavio Sun — Thu, 30 Apr 2026 10:26:59 GMT

Hi Patrick Andrew Hartnett ,

Thanks for your answer. I want to know, if I want to do concurrent project to call many licenses at the same time, what would suggest, purchasing another type of license? or use Web application version?

RE: How to create multiple translation projects based on Trados APIs by using many licenses at the same time to release concurrent cases

Patrick Andrew Hartnett — Thu, 30 Apr 2026 09:58:32 GMT

Hi Flavio Sun ,

Trados Studio is fundamentally a desktop application, and the Studio APIs are intended for desktop automation scenarios, not for building a scalable server-style processing solution. The Project Automation API documentation also notes that FileBasedProject is not thread-safe and recommends using separate processes, not multiple threads, if you want to create projects simultaneously.

So, while you may be able to run more than one automation process, running multiple Studio/API-based processes simultaneously on the same machine is not a scalable design pattern and may lead to issues, especially around license allocation/release. For standalone applications that use licensed Project Automation APIs, you must call LicenseManager.ReleaseLicense() when the process exits; otherwise the license can remain blocked for some time after execution ends.

In short: Studio should be treated as a desktop solution for individual users, not as a multi-user automation server.

RE: Batch task plugin logs

Balázs Fehér — Thu, 30 Apr 2026 04:46:58 GMT

Many thanks!

Batch task plugin logs

Balázs Fehér — Fri, 24 Apr 2026 13:06:58 GMT

Hi All,

I am implementing a batch task plugin and during batch task execution multiple error, warning or info event can happen. Errors of course block the execution, but warnings can be ignored, info item are just for informing the user know what happened. I am looking for the best way to display these events/messages for the user. Based on the UI there should definitely exists a possibility to do such thing (see image below). For errors I just need to throw an exception, but I do not see how can I add a warning. So my question is that, how can I add a "Warning" in a "AbstractFileContentProcessingAutomaticTask" specifically? And is there a way to add info messages?
Thank you in advance for your reply,
Balazs

Error when setting value in import task settings

Bram van der Steen — Fri, 31 Oct 2025 16:43:38 GMT

Good day,

In our plugin with Studio 2024, we are trying to run the automatic task “UpdateFromExternalReview” via the Studio API. However, when preparing the task settings, we receive an error. See the following code snippet:

ISettingsBundle settings = project.GetSettings();
Sdl.ProjectApi.Settings.ImportFromReviewTaskSettings importTaskSettings = settings.GetSettingsGroup<Sdl.ProjectApi.Settings.ImportFromReviewTaskSettings>();
importTaskSettings.ExternalReviewMappingItems.Value = reviewedItems;

When setting this value, we receive the following error:

No set method for property 'IsoAbbreviation' in type 'Sdl.Core.Globalization.LanguageBase'. ---> System.Runtime.Serialization.InvalidDataContractException: No set method for property 'IsoAbbreviation' in type 'Sdl.Core.Globalization.LanguageBase'.
at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.ThrowInvalidDataContractException(String message, Type type)
at WriteLanguageToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.WriteDataContractValue(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithoutXsiType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
at WriteExternalReviewMappingItemToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.WriteDataContractValue(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithoutXsiType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
at WriteArrayOfExternalReviewMappingItemToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.WriteDataContractValue(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithoutXsiType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.DataContractSerializer.WriteObject(XmlWriter writer, Object graph)

This error is mysterious to us, as there's no obvious connection to what we're trying to do.

The error occurred both in versions 18.0.1.2259 and 18.1.2.6370.

Any help would be greatly appreciated.

Best regards,
Bram van der Steen

RE: Error when setting value in import task settings

Bram van der Steen — Tue, 28 Apr 2026 08:32:19 GMT

Hi Patrick Andrew Hartnett , we've verified that this does indeed solve our problem. Thank you very much for your assistance.

RE: Batch task plugin logs

Emanuel Albu — Mon, 27 Apr 2026 07:44:43 GMT

Balázs Fehér

Hello!

You can achieve this by using the bilingual processor added to the multiFileConverter. It provides a `ReportMessage` method that fits your needs exactly.

Example

public class MyProcessor : AbstractBilingualContentProcessor
{
    public override void ProcessParagraphUnit(IParagraphUnit paragraphUnit)
    {
        if (paragraphUnit.IsStructure)
            return;
        foreach (var _ in paragraphUnit.SegmentPairs)
        {
            ReportMessage("source", "origin", ErrorLevel.Warning, "message", "location");
        }
    }
}

RE: MultiTerm COM API Termbases.New() fails when Croatian is present in XDT, but MultiTerm Desktop can create the termbase

Patrick Andrew Hartnett — Thu, 23 Apr 2026 07:52:46 GMT

Hi Adam Csillag , I'll follow up with the team this morning and see if this is a known issue and if/any workarounds; I'll circle back once I have more info.

MultiTerm COM API Termbases.New() fails when Croatian is present in XDT, but MultiTerm Desktop can create the termbase

Adam Csillag — Fri, 10 Apr 2026 11:16:49 GMT

Hello,

I’m seeing a reproducible issue with MultiTerm COM automation when creating a local termbase from an .xdt definition.

Environment

MultiTerm Desktop 2022 SR2 - 17.2.5.2838
Trados Studio 2022 SR2 - 17.2.12.19268
C# app running as x86 (Environment.Is64BitProcess = False)
Interop: Sdl.MultiTerm.TMO.Interop

Code

Sdl.MultiTerm.TMO.Interop.Application oMt = new Sdl.MultiTerm.TMO.Interop.Application();
TermbaseRepository oLocalRep = oMt.LocalRepository;
oLocalRep.Connect("", "");

Termbases oTbs = oLocalRep.Termbases;
oTbs.New(name, "", definition, sdltbPath);

Example values used

name = "Test"
definition = C:\Users\...\Temp\Test_20260409_141955534\Test.xdt
sdltbPath = C:\Users\...\Temp\Test_20260409_141955534\Test.sdltb

What I tested

The process is 32-bit (Environment.Is64BitProcess = False)
definition exists
sdltbPath does not exist before calling New(...)
Creating in %TEMP% gives the same result as other local paths
Opening an existing .sdltb through COM works:

oLocalRep.Termbases.Add(existingTbPath, "", "");
var tb = oLocalRep.Termbases[existingTbPath];

MultiTerm Desktop can successfully create the termbase from the same .xdt

Observed behavior

Termbases.New(...) throws:
- System.Runtime.InteropServices.COMException: 'MultiTerm is unable to create the termbase.'
After a lot of testing, I found that the problem is related to Croatian in the .xdt
If I remove Croatian from the termbase definition, Termbases.New(...) succeeds
If Croatian is present, Termbases.New(...) fails
However, MultiTerm Desktop is able to create the same termbase from the same .xdt

Question

Is this a known issue in the MultiTerm COM API with Croatian language handling during termbase creation?
Is there a specific Croatian language code/locale that COM expects here?
Could this be related to SH-HR vs hr-HR handling?

Since Desktop can create the termbase, but COM cannot when Croatian is included, this looks like an API-specific issue rather than a broken .xdt.

Thanks in advance for any guidance.

Verification plugin triggered when confirming a segment even if disabled

Arturo Vazquez Rodriguez — Fri, 17 Apr 2026 09:07:28 GMT

Hello,

I have developed a custom verification plugin for Trados Studio.

When I disable it in the project settings, it won't be triggered when pressing F8, which is expected and completely normal.

The problem is that confirming a segment triggers the verifications performed by that plugin even if the plugin is completely disabled (that is, unchecked in the Verification options node).

I am using Trados Studio 2024 SR1 18.1.3.6657

I cannot share the source code publicly or the plugin, but I can privately, please get in touch with me for that.

Thanks!

Kind regards,

Arturo

RE: Verification plugin triggered when confirming a segment even if disabled

Patrick Andrew Hartnett — Mon, 20 Apr 2026 09:17:17 GMT

hey Arturo Vazquez Rodriguez awesome work finding this workaround; will be useful also to others blocked with this.

RE: Verification plugin triggered when confirming a segment even if disabled

Arturo Vazquez Rodriguez — Mon, 20 Apr 2026 09:02:11 GMT

I found an alternative to this that works in my case:

string isEnabled = _projectsController.CurrentProject.GetSettings().GetSettingsGroup("Plugin_ID").GetSetting<string>("Enabled").Value;

Here I have an Enabled status that is updated and seems to reflect the current activation status of the Verification plugin in the options node. It seems to be working as expected. If you don't have a better alternative, I think I will be using this one. Thanks!!

RE: Verification plugin triggered when confirming a segment even if disabled

Arturo Vazquez Rodriguez — Mon, 20 Apr 2026 08:33:51 GMT

Hi Patrick,

Thanks for your reply!

I think you pointed me at Translation Providers rather than Verificators, so I changed this line:

GetExtensionPoint<GlobalVerifierAttribute>()

However, the Enabled property is always set to true even if the plugin is disabled in the Verification options node, so this solution does not seem to change the behavior.

RE: Verification plugin triggered when confirming a segment even if disabled

Patrick Andrew Hartnett — Sat, 18 Apr 2026 08:33:04 GMT

Hey Arturo Vazquez Rodriguez , This is a know bug and at the moment your only option is to implement your own mechanism to check if the project is disabled.

Here is an example of how you could accomplish this, let me know how it goes.

var extensionPoint = PluginManager.DefaultPluginRegistry.GetExtensionPoint<TranslationProviderFactoryAttribute>();
if (extensionPoint == null)
{
	return;
}
foreach (var extension in extensionPoint.Extensions)
{
	// 1. identify if the extension is a provider of interest to you
	// from here you can identify the type
	// extension.ExtensionType == etc..
	// extension.Plugin.Id == etc...
	
	// 2. identify if the provider is enabled; this should already solve yr problem
	if (extension.Enabled)
	{
	   // do something
	}
}

RE: Verification plugin triggered when confirming a segment even if disabled

Arturo Vazquez Rodriguez — Fri, 17 Apr 2026 11:27:00 GMT

Just adding here that disabling individual checks in my verification plugin works as intended: confirming a segment does not trigger the check if the individual check is disabled. Therefore, it seems that Trados is ignoring the status of the plugin enablement at the top level and only looking at the enablement status of individual options. Is there a solution for this I can put in place on my end?

RE: Error when setting value in import task settings

Patrick Andrew Hartnett — Tue, 14 Apr 2026 10:32:42 GMT

Hi Bram van der Steen , thank you for providing the source code. The team have reviewed this; here is the response:

This reproduces in Trados 2024 and 2022.

For comparison, I ran the task in Trados (Update from Bilingual Review) and compared the items added in the settings with what the user is trying to add programmatically. The item added by Trados has its Language property set to null, while the user is attempting to set it. If the code is changed so that the Language property is not set, the error no longer occurs.

RE: TerminologyProvider does not reliably generate scores for Fuzzy Search

Lukas Ley — Mon, 13 Apr 2026 09:45:13 GMT

Hi Patrick Andrew Hartnett ,

I wanted to check in and ask if you can give me any information about further developments on this.

Best, Lukas

TerminologyProvider does not reliably generate scores for Fuzzy Search

Lukas Ley — Mon, 01 Sep 2025 09:42:43 GMT

Hello,

I am using Trados Studio 2024 (not SR1) and I have another question.

After getting the search with the TerminologyProviderManager Singleton to work (see the answers in this question) I noticed some strange behavior.
My goal is to get the scores for terms like they are displayed in the "Term Recognition" view in the Editor UI. Ideally I want to put the whole segment string in and get the scores.

When I search via ITerminologyProivder.Search() the scores never line up. Even if I put in only a single term it only lines up when there is a 100% match.

When I put in a longer sentence the score for the best fitting term decreases with the length of the sentence.

For example see this code from the other question:

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:ea15cfd2-4189-424b-8b29-84d13a5bc4d9:type=csharp&text=var%20sourceLanguage%20%3D%20new%20CultureInfo%28%22en-US%22%29%3B%0Avar%20targetLanguage%20%3D%20new%20CultureInfo%28%22de-DE%22%29%3B%0Astring%20segmentText%20%3D%20%22...%22%3B%0Aint%20maxResultsCount%20%3D%2010%3B%0Abool%20targetRequired%20%3D%20true%3B%0A%0Avar%20searchResults%20%3D%20terminologyProvider.Search%28%0A%20%20%20%20segmentText%2C%0A%20%20%20%20sourceLanguage%2C%0A%20%20%20%20targetLanguage%2C%0A%20%20%20%20maxResultsCount%2C%0A%20%20%20%20SearchMode.Fuzzy%2C%0A%20%20%20%20targetRequired%0A%29%3B]

If I have a Termbase with the word "Gefahrstoff" in it and when I set the segmentText to "Gefahrstoff" the top searchResult has a score of 100.

If i set the segmentText to "Gefahrstoffen" it has a score of 90. In the Term Recognition view in the Editor UI, "Gefahrstoff" has a Score of 87. The sentence in the Editor is "Die Nutzung von Gefahrstoffen ist gefährlich".
When I set the segmentText to "Die Nutzung von Gefahrstoffen ist gefährlich" the term "Gefahrstoff" has only a score of 63.

Do i really need to parse the thext and search for each token? I would like to avoid doing that. And even if i did that the scores do not line up.

Is there any method for getting the same scores?

Best,
Lukas

API calls to pretranslate files using DeepL plugin no longer work

TTS Team — Wed, 01 Apr 2026 14:25:52 GMT

Hello,

Since DeepL changed their authentication methods, we no longer can pretranslate our files using API calls to Trados 2024. It still work when pretranslating "manually" from within Trados Studio, but when using the API call

project.RunAutomaticTask(targetFiles.GetIds(), AutomaticTaskTemplateIds.PreTranslateFiles)

, it won't work.

We've narrowed it down to DeepL API key authentication: when adding the DeepL provider manually in Trados Studio, the API key is automatically authenticated when you enter it in the settings dialog for DeepL, but when our external tool uses Trados API to add the DeepL provider to the project using our API key, no such validation occurs, and that's what blocks the pretranslation task from working.

So my question is: is there any way to make it work, it worked just fine before the authentication change? We even tried duplicating the API key authentication when adding the provider to the project, but no luck there.

Thanks for any help on this subject.

RE: API calls to pretranslate files using DeepL plugin no longer work

TTS Team — Thu, 09 Apr 2026 11:09:06 GMT

Thanks again Emanuel Albu , I adapted your code to mine, removing all the complexities we had added to mimic what Trados adds in the provider, and let it do its job, and it worked just fine! That's all there was to it.

RE: API calls to pretranslate files using DeepL plugin no longer work

Patrick Andrew Hartnett — Thu, 09 Apr 2026 09:51:08 GMT

Hey TTS Team , not sure if it helps, but also check and update the App.Config file. we identified some dependencies changed with the latest update a few months ago...
please check here:
RE: Create Project Via API shows files as Reference

RE: API calls to pretranslate files using DeepL plugin no longer work

TTS Team — Thu, 09 Apr 2026 09:46:43 GMT

Hello Emanuel Albu ,

Thanks for the sample code. Ours is very similar (I'm going to try to put it in as much context as possible, while omitting the irrelevant parts).

        public DeepLPluginOptions()
        {
            _uriBuilder = new TranslationProviderUriBuilder("deepltranslationprovider");
        }
        protected TranslationProviderUriBuilder UriBuilderDL => _uriBuilder;

        public void AddDeepLPluginToProject(FileBasedProject project, string apikey, Language locale,
            string settingsName = null, bool cutTag = false)
        {
            var uri = GetUri(apikey, settingsName, cutTag);
            //Console.WriteLine("Saving plugin settings for DeepL/Intento: {0}", uri);
            SaveDeepLPluginSettings(uri, project, locale, apikey);
        }
        
        Uri GetUri(string apikey, string providerId, string providerName, string customAuth = null,
            string customModel = null,
            string glossary = null, string settingsName = null, bool cutTag = false, bool smartRouting = false)
        {
            return UriBuilderDL.Uri;
        }

        public void SaveDeepLPluginSettings(Uri uri, FileBasedProject prj, Language locale, string ApiKey)
        {
            TranslationProviderConfiguration pluginSettings = prj.GetTranslationProviderConfiguration(locale);

            Console.WriteLine("Preparing the JSON string for DeepL MT provider");
            Uri DeepLUri = new Uri("deepltranslationprovider://");
            string state = GetStateObject(uri, prj, locale);
            Console.WriteLine("Creating Trados provider using DeepL settings");
            TranslationProviderReference reference = new TranslationProviderReference(uri, state, true);
            TranslationProviderCascadeEntry entry = new TranslationProviderCascadeEntry(reference, false, true, true, 0);
            pluginSettings.Entries.Add(entry);

            prj = PreTranslationSettings.SetMinimumMatchValue(prj, locale);
            prj.Credentials.AddCredential(DeepLUri, ApiKey);

            prj.UpdateTranslationProviderConfiguration(locale, pluginSettings);
 
            prj.Save();
        }
        
        string GetStateObject(Uri uri, FileBasedProject prj, Language locale)
        {
            System.IO.TextWriter tw = new System.IO.StringWriter();
            JsonTextWriter stateWriter = new JsonTextWriter(tw);
            stateWriter.WriteStartObject();
                stateWriter.WritePropertyName("ApiVersion");
                stateWriter.WriteValue("V2 (DeepL Pro API subscription)");
                stateWriter.WritePropertyName("IgnoreTagsParameter");
                stateWriter.WriteNull();
                stateWriter.WritePropertyName("LanguagePairOptions");
                stateWriter.WriteStartArray();
                    stateWriter.WriteStartObject();
                        stateWriter.WritePropertyName("Formality");
                        stateWriter.WriteValue(0);
                        stateWriter.WritePropertyName("SelectedGlossary");
                        stateWriter.WriteStartObject();
                            stateWriter.WritePropertyName("glossary_id");
                            stateWriter.WriteNull();
                            stateWriter.WritePropertyName("IsChecked");
                            stateWriter.WriteValue(false);
                            stateWriter.WritePropertyName("Name");
                            stateWriter.WriteValue("No glossary");
                            stateWriter.WritePropertyName("source_lang");
                            stateWriter.WriteNull();
                            stateWriter.WritePropertyName("target_lang");
                            stateWriter.WriteNull();
                        stateWriter.WriteEndObject();
                        stateWriter.WritePropertyName("LanguagePair");
                        stateWriter.WriteStartObject();
                            stateWriter.WritePropertyName("SourceCultureName");
                            Sdl.ProjectAutomation.Core.ProjectInfo prjSettings = prj.GetProjectInfo();
                            string SrcLang = prjSettings.SourceLanguage.CultureInfo.Name;
                            string TgtLang = locale.CultureInfo.Name;
                            stateWriter.WriteValue(SrcLang);
                            stateWriter.WritePropertyName("TargetCultureName");
                            stateWriter.WriteValue(TgtLang);
                        stateWriter.WriteEndObject();
                    stateWriter.WriteEndObject();
                stateWriter.WriteEndArray();
                stateWriter.WritePropertyName("LanguagesSupported");
                stateWriter.WriteStartObject();
                    stateWriter.WritePropertyName(TgtLang);
                    stateWriter.WriteValue("DeepLTranslator");
                stateWriter.WriteEndObject();
                stateWriter.WritePropertyName("PreserveFormattingParameter");
                stateWriter.WriteValue(false);
                stateWriter.WritePropertyName("SendPlainTextParameter");
                stateWriter.WriteValue(false);
                stateWriter.WritePropertyName("ResendDraftParameter");
                stateWriter.WriteValue(false);
                stateWriter.WritePropertyName("ModelTypeParameter");
                stateWriter.WriteValue("Latency_Optimized");
                stateWriter.WritePropertyName("TagHandlingParameter");
                stateWriter.WriteValue("None");
                stateWriter.WritePropertyName("SplitSentenceHandlingParameter");
                stateWriter.WriteValue("Default");
                stateWriter.WritePropertyName("Uri");
                stateWriter.WriteValue("deepltranslationprovider:///");
            stateWriter.WriteEndObject();

            return tw.ToString();
        }

        static int Main(string[] args)
        {

            MtTask mtTask = new MtTask(args[0]);

            try
            {
                ProjectProcessor processor = new ProjectProcessor();

                FileBasedProject project = processor.SetProject(mtTask.ProjectFile);

                foreach (TargLang targLang in mtTask.TargLangs)
                {
                    if (targLang.Provider == "DeepL")
                    {
                        Console.WriteLine($"Configuring DeepL Settings for {targLang.Lang.ToString()}...");
                        DeepLPluginOptions options = new DeepLPluginOptions();
                        options.AddDeepLPluginToProject(
                            project,
                            targLang.Api,
                            targLang.ProviderId,
                            targLang.ProviderName,
                            targLang.Lang
                        Console.WriteLine($"Pre-translating {targLang.Lang} files...");

                        processor.PreTranslateTargetLanguageFiles(project, targLang.Lang);
                    }
                }

                return ConsoleHelper.WriteSuccess("PackageCreation");
            }
            catch (Exception ex)
            {
                return ConsoleHelper.WriteError(ex);
            }
        }

As you can see, for the most part, it goes more or less the same way, except we spell out the json content to be inserted as the provider State. Or do we have to rely completely on Trados to insert it automatically? We tried it that way, and it didn't seem to work...

Create Project Via API shows files as Reference

Mark Owens — Mon, 30 Mar 2026 11:05:15 GMT

I've recently upgraded to Trados 2024, and am running code that creates a new project from a Studio 2024 template, add files, and machine translates. All VS references are for Studio 2024 assemblies.

The template is setup exactly as you'd expect to do this. There is no memory selected, and the DeepL translation configuration is correct. The file types for the template have most entries in the list unticked, but XML2: MadCap Compliant is ticked.

The program steps are:

Create project
AddFolderWithFiles (recursively)
Save project
Scan files
Save project
ConvertToTranslatableFormat (via RunAutomatiobTask)
CopyToTargetLanguages (via RunAutomatiobTask)
Save project
Modify settings to applyAutomatedTranslation
Save settings
Save project
PreTranslateFiles (via RunAutomatiobTask)
Save project

It never seems to use the project template setting to recognise the .htm files are translatable.

If I create the project manually, with the same template, same source files, it performs the MT as expected.

There must be some sort of gotcha going on. Can anyone tell me where I'm going wrong?
Thanks

Mark