Task #31039

workspaces: English XLIFF files should not contain target element

Added by Xavier Perseguers over 9 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Must have
Category:
Workspaces
Target version:
-
Start date:
2011-10-18
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Currently the XLIFF files provided with the Core are "en" -> "en" translation files,
and this is a wrong design.

English localization files should only contain the source attribute to become templates for the different localizations.

The command use to process all the file, is xmlstarlet:

xmlstarlet ed -u "/xliff/file[@date]/@date" -v $(date -u +"%Y-%m-%dT%H:%M:%SZ") file.xlf | \
xmlstarlet ed -d "/xliff/file/body/trans-unit/target" | \
xmlstarlet ed -d "/xliff/file[@target-language]/@target-language" | \
xmlstarlet ed -d "/xliff/file/body/trans-unit[@approved]/@approved" | \
xmlstarlet ed -u "/xliff/file[@source-language]/@source-language" -v en |
xmlindent -t

Related issues

Follows TYPO3 Core - Task #30916: Transform the current en->en XLIFF file to template fileClosedDominique Feyer2011-10-14

Actions

Also available in: Atom PDF