Re: [RFC] Deprecate and Remove utf8_encode and utf8_decode
| From: | Björn Larsson via internals | Date: | Thu, 24 Mar 2022 15:51:14 +0000 |
| Subject: | Re: [RFC] Deprecate and Remove utf8_encode and utf8_decode | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117416@lists.php.net to get a copy of this message | ||
Den 2022-03-23 kl. 14:46, skrev Rowan Tommins:
On 20/02/2022 18:55, Rowan Tommins wrote:in ISO9959-1 (Latin 1). Now the utf8_decode are used in the backend when the webapps and site are communicating with DB, e.g. in Ajax calls. The webapps are built in Javascript. Our feedback would be that the usage of this function have had zero issues or bugs for more then five years that e.g. the apps have been in production. So in this specific use case there is no benefit at the moment with this removal. OTOH, the usage of this function is mostly wrapped so it's not a big job changing it and it's good that the RFC points out alternatives, where we would go for mbstring. I also find the usage of both functions in one of our most important Open Source libraries. How important they are there I don't know. r//BjörnI would like to open discussion on an RFC to deprecate and later remove the functions utf8_encode() and utf8_decode() https://wiki.php.net/rfc/remove_utf8_decode_and_utf8_encodeFinal chance for feedback on this RFC, as revised, before I put it to a vote. There's been very little reaction on this thread, which I'm hoping means everyone's either planning to vote "Yes" or just doesn't care... Regards, Well, the usecase I can provide is that we have a site with content