[TYPO3-english] Problems with locallang.xml translation since 4.6
Sören Kracker
s.kracker at kopfstand-mail.de
Wed Jan 18 17:28:17 CET 2012
This shouldn't be forgotten. Imho this is a big problem when using
multiple languages.
There has been no reaction to my bug report. Has nobody else noticed
this bug?
Am 15.12.2011 16:08, schrieb Sören Kracker:
> You didn't mean testing on 4.6.0 or?
> I tested on 4.6.1 and it makes no difference there.
>
> Am 15.12.2011 15:24, schrieb Dominique Feyer:
>> And before further work on this issue, please can you try this:
>>
>> 4.6 introduce a caching mechanism for the l10n parser (based on the
>> caching framework).
>>
>> Add this line in your localconf.php
>> $GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['cache']['clear_menu'] =
>> TRUE;
>>
>> Clear configuration cache and reload the backend, you now have a new
>> item in the clear cache menu to clear the l10n cache.
>>
>> After that reload your frontend.
>>
>> Please do that on a vanilla 4.6 (without patch).
>>
>> Keep me in touche with the result.
>>
>> On a local setup of the 4.7 I override en key, with
>> $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['typo3/sysext/lang/locallang_core.xml'][]
>>
>> = 'fileadmin/locallang_core.xml';
>>
>> And my english string are used (not the default key from the lang
>> extension).
>>
>> Sören Kracker wrote:
>>> Thanks Dominique,
>>> I've filed a bug report:
>>> http://forge.typo3.org/issues/32590
>>>
>>> Am 15.12.2011 12:04, schrieb Dominique Feyer:
>>>> In 4.6 en === default it's not a bug currently but I understand your
>>>> needs and it make sense to change that.
>>>>
>>>> Can you please open a bug on the forge issue tracker ?
>>>> http://forge.typo3.org/projects/team-translation/issues
>>>>
>>>> Thanks
>>>>
>>>> Sören Kracker wrote:
>>>>> I can't get any other translations than default and de in 4.6.
>>>>> This all
>>>>> worked in 4.5!
>>>>> This is really strange, because the content gets translated correctly
>>>>> (so language is set properly), but translations using locallang.xml
>>>>> don't work. Neither locallang of extensions (formhandler or
>>>>> overriding
>>>>> via $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride'] ) nor
>>>>> translations via typoscript (using LLL:translation.xml:string) are
>>>>> working. TYPO3 finds the xml files and fetches default strings and
>>>>> those
>>>>> for de too, but for en I always get the default translation.
>>>>> Is there any change regarding XLIFF? I have absolutely no idea what's
>>>>> wrong here.
>>>> _______________________________________________
>>>> TYPO3-english mailing list
>>>> TYPO3-english at lists.typo3.org
>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>> _______________________________________________
>> TYPO3-english mailing list
>> TYPO3-english at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
More information about the TYPO3-english
mailing list