docs: correct MT provider list and AI Translator context availability - #1133
Open
JanCizmar wants to merge 1 commit into
Open
docs: correct MT provider list and AI Translator context availability#1133JanCizmar wants to merge 1 commit into
JanCizmar wants to merge 1 commit into
Conversation
Two statements on the docs did not match the product. The machine translation provider list omitted Baidu Translate. It is a real provider (MtServiceType.BAIDU) with its own configuration section in the self-hosting docs, so the list showed four external providers where the product ships five. The AI Translator context note said the functionality is Cloud only. It is not Cloud only; the SDK 5.9.0 requirement is the actual constraint. Both were found while verifying plan gating and feature availability against the platform source.
❌ Deploy Preview for tolgee-docs failed.
|
Member
|
@JanCizmar Build fails on a broken link.
|
Barush
self-requested a review
August 10, 2026 06:31
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
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.
Two statements in the docs do not match the product. Both were found while verifying Tolgee feature availability against the platform source for a comparison page.
Machine translation providers
platform/translation_process/machine_translation.mdxlisted four external providers. The product ships five:MtServiceTypehasGOOGLE,AWS,DEEPL,AZUREandBAIDU, and Baidu Translate has its own configuration section in the self-hosting docs (tolgee.machine-translation.baidu).Added Baidu, marked self-hosted only since it is configured with your own API key via server configuration.
AI Translator context
platform/translation_process/ai_translator.mdxsaid Tolgee Context is "available only in the Cloud version with SDK 5.9.0 and higher". It is not Cloud only. The SDK 5.9.0 requirement is the real constraint, so the note now states just that.Why this matters
Both statements understate what Tolgee does, and a competitor comparison page repeated one of them because our own docs said it. The provider count in particular was used to score a competitor claim as wrong when the competitor was right.
Not covered here
Three further inaccuracies live on
tolgee.io/pricing, which is not in this repo:LlmProviderControllerhas no@RequiresFeaturesand there is no AI translator feature in theFeatureenum.