logo

Previous Thread:   Creating an instance is hang for one foreign language only

8/27/2005 2:07:02 PM    Incorrect Vietnamese Collation in VS 2003 & 2005 Beta 2
I have tried to sort Vietnamese words after setting the Culture property, but  
  
the result is still in wrong order.  
  
Code:  
  
Thread.CurrentThread.CurrentCulture = new CultureInfo("vi-VN");  
  
string[] words = txtbox.SelectedText.Split('\n');  
  
Array.Sort(words);  
  
as is implemented in VietPad.NET text editor (http://vietpad.sf.net). I  
  
believe this is a bug with .NET. How can I work around this problem?  
  
The Vietnamese collation rules can be found at:  
  
http://vietunicode.sourceforge.net/charset/vietalphabet.html  
  
http://www-950.ibm.com/software/globalization/icu/demo/locales/?d_=en&_=vi

8/27/2005 2:23:17 PM    Re: Incorrect Vietnamese Collation in VS 2003 & 2005 Beta 2
This problem was reported some time ago (by you, I believe!), and cannot be  
  
changed in either product since that would break the collation versioning  
  
guarantees we make (and break database products that depend on the index).  
  
The bug has been fixed in Vista (Beta 1 now available), which has a new  
  
sorting version so we were able to make the change. I'll probably be posting  
  
on this in my blog sometime soon, with some more details....  
  
--  
  
MichKa [Microsoft]  
  
NLS Collation/Locale/Keyboard Technical Lead  
  
Globalization Infrastructure, Fonts, and Tools  
  
Blog: http://blogs.msdn.com/michkap  
  
This posting is provided "AS IS" with  
  
no warranties, and confers no rights.  
  
"Quan Nguyen" <QuanNguyen@discussions.microsoft.com> wrote in message  
  
news:9327C680-21D1-4888-9EE6-1E867D1A51E7@microsoft.com...

9/4/2005 7:30:57 PM    Re: Incorrect Vietnamese Collation in VS 2003 & 2005 Beta 2
Hi Michael Kaplan,  
  
Vista is OS. Does your statement indictate that the collation table is taken  
  
from the OS by VS.NET and not native to .NET? If that is the case the  
  
collation will be dependent on the target OS where the application is run.  
  
Say, I develop an application on Vista and run it on XP, the collations will  
  
be different.  
  
Actually, it is better to have the collation table to be present at one  
  
place and all use it. At present, the collation tables used by Win XP, .NET,  
  
Office, SQL Server are different. The natural choice of place to keep the  
  
collation table will be the OS.  
  
You have mentioned that the table is fixed in Vista (for Vietnamese, in this  
  
case). Any plans to provide regular upgrades collation tables of Win XP in  
  
the monthly upgrades or in Service Packs?  
  
Regards,  
  
Pavanaja  
  
"Michael (michka) Kaplan [MS]" <michkap@microsoft.online.com> wrote in  
  
message news:%23GH1K20qFHA.3640@tk2msftngp13.phx.gbl...

9/5/2005 10:54:01 AM    Re: Incorrect Vietnamese Collation in VS 2003 & 2005 Beta 2
"pavanaja" <pavanaja@vishvakannada.com> wrote...  
  
The .NET Framework has its own collation tables, which cannot be updated  
  
until a provision for versioning could somehow be added. This is true for  
  
the very reasons you indicate -- the same results across the framework on  
  
different platforms is preferred.  
  
I would in theory agree; however, since both SQL Server and the .NET  
  
Framework span versions of the OS, both take snapshots of the OS data.  
  
No, this cannot be done. A new major version and a way to handle versioning  
  
is required for both.  
  
The .NET Framework has no way to handle versioning at the moment, so it  
  
cannot have an update that woul break backward compatibility until it does.  
  
SQL Server has provided a whole new set of collations for its upcoming  
  
release, and will now be up to the Server 2003 levels, but it cannot have  
  
this fix in it until some future date when it is updated to provide the  
  
Vista version of the data.  
  
--  
  
MichKa [Microsoft]  
  
NLS Collation/Locale/Keyboard Technical Lead  
  
Globalization Infrastructure, Fonts, and Tools  
  
Blog: http://blogs.msdn.com/michkap  
  
This posting is provided "AS IS" with  
  
no warranties, and confers no rights.