Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116066 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 83272 invoked from network); 17 Sep 2021 09:43:48 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Sep 2021 09:43:48 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9B2611804C0 for ; Fri, 17 Sep 2021 03:23:44 -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=-3.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, 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-pl1-f181.google.com (mail-pl1-f181.google.com [209.85.214.181]) (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 ; Fri, 17 Sep 2021 03:23:44 -0700 (PDT) Received: by mail-pl1-f181.google.com with SMTP id bb10so5908776plb.2 for ; Fri, 17 Sep 2021 03:23:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wikimedia.org; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=mxHcTNstjflc6FDZd/dLr2GilVauaEqOEsOrDFdcB8I=; b=FqKpu1d10aYgpjWuLDRrFOdhQSKanTiZGUkrYTLJ1BwKvUpiyQ7D3EToGXJ4MgjOfi 1Al+xIp4gCIhPR6aPlv/Pbjg1ONgnh+eXIbAnXrnNiNeberu8Ps7+iXNd2dI3PYaXujd UsIEmhFhz4HbRLJNx9VFcC/tz4CBejhcpB0zg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=mxHcTNstjflc6FDZd/dLr2GilVauaEqOEsOrDFdcB8I=; b=0OVJPjOFEktlMLb/dxJEXc4YchM0dnKRZLj8TOgzN7AOfGpz9Rh72LSU8IUF5NKbRl Q/dyNlb/P5kln9W51aJt534HM95MQ0W+E2e7WUJvhZjePLihUlHJpeDOZbKbcSOzTXi1 U8J6gjSOjvmKJQrosZWNPPq/ow+FvR/7jtyuRNcfpCJopssEBUzggUJ6zK1QrxsO3BI3 FcRSdhCqEUUCw8Vme15BzjPwLs9e7irEHiegy/9nkbQA1eXzGY1QnZExiCrwblMUl3de l20V1OYzMrCx/cc0RPMBMvl9LtpAgNPBbmmk+ErzxvFc3Tx8KHg+rBQFVNNSX38HCD2Z 9MSg== X-Gm-Message-State: AOAM5339LCHMTzwA+zqzrqMfq3FgsQnPrvRlCwRwI4OXTmtexox5CHP1 +3f+M+CdoEia9VOhXPuQ4I2aNeQap85zFw== X-Google-Smtp-Source: ABdhPJyTjRCOFp9Tl3M0oTzJho/detCzW2EEIFJzmy2BvXLt4Neo8BXt8bz6f1bqsB4Zv1Erhql5vg== X-Received: by 2002:a17:90b:4b89:: with SMTP id lr9mr20196369pjb.145.1631874221380; Fri, 17 Sep 2021 03:23:41 -0700 (PDT) Received: from [10.1.1.45] (124-168-141-168.dyn.iinet.net.au. [124.168.141.168]) by smtp.gmail.com with ESMTPSA id y6sm5301822pjr.48.2021.09.17.03.23.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 17 Sep 2021 03:23:41 -0700 (PDT) To: Nikita Popov Cc: "internals@lists.php.net" References: Message-ID: <989b70b7-a86f-29ea-b760-c76b08eac091@wikimedia.org> Date: Fri, 17 Sep 2021 20:23:37 +1000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Make strtolower/strtoupper just do ASCII From: tstarling@wikimedia.org (Tim Starling) On 17/9/21 6:43 pm, Nikita Popov wrote: > We've been slowly moving away from locale-dependent functionality. > Since PHP 8 we no longer inherit any locales from the environment and > have made float to string conversion locale-independent. > > I would very much support making strtolower() and friends a simple > ASCII case conversion operation. mb_strtolower() etc already offer > full Unicode-compliant case conversions that work correctly with > multi-byte encodings. The locale-sensitivity of strtolower() only > works with legacy single-byte encodings and as such is of questionable > usefulness even in cases where it is not actively harmful. > > That said, I do think this change requires an RFC. Thanks Nikita. I'll write the code and then make an RFC. -- Tim Starling