🚀 go-pugleaf

In article <TT.93Jan1135637@tarzan.jyu.fi> tt@tarzan.jyu.fi (Tapani Tarvainen) writes:
>>Unicode (and for that matter Plan 9 UTF) does not support the last
>>two mentioned functions. I have yet to see Plan 9 _sort_ which will
>>sort Russian strings without being told explicitly that it is Russian.
>
>So what?
>I've yet to see anything even planned that would allow sorting
>both Finnish and German without being told which is wanted.  
>In fact I can't even imagine one that would make any sense.
>In the case of a list of names, the very same data could be
>sorted differently depending on where it is going to be used.

Pfrr, take a look at DEMOS Unix-likes -- they do sort both Russian and English
without being told which is wanted. [<ah>-<ya>]* in shell really selects
				      ^    ^ -- imagine real cyrillic letters here
all files startting from lowercase russian letter. lex generates correct
parsers for languages with russian keywords. Grep works as it is supposed to.
So far no user complained that there are two o's and two A's in the code.

It is not impossible -- it's rather easy if the right code is choosen.

>Tying sorting rules to character sets is not a good idea, IMHO.

Would you like to specify the language for every range in every regular
expression you use?

Embedding sorting rules to character sets is not a "good idea" -- it's
a necessity and you can do nothing about it.

--vadim