Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117403 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 26393 invoked from network); 23 Mar 2022 12:20:04 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Mar 2022 12:20:04 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E961F180539 for ; Wed, 23 Mar 2022 06:46:48 -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=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 23 Mar 2022 06:46:48 -0700 (PDT) Received: by mail-wr1-f42.google.com with SMTP id a1so2202053wrh.10 for ; Wed, 23 Mar 2022 06:46:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language :from:to:references:in-reply-to:content-transfer-encoding; bh=dqWDwgJ9kgakGBMnoWLuKIi4WC4EQOjqcWFwfWfE+S0=; b=BQUfe+tOcEe/mTqZUfDrBXZtDIevW7zUEZjEUg04+6jsJVWpRuViHV71ZRySSZP0M3 47PGuR1/Eu19Jocz5E2TGdqbsKY2IbuzfeJ8IwAEYlPODjFQ5ZLyHyZQ8kqVkgzeL8rJ tugult8j+R9mxQexV9vR1BE8g/GgbYK+1GAG/UUImOdYsHq0rL+kDgvj0SvWS6sK+uuA NFtQD/YOdaN+w/bENR+AI5niENHczPeveXykT1NZ0roM081MyBJqWC+nQRvA3WBUrtpQ qgdHfMmyNkUuDr9utXxJqls9lnWzbj3xm78pE6b2gaOyh1ZVdyPAD+L35FF9py02oPR/ T4IQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:from:to:references:in-reply-to :content-transfer-encoding; bh=dqWDwgJ9kgakGBMnoWLuKIi4WC4EQOjqcWFwfWfE+S0=; b=0OP1PMEmU7Sl8ej56pTJ6rymgdsiPwJ9KujqEzVIO33S6nanNhWEBOavPo9V5CSx0m 2Sd7+oauEjCfdTMQvcr3sTv8O3NVI6tEp7PaV99eHHyoYMSmeN1XTv4UZJUKgN+L4yAz gnj6S9Mh5XHKOyWeRoLe8tK+/3a2q7GuZiAWvWxBI47fSDzNG0boVxPGUlJ7Ub1I9rU/ UXukHqS2HVyzpuHY03gRoc/+l73YS1Tl2MLRv1x1sHcN56DXxgsZMIv2MUYH0sX6bTpe nfVizs1VusRrc/4vmuB+mhWeTevWcoJwuJTfEkI+FRN589iWc8kv2dKGUjg1K0G2F+Nl Yz+w== X-Gm-Message-State: AOAM531dBR/Rsq4Qdr2/EDWLi+t1L/ENKp+B+McDMtSYOcs2uBCMRRAB hq+/GfWGI8kO+6pzs2yvwrgj0f9CHaA= X-Google-Smtp-Source: ABdhPJzlE2McHr6OH33jNio5L6KTV11cmriiFgX9e5sZ553JM5YHJqmC3gP05RsqLE1CxYs4kRSN6Q== X-Received: by 2002:a05:6000:384:b0:203:ed51:8ab3 with SMTP id u4-20020a056000038400b00203ed518ab3mr24690004wrf.211.1648043206992; Wed, 23 Mar 2022 06:46:46 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id b3-20020adfd1c3000000b00205820686dasm2623014wrd.5.2022.03.23.06.46.46 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Mar 2022 06:46:46 -0700 (PDT) Message-ID: <0b322a3e-469a-7ed7-16e3-0b76287f4091@gmail.com> Date: Wed, 23 Mar 2022 13:46:44 +0000 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: PHP Internals References: <22242169-a16d-5261-696c-3cf00b00336a@gmail.com> In-Reply-To: <22242169-a16d-5261-696c-3cf00b00336a@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [RFC] Deprecate and Remove utf8_encode and utf8_decode From: rowan.collins@gmail.com (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, -- Rowan Tommins [IMSoP]