Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117416 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 15445 invoked from network); 24 Mar 2022 14:24:18 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Mar 2022 14:24:18 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 15D1F180505 for ; Thu, 24 Mar 2022 08:51:19 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3301 81.224.0.0/12 X-Spam-Virus: No X-Envelope-From: Received: from ts201-smtpout76.ddc.teliasonera.net (ts201-smtpout76.ddc.teliasonera.net [81.236.60.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 24 Mar 2022 08:51:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telia.com; s=tssemail; t=1648137078; bh=WF/Aj6J3R0l/3BGV8d2xYUkafmrugdn1qdMk0OD9hdI=; h=Message-ID:Date:MIME-Version:Subject:To:References:From:In-Reply-To; b=ak1YftpshZaIPpSi7BYROoPLgva/ef07g2OOSIYZcU09e5kemmBfFi8uyGlc5n+7Q4BqhKZgI8kYW6rHfcm5fz834Abv0BcjJjU6Or7o40JWb5FYgAAmTDXdbaINKDx56hIpuF/ccvEpLF105GhTmviXfeA8Uv8+pRXMPgQ5P/KK0k8sa7IT+ryPq5vJ+3B35WIKtXdnIAwNnOQkrKoorQ7VliOObjLgWE0nu4hAlo5wJT4tP/uBOTOIKx2ZNMIQszeZY4B83Kf0sDa6s5na4T+HkbM3WQqgrThzAQTTwThG0prnn1MZotjN9UPOkuc8l7JSdjDTZLsXMW9wDskTKg== X-RG-Rigid: 61A898DD06B4D331 X-Originating-IP: [84.216.97.240] X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvvddrudegledgjeejucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvffgnffktefuhgdpggftfghnshhusghstghrihgsvgdpqfgfvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomhepuehjnphrnhgpnfgrrhhsshhonhcuoegsjhhorhhnrdigrdhlrghrshhsohhnsehtvghlihgrrdgtohhmqeenucggtffrrghtthgvrhhnpeelieelhfdvteeuudektdetieetgffgtdeitdeiuefggeeffffgjeeijeehledukeenucffohhmrghinhepphhhphdrnhgvthenucfkphepkeegrddvudeirdeljedrvdegtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddrkegnpdhinhgvthepkeegrddvudeirdeljedrvdegtddpmhgrihhlfhhrohhmpehukeelledtieegudejsehpnhgvrdhtvghlihgrrdgtohhmpdhnsggprhgtphhtthhopedvpdhrtghpthhtohepihhnthgvrhhnrghlsheslhhishhtshdrphhhphdrnhgvthdprhgtphhtthhopehrohifrghnrdgtohhllhhinhhssehgmhgrihhlrdgtohhm X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.8] (84.216.97.240) by ts201-smtpout76.ddc.teliasonera.net (5.8.716) (authenticated as u89906417) id 61A898DD06B4D331; Thu, 24 Mar 2022 16:51:14 +0100 Message-ID: <811c1fb8-5f76-1a5e-474c-fe654330adaf@telia.com> Date: Thu, 24 Mar 2022 16:51:14 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Content-Language: en-GB To: Rowan Tommins References: <22242169-a16d-5261-696c-3cf00b00336a@gmail.com> <0b322a3e-469a-7ed7-16e3-0b76287f4091@gmail.com> Reply-To: =?UTF-8?Q?Bj=c3=b6rn_Larsson?= Cc: PHP Internals In-Reply-To: <0b322a3e-469a-7ed7-16e3-0b76287f4091@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [RFC] Deprecate and Remove utf8_encode and utf8_decode From: internals@lists.php.net ("Björn Larsson via internals") Den 2022-03-23 kl. 14:46, skrev Rowan Tommins: > On 20/02/2022 18:55, Rowan Tommins wrote: >> >> I 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_encode > > > Final 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 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örn