[TYPO3-project-4-3] Why is contextmenu slow?

[Ernesto Baschny [cron IT]]

Hi,

no default is still language-dependent charset (iso-8859-1 for germany
for example). This requires lots of utf-8 conversions, since all
resources are stored in utf-8 (e.g. labels etc).

So in any production site I would recommend setting forceCharSet to utf8.

The "new installer" once we have something like that will probably also
set this as the "new default". And also it should auto-detect your
mb_stirng configuration. But for now we have to manually set it.

Cheers,
Ernesto

Dan Osipov schrieb:
> No, its blank by default. Shouldn't it be set to utf-8 from the start?
> 
> Dan Osipov
> Calkins Media
> http://danosipov.com/blog/
> 
> Ernesto Baschny [cron IT] wrote:
>> Dan Osipov schrieb:
>>> I'm using a default installation, straight from the trunk.
>>
>> even you need to configure how TYPO3 will do encodings/decodings. If you
>> have the mb-lib enabled in your PHP (and you should...), enable in the
>> install tool for TYPO3 to use use mb_string. It should be much faster
>> than the PHP-based version provided with TYPO3 as a fallback.
>>
>> Do you have forceCharSet set to utf-8?
>>
>> Cheers,
>> Ernesto
>>
>>> Dan Osipov
>>> Calkins Media
>>> http://danosipov.com/blog/
>>>
>>> Dmitry Dulepov wrote:
>>>> Hi!
>>>>
>>>> Dan Osipov wrote:
>>>>> I ran a quick profile test, and it looks like a lot of time is
>>>>> spent in
>>>>> t3lib_cs, specifically the utf8_encode function. By itself its not a
>>>>> problem, but the lines in the for loop are called ~12000 times for a
>>>>> single click menu (!!). Can some confirm?
>>>> Did you enable mb_string in the Install tool?
>>>>
>>>> Better would be to use UTF-8 in BE. There is no real reason for any
>>>> other encoding these days :)
>>