Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116504 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 49717 invoked from network); 25 Nov 2021 09:01:45 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 25 Nov 2021 09:01:45 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 402661804E3 for ; Thu, 25 Nov 2021 01:58:55 -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.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, 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-ed1-f54.google.com (mail-ed1-f54.google.com [209.85.208.54]) (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 ; Thu, 25 Nov 2021 01:58:54 -0800 (PST) Received: by mail-ed1-f54.google.com with SMTP id g14so23097936edb.8 for ; Thu, 25 Nov 2021 01:58:54 -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:to :cc; bh=cIj1ekVJms3b//lFWupCI3QnU5GylDoYLvnTP8yFzIw=; b=QxwdjCAbDNRA7NVZfOVq8RsVKFd7wCCgg+GveMbgIl9V7RHsKpkMka2pNDdVRy3Wof zAHBNbFbR93QsQt4ren7Cue3hB6ZP2I1Rc8Fc4cXLpIoUtSR+NGRgLAkr0hl5NIRhthy Zc3n9KKiytLe2WDHaYVzEKA1IEFCde1HIQPYKDpijCLvXqfj7bc7wzJ3f78cEoFd83s5 FQ5xZUXIDGzfINtyHUXeFXfZGcIgT3KI1FDiU5d07Aucn7KrAc51r8lfOrFnUvGtEE+B cxODxkafx8LmXS5iTcrIfsI7s35/PWIjLQjz+A5BJ0L3AvBwgF0GLSzmObTX3+8Q8IE7 BuiQ== 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:to:cc; bh=cIj1ekVJms3b//lFWupCI3QnU5GylDoYLvnTP8yFzIw=; b=fajst5FCZOJ5dVsVlDz4hOrSRSnrT7X+tjsZvifsvHOyRGNwNrR0K6YFbR7Z7foiQS /OTo1QoYUkZVGBJ8o46Uu1zhIu6KuPXewzVylQgXc0QGJV045XD7UyJ5Z2aun31TcKyP v1RQjYaNtaKB/hjLymR0YvBKtwKZbDGT1+OULsynKerFGO+YMc0Wb3kXWmHHRUajyVLt YqwcEcXIBXNWb5Lk4BvHlwoCv1nqmkqBxEQOZoUnP6lk5fHpD9KK1rQvH0sM9U86evJE rcouUtTuj3ek/Is0EhXOY9R7uq38FWp2PJyrvXKWICD4jL2FDV3oX5eCVEZjLguKNFL8 lUwg== X-Gm-Message-State: AOAM531vYAZ9cSWc/R8runMGt1wNAEPTdylK7jCt39mq5Z6d8fQ1/Zw/ GWnEIAkWscwEt8VYDjoFPbt9oVm9IhULfkLayiI= X-Google-Smtp-Source: ABdhPJw5b+wDG0oMCfNXU26LJlPpgGqpqZZey6BN1Q1Uggzar2/zSst+h9P+c2o3G70vxYa1p9so3izq7oHX00iyABc= X-Received: by 2002:a17:906:f6c2:: with SMTP id jo2mr28808850ejb.496.1637834332868; Thu, 25 Nov 2021 01:58:52 -0800 (PST) MIME-Version: 1.0 References: <757fcf17-4d8b-0eee-8226-e88705d92795@wikimedia.org> <59feb482-2dec-3fdc-1104-5a47cb627634@wikimedia.org> In-Reply-To: <59feb482-2dec-3fdc-1104-5a47cb627634@wikimedia.org> Date: Thu, 25 Nov 2021 10:58:41 +0100 Message-ID: To: Tim Starling Cc: Internals Mailing List Content-Type: multipart/alternative; boundary="0000000000009c938105d19a056f" Subject: Re: [PHP-DEV] [VOTE] Locale-independent case conversion From: nicolas.grekas+php@gmail.com (Nicolas Grekas) --0000000000009c938105d19a056f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le jeu. 25 nov. 2021 =C3=A0 10:47, Tim Starling a =C3=A9crit : > On 25/11/21 7:55 pm, Nicolas Grekas wrote: > > > I voted yes because I want to see this happen but I raised a point in > https://externals.io/message/116141#116259 and didn't get an answer: > > Despite their name, I never used natcase functions for natural language >> processing. I use them eg to sort lists of files in a directory, to >> account >> for numbers mainly. But that's not what I would call natural language >> processing. I'm not aware of anyone using them for that actually. I'm >> wondering if it's a good idea to postpone migrating them to an >> hypothetical >> future as to me, the whole reasoning of the RFC applies to them. >> > > I wish the strnatcasecmp() and natcasesort() function, but also the > SORT_NATURAL flag were also covered by this RFC. > Is that possible? Would it make sense? > > > I'm not going to migrate those functions at this time. It's just a projec= t > scope decision. > Why? The RFC says: > because they also use isdigit() and isspace(), Does that mean "too much work needed"? I would totally understand that of course but I hope someone could do these last miles. > and because they are intended for natural language processing I definitely do not agree with this argument and it should be removed from the RFC to me as it might add confusion in the future. Nicolas --0000000000009c938105d19a056f--