There have been a huge number of globalization changes; many of them will affect only a minority of users. For a full list, please refer to http://msdn.microsoft.com/en-us/netframework/dd890508.aspx.
I do want to draw your attention to some of the changes in .NET 4.0:
• Neutral culture properties will return values from the specific culture that is most dominant for that neutral culture.
• Neutral replacement cultures created by .NET 2.0 will not load in .NET 4.0.
• Resource Manager will now refer to the user’s preferred UI language instead of that specified in the CurrentUICultures parent chain.
• Ability to opt in to previous framework versions’ globalization-sorting capabilities.
• zh-HK_stroke, ja-JP_unicod, and ko-KR_unicod alternate sort locales removed.
• Compliance with Unicode standard 5.1 (addition of about 1400 characters).
• Support added for following scripts: Sundanese, Lepcha, Ol Chiki, Vai, Saurashtra,
Kayah Li, Rejang, and Cham.
• Some cultures display names changed to follow naming convention guidelines:
(Chinese, Tibetan (PRC), French (Monaco), Tamazight (Latin, Algeria), and Spanish
(Spain, International Sort).
• Parent chain of Chinese cultures now includes root Chinese culture.
• Arabic locale calendar data updated.
• Culture types WindowsOnlyCultures and FrameworkCultures now obsolete.
• CompareInfo.ToString()() and TextInfo.ToString()() will not return locale IDs because Microsoft wants to reduce this usage.
• Miscellaneous updates to globalization properties such as currency, date and time formats, and number formatting.
• Miscellaneous updates to globalization properties such as currency, date and time formats, and number formatting.
TimeSpan Globalized Formatting and Parsing
TimeSpan now has new overloaded versions of ToString()(), Parse()(), TryParse()(), ParseExact()(), and TryParseExact()() to support cultural sensitive formatting. Previously, TimeSpan’s ToString() method would ignore cultural settings on an Arabic machine.
Source of Information : Apress Introducing dot NET 4.0 with Visual Studio 2010
I do want to draw your attention to some of the changes in .NET 4.0:
• Neutral culture properties will return values from the specific culture that is most dominant for that neutral culture.
• Neutral replacement cultures created by .NET 2.0 will not load in .NET 4.0.
• Resource Manager will now refer to the user’s preferred UI language instead of that specified in the CurrentUICultures parent chain.
• Ability to opt in to previous framework versions’ globalization-sorting capabilities.
• zh-HK_stroke, ja-JP_unicod, and ko-KR_unicod alternate sort locales removed.
• Compliance with Unicode standard 5.1 (addition of about 1400 characters).
• Support added for following scripts: Sundanese, Lepcha, Ol Chiki, Vai, Saurashtra,
Kayah Li, Rejang, and Cham.
• Some cultures display names changed to follow naming convention guidelines:
(Chinese, Tibetan (PRC), French (Monaco), Tamazight (Latin, Algeria), and Spanish
(Spain, International Sort).
• Parent chain of Chinese cultures now includes root Chinese culture.
• Arabic locale calendar data updated.
• Culture types WindowsOnlyCultures and FrameworkCultures now obsolete.
• CompareInfo.ToString()() and TextInfo.ToString()() will not return locale IDs because Microsoft wants to reduce this usage.
• Miscellaneous updates to globalization properties such as currency, date and time formats, and number formatting.
• Miscellaneous updates to globalization properties such as currency, date and time formats, and number formatting.
TimeSpan Globalized Formatting and Parsing
TimeSpan now has new overloaded versions of ToString()(), Parse()(), TryParse()(), ParseExact()(), and TryParseExact()() to support cultural sensitive formatting. Previously, TimeSpan’s ToString() method would ignore cultural settings on an Arabic machine.
Source of Information : Apress Introducing dot NET 4.0 with Visual Studio 2010
|
|
0 comments
Post a Comment