Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
locale.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2010 at 22:47 UTC
Updated:
4 Jan 2011 at 03:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bfroehle commentedAnd a patch, mostly copied from system_date_time_settings.
Comment #3
bfroehle commentedThank you automated testing. Localize date formats test changed slightly to set valid short, medium, and long formats for each language.
Comment #4
bfroehle commented~
Comment #5
bfroehle commented#3: 989894-3.patch queued for re-testing.
Comment #7
bfroehle commented#3: 989894-3.patch queued for re-testing.
Comment #8
sunThis merge makes no sense to me.
I do not understand why we need to reset the static cache here. The form constructor is invoked very early in the page request, so I'm not sure why the static cache should be populated already, and perhaps more importantly, even it would be populated already, why we can't work off that existing info.
This comment looks superfluous to me -- doesn't explain anything that the function name wouldn't denote already.
I don't see any usage of current(), next(), or prev() in this code, so I'm not sure why this reset() is required at all...?
Powered by Dreditor.
Comment #9
bfroehle commentedHere's a visual of this issue. The first attached image are the date type formats for 'long'. The second are those for 'long' in the French localization.
Comment #10
bfroehle commented@sun, almost all of the code was aped from system_date_time_settings, which explains many of the weirdnesses you pointed out above.
Since I don't actually know the "proper" functioning for this page, especially when it comes to the form respecting 'locales' specified with the date formats, I'm going to let this one go until I do a little more homework.