Project

General

Profile

Actions
Copy link

Bug #29248

closed

Cannot use own translation with XLIFF

Added by Xavier Perseguers over 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Xavier Perseguers
Category:
-
Target version:
4.6.0-beta2
Start date:
2012-09-04
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
TYPO3 Version:
4.6
PHP Version:
5.2
Tags:
Complexity:
easy
Is Regression:
Sprint Focus:

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

Files

Download all files
29248.diff (4.74 KB) 29248.diff Xavier Perseguers, 2011-08-25 16:21
29248_T45_T44.diff (2.28 KB) 29248_T45_T44.diff Simplified version for TYPO3 4.5 and 4.4 Xavier Perseguers, 2011-08-25 16:31

Subtasks

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #29313: Externally referenced ll-XML files are not parsedClosedXavier Perseguers2011-08-29

Actions
Actions
Copy link

Also available in: Atom PDF