Skip to main content

Search and Top Navigation

#7405 closed feature (wontfix)

Opened May 20, 2011 10:34AM UTC

Closed April 04, 2013 05:06PM UTC

Add date format hint to localizations

Reported by: saje Owned by: saje
Priority: minor Milestone: 1.11.0
Component: ui.datepicker Version: 1.8.13
Keywords: Cc:
Blocked by: Blocking:
Description

It would be useful if localizations contained translated version of date format eg. mm/dd/yyyy (mm/dd/yy) for en-GB, дд/мм/гггг (dd.mm.yy) for ru and DD-MM-ÅÅÅÅ (yy-mm-dd) for sv which could be used as date format hint:

$('span.dateFormatHint').text( $.datepicker._defaults.dateFormatHint );

Attachments (0)
Change History (5)

Changed October 11, 2012 02:43PM UTC by scottgonzalez comment:1

milestone: 1.9.01.11.0

Changed October 19, 2012 09:58PM UTC by mikesherov comment:2

status: newopen

Changed April 03, 2013 05:58PM UTC by scottgonzalez comment:3

owner: → saje
status: openpending

So you want a new option which won't be used by the datepicker itself? I may be missing something, but I don't think this is even provided by CLDR.

Changed April 04, 2013 05:02PM UTC by saje comment:4

status: pendingnew

Replying to [comment:3 scott.gonzalez]:

So you want a new option which won't be used by the datepicker itself? I may be missing something, but I don't think this is even provided by CLDR.

No I think it's not provided by CLDR. Nor brought together in anywhere else. Just like the other text translations, I suppose.

It's cumbersome to type in the date in cultures that have several semi-official formats and sometimes it's not clear which culture-settings are active. Yes visitor is supposed to pick the date but some users prefer not to browse for the date. And input field is good to be there as fallback for some exotic/mobile ua's.

<p>Date (<span class="dateFormatHint"></span>): <input class="datepicker" type="text"></p>

Changed April 04, 2013 05:06PM UTC by scottgonzalez comment:5

resolution: → wontfix
status: newclosed

Unfortunately we don't have a way to get this information, and we plan to move to CLDR for all of our data anyway. We're also not likely to add data that won't even be used by the plugin.