Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121433 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 86011 invoked from network); 19 Oct 2023 14:35:48 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 19 Oct 2023 14:35:48 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 48849180507 for ; Thu, 19 Oct 2023 07:35:48 -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=-0.6 required=5.0 tests=BAYES_00,BODY_8BITS, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 19 Oct 2023 07:35:47 -0700 (PDT) Received: by mail-lf1-f51.google.com with SMTP id 2adb3069b0e04-507a3b8b113so7472123e87.0 for ; Thu, 19 Oct 2023 07:35:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697726146; x=1698330946; 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=BX8/YYeiVGlsVYQ3iwZgYM3zluo5tNAHo5GLrEzeNcM=; b=kKhj5QQwQpgDwJNm4QXbHrVubrZizqXwCkqbRQGuCoITaMjqLBkViVHcX/Q9TR7CTo wE4vkzC7HqanAE3racJp/DMYm7b76Rd6bFNjkgXjSa3SOXjEDEIHpRkyi6ZeQmUZOmiP 6/7gE8snp/rzv4hLvgfqyJwoy83+ESQg9o/PP8/3oby9WfBPMgaXierARWa3/isXTPOY KMjBnYahZXRdTtq3RsEymS67jZEDFGxrAQ+cf1AOOFdHXi8btLYXH0voazrLFxMpULwx IyKmjqKfYspKba99yIEtjfTkudiImTN18voGHb5dp1iHb9+kxNwd3Xa9/1sbDGwaZeCq m+Iw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697726146; x=1698330946; 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=BX8/YYeiVGlsVYQ3iwZgYM3zluo5tNAHo5GLrEzeNcM=; b=lhmpb1XqoGLsLso67mAuRdic34ohCzcP73SQodh3NfSmYvthE+889XeTWlZgPfxm2q phgfMW8oMGXwOBy28DY3G6xQHqniMeYUyP5BIet8A/evXTn0ncw7OWmK7aSliBsR8Uvw FDd7UeS/5V+zVes/XBxcw15dPAryPGVFqa8sW+1Ei0Y6lxf/nYKe3NaKioz55bHqM5hT dV3bx5D58AJPRIhmUMp86IJjo5Dp5G/YJLmFwTHZ6KzLXG1tadFrWDSwd4zg7JdDRtcY 0P7dTSPRkCJ0YX4bi80ybcP10OTcZK7BsiMipnKOQHKZsUOWqyaNV8viulL7MhLXywUO wvPg== X-Gm-Message-State: AOJu0Yy3Y/7ck68qtraswymdmoBZVyjTOF3sLiBCIiM4mOHWaW615kje 32Q/P8AZQwYI92y/MGiIQY/IeOcEeNc9QsrQy0EP71YOdg== X-Google-Smtp-Source: AGHT+IH4FXnOWrxp+hGpcx9TErnEWgIeOBJ28foEnGq3ePuHu67m2RNWC7FpiW/tcaIJC55LhXQY89/ch9wq9z8rjrY= X-Received: by 2002:ac2:560f:0:b0:506:8d2a:5654 with SMTP id v15-20020ac2560f000000b005068d2a5654mr1558501lfd.28.1697726145892; Thu, 19 Oct 2023 07:35:45 -0700 (PDT) MIME-Version: 1.0 References: <7a6178b9-a967-4b9f-b091-4057013838f9@gmail.com> In-Reply-To: <7a6178b9-a967-4b9f-b091-4057013838f9@gmail.com> Date: Thu, 19 Oct 2023 23:35:34 +0900 Message-ID: To: internals@lists.php.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] [Discussion] Add multibyte trim function (mb_trim, mb_ltrim and mb_rtrim) From: youkidearitai@gmail.com (youkidearitai) 2023=E5=B9=B410=E6=9C=8819=E6=97=A5(=E6=9C=A8) 22:33 Niels Dossche : > > Hi Yuya > > On 19/10/2023 13:57, youkidearitai wrote: > > Hi, internals. > > > > 8ctopus san can't send email, so I'm writing new RFC for multibyte > > trim function. > > https://wiki.php.net/rfc/mb_trim > > https://github.com/php/php-src/pull/12459 > > > > I would like to under discussion. > > Thanks for this. > > I have a question about the .. support: > You state "Mapping with other character codes may be incompatible", for o= ne of the reasons not to support this. > Can you please explain this a bit more? > > Also, I notice at the top of your RFC it still says: "Status: Draft", I t= hink you forgot to change this. > Similarly, the RFC is not listed under discussion on https://wiki.php.net= /rfc. > > > > > Regards. > > Yuya > > > > Kind regards > Niels > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > Hi, Niels. Thank you for your question and Wiki status is changed. > You state "Mapping with other character codes may be incompatible", for o= ne of the reasons not to support this. > Can you please explain this a bit more? Sure. For example, Japanese character code, If try to match hiragana for each character code, it will end up with different bytes. Hiragana letter matches in UTF-8. [=E3=81=81-=E3=82=9E] But other character code is sometimes different. example: EUC-JP [=E3=81=81-=E3=82=93=E3=82=9B=E3=82=9D=E3=82=9E] Sometimes the order is different why I say "Mapping with other character codes may be incompatible". Therefore, I thought it was impossible to express the ".." notation. Regards Yuya --=20 --------------------------- Yuya Hamada (tekimen) - https://tekitoh-memdhoi.info - https://github.com/youkidearitai -----------------------------