Re: default_encoding RFC – aftermath
| From: | Andrea Faulds | Date: | Sun, 12 Aug 2018 17:57:40 +0000 |
| Subject: | Re: default_encoding RFC – aftermath | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-103088@lists.php.net to get a copy of this message | ||
Hi Cristoph,
Christoph M. Becker wrote:
I'm quite happy, though, that this hasn't happened yet, since it seems that the encoding names may be different between the extensions. At least the php.net manual states[2]: | Some systems (like IBM AIX) use "ISO8859-1" instead of "ISO-8859-1" so | this value has to be used in configuration options and function | parameters. It appears to be worthwhile to review the deprecation of the respective iconv.* ini options. Not quite sure about the mbstring.* ini options.Could this not be solved by making all the extensions support all the encoding name aliases or so? That wouldn't be difficult to implement and wouldn't break anything. Thanks! -- Andrea Faulds https://ajf.me/