You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 27, 2023. It is now read-only.
Concerning a very frequently used ideograph "的", there are two coherency problems:
It does not match with, for example, 玓, whose design has a "㇐" instead of a "㇔" in the right component. I believe similar issues can be fixed with reference to the mapping mechanism of Genne Gothic, which maps not only KR glyphs but JP glyphs (with variant selector) also to achieve the so-called traditional printing shapes 印刷舊字形.
A less urgent glitch. The left components do not align in the word 的皪. Though it's not a common word, it might be desirable to use contextual alternates to obtain a desired different design only in this word.
Even if it isn't this project's particular interest to provide traditional printing shapes I'd very much like to see a more coherent design!
The text was updated successfully, but these errors were encountered:
Thank you for your carefulness. The Han ideographs part of Glow Sans's TC version is completely based on Source Han Sans K 2.001. Glow Sans will not try to manually fix any glyph design problem. A friend of mine said he was willing to provide a full list for fine glyph mapping of the traditional orthography. If this problem does not require redesigning the glyphs, hopefully it will be solved sooner or later.
Thank you, that would be really helpful in fixing the first and most concerning problem. Currently a font like Genne Gothic which uses glyphs solely from Source Han Sans JP, KR and TC would cover most usage. Looking forward to a similar, even better, mapping plus Glow Sans's awesome design.
Concerning a very frequently used ideograph "的", there are two coherency problems:
Even if it isn't this project's particular interest to provide traditional printing shapes I'd very much like to see a more coherent design!
The text was updated successfully, but these errors were encountered: