Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113667 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 53709 invoked from network); 22 Mar 2021 13:18:49 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Mar 2021 13:18:49 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 711F51804D8 for ; Mon, 22 Mar 2021 06:14:05 -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=1.4 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53]) (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 ; Mon, 22 Mar 2021 06:14:04 -0700 (PDT) Received: by mail-lf1-f53.google.com with SMTP id n138so21199378lfa.3 for ; Mon, 22 Mar 2021 06:14:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7NR3/nYnDyYAgBDikXJ2wQxGoiiHYqAEO0km7WobN7A=; b=dBC4xAvsuMjtahnaJYNKEpdw3MhmTnkCGg0WMnT7s6Xno8SSC/kBuIkVWO1nCmTWMg vi02HvjmJeq9qBt90spiu3NFM3zAQND4vqX+vuXXNFKRvOYwNfXFDC705j3451rPzwFB JhFqqcHFkrct3r3gJtm2Pya0VWpDPglp4sit3+8wTbmEgfRt0CXCl8Go5bKcKLmV+iFI QvuQ2ly63rUieuOB9G7ABoNL2w22BAOdj2k1c+DD8rllskFiePs8HBSyFyRRrfM3ZjUE StloxMBduvo7gZrcTGrbnH8aCwQ07ubMdP1lN5BiRV7tfrpq0QaEn4jgFrmuccXxUFGh eYRg== X-Gm-Message-State: AOAM531zXoNQa+zY6e1B9xey1y7I3dJaH0enex+w+CkOKKMQAwrj8na3 vArPEkpwj78t+T6aUotg4bdWo2ziBf+hz/EbcSaR8Q== X-Google-Smtp-Source: ABdhPJyuiMKlmiBnQczj3Z60wq4BtIcPnivHOlydn6lzrw8rHfMdnrOE0spuxgxsAhG+lsPj1JrUywwUGvNkhzcWVkw= X-Received: by 2002:ac2:58cf:: with SMTP id u15mr8941611lfo.397.1616418841142; Mon, 22 Mar 2021 06:14:01 -0700 (PDT) MIME-Version: 1.0 References: <3a4d89fc-c5f8-4720-b2e0-f6f3c28684f9@www.fastmail.com> <5f5fd136-e181-d5d3-fe40-1a4cc5c668f2@gmail.com> <25680b8d-af02-c1d4-e630-7bf079881f1c@gmail.com> In-Reply-To: Date: Mon, 22 Mar 2021 08:13:50 -0500 Message-ID: To: Rowan Tommins Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000d5b70705be1fd6e5" Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode? From: pollita@php.net (Sara Golemon) --000000000000d5b70705be1fd6e5 Content-Type: text/plain; charset="UTF-8" On Mon, Mar 22, 2021 at 6:12 AM Rowan Tommins wrote: > I realise you can't speak for anyone else, but as a point of interest, > would you be OK with a polyfill having a requirement on ext/mbstring or > ext/iconv, or would you have a strong preference for a replacement built > into the core (i.e. guaranteed available without any optional packages)? > Can you clarify what *YOU* mean by a polyfill? Because you're talking about dependence on iconv/mbstring/icu which implies you want a polyfill that does something other than what the original utf8_en/decode() functions do, and those functions certainly do not need external dependencies. They're really just not that complex. -Sara --000000000000d5b70705be1fd6e5--