1)
_locales.php
-------------------------
$default_locale = 'ru-RU';
$locales = array(
'ru-RU' => array( 'name' => NT_('Russian (RU)'),
'charset' => 'windows-1251', ......
),
-------------------------
2) .../locales/ru_RU/_global.php in the "windows-1251'"
3) In the back-office in Russian locale "windows-1251" i see back-office :(
4) In the front front :(
if $evo_charset = 'windwos-1251';
Debug info:
locale:
* default_locale from conf: ru-RU
* default_locale from DB: en-EU
* default_locale from HTTP_ACCEPT: ru-RU
* Could not "SET NAMES cp1251"!
* evo_charset (_main.inc.php): windows-1251
* io_charset (_main.inc.php): windows-1251
* Activating blog locale: ru-RU
if $evo_charset = '';
locale:
* default_locale from conf: ru-RU
* default_locale from DB: en-EU
* default_locale from HTTP_ACCEPT: ru-RU
* Could not "SET NAMES cp1251"!
* evo_charset (_main.inc.php): windows-1251
* io_charset (_main.inc.php): windows-1251
* Activating blog locale: ru-RU
We've tried it together on another host, with a MySQL version (>= 4.1) which supports "SET NAMES", but the problem persisted: the text coming from DB is not cp1251 really.
I've fixed now a several things, which I'll commit later, but a single fix I've made, might help in your case:
Find function convert_chars in /inc/_misc/_misc.funcs.php and replace
with:
I wasn't aware a long time, that the characters have been replaced with entities in the source code.. :/