On Fri, 2007-12-07 at 08:38 -0500, Matt Kettler wrote:
> Stefan Jakobs wrote:
> > Let's assume you running a mailrelay for a university and your users are
> > from
> > different countries. Lets assume further on you have no Swedish people at
> > your university (and you get a lot of spam from Sweden). Then it would be
> > nice to have a not_ok_locales option, because you see immediately which
> > locale character set is considered as possible spam.
Now let's further assume, your students are able to speak English. And
they are collaborating with an Open Source project, discussing with a
lot of people from all over the world.
Let's assume, one of them happens to be Swedish. And even though the
entire communication is English, that ignorant bastard dares to have his
real name at the bottom of his mail -- which includes Swedish chars.
Do you hear that flushing sound of catching spam?
Swedish chars are a superset of English chars. As are German and many
others. To see that this is not an artificial, made up example please
have a look at my real name. :)
> Now that sounds like a valid reason to me.
It doesn't to me...
Anyway, this whole example is non-realistic as is. As Matt pointed out
in a later post, we are talking character sets here, not languages. In
the world of ok_locales, there is no distinction between en and se,
which is just en to ok_locales...
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
