Bug tracker

This ticket has been moved to our new tracker. Open Ticket PHPBB3-2375 now.

No Japanese word match in search.php page (fix completed in vcs)

I tried to search Japanese word "てすと" in search.php page, but returned "No suitable matches were found.". The Japanese word "てすと" had been already posted as both topic title and topic messege.

I tested in local host. The php.ini setting "mb_internal_encoding" is EUC-JP, not UTF-8. I'm aware that it is the cause. In fact, when I add "php_value mbstring.http_output UTF-8" into .htaccess, the problem never occurs.

I think it is better to add "php_value mbstring.http_output UTF-8" into .htaccess for this problem. Forthermore for all user who use mbstring module, I think it is better to add following sentences into .htaccess.
php_flag output_buffering Off
php_value default_charset UTF-8
php_value mbstring.language neutral
php_flag mbstring.encoding_translation On
php_value mbstring.http_input auto
php_value mbstring.http_output UTF-8
php_value mbstring.internal_encoding UTF-8
php_value mbstring.substitute_character none
php_value mbstring.func_overload 0

Especially I think "php_value mbstring.func_overload 0" is important and necessary for e-mailing.

Is'nt it impossible to have added above sentences into .htaccess file as download package? I would be happy if dev team granted my wishes.

Comments / History

Posted by ocean=Yohsuke (Translator) on Nov 30th 2006, 03:01

mmm...Japanese characters greeking ;_;

Posted by ocean=Yohsuke (Translator) on Nov 30th 2006, 03:20

sorry, I have misdescribed...

x --- In fact, when I add "php_value mbstring.http_output UTF-8" into .htaccess, the problem never occurs.
o --- In fact, when I add "php_value mbstring.internal_encoding UTF-8" into .htaccess, the problem never occurs.

x --- I think it is better to add "php_value mbstring.http_output UTF-8" into .htaccess for this problem.
o --- I think it is better to add "php_value mbstring.internal_encoding UTF-8" into .htaccess for this problem.

Posted by coldsteel111 on Nov 30th 2006, 11:41

What's your MySQL version?
The announcement says phpbb3 requires mysql 3.23 or above. But to insert foreign characters, I think you need 4.1 or above.

Posted by DavidMJ (Former Team Member) on Nov 30th 2006, 20:15

coldsteel111: no, you are wrong.

ocean=Yohsuke: thank you very much for bringing this to my attention, I will handle this in a different manner.

Posted by coldsteel111 on Dec 1st 2006, 00:14

Acutally I had same problem with searching Korean words in phpbb3 b3 installed on MySQL ver 4.0.26, but no longer on 4.1.22.

I reported another character set problem which appeared on 4.0.26, that doesn't appear on 4.1.22.

Yosuke, try to upgrade your MySQL and report the result if possible.

Posted by DavidMJ (Former Team Member) on Dec 1st 2006, 00:25

coldsteel111: the bug reporter was able to correct the issue at hand by changing mbstring settings, unrelated to MySQL. Stay out of this or I will take action.

Posted by coldsteel111 on Dec 1st 2006, 00:36

Ok. I'm just trying to help you.

Posted by ocean=Yohsuke (Translator) on Dec 1st 2006, 11:13

coldsteel111: My local host environment is follwing

Apache 1.3.34 (Win32) PHP/4.3.11
or Apache 2.2.3 (Win32) PHP/4.4.4 <--- XAMPP

MySQL 4.1.18-nt
character set client utf8
(global) ujis
character set connection utf8
(global) ujis
character set results utf8
(global) ujis
character set server ujis
character set system utf8
collation connection utf8_bin
(global) ujis_japanese_ci
collation database ujis_japanese_ci
collation server ujis_japanese_ci

DEFAULT CHARSET=utf8 COLLATE=utf8_bin (for all tables of my phpBB3 database)

Checking by phpMyAdmin, Japanese characters of data in my phpBB3 table don't get garbled at all. I can read those data as Japanese word.

Linked ticket with changeset: r6701

Action performed by DavidMJ (Former Team Member) on Dec 2nd 2006, 18:16

Ticket details

Related SVN changesets