[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <83a555debf84415a7ffa269f64a2591f@smtp.hushmail.com>
Date: Sat, 15 Aug 2015 09:02:26 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: plaintext truncation
On 2015-08-14 15:12, Solar Designer wrote:
> On Fri, Aug 14, 2015 at 12:18:13AM +0200, magnum wrote:
>> The plans we have for interally representing plaintexts as UTF-32
>> throughout all of core will fix this and *many* other issues. All such
>> figures will always mean characters, not necessarily bytes.
>>
>> BTW right now I don't really expect that new code to ever (!) merge into
>> Jumbo as we know it. It will stay as another fork, whatever name we'll
>> give it. As a heads-up, I expect to continue my work mainly in that
>> fork. However, all this is just ideas so far, we'll see what actually
>> happens. Also, the plans right now has a nice side effect: All format
>> plugins will be 100% compatible between those two forks/versions of Jumbo.
>
> "As a heads-up, I expect to continue my work mainly in that fork."
>
> Does this mean someone else will need to volunteer as the new primary
> maintainer for jumbo?
For some time, I can maintain both. In the long run, I *may* end up
regarding "current" Jumbo obsolete. This all depends on how good
"Unicode Jumbo" ends up in real life - mainly in terms of performance.
magnum
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.
