I’m unhappy that the notion of tweaking Shift_JIS is even brought up. blogs.technet.microsoft.com/… (via @vyv03354). (I’m also unhappy about the prospect of swapping the meaning of some two-byte and four-byte sequences in GB18030.) Opportunity to migrate to UTF-8 has been long.
1
6
Replying to @hsivonen @vyv03354
Is this assigning unassigned codepoints, or making a breaking change (presumably one expected not to cause real-world breakage)?

Apr 7, 2018 · 7:04 AM UTC

2
Replying to @davidbaron @hsivonen @vyv03354
Also, is there an expectation for when the new character will be assigned in @unicode and how long we'll have from that point until it's heavily in demand?
Replying to @davidbaron @hsivonen
To be clear, Japan MS said they will NOT change Shift_JIS. But they should not tell a lie about the reasoning. (They said they did not assign a Shift_JIS codepoint for SQUARE ERA NAME HEISEI, but it is wrong.)
1