Project

General

Profile

Actions
Copy link

Feature #56953

closed

custom locallang.xml

Added by David Bruchmann over 10 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Extbase
Target version:
9.0
Start date:
2014-03-16
Due date:
% Done:

0%

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

Description

Using a custom locallang.xml with any extension on the first view looks like a feature-request.
As some translations maybe required but not present it's more than that: it's a bug.

Ok, what it is about now in detail?
For an extension (news) even already translated in many languages I need another translation and I never get it running without changing the locallang.xml in the extension itself.
I know, there must be a way how to do it without changes at extension or extbase but that's still not the issue.

The Issue is that the path to the default locallang.xml always is hardcoded and can't be overriden by configuration. So any other translation file will overwrite the values, it won't be loaded instead but additionally.

         static protected function initializeLocalization($extensionName) {
                 if (isset(self::$LOCAL_LANG[$extensionName])) {
                         return;
                 }
                 $locallangPathAndFilename = 'EXT:' . t3lib_div::camelCaseToLowerCaseUnderscored($extensionName) . '/' . self::$locallangPath . 'locallang.xml';
         ...

I wish a solution by configuration:

if (!$someConfigPath){
$locallangPathAndFilename = 'EXT:' . t3lib_div::camelCaseToLowerCaseUnderscored($extensionName) . '/' . self::$locallangPath . 'locallang.xml';
} else {
$locallangPathAndFilename = $someConfigPath.'locallang.xml'; // i.e. fileadmin/whatever/locallang.xml
}
Actions
Copy link

Also available in: Atom PDF