Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116718 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 32044 invoked from network); 22 Dec 2021 13:42:03 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Dec 2021 13:42:03 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D5A34180549 for ; Wed, 22 Dec 2021 06:46:00 -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_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,MISSING_HEADERS,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) (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:46:00 -0800 (PST) Received: by mail-pj1-f43.google.com with SMTP id x1-20020a17090a2b0100b001b103e48cfaso4290340pjc.0 for ; Wed, 22 Dec 2021 06:46:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:cc; bh=25EtJG/vR12S063dbIbdUgXKLcjMvuB28OFgNyCDYoQ=; b=l/6IqlDyUOc+dL0tEmyOkU7b+1ncPszNRpkmmhsa51l88vhy8ivxEyGKhywb78DRY6 +nG+pgqDEpq5vw2HaBMVOt5AvTGn+yx3Dg9JOZqjooZwrTkS4fPDKPJnOFUhgqA7+eLW TZ45ez8ReeacDvmESpT5Kf73sl3TxUfOjyQ/9uYQSotvOlD/eTRlWxUVz/iQbdqkSshI 0kqRal2wpGZs+xW2PSh8DvAjF4nATs3Mrhd5sVl86+BjRf+ApOmZgqlj3JqxHKe2eq7F KFHHbyP443s2cavYCZjC11Vv5Lfy5WRBwavN8Qvciy2AM6rvlb/ZUcG9r3iv3jxXkHlH AP/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:cc; bh=25EtJG/vR12S063dbIbdUgXKLcjMvuB28OFgNyCDYoQ=; b=g9lxpw9XYR/N5sU7JMLEw+2tfKySGvFRXHyt1B2Mdescrr5+gqwRDrqTrxSYBD5EYk Howh2KSoK2UGajdZvnnQCz/ZTp0CCz9481T+hX0npU9JV7FvjcyFHuM5dZ85Ty2nYo4P bA9JK5X94N1yr/ipFVP6XGugn45gkGnJ8J+32aC87ukGm4aMv7MC/ZmUi4CZoWQM8TKt DM58nzT1PSaGsoPEC+QYnE2WvG7D59E2q7xjNz/283+DksEDuKBzhRmkvy6gpd1Xvmn/ IdW0XuCDuwKdgi719P/fLQTxb6xPLEKTIAqasUV2IrMvW+bn0e5Gzfork3cGVZOU/9TG I/Aw== X-Gm-Message-State: AOAM530WTSaML9kxkXCy6rfHU+dQSWSLlu1cLOlnYaF7IL1b3lqN9zV6 B47ErO8+AiKKdLmPYeDKjX9WOolC8k4RRKaBvhKljVzZQRU= X-Google-Smtp-Source: ABdhPJyBOqZPFuw74H0VTnIDSF8AyZbbHidktIUWZ+KOiiHpBmwofgnJu3m5GxV9KwON26IU+fs0Q6e+Q9dF5RzlFL8= X-Received: by 2002:a17:90b:20ca:: with SMTP id ju10mr1709296pjb.171.1640184358881; Wed, 22 Dec 2021 06:45:58 -0800 (PST) MIME-Version: 1.0 References: <3a4d89fc-c5f8-4720-b2e0-f6f3c28684f9@www.fastmail.com> <9e93269e-986f-ffa4-7433-cf2c548a133f@gmail.com> <67aa2782-816e-4885-01ea-971cc6a52a86@gmail.com> In-Reply-To: <67aa2782-816e-4885-01ea-971cc6a52a86@gmail.com> Date: Wed, 22 Dec 2021 15:45:46 +0100 Message-ID: Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000013ce1805d3bd2e4d" Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode? From: divinity76@gmail.com (Hans Henrik Bergan) --00000000000013ce1805d3bd2e4d Content-Type: text/plain; charset="UTF-8" I wonder if anyone depends on utf8_* without also depending on mb_* ? I imagine that is exceedingly rare On Wed, Dec 22, 2021, 15:26 Rowan Tommins wrote: > 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] > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > > --00000000000013ce1805d3bd2e4d--