[TYPO3-core] Translation 'en' missing

Jigal van Hemert jigal.van.hemert at typo3.org
Sun Nov 4 17:31:23 CET 2012


On 2-11-2012 11:52, Daniel Alder wrote:
>> Your idea that English labels should be made as a translation of the
>> description for translators is simply not the way things work in TYPO3.
> that exactly what i am here for. i do not agree that it's the way how
> typo3 should work. because it's just working since 4.6 in that way.

This is a mistake that is made often: if something happens to work which 
is not documented to work that way then it is not part of the official 
API and it is not guaranteed to work like that in the future.

There has always been an API to get labels in the current language, but 
quite a few extensions have been found to use the raw internal data. 
After the switch to XLIFF the internal structures were changed and the 
extensions were broken. If they would have used the official API 
functions there would not have been a problem.

> your right, there are other ways. but the l10n-mechanisem was one of the
> best ways for translations (for example if you want to put the languages
> under version control, have all translations in the same place and are
> save if the extension get updates). but this case we can't use anymore
> for english labels. so i have to use an other way just for english.

The extension llxmltranslate did indeed store the translations in the 
typo3conf/l10n directories. Unfortunately this is exactly the place 
where the downloaded translations also end up. The same location 
competing for downloaded and custom extensions is a bit of a challenge 
to me.

I'd let the typo3conf/l10n be used for downloaded translations and use 
the available options such as locallangXMLOverride or the TypoScript 
_LOCAL_LANG settings (which you can also store in files and thus you can 
have them in a versioning system) for your modifications or custom 

> so please tell me one more time why do you think 'en' shouldn't be
> woring as a language in l10n?

English is the default language and the base language for translations 
of labels. All English texts are already present in the core and in the 
extensions. I really can't see the use of storing these texts yet again 
as a "translation" into the same language.

Or could I interest you in buying an English-English dictionary? :-)

Jigal van Hemert
TYPO3 Core Team member

TYPO3 .... inspiring people to share!
Get involved: typo3.org

More information about the TYPO3-team-core mailing list