Bug#600310: wrong collation(?) order for et_EE.UTF-8 causes regexps to fail matching randomly

2010-10-16 Thread Bastian Blank
On Sat, Oct 16, 2010 at 01:47:42AM +0400, Michael Tokarev wrote: There's a bug in et_EE.UTF-8 locale definition causing some latin chars to be treated as non-letters. These are at least in range t..y inclusive, i.e. [t-y]. Like this: Are you sure that the letters t to y a valid in the

Bug#600310: wrong collation(?) order for et_EE.UTF-8 causes regexps to fail matching randomly

2010-10-16 Thread mihkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just installed -115 from incoming.debian.org and I can confirm that now my cronjobs are running as expected. Thanks for quick response. mihkel I'm preparing an upload right away to fix this bug (-115). I would appreciate it if you can test it

Bug#600310: wrong collation(?) order for et_EE.UTF-8 causes regexps to fail matching randomly

2010-10-15 Thread Michael Tokarev
Package: locales Version: 2.11.2-6 Severity: critical Tags: l10n There's a bug in et_EE.UTF-8 locale definition causing some latin chars to be treated as non-letters. These are at least in range t..y inclusive, i.e. [t-y]. Like this: $ echo $LANG et_EE.UTF-8 $ echo s | grep '[a-z]' s $

Bug#600310: wrong collation(?) order for et_EE.UTF-8 causes regexps to fail matching randomly

2010-10-15 Thread Michael Tokarev
Ok, after discussing on #debian-devel and some more thinking, even if it's 02:23 here already... I now see the problem isn't in locales package actually, and it should affect other locales too. The prob is that people used to use [a-z] to mean all 26 latin chars, while various locales have them