[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #5920(closed enhancement: fixed)

Opened 5 years ago

Last modified 5 years ago

Specify when to use which length with available formats

Reported by: mark Owned by: pedberg
Component: xxx-spec Data Locale:
Phase: Review: mark
Weeks: Data Xpath:


When constructing patterns from date skeletons, we don't say when to use which of the following patterns.

<dateTimeFormatLength type="full">
		<pattern>{1} 'at' {0}</pattern>
<dateTimeFormatLength type="long">
		<pattern>{1} 'at' {0}</pattern>
<dateTimeFormatLength type="medium">
		<pattern>{1}, {0}</pattern>
<dateTimeFormatLength type="short">
		<pattern>{1}, {0}</pattern>

My recommendation is that we base it on the month and dow:

MMMM => if E+ then long, else full
MMM => medium
else => short

If the date is relative, probably also the full.


Change History

comment:1 Changed 5 years ago by emmons

  • Status changed from new to assigned
  • Component changed from unknown to spec
  • Priority changed from assess to medium
  • Milestone changed from UNSCH to 24final
  • Owner changed from anybody to pedberg
  • Type changed from unknown to enhancement

comment:2 Changed 5 years ago by pedberg

Spec bug for CLDR, need ICU ticket to implement

comment:3 Changed 5 years ago by pedberg

Base on patterns in the *skeleton*

Agreed in TC 2013-09-11

comment:4 Changed 5 years ago by pedberg

  • Status changed from assigned to accepted
  • Review set to mark

OK, specified how to choose which dateTimeFormat to use when combining dateFormatItems for date & time parts of a requested skeleton, but also when combining standard date & time patterns. Also added brief info about how skeletons & corresponding patterns can have field lengths adjusted to match a request, and deleted the deprecated "default" element in various DTD snippets and examples.

The iCU ticket to implement the dateFormatItems combining procedure is http://bugs.icu-project.org/trac/ticket/10395

comment:5 Changed 5 years ago by mark

  • Status changed from accepted to closed
  • Resolution set to fixed

Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.