Some radicals in Kangxi Radicals block of CN region may need to be remapped to match GB18030-2022.
Immediate attention
U+2FC1 ⿁ requires immediate update to change from current CN glyph to TW glyph with broken bottom left stroke. This crashes with U+2EE4 ⻤ which should have connected bottom left stroke. These two radical characters should be differentiated.
Ref: U+2FBB ⾻ and U+2EE3 ⻣ with different direction in Unicode code charts and GB18030-2022. (notice the broken bottom left stroke of U+2FC1 ⿁ although it's minor)
Other remapping suggestions
The following glyphs can be remapped according to GB18030-2022.
U+2FCB ⿋ from uni9EF9-CN to uni9EF9-TW
U+2F3E ⼾ from uni6237-CN to uni6236-CN
U+2FC7 ⿇ from uni9EBB-CN to uni9EBB-TW
U+2FCD ⿍ from uni9F0E-CN to uni9F0E-JP
However, note that such remapping might cause other issues such as #438 .
U+2F4F ⽏ do not have the corresponding glyphs to be remapped. This may or may not be added.
Some radicals in Kangxi Radicals block of CN region may need to be remapped to match GB18030-2022.
Immediate attention
U+2FC1
Ref: U+2FBB 
⿁requires immediate update to change from current CN glyph to TW glyph with broken bottom left stroke. This crashes with U+2EE4⻤which should have connected bottom left stroke. These two radical characters should be differentiated.⾻and U+2EE3⻣with different direction in Unicode code charts and GB18030-2022. (notice the broken bottom left stroke of U+2FC1⿁although it's minor)Other remapping suggestions
The following glyphs can be remapped according to GB18030-2022.
⿋from uni9EF9-CN to uni9EF9-TW⼾from uni6237-CN to uni6236-CN⿇from uni9EBB-CN to uni9EBB-TW⿍from uni9F0E-CN to uni9F0E-JPHowever, note that such remapping might cause other issues such as #438 .
U+2F4F
⽏do not have the corresponding glyphs to be remapped. This may or may not be added.