Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126890
Precedence: bulk
MIME-Version: 1.0
Date: Fri, 21 Mar 2025 12:17:32 +0100
To: "Paul M. Jones" <pmjones@pmjones.io>
Cc: youkidearitai <youkidearitai@gmail.com>, php internals
 <internals@lists.php.net>
Subject: Re: [PHP-DEV] Potential RFC: mb_rawurlencode() ?
In-Reply-To: <EEC27D2D-BDBE-41F4-95F1-45EBD0B328BC@pmjones.io>
References: <C47E5955-E75E-49A7-88D3-6957669057F0@pmjones.io>
 <CAEPPVa1p9tiTZLs69Mjo05KTyLi2RwLJ+Z4SSWKEwCZdR9RnOw@mail.gmail.com>
 <CAEPPVa38tgc=K5Hgcf+-d7JNfi+v97fjFQpwA0J7cOMCz1FxNw@mail.gmail.com>
 <EEC27D2D-BDBE-41F4-95F1-45EBD0B328BC@pmjones.io>
Message-ID: <c0b86fc1b3a5eb1d144f80c931febeaa@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-03-20 17:46, schrieb Paul M. Jones:
>> ```php
>> function mb_rawurlencode(string $string, string $encode): string {}
>> ```
> 
> Ah yes, you're right -- probably `?string $encode = null` to match with 
> mb_substr().

I am not sure if that signature makes sense and if the proposed 
functionality fits into mbstring for that reason. IRIs are defined as 
UTF-8, any other encoding results in invalid output / results that are 
not interoperable. As one example paragraph from RFC 3987:

> Conversions from URIs to IRIs MUST NOT use any character encoding
> other than UTF-8 in steps 3 and 4, even if it might be possible to
> guess from the context that another character encoding than UTF-8 was
> used in the URI.

The correct solution to me is to build a proper thought-through API as 
part of the proposed new Uri namespace and not adding new standalone 
functions without a clear vision.

Best regards
Tim Düsterhus