Repository navigation
DET-827: Recognizing Terms in Text (term recognition API, Trados Studio 2026 CU1) - #292
Merged
Merged
Conversation
New article for third-party developers on the term recognition API (TerminologyRecognition, Trados Studio 2026 CU1): when to use it instead of ITerminologyProvider.Search, a quick start with the sample project's Printer termbase, languages and termbase indexes, the request options, reading the results (translations, status, homonyms and synonyms), matching the project's termbase settings, performance, and supporting earlier Studio versions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds the article under Terminology Provider, after Working with File-based Termbases, so it appears in the navigation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cornea-robert
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new article, Recognizing Terms in Text (
apiconcepts/terminology/recognizing_terms.md), for the term recognition API that ships in Trados Studio 2026 CU1 (TerminologyRecognition, Jira DET-827), and adds it to the navigation inapiconcepts/toc.yml(Terminology Provider, after Working with File-based Termbases).The article is written for third-party developers who consume terminology, for example translation providers that pass terms to MT or AI services. It covers:
TerminologyRecognitioninstead ofITerminologyProvider.Search(comparison table).DefinitionLanguage, index name versus culture).Not included in this PR: links to the API reference pages for the new types, which will exist once the CU1 API reference is generated.
Please check the CU1 version number used in the manifest example (
minversion="19.0.1").