IBX-10684: Document translation management#407
Open
dabrt wants to merge 10 commits into
Open
Conversation
Preview of modified filesPreview of modified Markdown: |
juskora
reviewed
Jun 10, 2026
mikadamczyk
reviewed
Jun 22, 2026
| If the translations management feature [is installed and properly configured]([[= developer_doc =]]/multisite/languages/translations_management) in your system, the set of features available for content translation changes: | ||
|
|
||
| - Application administrators can [define language pairs]([[= developer_doc =]]/multisite/languages/translations_management/#define-language-pairs) and assign [translation providers]([[= developer_doc =]]/multisite/languages/translations_management/#configure-translation-providers) to them. | ||
| - Content editors get a redesigned translation interface called side-by-side translation view. If at least one automated translation provider is configured, editors can use them to machine-translate content. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Content editors get a redesigned translation interface called side-by-side translation view. If at least one automated translation provider is configured, editors can use them to machine-translate content. | |
| - Content editors get a redesigned translation interface called side-by-side translation view. | |
| - If at least one automated translation provider is configured, editors can use it to machine-translate content. |
Those two are not connected
| !!! note "Draft conflict" | ||
|
|
||
| If a draft already exists for the selected target language, a warning appears in the modal to inform you about this fact. | ||
| You can proceed and add a new draft, or discard the modal and edit the existing draft translation. |
Contributor
There was a problem hiding this comment.
The provider selection is not always a drop-down. When exactly one provider is enabled, the form renders a single checkbox labeled with that provider instead.
|
|
||
| #### Change source language | ||
|
|
||
| When a content item has three or more published language versions, a dropdown field appears at the top of the source column instead of a label. |
Contributor
There was a problem hiding this comment.
The source-language selector is shown when there are at least two available source languages after excluding the target language. This can already happen with only two existing translations when creating a third one, so "three or more published language versions" seems too strict. Could we describe the condition more generically?
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
3 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.
Document translation management in user doc.
PR waits with images and specific procedures for UI changes to the product.
Checklist