Why does System.Globaliz ation.DateTimeF ormatInfo.Curre ntInfo.MonthNam es
return 13 elements? Why does it not use the cuurent culture?
RTFM ;)
DateTimeFormatI nfo.MonthNames Property
Property Value
A one-dimensional array of type String containing the culture-specific
full names of the months. In a 12-month calendar, the 13th element of
the array is an empty string. The array for InvariantInfo contains
"January", "February", "March", "April", "May", "June", "July",
"August", "September" , "October", "November", "December", and "".
"Ignacio Machin ( .NET/ C# MVP )" <machin TA laceupsolutions .comwrote in
message news:uQ1Tllz4HH A.5804@TK2MSFTN GP05.phx.gbl...
Hi,
>
"AA2e72E" <AA2e72E@discus sions.microsoft .comwrote in message
news:7C1864F4-1158-48B3-A42D-B244CD9A44D5@mi crosoft.com...
>Why does System.Globaliz ation.DateTimeF ormatInfo.Curre ntInfo.MonthNam es
>return 13 elements? Why does it not use the cuurent culture?
>
I do not know of any culture that has 13 months.
>
Now I do not know the rationale behind using a final empty value, somebody
has a clue?
>
A calendar system that has 13 months is a "reformed" calendar that allows an
equal # of days spread across the 13 months (28 days x 13 months = 364
calendar days).
Checkout "Calendar reform" on wikipedia for a more in-depth explanation :)
>>Why does System.Globaliz ation.DateTimeF ormatInfo.Curre ntInfo.MonthNam es
>>return 13 elements? Why does it not use the cuurent culture?
>>
>I do not know of any culture that has 13 months.
>>
>Now I do not know the rationale behind using a final empty value,
>somebody has a clue?
>>
>
A calendar system that has 13 months is a "reformed" calendar that allows
an equal # of days spread across the 13 months (28 days x 13 months = 364
calendar days).
>
Checkout "Calendar reform" on wikipedia for a more in-depth explanation :)
Comment