TYPO3 XLIFF for Extension Development¶
Since TYPO3 4.5 it’s possible to use the new XLIFF-Format for translation. There is a very nice article about the differences and usage in the internet. Take a look at it. After reading I had some more question. I’ll try to answer them now in this post.
Without XLIFF you just wrote the following line to use an label from the old locallang-files:
'title' => 'LLL:EXT:' . $_EXTKEY . '/Resources/Language/locallang.xml:label',. But what do you
need to write now? It’s the same line with one change:
'title' => 'LLL:EXT:' . $_EXTKEY .
'/Resources/Private/Language/locallang.xlf:label',. You just have to change the format from
xml, or php, to xlf. That’s it. Fine, you now should see your label in the default language,
but what’s with the other languages?
Each language has to be in it’s own file like described in the blogpost. But how do you reference to them? You don’t. It’s that easy, you just have to name the files in the right way and you’re done. For example if you want to provide a german translation for your english default language, you just have to add a file called de.locallanx.xlf inside the same folder you created your locallang.xlf. TYPO3 will fetch this file. You don’t have to change anything inside your php-code.
If you are ever wondering why your changes aren’t applied, just clear the cache. Your locallang-files are cached!
Checked for TYPO3 Versions¶
The post was checked against TYPO3 versions 4.5 up to 8 LTS.