Re: Re: Default character encoding
| From: | Yasuo Ohgaki | Date: | Mon, 30 Dec 2013 21:06:35 +0000 |
| Subject: | Re: Re: Default character encoding | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-70929@lists.php.net to get a copy of this message | ||
Hi Nikita,
On Tue, Dec 31, 2013 at 5:38 AM, Nikita Popov <nikita.ppv@gmail.com> wrote:
> Context: https://wiki.php.net/rfc/default_encoding
>
> I'm also a bit concerned about this RFC in general. I think the idea behind
> it make sense (consolidate encoding settings), but right now it feels a lot
> like http://xkcd.com/927/ (turning 6 ini options into 9).
> Especially given
> the issue with the different charset names between mbstring and iconv, I'm
> not convinced that this will be more help than harm.
>
Most applications won't mix multibyte char modules. Even if one did, they
still can change encoding by setting INI from user scripts.
If users use default (UTF-8), it does not matter which multibyte char module
they are using.
I think too many INI settings bad also. Unneeded INIs should be cleaned up
in future version. (PHP6?)
> Also, the most important part of the RFC (htmlspecialchars) doesn't seem
> reflected in the patch. Is that not yet implemented or did I misunderstand
> something?
>
I'll implement required changes for functions. It's incomplete. I just
don't have
enough time :(
Thank you for the comment.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net