Consolidation of CJK component unification across different regions to reduce unnecessary characters (for 2022) #326
Comments
|
I have made some amendments, so if anyone have the initial unfinished version via email and saved it internally (I am not sure how people save their issues and whether revisions are taken into account), please see this page on Github for the most up to date version, and save it instead to replace that unfinished version. |
|
I found a tool (in Chinese) that would enable me to easily have details on specific components, but the site is not HTTPS secure, so... I apologize for not doing any colour coding. I really wanted to make the Adobe team's work easier and get my point across as quick as possible before the next release cycle, but I am very busy with work and I am not even sure if they would really work on it. So the pictures I uploaded will mostly be devoid of colour so there won't be specific characters to adjust, replace or remove. 夕 componentIf it can be unified to one form as per the following options, it will save quite an amount of CIDs to make way for new glyph additions. Option 1: JP/TW/HK form
Option 2: CN form
List may still not be exhaustive. The characters to review are:
名 componentThe characters to review are:
Green means v1 JP glyph that can possibly be restored (if the JP/TW/HK form is chosen). As said before, 名 (U+540D) is a special case. If the JP/TW/HK form is chosen, follow this below quote:
Otherwise adjust the JP glyph of 名 to the CN form of 夕. 多 componentThe characters to review are:
In this picture, blue means the v1 JP glyphs which were removed (and cannot be restored) and grey means v1 does not have the glyph. 死 componentThe characters to review are:
Blue means v1 JP glyph that cannot be restored. |
Marcus98T
changed the title
|
I am not sure if we should unify the 祭 component for Source Han Sans, as I observed, the top right part of 祭 (open loop for JP, closed loop for CN) is considered a regional difference. However, I personally think that "regional difference" is not very obvious and should be consolidated, either to the open JP form or the closed CN form. If the closed CN form is preferred, the JP glyphs must be adjusted, do not use the CN glyphs directly because the JP glyphs are better designed (with the exception of those characters that contain 宀, e.g. 察, which is an essential regional difference).
In cyan are the Adobe-Japan1 glyphs. The characters in the list are: And please adjust 聺 (U+807A, marked in yellow, below image) to be more consistent with the other characters as well.
|
|
While I earlier said that 女, 弓 and 廴 in JP/KR should have the feet removed and follow CN for all regions, and this may not happen because it can be controversial, I will put here for organizational purposes and I will edit out that part in my original issue. If the design team believes that the feet is essential as a regional difference, do not consolidate. Here is the original quote (and slightly edited with a new picture):
My rationale at that time was because I thought some Japanese fonts have the feet removed for UD (Universal Design) purposes (although it may not be applied to all the characters). Here is the quote:
Also, I originally asked to redesign 廴 back to v1, but I have retracted this request because as quoted by @NightFurySL2001:
EDIT: Edited last quote in this post for clarity. |
|
Also, I am recently aware that there was a request to disunify 豆 and 立 for TW and HK use, which was posted 1.5 years ago as of this writing, however, it should not be in the page where the original issue is unifying the 辶 component between CN and JP, because it's not relevant, so here is the quote:
So here is my viewpoint (keeping relevant to this thread): I strongly suggest against this because I do not believe that strictly following the 台標 standard would be of any benefit and would make readability even uglier for Traditional Chinese users, and could create more CIDs than reducing them. Even a commercial 台標 font, like Hiragino Sans CNS (for TW/HK use), follows the same glyphs as Hiragino Sans GB (for CN use, as pictured below).
This is also why I will not retract my request that the top 竹 radical be unified to the JP form for all regions, although it would probably not happen for v3.
I do not think the 台標 standard is a strict guideline, and I am not saying Adobe should stop supporting 台標, because most other components will have to follow that standard, like the 肉月 radical in 腔, 脞, 胞, etc., but rather the designers should balance aesthetics and standards. |
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, 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.
So, to summarise from the Serif page:
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:
Example: U+6B7B itself
冘 and 尤 components
See here.
竹 component
See here. 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.
Miscellaneous
花 (U+82B1)
花 (U+82B1) would need have the KR form and CN form (marked in red) merged. Either:
For components that are potentially controversial and might break the 新字形 or Taiwan/Hong Kong educational standard rules
辶 component
See here.
人 component (when it's the top component)
Well I can't say any further, because this was rejected already, and Dr Lunde said it would be dangerous to suggest changes that would make Source Han Sans CN look like an existing commercial typeface, 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
The text was updated successfully, but these errors were encountered: