Re-Entry from Q1/2025: TYPO3 AI Localization with Crowdin Integration

[ischmittis (Ingo Schmitt)]

We have asked all Q1 participants, if their idea should be re enter the Q2 poll. @nitsan
agreed to reenter his idea. Please see all details at the original submission:

TYPO3 AI Localization with Crowdin Integration

A proof of concept extension has been presented to the TYPO3 Localization Team today by Sanjay Chauhan from Nitsan. The extension is working and the usability for the backend users is easy. The translation results can be edited/proofread and then be stored locally and optionally transfered to Crowdin, the official TYPO3 translation handling tool. The tool will not only work with TYPO3 Core but any extension available in Crowdin or outside. We have not yet been able to assess the quality of the…

[pkraume (Peter Kraume)]

The feedback of the TYPO3 Localization Team which I posted for the initial budget request last year is still valid:

TYPO3 AI Localization with Crowdin Integration

A proof of concept extension has been presented to the TYPO3 Localization Team today by Sanjay Chauhan from Nitsan. The extension is working and the usability for the backend users is easy. The translation results can be edited/proofread and then be stored locally and optionally transfered to Crowdin, the official TYPO3 translation handling tool. The tool will not only work with TYPO3 Core but any extension available in Crowdin or outside. We have not yet been able to assess the quality of the…

The Localization Team will support and promote this solution, but not as the one and only official solution. There are also other tools such as the web interface, XLF upload, EXT:crowdin, etc.
So it’s up to the translators to evaluate the pros and cons of each solution and choose the one that suits them best.

[nitsan (Sanjay Chauhan)]

Hey Peter,

Thanks for your feedback and for sharing the team’s perspective. I appreciate the constructive discussion around TYPO3 localization and the role different tools play in this ecosystem.

Our initiative with AI-powered localization is meant to complement, not replace, existing solutions like the web interface, XLF uploads, and EXT:crowdin. We understand and fully support the idea that translators should have the freedom to choose the best tool that suits their workflow.

Right now, we’ll wait for the results of the TYPO3 Association vote. Based on the outcome, we’ll determine the next steps and explore how this initiative can best serve the community alongside other localization tools.

Looking forward to further collaboration and making TYPO3 more accessible across languages.

Cheers,
Sanjay