Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121715 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 9859 invoked from network); 19 Nov 2023 01:55:33 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 19 Nov 2023 01:55:33 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 74DB418002E for ; Sat, 18 Nov 2023 17:55:33 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 18 Nov 2023 17:55:32 -0800 (PST) Received: by mail-wr1-f49.google.com with SMTP id ffacd0b85a97d-32d895584f1so2317235f8f.1 for ; Sat, 18 Nov 2023 17:55:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700358929; x=1700963729; darn=lists.php.net; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=SvnnVre+eRg7JWo4DE378B84l3J5QGD1EQWH7bm0jUs=; b=L7l9xgdLS6l8Njp+6jQh5/DT3jJUpbus9vg+60CA4BbbtJUiv6x8We56wyYhAQ5enU xXZmUVxa3FG580NTsxoFAk6m6+g91BLJOL+U3Fbik/3G3ZxhQMD4JUEcVJ9GM8aQU+xi 1kbjHU4VErrYUpyl1oSFOyxwP4OHQdkuz9ds35Ao88PNX4pK9DcIWhkgeNbaye3fvQSO GxkCatQuzW+OVFQHyQGNBG2B1oE5K/QSXpHg1jDEJRENSmn2OTBMG17u4KDYUUz/e1A6 AWWJJms5spShZxtsjvCPPIfwwU/eE7Yq2vAlqDxuYzfka49FIAEwsrMiYpm8G9oF+c84 d/uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700358929; x=1700963729; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=SvnnVre+eRg7JWo4DE378B84l3J5QGD1EQWH7bm0jUs=; b=AGAGOPL0/KQD4KwsZXdxrWmkzzPGZJcW/U4p8MdVTDS4w2rRZ8wQ984k77L/15MkZI M2kME8fVavKAS0QZAvQ6+zzA2FmDHFRaabGCFkOWCNVTeWcsAlTrcCrcm4mNLZ7UDDB1 TtMpRjRm6T60V5RtD6cNwByrlQGEIbAH4LJn2+U3AJt5pa/FOtxAlwRRk4ihdrcL77ab Z7HdQQ4D/azPLrAcBKUN0jLSP7YzhAP7RbGzx6o6FJ/35FWcA1V31uxLRaa3KYKiWGll o1oZNSR71zsCNjnLkZnjjCTXTBur5N1UusSygJvcxbANCAYIt6gPSAxK2wYsjlRteWfZ glWw== X-Gm-Message-State: AOJu0YxVG246LMtNJjg7hr1xxyx0B6sZuED20eC9+xBgDdY372By+1kR WE7N7iyOVt4znhAaq2S1BzUFF8xU/N2IzEqfdPAjJ3M5KA== X-Google-Smtp-Source: AGHT+IFanhtDMAxvCrzM2/dMwiwipa5X2VMVQ6yivyEJ/9XsjRnfTORPtOaDoECYRo045r5Fj5C4ljzlscOngEBL5uc= X-Received: by 2002:adf:f884:0:b0:330:3f1e:9eeb with SMTP id u4-20020adff884000000b003303f1e9eebmr2035001wrp.71.1700358929501; Sat, 18 Nov 2023 17:55:29 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 19 Nov 2023 10:55:16 +0900 Message-ID: To: "internals@lists.php.net" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV][VOTE][RFC] Add multibyte trim function mb_trim, mb_ltrim and mb_rtrim From: youkidearitai@gmail.com (youkidearitai) 2023=E5=B9=B411=E6=9C=8819=E6=97=A5(=E6=97=A5) 5:11 mickmackusa : > Can you please clear up some ambiguity for me regarding mb_trim()? > > Is it true that the .. character range syntax will not be supported at al= l or is it merely that that syntax will not be allowed when one of the rang= e limits includes a multibyte character? > > Is a mix of a single byte range plus individual multibyte characters allo= wed? > > If .. is attempted, will it be silently interpretted as two literal dots = or will some kind of Notice be issued? > > I want to keep https://stackoverflow.com/a/72865139/2943403 accurate and = up to date. Hi, Yes, mb_trim series is not support ".." notation. ".." is processed as is. Because single byte character code is also Unicode mapping incompatible. For example, ISO-8859 series, KOI8-R and KOI8-U etc... Regards Yuya --=20 --------------------------- Yuya Hamada (tekimen) - https://tekitoh-memdhoi.info - https://github.com/youkidearitai -----------------------------