From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: [PATCH] iconv: fix to=utf32 to behave like utf32be (not... ascii?)
Date: Mon, 7 May 2018 15:25:34 -0400 [thread overview]
Message-ID: <20180507192534.GK1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAKGWAO-28CVczupmg+0+n9gEBUv3X_R+EFaLo-M02MMxhjB3Kw@mail.gmail.com>
On Mon, May 07, 2018 at 01:06:57PM -0500, Will Dietz wrote:
> Hmm this is more complicated than I originally thought.
> I'm not sure I understand the current behavior,
> but am less convinced this is a clear improvement.
Can you explain what you're confused about? It seems ok.
> Thoughts/comments appreciated :).
>
> ~Will
>
> PS: Did we discuss this years ago? I thought so, but can't find it anywhere...
I don't think so. UTF-32 did not exist as a different case from
UTF-32BE until this year.
Rich
next prev parent reply other threads:[~2018-05-07 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 19:45 Will Dietz
2018-05-07 18:06 ` Will Dietz
2018-05-07 19:25 ` Rich Felker [this message]
2018-05-07 20:52 ` Will Dietz
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=20180507192534.GK1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).