[TYPO3-mvc] l10n_parent or l18n_parent ?

[Stefano Cecere]

Hi kevin!

waht an "old" topic..any way it was fixed some time ago in Extension  
Builder (which uses the correct l10n :)




On Tue, 20 Dec 2011 17:25:19 +0100, Kevin Ulrich Moschallski  
<km at 3digit.de> wrote:

> Hi Stefano,
>
> i stumbled upon your post as i also noticed that everywhere in the core  
> and many other extensions L18N is used and not I18N. I couldn't find any  
> codeing guidelines regarding this field name. Maybe someone knows if  
> there's a reason why it's L18N and not I18N or why it's not L10N  
> anymore, i still can't figure out if it's more an internationalization  
> or a localization here.
>
> Regards,
> Kevin
>
> On 2011-02-16 17:47:40 +0000, Stefano Cecere said:
>
>> i dont' know how it's important, but "classic" kickstarter was creating
>> translation fields
>>  l10n_parent
>> l10n_diffsource
>>  but the extbase kickstarter uses
>>  l18n_parent
>> l18n_diffsource
>>   i see that all TYPO3 core tables are using l18n
>>  anyway "L"18n is wrong... it should be at least i18n  
>> (internationalization)
>> L is ok for 10: l10n (localization)
>>  any idea?
>>  i guess extbase kickstarted should start using the right l10n_ suffix
>> (the variable is defined in the TCA, so we can choose freely)
>>          'transOrigPointerField'    => 'l10n_parent',
>>          'transOrigDiffSourceField' => 'l10n_diffsource',
>>   what do you think?
>>  stefano
>
>


-- 
____    ___   __  _ ______________________

   Stefano Cecere
   KRUR studio