[TYPO3-core] RFC #29248: Cannot use own translation with XLIFF

Xavier Perseguers xavier at typo3.org
Thu Aug 25 16:30:45 CEST 2011


Hi,

Using this list again because I'd like to start the discussion whether 
it makes sense to backport it (or not). It can be seen as a feature, I 
see it since ages as a bad behaviour of TYPO3...

Type: Bug (in master), BadBehaviour/Feature (in 4.4, 4.5)

Bugtracker reference:
http://forge.typo3.org/issues/29248

Branches: 4.5, 4.4 (master shall not be discussed here)

Problem:
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.

Solution:
Allow translations to be stored next to the main language:

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

Note:
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).

Note 2:
Description is taken from bug tracker, references to XLIFF do not make 
sense in the context of 4.5 and 4.4 but this way you have a clear 
understanding of why this patch is a bugfix for master and not a new 
feature (except for the side-effect, I agree).

Note 3:


Kind regards

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

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

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 29248_T45_T44.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20110825/cd394c4b/attachment.txt>


More information about the TYPO3-team-core mailing list