-
Notifications
You must be signed in to change notification settings - Fork 651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glyphs of U+11ED ᇭ, U+D7F5 ퟵ, U+D7F6 ퟶ #6
Comments
Thank you. I will report this issue to Sandoll's designer for consideration. |
Sandoll's designer confirmed this bug, which affects the following 15 glyphs: uni11ED, uni11ED.tjmo01 through uni11ED.tjmo04 (4), uniD7F5, uniD7F5.tjmo01 through uniD7F5.tjmo04 (4), uniD7F6, and uniD7F6.tjmo01 through uniD7F6.tjmo04 (4). The first update will reflect fixed versions of these glyphs. |
BTW, under which condition is tjmo01, tjmo02, tjmo03, or tjmo04 displayed? I want to know what a trailing (final) consonant needs to be preceded by in each condition in order to have its glyph replaced with one of tjmo0[1-4]. |
(Note that the fourth set, for the tjmo04 glyphs, includes ranges.) |
To follow up on this, in addition to fixing the 15 glyphs that were originally reported, Sandoll's designer decided to adjust the following four additional glyphs: uni118C.vjmo01, uni1190.vjmo01, uni1192.vjmo01, and uni1112uni119Euni11D9. The last glyph is one of the 500 high-frequency archaic hangul syllables. |
tjmo01: when preceded by ᅡ, ᅣ, ᅪ, ᆄ, ᆉ, ᆎ, ᆦ, ힲ, ힹ, ퟅ Thank you for listing those conditions. Do those apply to Source Han Sans as well, without any differences? |
Yes, Source Han Sans is the same. |
Just in case, can you please list the conditions for ljmo0[1-6] as well? I just want to check whether what I thought is the same as the ones defined in the font. |
The one about uni1112uni119Euni11D9 is interesting. I wonder how ᄒᆞᇙ became 흐ᇙ. Perhaps you can keep the current glyph (흐ᇙ) and rename that uni1112uni1173uni11D9, and add a new glyph for uni1112uni119Euni11D9. Rather than getting rid of the well-designed 흐ᇙ glyph (rather than the effort used to design the 흐ᇙ glyph getting wasted), I suggest keeping it while adding the correct glyph for ᄒᆞᇙ. |
I received the 19 updated glyphs from Sandoll's designer and processed them this morning. The PDF synopsis below shows the ExtraLight, Medium, and Heavy weights, and the combining glyphs are shown before I shifted them to the left and zero-out their horizontal advances (so that they are easier to see here). Also, the CIDs don't correspond to Source Han Serif CIDs, but are for the back-end source data. |
Here are the CID to working glyph name correspondences:
|
Any L + lmjo04 through ljmo06 are identical to lmjo01 through ljmo03, respectively, except that the "any T" portion is removed from their context. |
About yesieung- jamo: Great. For those three vjmo01 glyphs: The new design is better, as they are followed by a T. Under the old design, it is hard to see the short horizontal strokes. Conditions for ljmo: Thank you. They are the same as I thought. |
Note to self (and to others who want to test archaic hangul jamo in Source Han Sans and Source Han Serif) ljmo01: when followed by [ᅡ, ᅢ, ᅣ, ᅤ, ᅥ, ᅦ, ᅧ, ᅨ, ᅵ / ᆘ, ᆙ, ᆝ, ᆥ, ힾ, ힿ, ퟀ, ퟄ] + any T vjmo01: when followed by a T tjmo01: when preceded by [ᅡ, ᅣ, ᅪ / ᆄ, ᆉ, ᆎ, ᆦ, ힲ, ힹ, ퟅ] |
Examples for testing ljmo01: Lᆘᇫ vjmo01: ᄓVᇫ tjmo01: ᄓᆄT Do NOT use these when testing: |
Thank you for confirming the fixes. |
Consolidated with Issue #39. |
Yesieung (ㆁ), not ieung (ㅇ). This includes .tjmo0[1-4] glyphs of those three hangul jamo characters as well.
The text was updated successfully, but these errors were encountered: