lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20180113002407.GD8249@thunk.org> Date: Fri, 12 Jan 2018 19:24:07 -0500 From: Theodore Ts'o <tytso@....edu> To: Gabriel Krisman Bertazi <krisman@...labora.co.uk> Cc: david@...morbit.com, bpm@....com, olaf@....com, linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org, kernel@...ts.collabora.co.uk, alvaro.soliverez@...labora.co.uk Subject: Re: [PATCH RFC 03/13] charsets: utf8: Add unicode character database files On Fri, Jan 12, 2018 at 05:12:24AM -0200, Gabriel Krisman Bertazi wrote: > From: Olaf Weber <olaf@....com> > > Add files from the Unicode Character Database, version 7.0.0, to the source. > A helper program that generates a trie used for normalization from these > files is part of a separate commit. It looks like the latest version of Unicode is 10.0.0. Once we pick a Unicode version, changing will be painful; but in the absence of interop requirements, is there a reason to stick with Unicode 7? Why not take the latest version of Unicode and then freeze on it? - Ted
Powered by blists - more mailing lists