Unifont - Bugs: bug #51422, Jamo don’t form syllable blocks
You are not allowed to post comments on this tracker with your current authentication level.
bug #51422: Jamo don’t form syllable blocks
Submitter: | David Corbett <dscorbett> | ||
Submitted: | Sun 09 Jul 2017 12:24:26 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Works For Me |
Privacy: | Public | Assigned to: | unifoundry |
Open/Closed: | Closed |
Thu 28 Dec 2017 03:26:16 AM UTC, comment #4: |
Paul Hardy <unifoundry> |
Sun 09 Jul 2017 09:06:17 PM UTC, comment #3: David,
|
Paul Hardy <unifoundry> |
Sun 09 Jul 2017 02:57:44 PM UTC, comment #2: Unifont can do this, and I think you’ve misunderstood the scope of my suggestion.
|
David Corbett <dscorbett> |
Sun 09 Jul 2017 05:07:33 AM UTC, comment #1: David,
|
Paul Hardy <unifoundry> |
Sun 09 Jul 2017 12:24:26 AM UTC, original submission:
Hangul jamo don’t combine into syllable blocks; for example, ⟨ᅞᆦᇾ⟩. The jungseong and jongseong (vowels and trailing consonants) should be treated as combining characters. Some jamo will need to be shifted or made a bit smaller to avoid overlapping other jamo. U+115F HANGUL CHOSEONG FILLER and U+1160 HANGUL JUNGSEONG FILLER should have blank 2-cell-wide glyphs. |
David Corbett <dscorbett> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-12-28 | unifoundry | Status | Postponed | Works For Me | |
Assigned to | None | unifoundry | |||
Open/Closed | Open | Closed | |||
2017-07-12 | unifoundry | Status | None | Postponed |
Powered by Savane 3.13-d3ae.
Corresponding source code
These are not combining characters, and any substitutions would be handled by an input method editor and/or use an intelligent OpenType font with glyph substitutions. Unifont is neither of those. So I am going to leave the Jamo glyphs as they are.
Paul Hardy