ID: 22108 Comment by: foospam at wp dot pl Reported By: bugzilla at jellycan dot com Status: Assigned Bug Type: Feature/Change Request Operating System: * PHP Version: * Assigned To: moriyoshi New Comment:
17 Dec 2003 1:47am EST, "dev at glossword dot info" wrote: > Not a bug. Please use correct text-editors (...) "Correct" = "standard". Unicode IS a new standard and PHP should support it. These text-editors aren't correct, if they doesn't support unicode. Previous Comments: ------------------------------------------------------------------------ [2003-12-17 01:47:47] dev at glossword dot info Not a bug. Please use correct text-editors (unipad, emeditor). ------------------------------------------------------------------------ [2003-11-20 18:11:37] gergely77 at hotmail dot com This bug can be circumvented by using a hex editor to delete the first 3 bytes of the file thereby removing the Windows inserted UTF-8 BOM (Byte Order Mark). Frhed, a free GNU GPL'ed hex editor's source and executable Windows binary can be found at (http://www.kibria.de/frhed.html) ------------------------------------------------------------------------ [2003-11-09 16:12:50] a9c83cd8bb41db324db5b449352f183 at arcor dot de Thought about it... Now I think it's better when the BOM isn't part of the output because that would cause trouble if you want to output images or PDF or something like that... ------------------------------------------------------------------------ [2003-11-08 06:45:22] a9c83cd8bb41db324db5b449352f183 at arcor dot de I think the best would be that PHP recognizes the BOM and outputs it before it outputs the document (but after the HTTP headers, of course) so that the document can still be recognized as UTF-8 when it's saved to disk (where no Content-Type headers with a charset specification are available). ------------------------------------------------------------------------ [2003-11-07 03:09:53] trunghongnguyen at yahoo dot com ertre ------------------------------------------------------------------------ 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/22108 -- Edit this bug report at http://bugs.php.net/?id=22108&edit=1
