[TYPO3-dev] forceCharset = windows-1251 - do you plan to support this in Core?

[Valery Romanchev]

Hello

I see a lot of problems with

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

in TYPO3 4.0 with PHP5 and even with PHP4

1) PHP5 + windows-1251 -> major problem
This combination not works absolutly because of xml_parser in PHP5.

from  class.t3lib_div.php

// PHP5 fix of charset awareness:
   // Problem is: PHP5 apparently detects the charset of the XML file (or
defaults to utf-8) and will AUTOMATICALLY convert the content to either
utf-8, iso-8859-1 or us-ascii. PHP4 just passed the content through without
taking action regarding the charset.
   // In TYPO3 we expect that the charset of XML content is NOT handled in
the parser but internally in TYPO3 instead. Therefore it would be very nice
if PHP5 could be configured to NOT process the charset of the files. But
this is not possible for now.
   // What we do here fixes the problem but ONLY if the charset is utf-8,
iso-8859-1 or us-ascii. That should work for most TYPO3 installations, in
particular if people use utf-8 which we highly recommend.

So what to do:
- forget about PHP5
- forget about windows-1251 and use utf-8
(this is not good, because all wellknown sites in Russia use windows-1251)
- make patch  windows-1251-> utf-8 -> xml-parser -> utf-8 -> windows-1251
I am not sure that it is possible
- use othe  XML parset for PHP5  (DOM if I am not mistaken)


2) indexed_search store all data in utf-8 so this is ablosutle not possible
to see it in phpmyadmin

3) phpmyadmin not show correctly russian (this is phpmyadmin configuration
problem )

My questuon is:
waht is core-team plans on support of  'windows-1251' ?

Regards
Valery