#28654 [Fbk->Opn]: Possible bug in utf8_encode (bit operations)

From: Date: Wed, 14 Jul 2004 08:25:45 +0000
Subject: #28654 [Fbk->Opn]: Possible bug in utf8_encode (bit operations)
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-62202@lists.php.net to get a copy of this message
ID: 28654 User updated by: krausbn@php.net Reported By: krausbn@php.net -Status: Feedback +Status: Open Bug Type: *Languages/Translation Operating System: WinXP PHP Version: 4.3.4 Assigned To: moriyoshi New Comment: Sorry, but even the iconv() function doesn't do the job. Maybe someone else (german guy?) can make some tests to furnish proof to my problem. Previous Comments: ------------------------------------------------------------------------ [2004-07-12 18:51:24] moriyoshi@php.net Most likely not a bug in PHP. The reporter better check out things I pointed out. ------------------------------------------------------------------------ [2004-07-11 21:34:21] sniper@php.net Moriyoshi: Was that last comment a statement of this being a bug in PHP or what? Is this verified bug? Can you fix it if it is? (if it's not bug -> bogus..) ------------------------------------------------------------------------ [2004-06-14 21:00:29] moriyoshi@php.net Looks like you are trying to do the conversion between the code page 1252 and UTF-8. http://www.microsoft.com/globaldev/reference/sbcs/ 1252.htm Let alone mbstring, most of iconv() implementations support CP1252 (a.k.a. IBM1252). HTH ------------------------------------------------------------------------ [2004-06-10 00:11:14] krausbn@php.net Hm, what ISO standard do I use (german, Win32) when I paste&copy Word text into a textarea and post it to a PHP script? Is it possible to solve my problem by converting my character encoding to iso-8859-1 with the mb-functions? ------------------------------------------------------------------------ [2004-06-08 09:38:23] derick@php.net utf8_encode only deals with iso-8859-1, which does not define characters in the range from 128 to 160. Though it should probably just replace those characters with a question mark, as that's how invalid characters are usually converted. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/28654 -- Edit this bug report at http://bugs.php.net/?id=28654&edit=1

« previous php.bugs (#62202) next »