Re: login.conf --> UTF-8

看板FB_current作者時間11年前 (2014/04/05 14:32), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串18/18 (看更多)
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WqlgSiG77op5Fj3s6Ms0t8jaD0qQIaXoJ Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable 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. --=20 http://ache.vniz.net/ --WqlgSiG77op5Fj3s6Ms0t8jaD0qQIaXoJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlM/naMACgkQVg5YK5ZEdN2PdQCeJA7hyp/U4oThZD+j87q6OGPq SF4AoJXabznOTztYBFRILyDxiSWRwbHQ =dN96 -----END PGP SIGNATURE----- --WqlgSiG77op5Fj3s6Ms0t8jaD0qQIaXoJ--
文章代碼(AID): #1JFwDZ79 (FB_current)
討論串 (同標題文章)
文章代碼(AID): #1JFwDZ79 (FB_current)