Opened 10 years ago

Closed 7 years ago

#4254 closed bug (wontfix)

Datepicker: Localization error in uk locale

Reported by: dvp Owned by:
Priority: major Milestone: 1.11.0
Component: ui.datepicker Version: 1.6rc6
Keywords: globalize Cc:
Blocked by: Blocking:

Description

In UK (Ukraine) locale default date format does not match ISO.

WRONG: 'Січ','Лют','Бер','Кві','Тра','Чер', ...

VALID: 'січ.','лют.','бер.','квіт.','трав.','черв.' ...

because of the server tools that take a date - do not recognize its true

references:

http://framework.zend.com/issues/browse/ZF-5909

http://unicode.org/cldr/data/common/main/uk.xml

Change History (5)

comment:1 Changed 10 years ago by rdworth

Milestone: TBD1.8

To fix this, we're going to need to add a capability for the datepicker to differentiate between 'stand-alone' and 'format' month name abbreviations. It currently has only one property 'monthNamesShort' which is used for both headers (stand-alone) and formatting (format), despite the following code comment

monthNamesShort: [...], // For formatting

comment:2 Changed 10 years ago by rdworth

For more info, see http://unicode.org/reports/tr35/tr35-2.html#%3Cdates%3E "Both month and day names may vary along two axes: the width and the context. The context is either format (the default), the form used within a date format string (such as "Saturday, November 12th", or stand-alone, the form used independently, such as in Calendar headers. The width can be wide (the default), abbreviated, or narrow. The latter is the shortest possible width: it is typically used in calendar headers."

comment:3 Changed 7 years ago by Scott González

Milestone: 1.9.01.11.0

comment:4 Changed 7 years ago by petersendidit

Keywords: globalize added
Status: newopen
Summary: Localization error in uk localeDatepicker: Localization error in uk locale

comment:5 Changed 7 years ago by Scott González

Resolution: wontfix
Status: openclosed

It sounds like this isn't something that can be fixed with the current datepicker. If the datepicker actually should be using the other form in the UI, then please file a pull request. Thanks.

Note: See TracTickets for help on using tickets.