Time format characters 'h' and 'k'

[Mark Davis ☕️ via CLDR-Users]

> placing the surrogates at top would have avoided the emergence of UTF-8
with compatiblity with 7-bit US-ASCII

I don't see what you're talking about at all — and I was one of the people
present at the times when all the decisions were being made.

Mark

(https://twitter.com/mark_e_davis)

On Sun, Aug 20, 2017 at 1:16 PM, Philippe Verdy <verdy_p at wanadoo.fr> wrote:

> 2017-08-20 11:42 GMT+02:00 Mark Davis ☕️ via CLDR-Users <
> cldr-users at unicode.org>:
>
>> As I recall, one of those historical anomalies (like the surrogate range
>> not being at the top of the BMP).
>>
>
> I don't think this is an anomaly: placing the surrogates at top would have
> avoided the emergence of UTF-8 with compatiblity with 7-bit US-ASCII.
> Placing them at top would have broken many more things and UTF-8 would have
> not become the most useful encoding and the default now to be supported by
> all web standards.
>
> Ideally the surrogates should have been at end of the BMP (possibly
> leaving only a few non-characters after them or tweaking surrogates and
> allcoations in places so that they would have not used U+FFFE and U+FFFF
> kept as reserved surrogates not used in any pair for valid codepoints).
> They would have sorted in binary mode and preserved the binary order
> between UTF-8, UTF-16 and UTF-32...
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20170820/3c4668e8/attachment.html>