Re: Re: [RFC] Use default_charset As Default Character Encoding
| From: | Joe Watkins | Date: | Thu, 31 Oct 2013 08:31:00 +0000 |
| Subject: | Re: Re: [RFC] Use default_charset As Default Character Encoding | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-69979@lists.php.net to get a copy of this message | ||
On 10/31/2013 08:28 AM, Martin Keckeis wrote:
How could you override them ?? If they are removed then they cannot be referenced. If they are not being removed then nothing is being simplified ... Cheers JoeI don't see that it is possible to merge the settings from different libraries, what if an application is relying on mbstring and iconv having different settings ??I think this use case is descibed in the RFC. The default_charset can be overwritten: default_charset < php.* < mbstring.*/iconv.* < encoding specified by functionsIt's possible that applications are relying on the separation of their settings in order to function properly, is what I am trying to say.The same like above.The only way you could possibly merge those configuration settings is by also merging the functionality, there's no backward compatible way to do that, but I can imagine at some time in the future those libraries being used to support all of the required input/output/script encoding features at the level of Zend. I don't see how this can move forward and not break stuff ...I think it's the same like above...You can override the default setting, so everything should be fine. I'm +1 for this, as there are really to much unnecessary settings around!