mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Philipp Klaus Krause <krauseph@informatik.uni-freiburg.de>
To: musl@lists.openwall.com
Subject: Re: Funktion for converting strings from / to UTF-16 and UTF-32?
Date: Tue, 30 Apr 2019 23:14:47 +0200	[thread overview]
Message-ID: <dfbecf59-b073-a9c0-0be3-e148f7089c35@informatik.uni-freiburg.de> (raw)

I mostly agree with your opinion on the UTF-32 functions. They had been
added to the proposal in response to comments on earlier drafts. AFAIK
the addition of char32_t probably was in part a response to platforms
that do not use a UTF-32 wchar_t.
If the proposal is put up for straw poll at WG14 again, I'd suggest
separate polls for the UTF-16 vs UTF-32 functions.

For implementation experience, the UTF-16 functions is what matters.

I do consider the UTF-16 / char16_t functions to be quite useful.
UTF-16 is still quite relevant today. The format has found its way into
many specifications, such as USB and file systems so there are important
use case in converting from / to UTF-16.

Philipp



             reply	other threads:[~2019-04-30 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 21:14 Philipp Klaus Krause [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-29 18:27 Philipp Klaus Krause
2019-04-29 22:24 ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dfbecf59-b073-a9c0-0be3-e148f7089c35@informatik.uni-freiburg.de \
    --to=krauseph@informatik.uni-freiburg.de \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).