Date: Mon, 25 Aug 2025 18:47:46 -0700
On Sunday, 24 August 2025 23:07:32 Pacific Daylight Time Paul Caprioli wrote:
> > As I pointed out in the other email: the choice here should be UTF-16, not
>
> UTF-8. That would get immediate and unconverted access to ICU, Win32 and
> Cocoa/CoreFoundation APIs.
>
> Sorry, but I'm not seeing how this relates to extended floating-point types.
It doesn't. This portion of the thread changed from discussing aliasing double
and std::float16_t to discussing aliasing char and char8_t, which then led to
the discussion of what encodings SG16 and the Standard should be looking into.
> > As I pointed out in the other email: the choice here should be UTF-16, not
>
> UTF-8. That would get immediate and unconverted access to ICU, Win32 and
> Cocoa/CoreFoundation APIs.
>
> Sorry, but I'm not seeing how this relates to extended floating-point types.
It doesn't. This portion of the thread changed from discussing aliasing double
and std::float16_t to discussing aliasing char and char8_t, which then led to
the discussion of what encodings SG16 and the Standard should be looking into.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel Platform & System Engineering
Received on 2025-08-26 01:47:58