Re: Potential RFC: mb_rawurlencode() ?
Hi Rowan & all,
> On Mar 22, 2025, at 10:20, Rowan Tommins [IMSoP] <[email protected]> wrote:
>
> On 21/03/2025 11:17, Tim Düsterhus wrote:
>>
>> 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.
>
> This confirms a nagging feeling I had when I first saw the thread: the name
> "mb_rawurlencode" implies "do the same things as rawurlencode, but for multi-byte
> strings", but that's not what is being proposed.
[snip]
No argument; my point is more "if we are going to do IRI and WHATWG-URL, we're going to
need some additional support functionality around encoding component values for them." How that
is achieved is up for grabs. If this discussion has revealed a tentative consensus that it needs to
happen, I consider it a success.
Next up: what exactly should the API around this functionality look like? I suggested functions but
that's clearly a non-starter; what do we feel is a good alternative, and can it be achieved
independently from (but in support of) the URI+WHATWG-URL proposal?
-- pmj
Thread (6 messages)