Bug 3278 - DateTimeFormatInfo.GenitiveMonthNames returns invariant month names
Summary: DateTimeFormatInfo.GenitiveMonthNames returns invariant month names
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 2.10.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-02-08 16:05 UTC by Jon Skeet
Modified: 2012-05-15 13:41 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Jon Skeet 2012-02-08 16:05:20 UTC
Currently, DateTimeFormatInfo.GenitiveMonthNames and DateTimeFormatInfo.AbbreviatedGenitiveMonthNames appear to always use the *invariant* names.

If Mono doesn't want to get into the business of actually researching the real genitive names (which I can see would be a pain) it would at least be better to use the non-genitive names for the culture, rather than leaving the invariant ones. That way, any code which attempts to use the genitive month names correctly ends up looking minorly, forgiveably wrong instead of totally awful.
Comment 1 Marek Safar 2012-05-15 13:41:21 UTC
Fixed in master