Bug #53036
closed
no usage of external locallang.xlf
0%
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
Updated by Alexander Stehlik over 10 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.
Updated by d.ros no-lastname-given over 10 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
Updated by Philipp Gampe over 10 years ago
IMHO that would need to go into Flow first? Did you check upstream?
Updated by Georg Ringer over 9 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/.