Project

General

Profile

Actions

Bug #53036

closed

no usage of external locallang.xlf

Added by d.ros no-lastname-given about 11 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
Start date:
2013-10-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I don´t know if this is still true in 6.2 alpha. Nor I don´t know if I am the problem.

But I set:

plugin.tx_femanager.view.layoutRootPath = fileadmin/template/ext/femanager/Resources/Private/Layouts/
plugin.tx_femanager.view.partialRootPath = fileadmin/template/ext/femanager/Resources/Private/Partials/
plugin.tx_femanager.view.templateRootPath = fileadmin/template/ext/femanager/Resources/Private/Templates/

where the Resources Folder is a 1:1 copy from extension path.

The locallang.xlf files are normally expected in ext:Resources/Private/Language

I didn´t find a option to switch the path for the locallang.xlf files.

Shouldn´t this be taken into account ?

Cheers

David

Actions #1

Updated by Alexander Stehlik about 11 years ago

The path is currently hardcoded in the \TYPO3\CMS\Extbase\Utility\LocalizationUtility class.

One workaround would be to prefix your translation keys with the path to your locallang file:

LLL:EXT:myext/mypath/mytranslation.xlf:my_translation_key

Or you could overwrite the TYPO3\CMS\Fluid\ViewHelpers\TranslateViewHelper class that will append the prefix automatically and reads the path from the plugin settings.

But of course it would be nice if the path could be modified somehow.

Actions #2

Updated by d.ros no-lastname-given about 11 years ago

Isn´t this a kind of fault by design ? IMHO this should be flexible because translation is for my understanding something template based.
BTW: shortly there was an issue done for template fallback handling. Same should be done in here.

cheers

Actions #3

Updated by Philipp Gampe about 11 years ago

IMHO that would need to go into Flow first? Did you check upstream?

Actions #4

Updated by Georg Ringer almost 10 years ago

  • Status changed from New to Rejected

Translations are always found in Resources/Private/Language/language.xlf. If you need to override those, either use a hook to overload the original files or better approach if you copy the templates anyway to add your own extensionKey to the TranslateViewHelper. You can also add the full path there as well if your templates are e.g. in fileadmin/.

Actions

Also available in: Atom PDF