Re: [PATCH] Changing entity charset handling inext/standard/html.c
| From: | Moriyoshi Koizumi | Date: | Wed, 16 Oct 2002 21:25:21 +0000 |
| Subject: | Re: [PATCH] Changing entity charset handling inext/standard/html.c | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-89582@lists.php.net to get a copy of this message | ||
Wez Furlong <wez@thebrainroom.com> wrote:
> Unfortunately, we absolutely must remain 100% backwards compatible with
> htmlentities(), so this patch should not be applied.
Were there any discussions exactly about this issue? Though I have to see
some historical reason, however I don't understand why 100% backwards
compatibility is required for htmlentities().
Because the patched htmlentities() acts in the same way with default
configuration, and IMHO defaulting to iso-8859-1 is quite meaningless for
the scripts that uses other charsets than it.
Hmm... otherwise I would like to suggest a mbstring function like
mb_htmlentities(), but it would sound like a reinvention of the same
wheel...
> However, I don't see a problem with making phpinfo determine the charset
> and passing that on to the internal htmlentities function?
The problem is that php_info_html_esc() in ext/standard/info.c calls
php_escape_html_entities() with no charset information specified. Without
the patch, every character is treated as ISO-8859-1 even if a fetched
character is actually a mere first byte of a multibyte character.
Moriyoshi Koizumi