TYPO3 Core

String should not be changed back to english version!

Problem happens if UTF-8 is NOT used for BE charset. Translation's character set is correct (utf-8).

On this site I use:

$TYPO3_CONF_VARS["BE"]["forceCharset"] = 'windows-1251';

So how I can solve this problem withouth changing back to English?
Do you confirm that this is bug?

Well, you should use utf-8, not windows-1251...

But this is a bug. It should be fixed but word should not be changed back to English.

Bug is in /typo3/sysext/version/class.tx_version_cm1.php line 80:
"$GLOBALS['LANG']->getLLL('title',$LL),"
should be changed to
"$GLOBALS['LANG']->makeEntities($GLOBALS['LANG']->getLLL('title',$LL)),"

Fixed file in attacment.

BTW, I suggest to change names from "Versionniy kontol" and "Versioning" to "Kontrol versiy". It's more look like Russian... 8=)

Hi,
it might be that this relates to the ajax clickmenu... Not sure though, I am no expert in charsets.
Greets, Sebastian

I just look at source code. The bug was not corrected in 4.0.3rc1 and in 4.1beta1

I confirm that this solution works fine for 4.0.2 :
---------------------------------
Bug is in /typo3/sysext/version/class.tx_version_cm1.php line 80:
"$GLOBALS['LANG']->getLLL('title',$LL),"
should be changed to
"$GLOBALS['LANG']->makeEntities($GLOBALS['LANG']->getLLL('title',$LL)),"
--------------------------------
Please note that the bug exists for situation
$TYPO3_CONF_VARS["BE"]["forceCharset"] = 'windows-1251';
and probably for some other encoding too.

Hi Valery,

are you sure that the bug is not fixed in 4.0.3rc1? Actually I am quite sure that this was solved, as it seems to be exactly the same problem that others had with German Umlauts.

Please clear your cache and test it once again, thanks.

See bug #15979 for more information!

Many thank for fast reply
Sorry for my mistake

Now I confirm that the bug is fixed in 4.0.3rc1

Perfect, so I mark this issue as a duplicate of #15979.