Skip to main content
7 events
when toggle format what by license comment
Nov 4, 2016 at 4:58 comment added SamB And I think they'd have to kill off Windows an JavaScript first, too, since they both rely on UTF-16. (It might be possible to rectify this in JavaScript's case, though?)
Jun 7, 2016 at 16:00 comment added Rahly But highly unlikely, unless they start adding characters like mad. As of U8.0, only 120k are assigned. They added ~8k characters in this iteration. If they keep it up, it'll needed expanding at version ~106.
Jun 1, 2016 at 19:01 comment added ssokolow @Rahly That may eventually change, though. Before the maximum valid Unicode code point was reduced to U+10FFFF to meet the limitations of UCS-2 (basically UTF-16 without surrogate pairs), UTF-8 could require up to 6 bytes to represent a 32-bit code point because of how it encodes "start of character" and "continuation of character" to ensure that parser synchronization can be re-acquired no matter where you start parsing within a byte stream. It's always a possibility that they'll eventually decide to reverse that decision because they're running out of unassigned code points.
May 30, 2016 at 19:35 comment added Rahly 63 is the max if every character uses the max encoding of 4 bytes per code point. This is the same for any of the UTF schemas (UTF-16 and UTF-32)
Feb 3, 2015 at 11:10 review Late answers
Feb 3, 2015 at 11:40
Feb 3, 2015 at 10:54 review First posts
Feb 3, 2015 at 10:59
Feb 3, 2015 at 10:52 history answered Richard Jelinek CC BY-SA 3.0