Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116720 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 37992 invoked from network); 22 Dec 2021 15:05:39 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Dec 2021 15:05:39 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EBB261804B4 for ; Wed, 22 Dec 2021 08:09:37 -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=-2.2 required=5.0 tests=BAYES_00,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-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, 22 Dec 2021 08:09:37 -0800 (PST) Received: by mail-wr1-f42.google.com with SMTP id e5so5905135wrc.5 for ; Wed, 22 Dec 2021 08:09:37 -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=My3Tgka2ljLPVu+MuD3CYNqcRH6qR/JRLHZTLU+zubg=; b=cnedCbgoqixDLW5YJ2LuwnrDV02gZTpwV3y3u6wjYK9Pzik9X2gBFJzsWy3Gqrq7cs jaYApUtc7ValhpRLa021I0XkzXSZAfB3f8hXlvmDgpiaK3aS8sFY0xRw/5XN+dVr8ba4 bvDXH3DoVBDlJpFg9DyKhwtQkt/WaUuLuLp7I1jJX6V5SI458DijSXDkNXOaXWcCwFbu pMRCyh6DsNP5IeYto4GBEKVZ5hdya5B4pQbONLPIl8aatN9wIfOfE0mr06FsDZvVzbdu Vc5us9T9h4aF1exPEtvwiZzK4MhHPMPy/20HxHXHenmIf42YH66YceDz+lIYqLr3JBDT 25AA== 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=My3Tgka2ljLPVu+MuD3CYNqcRH6qR/JRLHZTLU+zubg=; b=U6axhvtwervaBDCW4lNXrYyCgKLDBulQzDE3Blf6AZPGjb5NXCgXLtGaDEZApSOhz0 AGoICpv9xkMMVPj9gouD2IqxbI6l1Z9kqHWrXBDeMrz2YLigadZL3Kfc6tJga21Pxfg3 B+ti2foPWgjm2s9X5MguUT34+8X5nkbBhgcK4CuDbt1ld3iVrHouSZApQNfkGQM+E7z+ DK0W0mr2BAsX7Zzt1X0BuSj4kEHOajLljStbliMjsaB0xF0Au6G7SU6UYBB2rTYYXFKZ 2SPpM2yg2lFFg/WK7PYEpkiNMyME+kLaXyfqZDsZ8ssbmoF79G2RuRTy63zFO9iDtZ1d eOwQ== X-Gm-Message-State: AOAM530new1RVTUloKX4KHsRUG4EKicxQBiTZ/FiGfQgwnPZcB/t/7e8 kf0TzDGeSUDuRq9EfIlxkVBTvMlfib4= X-Google-Smtp-Source: ABdhPJyyw2Unqx/jl9J42IZWH4f4LWVTZh9LJ/N2GxBTbrfjCisywi5zP8G9CzfqD7qly6O+7086sQ== X-Received: by 2002:a5d:4804:: with SMTP id l4mr2545929wrq.629.1640189376434; Wed, 22 Dec 2021 08:09:36 -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 c11sm6584262wmq.48.2021.12.22.08.09.35 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Dec 2021 08:09:35 -0800 (PST) Message-ID: <1569f0ad-278e-a0aa-aa77-bfc7c23e6631@gmail.com> Date: Wed, 22 Dec 2021 16:09:35 +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> <67aa2782-816e-4885-01ea-971cc6a52a86@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 14:45, Hans Henrik Bergan wrote: > I wonder if anyone depends on utf8_* without also depending on mb_* ? I > imagine that is exceedingly rare On the contrary, anyone who uses mb_* functions is likely to use mb_convert_encoding rather than utf8_encode and utf8_decode. In fact, the only legitimate uses of the functions I've seen are as a fallback for when ext/mbstring is not loaded, since they are always available (since PHP 7.2; before that, they were oddly part of ext/xml). There is a very small set of use cases where you really do know you have or want ISO 8859-1, and they are the most portable implementation. Regards, -- Rowan Tommins [IMSoP]