qr code c# mvc Globalization in Visual C#

Generation QR Code JIS X 0510 in Visual C# Globalization

16

The DateTimeFormatInfo class provides a comprehensive set of methods and properties to handle and respond to the dates of different cultures. Examine the following code:

' VB Dim UsersCulture As CultureInfo = New CultureInfo("es-VE") Dim Days() As String = UsersCulture.DateTimeFormat.DayNames For Each Day As String In Days Console.WriteLine("Day Name for Venezuelan Spanish : " & Day) Next // C# CultureInfo UsersCulture = new CultureInfo("es-VE"); String[] Days = UsersCulture.DateTimeFormat.DayNames; foreach (String Day in Days) { Console.WriteLine("Day Name for Venezuelan Spanish : " + Day); }

The corresponding output should resemble that shown in Figure 16-4.

Figure 16-4

If this same code was run with United States English as the CurrentCulture, the output would be Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday, respectively. The same differences exist with respect to months, as shown in the following code:

' VB Dim UsersCulture As CultureInfo = New CultureInfo("es-VE") Dim Months() As String = UsersCulture.DateTimeFormat.MonthNames For Each Month As String In Months Console.WriteLine("Month Name for Venezuelan Spanish : " & Month) Next

// C# CultureInfo UsersCulture = new CultureInfo("es-VE"); String[] Months = UsersCulture.DateTimeFormat.MonthNames; foreach (String Month in Months) { Console.WriteLine("Month Name for Venezuelan Spanish : " + Month); }

Again, when this code is run, the name of each month in Venezuelan Spanish will be shown. There are many other properties corresponding to just about every conceivable facet of date manipulation. One of the reasons this is so important is because of evaluation and comparisons. If one culture has a date format in mm/dd/yyyy format and the other stores the values in dd/mm/yyyy format, what would happen if you tried to compare them Chances are that you d end up with erroneous comparisons. However, by specifying that the dates are from different cultures, comparisons will work correctly. The same problem exists when dealing with numbers and currency, and essentially the same solution is in place using the NumberFormatInfo class instead of the DateFormatInfo class. This can be easily illustrated by using the same code we used previously, but with a slight modification:

' VB Dim UsersCulture As CultureInfo = New CultureInfo("es-VE") Console.WriteLine("Venezuelan Currency Symbol: " _ + UsersCulture.NumberFormat.CurrencySymbol) Console.WriteLine("Number Decimal Symbol: " _ + UsersCulture.NumberFormat.NumberDecimalSeparator) // C# CultureInfo UsersCulture = new CultureInfo("es-VE"); Console.WriteLine("Venezuelan Currency Symbol: " + UsersCulture.NumberFormat.CurrencySymbol); Console.WriteLine("Number Decimal Symbol: " + UsersCulture.NumberFormat.NumberDecimalSeparator);

As shown by the output from this code, the Venezuelan currency abbreviation is Bs and a comma is used as the decimal separator when writing numbers.

One important reason to use the CultureInfo class is to allow for culturally aware string comparisons. To do this, the CultureInfo class has a CompareInfo property, which is an instance of the CompareInfo class. You can create a new instance of the CompareInfo class or, more practically, you can set it to the CompareInfo property of the CurrentCulture.

16

The following code shows the results from outputting the current CompareInfo associated with the CurrentCulture on your machine:

' VB Dim DemoInfo As CompareInfo = _ Thread.CurrentThread.CurrentCulture.CompareInfo Console.WriteLine(DemoInfo.Name) Console.WriteLine(DemoInfo.LCID) // C# CompareInfo DemoInfo = Thread.CurrentThread.CurrentCulture.CompareInfo; Console.WriteLine(DemoInfo.Name); Console.WriteLine(DemoInfo.LCID);

Comparisons are typically based on one specific culture. (For instance, if an application was written in the United States, all comparisons would probably be based on en-US.) Because of this, it s generally best to create a CompareInfo object based on the current culture. If necessary, however, you can also create a new CultureInfo object based on any culture you d like, as shown in the following code:

' VB Dim DemoInfo As CompareInfo = New CultureInfo("en-US").CompareInfo Console.WriteLine(DemoInfo.Name) Console.WriteLine(DemoInfo.LCID) // C# CompareInfo DemoInfo = Thread.CurrentThread.CurrentCulture.CompareInfo; Console.WriteLine(DemoInfo.Name); Console.WriteLine(DemoInfo.LCID);

The most basic approach to using the CompareInfo class is to call the Compare method, passing in the values to be compared. The following code illustrates comparing two words for equivalency using the Compare method of the CompareInfo class:

' VB Dim FirstString = "Cot " Dim SecondString = "cot " Dim DemoInfo As CompareInfo = New CultureInfo("fr-FR").CompareInfo DemoInfo.Compare(FirstString, SecondString) // C# String FirstString = "Cot "; String SecondString = "cot "; CompareInfo DemoInfo = new CultureInfo("fr-FR").CompareInfo; DemoInfo.Compare(FirstString, SecondString);

If you run this code, the two strings will not be considered equal. Even though the cultural information will evaluate to true, the casing is different. To handle items like this, you can use members of the CompareOptions enumeration to control how