Time format characters 'h' and 'k'

[Mark Davis ☕️ via CLDR-Users]

As I recall, one of those historical anomalies (like the surrogate range
not being at the top of the BMP). Then h and then H came first. When later
we found evidence of 1..24 systems, we added 'k' (we tend to do lowercases
first), and still later we found the 0..1 case, and that got 'K'.

It's a bit like the narrow form being MMMMM; that was created long after
the abbreviated and long forms.

Mark

(https://twitter.com/mark_e_davis)

On Sat, Aug 19, 2017 at 6:07 PM, Martin J. Dürst <duerst at it.aoyama.ac.jp>
wrote:

> Hello Mark, others,
>
> On 2017/08/19 16:32, Mark Davis ☕️ via CLDR-Users wrote:
>
>> http://unicode.org/reports/tr35/tr35-dates.html#dfst-hour. I think this
>> captures it:
>>
>> midn. noon midn.
>> h 12 1 ... 11 12 1 ... 11 12
>> H 0 1 ... 11 12 13 ... 23 0
>> K 0 1 ... 11 0 1 ... 11 0
>> k 24 1 ... 11 12 13 ... 23 24
>>
>
> I don't know the details. It looks to me as if these would be the fours
> selections that make sense (12 vs. 24 hours, and 0 vs. 1 index origin).
>
> However, what doesn't make sense to me here is that while the distinction
> of origin is made by upper vs. lower case (0 origin: H, K;
> 1 origin: h, k), the distinction between 12h and 24h is mixed up (12
> hours: h, K; 24 hours: H, k).
>
> I wonder who came up with this, or if it is a mistake.
>
> Regards,    Martin.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20170820/89573318/attachment.html>