+49 (0)5583 2829973 info(at)coders(dot)care

How we should rethink TYPO3 translation handling

Set the course for the future of multilingualism in TYPO3 with us. We want to hear your point of view, your wishes but also your problems and together we will think about what solutions we will need. Visit our workshop at the TYPO3 Developer Days or send us your story by email, so that multilingualism in TYPO3 will be even better with the next versions.

Estimated time to read: 4 minutes

Multilingual TYPO3

the reliable workhorse

TYPO3 has traditionally been well known for its special strengths in terms of multilingualism. Both the backend, which has already been translated into many languages, and the possibilities for frontend output of translated content are seeking their equal in the world of content management systems, even outside the open source community. Based on the multilingual functions of the TYPO3 core, there are additional extensions such as the L10nmanager or the Localizer, which can be used to additionally connect the APIs of professional translation service providers to TYPO3.

Self improvement

to be future proof

Nevertheless, there is of course always room for improvement and therefore the functions for internationalization (I18N), localization (L10N) and translation (T9N) in TYPO3 are always evolving. At the TYPO3 Conference 2016, there was already a talk on this topic "Quo Vadis TYPO3" by Daniel Zielinski from the company Loctimize and me, in which, among other things, the concepts and improvements developed during the TYPO3 User Experience Week were presented. Basic concepts are so-called Language-IDs, the two modes "Connected" and "Free" for the connection between records in source and target language, as well as additional settings for the so-called "Fallback", if records in the target language are not available.

Sufficient concepts

but are they?

Up to now, these concepts were sufficient to implement most of the tasks in the multi-language support of TYPO3 projects, but in recent years there has been increasing criticism of the approach. At the TYPO3-Camp Mitteldeutschland in Dresden, there was a session on this topic by Eric Bode with the aim of finding new ways for an improved and standardized implementation, which in particular solves the problems that can occur with the current approaches again and again. One result of this session is a discussion on decisions.typo3.org, where Eric shared his ideas with other interested people and already got first feedback.

The workshop

we want your input

Based on these valuable insights, Eric and I want to hold a workshop together with Benni Mack during the TYPO3 Developer Days in Karlsruhe, where you will have the opportunity to tell us about your tasks, their solutions but also their problems in your daily work with TYPO3 translation processes. If you are not able to attend this workshop, you are welcome to send us corresponding descriptions and requests to info(at)coders(dot)care, so that we can include them in the results of the workshop.

All results will be presented in a summary in a further session during the Developer Days and will then be incorporated into the development of the new concepts. We are looking forward to a lively participation and see you in Karlsruhe.

Jo Hasenau