Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 29 Apr 2019 18:24:12 -0400
From: Rich Felker <>
Subject: Re: Funktion for converting strings from / to UTF-16 and

On Mon, Apr 29, 2019 at 08:27:35PM +0200, Philipp Klaus Krause wrote:
> Would musl be interested in adding support for functions that convert
> from / to UTF-16 and UTF-32 (assuming that char16_t is UTF-16 and
> char32_t is UTF-32)?
> There is the proposal N 2282, which was discussed half a year ago at the
> Pittsburg meeting of WG 14; back then the comitee wanted to see a second
> implementation fo these functions (the library that comes with SDCC
> already has them).

I'm not sure. They seem to be of limited usefulness - UTF-16 is
legacy, and UTF-32 is the same as wchar_t on any implementation that
actually supports UTF-32 (at least wchar_t has to cover the whole
Unicode codepoint space, so 16-bit is out and the only reason it could
be anything other than UTF-32 is gratuitous incompatibility).

Of course we'll support this if it's standardized as a required
interface for future C versions, but I'm not sure it's in line with
musl's philosophy or criteria for inclusion to be trying to advance
these interfaces into a standard without a good argument that they're
important to have (if you believe they are, I'm open to hearing that
and seeing what others think).


Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.