Our documentation automatically fills in the product name and other details so you don't have to make the changes manually if we decide to update the product name. Use the 'var:VariableName' construct to tell our documentation engine to fill in the info for you. Here are the constructs available at this point:
Trados Studio - The product name, for example Trados Studio
-Trados Studio 2024 SR1 - The official product release name including the edition, for example 'Trados Studio 2021'
-Studio18 - the official product version, for example Studio16
-18 - the official product version number, such as 16
+Trados Studio 2026 Release - The official product release name including the edition, for example 'Trados Studio 2021'
+Studio19 - the official product version, for example Studio16
+19 - the official product version number, such as 16
Microsoft Visual Studio 2022 - the most recent development compatible Microsoft Visual Studio edition
-%AppData%\Trados\Trados Studio\18\Plugins\Packages\ - the location where plugins are deployed, for example '%AppData%\Roaming\SDL\SDL Trados Studio\16\Plugins\Packages\'
-%AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ - the location where plugins are unpacked, for example '%AppData%\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked\'
-C:\Program Files (x86)\Trados\Trados Studio\Studio18 - the current installation folder of our product, for example 'C:\Program Files\SDL\SDL Trados Studio\Studio16\'
+%AppData%\Trados\Trados Studio\19\Plugins\Packages\ - the location where plugins are deployed, for example '%AppData%\Roaming\SDL\SDL Trados Studio\16\Plugins\Packages\'
+%AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ - the location where plugins are unpacked, for example '%AppData%\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked\'
+C:\Program Files (x86)\Trados\Trados Studio\Studio19 - the current installation folder of our product, for example 'C:\Program Files\SDL\SDL Trados Studio\Studio16\'
Make sure that you sign your assembly. Then build the assembly. The project is automatically configured to build the plug-in file into the folder: %AppData%\Trados\Trados Studio\18\Plugins\Packages\ . After you have built the plug-in, you should find the file Custom Batch Task1.sdlplugin. Now start Trados Studio. Because the plug-in is not yet officially signed by RWS, you will see the following message after you start the application: +
Make sure that you sign your assembly. Then build the assembly. The project is automatically configured to build the plug-in file into the folder: %AppData%\Trados\Trados Studio\19\Plugins\Packages\ . After you have built the plug-in, you should find the file Custom Batch Task1.sdlplugin. Now start Trados Studio. Because the plug-in is not yet officially signed by RWS, you will see the following message after you start the application:
-For the moment, ignore this message. Click Yes to make sure that Trados Studio extracts the plug-in file. Once Studio is started, you should find the sub-folder Custom Batch Task1 under %AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ . This sub-folder contains the unpacked plug-in assemblies.
In the batch tasks list of Trados Studio, you will see the name of your newly compiled plug-in:
When you select your sample batch task you will see the following window with the plug-in description: diff --git a/apiconcepts/core/overview.html b/apiconcepts/core/overview.html index 56978d716..fd1ff65b5 100644 --- a/apiconcepts/core/overview.html +++ b/apiconcepts/core/overview.html @@ -84,7 +84,7 @@
This help system describes the Plug-in Framework. This framework offers plug-in functionality to applications and components. Application developers can define extension points and dynamically load any plug-ins providing extensions targeting these extension points using the plug-in framework.
The version of the Plug-in Framework documented here is the one that was released with Trados Studio 2024 SR1.
+The version of the Plug-in Framework documented here is the one that was released with Trados Studio 2026 Release.
This section introduces a number of concepts and definitions that are central to the plug-in framework.
When creating a plug-in project using the project template from the SDK, the project file will contain the following pieces of custom content:
CreatePluginPackage - if set to true will generate the *.sdlpluginPluginDeploymentPath - path to the root folder where the Packages and Unpacked folders are present, default path is set to %AppData%\Trados\Trados Studio\18\Plugins\Packages\PluginDeploymentPath - path to the root folder where the Packages and Unpacked folders are present, default path is set to %AppData%\Trados\Trados Studio\19\Plugins\Packages\In order for Trados Studio to pick up the plug-in package and to extract it, the following folders need to be available on your hard drive:
For Windows 10\ Windows 7\ Windows 8:
and
Make sure that you place the *.sdlplugin file into the sub-folder Packages and launch Trados Studio. During startup of Trados Studio the content of the package will be automatically extracted to the Unpacked sub-folder, as illustrated below:
The above folder does not have to be the build output path, but it is convenient to build the project in this folder, as this will also create the *.sdlplugin file where it needs to be. After creating the plug-in based on the (empty) template, you could already build the project. However, it will, of course, not offer any functionality.
@@ -145,10 +145,10 @@Here are a couple of simple suggestions to help buld and debug your plug-in.
rmdir /S /Q "%AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ \Sdl.Sdk.FileTypeSupport.Samples.Bil"
+rmdir /S /Q "%AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ \Sdl.Sdk.FileTypeSupport.Samples.Bil"
See Also
diff --git a/apiconcepts/filetypesupport/create_a_new_bil_project.html b/apiconcepts/filetypesupport/create_a_new_bil_project.html
index 6a50ab300..0c767d1f0 100644
--- a/apiconcepts/filetypesupport/create_a_new_bil_project.html
+++ b/apiconcepts/filetypesupport/create_a_new_bil_project.html
@@ -96,7 +96,7 @@ Add the Required References
- Sdl.Core.Settings.dll
- Sdl.Core.PluginFramework.dll
-By default you will find these files in the Trados Studio installation folder, e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio18. The Copy Local property for these references should be set to True.
+By default you will find these files in the Trados Studio installation folder, e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio19. The Copy Local property for these references should be set to True.
diff --git a/apiconcepts/filetypesupport/create_a_new_native_project.html b/apiconcepts/filetypesupport/create_a_new_native_project.html
index c6c8d8014..e5abb1496 100644
--- a/apiconcepts/filetypesupport/create_a_new_native_project.html
+++ b/apiconcepts/filetypesupport/create_a_new_native_project.html
@@ -97,7 +97,7 @@ Add the Required References
Sdl.Core.Settings.dll
Sdl.Core.PluginFramework.dll
-By default you find these files in the Trados Studio installation folder, usually C:\Program Files (x86)\Trados\Trados Studio\Studio18. The Copy Local property for these references should be set to True.
+By default you find these files in the Trados Studio installation folder, usually C:\Program Files (x86)\Trados\Trados Studio\Studio19. The Copy Local property for these references should be set to True.
Note
diff --git a/apiconcepts/filetypesupport/creating_a_new_assembly_for_the_settings_ui.html b/apiconcepts/filetypesupport/creating_a_new_assembly_for_the_settings_ui.html
index 363dd08ac..2ec7b953a 100644
--- a/apiconcepts/filetypesupport/creating_a_new_assembly_for_the_settings_ui.html
+++ b/apiconcepts/filetypesupport/creating_a_new_assembly_for_the_settings_ui.html
@@ -97,7 +97,7 @@ Add the Required References
Sdl.Core.Settings.dll
Sdl.FileTypeSupport.Framework.Core.Settings.dll
-Set the output path for building your project to the installation folder of Trados Studio, e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio18.
+Set the output path for building your project to the installation folder of Trados Studio, e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio19.
See Also
Implementing the UI Controller Class
diff --git a/apiconcepts/filetypesupport/creating_a_new_bil_project.html b/apiconcepts/filetypesupport/creating_a_new_bil_project.html
index 46b0e3f11..c1daaf796 100644
--- a/apiconcepts/filetypesupport/creating_a_new_bil_project.html
+++ b/apiconcepts/filetypesupport/creating_a_new_bil_project.html
@@ -98,7 +98,7 @@ Add the Required References
Sdl.Core.PluginFramework.dll
Sdl.Core.Settings.dll
-By default you find these files in the Trados Studio installation folder, usually C:\Program Files (x86)\Trados\Trados Studio\Studio18. The Copy Local property for these references should be set to True.
+By default you find these files in the Trados Studio installation folder, usually C:\Program Files (x86)\Trados\Trados Studio\Studio19. The Copy Local property for these references should be set to True.
Remember to generate a key to sign the assembly. It is also recommended that you set SDLTradosStudio.exe as the external application for debugging purposes.
Add the Required Resources
Add a resources file (Resources.resx) to the project's properties. We will use this resources file later for storing information text on the file type plug-in that will be exposed in the user interface of Trados Studio.
diff --git a/apiconcepts/filetypesupport/creating_a_new_project.html b/apiconcepts/filetypesupport/creating_a_new_project.html
index 33500455f..ab736ca18 100644
--- a/apiconcepts/filetypesupport/creating_a_new_project.html
+++ b/apiconcepts/filetypesupport/creating_a_new_project.html
@@ -95,7 +95,7 @@ Add the Required References
Sdl.Core.Globalization.dll
Sdl.FileTypeSupport.Framework.Core.Utilities
-By default these files can be found in the installation folder of Trados Studio, i.e. C:\Program Files (x86)\Trados\Trados Studio\Studio18. The 'Copy Local' property for these references should be set to True.
+By default these files can be found in the installation folder of Trados Studio, i.e. C:\Program Files (x86)\Trados\Trados Studio\Studio19. The 'Copy Local' property for these references should be set to True.
Note
diff --git a/apiconcepts/integration/create_a_trados_studio_commandLineProcessor.html b/apiconcepts/integration/create_a_trados_studio_commandLineProcessor.html
index 166ef2c2d..c25aee589 100644
--- a/apiconcepts/integration/create_a_trados_studio_commandLineProcessor.html
+++ b/apiconcepts/integration/create_a_trados_studio_commandLineProcessor.html
@@ -92,7 +92,7 @@ Creating a Tr
If you don't implement IExternalCommandLineProcessor or IExternalWindowAwareCommandLineProcessor, an exception will be thrown, but if you omit the ExternalCommandLineProcessorAttribute, your plugin will simply be ignored when Trados Studio starts.
-After successfully creating your command line processor you can check the Help generated for it by and running the following command in cmd.exe : C:\Program Files (x86)\Trados\Trados Studio\Studio18\SdlTradosStudio.exe ? . Your command will appear, among other commands available, in the following screen :
+
After successfully creating your command line processor you can check the Help generated for it by and running the following command in cmd.exe : C:\Program Files (x86)\Trados\Trados Studio\Studio19\SdlTradosStudio.exe ? . Your command will appear, among other commands available, in the following screen :
[Creating a Trados Studio Command line processor Sample]
(trados_studio_command_processor.md)
diff --git a/apiconcepts/integration/setting_up_the_visual_studio_project.html b/apiconcepts/integration/setting_up_the_visual_studio_project.html
index 3fd5049ee..48d68ebee 100644
--- a/apiconcepts/integration/setting_up_the_visual_studio_project.html
+++ b/apiconcepts/integration/setting_up_the_visual_studio_project.html
@@ -93,7 +93,7 @@ How to create the Visual Studio
Important
The The Sdl.Core.Globalization assembly is not automatically added to the project with the Trados Studio (2021) template. This assembly will be required for this project, as we will be making reference to some of the ISegmentPair enumerators.
-To add this assembly, from the Solution Explorer, right-click on the References node and click Add Reference from the context menu. Then, navigate to the C:\Program Files (x86)\Trados\Trados Studio\Studio18 and select the Sdl.Core.Globalization.dll file.
+To add this assembly, from the Solution Explorer, right-click on the References node and click Add Reference from the context menu. Then, navigate to the C:\Program Files (x86)\Trados\Trados Studio\Studio19 and select the Sdl.Core.Globalization.dll file.
How to sign the solution
To sign your development solution from the project properties area.
diff --git a/apiconcepts/integration/studio_automation.html b/apiconcepts/integration/studio_automation.html
index 51e48bd2d..3565c6dd3 100644
--- a/apiconcepts/integration/studio_automation.html
+++ b/apiconcepts/integration/studio_automation.html
@@ -98,8 +98,8 @@ Introduction
Note
-As build output path for your implementations please choose the %AppData%\Trados\Trados Studio\18\Plugins\Packages\.
-Also check that your library references are pointing to the Trados Studio folder. e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio18.
+As build output path for your implementations please choose the %AppData%\Trados\Trados Studio\19\Plugins\Packages\.
+Also check that your library references are pointing to the Trados Studio folder. e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio19.
For more information on how to build and deploy a Studio plug-in, see (Building a plug-in and Plug-in deployment)
Sign and use Strong-Named Assemblies to enable the loading of your plug-ins inside the Trados Studio.
How to: Sign an Assembly with a Strong Name
diff --git a/apiconcepts/integration/user_interface_integration.html b/apiconcepts/integration/user_interface_integration.html
index 23b1d1b9e..88a70c344 100644
--- a/apiconcepts/integration/user_interface_integration.html
+++ b/apiconcepts/integration/user_interface_integration.html
@@ -93,8 +93,8 @@ Introduction
Note
-As build output path for your implementations please choose the %AppData%\Trados\Trados Studio\18\Plugins\Packages\.
-Also check that your library references are pointing to the Trados Studio folder. e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio18.
+As build output path for your implementations please choose the %AppData%\Trados\Trados Studio\19\Plugins\Packages\.
+Also check that your library references are pointing to the Trados Studio folder. e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio19.
For more information on building an deploying a Trados Studio plug-in, see (Building a plug-in and Plug-in deployment).
Sign and use Strong-Named Assemblies to enable the loading of your plug-ins inside the Trados Studio.
diff --git a/apiconcepts/projectautomation/about_project_files.html b/apiconcepts/projectautomation/about_project_files.html
index 2fd84ec34..d9b8c6dcb 100644
--- a/apiconcepts/projectautomation/about_project_files.html
+++ b/apiconcepts/projectautomation/about_project_files.html
@@ -112,7 +112,7 @@ Reference Files
Reference files are files that need to be part of the project, for instance for preview reasons, but that can be changed as part of the project. Reference files are language files, which means they are associated with a particular project language.
Reference files are represented by the IReferenceFile interface in the object model.
-The screenshot above illustrates how project files are selected in Trados Studio 2024 SR1.
+The screenshot above illustrates how project files are selected in Trados Studio 2026 Release.
See also
diff --git a/apiconcepts/projectautomation/required_references_and_namespaces.html b/apiconcepts/projectautomation/required_references_and_namespaces.html
index 694c76686..bd420fa09 100644
--- a/apiconcepts/projectautomation/required_references_and_namespaces.html
+++ b/apiconcepts/projectautomation/required_references_and_namespaces.html
@@ -109,7 +109,7 @@ Namespaces to Use
Further Requirements
In addition to the above, you should observer the following:
-- As build output location choose the installation folder of Trados Studio , e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio18
+- As build output location choose the installation folder of Trados Studio , e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio19
- Configure your projects as x84 applications, as otherwise they will not work when running on 64 bit platforms. Therefore, set the platform target of your projects to x84.
References from the Translation Memory API
diff --git a/apiconcepts/projectautomation/setting_the_project_information.html b/apiconcepts/projectautomation/setting_the_project_information.html
index 727440a51..7f020b4db 100644
--- a/apiconcepts/projectautomation/setting_the_project_information.html
+++ b/apiconcepts/projectautomation/setting_the_project_information.html
@@ -137,7 +137,7 @@ Set the Project Information
The screenshot below illustrates how this information is entered in the New Project wizard of Trados Studio.
Set the Local Project Folder
-All project files, i.e. translatable and localizable documents, reference files, project TMs, etc. are stored in a specific folder. By default, the main folder used for storing projects is: C:\Users\UserName\Documents\Studio 2024\Projects. Below this main folder Trados Studio creates sub-folders that carry the name of the respective project. However, you could just as well pick any other folder name, as long as the specified folder is empty so as to avoid collisions with existing files. In the example below we follow the default folder rule of Trados Studio by selecting the Studio 2024\Projects\ folder below Documents, and by appending the project name sub-folder. We then set the LocalProjectFolder property accordingly as shown in the example below:
+All project files, i.e. translatable and localizable documents, reference files, project TMs, etc. are stored in a specific folder. By default, the main folder used for storing projects is: C:\Users\UserName\Documents\Studio 2026 Release\Projects. Below this main folder Trados Studio creates sub-folders that carry the name of the respective project. However, you could just as well pick any other folder name, as long as the specified folder is empty so as to avoid collisions with existing files. In the example below we follow the default folder rule of Trados Studio by selecting the Studio 2026 Release\Projects\ folder below Documents, and by appending the project name sub-folder. We then set the LocalProjectFolder property accordingly as shown in the example below:
-
@@ -218,7 +218,7 @@
Select the Project Languages
After running the above code you should already see a result in the projects folder as illustrated in the screenshot below:
Even if you have not added any translatable files yet, you will end up generating the project sub-folder (i.e. Projects\My first project), which contains the *.sdlproj file. In the following chapters you will learn how to add documents, TMs, termbases, etc. to turn your sample into a meaningful project. Note that if you run your sample application again while the My first project is still there, an error will be thrown, as the folder is not empty. It is recommended that when you re-run your sample application for testing purposes that you delete the project sub-folder, so that you have a fresh start (see also Deleting Projects).
-Also note that the C:\Users\UserName\Documents\Studio 2024\Projects folder contains a file called projects.xml. This is a meta file that contains references to all the projects that have been created in Trados Studio. The projects that you create programmatically will not be referenced in this file, and thus not be listed in Trados Studio, which is by design. However, you can, of course, open the programmatically created *.sdlproj file in Trados Studio.
+Also note that the C:\Users\UserName\Documents\Studio 2026 Release\Projects folder contains a file called projects.xml. This is a meta file that contains references to all the projects that have been created in Trados Studio. The projects that you create programmatically will not be referenced in this file, and thus not be listed in Trados Studio, which is by design. However, you can, of course, open the programmatically created *.sdlproj file in Trados Studio.
Putting it All Together
The complete function for setting the project properties should look as shown below:
diff --git a/apiconcepts/projectautomation/setting_up_the_visual_studio_project.html b/apiconcepts/projectautomation/setting_up_the_visual_studio_project.html
index cefa7fa72..595dd540a 100644
--- a/apiconcepts/projectautomation/setting_up_the_visual_studio_project.html
+++ b/apiconcepts/projectautomation/setting_up_the_visual_studio_project.html
@@ -101,7 +101,7 @@ Setting up the Visual Studio Proje
- Sdl.LanguagePlatform.TranslationMemoryApi.dll
Note that we require the functionality of the Translation Memory API to access information on the selected TM, i.e. the source / target language combination. Note that this is a case in point of how the Project Automation API and the Translation Memory API are sometimes required to be leveraged both to implement the functionality of your applications.
-Make sure to set the project build output location to the Trados Studio installation folder, e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio18. Important note: Set the platform target of your projects to x86.
+Make sure to set the project build output location to the Trados Studio installation folder, e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio19. Important note: Set the platform target of your projects to x86.
See Also
Required References and Namespaces
diff --git a/apiconcepts/releasenotes/overview.html b/apiconcepts/releasenotes/overview.html
index 65b25924f..a2658c492 100644
--- a/apiconcepts/releasenotes/overview.html
+++ b/apiconcepts/releasenotes/overview.html
@@ -82,8 +82,8 @@
Trados Studio API Release Notes
-A list of API changes released together with Trados Studio 2024 SR1.
-API Changes for Trados Studio 2024 SR1
+A list of API changes released together with Trados Studio 2026 Release.
+API Changes for Trados Studio 2026 Release
diff --git a/apiconcepts/releasenotes/tradosstudio2022.html b/apiconcepts/releasenotes/tradosstudio2022.html
index 7b95c349a..81134b395 100644
--- a/apiconcepts/releasenotes/tradosstudio2022.html
+++ b/apiconcepts/releasenotes/tradosstudio2022.html
@@ -5,9 +5,9 @@
- Release Notes for Trados Studio 2024 SR1
+ Release Notes for Trados Studio 2026 Release
-
+
@@ -80,10 +80,10 @@
-Release Notes for Trados Studio 2024 SR1
+Release Notes for Trados Studio 2026 Release
Groupshare 2015 Integration
-As of Trados Studio 2024 SR1 the integration with Groupshare 2015 is EOL. Therefore the our public APIs no longer offer the support and any code references have been removed.
+As of Trados Studio 2026 Release the integration with Groupshare 2015 is EOL. Therefore the our public APIs no longer offer the support and any code references have been removed.
Project Automation API
New properties on ProjectInfo
We expanded the ProjectInfo class to include information regarding the current user associated to the project.
diff --git a/apiconcepts/releasenotes/tradosstudio2022sr1.html b/apiconcepts/releasenotes/tradosstudio2022sr1.html
index 27b6e0adc..f7c90dc60 100644
--- a/apiconcepts/releasenotes/tradosstudio2022sr1.html
+++ b/apiconcepts/releasenotes/tradosstudio2022sr1.html
@@ -5,9 +5,9 @@
- Release Notes for Trados Studio 2024 SR1 SR1
+ Release Notes for Trados Studio 2026 Release SR1
-
+
@@ -80,10 +80,10 @@
-Release Notes for Trados Studio 2024 SR1 SR1
+Release Notes for Trados Studio 2026 Release SR1
Retargeted assemblies
-Some of the available APIs provided along with Trados Studio 2024 SR1 have been retargeted from .NET Framework 4.8 to .NET Standard for better compatibility options and richer overall support.
+Some of the available APIs provided along with Trados Studio 2026 Release have been retargeted from .NET Framework 4.8 to .NET Standard for better compatibility options and richer overall support.
At the time of this release, the retargeted assemblies are as follows:
| Parent API | Assembly |
|--------------------------------------|------------------------------------------------------|
@@ -261,7 +261,7 @@
General API changes
```
Dependency version changes
-The following is a list of known dependency version changes that may influence your integration with the latest Trados Studio 2024 SR1 APIs; this is typically seen from standalone applications that are running outside of the Trados Studio context. To resolve these references, include the following binding redirects in the configuration file of the project.
+The following is a list of known dependency version changes that may influence your integration with the latest Trados Studio 2026 Release APIs; this is typically seen from standalone applications that are running outside of the Trados Studio context. To resolve these references, include the following binding redirects in the configuration file of the project.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
diff --git a/apiconcepts/releasenotes/tradosstudio2022sr2.html b/apiconcepts/releasenotes/tradosstudio2022sr2.html
index 4425958f3..7a0bbc7d6 100644
--- a/apiconcepts/releasenotes/tradosstudio2022sr2.html
+++ b/apiconcepts/releasenotes/tradosstudio2022sr2.html
@@ -5,9 +5,9 @@
- Release Notes for Trados Studio 2024 SR1 SR2
+ Release Notes for Trados Studio 2026 Release SR2
-
+
@@ -80,13 +80,13 @@
-Release Notes for Trados Studio 2024 SR1 SR2
+Release Notes for Trados Studio 2026 Release SR2
Added API licensing support for subscriptions
When creating standalone apps, you can now use Project automation API calls that need a license even if Trados Studio is licensed through a subscription. This expands the list of supported scenarios where Trados Studio is licensed through a perpetual license, or through a network server license.
Note
-Starting with Trados Studio 2024 SR1 SR2, when developing a standalone application using Project Automation APIs that require a license, make sure to call LicenseManager.ReleaseLicense() before the application exits. See Project Automation Overview for more details.
+Starting with Trados Studio 2026 Release SR2, when developing a standalone application using Project Automation APIs that require a license, make sure to call LicenseManager.ReleaseLicense() before the application exits. See Project Automation Overview for more details.
Terminology Provider
The changes are included in Sdl.Terminology.TerminologyProvider.Core.
diff --git a/apiconcepts/releasenotes/tradosstudio2024.html b/apiconcepts/releasenotes/tradosstudio2024.html
index e915cda16..ef5f329ed 100644
--- a/apiconcepts/releasenotes/tradosstudio2024.html
+++ b/apiconcepts/releasenotes/tradosstudio2024.html
@@ -5,9 +5,9 @@
- Release Notes for Trados Studio 2024 SR1
+ Release Notes for Trados Studio 2026 Release
-
+
@@ -80,7 +80,7 @@
-Release Notes for Trados Studio 2024 SR1
+Release Notes for Trados Studio 2026 Release
Trados Studio Automation
The changes are included in Sdl.TranslationStudioAutomation.IntegrationApi.
diff --git a/apiconcepts/releasenotes/tradosstudio2024sr1.html b/apiconcepts/releasenotes/tradosstudio2024sr1.html
index ded182b87..7e9ed7699 100644
--- a/apiconcepts/releasenotes/tradosstudio2024sr1.html
+++ b/apiconcepts/releasenotes/tradosstudio2024sr1.html
@@ -5,9 +5,9 @@
- Release Notes for Trados Studio 2024 SR1 SR1
+ Release Notes for Trados Studio 2026 Release SR1
-
+
@@ -80,7 +80,7 @@
-Release Notes for Trados Studio 2024 SR1 SR1
+Release Notes for Trados Studio 2026 Release SR1
MultiTerm TMO Interop
Sdl.Multiterm.TMO.Interop.dll is no longer present in the install folder after the separation from MultiTerm.
diff --git a/apiconcepts/terminology/settingup_the_visual_studio_project.html b/apiconcepts/terminology/settingup_the_visual_studio_project.html
index 1fddb7d19..92dc66de6 100644
--- a/apiconcepts/terminology/settingup_the_visual_studio_project.html
+++ b/apiconcepts/terminology/settingup_the_visual_studio_project.html
@@ -115,9 +115,9 @@ The Plug-in Declaration: ID
Make sure the resource file access modifier is set to public and that you treat it as an embedded resource.
Open the MyTerminologyProviderWinFormsUI.cs class. This class controls how the plug-in manifests in the Trados Studio UI. Change the TypeName and TypeDescription members as shown below.
How to build and load the plugin in Trados Studio
-Build the assembly. The project is automatically configured to build the plug-in file into the %AppData%\Trados\Trados Studio\18\Plugins\Packages\ folder. After you have built the plug-in, you should find the Terminology Provider1.sdlplugin file in the folder. Start Trados Studio. As the plug-in is not yet officially signed by RWS, you will see the following message when starting the application:
+
Build the assembly. The project is automatically configured to build the plug-in file into the %AppData%\Trados\Trados Studio\19\Plugins\Packages\ folder. After you have built the plug-in, you should find the Terminology Provider1.sdlplugin file in the folder. Start Trados Studio. As the plug-in is not yet officially signed by RWS, you will see the following message when starting the application:
-For the moment, ignore this message and click Yes to make sure that Trados Studio extracts the plug-in file. Once Trados Studio is started, you should find the sub-folder Terminology Provider1 under %AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ . This sub-folder contains the unpacked plug-in assemblies.
+For the moment, ignore this message and click Yes to make sure that Trados Studio extracts the plug-in file. Once Trados Studio is started, you should find the sub-folder Terminology Provider1 under %AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ . This sub-folder contains the unpacked plug-in assemblies.
Note
To officially sign the plugin, send the sdlplugin file to app-signing@sdl.com.
diff --git a/apiconcepts/translationmemory/building_the_plugin.html b/apiconcepts/translationmemory/building_the_plugin.html
index f0be3dae3..ccb1a35fb 100644
--- a/apiconcepts/translationmemory/building_the_plugin.html
+++ b/apiconcepts/translationmemory/building_the_plugin.html
@@ -91,9 +91,9 @@ Building the Plug-in
In order for Trados Studio to pick up the plug-in package and to extract it, the following folders need to be available on your hard drive:
**For Windows 10 / Windows 8.1 **:
-%AppData%\Trados\Trados Studio\18\Plugins\Packages\
+%AppData%\Trados\Trados Studio\19\Plugins\Packages\
and
-%AppData%\Trados\Trados Studio\18\Plugins\Unpacked\
+%AppData%\Trados\Trados Studio\19\Plugins\Unpacked\
Make sure that you place the *.sdlplugin file into the sub-folder Packages and launch Trados Studio. During startup of Trados Studio the content of the package will be automatically extracted to the Unpacked sub-folder, as illustrated below:
Upon start-up Trados Studio will load the unpacked plug-in and show the following message, which you can confirm with Yes, so that the plug-in gets loaded. This message appears when loading plug-ins that have not been certified by RWS, which could potentially be unsafe. The message can be avoided by submitting your plug-in to RWS for certification.
diff --git a/apiconcepts/verification/create_a_new_project.html b/apiconcepts/verification/create_a_new_project.html
index 86fe4c64b..b6bb6c7d5 100644
--- a/apiconcepts/verification/create_a_new_project.html
+++ b/apiconcepts/verification/create_a_new_project.html
@@ -94,7 +94,7 @@ Add the Required References
- Sdl.FileTypeSupport.Framework.Core
- Sdl.Core.Settings.dll
-By default, these files can be found in the installation folder of Trados Studio, i.e. C:\Program Files (x86)\Trados\Trados Studio\Studio18. The 'Copy Local' property for these references should be set to True.
+By default, these files can be found in the installation folder of Trados Studio, i.e. C:\Program Files (x86)\Trados\Trados Studio\Studio19. The 'Copy Local' property for these references should be set to True.
Note
diff --git a/articles/gettingstarted/building_a_plugin.html b/articles/gettingstarted/building_a_plugin.html
index d2acd73e4..203035721 100644
--- a/articles/gettingstarted/building_a_plugin.html
+++ b/articles/gettingstarted/building_a_plugin.html
@@ -127,7 +127,7 @@ Building a Plug-in
- Description: description of the plug-in package.
- Author: the name of the plug-in author
- RequiredProduct: this indicates which product this plug-in supports. This must include the minimum version and can optionally include a maximum version.
-If the minimum version is set to 18.1 that means the plugin can be installed only in Trados Studio SR1 and above.
+If the minimum version is set to 19.1 that means the plugin can be installed only in Trados Studio SR1 and above.
- Include: a list of additional files to be included into the plugin package.
Any plugin project need to have the following nuget packages refrenced :
@@ -150,7 +150,7 @@ Note
- The plug-in package,
MyPlugin.sdlplugin which contains all of the above, together with the plug-in package manifest.
-After all the relevant information was added, build the project. Plugin can be found at the following local path %AppData%\Trados\Trados Studio\18\Plugins\Packages\ if the default path wasn't changed.
+After all the relevant information was added, build the project. Plugin can be found at the following local path %AppData%\Trados\Trados Studio\19\Plugins\Packages\ if the default path wasn't changed.
If in the console following error appears: Error 1 Failed to locate ResGen.exe and unable to compile plug-in resource file... please make sure you have installed .Net Framework 4.8.
Now, we are ready to deploy the plug-in package in Trados Studio. See Plug-in deployment.
diff --git a/articles/gettingstarted/community_plugins.html b/articles/gettingstarted/community_plugins.html
index dfce7a174..31b5f9715 100644
--- a/articles/gettingstarted/community_plugins.html
+++ b/articles/gettingstarted/community_plugins.html
@@ -94,7 +94,7 @@ Getting Started
After the repository was cloned, navigate to the repository path you’ve specified when cloning the repository. Each plugin has a dedicated folder. All you need to do is to find the plugin you’re looking for, enter the folder and open the solution file using Microsoft Visual Studio.
Build the solution. After the build has succeeded, open Trados Studio 2024 SR1. Click “Yes” when the warning message appears. After Trados Studio loads, the built plugin will be available in Trados Studio.
+Build the solution. After the build has succeeded, open Trados Studio 2026 Release. Click “Yes” when the warning message appears. After Trados Studio loads, the built plugin will be available in Trados Studio.
diff --git a/articles/gettingstarted/plugin_deployment.html b/articles/gettingstarted/plugin_deployment.html
index 1dd295f60..bdf333d3f 100644
--- a/articles/gettingstarted/plugin_deployment.html
+++ b/articles/gettingstarted/plugin_deployment.html
@@ -87,14 +87,14 @@ Installing a Plug-in Package
Double click the plug-in package and follow the instructions.
Note
-During development, you can configure the output path of the project to point to %AppData%\Trados\Trados Studio\18\Plugins\Packages\. This is already configured if you created the project with one of the project templates available in the Trados Studio SDK here. For more information on this, see Setting up a Developer Machine.
+During development, you can configure the output path of the project to point to %AppData%\Trados\Trados Studio\19\Plugins\Packages\. This is already configured if you created the project with one of the project templates available in the Trados Studio SDK here. For more information on this, see Setting up a Developer Machine.
The following warning message will be shown while Trados Studio starts:
To avoid this message from appearing, you need to submit your plug-in package to RWS for verification. Once verified, your plug-in package will be signed by RWS and the warning message will not appear anymore. To verify the plugin, send an email to app-signing@sdl.com with a link from where the plugin can be downloaded for verification. Once the verification is done, you will receive an answer email with a download link, where you will be able to obtain the signed version of the plugin.
Once Trados Studio has started, go to the Tools > Plug-ins dialog and notice that "MyPlugin" is now listed as a plug-in and is ready to be used.
Updating a Plug-in Package
-Once deployed, you can update your plug-in package by increasing the version in the plug-in package manifest (see Plug-in deployment). Double click the plug-in package and follow the instructions. Once the plug-in is deployed, start Trados Studio. The application will automatically detect the presence of the updated plug-in package, verify it, extract its contents into %AppData%\Trados\Trados Studio\18\Plugins\Unpacked\ and load it.
+Once deployed, you can update your plug-in package by increasing the version in the plug-in package manifest (see Plug-in deployment). Double click the plug-in package and follow the instructions. Once the plug-in is deployed, start Trados Studio. The application will automatically detect the presence of the updated plug-in package, verify it, extract its contents into %AppData%\Trados\Trados Studio\19\Plugins\Unpacked\ and load it.
It is essential that you increase the version of the plug-in package as listed in the plug-in manifest, or the update will not be applied.
Uninstalling a Plug-in Package
To uninstall a plug-in, you have two options:
diff --git a/articles/gettingstarted/setting_up_a_developer_machine.html b/articles/gettingstarted/setting_up_a_developer_machine.html
index 99e0acc7a..1e3490a76 100644
--- a/articles/gettingstarted/setting_up_a_developer_machine.html
+++ b/articles/gettingstarted/setting_up_a_developer_machine.html
@@ -86,7 +86,7 @@ Setting up a Developer Machine
Prerequisites
- For the development environment, we recommend using Microsoft Visual Studio 2022.
-- You need a licensed Trados Studio 2024 SR1 or later installed on your development machine
+- You need a licensed Trados Studio 2026 Release or later installed on your development machine
- We also recommend installation of the Trados Studio SDK on your machine. Note that after the installation of Trados Studio SDK, the New Project dialog box from Microsoft Visual Studio 2022 will feature additional project templates specific to the Trados Studio application development.
- You can get the latest version from the developer hub.
@@ -95,25 +95,25 @@ Prerequisites
- If your implementations need to connect to a TM Server system, then make sure that the TM Server also runs the latest version.
-- If you are developing against a version of API the which is distributed with one of SDL's publicly released applications (i.e. Trados Studio 2024 SR1), then all required assemblies and files should be available alongside the application. Make sure that you have the latest release of Trados Studio installed.
+- If you are developing against a version of API the which is distributed with one of SDL's publicly released applications (i.e. Trados Studio 2026 Release), then all required assemblies and files should be available alongside the application. Make sure that you have the latest release of Trados Studio installed.
Note
-As build output path for your implementations please choose the %AppData%\Trados\Trados Studio\18\Plugins\Packages\
-Also check that your library references are pointing to the Trados Studio folder. e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio18.
+As build output path for your implementations please choose the %AppData%\Trados\Trados Studio\19\Plugins\Packages\
+Also check that your library references are pointing to the Trados Studio folder. e.g. C:\Program Files (x86)\Trados\Trados Studio\Studio19.
For more informations regarding how to build and deploy a Studio plug-in see Building a plug-in and Plug-in deployment
Sign and use Strong-Named Assemblies to enable the loading of your plug-ins inside Trados Studio. For more information see How to: Sign an Assembly with a Strong Name
If you don't have a key, you can download SdlCommunity.snk key from public AppStore repository.
Choosing a different build output path or not signing your assembly will prevent your plugin to be loaded.
-System requirements for running Trados Studio 2024 SR1:
+System requirements for running Trados Studio 2026 Release:
-- A Microsoft Windows-based PC or an Intel-based Apple Mac computer running Windows as an operating system. Trados Studio 2024 SR1 runs on the latest build of Windows 11 and the latest updated version of Windows 10.
-- Up to 2.5 GB of available disk space to run the Trados Studio 2024 SR1 installer
-- 2 GB of available disk space to run Trados Studio 2024 SR1
+- A Microsoft Windows-based PC or an Intel-based Apple Mac computer running Windows as an operating system. Trados Studio 2026 Release runs on the latest build of Windows 11 and the latest updated version of Windows 10.
+- Up to 2.5 GB of available disk space to run the Trados Studio 2026 Release installer
+- 2 GB of available disk space to run Trados Studio 2026 Release
- A recent processor with dual or multi-core technology
- At least 8 GB RAM
-- Trados Studio 2024 SR1 requires Microsoft .Net Framework 4.8.
+- Trados Studio 2026 Release requires Microsoft .Net Framework 4.8.
- Additional details can be found on the product release notes
System requirements for running SDL GroupShare ( TM Server, Multiterm, Project Server):
diff --git a/index.html b/index.html
index 87028d3dd..829379b85 100644
--- a/index.html
+++ b/index.html
@@ -5,9 +5,9 @@
- Access the Trados Studio 2024 SR1 APIs
+ Access the Trados Studio 2026 Release APIs
-
+
@@ -73,14 +73,14 @@
-Access the Trados Studio 2024 SR1 APIs
+Access the Trados Studio 2026 Release APIs
-Getting started with Trados Studio 2024 SR1 APIs
+Getting started with Trados Studio 2026 Release APIs
Read more on how you can write your first Trados Studio plugin.
-Learn more about Trados Studio 2024 SR1 APIs
+Learn more about Trados Studio 2026 Release APIs
Learn more about the APIs and what you can achieve with them.
-How to update plugins to Trados Studio 2024 SR1
-Learn more about how you can make your plugin compatible with Trados Studio 2024 SR1.
+How to update plugins to Trados Studio 2026 Release
+Learn more about how you can make your plugin compatible with Trados Studio 2026 Release.
Articles
Read articles on how to get more out of Trados Studio.
Code samples
@@ -88,6 +88,7 @@ Open Source Community Projects
Join our community-driven repository of Trados Studio plugins on RWS Community.
Trados Studio API versions
+Trados Studio 2024 SR1 - API 18.1
Trados Studio 2024 - API 18.0
Trados Studio 2022 - API 17.2
Trados Studio 2022 - API 17.1
diff --git a/index.json b/index.json
index a685095b2..1b594764a 100644
--- a/index.json
+++ b/index.json
@@ -11012,7 +11012,7 @@
"index.html": {
"href": "index.html",
"title": "Access the Var:ProductNameWithEdition APIs",
- "summary": "Access the Var:ProductNameWithEdition APIs Getting started with Var:ProductNameWithEdition APIs Read more on how you can write your first Var:ProductName plugin. Learn more about Var:ProductNameWithEdition APIs Learn more about the APIs and what you can achieve with them. How to update plugins to Var:ProductNameWithEdition Learn more about how you can make your plugin compatible with Var:ProductNameWithEdition. Articles Read articles on how to get more out of Var:ProductName. Code samples Find more of our code samples on GitHub. Open Source Community Projects Join our community-driven repository of Var:ProductName plugins on RWS Community. Var:ProductName API versions Var:ProductName 2024 - API 18.0 Var:ProductName 2022 - API 17.2 Var:ProductName 2022 - API 17.1 Var:ProductName 2022 - API 17.0 Var:ProductName 2021 SR2 - API 16.2 Var:ProductName 2021 SR1 - API 16.1 Var:ProductName 2019 - API 15.2"
+ "summary": "Access the Var:ProductNameWithEdition APIs Getting started with Var:ProductNameWithEdition APIs Read more on how you can write your first Var:ProductName plugin. Learn more about Var:ProductNameWithEdition APIs Learn more about the APIs and what you can achieve with them. How to update plugins to Var:ProductNameWithEdition Learn more about how you can make your plugin compatible with Var:ProductNameWithEdition. Articles Read articles on how to get more out of Var:ProductName. Code samples Find more of our code samples on GitHub. Open Source Community Projects Join our community-driven repository of Var:ProductName plugins on RWS Community. Var:ProductName API versions Var:ProductName 2024 SR1 - API 18.1 Var:ProductName 2024 - API 18.0 Var:ProductName 2022 - API 17.2 Var:ProductName 2022 - API 17.1 Var:ProductName 2022 - API 17.0 Var:ProductName 2021 SR2 - API 16.2 Var:ProductName 2021 SR1 - API 16.1 Var:ProductName 2019 - API 15.2"
},
"writing_guidelines.html": {
"href": "writing_guidelines.html",