Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113662 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 39044 invoked from network); 22 Mar 2021 11:17:37 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Mar 2021 11:17:37 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E9EA9180508 for ; Mon, 22 Mar 2021 04:12:50 -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=-2.1 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-Virus: No X-Envelope-From: Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com [209.85.208.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 ; Mon, 22 Mar 2021 04:12:50 -0700 (PDT) Received: by mail-ed1-f43.google.com with SMTP id y6so18815407eds.1 for ; Mon, 22 Mar 2021 04:12:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Ujh672+Rn2x0j55s+sF8if0roPDcZFoyNL3jlnpWxvQ=; b=afiY/+wE9RJ3+t4xB3jF4IlV/yFyWtfAU+Abr0TqiXnqYCOJO+bDKbT7wlyLpe8p6O i4fJKqVdl6KjfTyza5uA5y7IP4EUpxnVhYu8aZnnaK0yn9wWhCd6FLWczAh5rLjkKAX+ shAl2eRfzso2o1FfQnYLuRLmy1NJ2Byvc9bw7xeln85Naf2NkGxHsJpNjUa2CHemm/Qa qlWppG+0KZHQZ6GZ48/tIG1GtyuHtuOCMZe+AlBBIa3DRM3GMXLsHsowbT3blf6lly22 hJDEPMrSed81Mg6LGg7OUN9ZSoIHdDyXnqXMfg68+z7WvEtdo5KDvolTfG11a6nTNwgL srxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Ujh672+Rn2x0j55s+sF8if0roPDcZFoyNL3jlnpWxvQ=; b=MsaP2crTcae0In50yAtwHTE7/2b9S4Pey/i7S576bUu6ryz1cGvQ41Y+jgpJFZmTSb OMAL0S7JWR9JagJ8qg0rUTp2lPnktM78NceaTi6XwaHRKlA783LAsj5tNrR9yJrKGU0r U+JcqWA2IgmNFloiBXxGhWG0W5ILVvkB578HscnHknAHeg01Ot9TJInYUanlfsokyXHI RRnxDnVBJGDMHsbYSXmTkk6QboB15j1IwV00PB2LXmP4XU5ep+UFhBXjBRNv7YVaIGOn XKSTW3G34FVpNUU0jR+G/lhriDxcs3+nhhVztrYF+yBTE0F7wmFYGtmDMNocB1JeV3Wc wCaQ== X-Gm-Message-State: AOAM531qkpWmmEDbgakoSwGNPm7ln27V49SiXXbF7Nzm63jaLQmIDVSs sLJGTafnhANzkplhfxhrkl3b9Y/C7k8= X-Google-Smtp-Source: ABdhPJzBVjW37Xz9qldnCDxOfBtBJKIkUIiyAz6vEXw/RWy0WXe6dG7QRePsZHDnbfT3SDLXt4Y7zw== X-Received: by 2002:aa7:cf14:: with SMTP id a20mr24973916edy.49.1616411568295; Mon, 22 Mar 2021 04:12:48 -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 f9sm11027124edq.43.2021.03.22.04.12.47 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 Mar 2021 04:12:47 -0700 (PDT) To: PHP internals References: <3a4d89fc-c5f8-4720-b2e0-f6f3c28684f9@www.fastmail.com> <5f5fd136-e181-d5d3-fe40-1a4cc5c668f2@gmail.com> <25680b8d-af02-c1d4-e630-7bf079881f1c@gmail.com> Message-ID: Date: Mon, 22 Mar 2021 11:12:46 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode? From: rowan.collins@gmail.com (Rowan Tommins) Hi Björn, On 22/03/2021 10:28, Björn Larsson wrote: > In our case we use the utf8_decode functions to convert from UTF8 in > the client to ISO-8859-1 on the server, since the site is encoded in > latin1. > > Our usage of that function is working flawlessly, so for us it's super > important to have a clear migration path with a good polyfill! 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)? Regards, -- Rowan Tommins [IMSoP]