Issue Bug Closed

#29248Cannot use own translation with XLIFF

Xavier Perseguers 08/25/11, 16:17 updated 01/26/13, 18:04

Description

XLIFF files contains the definition for a single language. Additional languages cannot be stored as when using ll-XML (locallang*.xml) files.

Those translations should be stored in

typo3conf/l10n/<langKey>/<extKey>/path/to/<langKey>.locallang*.xlf

instead.

If an extension developer wants to create a multilingual extension with XLIFF files, he has no other choice than using the official TYPO3 translation server to provide the corresponding translations. This is not realistic as the translation server is not intended to be used for each and every extension available on TER.

This patch allows translations to be stored next to the main language:

locallang.xlf
fr.locallang.xlf
de.locallang.xlf
locallang_db.xlf
fr.locallang_db.xlf

This has the side-effect of enabling this support for ll-XML as well.

As such, this could be backported to 4.5 and 4.4 as well. This would allow developers currently dealing with gigantic locallang*.xml files to split them (e.g., take EXT:seminar).

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.