Bug #29248: Cannot use own translation with XLIFF - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #29248

closed

Cannot use own translation with XLIFF

Added by Xavier Perseguers about 13 years ago. Updated almost 12 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)

Actions

Copy link

Updated by Xavier Perseguers about 13 years ago

File 29248.diff 29248.diff added

Actions

Copy link

Updated by Xavier Perseguers about 13 years ago

File 29248_T45_T44.diff 29248_T45_T44.diff added

Actions

Copy link

Updated by Mr. Hudson about 13 years ago

Patch set 1 of change If930350527077be33bdbeced9672f13793d1d8f4 has been pushed to the review server.
It is available at http://review.typo3.org/4601

Actions

Copy link

Updated by Xavier Perseguers about 13 years ago

Priority changed from Should have to Must have

Actions

Copy link

Updated by Xavier Perseguers about 13 years ago

Status changed from New to Under Review

Actions

Copy link

Updated by Mr. Hudson about 13 years ago

Patch set 1 of change I57dc8f359395f0da53a6bc7977ceb3554273946d has been pushed to the review server.
It is available at http://review.typo3.org/4650

Actions

Copy link

Updated by Mr. Hudson about 13 years ago

Patch set 2 of change If930350527077be33bdbeced9672f13793d1d8f4 has been pushed to the review server.
It is available at http://review.typo3.org/4601

Actions

Copy link

Updated by Xavier Perseguers about 13 years ago

To test, you can checkout https://svn.typo3.org/TYPO3v4/Extensions/egovapi/trunk (just load in extList without creating the DB structure), reference the "eGov API settings" static TS in your template and use Constant Editors section PLUGIN.TX_EGOVAPI.

In master, if you use a backend in French, German or Italian, you will only have English texts, apply patch and see nearly all messages translated in the corresponding language.

Make sure to use patch from Gerrit (review.typo3.org).

Actions

Copy link