Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKGWAO-28CVczupmg+0+n9gEBUv3X_R+EFaLo-M02MMxhjB3Kw@mail.gmail.com>
Date: Mon, 7 May 2018 13:06:57 -0500
From: Will Dietz <w@...z.org>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] iconv: fix to=utf32 to behave like utf32be (not... ascii?)

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.

Thoughts/comments appreciated :).

~Will

PS: Did we discuss this years ago? I thought so, but can't find it anywhere...


On Thu, May 3, 2018 at 2:45 PM, Will Dietz <w@...z.org> wrote:
> Attached, I think it's just a case of a missing case statement.
>
> This is needed or the result can't be read back as utf32 which seems
> like an important property.
>
> ~Will

Powered by blists - more mailing lists

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