Re: login.conf --> UTF-8
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--cpMjnvqgx8hIIMiisNcgSOWqhf4qoBnWx
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: quoted-printable
On 05.04.2014 6:39, Sean Bruno wrote:
> On Sat, 2014-04-05 at 05:35 +0400, Andrey Chernov wrote:
>> On 04.04.2014 16:46, Gleb Smirnoff wrote:
>>> On Thu, Apr 03, 2014 at 01:34:33AM +0400, Andrey Chernov wrote:
>>> A> On 02.04.2014 21:15, Gleb Smirnoff wrote:
>>> A> > S> + :lang=3Den_US.UTF-8:\
>>> A> > S> + :charset=3DUTF-8:
>>> A> >=20
>>> A> > And I'd like to do same change for the 'russian' login class
>>> A> > in /etc/login.conf.
>>> A>=20
>>> A> Please everybody remember that we don't have UTF-8 collation
>>> A> implemented, just fallback to bytecode comparison.
>>>
>>> Any objections on checking in FreeBSD-compatible[1] UTF-8 collation
>>> implementation from Alex Tutubalin?
>>>
>>> http://blog.lexa.ru/2008/03/03/freebsd_utf8_russian_collate_vtoraja_p=
opitka.html
>>>
>>
>> Even his "version 2" have my objections. I already reply Alex about th=
is
>> in 2008. In short:
>> 1) It is error there: almost all single chars above ASCII should be
>> "chains", i.t. two bytes minimum, since there almost no intersections
>> with ISO8859-1 as UTF-8 subset.
>> 2) The table itself is very incomplete, f.e. not covering either whole=
>> KOI8-R, nor ISO8859-5, nor CP866. It is made from CP1251 with all its
>> restrictions. So, switching from f.e. KOI8-R to UTF-8 will cause sorti=
ng
>> regression. Russian UTF-8 collation should be able to sort all major
>> Russian charsets mentioned, i.e. we need combined table.
>> 3) "charmap map.ISO8859-1" declaration is missing (needed mainly for
>> using pure ASCII chars mnemonic names).
>>
>> Even in case above mentioned errors will be removed and the code will =
be
>> committed afterwards, we should understand that this way (implementing=
>> multibyte collation via single byte one) even while being possible is =
a
>> big hack and slowing sorting down up to 10 times.
>>
>> Proper "Unicode collation algorithm" is already implemented by ICU and=
>> other projects. See
>> http://unicode.org/reports/tr10/
>> It will be better if someone adopt it instead of hacks.
>>
>=20
>=20
> If you have a different patch, I'd appreciate seeing it. =20
I don't have a different patch. In case you have enough time to fix
above mentioned obstacles, I can review yours (or somebody else's) one.
"No code" situation doesn't mean wrong code can be committed. Do it
properly even when it is a hack.
--=20
http://ache.vniz.net/
--cpMjnvqgx8hIIMiisNcgSOWqhf4qoBnWx
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/eiMACgkQVg5YK5ZEdN1tvwCcDf+on6g+N/KZ2c3qD7zxNCmN
YKsAoKt2mzGExaqJxIpkfHhVpzHv1VMp
=1bq4
-----END PGP SIGNATURE-----
--cpMjnvqgx8hIIMiisNcgSOWqhf4qoBnWx--
討論串 (同標題文章)
完整討論串 (本文為第 16 之 18 篇)：