Indeed, the choices are:
And no Farsi in sight. :-(
Oh well, the 3rd party (being me!) solution still works....
----- Original Message -----
From: "Michael (michka) Kaplan" <firstname.lastname@example.org>
To: "Unicode List" <email@example.com>
Sent: Friday, July 28, 2000 9:12 AM
Subject: Re: SQL Server and Unicode
> It does indeed let them change the collation order to any that is on their
> "supported" list. I have to go to a meeting, but I will take a look later
> the Persian (Farsi) question but I do not remember it on the list so I
> suspect you are right.
> I have helped at least one client with utilities that create sort keys,
> interestingly enough for Farsi in SQL Server 7.0. My solution will keep
> working even if COLLATE cannot yet handle Farsi. :-)
> ----- Original Message -----
> From: "Roozbeh Pournader" <firstname.lastname@example.org>
> To: "Michael (michka) Kaplan" <email@example.com>
> Cc: "Unicode List" <firstname.lastname@example.org>
> Sent: Friday, July 28, 2000 9:11 AM
> Subject: Re: SQL Server and Unicode
> > On Wed, 26 Jul 2000, Michael (michka) Kaplan wrote:
> > > SQL Server 2000 supports a COLLATE keyword that allows you to specify
> > > collation at the database or field level and thus choose a different
> > > language for such columns/indexes if you like (I discuss practical
> > > and implications of this feature in an upcoming article in the Visual
> > > Programmer's Journal, tentatively scheduled for November).
> > Does is let the user choose the collation order? I've heard that it
> > doesn't support Persian well enough, and it doesn't allow modifications
> > sorting order. So people are stuck to Arabic sortings for Persian.
> > --roozbeh
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:06 EDT