Consolidation of CJK component unification across different regions to reduce unnecessary characters (for 2022)

_This page is under construction as I have posted this too early without checking. But for now I have made sufficient edits that will remove references to Serif and focus on Sans mostly._

This page is created to consolidate all my issues for every single component that may need unification, without opening too many separate issues. This one is for Source Han Sans, so my unification objectives will be different compared to Serif.

[Well we have people reporting glyphs that do not conform to China's 新字形 rule](https://github.com/adobe-fonts/source-han-sans/issues/313), because I think the glyphs are choke full having to cater to different national standards, so only the most common characters (including some traditional Chinese characters) would get the 新字形 treatment and others would have the JP/TW/HK look because they are rare characters that no practical person in China would be using. By unifying some components as they pointed out earlier, there can be more room for CN-style glyphs for rare characters.

For the time being, any components I missed in the initial edit is in a quote from the above link. I will update this page to include them in the future.
> If there are not enough slots left, maybe we should consider merging some non-essential regional differences like ⻌, ⺮, 䒑 (as in 豆), 𠂆 between CN and JP? And we can also keep only the Japanese style of Japanese dingbats like ㍿. I believe those have been suggested in other issues.

So, to summarise from the Serif page:

> Over time, I will start nitpicking more details which I deem unnecessary and can be shared with as many regions as possible, without breaking the respective national government glyph standard rules too much. My general preference is towards JP-style glyph shapes with some exceptions. The purpose is to ensure that by unifying components, we can keep it under the 65536 glyph limit and have more room to add necessary glyphs in the future.
>
> I am very well aware that some of the unifications presented here might have been discussed before (and which I didn't have the time to go through thoroughly) and could be rejected, but I am going to keep them because I would like a confirmation on whether these unifications can go ahead under the new design team from Arphic.
>
> For now it's a very quick summary, after Chinese New Year, I will update with a (perhaps incomplete) list of affected characters to fix for each affected component, if it isn't too much to handle. Unfortunately I may not be able to provide a complete list as finding the affected component in every character is very time consuming and there are currently no tools to do that instantly.

This page will be updated regularly if I can.

For components that I believe are safe to unify without breaking the 新字形 or Taiwan/Hong Kong educational standard rules
-----
### 夕 component

There are two ways to unify this: The JP/TW/HK way and the CN way.

#### JP/TW/HK way

If this is to be followed, I think having the dot (丶) touching (or at least be very close to) the ク part should be OK for the CN region.

As per the example image (will be updated soon for more characters), currently, the JP version of 多 and 移 is mapped to all regions except for CN (marked yellow).

On another note, 夕 could be mapped to TW/HK forms for the JP/KR regions for consistency sake, however, that might not be an option as this will go against Japanese standards (probably there are exceptions to the rule).

For 名, I suggest to adjust the CN glyph, the 夕 part, so the dot can touch the ク part, and in turn match the balance of the JP aesthetic. Then the TW/HK region can be mapped to the adjusted CN.

#### CN way (update)

I realised there's another problem: Most commercial Japanese typefaces seem to follow the CN form (except for the ones marked yellow).

In light of this, I suggest another way to unify the 夕 component: Adjust the JP/KR/TW/HK glyphs to match the CN form, and then remove the redundant CN glyphs.

Alternatively, the CN forms can be mapped to JP/KR/TW/HK whenever possible, and then remove those redundant glyphs. For those which components cannot be unified (e.g. 言 and 糸 component), adjustments would have to be made to the 夕 part to match the CN form.

But I think it would take a lot of trouble to do that, plus we probably need to consider if the TW/HK standard can allow for the CN form (BTW Hiragino Sans CNS and Pingfang TC/HK have the CN forms).

For the 死 component, it's only a matter of unifying the 夕 part, so:
1. Map JP-style glyph to CN region.
2. Map CN-style glyph to JP/KR/HK regions, and then adjust the TW form to match the CN part of 夕.

Example: U+6B7B itself

1. Map uni6B7B-JP to CN, and then remove uni6B7B-CN.
2. Map uni6B7B-CN to JP/KR/HK, remove uni6B7B-JP and adjust uni6B7B-TW to match the CN part of 夕.

### 冘 and 尤 components

[See here.](https://github.com/adobe-fonts/source-han-sans/issues/322)

### 竹 component
[See here.](https://github.com/adobe-fonts/source-han-sans/issues/182#issuecomment-365598683) Apparently this was not addressed even till today, and I suppose the suggestion was rejected, so I will bring this up again.

While I cannot suggest changes to resemble another commercial typeface, for the sake of unifying components, I have to give a reference. This reference is Hiragino Sans CNS, which was updated to completely follow Taiwan MOE standards on macOS 12 Monterey after many years of being an incomplete typeface with a mix of Japanese and mainland China glyph shapes. Basically put, the 竹 component in Hiragino Sans CNS is exactly the same as the GB (China) and the Japanese version.

### 亙 component (TW/HK regions only)
[See here.](https://github.com/adobe-fonts/source-han-sans/issues/315)

### Miscellaneous

#### 花 (U+82B1)

花 (U+82B1) would need have the KR form and CN form (marked in red) merged. Either:
1. Remove the CN glyph and assign uni82B1uE0101-JP to the CN locale.
2. Remove uni82B1uE0101-JP and assign uni82B1-CN glyph to the KR locale and that alternate JP glyph IVS thing in Adobe-Japan1, and then adjust the JP, TW and HK glyphs to match the form and balance of uni82B1-CN.

For components that are potentially controversial and might break the 新字形 or Taiwan/Hong Kong educational standard rules
-----
### 辶 component
[See here.](https://github.com/adobe-fonts/source-han-sans/issues/300)

### 人 component (when it's the top component)
Well I can't say any further, [because this was rejected already](https://github.com/adobe-fonts/source-han-sans/issues/205#issuecomment-500001082), [and Dr Lunde said it would be dangerous to suggest changes that would make Source Han Sans CN look like an existing commercial typeface,](https://github.com/adobe-fonts/source-han-sans/issues/202#issuecomment-506845868) but with a different design team, we'll never know for quite a long time.

### 今 component (TW/HK regions only)

The roof of 人 would have to be unified in order for this to happen. For now I would not touch this.

### Changelog

**UPDATE 1 (2022-02-06):** Added 花 (U+82B1) under Miscellaneous and clarified wording about unifying 死 component