ID: 38138 Comment by: dennis at nikolaenko dot ru Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Feature/Change Request PHP Version: 4.4.2 New Comment:
I also bumped into this, just voting. Previous Comments: ------------------------------------------------------------------------ [2006-07-20 07:04:21] [EMAIL PROTECTED] I would like to if anybody will explain "how to" port PHP functions into Unicode "for dummies". It will also be nice to see an environment to monitor the changes (?trac) and control requirements. The last one is to help analyze deprecated, inconvenient and obscure API - logical bugs - to provide means to increase usability. Like unify inlcude_path delimiters on all platforms etc. It is just to save some time and make occasional development (which I am pretty restrained to) effective. ------------------------------------------------------------------------ [2006-07-20 06:27:56] [EMAIL PROTECTED] >I evaluated PHP6 for a few days, but it was very far from >being complete, unfortunately. I wonder why.. probably because it's still 12+ months before the release? =) Feel free to help us, though. The documentation is not the only area that needs some help =) ------------------------------------------------------------------------ [2006-07-19 17:34:30] [EMAIL PROTECTED] Well, i can't say this is ok for me. At first I thought that simple configure with --enable-mbstring=all should solve the problem, but it appeared that my host of dream already has this option turned on. So autodetection of russian language is just not enabled on code level, i.e. i18n support via mbstring is somehow crippled. I evaluated PHP6 for a few days, but it was very far from being complete, unfortunately. ------------------------------------------------------------------------ [2006-07-19 09:50:33] [EMAIL PROTECTED] Reclassified as feature request, where it belongs. techtonik, I'm sure you know email addresses of ext/mbstring maintainers and can contact them about it. Although, I don't think this will ever appear in PHP6 (because mbstring itself doesn't make much sense there) and it definitely won't appear in PHP4 (it's time to upgrade, eh?). ------------------------------------------------------------------------ [2006-07-19 09:41:58] [EMAIL PROTECTED] Description: ------------ Detection of russian encoding in mb_detect_encoding is disabled although it present among the list of supported encodings. It just three rather simple encodings - windows-1251, cp866 and koi8-r that spoil everyday life routines of russian programmer and make PHP less attractive for millions of potential PHP developers. I'll be grateful if somebody will care about them by providing default option for hosting providers, who are not too enthusiastic to experiment with server-wide configuration. Reproduce code: --------------- <?php $str = "Íà÷àòà ðàáîòà íàä ðàçðàáîòêîé ñòðàíè÷êè ïðîåêòà. Êîä ñàéòà ñîäåðæèòñÿ â ìîäóëå farplugins íà CVS. Ñâåäåíèÿ îá îøèáêàõ è ïðåäëîæåíèÿ ìîæíî îñòàâëÿòü â òðýêåðàõ â êàòåãîðèè project website èëè â ñïèñêå ðàññûëêè farplugins-devel."; // $encoding = mb_detect_encoding($str, "UTF-8, Windows-1251, CP866, KOI8-R"); $encoding = mb_detect_encoding($str, array("UTF-8", "Windows-1251", "CP866", "KOI8-R")); var_dump($encoding); Expected result: ---------------- string(12) "Windows-1251" Actual result: -------------- bool(false) ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=38138&edit=1