A re-genitive post

by Michael S. Kaplan, published on 2007/08/04 03:35 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2007/08/04/4218583.aspx

People may recall that I have talked about genitive dates in whole heap o' posts:

• What the %$#! are genitive dates? (25 December 2004)
• Don't roll your own GetDateFormat (15 July 2005)
• Genitive dates, revisited (10 November 2005)
• Do genitive dates always work properly for Greek? (10 November 2005)
• Any Sami speakers reading this blog? :-) (11 November 2005)
• One last post about genitive dates (12 November 2005)
• Practical Uses for Replacement Cultures/Locales (20 March 2006)
• It may not always end with ի (08 April 2006)
• It may not always end with ის or ისა, either (09 April 2006)

Anyway, there is an interesting programmatic issue related to making changes in .NET >= 2.0 in DateTimeFormatInfo.MonthNames but not DateTimeFormatInfo.MonthGenitiveNames that Shawn Steele talked about yesterday in What's a genitive month name anyway?.

This would not usually be a common issue (and thankfully does not cause problems in the most reasonable scenario of creating a custom culture) but it is possible to run into the problem if you are modifying a DateTimeFormatInfo directly to use it. So it is a good one to point out. :-)

This post brought to you by ᙖ (U+1656, a.k.a. CANADIAN SYLLABICS CARRIER SHE)

referenced by

go to newer or older post, or back to index or month or day