Bug #27950

l10n: localizations in extension llxml-files are not respected

Added by Björn Pedersen about 4 years ago. Updated about 4 years ago.

Status:Closed Start date:2011-07-07
Priority:Must have Due date:
Assigned To:- % Done:

0%

Category:Default Spent time: -
Target version:-
TYPO3 Version:4.6 Is Regression:
PHP Version: Sprint Focus:
Complexity:

Description

If you have more then one language in an extension llxml-file, only the default language is used. This results in wrong labels.

I tracked it down to this code in tx_lang_parser_llxml.php:

public function getParsedTargetData($path) {
if (!isset($this->parsedTargetFiles[$path])) {
$this->parsedTargetFiles[$path] = $this->parseXmlTargetFile($path);
}
return $this->parsedTargetFiles[$path];
}
In this use case, $path is <extpath>/locallang.xml for both default language and additional languages.

A workaround is to move the labels to a file in typo3conf/l10n as the language packs from translation server do.


Related issues

duplicates Core - Bug #27972: LLXML Parser does not support localized label in the main... Closed 2011-07-08

History

#1 Updated by Björn Pedersen about 4 years ago

Extension for test:
tx_frm2newpm (in the repository)

#3 Updated by Björn Pedersen about 4 years ago

fixed in master now. See http://forge.typo3.org/issues/27972

#4 Updated by Xavier Perseguers about 4 years ago

  • Status changed from New to Closed

Also available in: Atom PDF