diff --git a/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/ExtensionIntegration.rst b/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/ExtensionIntegration.rst index 4bdd526f11..76c65708dc 100644 --- a/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/ExtensionIntegration.rst +++ b/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/ExtensionIntegration.rst @@ -221,6 +221,13 @@ Step-by-step instructions for GitHub ```` and ```` elements. If the ```` elements are missing, Crowdin will not be able to match the translations with the original English labels. + .. important:: + Using the recommended GitHub workflow the GitHub default branch can be + mapped to the Crowdin branch name via the attribute :yaml:`crowdin_branch_name`. + It is recommended that you always use `main` as the Crowdin branch name. + **More than one Crowdin branch (for example via different + GitHub branches) is not supported by the Crowdin Bridge!** + 3. Approve imported translations After importing existing translations, they will arrive in Crowdin in an diff --git a/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst b/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst index 968f531053..03c683eed8 100644 --- a/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst +++ b/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst @@ -141,17 +141,29 @@ checkbox. Why is translated content not available in TYPO3? ------------------------------------------------- -* The translated strings are not approved. As an owner of the Crowdin project - (for example, if you're the extension owner) or as proofreader you can approve - strings by yourself. Otherwise please ask in the Slack channel - `#typo3-localization-team `__ - for approval. With the next run of the Crowdin Bridge the translations - should be available (approx. every two hours). - -* Only translations provided from the following default branches in your - repository are used: `main`, `master`, `release`, `develop`, `dev`, - `development`. If you use other branches, the translations are not - available — even if they are translated in Crowdin. +Approval is missing +~~~~~~~~~~~~~~~~~~~ + +The translated strings are not approved. As an owner of the Crowdin project +(for example, if you're the extension owner) or as proofreader you can approve +strings by yourself. Otherwise please ask in the Slack channel +`#typo3-localization-team `__ +for approval. With the next run of the Crowdin Bridge the translations +should be available (approx. every two hours). + +Integration branch is not recognized +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +If the legacy Crowdin <> GitHub integration is used, only translations +provided from the following default branches in your repository are used: +`main`, `master`, `release`, `develop`, `dev`, `development`. If you use +other branches, the translations are not available — even if they are +translated in Crowdin. + +It is recommended to configure the +:ref:`GitHub workflow as integration for Crowdin `, +this way you define the `crowdin_branch_name` which can be set to +`main` — independently of your GitHub default branch. .. index:: Crowdin; Reconnect your project .. _reconnect-your-project: