A future for a translated TYPO3

I’ve been involved in translation TYPO3 core and selected extensions for a few good years by now. As a self employed consultant selling TYPO3 solutions in Denmark, it’s important to me that I can deliver a CMS where the focus is on getting content online, smooth and easy. TYPO3 is a good choice :smiley:
But TYPO3 will be much better, if it’s available in native language - especially for (chief) editors and for administrators to some extend. And as minimum TYPO3 Core and the most used Extensions.

Over the years my focus has been on core and extensions that I’m using on daily basis, either by customers or for my own projects.

The existing TYPO3 translation server suffer from a number of issues that makes it a bit troublesome to keep a good and safe workflow on the translation process.

In general, the translation server (https://translation.typo3.org) works okay, if you only need to translate or approve a small amount of labels. There is different filters, you can choose files, there is a good selection of short cuts, etc.

But on major translation work, trouble begins. There is a long list of obstacles to go through when working with major translations. It’s difficult to get an overview of what state the projects you’re working on are in, the Pootle server has many blackouts, and are in general slow, you can’t work offline, you can’t download files for testing, you have to paddle through many many obsoleted projects for find the important once

During the years, I’ve kept a little log on how I would like things should be. I’m also involved in translating other Open Source projects on CrowdIn and Transifex, and some smaller OS software projects here and there. I’m also a humble guy, so take the list as suggestions to how it could be, and not a criticism of the existing server:

Need to have:

  • Remove all current obsolete Extensions from the translation server
  • Remove all Extensions only supported by TYPO3 below v6.2
  • Download for local translation
  • Upload after local translation
  • Add new extensions to server by developer
  • Filters:
    ** My selections (things that I translate)
    ** Obsolete, TYPO3 versions
    ** Core / Extensions
    ** Finished
    ** Needs work
    ** Needs translation

Notification (mails) when things changes:

  • When new labels are added in core and extensions
  • When suggestions are made in core and extensions form “My selections”
  • When new extensions/projects are added

A (more) clear way to communicate:

  • Slack (as is)
  • Wiki on [docs.typo3.org]
    ** On each core element
    ** On each extension
    ** On Terminology
    ** On workflow, roles, translation rules, hoot, etc
    ** A page for each Language team, maintained by the team administrators
    ** Specifications for extension developers
  • Stackoverflow
  • Online meetings

Nice to have:
It would be great to integrate translation in TYPO3. A composer-installed version of a TYPO3 main version (7, 8, 9…) of own choice, where you can install and update the extensions from “My selection” and where you can translate labels directly in an overlay by selecting the labels as you walk through the extension. It would give good support in the understanding of features and the use of a given extension of core feature. The final translation can, after final work, be uploaded to the translation server.

Additional knowledge
Translation related channels in TYPO3 world:

Translation Team forge.typo3.org
TYPO3 Slack

There are probably other channels in use, but these tree should be the primaries.

Translation related ressources in TYPO3 community

[Localization — TYPO3 Explained main documentation]
[TYPO3 Documentation — Homepage of docs.typo3.org main documentation] (obsolete?)
[Localization — TYPO3 Explained main documentation] (obsolete?)
[TYPO3 Documentation — Homepage of docs.typo3.org main documentation] (obsolete?)

There are different kind of extensions aiming to support translators. Most of them are obsolete.
I think a more slim documentation based on docs.typo3.org would be a huge improvement. One door in.

Translation servers
The list is far from complete, but these are the solutions I’ve been working with. They all has pros and cons, and it would be good to do a more proper comparison.
TYPO3 uses Pootle with Translate Toolkit 1.13.0

Pootle: [http://pootle.translatehouse.org/] - newest version is 2.7.6 with Translate Toolkit 2.2.4
Trasifex: [https://www.transifex.com/] - used by many Open Source projects and with loads of features
CrowedIn: [https://crowdin.com/] - used by many Open Source projects and with loads of features

I’m willing to put some energy into this. I have a good understanding on TYPO3, I has some server knowledge and of course; I’m a Ninja in translation into Danish :wink:

Topic Initiator: Preben Rather Sørensen
Topic Mentor: ??

As recently I did quite some work with translating TYPO3 in Italian, I can say that I agree with, well, basically everything.

If I have to point out the problems that has been major for me:

  • keep the translation coherent. I mean, it is difficult to remember if everyone involved in the translation have always used the same terminology.
  • you almost translate everyting in “blind” mode: I mean that you don’t actually know where that label is actually used (sometimes it can be guessed) so you don’t have context.

I don’t know the other tools so I can’t say if a tool change is worth the effort.

It’s already possible to show the label names and file locations in the backend (to provide context). Available people would IMO be useful to create better documentation for translators and have additional manpower in administration of Pootle.
For the Dutch translations we first tried to fill the Terminology as much as possible. This is shown next to the label to help make the translation consistent.
I’ve been doing loads of translations in Pootle and I can’t say it’s complicated or slow.

We actually need more people to do translations, both for labels and for things like What’s new slides, tutorials and guides. Changing the tools yet again is not a huge priority for me.

This topic was automatically closed after 14 days. New replies are no longer allowed.