Encode and Decode are definitely more important, even for nominally Unicode
text. You need scalar values or code points to do anything else.

On Wed, Mar 17, 2021 at 10:55 AM Corentin Jabot <corentinjabot_at_[hidden]>
wrote:

>
>
> On Wed, Mar 17, 2021, 15:45 Steve Downey via SG16 <sg16_at_[hidden]>
> wrote:
>
>>
>>
>> On Wed, Mar 17, 2021 at 9:22 AM Tom Honermann via SG16 <
>> sg16_at_[hidden]> wrote:
>>
>>> On 3/17/21 5:23 AM, Corentin Jabot wrote:
>>>
>>>
>>>
>>> On Tue, Mar 16, 2021 at 3:59 PM Tom Honermann via SG16 <
>>> sg16_at_[hidden]> wrote:
>>>
>>>
>>>> - P1628 <https://wg21.link/p1628>: Unicode character properties
>>>>
>>>> As the author I do not expect to do further work on this in the 23 cycle
>>>
>>> That matches my expectations, thanks for confirming.
>>>
>>
>> Not that we have a paper, or that I'm asking for anyone to do work, but
>> without access to the UCD, all the other algorithms are off the table. In
>> theory it's an implementation detail, in practice it would be an ABI break
>> to change the APIs for property lookup, and having two or more mechanisms
>> in a std library implementation seems like a bad idea.
>> Expectation setting is important. It's not clear to everyone how the
>> Unicode layers work, even if the explanations are straight-forward.
>>
>
> Clarification: i will do further work. Just don't expect that to happen
> before the end of the C++23 cycle. Lewg queue is full :)
> We can start to talk about it... But transcoding seems more important
> anyway?
>
>> --
>> SG16 mailing list
>> SG16_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>>
>