ID: 24309
User updated by: jc at mega-bucks dot co dot jp
Reported By: jc at mega-bucks dot co dot jp
Status: Bogus
Bug Type: mbstring related
Operating System: Linux
PHP Version: 4.3.3RC1
Assigned To: hirokawa
New Comment:
Are you sure? ^_^
I am not an encoding expert so if you say that it is a valid sequence I
believe you but ...
I am using postgreSQL as a database and it says that it is not a valid
EUC sequence. So either PHP is wrong or the database is wrong :)
Here is my test code:
echo "Checking $string .......<BR>";
$sql = "select id from products where name like '$string'";
$conn = pg_connect("host=$IP port=5432 dbname=$DB user=postgres");
$res = pg_query($conn, $sql);
$err_msg = pg_last_error($conn);
if (preg_match("/Invalid EUC_JP character sequence found/",
$err_msg)) {
echo "NOT VALID<BR>";
}
The error message returned by the DB is:
pg_query(): Query failed: ERROR: Invalid EUC_JP character sequence
found (0xba7e)
The output is:
Checking 喧� .......
NOT VALID
I'll post this to the postgreSQL developer's list also in case it is a
bug in postgreSQL.
If you are certain that this character sequence is valid can you point
me to a ressource I can use to show the postgreSQL team that they have
a bug that needs fixing?
Thanks!
Previous Comments:
------------------------------------------------------------------------
[2003-06-30 07:49:30] [EMAIL PROTECTED]
It is not a bug of mbstring.
0xb7,0xf6,0xba,0x7e is a correct byte seqence of EUC-JP.
------------------------------------------------------------------------
[2003-06-28 09:40:13] [EMAIL PROTECTED]
URL decoded byte sequance of 'search_words=%B7%F6%BA%7E' is
B7E6+BA7E, which is correct EUC-JP character sequence.
<?php // sample code
$str_euc = sprintf("%c%c%c%c",0xb7,0xf6,0xba,0x7e);
echo mb_detect_encoding($str_euc); // output is 'EUC-JP'
?>
Encoding detection is not perfect, it may make mistake if the length of
string is too short.
But, I believe encoding detection of mbstring works fine in this case.
B7E6+BA7E is not correct byte sequence of SJIS, UTF-8, ISO2022-JP. It
is correct EUC-JP byte sequence.
------------------------------------------------------------------------
[2003-06-24 02:52:51] jc at mega-bucks dot co dot jp
Description:
------------
I've just run into a strange "bug". I have a form on my web site that
takes input from the user and then uses that to do a search of a
postgresql database.
The form is set to be EUC-JP, but this weekend a user submitted a
query
that postgres reject because it "contains invalid EUC-JP" characters.
Luckily the error was logged and I was able to track it down.
I thought that maybe the user had entered some bad characters in the
form or used some strange encoding so I should better check to make
sure
that the encoding of the submitted form data really is EUC-JP using
mb_detect_encoding(). But unfortunately mb_detect_encoding() says that
the invalid string *is* in EUC-JP!?
The query string is as it appears in the URL is:
search_words=%B7%F6%BA%7E
In the script that parses this query I have put the following:
$words = $_GET["words"];
$enc = mb_detect_encoding($aI["words"]);
echo "encoding is $enc and the query is ($words)";die;
The result is:
encoding is EUC-JP and the query is (喧?)
As you can see the query string is *not* a valid EUC-JP sequence ...
Reproduce code:
---------------
$words = $_GET["words"];
$enc = mb_detect_encoding($aI["words"]);
echo "encoding is $enc and the query is ($words)";die;
Expected result:
----------------
SJIS (?) or Undefined.
mb_detect_encoding() does not specify what it returns if an invalid
character sequence for which the encoding cannot be detectec is passed
in.
In the above case the character sequence is valid SJIS I believe ...
Actual result:
--------------
EUC-JP
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=24309&edit=1
