Project

General

Profile

Actions

Bug #27950

closed

l10n: localizations in extension llxml-files are not respected

Added by Björn Pedersen almost 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Miscellaneous
Target version:
-
Start date:
2011-07-07
Due date:
% Done:

0%

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

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 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #27972: LLXML Parser does not support localized label in the main LLXMLClosedDominique Feyer2011-07-08

Actions
Actions #1

Updated by Björn Pedersen almost 13 years ago

Extension for test:
tx_frm2newpm (in the repository)

Actions #3

Updated by Björn Pedersen almost 13 years ago

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

Actions #4

Updated by Xavier Perseguers almost 13 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF