• TYPO3 Core can be translatable supporting various branches
• The translations of TYPO3 Core are downloadable via the Maintenance Area in TYPO3 Backend
• Extension authors can localize their extensions on Crowdin using the same Translation Memory as TYPO3 Core
• The translations of TYPO3 Extensions are downloadable via the Maintenance Area in TYPO3 Backend
• Both translation for TYPO3 Core and extensions can be updated through Scheduler
• The In-Context localization is integrated into TYPO3 Core.

Crowdin’s glossary is being filled with terms which are often used and might need an additional explanation. Examples are strings like “ Constants”, “SEO”, “Page Template”, “TypoScript Template”. It needs to be clear for every translator how those terms are translated.

Extensions can be localizable with Crowdin. The project (each extension at Crowdin is called project) is created manually but the translations can already be downloaded within the System Maintenance Area.In-Context localization is integrated.

Extension authors can decide to have their extension on Crowdin and the project is setup automatically and connected to the CVS of the extension.

Coming up with a solution to avoid having duplicates for general fields over and over again for strings like “Title” or “Description” - not only for the core but also for extension authors. Even though the Translation Memory (TMS) is very useful during translation there shouldn’t even be required to have a custom label.

The feature-richness of Crowdin can be used to attract and support new maintainers, e.g. by providing Screenshots of the Backend showing where the translations are actually used.