#25397Adding XLIFF support as the default format for translation
Description
The goal of the project is to extend TYPO3 translation format support with XLIFF format.
This move is motivated by the lack of good tools to translate TYPO3. Translation team need advanced feature to manage their workload and improve TYPO3 translation quality. Actually we are impressed by the features of Pootle (use by LibreOffice, Mozilla, Gnome, …) and plan to use it as a replacement of llxmltranslate.
We are actually working in the TYPO3 core, on github. The current job is to move the existing feature to dedicated class (parsing llxml, llphp, …) and adding a sort of factory to switch between the correct parser.
https://github.com/dfeyer/git.typo3.org
You can check our test Pootle server here:
https://pootle.reelpeek.net/pootle/
And a quick and dirty tools to convert core llxml to XLIFF:
https://github.com/dfeyer/llxml2xliff
(issue imported from #M18040)
Reviews 7
- TYPO3_4-6 18264[BUGFIX] Allow "en" as language key
- main 17414[BUGFIX] Allow "en" as language key
- TYPO3_6-0 18262[BUGFIX] Allow "en" as language key
- main 2572[FEATURE] Add XLIFF translation support (l10n)
- TYPO3_4-7 18263[BUGFIX] Allow "en" as language key
- main 2930[FEATURE] New caching framework implementation for l10n
- main 2929[BUGFIX] Better check for the l10n method