Unifont - Bugs: bug #51807, Problems with Tai Tham
You are not allowed to post comments on this tracker with your current authentication level.
bug #51807: Problems with Tai Tham
Submitter: | David Corbett <dscorbett> | ||
Submitted: | Sun 20 Aug 2017 10:57:54 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Fixed |
Privacy: | Public | Assigned to: | unifoundry |
Open/Closed: | Closed |
Jump to the original submission
Tue 23 Jul 2019 02:37:53 PM UTC, comment #8: |
David Corbett <dscorbett> |
Tue 23 Jul 2019 03:09:50 AM UTC, comment #7: David,
|
Paul Hardy <unifoundry> |
Mon 22 Jul 2019 06:57:57 PM UTC, comment #6: If the spacing marks U+1A61, U+1A63, and U+1A64 are implemented as non-spacing, their glyphs from my original comment won’t work, so I’ve redrawn them. To make room, I moved most glyphs to the left one pixel, and redrew the pre-base marks to be narrower. While I was at it, I shifted the above-base tone marks and below-base medial consonants to the left and the below-base vowel signs to the right, to make overlaps less likely. I also removed a stray line from U+1A50.
|
David Corbett <dscorbett> |
Sun 21 Jul 2019 10:40:13 PM UTC, comment #5: David,
|
Paul Hardy <unifoundry> |
Mon 30 Jul 2018 11:40:24 AM UTC, comment #4: David,
|
Paul Hardy <unifoundry> |
Mon 30 Jul 2018 05:30:57 AM UTC, comment #3: David,
|
Paul Hardy <unifoundry> |
Mon 30 Jul 2018 04:18:44 AM UTC, comment #2: David,
|
Paul Hardy <unifoundry> |
Wed 20 Sep 2017 01:00:48 AM UTC, comment #1: Erratum: U+1A61, U+1A63, and U+1A64 should be removed from plane00-combining.txt. I had written that they should be removed from that file yet have x-offsets in that file, which are mutually exclusive. |
David Corbett <dscorbett> |
Sun 20 Aug 2017 10:57:54 PM UTC, original submission:
Minor problems
|
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 |
---|---|---|---|---|---|
2022-03-06 | unifoundry | Status | In Progress | Fixed | |
2019-08-11 | unifoundry | Open/Closed | Open | Closed | |
2019-07-23 | unifoundry | Status | None | In Progress | |
Assigned to | None | unifoundry |
Powered by Savane 3.13-758e.
Corresponding source code
Yes, I noticed that you removed the stray pixels when I diffed the glyphs. I don’t know how that slipped through. I’m glad someone is checking my work!
For the record, HarfBuzz zeroes mark widths by GDEF class for most scripts, not by Unicode general category, so I would not have expected any problem in HarfBuzz. Maybe other shaping engines have this problem.