Bug #29248
closed
Cannot use own translation with XLIFF
100%
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
Subtasks
Updated by Xavier Perseguers over 12 years ago
- File 29248_T45_T44.diff 29248_T45_T44.diff added
Updated by Mr. Hudson over 12 years ago
Patch set 1 of change If930350527077be33bdbeced9672f13793d1d8f4 has been pushed to the review server.
It is available at http://review.typo3.org/4601
Updated by Xavier Perseguers over 12 years ago
- Priority changed from Should have to Must have
Updated by Xavier Perseguers over 12 years ago
- Status changed from New to Under Review
Updated by Mr. Hudson over 12 years ago
Patch set 1 of change I57dc8f359395f0da53a6bc7977ceb3554273946d has been pushed to the review server.
It is available at http://review.typo3.org/4650
Updated by Mr. Hudson over 12 years ago
Patch set 2 of change If930350527077be33bdbeced9672f13793d1d8f4 has been pushed to the review server.
It is available at http://review.typo3.org/4601
Updated by Xavier Perseguers over 12 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).
Updated by Xavier Perseguers over 12 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Change has been successfully cherry-picked as c7118c7eb30695d5649e417adba19f9c96651ffb.
Updated by Xavier Perseguers about 12 years ago
- Status changed from Resolved to Closed
Updated by
Updated by Francois Suter over 11 years ago
This should be documented.
I agree. The right place would be Core API. Xavier, could you report this here: http://forge.typo3.org/projects/typo3v4-doc_core_api/issues ? Thanks.
Updated by Xavier Perseguers over 11 years ago
done. thanks to both of you for pointing out.