Feature #25397: Adding XLIFF support as the default format for translation - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues

Watchers (4)

Karsten Dambekalns
Karsten Dambekalns
Laurent Cherpit
Xavier Perseguers

Actions

Copy link

Feature #25397

closed

Adding XLIFF support as the default format for translation

Added by Dominique Feyer about 13 years ago. Updated almost 11 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Target version:

Start date:

2011-06-24

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

PHP Version:

5.3

Tags:

Complexity:

Sprint Focus:

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)

Files

l10n.tar.gz (15.6 MB) l10n.tar.gz

Language Pack for testing XLIFF support

Dominique Feyer, 2011-06-07 23:09

Subtasks 3 (0 open — 3 closed)

Task #27673: Add Parser for PHP locallang array

Closed

Xavier Perseguers

2011-06-24

Actions

Bug #27923: locallangXMLOverride hook has been removed

Closed

Xavier Perseguers

2011-07-06

Actions

Bug #28264: Wrong check for existance of translated label

Closed

2011-07-17

Actions

Related issues 3 (0 open — 3 closed)

Related to TYPO3 Core - Bug #27928: htmlArea RTE: Localization is broken in master

Closed

Stanislas Rolland

2011-07-07

Actions

Related to TYPO3 Core - Bug #27972: LLXML Parser does not support localized label in the main LLXML

Closed

Dominique Feyer

2011-07-08

Actions

Related to TYPO3 Core - Bug #28086: Disable clear lang cache by default

Closed

Dominique Feyer

2011-07-11

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Karsten Dambekalns about 13 years ago

Just chiming in to say this has full support from the Phoenix and FLOW team, as we use XLIFF as default format as well, and Pootle was the translation server of choice as well. :)

Actions

Copy link

Updated by Dominique Feyer almost 13 years ago

File l10n.tar.gz l10n.tar.gz added

I just attach some XLIFF file to test the parser. The language pack contain LLXML + XLIFF

Actions

Copy link

Updated by Steffen Gebert almost 13 years ago

Hints for reviewing the changes by Dominique:

First public version of the parser to support XLIFF + LLXML file as localization file format.

This patch includes:

- A parser factory to support multiple internationalization formats (actually LLXML and XLIFF,
parser for PHP array is not implemented yet). New parsers can be added in the future.
- A new parser for XLIFF (supporting plurals, based on the parser of FLOW3)
- Autoload for sysext 'lang'
- Update the existing localization method (FE, BE, Extbase) to support the new format
of the LOCAL_LANG array
- New caching class based on the caching framework or file based
- Autodetection igbinary for cache un/serialization
- htmlArea RTE: update of the localization API

Currently the localization method works as before (only key-based localization).

More functionality will be implemented in the new localization API (plurals, ...). The current
parser can be used on a TYPO3 instance with LLXML and/or XLIFF files. However if an extension
uses XLIFF, the language pack (typo3conf/l10n) MUST use the same format.

The parser and the format priority (by default: xlf, xml, php), can be configured in:

$TYPO3_CONF_VARS['SYS']['lang']

Beware: This patch breaks internationalization of many ExtJS based extension (like extension
manager, workspace, recycler). This bug shows "Object" as label. Another patch will be pushed
with a new ExtJS API to handle it, and extension update will be needed to fix this breaking
change.

If you see "Object" as label in rtehtmlarea, please clear the cache of the RTE and reload
your backend.

Actions

Copy link