[TYPO3-core] RFC #11571: Feature: tslib_pibase - function pi_loadLL - _LOCAL_LANG Keys like listView.more should also be possible in Typoscript

bernd wilke t3ng at pi-phi.tk
Thu Aug 12 21:22:13 CEST 2010


Am Thu, 12 Aug 2010 18:41:41 +0200 schrieb Steffen Kamper:

> Hi,
> 
> Gosign | Caspar Stuebs schrieb:
>> 
>> I completely agree that we should force to use another seperator for
>> the locallang labels. But for this we should also update all files
>> within the core, including the kickstarter.
>> I would use '|'.

little misunderstanding.
I thought a way to replace the dots used in the indexkeys in typoscript:
e.g. use 
plugin.tx_my_extension_pi1._LOCAL_LANG.de.selection:I:1 = auswahl 1
instead of 
plugin.tx_my_extension_pi1._LOCAL_LANG.de.selection.I.1 = auswahl 1
(which will not work)
for translation of
<label index="selection.I.1">selection 1</label>

the optimal long time solution would be to avoid any dots in the 
indexkeys of any locallang-file and I think the first change has to be 
the kickstarter. 
As a readable character the kickstarter should use I would prefer '_' 
underscore as it is common to everyone as 'alphabetic character', also 
(nearly) any ASCII character is usable. I suppose 8bit-ASCII/UTF will 
have problems too.

up to then a support for all that users which want/have to redine a label 
in TS should be given as we can't remove all that dots from all that 
indexkeys in all extensions.

is this constraint (trap?) mentioned in the CGL (I have not found it)?
why should an extension developer be punished with this caveat?
 
>> I have created another patch, which adds a check for dots in the keys
>> to t3lib_div::readLLfile() and then adds a deprecation log entry. I
>> also marked the new function getSupportForDotsInLocallangLabels() as
>> deprecated.
>> 
>> But maybe this topic should be moved to dev list ?!?
>> 
>> 
> don't forget - we are talking about FE extensions. The core labels are
> not relevant here.
> 

can you redefine those core-labels for editor(groups) with typoscript?

shouldn't we have a unique system of label keys for FE and BE instead of 
forbid some chars for FE for the special handling of translation/
redefinition in TS?


bernd
-- 
http://www.pi-phi.de/cheatsheet.html


More information about the TYPO3-team-core mailing list