| 19:45 | <hallvors> | I'd like some developer comments on this idea: https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0173.html - any idea how I can get it some attention? Seems Chrome is busy improving their clipboard stuff support, which is cool, but it means it would be nice to find a good feature detection story soon.. (also posted on W3C #webapps, with |
| 19:45 | <hallvors> | apologies to those in both rooms..) |
| 19:55 | <hallvors> | Asking IRC questions on a Saturday afternoon in April is obviously not the right way to get attention :) |
| 21:15 | <gsnedders> | Unicode 3.0 is such a clusterfuck. "A process shall interpret Unicode code values as 16-bit quantities"; "Unicode scalar value: a number N from 0 to 10FFFF_{16}", "A Unicode scalar value is also referred to as acode position or a code point" |
| 21:27 | <caitp> | does that predate the supplementary planes? |
| 21:27 | <caitp> | and if so, does it matter? |
| 21:29 | <gsnedders> | caitp: no, it doesn't |
| 21:29 | <gsnedders> | caitp: the supplementary planes are defined but have no allocations as of Unicode 3.0 |
| 21:31 | <caitp> | but that's still like a decade and a half ago |
| 21:32 | <caitp> | just not totally sure why this still matters, the bmp should be more or less compatible still no? |
| 21:32 | <caitp> | not really following unicode too closely |
| 21:32 | <gsnedders> | it is, but it's still hurting insofar as pushing everything to use 16-bit code units as their basic unit |
| 21:32 | <gsnedders> | instead of code points |
| 21:43 | <caitp> | well it suits most of the people using computers that don't need to use ideographic writing systems often pretty nicely |
| 21:43 | <caitp> | so that's something at least |