Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116717 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 30218 invoked from network); 22 Dec 2021 13:22:16 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Dec 2021 13:22:16 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id BF7A0180544 for ; Wed, 22 Dec 2021 06:26:13 -0800 (PST) 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.8 required=5.0 tests=BAYES_05,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 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-wm1-f44.google.com (mail-wm1-f44.google.com [209.85.128.44]) (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, 22 Dec 2021 06:26:13 -0800 (PST) Received: by mail-wm1-f44.google.com with SMTP id n10-20020a7bc5ca000000b00345c520d38eso1154882wmk.1 for ; Wed, 22 Dec 2021 06:26:13 -0800 (PST) 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:to :references:from:in-reply-to:content-transfer-encoding; bh=wBEAkxBxI5FSSLV8mXISgivfqU6196izr1XDQohQdEU=; b=QULDqh6A5uNj3tw1c6eT5SuaVhPG0wPFcmEKO9TGE5k6Gijmmf5SEegGPgHyz7dm5L f8h9fbxdEnp8QyoPTAKePmyxEPq5rdbbO/XQ7e8EP77iVXMTHdTVCLVyhMqoK6vIlFU6 dfTWHirnoDvXS90Kk8FKY0MFQDZG3OwTzjv0o2cYHoJ5cdpPFYlFazFmT7CQYVdpRE35 R51RxeU62K8t5JrZSqVwfb03FYwtdvqC4+z6rifIcXWs5lwnFxvw6Om8jXKOWUm/y+AT knxm84Uk3j4UGoLw5iHONmawfJLiZO2Ht+QuQ2P3V6FT+ScmJKXAsaD/jbtTH6g087qq Q3RQ== 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:to:references:from:in-reply-to :content-transfer-encoding; bh=wBEAkxBxI5FSSLV8mXISgivfqU6196izr1XDQohQdEU=; b=ZyZeazFaR4IaS/dLzHFlomF061dpIzQIM6B5ed6XXfN+5a9f+Akiqs0AQb8M2W+l0k Ig5FOxSTRQDOUJuAK+J8/rvADtDJyXaxt7+H2fvE9Do/yImdR5AoZ8tNtryu0NeZGD8Q OtHYbtIc++oG1h5VSvbeU/qly1+3QcRI4jTOU5ZO81NU8+4hcMhQnoMgDgklnTIEekBZ I6kpljlca2E5kd1GJ6IT1r/1lIN1aIS5uIxJ2bYkFrT9XE7s6tfMChEwZ5CYVBBoZg+w yXb2NDv1kvzbtgiPDOa2JTp3gsBsbkIidcdVLx8Nj710M0AkSS9BIvcpdkGTkGeuy29e eUDA== X-Gm-Message-State: AOAM5334KDjPSkcr1iziMpgwmBk8HgvpFjupWqATlRimbtYfiWrMMear c7ycBD63lqVRMnPHY0BZBHQoWWH7AQw= X-Google-Smtp-Source: ABdhPJxyZZMXToLR8F7oAbP4KE4pZRUqUJATlwe39rxBHsNF4MbH9YXsQp1+NH31BOvLv4mz+5l57Q== X-Received: by 2002:a7b:cb17:: with SMTP id u23mr1111596wmj.155.1640183172029; Wed, 22 Dec 2021 06:26:12 -0800 (PST) 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 bd19sm5163051wmb.23.2021.12.22.06.26.11 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Dec 2021 06:26:11 -0800 (PST) Message-ID: <67aa2782-816e-4885-01ea-971cc6a52a86@gmail.com> Date: Wed, 22 Dec 2021 14:26:10 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Content-Language: en-GB To: internals@lists.php.net References: <3a4d89fc-c5f8-4720-b2e0-f6f3c28684f9@www.fastmail.com> <9e93269e-986f-ffa4-7433-cf2c548a133f@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode? From: rowan.collins@gmail.com (Rowan Tommins) On 22/12/2021 10:45, Andreas Heigl wrote: > I just dug a bit deeper on the subject and found this RFC from 2016: > > https://wiki.php.net/rfc/remove_utf_8_decode_encode > > Perhaps we can just revive that one! As I say, I have a draft with lots more detail in, which I will tidy up after Christmas. I deliberately didn't link to it, because I want to re-read it myself before letting other people comment on it, and don't have the time right now. My current inclination is to deprecate in 8.next, and remove in 9.0, but I want to make sure the argument for that is solid before putting it to a vote. Regards, -- Rowan Tommins [IMSoP]