DateIntervalFormat::getDateTimeSkeleton() should not normalize 'H' to 'h'

Description

Deleted Component: formatting

Per e-mail discussion today, DateIntervalFormat::getDateTimeSkeleton() should not normalize 'H' to 'h'.

See also CldrBug:2155

Activity

Show:
TracBot
July 1, 2018, 10:07 AM
Trac Comment 3 by —2009-04-17T17:41:41.000Z

We are deferring the CLDR intervalFormats change for this to CLDR 1.8, so this bug goes to ICU 4.4

TracBot
July 1, 2018, 10:07 AM
Trac Comment 4 by —2009-04-17T21:03:42.000Z

The goal is:
1. if the Key has 'hM' only and Data is 'hM',
input hM, or HM should match either input and produce the hM data

2. if the Key has both 'hM' and 'HM',
and Data is 'hM' and 'HM',
Input hM should match hM data, BUT input 'HM' should match HM data

Should use same pattern matching as DateTimePatternGenerator ("closest match")

TracBot
July 1, 2018, 10:07 AM
Trac Comment 6 by —2010-02-12T20:38:00.000Z

reassigning to pedberg provisionally.

TracBot
July 1, 2018, 10:07 AM
Trac Comment 7 by —2010-02-15T19:37:46.000Z

Checked in some changes to address thus. Have not fully expanded the tests to check this yet, since the new tests will depend on the new CLDR data that is not in yet. The current tests only check skeletons with 'h' and they pass.

TracBot
July 1, 2018, 10:07 AM
Trac Comment 10 by —2016-10-05T23:14:33.489Z

Milestone 4.3.5 deleted

Fixed

Assignee

Peter Edberg

Reporter

Peter Edberg

Components

None

Labels

None

Reviewer

None

Priority

blocks-release

Time Needed

Days

Fix versions