Re: Re: Default character encoding

On Mon, Dec 30, 2013 at 8:38 PM, Daniel Lowrey <rdlowrey@php.net> wrote: > > PHP 5.6 and master, introduce new php.ini settting. Old > > iconv.*/mbstring.* php.ini parameters will be removed for master. > > If I understand the RFC correctly shouldn't the use of the old/existing > functions trigger an E_DEPRECATED error as of 5.6 to funnel users into the > new settings? I don't see this anywhere in the associated patch. Shouldn't > this be included or have I misunderstood? > 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. 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? Nikita