Date: Sat, 05 Apr 2014 10:07:31 +0400 From: Andrey Chernov <ache@freebsd.org> To: sbruno@freebsd.org Cc: Gleb Smirnoff <glebius@FreeBSD.org>, i18n@freebsd.org, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: login.conf --> UTF-8 Message-ID: <533F9DA3.9020901@freebsd.org> In-Reply-To: <533F7A14.7060403@freebsd.org> References: <1396457629.2280.2.camel@powernoodle.corp.yahoo.com> <20140402171546.GL44326@FreeBSD.org> <533C8269.7040305@freebsd.org> <20140404124634.GC44326@glebius.int.ru> <533F5DF5.9020803@freebsd.org> <1396665553.2415.0.camel@powernoodle.corp.yahoo.com> <533F7A14.7060403@freebsd.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Few explanations to clarify maybe non-obvious moments: On 05.04.2014 7:35, Andrey Chernov wrote: >>> big hack and slowing sorting down up to 10 times. Because our search for chains is linear because common single byte table have no more than 2-3 chains. I don't think it worth efforts to optimize search here, because better way to spend them is to implement UCA: >>> http://unicode.org/reports/tr10/ > "No code" situation doesn't mean wrong code can be committed. Since we plan to change defaults from KOI8-R to UTF-8 ("russian" login class), breaking sort order for non-alphabetic chars will violate POLA. Sort order will be broken because only CP1251 is used to construct Alex "chains" collation without merging with KOI8-R table. Merging KOI8-R collation is absolute minimum, but proper hack will be merging CP866 and ISO8859-5 too, as I already mention. -- http://ache.vniz.net/ [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlM/naMACgkQVg5YK5ZEdN2PdQCeJA7hyp/U4oThZD+j87q6OGPq SF4AoJXabznOTztYBFRILyDxiSWRwbHQ =dN96 -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?533F9DA3.9020901>