Bug #66618 [Opn->Csd]: UTF-8 encoding error

From: Date: Wed, 04 Aug 2021 11:07:18 +0000
Subject: Bug #66618 [Opn->Csd]: UTF-8 encoding error
References: 1  Groups: php.webmaster 
Request: Send a blank email to php-webmaster+get-29496@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=66618&edit=1 ID: 66618 Updated by: cmb@php.net Reported by: francois dot gannaz at silecs dot info Summary: UTF-8 encoding error -Status: Open +Status: Closed Type: Bug Package: Website problem PHP Version: Irrelevant -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: The mentioned user notes have been removed in the meantime; there might be others with non UTF-8 encoding, but these can be handled on a case by case basis. Previous Comments: ------------------------------------------------------------------------ [2014-02-03 15:00:36] francois dot gannaz at silecs dot info As I wrote in the first note: | The problem with "zero-width spaces" that get printed is probably related to CSS, not to encoding bugs. Sorry, my bad, I thought that the encoding bugs that cause the W3C validator to refuse to validate the page also caused the display error. As I wrote, I later discovered that they were separated problem. See bug 66196 for the display error. I still think that serving well encoded pages would be better, even if it means deleting (or applying iconv) to old comments. ------------------------------------------------------------------------ [2014-02-03 14:59:50] cmbecker69 at gmx dot de I have not opened the ticket, but it seems reasonable to convert all old user contributed notes to UTF-8; the newer ones seem to be anyway. ------------------------------------------------------------------------ [2014-02-03 14:50:11] bjori@php.net thanks for the explaination, but I'm still missing the actual bug here. Is this ticket for making sure all user contributed notes are utf-8? ------------------------------------------------------------------------ [2014-02-03 14:47:08] cmbecker69 at gmx dot de If a browser shall display a page in UTF-8 encoding, and there are unrecognized code points, it will substitute them by the Unicode replacement character U+FFFD[1]. You can see that yourself if you visit the array_search man page[2], and search for "greetz Udo". Just below this text is an "ANSI" encoded non-breaking space character (0xA0), which is displayed as <?>. [1] <http://www.fileformat.info/info/unicode/char/0fffd/index.htm> [2] <http://php.net/manual/en/function.array-search.php> ------------------------------------------------------------------------ [2014-02-03 14:23:18] bjori@php.net I can't imagine that a handful of latin-1 encoded characters in the user submitted data are causing your browser to present you weird data or broken navigation. ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=66618 -- Edit this bug report at https://bugs.php.net/bug.php?id=66618&edit=1

« previous php.webmaster (#29496) next »