ChiuKongGothic icon indicating copy to clipboard operation
ChiuKongGothic copied to clipboard

Need more removed 1.004 JP glyphs / 請恢復一些已刪除 v1.004 JP 字型

Open Marcus98T opened this issue 2 years ago • 5 comments

Please reinstate some removed v1.004 JP glyphs, these files from here will help you review which glyphs to reinstate. I already sorted out all the JP glyphs needed to restore. 請恢復一些已刪除 v1.004 JP 字形,以下提供的PDF可參考。我已經整理了所有需要恢復的JP字形。

With a little help from my friend on sorting through all the infos, here is a full list: shs-v1.004-full-removed.pdf shs-1.004-full-removed.txt

List / 列表:

㐄㐪㐭㐯㑁㑒㑓㑞㑧㑹㒴㒶㓃㓜㓪㓬㔁㔓㔗㔜㔦㔰㔱㔳㔴㔵㔺㔼㕽㖖㖢㖫㗁㗔㗖㗫㘜㙄㙻㚆㚈㚉㚕㚻㛒㛷㜾㝇㝋㝑㝘㝙㝟㝠㝭㞪㞴㞷㞻㞼㟜㟟㟡㟧㟻㠉㠌㠎㠕㠝㠼㡞㡢㡣㡫㡬㡳㡽㢈㢋㢑㢕㢜㢢㢧㢴㣀㣃㣞㣠㣢㣪㤅㤠㤺㥀㥁㥐㥦㥩㥱㥲㦘㦛㦣㦥㦶㧈㧞㧨㨋㨗㨯㨻㪉㪘㪟㪰㪽㪿㫀㫤㫦㫨㫴㫷㬁㬊㬝㬥㬦㬧㬵㬶㭃㭕㭸㭻㮵㮻㯬㰓㰞㰭㰮㰱㰸㱅㱋㱝㲊㲝㳖㳙㳟㳵㳺㴀㴠㵒㵓㵧㵮㵶㵼㷱㸳㹣㹲㹹㼋㼘㼼㽪㾗㿂㿋㿤䀵䁀䁈䂊䂖䂢䂲䃍䃝䃾䄀䄂䄇䄦䅆䅥䆒䇊䇋䇒䇡䇱䈞䈧䈴䈵䉖䉜䉽䊅䊑䊢䊣䊯䊶䋁䋇䋐䋛䋨䌆䌇䌓䌖䌞䌬䍪䎩䏕䏬䑑䑧䑨䑭䒔䒢䒱䓐䓓䔊䔤䔵䔻䕌䕞䕶䖇䗙䗝䗟䘖䘘䘡䘱䘺䙞䙴䚈䚬䚱䚸䛑䛕䛦䛭䛮䛱䜋䜏䜢䜬䝉䝩䝺䝿䞯䠁䡱䢉䢗䢞䢟䢣䣛䣩䣴䤎䤛䤝䤞䤢䤣䤤䤩䤰䤱䤷䥃䥍䥎䥏䥢䥬䥮䥶䦇䦓䦚䦜䦾䧢䧶䩫䪄䪵䫓䫫䬢䭕䭰䮞䮲䯫䯬䰇䰌䰵䰺䱶䲬䲳䲾䴟䴡䶑䶬䶯䶰丽义乒乓仅优佢俖俷偝偮偯偻傇傼僁僗僠僽儮兝刽剎剢劲卟叻叼吆吔吙吣吷呯咂咓咔咣哋唒唿啋啕啥喌嗥嗦嗧嗨嘀嘟嘭噘嚉嚎嚐囆囔团垒垦垹垺埮堸塻壆奋奰孢孻实宪尘屉幂幙幠庴归忧怹恳悐惦愣慔懱执扰抚抰挎挕揍揞搣摁摵擏擫攎敥敹晱暯曞朌杹栠栦栺梑楧榵橗歶氋沎沷浂渃渪湡漜潕潹澫澿濿瀎瀱灱灴炋炓炣烅烆烌烍烒烳烴焟焨焬焺焻煂煄煍煏煔煘煟煰煼熁熂熼熽燆燊燤燨爃爅爏爞爣爧牊犡狅猼獛獳玤瑌盚眏眲瞁瞨矎磰磱礝礣稪稬竼笁笚笝筂筄筘筣筸箂箣篘篢篻篽篿簊簝簵粎糐罼肊肐肕胉胑胣脁脕脙脪脴腂腄腖腜腢腬膫臐舕艼芅芞芵苃苖苲苵苸苼茙茠茦茿荁荋荴莁莋莐莗莤莮莯菄菋菗龓鿅

Exceptions / 例外

Do not restore / 不要恢復:

  • 䂖 (looks weird)
  • 䎩 (JP is 畄 not 甾)
  • 䏕 (TW form good enough)
  • 义 (looks weird)
  • 垹 (TW form good enough)
  • 屉 (世 looks weird)
  • 归 (looks weird)
  • 燊 (already restored in v2)
  • 佢 (since you already changed it)

Restore and change / 恢復與修改:

  • 䌓 (毎 change to 每)
  • 䁈 (戸 change to 戶, with the JP detail shown on left)
Screenshot 2021-09-29 at 01 56 29

Do not restore, but change yourself / 不要恢復,但自己修改:

  • 䈧 (爫 change to 爪)

I see some characters like 㑒, 惦 and 嗦 are recreated like JP glyphs in this font, but please do more and reinstate all the JP glyphs from this PDF given, even if they are rare characters that the Chinese don't use. 我看在這個字體中重建了「㑒」、「惦」與「嗦」的 v.1004 版本,但請可以完全恢復已刪除 v1.004 JP 字形,就算有些字是中文很少使用的字符。

Source file of 1.004 here: https://github.com/adobe-fonts/source-han-sans/releases/tag/1.004 https://github.com/adobe-fonts/source-han-sans/releases/tag/1.004R

Marcus98T avatar Sep 28 '21 14:09 Marcus98T

Thank you for your suggestion and for your work.

Please reinstate some removed v1.004 JP glyphs, these files from here will help you review which glyphs to reinstate. I already sorted out all the JP glyphs needed to restore. 請恢復一些已刪除 v1.004 JP 字形,以下提供的PDF可參考。我已經整理了所有需要恢復的JP字形。

The list will be carefully reviewed and a decision will be made as to which should be restored.

Reinstating these glyphs is similar to implement the new glyph, as the font is built on the stroke-separated source file, but it might reduce the time working on each glyph as there is a ready-to-use reference.

even if they are rare characters that the Chinese don't use. 就算有些字是中文很少使用的字符。

Priority will be given to the glyph which is listed in the common-used character (Written Chinese), then some Less-Than-Common characters(次常用字) covered by BIG-5(common-used part)/GB2312. The shorthand characters(略字) of the character in these sets are also included.

Some examples of the particular character, for reference only:

  • 丽 JP 1.004 might be restored as the default glyph of CL version and assigned IVS code point E0100 as the glyph is defined in the Hanyo-Denshi IVD set. But MN and CM remain the TW glyph with IVS code point E0101.
  • 佢 JP 1.004 might be restored as the default glyph of MN version, as other characters containing 巨 part use the E0100 glyph form(Shin-Jitai) in MN version.
  • 刽 吆 嚐 垒 etc. might be redesigned to match the design of JP 1.004 form, since these characters are not perfected.
  • 归 JP 1.004 might not be restored as it is not defined in any of the IVD sets.
  • 䁈 might be included in both 戸 and 戶 form as they are both defined in the Hanyo-Denshi IVD set, and 戶 is the default one(Ext A character, low priority)
  • 䈧 same as above, might be included in both 為 and 爲(爪)form.

ChiuMing-Neko avatar Sep 29 '21 02:09 ChiuMing-Neko

I got it. As mentioned before, I have provided a list of exceptions (which to clarify, only applied to the CL version), since I was very busy. If you look at the PDF or use v1.004 of SHS, you can see which character I am talking about.

Exceptions / 例外

Do not restore / 不要恢復:

  • 䂖 (looks weird)
  • 䎩 (JP is 畄 not 甾)
  • 䏕 (TW form good enough)
  • 义 (looks weird)
  • 垹 (TW form good enough)
  • 屉 (世 looks weird)
  • 归 (looks weird, however, you also mentioned separately not to restore it)
  • 燊 (already restored in v2)
  • 佢 (since you already changed it, but now you say this form can be restored for the MN version)

Restore and change / 恢復與修改:

  • 䌓 (毎 change to 每)
  • 䁈 (戸 change to 戶, with the JP detail shown on left)
Screenshot 2021-09-29 at 01 56 29

Do not restore, but change yourself / 不要恢復,但自己修改:

  • 䈧 (爫 change to 爪)

Which is why I did not remove any character from the whole list of JP glyphs to restore.

Now come to think of it you can probably restore the JP glyph of 䏕 and 垹 for the MN version or so, but low priority.

~~Also of note, the list also missed 鄉, which had a JP form in v1.004, can be used for the MN version.~~ EDIT: Sorry, it was never there, only in Serif.

Marcus98T avatar Sep 29 '21 08:09 Marcus98T

「鄉(U+9109)」is already added in 1.200 since it is the common code point used by Chinese text, but not unified due to the source separation rule in UNO range (CNS 11643-1992 plane 3).

圖片

but other characters that are already unified, have different default glyph forms in different versions of the font. 圖片

ChiuMing-Neko avatar Nov 26 '21 13:11 ChiuMing-Neko

Progress Report of reimplementing removed glyph as of Ver 1.240 (WIP)

Since this version(1.240) focuses on the glyph in BIG-5 Level 1, the reimplemented removed glyph is mostly the commonly used character in the Chinese language. The Ver 1.240 is still work-in-progress, the glyph listed below is not final yet.

  • 乒 Re-added in 1.240.

  • 乓 Re-added in 1.240.

  • (Default glyph of MN version) 佢 Re-added in 1.221, Adjusted in 1.240.

  • 偯 Re-added in 1.240.

  • 刽 Re-added in 1.200 but the 人 component looks weird. Fixed in 1.220, and currently in 1.240 is adjusted to match the 1.004 JP glyph.

  • 剎 Re-added in 1.200.

  • (Actually is 𠡍 U+2084D, therefore U+52B2 continue using CN glyph) 𠡍 Re-added in 1.200 as the glyph for U+2084D, Adjusted in 1.240.

  • 叻 Re-added in 1.240, but not 100% matched. May removed since the difference between CN glyph and the re-added glyph is pretty closed.

  • 叼 Re-added in 1.240.

  • 吆 Re-added in 1.200, Adjusted in 1.240

  • 吔 Re-added in 1.240

  • 咓 Re-added in 1.240.

  • 咔 Re-added in 1.240.

  • 哋 Re-added in 1.240

  • 啥 Re-added in 1.230, Adjusted in 1.240 as requested in #9

  • 嗨 Re-added in 1.200, Adjusted in 1.240, but not 100% matched. Consider the newest design to be the final design.

  • (Default glyph of CL version) 嘟 Re-added in 1.230, Adjusted in 1.240

  • 嚐 Re-added in 1.210, May adjusted in 1.240

  • 囔 Re-added in 1.230, may not match the removed 1.004 glyph but consider the current design to be the final design.

Not consider re-implemented (If they were only minor differences with removed JP glyph):

仅优奋对

ChiuMing-Neko avatar Feb 09 '22 16:02 ChiuMing-Neko

Great job with the recreation of most glyphs, some are 95% close, others are like around 75% good enough. Except I also raised an issue with Adobe regarding the inconsistency of the position of the 口 radical between the CN and JP glyphs.

As I said before, at least we make do with this until, if ever, the v1.004 overlapping source is released. I have also raised an issue with Adobe to see if any similar looking 1.004 JP glyphs can be restored for a future SHSans release, and in addition, I have also created a consolidated issue page regarding whether it is possible to merge some components to the JP form without breaking Chinese national standards, which may also possibly include restoring some v1.004 JP glyphs on Adobe's end.

Not consider re-implemented:

仅优

For 优, same as above, except I've already reported a similar separate issue.

Well I did my part, but whether Adobe would work on these issues would be up to them.

Marcus98T avatar Feb 09 '22 17:02 Marcus98T