Task #31044

English XLIFF files should not contain target element

Added by Xavier Perseguers over 9 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Must have
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2011-10-18
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
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
#1

Updated by Mr. Hudson over 9 years ago

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

#2

Updated by Xavier Perseguers over 9 years ago

  • Status changed from New to Under Review
#3

Updated by Xavier Perseguers over 9 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#4

Updated by Michael Stucki about 7 years ago

  • Project changed from DBAL to TYPO3 Core
#5

Updated by Michael Stucki about 7 years ago

  • Category set to 999
#6

Updated by Riccardo De Contardi about 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF